Duplexed communications in one or more cells

Abstract

A method can include receiving, by a wireless device: first configuration parameters of a first cell, wherein the first configuration parameters indicate first symbols, of the first cell, as sub-band full duplex (SBFD) symbols; and second configuration parameters of a second cell. The second configuration parameters indicate second symbols, of the second cell, as SBFD symbols. The method can also include, in response to the second cell being activated: transmitting, via the second cell, uplink transmissions via at least one symbol of the second symbols; and not transmitting, via the first cell, uplink transmissions via the first symbols. The method can further include deactivating the second cell and, in response to the second cell being deactivated, transmitting, via the first cell, uplink transmissions via one or more symbols of the first symbols.

Description

Docket No.: 25-1055PCTTITLEDuplexed Communications in One or More CellsCROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of U.S. Provisional Application No. 63 / 777,438, filed March 25, 2025, which is hereby incorporated by reference in its entirety.BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0017] FIG. 12A and FIG. 12B respectively illustrate examples of three downlink and uplink beam management procedures.

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

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

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

[0021] FIG. 15 illustrates an example of a wireless device in communication with a base stationDocket No.: 25-1055PCT

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

[0023] FIG. 17A, FIG. 17B, and FIG. 17C illustrate aspects of example embodiments according to the present disclosure.

[0024] FIG. 18A and FIG. 18B illustrate aspects of example embodiments according to the present disclosure.

[0025] FIG. 19 illustrates an aspect of an example embodiment according to the present disclosure.

[0026] FIG. 20A and FIG. 20B illustrate aspects of example embodiments according to the present disclosure.

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

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

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

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

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

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

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

[0034] 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 capabil ity(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 totalDocket No.: 25-1055PCTwireless devices in a coverage area. This disclosure may refer to, for example, a plurality of wireless devices of a given LTE or 5G release with a given capability and in a given sector of the base station. The plurality of wireless devices in this disclosure may refer to a selected plurality of wireless devices, and / or a subset of total wireless devices in a coverage area which perform according to disclosed methods, and / or the like. There may be a plurality of base stations or a plurality of wireless devices in a coverage area that may not comply with the disclosed methods, for example, those wireless devices or base stations may perform based on older releases of LTE or 5G technology.

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

[0036] 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 {cell 1 , 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.

[0037] 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 suchDocket No.: 25-1055PCTas "a control message to cause in a device” may mean that a control message has parameters that may be used to configure specific characteristics or may be used to implement certain actions in the device, whether the device is in an operational or non-operational state.

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

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

[0040] 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 LabVI E WMathScript. 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, applicationspecific 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.

[0041] FIG. 1A illustrates an example of a mobile communication network 100 in which embodiments of the present disclosure may be implemented. The mobile communication network 100 may be, for example, a public land mobileDocket No.: 25-1055PCTnetwork (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.

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

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

[0044] 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 maybe a telephone, smartphone, 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.

[0045] 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 (g N B, 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 g N B Central Unit (gNB-CU) and at least one a g NB Distributed Unit (gNB-DU).

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

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

[0048] The RAN 104 maybe 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.

[0049] 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. 1 A, the RANs of earlier 3G and 4G networks, and those of future networks yet to be specified (e.g . , a 3GPP 6G network). NG-RAN implements 5G radio access technology known as New Radio (NR) and may be provisioned to implement 4G radio access technology or other radio access technologies, including non-3GPP radio access technologies.

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

[0051] 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-Docket No.: 25-1055PCTto-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).

[0052] As illustrated in FIG. 1B, 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. 1B 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- / ! nter-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 UEanda DN.

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

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

[0055] 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 g NBs, illustrated as g NB 160A and g NB 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 orDocket No.: 25-1055PCTmore 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.

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

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

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

[0059] 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.Docket No.: 25-1055PCT

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

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

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

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

[0064] 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.Docket No.: 25-1055PCT

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

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

[0067] 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 g N B 220 (at the MAC 222) for downlink and uplink The MACs 212 and 222 may be configured to perform error correction through Hybrid Automatic Repeat Request (HARQ) (e.g. , one HARQ entity per carrier in case of Carrier Aggregation (CA)), priority handling between logical channels of the UE 210 by means of logical channel prioritization, and / or padding. The MACs 212 and 222 may support one or more numerologies and / or transmission timings. In an example, mapping restrictions in a logical channel prioritization may control which numerology and / or transmission timing a logical channel may use. As shown in FIG. 3, the MACs 212 and 222 may provide logical channels as a service to the RLCs 213 and 223.

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

[0069] 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 g N B 220. An uplink data flow through the NR user plane protocol stack may be similar to the downlink data flow depicted in FIG.4A.Docket No.: 25-1055PCT

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

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

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

[0073] FIG. 4B further illustrates MAC control elements (CEs) inserted into the MAC PDU by a MAC, such as MAC 212 or MAC 222. For example, FIG. 4B illustrates two MAC CEs inserted into the MAC PDU. MAC CEs may be inserted at the beginning of a MAC PDU for downlink transmissions (as shown in FIG. 4B) and at the end of a MAC PDU for uplink transmissions. MAC CEs maybe 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.

[0074] 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.Docket No.: 25-1055PCT

[0075] 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 includes, for example:

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

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

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

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

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

[0081] T ransport 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 includes, for example:

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

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

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

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

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

[0087] 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 includes, for example:

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

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

[0090] - 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;Docket No.: 25-1055PCT

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

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

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

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

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

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

[0097] The RRCs 216 and 226 may provide control plane functionality between the UE 210 and the gNB 220 or, more generally, between the UE 210 and the RAN. The RRCs 216 and 226 may provide control plane functionality between the UE 210 and the gNB 220 via signaling messages, referred to as RRC messages. RRC messages may be transmitted between the UE 210 and the RAN using signaling radio bearers and the same / similar PDCP, RLC, MAC, and PHY protocol layers. The MAC may multiplex control-plane and user-plane data into the same transport block (TB). The RRCs 216 and 226 may provide control plane functionality such as: broadcast of system information related to AS and NAS; paging initiated by the CN or the RAN; establishment, maintenance and release of an RRC connection between the UE 210 and the RAN; security functions including key management; establishment, configuration, maintenance and release of signaling radio bearers and data radio bearers; mobility functions; QoS management functions; the UE measurement reporting and control of the reporting; detection of and recovery from radio link failureDocket No.: 25-1055PCT(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.

[0098] 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 UE210 depicted in FIG. 2Aand FIG.2B, or any other wireless device described in the present disclosure. As illustrated in FIG. 6, a UE may be in at least one of three RRC states: RRC connected 602 (e.g., RRC_CONNECTED), RRC idle 604 (e.g., RRC_I DLE), and RRC inactive 606 (e.g., RRCJNACTIVE).

[0099] 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. 1B, the gNB 220 depicted in FIG. 2Aand 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.

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

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

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

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

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

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

[0106] AgNB, such asgNBs 160 in FIG. 1B, maybe split into two parts: a central unit (gNB-CU), and one or more distributed units (gNB-DU). A gNB-CU maybe 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.

[0107] 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 streamsDocket No.: 25-1055PCTmay be treated as though they are in the frequency domain and used as inputs to an Inverse Fast Fourier Transform (IFFT) block that transforms them into the time domain. The IFFT block may take in F source symbols at a time, one from each of the F parallel symbol streams, and use each source symbol to modulate the amplitude and phase of one of F sinusoidal basis functions that correspond to the F orthogonal subcarriers. The output of the IFFT block may be F time-domain samples that represent the summation of the F orthogonal subcarriers. The F time-domain samples may form a single OFDM symbol. After some processing (e.g. , addition of a cyclic prefix) and up-conversion, an OFDM symbol provided by the IFFT block maybe 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.

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

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

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

[0111] 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 RBDocket No.: 25-1055PCTspans twelve consecutive REs in the frequency domain as shown in FIG. 8. An NR carrier may be limited to a width of 275 RBs or 275*12 = 3300 subcarriers. Such a limitation, if used, may limit the NR carrier to 50, 100, 200, and 400 MHz for subcarrier spacings of 15, 30, 60, and 120 kHz, respectively, where the 400 MHz bandwidth may be set based on a 400 MHz per carrier bandwidth limit.

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

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

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

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

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

[0117] 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.: 25-1055PCT

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

[0119] A base station may semi-statical ly 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.

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

[0121] In an example, a base station may semi-statical ly 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).

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

[0123] 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 ata switching point. In the example illustrated in FIG. 9, the BWPs include: a BWP 902 with a bandwidth of 40 MHz and a subcarrier spacing of 15 kHz; a BWP 904 with a bandwidth of 10 MHz and a subcarrier spacing of 15 kHz; and a BWP 906 with a bandwidth of 20 MHz and a subcarrier spacing of 60 kHz. The BWP 902 may be an initial active BWP, and the BWP 904 may be a default BWP. The UE may switch between BWPs at switching points. In the example of FIG. 9, the UE may switch from the BWP 902 to the BWP 904 at a switching point 908. The switching at the switching point 908 may occur for any suitable reason, for example, in response to an expiry of a BWP inactivity timer (indicating switching to the default BWP) and / or in response to receiving a DCI indicating BWP 904 as the active BWP. The UE may switch at a switching point 910 from active BWP 904 to BWP 906 in response to receiving a DCI indicating BWP 906 as the active BWP The UE may switch at a switching point 912 from active BWP 906 to BWP 904 in response to an expiry of a BWP inactivity timerDocket No.: 25-1055PCTand / 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.

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

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

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

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

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

[0129] 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 maybe 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 indicateDocket No.: 25-1055PCTwhich 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).

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

[0131] 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 UC11031, UC11032, and UC11033, maybe transmitted in the uplink of the PCell 1021. Uplink control information (UCI) related to the downlink CCs of the PUCCH group 1050, shown as UC11071, UC11072, and UC11073, maybe 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.

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

[0133] 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.Docket No.: 25-1055PCT

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

[0135] FIG. 11A illustrates an example of an SS / PBCH block's structure and location. A burst of SS / PBCH blocks may include one or more SS / PBCH blocks (e.g., 4 SS / PBCH blocks, as shown in FIG. 11 A). Bursts may be transmitted periodically (eg., 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. 11 A 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.

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

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

[0138] 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 / PBCHDocket No.: 25-1055PCTblock. 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.

[0139] The PBCH may use a QPSK modulation and may use forward error correction (PEC). The PEC 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 maybe pointed to a frequency. The UE may search for an SS / PBCH block at the frequency to which the UE is pointed.

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

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

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

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

[0144] 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 mayDocket No.: 25-1055PCTselectively 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.

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

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

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

[0148] 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).Docket No.: 25-1055PCT

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

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

[0151] The UE may transmit an uplink DMRS to a base station for channel estimation. For example, the base station may use the uplink DMRS for coherent demodulation of one or more uplink physical channels. For example, the UE may transmit an uplink DMRS with a PUSCH and / or a PUCCH. The uplink DM-RS may span a range of frequencies that is similar to a range of frequencies associated with the corresponding physical channel. The base station may configure the UE with one or more uplink DMRS configurations. At least one DMRS configuration may support a front-loaded DMRS pattern. The front-loaded DMRS maybe 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 symbolsofa 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.

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

[0153] 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 atDocket No.: 25-1055PCTleast 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.

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

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

[0156] 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 colocated (QCLed) if one or more large-scale properties of the channel over which a first symbol on the first antenna portDocket No.: 25-1055PCTis 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 ( x) parameters.

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

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

[0159] The three beams illustrated in FIG. 11 B maybe configured fora 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.

[0160] CSI-RSs such as those illustrated in FIG. 11 B (e.g., CSI-RS 1101, 1102, 1103) maybe 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 referenceDocket No.: 25-1055PCTsignals. 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.

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

[0162] FIG. 12A illustrates examples of three downlink beam management procedures: P1 , P2, and P3. Procedure P1 may enable a UE measurement on transmit (Tx) beamsofa 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.

[0163] FIG. 12B illustrates examples of three uplink beam management procedures: U 1 , U2, and U3. Procedure U1 may be used to enable a base station to perform a measurement on Tx beams of a UE, e.g., to support a selection of one or more UE Tx beams and / or base station Rx beams (shown as ovals in the top row and bottom row, respectively, of U 1 ). Beamforming at the UE may include, e.g., a Tx beam sweep from a set of beams (shown in the bottom rows of U1 and U3 as ovals rotated in a clockwise direction indicated by the dashed arrow). Beamforming at the base station may include, e.g., an Rx beam sweep from a set of beams (shown, in the top rows of U1 and U2, as ovals rotated in a counterclockwise direction indicated by the dashed arrow). Procedure U2 may be used to enable the base station to adjust its Rx beam when the UE uses a fixed Tx beam. The UE and / or the base station may perform procedure U2Docket No.: 25-1055PCTusing 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.

[0164] 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 initiation of the BFR procedure. The UE may detect the beam failure based on a determination that a quality of beam pair link(s) of an associated control channel is unsatisfactory (e.g., having an error rate higher than an error rate threshold, a received signal power lower than a received signal power threshold, an expiration of a timer, and / or the like).

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

[0166] 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 RRCJ DLE state and / or an RRC_INACTIVE 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.

[0167] 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 21312, a Msg 31313, and a Msg 41314. The Msg 1 1311 may include and / or be referred to as a preamble (or a random access preamble). The Msg 21312 may include and / or be referred to as a random access response (RAR).

[0168] 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 oneDocket No.: 25-1055PCTor 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 broadcastor multicast the one or more RRC messages to one or more UEs. The one or more RRC messages may be UE-specific (e.g., dedicated RRC messages transmitted to a UE in an RRC_CONNECTED state and / or in an RRC J NACTIVE 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 31313. Based on the one or more RACH parameters, the UE may determine a reception timing and a downlink channel for receiving the Msg 21312 and the Msg 41314.

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

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

[0171] 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 31313. 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 theDocket No.: 25-1055PCTassociation between the one or more preambles and the at least one reference signal is configured by an RRC message.

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

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

[0174] The Msg 21312 received by the UE may include an RAR. In some scenarios, the Msg 21312 may include multiple RARs corresponding to multiple UEs. The Msg 21312 may be received after or in response to the transmitting of the Msg 1 1311. The Msg 21312 may be scheduled on the DL-SCHand indicated on a PDCCH using a random access RNTI (RA-RNTI). The Msg 21312 may indicate that the Msg 1 1311 was received by the base station. The Msg 21312 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 31313, and / or a Temporary Cell RNTI (TC-RNTI). After transmitting a preamble, the UE may start a time window (e.g., ra-ResponseWndow) to monitor a PDCCH for the Msg 21312. The UE may determine when to start the time window based on a PRACH occasion that the UE uses to transmit the preamble. For example, the UE may start the time window one or more symbols after a last symbol of the preamble (e.g., at a first PDCCH occasion from an end of a preamble transmission). The one or more symbols may beDocket No.: 25-1055PCTdetermined 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:

[0175] RA-RNTI= 1 + sjd + 14 x tjd + 14 x 80 xfjd + 14 x 80 x 8 x ul_carrierjd, where sjd maybe an index of a first OFDM symbol of the PRACH occasion (e.g., 0 < sjd < 14), tjd may be an index of a first slot of the PRACH occasion in a system frame (e.g., 0 < tjd < 80), fjd may be an index of the PRACH occasion in the frequency domain (e.g., 0 s fjd < 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).

[0176] The UE may transmit the Msg 31313 in response to a successful reception of the Msg 21312 (e.g., using resources identified in the Msg 21312). The Msg 31313 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 31313 and the Msg 41314) 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 31313 (e.g., a C-RNTI if assigned, a TC-RNTI included in the Msg 21312, and / or any other suitable identifier).

[0177] The Msg 41314 may be received after or in response to the transmitting of the Msg 31313. If a C-RNTI was included in the Msg 31313, 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 31313 (e.g., if the UE is in an RRC_IDLE state or not otherwise connected to the base station), Msg 41314 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 31313, the UE may determine that the contention resolution is successful and / or the UE may determine that the random access procedure is successfully completed.

[0178] The UE may be configured with a supplementary uplink (SUL) carrier and a normal uplink (NUL) carrier. An initial access (e.g., random access procedure) may be supported in an uplink carrier. For example, a base station may configure the UE with two separate RACH configurations: one for an SUL carrier and the other for an NUL carrier. For random access in a cell configured with an SUL carrier, the network may indicate which carrier to use (NUL or SUL). The UE may determine the SUL carrier, for example, if a measured quality of one or more reference signals is lower than a broadcast threshold. Uplink transmissions of the random access procedure (e.g., the Msg 1 1311 and / or the MsgDocket No.: 25-1055PCT31313) 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 31313 based on a channel clear assessment (e.g., a listen-before-talk).

[0179] FIG. 13B illustrates a two-step contention-free random access procedure. Similar to the four-step contentionbased 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 21322. The Msg 1 1321 and the Msg 21322 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 31313 and / or the Msg 41314.

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

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

[0182] FIG. 13C illustrates another two-step random access procedure. Similar to the random access procedures illustrated in FIGS. 13Aand 13B, a base station may, prior to initiation of the procedure, transmit a configuration message 1330 to the UE. The configuration message 1330 maybe 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.

[0183] 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 31313 illustrated in FIG. 13A.Docket No.: 25-1055PCTThe transport block 1342 may comprise UCI (e.g., an SR, a HARQACK / 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 21312 (e.g., an RAR) illustrated in FIGS. 13Aand 13B and / or the Msg 41314 illustrated in FIG. 13A.

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

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

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

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

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

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

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

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

[0192] 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 theDocket No.: 25-1055PCTbase 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).

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

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

[0195] The base station may transmit, to the UE, RRC messages comprising configuration parameters of one or more CORESETs and one or more search space sets. The configuration parameters may indicate an association between a search space set and a CORESET. A search space set may comprise a set of PDCCH candidates formed by CCEs ata 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)

[0196] As shown in FIG. 14B, the UE may determine a time-frequency resource fora 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 compriseDocket No.: 25-1055PCTdecoding 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).

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

[0198] 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.Docket No.: 25-1055PCT

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

[0200] After determining a PUCCH resource set from a plurality of PUCCH resource sets, the UE may determine a PUCCH resource from the PUCCH resource set for UCI (HARQ-ACK, CSI, and / or SR) transmission. The UE may determine the PUCCH resource based on a PUCCH resource indicator in a DCI (e.g., with a DCI format 1_0 or DCI for 1_1) received on a PDCCH. A three-bit PUCCH resource indicator in the DCI may indicate one of eight PUCCH resources in the PUCCH resource set. Based on the PUCCH resource indicator, the UE may transmit the UCI (HARQ-ACK, CSI and / or SR) using a PUCCH resource indicated by the PUCCH resource indicator in the DCI.

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

[0202] 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.1Docket No.: 25-1055PCT

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

[0204] 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 (Ml MO) or multi-antenna processing, and / or the like.

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

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

[0207] 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 (eg., 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.Docket No.: 25-1055PCT

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

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

[0210] 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 embodimentsDocket No.: 25-1055PCT

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

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

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

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

[0215] 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.Docket No.: 25-1055PCTWhen 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.

[0216] FIG. 17 A shows an example timing diagram as per an aspect of an embodiment of the present disclosure. The example of FIG. 17A may be used together with or independently from any of the previous examples (e.g., in FIGS. 1A-16D).

[0217] In the example of FIG. 17A, a wireless device 1700 receives message(s) 1706. Wireless device 1700 may receive message(s) 1706 from a base station 1720.

[0218] Wireless device 1700 may be, for example, a sidelink wireless device. Wireless device 1700 may be, for example, a non-terrestrial network (capable) wireless device, e.g., global navigation satellite system (GNSS)-enabled wireless device. Wireless device 1700 may be, for example, a network control repeater (NCR), e.g., NCR-mobile termination (MT) or NCR-forwarding (Fwd). Wireless device 1700 may be, for example, an integrated access and backhaul (IAB) node, e.g., IAB-MT. Wireless device 1700 may be an air-to-ground (ATG) wireless device. Wireless device 1700 may be an Internet-of-Things (loT) wireless device, e.g., ambient loT wireless device, narrowband loT (NB-loT) wireless device. Wireless device 1700 maybe, for example, an intelligent reflective surface (IRS) or reflective intelligent surface (RIS) node. Wireless device 1700 may be a joint communication and sensing (JCAS) or an integrated sensing and communication (ISAC) device or node (e.g., a device capable of or capable of performing JCAS or ISAC).

[0219] Base station 1720 may be, for example, a satellite. Base station 1720 may be, for example, a g NB or an eNB. Base station 1720 may be, for example, a gNB-CU. Base station 1 20 may be, for example, a gNB-DU. Base station 1720 maybe, for example, an NCR. Base station 1720 maybe, for example, an IAB node. Base station 1720 maybe, for example, a sidelink device or node. Base station 1720 may be, for example, an intelligent reflective surface (IRS) or reflective intelligent surface (RIS) node. Base station 1 20 may be, for example, a reader node.

[0220] Message(s) 1706 may be (or comprise) one or more radio resource control (RRC) messages. For example, the one or more RRC messages may be (or comprise) one or more RRC reconfiguration messages, one or more RRC setup messages, one or more RRC release messages, and / or one or more RRC resume messages.

[0221] Message(s) 1706 may be (or comprise), for example, one or more system information messages. For example, the one or more system information messages message may be (or comprise) one or more system information blocks (SIBs), one or more synchronization signal / physical broadcast channel (SS / PBCH) blocks, and / or one or more master information blocks (MIBs).

[0222] Message(s) 1706 may be (or comprise), for example, a layer-2 message, such as, e.g., a MAC CE, a MAC sub-header, a MAC PDU, a MAC subPDU, a MAC payload, a MAC header, and / or any other type of message in MAC layer.Docket No.: 25-1055PCT

[0223] Message(s) 1706 may be, for example, a layer-1 message, such as, e.g., a DCI, a PDCCH message, a PDSCH message, a sidelink message, a PSSCH message, a PSCCH message, an access link message, a control link message, and / or any other type of message in a lower layer (e.g., the physical layer).

[0224] Message(s) 1706 may indicate, or comprise, configuration parameters 1708. Configuration parameters 1708 may be, for example, RRC configuration parameters.

[0225] In an example, the configuration parameters 1708 may be for one or more cells.

[0226] Configuration parameters being for the one or more cells may comprise, be the same as, and / or referred to as follows: the configuration parameters being of the one or more cells, the configuration parameters being associated with the one or more cells, the configuration parameters being configured for the one or more cells, the configuration parameters being assigned to the one or more cells, the configuration parameters configuring the one or more cells, and / or the like.

[0227] The one or more cells may comprise a cell. The wireless device may be camped on the cell. The wireless device camping on the cell may comprise or be the same as the wireless device being located in a geographical area covered by the cell, the wireless device being served by the cell, the wireless device being configured (e.g., by configuration parameters 1708) the cell, the wireless device being in the cell, the wireless device receiving configuration parameters for the cell, and / or the like.

[0228] The cell may comprise (or be associated with) one or more bandwidth parts (BWPs). The one or more BWPs may comprise one or more uplink BWPs and / or one or more downlink BWPs.

[0229] Configuration parameters 1708 may be of (e.g., for, associated with, or configured for) the one or more BWPs.

[0230] Configuration parameters 1708 may be of (e.g., for, associated with, or configured for) a BWP (or per each BWP) of the one or more BWPs of the cell.

[0231] The cell may be, for example, a serving cell (e.g., of the wireless device).

[0232] The cell may be, for example, a non-serving cell (e.g., a layer 1 or layer 2 triggered mobility (LTM) candidate cell, inter-cell beam management cell, inter-cell multi transmission and reception point (TRP) cell, and / or any other type of cell that is configured by configuration parameters 1708 as a non-serving cell).

[0233] The cell may be, for example, a special cell (SpCell). For example, the cell may be a primary cell (PCell) and / or a primary secondary cell (PSCell). For a master cell group, SpCell maybe PCell. For a secondary cell group, SpCell maybe PSCell.

[0234] In some embodiments, “PCell,” “SpCell,” and / or “PSCell” may be used interchangeably.

[0235] The cell may be, for example, a deactivated cell (e.g., deactivated SCell, deactivated PSCell, and / or the like).

[0236] The cell may be, for example, a network energy savings (NFS) cell. For example, the cell may be configured or associated with: cell discontinuous transmission (DTX) operation; cell discontinuous reception (DRX) operation; on-demand SIB transmission operation; on-demand synchronization signal block (SSB) transmission operation; adaptation of random access (RA) resources, e.g., RA parameters, RACH resources, PRACH resources; adaptation of SSB;Docket No.: 25-1055PCTand / or adaptation of paging occasions. The cell maybe, for example, an anchor cell (e.g., a cell that is used as a reference cell for NES operation).

[0237] The cell may be, for example, a reference cell (e.g., for determining resources, timing, synchronization, and / or the like) for transmissions and / or receptions via a second cell. The second cell may be different from the cell.

[0238] The cell may be, for example, an NTN cell. For example, configuration parameters 1708 may comprise one or more NTN-specific / related configuration parameters. The cell may be an NTN cell, for example, based on configuration parameters 1708 comprising or indicating the one or more NTN-specific / related configuration parameters.

[0239] The cell may be, for example, a licensed cell. For example, uplink (UL) and downlink (DL) communications via the cell may occur over licensed frequency bands (e.g., spectrum).

[0240] The cell may be, for example, an unlicensed cell. For example, the cell may be for shared spectrum channel access. For example, UL and DL communications via the cell may occur over unlicensed frequency bands (e.g., spectrum).

[0241] The cell may comprise (e.g., be configured with or associated with) one or more BWPs. For example, configuration parameters 1708 may indicate the one or more BWPs for the cell.

[0242] In an example, each of the one or more BWPs may be (or comprise) a UL BWP and / or a DL BWP.

[0243] Configuration parameters 1708 may be (or comprise), for example, cell-specific configuration parameters. For example, configuration parameters 1708 may be transmitted to a plurality of wireless devices in the cell. Cell specific configuration parameters may be referred to as common configuration parameters, group-common configuration parameters, non / not dedicated configuration parameters, configuration parameters received before receiving dedicated configuration parameters, and / or the like.

[0244] Configuration parameters 1708 maybe (or comprise), for example, BWP-specific configuration parameters. For example, configuration parameters 1708 may be applicable for a BWP, of the one or more BWPs, of the cell.

[0245] In an example, the configuration parameters 1708 may be (or comprise) wireless device specific configuration parameters Wireless device specific configuration parameters may be referred to as, for example, dedicated configuration parameters, non / non-common configuration parameters, UE-specific configuration parameters, and / or the like.

[0246] In some embodiments, duplexing mode may be referred to as duplexing or duplexed or duplex (operation or operating) mode. For example, sub-band full duplex (SBFD) mode may be referred to as or be equivalent to SBFD operation, SBFD symbols, SBFD slots, and / or SBFD operating mode.

[0247] In some embodiments, “symbol” or “slot’ may indicate a time unit, an occasion, a time occasion, a resource, a time resource, time interval, time duration, time period, and / or time window. In some embodiments, the terms “symbols" and “slots” may be used interchangeably.

[0248] In some embodiments, a slot may comprise one or more symbols (e.g., 14 symbols).Docket No.: 25-1055PCT

[0249] FIG. 17B shows an exampleof a duplexing mode 1702 as per an aspect of an embodiment of the present disclosure. Duplexing mode 1702 may be, for example, a time division duplex (TDD) mode (or TDD operation). In duplexing mode 1702, transmission time intervals (e.g., symbols in FIG. 17B) may overlap in frequency (e.g., are in the same frequency or same band) and are transmitted on, or received on, at different times (e.g., different symbols and / or do not overlap in time). Duplexing mode 1702 may be for (e.g., of, associated with, configured for, applicable for) unpaired spectrum operation (e.g., communication in, on, or within unpaired spectrum).

[0250] The example of FIG. 17B may be used together with or independently from any of the previous examples (e.g., in FIGS. 1A-17A).

[0251] The example of FIG. 17B illustrates five symbols. In an example, configuration parameters 1708 may indicate which of the five symbols are for downlink (DL) and which of the five symbols are for uplink (UL). For example, in the exampleof FIG. 17B, configuration parameters 1708 indicate that the first four symbols, of the five symbols, are DL symbols and that the fifth / last symbol, of the five symbols, is an UL symbol. Examples of how the configuration parameters 1708 indicate which symbols are uplink and downlink are provided below.

[0252] In an example, a symbol may be (e.g., configured or designated as) a DL symbol based on configuration parameters 1708 indicating that the symbol is to be for (e.g., of, for, associated with, or configured for) DL operation. For example, a symbol may be a DL symbol, for example, based on configuration parameters 1708 indicating the symbols to be for (e.g., of, for, associated with, or configured for) only DL operation and the symbol being one of the symbols. As another example, a symbol may be a DL symbol based on configuration parameters 1708 indicating that the symbol is a flexible symbol and one or more second configuration parameters (e.g., dedicated configuration parameters, MAC CE, DCI) indicating that the symbol is associated with (e.g., indicated for, for, of, and / or the like) DL operation.

[0253] In an example, a symbol may be an UL symbol based on configuration parameters 1708 indicating the symbol to be configured with (e.g., associated with, for, of) UL operation. For example, a symbol may be a UL symbol, for example, based on configuration parameters 1708 indicating the symbols to be configured with (e.g., associated with, for, of) only UL operation. As another example, a symbol may be a UL symbol based on configuration parameters 1708 indicating that the symbol is a flexible symbol and one or more second configuration parameters (e.g., dedicated configuration parameters, MAC CE, DCI) indicating that the symbol is associated with (e.g., indicated for, for, of, and / or the like) UL operation.

[0254] In an example, wireless device 1700 may receive message(s) 1710 from base station 1720. For example, wireless device 1700 may receive message(s) 1710 from base station 1720 via a DL symbol (e.g., any of the first four symbols of the five symbols shown in FIG. 17B). In another example, wireless device 1700 may transmit message(s) 1712 to base station 1720 via a UL symbol (e.g., the fifth / last symbol of the five symbols shown in FIG. 17B).

[0255] Configuration parameters 1708 may be, comprise, or be referred to as TDD-DL-UL-ConfigCommon.Docket No.: 25-1055PCT

[0256] Configuration parameters 1708 may comprise a parameter (e.g., dl-UL-TransmissionPeriodicity) indicating a periodicity of DL-UL (or UL-DL) pattern for one or more symbols within a period. The DL-UL pattern may be referred to as a periodicity of a DL-UL pattern. For example, the parameter indicating the periodicity of DL-UL pattern may indicate that the first four symbols shown in FIG. 17B are DL symbols and the last symbol shown in FIG. 17B Isa UL symbol.

[0257] Configuration parameters 1708 may comprise a parameter indicating a number of consecutive DL (e.g., full DL, DL only) slots / symbols at the beginning of each DL-UL pattern. For example, the parameter indicating the number of consecutive DL slots / symbols at the beginning of each DL-UL pattern may indicate that the first four symbols shown in FIG. 17B are DL symbols and the last symbol shown in FIG. 17B is a UL symbol.

[0258] Configuration parameters 1708 may comprise a parameter indicating a number of consecutive DL symbols / slots at the beginning of a slot following a last (full) DL slot (e.g., as derived from the parameter indicating the number of consecutive full DL slots / symbols at the beginning of each DL-UL pattern).

[0259] Configuration parameters 1708 may comprise a parameter (e.g., nrofUplinkSlots) indicating a number of consecutive UL (e.g., full UL, UL only) slots / symbols at the end of each DL-UL pattern. For example, the parameter indicating a number of consecutive UL slots / symbols at the end of each DL-UL pattern may indicate that the first four symbols shown in FIG. 17B are DL symbols and the last symbol shown in FIG. 17B is a UL symbol.

[0260] Configuration parameters 1708 may comprise a parameter indicating a number of consecutive UL symbols at the end of the slot preceding the first full UL slot. The parameter indicating a number of consecutive UL symbols in the end of the slot preceding the first full UL slot may indicate that the first four symbols shown in FIG. 17B are DL symbols and the last symbol shown in FIG. 17B is a UL symbol.

[0261] According to the example of FIG. 17B in which duplexing mode 1702 is TDD, wireless device 1700 and / or base station 1720 may transmit and receive a signal on / in / via the same BWP and / or carrier but at different transmission time intervals (e.g., different symbols / slots). For example, wireless device 1700 may receive message(s) 1710 via the first symbol shown in FIG. 17B, which is a DL symbol, and / or transmit message(s) 1712 via the last symbol shown in FIG. 17B, which is a UL symbol. Wireless device 1700 may transmit and / or receive message(s) 1710 in, on, or via the same carrier and / or BWP in the example of FIG. 17B using duplexing mode 1702.

[0262] In some aspects, the terms “BWP,” “carrier,” “band,” “bandwidth,” “component carrier,” “center frequency,” “cell,” “center carrier,” “frequency,” and / or “band combination” may be used interchangeably.

[0263] FIG. 17C illustrates an example of a duplexing mode 1704 as per an aspect of an embodiment of the present disclosure. The duplexing mode 1704 may be a frequency division duplexing (FDD) mode in which transmission time intervals (e.g., symbols in FIG. 17C) overlap in time (e.g., same symbol) and are transmitted on, or received on, different frequencies (e.g., different frequency bands and / or do not overlap in frequency). The duplexing mode 1704 may be for (e.g., of, associated with, configured for, applicable for) paired spectrum operation (e.g., communication in, on, or within paired spectrum).Docket No.: 25-1055PCT

[0264] The example of FIG. 17C may be used together with or independently from any of the previous examples (e.g, in FIGS. 1A-17B).

[0265] FIG. 17C shows five symbols. Unlike in FIG. 17B, each symbol, of the five symbols, illustrated in FIG. 17C, may be both UL and DL symbols. For example, wireless device 1700 may transmit an uplink signal via any of the five symbols and receive a downlink signal via any of the five symbols. Wireless device 1700 may transmit the uplink signal and receive the downlink signal on the same symbol(s) but on different frequencies, such as different BWPs or different carriers (e.g., downlink carrier, SUL, NUL). In duplexing mode 1704 (e.g., FDD), wireless device 1700 and / or base station 1720 does not receive the DL signal and transmit the UL signal on the same symbol(s) and the same BWP (or the same carrier).

[0266] In some embodiments, transmitting via a symbol (or slot) may be the same as or be referred to as transmitting on, in, during, within, based on, after, before, or with the symbol (or slot).

[0267] In some embodiments, receiving via a symbol (or slot) may be the same as or be referred to as receiving on, in, during, within, based on, after, before, or with the symbol (or slot).

[0268] For example, wireless device 1700 may transmit the UL signal on the first symbol shown in FIG. 17C via a UL BWP. Wireless device 1700 may receive the DL signal on the first symbol shown in FIG. 17C via a DL BWP. In the example of FIG. 17C, the UL BWP may be different from the DL BWP. For example, the UL BWP and the DL BWP may be separated in frequency domain as shown in FIG. 17C. The UL BWP and the DL BWP may not overlap in frequency domain as shown in FIG. 17C. The UL BWP and / or the DL BWP may be of, for, associated with, or configured for the same cell (e.g., the cell, a cell of the one or more cells).

[0269] T ransmitting or receiving a signal or message via a BWP may be the same as or be referred to as transmitting or receiving, respectively, the signal or message on, in, using, based on, with, within, and / or over the BWP.

[0270] T ransmitting or receiving a signal or message via a cell may be the same as or be referred to as transmitting or receiving, respectively, the signal or message on, in, using, based on, with, within, to, toward, from and / or over the cell.

[0271] The base station 1720 may receive the UL signal and / or transmit the DL signal.

[0272] In some embodiments, the duplexing mode 1702 and / or the duplexing mode 1704 may be referred to as a half-duplex mode or a non-SBFD (mode / operation).

[0273] FIG. 18A illustrates an example of a duplexing mode 1802 as per an aspect of an embodiment of the present disclosure. Duplexing mode 1802 may be an advanced duplexing mode in which transmitting time intervals (e.g., symbols in FIG. 17B, FIG. 17C, and / or FIG. 18A) overlap in both frequency (e.g., same band, same BWP, same carrier) and time (e.g., same symbols). Duplexing mode 1802 may be, for example, sub-band full-duplex (SBFD) mode.

[0274] The example of FIG. 18A may be used together with or independently from any of the previous examples (eg, in FIGS. 1A-17C).Docket No.: 25-1055PCT

[0275] Duplexing mode 1802 may be different from duplexing mode 1702. Duplexing mode 1802 may be different from duplexing mode 1704.

[0276] Duplexing mode 1802 may be applicable for (e.g., associated with, configured for) unpaired spectrum operation (e.g., as in TDD operation as shown in FIG. 17B).

[0277] In another example, duplexing mode 1802 may be applicable for (e.g., associated with, configured for) paired spectrum operation (e.g., as in FDD operation as shown in FIG. 17C).

[0278] In some embodiments, “SBFD” may be (or comprise, refer to, be replaced with, be equivalent to) “advanced duplex,” “full duplex,” “partial full duplex,” “sub-band non-overlapping full-duplex,” “flexible duplex,” and / or the like.

[0279] FIG. 18A illustrates five symbols. Each symbol, of the five symbols, may be DL symbol, UL symbol, flexible symbol, and / or SBFD symbol. Each symbol, of the five symbols, may be on (e.g., over, in, via, for, of, configured for, assigned with, and / or associated with) the same carrier or BWP.

[0280] In the example of FIG. 18A, the five symbols may comprise a symbol 1804, a symbol 1806, a symbol 1808, a symbol 1810, and a symbol 1812.

[0281] Symbol 1804 may be a DL symbol. Symbol 1806 may be a DL symbol. Symbol 1812 may be a UL symbol.

[0282] A DL symbol may be a symbol via (e.g., over, in, on) which a wireless device may receive a DL signal. DL symbol may be a symbol via (e.g., over, in, on) which a base station may transmit a DL signal. A base station may not receive a UL signal via DL symbol. A wireless device may not transmit a UL signal via DL symbol.

[0283] A UL symbol may be a symbol via (e.g., over, in, on) which a wireless device may transmit a UL signal. A UL symbol may be a symbol via (e.g , over, in, on) which a base station may receive a UL signal. A base station may not transmit a DL signal via UL symbol. A wireless device may not receive a DL signal via UL symbol.

[0284] In some embodiments, the terms “operation” and “mode” may be used interchangeably. For example, SBFD mode and SBFD operation may be used interchangeably.

[0285] In an example, message(s) 1706 and / or configuration parameters 1708 may indicate that symbol 1804 is a DL symbol. Message(s) 1706 and / or configuration parameters 1708 may indicate that symbol 1806 is a DL symbol. Message(s) 1706 and / or configuration parameters 1708 may indicate that symbol 1812 is a UL symbol.

[0286] Message(s) 1706 and / or configuration parameters 1708 may indicate that symbol 1808 is an SBFD symbol. Message(s) 1706 and / or configuration parameters 1708 may indicate that symbol 1810 is an SBFD symbol.

[0287] An SBFD symbol may be (or comprise) a symbol via (e.g., over, in, on) which a wireless device and / or a base station may transmit and receive DL and UL signal(s), respectively. For example, an SBFD symbol may comprise (or be associated with, configured with) one or more sub-bands. The wireless device may transmit signals via (e.g., over, in, on) one or more UL sub-bands, of the one or more sub-bands, and / or receive signals via (e.g., over, in, on) one or more DL sub-bands of the one or more sub-bands. The base station may transmit signals via (e.g., over, in, on) one or more DL sub-bands, of the one or more sub-bands, and receive signals via (e.g., over, in, on) one or more UL subbands of the one or more sub-bands.Docket No.: 25-1055PCT

[0288] In the example of FIG. 18A, symbol 1808 may be an SBFD symbol. Symbol 1810 may be an SBFD symbol. Symbol 1808 may comprise (e.g., be associated with, configured with, have, and / or the like) a sub-band 1814. Symbol 1808 may comprise a sub-band 1816. Symbol 1808 may comprise a sub-band 1818. Sub-band 1814 and sub-band 1818 may be DL sub-bands. Sub-band 1816 may be a UL sub-band. The one or more sub-bands may comprise subband 1814, sub-band 1816, and / or sub-band 1818.

[0289] A DL sub-band may comprise resource blocks (RBs) via (e.g., over, in, on) which a wireless device may receive DL signal(s). A DL sub-band may comprise RBs via (e.g., over, in, on) which a base station may transmit DL signal(s). A wireless device may not transmit UL signal(s) via (e.g., over, in, on) a DL sub-band of an SBFD symbol. A base station may not receive UL signal(s) via (e.g., over, in, on) a DL sub-band of an SBFD symbol. The RBs comprised in a DL sub-band may be referred to as DL usable RBs or physical RBs (PRBs). DL usable PRBs may be an intersection of DL BWP(s) and DL sub-band(s).

[0290] A UL sub-band may comprise RBs via (e.g., over, in, on) which a wireless device may transmit UL signal(s). A UL sub-band may comprise RBs via (e.g., over, in, on) which a base station may receive UL signal(s). A wireless device may not receive DL signal(s) via (e.g., over, in, on) a UL sub-band of an SBFD symbol. A base station may not transmit DL signal(s) via (e.g., over, in, on) a UL sub-band of an SBFD symbol The RBs comprised in a UL sub-band may be referred to as UL usable RBs or PRBs. UL usable PRBs may be an intersection of UL BWP(s) and UL subbands.

[0291] A base station may transmit DL signals via (e.g., over, in, on) sub-band 1814 and / or sub-band 1818 of symbol 1808. A base station may receive UL signals via (e.g., over, in, on) sub-band 1816 of symbol 1808.

[0292] A wireless device may receive DL signals via (e.g., over, in, on) sub-band 1814 and / or sub-band 1818 of symbol 1808. A wireless device may transmit UL signals via (e.g., over, in, on) sub-band 1816 of symbol 1808 or UL sub-band of symbol 1810.

[0293] In an example, wireless device 1700 may use SBFD symbols (e.g., symbol 1808 and symbol 1810) for either UL transmission or DL reception. This may be because SBFD symbols are used for both UL and DL by the base station but may be used either for DL or UL by a wireless device (e.g., base station may be SBFD enabled but the wireless device may operate in a half-duplex or TDD manner or mode).

[0294] Configuration parameters 1708 may indicate link direction for at least one SBFD symbol, of one or more SBFD symbols, configured or indicated by configuration parameters 1708. For example, configuration parameters 1708 may comprise a field or parameter indicating link direction (e.g., UL or DL) for the at least one SBFD symbol of the one or more SBFD symbols. In the example of FIG. 18A, the one or more SBFD symbols may comprise symbol 1808 and symbol 1810.

[0295] In another example, wireless device 1700 may determine link direction of an SBFD symbol based on whether a UL transmission ora DL reception is scheduled on the SBFD symbol. For example, configuration parameters 1708 (or another signal, e.g., MAC CE or DCI) may indicate or schedule a UL transmission (e.g., PUSCH, PUCCH, SRS,Docket No.: 25-1055PCTand / or the like) via symbol 1808 (e.g., via sub-band 1816). Wireless device 1700 may determine link direction of symbol 1808 as UL based on configuration parameters 1708 (or another signal, e.g., MAC CE or DCI) indicating or scheduling a UL transmission via symbol 1808. In another example, configuration parameters 1708 (or another signal, e.g., MAC CE or DCI) may indicate or schedule a DL reception (e.g., CSI-RS, SSB, PDCCH, PDSCH, and / or the like) via symbol 1808 (e.g., via sub-band 1814 and / or sub-band 1818). Wireless device 1700 may determine link direction of symbol 1808 as DL based on configuration parameters 1708 (or another signal, e.g., MAC CE or DCI) indicating or scheduling a DL reception via symbol 1808.

[0296] In an example, configuration parameters 1708 may indicate symbol 1808 and / or symbol 1810 as SBFD symbols as follows: configuration parameters 1708 may indicate symbol 1808 and / or symbol 1810 as DL symbols (or UL symbols or flexible symbols). Configuration parameters 1708 may comprise one or more configuration parameters for SBFD mode (e.g., SBFD-configuration, SBFD-DL-UL-configuration, and / or the like). The one or more configuration parameters for SBFD mode may indicate a sub-set of symbols configured by configuration parameters 1708 (as DL, UL, or flexible symbols) as SBFD symbols. For example, the one or more configuration parameters for SBFD mode may indicate symbol 1808 and / or symbol 1810 as SBFD symbols.

[0297] For example, configuration parameters 1708 may indicate symbol 1804, symbol 1806, symbol 1808, symbol 1810, and symbol 1812 as a DL symbol, a DL symbol, a DL symbol, a DL symbol, and a UL symbol, respectively. The one or more configuration parameters for SBFD mode may indicate symbol 1808 and symbol 1810 as SBFD symbols (e.g., based on indicating the one or more sub-bands for symbol 1808 and symbol 1810 or based on indicating at least one DL sub-band and / or at least one UL sub-band for symbol 1808 and symbol 1810). Symbol 1804 and symbol 1806 may be / remain DL symbols. Symbol 1812 may be / remain a UL symbol (e.g., after wireless device 1700 applies the one or more configuration parameters for SBFD mode). In the example of FIG. 18A, the five symbols may be or comprise a DL-UL pattern (e.g., TDD DL-UL pattern). For example, periodicity of the DL-UL pattern may be five symbols (e.g., 5 ms if one symbol spans 1 ms).

[0298] In some embodiments, configuration parameters 1708 may indicate a first symbol as a DL symbol, a second symbol as a flexible symbol, and a third symbol as a UL symbol. The one or more configuration parameters for SBFD may indicate the first symbol as an SBFD symbol and the second symbol as an SBFD symbol. In some embodiments, the first symbol and the second symbol may be considered as (or referred to as) SBFD symbols.

[0299] In some embodiments, the first symbol may be considered as (or referred to as) an SBFD symbol and the second symbol may be considered as (or referred to as or treated as) a non-SBFD symbol (despite the one or more configuration parameters for SBFD mode indicating the second symbol as SBFD symbol).

[0300] In some embodiments, a symbol that is configured or indicated (by configuration parameters 1708) as a DL symbol may be considered (or referred to) as an SBFD symbol based on the one or more configuration parameters for SBFD mode indicating the symbol to be an SBFD symbol.Docket No.: 25-1055PCT

[0301] In some embodiments, a symbol that is configured or indicated (by configuration parameters 1708) as a flexible symbol may be considered (or referred to) as an SBFD symbol based on the one or more configuration parameters for SBFD mode indicating the symbol to be an SBFD symbol.

[0302] In some embodiments, a symbol that is configured or indicated (by configuration parameters 1708) as a flexible symbol may be considered (or referred to or treated) as a non-SBFD symbol based on (or despite) the one or more configuration parameters for SBFD mode indicating the symbol to be an SBFD symbol.

[0303] In some embodiments, an SBFD symbol may be a symbol that is configured or indicated (e.g. , by configuration parameters 1708) as a downlink symbol and / or indicated or configured by the one or more configuration parameters for SBFD mode as an SBFD symbol.

[0304] In some embodiments, an SBFD symbol may be a symbol that is configured or indicated (e.g., by configuration parameters 1708) as a flexible symbol and / or indicated or configured by the one or more configuration parameters for SBFD mode as an SBFD symbol.

[0305] In some embodiments, a non-SBFD symbol may be a symbol that is configured or indicated (e.g., by configuration parameters 1708) as a flexible symbol and / or indicated or configured by the one or more configuration parameters for SBFD mode as an SBFD symbol.

[0306] The one or more sub-bands may comprise sub-band 1814, sub-band 1816, and sub-band 1818. Each of the one or more sub-bands may comprise one or more resource blocks (RBs). Each of the one or more RBs may be in (e.g., within, part of, associated with) the same carrier or BWP. For example, sub-band 1814, sub-band 1816, and subband 1818 may be in (e.g., within, part of, associated with) the same carrier or BWP.

[0307] Symbol 1808 may be for (e.g., configured with, associated with, of) DL operation and UL operation via (e.g., in, on, within, over) the same carrier / BWP. Symbol 1810 may be for (e.g., configured with, associated with, of) DL operation and UL operation via (e.g., in, on, within) the same carrier / BWP. For example, base station 1720 may transmit a first DL signal (e.g., to a first wireless device) via (e.g., in, on, within, over) symbol 1808 and receive a first UL signal (e.g, from a second wireless device) via (e.g., in, on, within) symbol 1808 via (e.g., in, on, within) in the same carrier or BWP (e.g., the first carrier / BWP). Base station 1720 may transmit a second DL signal (e.g., to a first wireless device) via (e.g., in, on, within) symbol 1810 and receive a second UL signal (e.g., from a second wireless device) via (e.g., in, on, within) symbol 1810 via (e.g., in, on, within) in the same carrier or BWP (e.g., the first carrier or BWP). For example, base station 1720 may transmit the second DL signal via (e.g , in, on, within, over) a sub-band 1814 within symbol 1810 and via (e.g., in, on, within, over) the first carrier / BWP; and receive the second UL signal via (e.g., in, on, within, over) a sub-band 1816 within symbol 1810 and via (e.g., in, on, within, over) the first carrier / BWP.

[0308] Sub-band 1814 may comprise one or more first RBs. Sub-band 1816 may comprise one or more second RBs.

[0309] Symbol 1808 and symbol 1810 maybe, for example, referred to as advanced duplexed or SBFD symbols. Sub-band 1814 may, for example, be referred to as a DL sub-band (e.g., within or of the first carrier / BWP and symbolDocket No.: 25-1055PCT1808). Sub-band 1816 may, for example, be referred to as a UL sub-band (e.g., within or of the first carrier / BWP and the symbol 1808).

[0310] A DL sub-band may be a sub-band within (or of, for, associated with, or configured for) an SBFD symbol that is for (e.g., of, associated with, configured with, assigned with) DL operation. For example, the wireless device may receive DL signals via (e.g., on, in, within, over, using) DL sub-bands.

[0311] A UL sub-band may be a sub-band within (or of, for, associated with, or configured for) an SBFD symbol that is for (e.g., of, associated with, configured with, assigned with) for UL operation. For example, the wireless device may transmit UL signals via (e.g., on, in, within, over, using) UL sub-bands.

[0312] SBFD symbols may not be the same as flexible or flexible TDD symbols. For example, symbol 1808 and / or symbol 1810 may not be the same as (e.g., maybe different from) flexible or flexible TDD symbols. Flexible (TDD) symbols are not configured or assigned (both) DL and UL for the same period of time / interval . Instead, flexible (TDD) symbols may be symbols that may be configured or assigned as DL symbols for some time period / i nterval and UL symbols for / at other time periods / intervals. Different from flexible TDD symbols, SBFD symbols may be for (e.g., of, associated with, configured with, assigned with) (both) UL and DL operation in / on / via a same carrier / BWP and at the same time interval / period. As an example, FIG. 18A illustrates that symbol 1808 is an SBFD symbol, which comprises a sub-band 1814 for (e.g., of, associated with, configured with, assigned with) for DL operation and a sub-band 1816 for (e.g., of, associated with, configured with, assigned with) UL operation. Base station 1720 may transmit and receive DL and UL signal(s), respectively, via a same SBFD symbol (e.g., symbol 1808). Base station 1720 may either transmit or receive DL or UL signal(s), respectively, (but not both) via a same flexible (TDD) symbol.

[0313] SBFD symbols may comprise one or more sub-bands. For example, SBFD symbols may comprise at least one DL sub-band and / or at least one UL sub-band (e.g., within the BWP / carrier). Flexible symbols may not comprise one or more sub-bands. For example, flexible symbols may not comprise DL sub-band and / or UL sub-band. For example, all of the BWP / carrier for (e.g., of, associated with, configured with, assigned with) the flexible symbol may be used only for either UL operation or DL operation.

[0314] Symbol 1804, symbol 1806, symbol 1808, symbol 1810, and symbol 1812 may for (e.g., of, associated with, configured with, assigned with) the same carrier / BWP (e.g., regardless of whether the symbols are for (e.g., of, associated with, configured with, assigned with) DL operation, UL operation, and / or SBFD operation (e.g., both UL and DL operations)).

[0315] In some embodiments, “slot” and “symbol” may be used interchangeably. Actions, methods, operations, aspects, and / or features corresponding to a “symbol” described in the present disclosure may be applicable (e.g., in a similar manner or extended) to a “slot” (or vice versa).

[0316] In some embodiments, a wireless device transmitting a signal via (e.g., on, in, within, over, using) an SBFD symbol (e.g., symbol 1808) may comprise the wireless device transmitting the signal via (e.g., on, in, within, over, using) an UL sub-band (e.g., sub-band 1816) of the SBFD symbol (e.g., symbol 1808).Docket No.: 25-1055PCT

[0317] In some embodiments, a wireless device receiving a signal via (e.g., on, in, within, over, using) an SBFD symbol (e.g., symbol 1808) may comprise the wireless device receiving the signal via (e.g., on, in, within, over, using) a DL sub-band (e.g., sub-band 1814) of the SBFD symbol (e.g., symbol 1808).

[0318] In some embodiments, “SBFD’’ may refer to advanced duplex, full duplex, partial full duplex, enhanced duplex, and / or the like.

[0319] In some embodiments, “flexible symbols” and “flexible TDD symbols” maybe used interchangeably.

[0320] In some embodiments, SBFD may be different from full duplexing. Full duplexing may comprise fully or partially overlapping ULand DL sub-bands. For example, sub-band 1814 and sub-band 1816 maybe partially or fully overlapping (in frequency) in full duplexing. There maybe no sub-bands in full duplexing. For example, the entire BWP or band may be for both UL transmission and DL reception at all times. SBFD may face inter-band self-interference. On the other hand, full duplexing may face intra-band self-interference. Full-duplexing may be referred to as in-band fullduplexing.

[0321] In some embodiments, in SBFD, DL and UL sub-bands may not be overlapping. For example, the sub-band 1814 and the sub-band 1816 may not overlap (e.g., partially overlap and / or fully overlap).

[0322] In some embodiments, DL and UL sub-bands may overlap. For example, the sub-band 1814 and the subband 1816 may overlap (e.g., partially overlap and / or fully overlap).

[0323] In some embodiments, SBFD mode may be referred to as SBFD scheme, SBFD method, SBFD technique, SBFD operation, SBFD symbols, and / or any other description of communication via SBFD symbols.

[0324] SBFD operation may be, for example, within a (TDD) carrier. An SBFD symbol may comprise an RB or a set of (consecutive) RBs for a same transmission / link direction (e.g., UL or DL). An SBFD symbol may be a symbol with sub-bands that a base station (e.g., gNB) uses for SBFD operation.

[0325] In some embodiments, “carrier” may refer to “center frequency.”

[0326] SBFD scheme may be within a single configured DL and / or UL BWP pair with aligned center frequencies. There may be a maximum number of UL sub-bands for SBFD operation in an SBFD symbol within a TDD carrier. An UL sub-band may be located at one side of the carrier or may be located at the middle part of the TDD carrier.

[0327] SBFD operation may be on / for unpaired spectrum (e.g., similar to TDD operation).

[0328] In an example, for unpaired spectrum (e.g., TDD and / or SBFD operation), if a wireless device is not provided (eg., receives message(s) 1706 that do not comprise) configuration parameters 1708 or the one or more configuration parameters for SBFD mode, a PRACH occasion in a PRACH slot may be valid if the PRACH occasion does not precede a SS / PBCH block in the PRACH slot and starts at least Wgap symbols after a last SS / PBCH block reception symbol, and, if channelAccessMode = "semiStatic" is provided, does not overlap with a set of consecutive symbols before the start of a next channel occupancy time where the wireless device does not transmit. Candidate SS / PBCH block index of the SS / PBCH block corresponds to the SS / PBCH block index indicated by the one or more configuration parameters. In some embodiments, PRACH occasion may be the same as or refer to valid PRACH occasion.Docket No.: 25-1055PCT

[0329] In an example, unpaired spectrum (e.g. , TDD and / or SBFD operation), if a wireless device is provided (e.g., receives message(s) 1706 comprising) configuration parameters 1708 (e.g., tdd-UL-DL-ConfigurationCommon) and / or the one or more configuration parameters for SBFD mode, a PRACH occasion in a PRACH slot is valid if the PRACH occasion is within UL symbols / slots (e.g., symbol 1812); if the PRACH occasion is within UL sub-bands of / in / within SBFD symbols / slots (e.g., sub-band 1816 in symbol 1808 or the UL sub-bands in symbol 1810); and / or if the PRACH occasion does not precede a SS / PBCH block in a PRACH slot and starts at least / Vgap symbols after a last DL / SBFD symbol and at least / Vgap symbols after a last SS / PBCH block symbol.

[0330] / Vgap may indicate a number of symbols / slots based on subcarrier spacing of RA preamble. For example, for subcarrier spacing of 1.25 kHz or 5 kHz, 15 kHz or 30 kHz or 60 kHz or 120 kHz, 480 kHz, and 960 kHz, / Vgap maybe 0, 2, 8, 16, respectively. / Vgap may be 0 for preamble format B4.

[0331] In some embodiments, UL sub-bands and / or DL sub-bands (within an SBFD symbol) may be referred to as SBFD sub-bands. For example, sub-band 1814, sub-band 1816, and / or sub-band 1818 may be referred to as SBFD sub-bands.

[0332] Message(s) 1710 may comprise one or more DL messages. Message(s) 1710 may comprise one or more UL messages.

[0333] In the example of FIG. 18A, sub-band 1814 may comprise reception resources. The reception resources may occupy sub-band 1814. Sub-band 1816 may comprise transmission resources. The transmission resources may occupy sub-band 1816 that may be different from sub-band 1814. In the example of FIG. 18A, the reception resources are in a higher frequency sub-band (e.g., sub-band 1814) than the transmission resources. However, it should be noted that the transmission resources may be in a lower frequency sub-band with respect to the reception resources. For example, sub-band 1816 may be a higher sub-band than a sub-band 1818. Sub-band 1816 may comprise transmission resources.

[0334] In some embodiments, reception resources or transmission resources may occupy more than one sub-band. For example, in FIG. 18A, reception resources occupy sub-band 1814 and sub-band 1818. For example, sub-band 1814 and sub-band 1818 comprise reception resources.

[0335] In some embodiments, transmission resources may be separated from reception resources by a guard band. The guard band may be frequency resources, or a gap in frequency resources, provided between the transmission resources and the reception resources. Separating the transmission (frequency) resources and the reception (frequency) resources with a guard band may help to reduce self-interference. Transmission resources and reception resources that are immediately adjacent to each other (e.g., symbol 1808 comprising sub-band 1814 and sub-band 1816 that are adjacent) may be considered as having a guard band width of zero. As an output signal from a wireless device may extend outside the transmission resources, the guard band may reduce interference experienced by the wireless device.Docket No.: 25-1055PCT

[0336] In some embodiments, SBFD operation may be for a base station. For example, transmission resources may correspond to UL resources and reception resources may correspond to DL resources.

[0337] SBFD may be referred to as sub-band FDD and / or "flexible duplex."

[0338] SBFD allows for simultaneous transmission and reception of DL and UL on a sub-band basis. A full duplex or SBFD base station may conduct simultaneous transmission and reception on the same symbol (e.g., symbol 1808). SBFD may increase UL duty cycle, which leads to latency reduction (e.g., it is possible to transmit UL signals in DL-only symbols, which may enable latency savings) and UL coverage improvement. It may be possible to receive DL signals in UL-only symbols. Additionally, SBFD may enhance system capacity, resource utilization and spectrum efficiency. SBFD may enable flexible and dynamic UL / DL resource adaption or adaptation according to UL / DL traffic in a robust manner.

[0339] In some embodiments, the wireless device (e.g., wireless device 1700) may be / referred to as an SBFD-aware wireless device (or an SBFD-capable wireless device). An SBFD-aware wireless device may refer to a wireless device that supports receiving (or operating / functioning with) information (e.g., configuration parameters 1708 and / or the one or more configuration parameters for SBFD mode) about an SBFD mode of a device with which it is communicating, e.g. such as a network node / gNB / base station. By supporting receiving (or operating / functioning with) such information, the wireless device may be aware, e.g., may receive signaling indicating times when the base station will operate in SBFD mode, when to schedule UL transmission outside a UL sub-band, or when to schedule DL reception within a UL sub-band (e.g., receive the one or more configuration parameters of / for SBFD mode).

[0340] In some embodiments, the SBFD-aware wireless device, configured with a UL sub-band (e.g., sub-band 1816) in an SBFD symbol (e.g., symbol 1808), does not expect to be scheduled with UL transmission outside the UL subband (e.g., sub-band 1816) and does not expect to be scheduled with DL reception within the UL sub-band in an SBFD symbol. In some embodiments, methods and apparatus may be related to scenarios where an SBFD-aware wireless device, configured with a UL sub-band in an SBFD slot or symbol, does not expect to be scheduled with UL transmission outside the UL sub-band and maybe scheduled with DL reception within the UL sub-band in an SBFD slot or symbol. In other embodiments, methods and apparatus may be related to scenarios where an SBFD-aware wireless device, configured with a UL sub-band in an SBFD slot or symbol, does not expect to be scheduled with DL reception within a UL sub-band and may be scheduled with UL transmission outside a UL sub-band in the SBFD slot or symbol. In some embodiments, a base station may indicate to the wireless device, e.g., via a DCI, that the wireless device is scheduled for DL reception in the UL sub-band or scheduled for UL transmission outside of the UL sub-band (e.g., in a DL sub-band). The dynamic scheduling may allow for more flexibility and resource utilization.

[0341] In an example, wireless device 1700 may be an SBFD-aware wireless device (or the wireless device may be SBFD-aware) based on transmitting a capability message to base station 1720, wherein the capability message indicates that wireless device 1700 is capable of receiving / supporting SBFD-related / specific parameters (e.g., SBFD-related configurations, configuration parameters, the one or more configuration parameters for SBFD mode, and / or the like).Docket No.: 25-1055PCT

[0342] An SBFD symbol may be a symbol where a base station (and / or a wireless device) may perform both DL and UL operations (e.g., transmit and receive signals). An SBFD symbol may be a symbol that is associated with / for / of / configured for SBFD mode. An SBFD symbol may be a symbol which is configured with / associated with / indicated with one or more UL sub-bands (e.g., sub-band 1816) and / or one or more DL sub-bands (e.g., sub-band 1814, sub-band 1818). Symbol 1808 and symbol 1810 are examples of SBFD symbols.

[0343] A non-SBFD symbol may be a symbol where a base station (and / or a wireless device) may perform DL-only or UL-only operations (e.g., transmit but not receive, or receive but not transmit). A non-SBFD symbol may be a symbol that is associated with / for / of / configured for non-SBFD mode. Symbol 1804, symbol 1806, and symbol 1812 are examples of non-SBFD symbols. A flexible (TDD) symbol is an example of a non-SBFD symbol. DL symbol, UL symbol, and / or flexible TDD symbol are examples of non-SBFD symbols.

[0344] A non-SBFD symbol / mode may be (or comprise) a symbol / mode that is not indicated (e.g., by message(s) 1706 and / or configuration parameters 1708) as an SBFD symbol / mode. Duplexing mode 1702 (e.g., TDD) and duplexing mode 1704 (e.g., FDD) are examples of non-SBFD modes. Flexible symbol is an example of a non-SBFD symbol.

[0345] FIG. 18B illustrates an example as per an aspect of an embodiment of the present disclosure. The example of FIG. 18B maybe used together with or independently from any of the previous examples (e.g., in FIGS. 1A-18A).

[0346] The example of FIG. 18B shows three slots, wherein each slot comprises four symbols. The three slots are numbered slot number 0, slot number 1, and slot number 2, respectively, in FIG. 18B. Each of the three slots comprise four symbols that are numbered symbol number 0, symbol number 1 , symbol number 2, and symbol number 3, respectively.

[0347] A slot may comprise SBFD symbols and / or non-SBFD symbols. For example, in FIG. 18B, slot number 0 comprises three non-SBFD symbols (symbol number 0, symbol number 1, and symbol number 2) and one SBFD symbol (symbol number 3). Slot number 1 comprises three SBFD symbols (symbol number 0, symbol number 1 , and symbol number 2). Slot number 2 comprises four non-SBFD symbols and no SBFD symbols.

[0348] In an example, the one or more configuration parameters for SBFD mode may indicate a starting slot, a starting symbol, an ending slot, and / or an ending symbol for SBFD mode or operation (e.g., for SBFD symbols). In the example of FIG. 18B, the one or more configuration parameters for SBFD mode may indicate the starting slot as slot number 0, the starting symbol as symbol number 3 (e.g., of or within slot number 0), the ending slot as slot number 1 , and the ending symbol as symbol number 2 (e.g., of or within slot number 1) for indicating SBFD symbols. For example, the one or more configuration parameters may indicate SBFD symbols based on or by indicating the starting slot, the starting symbol, the ending slot, and / or the ending symbol for SBFD mode or operation.

[0349] In an example, a symbol configured as SBFD symbol via cell-specific configuration (e.g., by the one or more configuration parameters for SBFD mode) may not be reverted to a non-SBFD symbol via a wireless device-specific configuration or group-common signaling.Docket No.: 25-1055PCT

[0350] In an example, a symbol not configured as SBFD symbol via cell-specific configuration (e.g. , by the one or more configuration parameters for SBFD mode) may not be reverted to an SBFD symbol via a wireless device-specific configuration or group-common signaling.

[0351] Cell-specific frequency locations of SBFD subbands may be separately configured (e.g., indicated by the one or more configuration parameters for SBFD mode) for each SCS configuration in a list of SCS specific carrier list (e.g., SCS-SpecificCarrierLisf). For each SCS configuration, a reference starting PRB may be a PRB determined by the SCS configuration and offsetToCarrier corresponding to the SCS (e.g., in the SCS configuration).

[0352] For UL transmissions and DL receptions across SBFD symbols and non-SBFD symbols in different slots (e.g., each transmission / reception within a slot has either all SBFD or all non-SBFD symbols) for an SBFD-aware wireless device, the SBFD-aware wireless device may be provided (e.g., indicated via message(s) 1706, configuration parameters 1708, and / or the one or more configuration parameters for SBFD mode) with one or more of the configurations: Configuration 1 : Transmissions / receptions are restricted to SBFD symbols only or non-SBFD symbols only; and / or Configuration 2: Transmissions / receptions may be in SBFD symbols and non-SBFD symbols.

[0353] For cell-specific indication of SBFD subband frequency location (e.g., via, in, or by the one or more configuration parameters for SBFD mode), frequency locations of UL subband and DL subband(s) may be explicitly configured or indicated. Guardband(s) if any may be implicitly derived by wireless device 1700 as RBs which are not within UL subband or DL subband(s).

[0354] Frequency configurations for SBFD symbols and non-SBFD symbols in a same PUCCH-Resource may be separately indicated by configuration parameters 1708 and / or the one or more configuration parameters for SBFD mode.

[0355] For a physical channel or signal (e.g., PRACH, PUSCH, PUCCH, PDSCH, PDCCH, and / or any other channel or signal) occasion mapped to SBFD and non-SBFD symbols within a slot, the wireless device may not transmit or receive the physical channel / signal within the slot.

[0356] The wireless device may transmit PRACH transmission in a valid RO across SBFD symbols and non-SBFD symbols. The wireless device may transmit PUSCH repetition (e.g., type B PUSCH repetition) across SBFD symbols and non-SBFD symbols (e.g., within a slot or across slots). In an example, a nominal repetition maybe segmented into actual repetitions around boundary of SBFD symbols and non-SBFD symbols. In another example, a nominal repetition may be segmented into actual repetitions. An actual repetition mapped to both SBFD and non-SBFD symbols may be dropped by the wireless device.

[0357] FIG. 19 shows an example as per an aspect of an embodiment of the present disclosure. The example of FIG.19 may be used together with or independently from any of the previous examples (e.g., in FIGS. 1 A-18B).

[0358] FIG. 19 illustrates an example of a wireless device 1900 and / or a wireless device 1920 communicating with a base station 1940 in a subband full-duplex (SBFD) system (e.g., via one or more SBFD symbols like symbol 1808 and / or symbol 1810). The SBFD system may be referred to as an SBFD operation or a cell in SBFD operation.Docket No.: 25-1055PCT

[0359] Wireless device 1900 and / or wireless device 1920 may be the same as wireless device 1700

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

[0361] Generally, in TDD mode, communications are performed in a single link direction (e.g., uplink or downlink) within a given time interval (e.g., as shown in FIG. 17B for duplexing mode 1702). For example, in TDD, wireless device 1900 and wireless device 1920 may both be able to transmit (e.g., be scheduled to transmit) uplink transmissions to base station 1940 in a given time interval, such as a slot (e.g., an uplink slot). The same principle applies to the downlink. A TDD mode may be referred to as a half-duplex operation (in which transmissions or receptions, and not both, occur during a given time interval, such as a slot). On the other hand, in SBFD operation, different link directions may be applied to the same time interval. For example, in a given time interval, such as a symbol or slot, wireless device 1900 may transmit an uplink transmission to base station 1940 while (in the same given time interval, such as the slot) wireless device 1920 may receive a downlink transmission from base station 1940. For example, wireless device 1900 may transmit an uplink transmission in sub-band 1816 of symbol 1808 while (in the same given time interval, such as the symbol) wireless device 1920 may receive downlink transmission from base station 1940 in subband 1814 of symbol 1808. In SBFD, wireless device 1900 and wireless device 1920 may communicate in half-duplex operation (e.g., non-simultaneous transmission and reception) and base station 1940 may operate in a full-duplex operation (e.g., simultaneous transmission and reception in non-overlapping subbands or frequency resources). SBFD operation may be referred to as non-overlapping full-duplex operation or non-overlapping SBFD operation.

[0362] As illustrated in FIG. 19, wireless device 1900 and wireless device 1920 may receive one or more RRC messages 1902. One or more RRC messages 1902 maybe (or comprise), e.g., one or more one or more SIBs (e.g., SIB1) of the cell of base station 1940 and / or one or more RRC reconfiguration messages (e.g., RRCReconfiguration).

[0363] One or more RRC messages 1902 comprise a TDD configuration of a cell of base station 1940. The TDD configuration may comprise, or indicate, one or more parameters for TDD operation on the cell. For example, the TDD configuration may indicate a pattern of time intervals in a cell of base station 1940. The pattern may be the same as the DL-UL pattern as described above in connection with FIGS. 17A, 17B, 17C, 18A, and / or 18B. As an example, the time intervals may be slots or symbols. The pattern may be referred to as a TDD pattern. The TDD configuration may indicate a plurality of patterns (e.g., a first pattern and a second pattern).

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

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

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

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

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

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

[0370] In SBFD, one or more uplink sub-bands (e.g., sub-band 1816) and one or more downlink sub-bands (e.g., sub-band 1818, sub-band 1814) are configured in (or within) a symbol (e.g., the same symbol), e.g., symbol 1808. By being configured in a symbol, the one or more uplink sub-bands and the one or more downlink sub-bands overlap in the time duration of the symbol (i.e., overlap in time). The one or more uplink sub-bands and the one or more downlink subbands may not overlap in frequency in (the time duration of) the symbol. For example, an uplink sub-band may comprise one or more uplink frequency resources (e.g., contiguous uplink frequency resources), such as resource blocks (RBs) (e.g., or physical resource blocks (PRBs)) . A downlink sub-band may comprise one or more downlink frequency resources (e.g., contiguous downlink reference resources), such as RBs (e.g., or PRBs). The RBs for the one or more uplink sub-bands and the RBs for the one or more downlink sub-bands may not be the same within a particular symbol.

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

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

[0373] In some embodiments, a flexible symbol may refer to a flexible symbol that is not configured (e.g., indicated, for example, by one or more RRC messages 1902) as or to be an SBFD symbol.

[0374] As an example, FIG. 19 illustrates that wireless device 1900 and wireless device 1920 (both) transmit uplink transmission 1904 in a non-SBFD symbol (e.g., a non-SBFD symbol within a slot comprising a non-SBFD symbol ora non-SBFD slot). The non-SBFD symbol may be an uplink symbol or a flexible symbol (e.g., a flexible symbol scheduled with uplink transmission 1904). In this example, the non-SBFD symbol is an uplink symbol, which is configured with uplink RBs (and no downlink sub-bands or downlink RBs). From the perspective of base station 1940, the link direction is the same for (both) wireless device 1900 and wireless device 1920 during the non-SBFD symbol. It should be noted that other factors may be used to prevent interference during the non-SBFD symbols (e.g., different spatial parameters (e.g., uplink transmission filters or uplink beams) and / or different coding sequences being applied).

[0375] On the other hand, FIG. 19 illustrates that wireless device 1920 transmits an uplink transmission 1906 in an SBFD symbol (e.g., a SBFD symbol within a slot comprising an SBFD symbol or an SBFD slot). During the same symbol (i.e., the SBFD symbol) (or same slot (i.e., the SBFD slot)), wireless device 1900 receives a downlink transmission 1908 in the SBFD symbol (or the SBFD slot), e.g., symbol 1808. In this example, the SBFD symbol is configured with an uplink sub-band (e.g., sub-band 1816) via which uplink transmission 1904 is transmitted. In addition, the SBFD symbol is configured with one or more downlink sub-bands (e.g., sub-band 1814, sub-band 1818) via which downlink transmission 1908 is transmitted. From the perspective of base station 1940, the link direction is different (within the same symbol) for wireless device 1900 (e.g., for which the link direction is uplink) and wireless device 1920 (e.g., for which the link direction is downlink) during the SBFD symbol (or SBFD slot).

[0376] One or more RRC messages 1902 may indicate one or more parameters of an SBFD operation (e.g , the one or more SBFD configuration parameters described above) in the cell of base station 1940 (e.g., in one or more S / Bsof the cell and / or one or more RRCReconfiguration messages). For example, the one or more parameters may indicate one or more periods (durations) of SBFD within the pattern indicated by the TDD configuration. The one or more periods may be referred to as one or more SBFD periods. The one or more parameters, indicated by one or more RRC messages 1902, may comprise a starting slot index, a starting symbol index, an ending slot index, and / or an ending symbol index. The starting slot index may represent a slot at the start of a period for SBFD (e.g., within a periodDocket No.: 25-1055PCTindicated by the periodicity of the TDD configuration, such as a starting slot or an initial slot of the period for SBFD). The starting symbol index may indicate a symbol within the slot (e.g., indicated by the starting slot index) where the period for SBFD (symbols) starts (e.g., an earliest symbol or an initial symbol of the period for SBFD). The ending slot index may represent a slot at the end of the period for SBFD (e.g., within the period indicated by the periodicity of the TDD configuration, such as an ending slot or a last slot of the period for SBFD). The ending symbol index may indicate a symbol within the slot where the period for SBFD (symbols) ends (e.g., a last symbol or an ending symbol of the period for SBFD).

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

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

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

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

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

[0382] There may be at least two configurations used for uplink transmissions or downlink receptions performed across SBFD symbols and non-SBFD symbols (e.g., in different symbols or slots). In a first configuration, the transmissions or receptions are not performed across both SBFD symbols and non-SBFD symbols. For example, the transmissions or receptions may be restricted to SBFD symbols (eg., restricted to SBFD symbols only) or non-SBFD symbols (e.g., restricted to non-SBFD symbols only). The symbol type used in the first configuration may be referred to as an allowed symbol type. The allowed symbol type may be referred to as a valid symbol type. The allowed symbol type for the first configuration may be SBFD symbols or non-SBFD symbols (and not both SBFD symbols and non-SBFD symbols). In a second configuration, the transmissions or receptions may be (e.g., performed) in (both) SBFD symbols and non-SBFD symbols (e.g., in different slots or in a same slot). In the present disclosure, the first configuration may be referred to as configuration 1 and the second configuration may be referred to as configuration 2.

[0383] Configuration 2 may be used depending on a capability (e.g., a UE capability) of the wireless device.Configuration 2 may be used as follows. The wireless device (e.g., wireless device 1900 and / or wireless device 1920) may transmit a capability message. The wireless device may transmit the capability message via PUSCH, PUCCH, PRACH, or SRS. In a first example, the capability message may indicate that the wireless device supports configuration 2. The base station (e.g., base station 1940) may indicate (e.g., via the one or more configuration parameters) a configured grant configuration. The configured grant configuration may indicate that configuration 2 is for (e.g., of, for, associated with, corresponding to, or configured for) the configured grant configuration. In a second example, the capability message may indicate that the wireless device does not support configuration 2. The configured grant configuration may indicate that configuration 1 (and not configuration 2) is for (e.g., of, for, associated with, corresponding to, or configured for) the configured grant configuration.

[0384] Wireless device 1900 and / or wireless device 1920 may be configured with (e.g., keep or maintain) different sets of transmission parameters (e.g., different (uplink) power control parameters, different spatial relations, different MIMO configurations) for SBFD symbols and non-SBFD symbols. Different sets of transmission parameters may be used, e.g., due to uplink interference being higher in SBFD symbols than non-SBFD symbols. Base station 1940 may, for example, use a single panel (or an uplink antenna element) for uplink reception in SBFD symbols while using two panels (or two uplink antenna elements) for non-SBFD symbols (or vice versa). The lower number of uplink antenna elements at base station 1940 during SBFD symbols (or SBFD slots) may result in a lower uplink channel (e.g., PUSCHDocket No.: 25-1055PCTor PUCCH) decoding performance as compared to the non-SBFD symbols (e.g., such as uplink symbols or uplink slots).

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

[0386] As wireless devices (e.g., wireless device 1900 and / or wireless device 1920) may apply, maintain, and / or be configured with different sets of transmission parameters for SBFD symbols and non-SBFD symbols, capability signaling may be used to report whether, e.g., a particular wireless device supports configuration 2.

[0387] FIG. 19 illustrates an example of capability signaling for configuration 1 and configuration 2. In this example, wireless device 1900 supports both configuration 1 and configuration 2, and wireless device 1920 supports configuration 1 and does not support configuration 2.

[0388] As illustrated in FIG. 19, base station 1940 transmits one or more capability inquiry messages 1910 to wireless device 1900 and / or wireless device 1920 One or more capability inquiry messages 1910 may explicitly request wireless device 1900 and / or wireless device 1920 to indicate whether configuration 2 is supported (e.g., and / or configuration 1 is supported). One or more capability inquiry messages 1910 may request wireless device 1900 and / or wireless device 1920 to indicate capabilities (e.g., without explicitly requesting capability of configuration 1 and / or configuration 2).

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

[0390] Wireless device 1920 transmits a capability message 1914 to base station 1940. Capability message 1914 may be transmitted in response to receiving one or more capability inquiry messages 1910. Capability message 1914 indicates that wireless device 1920 does not support configuration 2. For example, capability message 1912 may comprise a parameter that indicates that wireless device 1920 does not support configuration 2 The parameter may indicate that wireless device 1920 supports configuration 1 (only). As an example, the parameter may indicate thatDocket No.: 25-1055PCTwireless device 1900 is not capable of performing transmissions, and / or receptions, in SBFD symbols and non-SBFD symbols (e.g., across multiple slots or in different slots). As an example, the parameter may indicate that wireless device 1900 is (only) capable of performing transmissions, and / or receptions, in SBFD symbols or non-SBFD symbols (e.g., across multiple slots or in different slots) (and not both SBFD symbols and non-SBFD symbols).

[0391] Base station 1940 may transmit one or more RRC messages 1916, such as one or more RRC reconfiguration messages, to wireless device 1900 and / or wireless device 1920. One or more RRC messages 1916 may be transmitted in response to (or after receiving) capability message 1912 and capability message 1914. In another example, one or more RRC messages 1916 may be transmitted not in response to capability message 1912 and capability message 1914 (e.g., independent from capability message 1912 and capability message 1914).

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

[0393] In an example, one or more RRC messages 1916 may not explicitly indicate which configuration to be used. For example, based on transmitting capability message 1914, wireless device 1920 may determine (e.g., assume) that uplink transmissions and / or downlink receptions in SBFD symbols and non-SBFD symbols (e.g., across a plurality of slots or in different slots) are based on configuration 1. That is, based on transmitting capability message 1912 indicating that configuration 2 is not supported, wireless device 1920 may determine that uplink transmissions and / or downlink receptions in SBFD symbols and non-SBFD symbols (across a plurality of slots or in different slots) are (to be) performed based on configuration 1.

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

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

[0396] As an example of configuration 2, FIG. 19 illustrates that wireless device 1900 (e.g., that supports configuration 2 and / or configuration 1) receives a DC11922. DC11922 schedules uplink transmissions 1924. Uplink transmissions 1924 are scheduled across SBFD symbols and non-SBFD symbols (e.g., in a plurality of slots or in different slots). In configuration 2, transmissions and / or receptions are performed across both SBFD symbols and non-SBFD symbols. As illustrated, uplink transmissions 1924 are transmitted in (both) non-SBFD symbols and SBFD symbols.

[0397] As an example of configuration 1, FIG. 19 illustrates that wireless device 1920 (e.g., that supports configuration 1 but not configuration 2) receives a DC11926. DC11926 schedules uplink transmissions 1928. Uplink transmissions 1928 are scheduled across SBFD symbols and non-SBFD symbols (e.g., in a plurality of slots or in different slots). In configuration 1 , transmissions and / or receptions are not performed across both SBFD symbols and non-SBFD symbols (e.g., are restricted to SBFD symbols only or are restricted to non-SBFD symbols only).

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

[0399] Wireless device 1900 may determine the allowed symbol type (i.e., which symbols to transmit in and / or which symbols not to transmit it) based on the symbol type of the initial occasion of uplink transmissions 1928. As illustrated in FIG. 19, the initial occasion of uplink transmissions 1928 is in a non-SBFD symbol. Based on the initial occasion of uplink transmissions 1928 being in a non-SBFD symbol, wireless device 1920 may transmit uplink transmissions 1928 in the non-SBFD symbolsand may not transmit (e.g , skips, drops, cancels, or postpones) uplink transmissions 1928 in the SBFD symbols. That is, the allowed symbol type is non-SBFD symbols based on the initial transmission of uplink transmissions 1928 being in a non-SBFD symbol.

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

[0401] In the example of FIG. 19, the initial transmission occasion is shown to be a non-SBFD symbol or slot. But the same principle described in the disclosure is also applicable for the opposite case, e.g., when the initial transmission occasion is an SBFD symbol or slot.

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

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

[0404] For dynamically scheduled PDSCH repetitions with Configuration 2, for TBS determination, if: the first repetition occasion indicated by scheduling DCI is in SBFD symbols, the number of PRBs for TBS determination may be based on assigned PRBs within DL usable PRBs; and the first repetition occasion indicated by scheduling DCI is in non-SBFD symbols, the number of PRBs for TBS determination may be based on assigned PRBs.

[0405] For a serving cell configured with SBFD subband time and frequency location (e.g., via the one or more SBFD configuration parameters), for an SBFD aware UE, SFI in DCI format 2_0 may be applicable to non-SBFD symbols but not applicable to SBFD symbols.

[0406] For type 2 CG PUSCH, SPS PDSCH, the valid symbol type for type 2 CG PUSCH may be determined based on the symbol type of the first CG PUSCH associated with activation DCI; and / or the valid symbol type for SPS PDSCH may be determined based on the symbol type of the first SPS PDSCH associated with activation DCI.Docket No.: 25-1055PCT

[0407] An association period and association pattern period of SBFD PRACH occasions (e.g., PRACH occasions that are in or overlap in time with SBFD symbols) may be determined separately from non-SBFD PRACH occasions (e.g., PRACH occasions that are in or overlap in time with non-SBFD symbols).

[0408] For a random-access procedure (e.g., contention-free random-access procedure) triggered by PDCCH order, the PDCCH order explicitly indicates (e.g., using a 1 -bit field) whether to use SBFD PRACH occasion (or randomaccess resources) or non-SBFD PRACH occasions (or random-access resources). For example, a first value (e.g., 0 or 1) of the 1 -bit field may indicate using SBFD (or non-SBFD) PRACH occasions (or random-access resources). A second value (e.g., 1 orO) of the 1-bit field may indicate using non-SBFD (or SBFD) PRACH occasions (or randomaccess resources). The wireless device may transmit a random-access preamble via the SBFD PRACH occasions or the non-SBFD PRACH occasions based on the 1-bit field. For example, the wireless device may transmit the randomaccess preamble via the SBFD PRACH occasion based on the 1-bit field in the PDCCH order being set to the first value; and / or transmit the random-access preamble via the non-SBFD PRACH occasion based on the 1-bit field in the PDCCH order being set to the second value.

[0409] If an SBFD PRACH occasion is selected (or used, e.g., transmitted via) for Msg 1 (e.g., random-access preamble) transmission, Configuration 1 may be used by the wireless device for Msg3 repetition or transmission.

[0410] In Carrier Aggregation (CA), two or more Component Carriers (CCs) are aggregated. A wireless device may simultaneously receive or transmit on one or multiple CCs depending on the wireless device’s capabilities. A wireless device with single timing advance capability for CA may simultaneously receive and / or transmit on multiple CCs corresponding to multiple serving cells sharing a same timing advance (multiple serving cells grouped in one TAG). A wireless device with multiple timing advance capability for CA may simultaneously receive and / or transmit on multiple CCs corresponding to multiple serving cells with different timing advances (multiple serving cells grouped in multiple TAGs). The base station may ensure that each TAG contains at least one serving cell. A non-CA capable wireless device may receive on a single CC and transmit on a single CC corresponding to one serving cell only (one serving cell in one TAG). In some aspects, a wireless device may refer to any of the above type of wireless device (e.g., a wireless device with single timing advance capability for CA, wireless device with multiple timing advance capability for CA, and / or a non-CA capable wireless device).

[0411] CA may be supported for both contiguous and non-contiguous CCs. When CA is deployed, frame timing and SFN may be aligned across cells that can be aggregated, or an offset in multiples of slots between the PCell / PSCell and an SCell is configured to the wireless device. The maximum number of configured CCs for a UE may be, for example, 16 for DL and 16 for UL.

[0412] In conjunction with a UL / DL carrier pair (FDD band) or a bidirectional carrier (TDD band), the wireless device may be configured with additional, Supplementary Uplink (SUL). SUL may differ from the aggregated uplink in that the wireless device may be scheduled (e.g., by the base station via or using the one or more configuration parameters) toDocket No.: 25-1055PCTtransmit either on the supplementary uplink or on the uplink of the carrier being supplemented, but, for example, not on both at the same time.

[0413] In uplink CA or SUL, a wireless device configured with uplink Tx switching may have Tx chain(s) dynamically switched from one uplink band or two uplink bands to another uplink band or two uplink bands for enabling up to 2Tx UL transmission in one uplink band or simultaneous UL transmissions in two uplink bands at a time.

[0414] If a wireless device is configured with one or more SCells, the base station may activate and / or deactivate the configured SCells. Upon configuration of an SCell, the SCell may be deactivated unless a parameter sCellState (e.g., in the one or more configuration parameters) is set to activated for the SCell.

[0415] In an example, the wireless device may receive a command (e.g., SCell Activation / Deactivation MAC CE, Enhanced SCell Activation / Deactivation MAC CE). The command may activate and / or deactivate an SCell. In an example, the command may indicate an index (e.g., identity or identifier) of the SCell that is being activated or deactivated by the command. The wireless device may activate or deactivate the SCell (e.g., identified or indicated by the command) based on (e.g., in response to, upon, or after) to receiving the command.

[0416] For each (configured) SCell, the wireless device may:1 > if an SCell is configured with sCellState (e.g., in the one or more configuration parameters) set to activated upon SCell configuration, or an SCell Activation / Deactivation MAC CE or an Enhanced SCell Activation / Deactivation MAC CE is received activating the SCell:2> if the SCell was deactivated prior to receiving this Enhanced SCell Activation / Deactivation MAC CE and a TRS is indicated for this SCell:3> indicate to lower layers (e.g., physical layer or layer-1) the information regarding the TRS.2> if the SCell was deactivated prior to receiving this SCell Activation / Deactivation MAC CE or this Enhanced SCell Activation / Deactivation MAC CE; or2> if the SCell is configured with sCellState set to activated upon SCell configuration:3> if firstActiveDownlinkBWP-ld is not set to dormant BWP:4> activate the SCell for direct SCell activation; i.e., apply normal SCell operation comprising:5> SRS transmissions on the SCell;5> CSI reporting for the SCell;5> PDCCH monitoring on the SCell;5> PDCCH monitoring for the SCell;5> PUCCH transmissions on the SCell, if configured.3> else (i.e. firstActiveDownlinkBWP-ld is set to dormant BWP):4> stop the bwp-lnactivityTimer of this Serving Cell, if running.3> activate the DL BWP and UL BWP indicated by firstActiveDownlinkBWP-ld and firstActiveUplinkBWP-ld respectively.Docket No.: 25-1055PCT2> start or restart the sCellDeactivationTimer associated with the SCell;2> if the active DL BWP is not the dormant BWP:3> (re-)initialize any suspended configured uplink grants of configured grant Type 1 associated with this SCell according to the stored configuration, if any, and to start in the symbol;3> trigger PHR.1> else if an SCell Activation / Deactivation MAC CE or an Enhanced SCell Activation / Deactivation MAC CE is received deactivating the SCell; or1 > if the sCellDeactivation Timer associated with the activated SCell expires; or1> if the SCG associated with the activated SCell is deactivated:2> deactivate the SCell;2> stop the sCellDeactivationTimer associated with the SCell;2> stop the bwp-lnactivityTimer associated with the SCell;2> deactivate any active BWP associated with the SCell;2> clear any configured downlink assignment and any configured uplink grant Type 2 associated with the SCell respectively;2> clear any PUSCH resource for semi-persistent CSI reporting associated with the SCell;2> suspend any configured uplink grant Type 1 associated with the SCell;2> flush all HARQ buffers associated with the SCell;2> cancel, if any, triggered consistent LBT failure for the SCell.1> if PDCCH on the activated SCell indicates an uplink grant or downlink assignment; or1> if PDCCH on the Serving Cell scheduling the activated SCell indicates an uplink grant or a downlink assignment for the activated SCell; or1> if a MAC PDU is transmitted in a configured uplink grant and LBT failure indication is not received from lower layers; or1> if a MAC PDU is received in a configured downlink assignment:2> restart the sCellDeactivationTimer associated with the SCell.1> if the SCell is deactivated:2> not transmit SRS on the SCell;2> not report CSI for the SCell;2> not transmit on UL-SCH on the SCell;2> not transmit on RACH on the SCell;2> not monitor the PDCCH on the SCell;2> not monitor the PDCCH for the SCell;2> not transmit PUCCH on the SCell;Docket No.: 25-1055PCT2> if the SCell is configured as a scheduled cell in MC-DCI-SelOfCells and with the search space for DCI to schedule multiple cells of the same searchSpaceld as the serving cell in which MC-DCI-SetOfCells containing the SCell is configured:3> not monitor the PDCCH for scheduling multiple cells for the set of cells in MC-DCI-SetOfCells including the SCell.When the measurement reporting for fast unknown SCell activation is configured by RRC (e.g., the one or more configuration parameters), the wireless device may:1> if SCell Activation / Deactivation MAC CE or an Enhanced SCell Activation / Deactivation MAC CE is received activating the SCell(s):2> if SCell(s) was deactivated prior to receiving this SCell Activation / Deactivation MAC CE or this Enhanced SCell Activation / Deactivation MAC CE:3> indicate to upper layers (e.g., RRC layer or layer 2 or 3) SCell(s) activation indication.

[0417] HARQ feedback for the MAC PDU containing SCell Activation / Deactivation MAC CE or Enhanced SCell Activation / Deactivation MAC CE shall not be impacted by PCell, PSCell and PUCCH SCell interruptions due to SCell activation / deactivation.

[0418] When SCell is deactivated, an ongoing Random Access procedure on the SCell, if any, may be aborted.

[0419] With reference to slots for PUCCH transmissions, when the wireless device receives in a PDSCH an activation command (e.g., the command above, the SCell Activation / Deactivation MAC CE or Enhanced SCell Activation / Deacti vation MAC CE) for a secondary cell ending in slot n, the wireless device may apply corresponding actions described above no later than a minimum requirement (e.g., indicated in the one or more configuration parameters or predefined) and no earlier than slot n+k, where k is m + 3 / y^tbframe^ + y where slot n+m is a slot indicated for PUCCH transmission with HARQ-ACK information for the PDSCH reception (e.g., comprising the command), and / VS|“tbframe' is a number of slots per subframe for the SCS configuration p of the PUCCH transmission.

[0420] With reference to slots for PUCCH transmissions, if a wireless device receives the command (e.g., wherein the command deactivates the SCell) for a secondary cell ending in slot n, the wireless device may apply the corresponding actions described above no later than the minimum requirement.

[0421] If the sCellDeactivationTimer associated with the secondary cell expires in slotn, the wireless device may apply the corresponding actions described above no later than the minimum requirement.

[0422] In some aspects, a wireless device receiving a signal (e.g., a message, command, and / or the like) may be from a base station. For example, the base station may transmit the signal to the wireless device.

[0423] In some aspects, a wireless device transmitting a signal (e.g., a message, command, and / or the like) may be to a base station. For example, the base station may receive the signal from the wireless device.

[0424] FIG. 20A shows an example as per an aspect of an embodiment of the present disclosure. The example of FIG. 20A maybe used together with or independently from any of the previous examples (e.g., in FIGS. 1A-19).Docket No.: 25-1055PCT

[0425] In the example of FIG. 20A, a wireless device 2000 receives configuration parameters 2002. In an example, wireless device 2000 may be the same as wireless device 1700, wireless device 1900, and / or any other wireless device described in any of the above examples. In an example, configuration parameters 2002 may be the same as the one or more configuration parameters. Configuration parameters 2002 may be, for example, the one or more SBFD configuration parameters.

[0426] In an example, configuration parameters 2002 may be of, for, associated with, corresponding to, or configured for a cell 2004. Cell 2004 may be, for example, the same as the cell described in connection with the example of FIG.17A, FIG. 17B, FIG. 17C, FIG. 18A, FIG. 18B, FIG. 19, and / or any other example. In an example, wireless device 2000 may receive configuration parameters 2002 via cell 2004. In another example, wireless device 2000 may receive configuration parameters 2002 via a cell that is different from cell 2004.

[0427] In an example, cell 2004 may be a special cell (SpCell). For Dual Connectivity operation the term Special Cell may refer to PCell of MCG or PSCell of SCG depending on if wireless device 2000 is associated to MCG or SCG, respectively. Otherwise, the term Special Cell refers to PCell. A Special Cell may support PUCCH transmission and contention-based Random Access, and may always be activated.

[0428] In an example, cell 2004 may be a primary cell (PCell). In an example, cell 2004 may be a primary secondary cell (PSCell).

[0429] In an example, cell 2004 may be a secondary cell. Cell 2004 may be, for example, a secondary cell configured with PUCCH (e.g., PUCCH SCell). In an example, cell 2004 maybe an unlicensed cell, e.g., operating in an unlicensed band. In an example, cell 2004 may be a licensed cell, e.g., operating in a licensed band. In an example, cell 2004 may operate in a first frequency range (FR1 ). The FR1 may, for example, comprise frequency bands below 6 GHz. In an example, cell 2004 may operate in a second frequency range (FR2). The FR2 may, for example, comprise frequency bands from 24 GHz to 52.6 GHz. In an example, cell 2004 may operate in a third frequency range (FR3). The FR3 may, for example, comprise frequency bands from 52.6 GHz to 71 GHz. The FR3 may, for example, comprise frequency bands starting from (or above) 52.6 GHz.

[0430] In an example, wireless device 2000 may perform uplink transmissions (e.g., PUSCH, PUCCH, PUCCH) via / of cell 2004 in a first time and in a first frequency. Wireless device 2000 may perform downlink receptions (e.g., PDCCH, PDSCH) via / of cell 2004 in a second time and in a second frequency. In an example, cell 2004 may operate in a time-division duplex (TDD) mode. In the TDD mode, the first frequency and the second frequency may be the same. In the TDD mode, the first time and the second time may be different. In an example, cell 2004 may operate in a frequency-division duplex (FDD) mode. In the FDD mode, the first frequency and the second frequency may be different. In the FDD mode, the first time and the second time may be the same.

[0431] In an example, wireless device 2000 may be in an RRC connected mode. In an example, wireless device 2000 may be in an RRC idle mode. In an example, wireless device 2000 may be in an RRC inactive mode.Docket No.: 25-1055PCT

[0432] In an example, cell 2004 may comprise a plurality of BWPs. The plurality of BWPs may comprise one or more uplink BWPs comprising an uplink BWP of cell 2004. The plurality of BWPs may comprise one or more downlink BWPs comprising a downlink BWP of cell 2004.

[0433] In an example, a BWP of the plurality of BWPs may be in one of an active state and an inactive state. In an example, in the active state of a downlink BWP of the one or more downlink BWPs, wireless device 2000 may monitor a downlink channel / signal (e.g., PDCCH, DCI, CSI-RS, PDSCH) on / for / via the downlink BWP. In an example, in the active state of a downlink BWP of the one or more downlink BWPs, wireless device 2000 may receive a PDSCH on / via / for the downlink BWP. In an example, in the inactive state of a downlink BWP of the one or more downlink BWPs, wireless device 2000 may not monitor a downlink channel / signal (e.g., PDCCH, DCI, CSI-RS, PDSCH) on / via / for the downlink BWP. In the inactive state of a downlink BWP of the one or more downlink BWPs, wireless device 2000 may stop monitoring (or receiving) a downlink channel / signal (e.g., PDCCH, DCI, CSI-RS, PDSCH) on / via / for the downlink BWP. In an example, in the inactive state of a downlink BWP of the one or more downlink BWPs, wireless device 2000 may not receive a PDSCH on / via / for the downlink BWP. In the inactive state of a downlink BWP of the one or more downlink BWPs, wireless device 2000 may stop receiving a PDSCH on / via / for the downlink BWP.

[0434] In an example, in the active state of an uplink BWP of the one or more uplink BWPs, wireless device 2000 may transmit an uplink signal / channel (e.g., PUCCH, preamble, PUSCH, PRACH, PUCCH, etc.) on / via the uplink BWP. In an example, in the inactive state of an uplink BWP of the one or more uplink BWPs, wireless device 2000 may not transmit an uplink signal / channel (e.g., PUCCH, preamble, PUSCH, PRACH, PUCCH, etc.) on / via the uplink BWP.

[0435] In an example, wireless device 2000 may activate the downlink BWP of the one or more downlink BWPs of cell 2004. In an example, the activating the downlink BWP may comprise setting (or switching to) the downlink BWP as an active downlink BWP of cell 2004. In an example, the activating the downlink BWP may comprise setting the downlink BWP in the active state. In an example, the activating the downlink BWP may comprise switching the downlink BWP from the inactive state to the active state.

[0436] In an example, the wireless device may activate the uplink BWP of the one or more uplink BWPs of cell 2004. In an example, the activating the uplink BWP may comprise that the wireless device sets (or switches to) the uplink BWP as an active uplink BWP of cell 2004. In an example, the activating the uplink BWP may comprise setting the uplink BWP in the active state. In an example, the activating the uplink BWP may comprise switching the uplink BWP from the inactive state to the active state.

[0437] In an example, the one or more configuration parameters may be for the (active) downlink BWP of cell 2004. In an example, at least one configuration parameter of the one or more configuration parameters may be for the downlink BWP of cell 2004.Docket No.: 25-1055PCT

[0438] In an example, the one or more configuration parameters may be for the (active) uplink BWP of cell 2004 In an example, at least one configuration parameter of the one or more configuration parameters may be for the uplink BWP of cell 2004.

[0439] The one or more configuration parameters may indicate a subcarrier spacing (or a numerology) for the downlink BWP.

[0440] The one or more configuration parameters may indicate a subcarrier spacing (or a numerology) for the uplink BWP.

[0441] A value of the subcarrier spacing (of the downlink BWP and / or the uplink BWP) may be or indicate, for example, 15 kHz (mu = 0). A value of the subcarrier spacing may be or indicate, for example, 30 kHz (mu = 1). A value of the subcarrier spacing may be or indicate, for example, 60 kHz (mu = 2). A value of the subcarrier spacing may be or indicate, for example, 120 kHz (mu = 3). A value of the subcarrier spacing may be or indicate, for example, 240 kHz (mu = 4). A value of the subcarrier spacing may be or indicate, for example, 480 kHz (mu = 5). A value of the subcarrier spacing may be or indicate, for example, 960 kHz (mu = 6). For example, 480 kHz may be valid or applicable in FR3. For example, 960 kHz may be valid or applicable in FR3. For example, 240 kHz may be valid or applicable in FR3. For example, 120 kHz may be valid or applicable in FR3.

[0442] Configuration parameters 2002 may comprise or indicate SBFD configuration 2006. SBFD configuration 2006 may comprise or indicate one or more SBFD configuration parameters. For example, SBFD configuration 2006 may comprise or indicate the one or more SBFD configuration parameters as described above (e.g., in connection with the examples of FIG. 18A, FIG. 18B, and / or FIG. 19). SBFD configuration 2006 may comprise or indicate one or more SBFD symbols (e.g., symbol 1808, symbol 1810) of cell 2004. SBFD configuration 2006 may comprise or indicate a starting slot index, a starting symbol in a starting slot identified by the starting slot index, an ending symbol index, and / or an ending symbol in an ending symbol identified by the ending slot index. SBFD configuration 2006 may indicate one or more uplink sub-bands (e.g., sub-band 1816) of, for, associated with, corresponding to, or configured for the one or more SBFD symbols SBFD configuration 2006 may indicate one or more downlink sub-bands (e.g., sub-band 1814, sub-band 1818) of, for, associated with, corresponding to, or configured for the one or more SBFD symbols.

[0443] In the example of FIG. 20A, wireless device 2000 receives configuration parameters 2012. In an example, configuration parameters 2002 may comprise or indicate configuration parameters 2012. In another example, configuration parameters 2012 may comprise or indicate configuration parameters 2002 For example, configuration parameters 2012 may comprise or indicate the one or more configuration parameters (e.g., as described above). The one or more configuration parameters may comprise or indicate configuration parameters 2012. Configuration parameters 2012 may be of, for, associated with, corresponding to, or configured for a cell 2014.

[0444] In an example, wireless device 2000 may receive configuration parameters 2012 via cell 2014. In another example, wireless device 2000 may receive configuration parameters 2012 via cell 2004. Cell 2014 may be, for example, a secondary cell (e.g., SCell). Configuration parameters 2012 may indicate cell 2014. For example,Docket No.: 25-1055PCTconfiguration parameters 2012 may comprise or indicate a field indicating an index or identity / identifier identifying cell 2014.

[0445] Configuration parameters 2012 may comprise or indicate configuration parameters of cell 2014. Configuration parameters 2012 maybe or comprise, for example, common configuration parameters. Common configuration parameters may be referred to as cell-specific configuration parameters. Common configuration parameters may, for example, not be dedicated (e.g ., UE-dedicated) configuration parameters for a single, a particular, or a specific wireless device (e.g., wireless device 2000). Common configuration parameters may be the same or applicable to a plurality of wireless devices (comprising wireless device 2000).

[0446] The following is an example structure of configuration parameters 2012. Configuration parameters 2012 may comprise SCell configuration parameters (e.g., sCellConfig). The SCell configuration parameters may comprise common serving cell configuration parameters.

[0447] In an example, configuration parameters 2012 may comprise or indicate SBFD configuration 2016. In an example, the SCell configuration parameters may comprise or indicate SBFD configuration 2016. In another example, the common serving cell configuration parameters may comprise or indicate SBFD configuration 2016. SBFD configuration 2016 may comprise or indicate one or more SBFD symbols of cell 2014. For example, SBFD configuration 2016 may comprise or indicate the one or more SBFD symbols of cell 2014 in the same or similar manner as SBFD configuration 2006 indicates the one or more SBFD symbols of cell 2004.

[0448] In an example, wireless device 2000 may use or apply SBFD configuration 2006. In another example, wireless device 2000 may use or apply SBFD configuration 2016.

[0449] In an example, SBFD configuration 2006 may comprise or indicate SBFD configuration 2016. In another example, SBFD configuration 2016 may comprise or indicate SBFD configuration 2006.

[0450] Using or applying an SBFD configuration (e.g., SBFD configuration 2006 or SBFD configuration 2016) may comprise wireless device 2000 transmitting uplink transmissions via one or more SBFD symbols indicated or identified by the SBFD configuration (e.g., via one or more uplink sub-bands, of the one or more SBFD symbols, indicated by the SBFD configuration). Using or applying an SBFD configuration (e.g., SBFD configuration 2006 or SBFD configuration 2016) may comprise wireless device 2000 receiving downlink receptions via one or more SBFD symbols indicated or identified by the SBFD configuration (e.g., via one or more downlink sub-bands, of the one or more SBFD symbols, indicated by the SBFD configuration). Using or applying an SBFD configuration (e.g., SBFD configuration 2006 or SBFD configuration 2016) may comprise determining the SBFD configuration to be activated.

[0451] Not using or not applying the SBFD configuration may comprise determining the SBFD configuration to be deactivated (or determining to be not activated). Not using or not applying the SBFD configuration may comprise wireless device 2000 transmitting uplink transmissions via one or more uplink symbols (e.g., and not the one or more SBFD symbols). Not using or not applying the SBFD configuration may comprise wireless device 2000 receiving downlink receptions via one or more downlink symbols (e.g., and not the one or more SBFD symbols).Docket No.: 25-1055PCT

[0452] FIG. 20B shows an example as per an aspect of an embodiment of the present disclosure. The example of FIG. 20B may be used together with or independently from any of the previous examples (e.g., in FIGS. 1 A-20A).

[0453] The example of FIG. 20B shows an example of an SBFD symbol 2022. SBFD symbol 2022 may be or comprise, for example, symbol 1808 and / or symbol 1810. SBFD symbol 2022 may be a symbol in a carrier aggregation scenario. SBFD symbol 2022 may comprise (e.g., be in, or overlap with) one or more uplink sub-bands and / or one or more downlink sub-bands. In the example of FIG.20B, SBFD symbol 2022 is a carrier aggregated symbol of the carriers of cell 2004 and cell 2014.

[0454] A symbol, of cell 2004, overlapping with SBFD symbol 2022, may comprise (e.g., be in, or overlap with) a single uplink sub-band (e.g., sub-band 1816) and two downlink sub-bands (e.g., sub-band 1818 and sub-band 1814). The symbol of cell 2004 may be, for example, symbol 1808 A symbol, of cell 2014, overlapping with SBFD symbol 2022, may comprise (e.g., be in, or overlap with) a single downlink sub-band and two uplink sub-bands, as shown in FIG. 20B. For example, the symbol of cell 2014 shown in FIG.20B may be symbol 1810. SBFD symbol 2022 may, for example, comprise (e.g., be in, or overlap with) three downlink sub-bands and three uplink sub-bands. This may be as a result of wireless device 2000 applying both SBFD configuration 2006 (of cell 2004) and SBFD configuration 2016 (or cell 2014).

[0455] There may be some wireless devices, such as wireless device 2000, that are not capable of such operation. For example, some wireless devices, such as wireless device 2000, may not support using (e.g., enabling or applying) SBFD configuration in two or more cells (e.g., cell 2004 and cell 2014) at the same time (e.g., simultaneously). Using existing technologies may result in wireless devices (e.g., wireless device 2000) being unsure of which SBFD configuration (e.g., SBFD configuration 2006 or SBFD configuration 2016) to use or apply. The base station and the wireless device may not be aligned on which SBFD configuration the wireless device uses or applies. This may result in: the wireless device not transmitting or receiving in certain symbols (e.g., SBFD symbols), which may lead to underutilization and / or wastage of network resources; and / or the wireless device transmitting or receiving in non-SBFD symbols by incorrectly determining the non-SBFD symbols as SBFD symbols (e.g., due to the wireless device not applying or using the SBFD configuration of the cell), which may lead to increase in self-interference and / or cross-link interference. As a result, uplink and downlink communication for one or more other wireless devices in the network may be impacted. For example, this may result in a neighboring wireless device experiencing call drops, slow file downloads, and / or lagging video streams.

[0456] According to example embodiments of the present disclosure, a wireless device receives, from a base station, first configuration parameters of a first cell, wherein the first configuration parameters indicate first symbols, of the first cell, as SBFD symbols; and second configuration parameters of a second cell, wherein the second configuration parameters indicate second symbols, of the second cell, as SBFD symbols. In response to (e.g., based on or after) the second cell being activated, the wireless device: transmits, via the second cell, uplink transmissions via at least one symbol of the second symbols; and does not transmit, via the first cell, uplink transmissions via the first symbols. TheDocket No.: 25-1055PCTwireless device deactivates the second cell, and in response to the second cell being deactivated, the wireless device transmits, via the first cell, uplink transmissions via one or more symbols of the first symbols.

[0457] Example embodiments of the present disclosure may be counter-intuitive since, for example, the first cell may be a PCell. Stopping SBFD operation on PCell and performing SBFD operation on SCell may be counter-intuitive since PCell is considered to have higher priority than SCell in uplink and / or downlink communication. Example embodiments may provide a common understanding between a base station and a wireless device on when to apply SBFD configuration and which SBFD configuration, among a plurality of SBFD configurations, to apply, under scenarios where the wireless device does not support simultaneously applying SBFD configurations of more than one cell or carrier. This may result in more efficient network resource utilization, reduce resource wastage, and / or improve (e.g., reduce) network interference.

[0458] In some aspects, overlap may indicate overlap in time and / or frequency. In some aspects, the terms "cell,” “carrier,” and “TDD carrier” may be used interchangeably (e.g., may be the same).

[0459] FIG. 21 illustrates an example as per an aspect of an embodiment of the present disclosure. The example of FIG. 21 maybe used together with or independently from any of the previous examples (e.g., in FIGS. 1A-20B).

[0460] In the example of FIG. 21, a wireless device 2100 transmits to a base station a message 2122. Wireless device 2100 may, for example, be the same as wireless device 2000, wireless device 1900, wireless device 1700, and / or any other wireless device described in the present disclosure in connection with any other embodiment.Wireless device 2100 may transmit message 2122 via a cell 2104. Wireless device 2100 may transmit message 2122 via a cell 2114. Cell 2104 maybe, for example, the same as cell 2004. Cell 2114 may be, for example, the same as cell 2014.

[0461] Cell 2104 and / or cell 2114 may be the same as the cell described in connection with FIG. 17A, FIG. 17B, and / or FIG. 17C.

[0462] The base station may be, for example, an eNodeB (eNB), a gNodeB (g N B), a 6G base station, a reconfigurable intelligent surface, a non-terrestrial network (NTN) payload, a satellite, a network controlled repeater (NCR), an integrated access and backhaul (IAB) node (e.g., IAB-DU, IAB parent, IAB child, and / or the like), a relay, a repeater, an NTN gateway, an integrated sensing and communication (ISAC) node, a second wireless device, and / or any other node that is capable of receiving wireless communication signal(s) from a wireless device (e.g., wireless device 2100). The base station may serve cell 2104 and / or cell 2114.

[0463] In an example, cell 2104 and cell 2114 maybe collocated, e.g., part of the same timing advance group. Wireless device 2100 may use a same value of timing advance for uplink transmissions via both cell 2104 and cell 2114.

[0464] In an example, cell 2104 and cell 2114 may not be collocated, e.g., may not be part of the same timing advance group. For example, a first timing advance group may comprise cell 2104 and a second timing advance group may comprise cell 2114. Wireless device 2100 may use or apply a first timing advance value (of, for, associated with,Docket No.: 25-1055PCTcorresponding to, or configured for the first timing advance group) for uplink transmission via cell 2104 Wireless device 2100 may use or apply a second timing advance value (of, for, associated with, corresponding to, or configured for the second timing advance group) for uplink transmission via cell 2114.

[0465] Message 2122 may be or comprise, for example, a capability message (e.g., UE capability message, UE capability information message). Wireless device 2100 may transmit message 2122 via a dedicated control channel. Wireless device 2100 may transmit message 2122 to indicate radio access capabilities (e.g., of one or more radio access technologies) of wireless device 2100 in response to a request by the base station. For example, wireless device 2100 may receive a UE capability enquiry message prior to transmitting message 2122. The UE capability enquiry message may indicate (e.g., request, schedule, order, ask, and / or the like) wireless device 2100 to transmit message 2122. Wireless device 2100 may transmit message 2122 via signaling radio bearer 1.

[0466] Message 2122 may indicate whether wireless device 2100 supports simultaneous SBFD operation in more than one carrier or cell. For example, message 2122 may comprise or indicate a field or parameter that indicates whether wireless device 2100 supports simultaneous SBFD operation in more than one carrier or cell. In an example, the field or parameter may be set to a first value (e.g., 0, 1, supported, enabled, and / or the like). Message 2122 may indicate that wireless device 2100 supports simultaneous SBFD operation in more than one carrier or cell based on the field or the parameter being set to the first value (or based on the field or the parameter being present (or absent) in message 2122). In another example, the field or the parameter may be set to a second value (e.g., 0, 1, not supported, disabled, and / or the like). Message 2122 may indicate that wireless device 2100 does not support (or does not indicate that wireless device 2100 supports) simultaneous SBFD operation in more than one carrier or cell, for example, based on the field or the parameter being set to the second value (or based on the field or the parameter being absent (or present) in message 2122).

[0467] Simultaneous SBFD operation in more than one carrier or cell may refer to (e.g., be the same as) wireless device 2100 applying or using more than one SBFD configurations (e.g., SBFD configuration 2006 and SBFD configuration 2016) simultaneously (eg., transmitting and / or receiving via one or more SBFD symbols of more than one cell or carrier simultaneously).

[0468] For brevity, in the following “more than one carrier or cell” may be replaced with “more than one cell." It is to be understood that, in some aspects, cell and carrier may refer to the same and may be used interchangeably.

[0469] In the example of FIG. 21, wireless device 2100 receives configuration parameters 2102. Configuration parameters 2102 may be, for example, the same as configuration parameters 2002. Configuration parameters 2102 may be, for example, of, for, associated with, corresponding to, or configured for cell 2104. Cell 2104 may be, for example, the same as cell 2004. Configuration parameters 2102 may comprise or indicate an SBFD configuration 2106. SBFD configuration 2106 may be, for example, the same as SBFD configuration 2006.

[0470] Wireless device 2100 may apply or use SBFD configuration 2106 based on (e.g., in response to, upon, or after) receiving configuration parameters 2102 and / or SBFD configuration 2106. In an example, wireless device 2100Docket No.: 25-1055PCTmay determine (e.g., consider, assume) SBFD configuration 2106 to be activated (or activate SBFD configuration 2106) based on (e.g., in response to, upon, or after) receiving configuration parameters 2102 and / or SBFD configuration 2106.

[0471] In the example of FIG. 21 , wireless device 2100 receives configuration parameters 2112. For example, wireless device 2100 may receive configuration parameters 2112 after receiving configuration parameters 2102. In an example, configuration parameters 2112 may be the same as or comprise configuration parameters 2012.Configuration parameters 2112 may be for cell 2114. Cell 2114 maybe, for example, a secondary cell (SCell). Cell 2114 may be, for example, a special cell (e.g., PSCell). Cell 2114 may be, for example, part of a master cell group (MCG). Cell 2114 may be, for example, part of a secondary cell group (SCG).

[0472] In an example, wireless device 2100 may receive configuration parameters 2112 via cell 2104. In another example, wireless device 2100 may receive configuration parameters 2112 via cell 2114.

[0473] Configuration parameters 2112 may comprise or indicate SBFD configuration 2116. SBFD configuration 2116 maybe, for example, the same as SBFD configuration 2016. For example, SBFD configuration 2116 may comprise or indicate one or more SBFD configuration parameters of, for, associated with, corresponding to, or configured for cell 2114. SBFD configuration 2116 may comprise or indicate one or more SBFD symbols of, for, associated with, corresponding to, or configured for cell 2114.

[0474] In an example, wireless device 2100 may determine whether to use (e.g., apply) SBFD configuration 2116 (e.g., together with SBFD configuration 2106) based on whether wireless device 2100 supports simultaneous SBFD operation in (e.g , on, via) more than one cell

[0475] In an example, wireless device 2100 may support simultaneous SBFD operation in more than one cell (or carrier). For example, message 2122 may indicate that wireless device 2100 supports simultaneous SBFD operation in more than one cell (or carrier). Wireless device 2100 may apply SBFD configuration 2116 (and SBFD configuration 2106) based on (e.g., in response to, upon, or after) wireless device 2100 supporting simultaneous SBFD operation in more than one cell (or carrier).

[0476] In another example, wireless device 2100 may not support simultaneous SBFD operation in more than one cell (or carrier). For example, message 2122 may indicate that wireless device 2100 does not support simultaneous SBFD operation in more than one cell (or carrier). Wireless device 2100 may not apply SBFD configuration 2116 (and SBFD configuration 2106) based on (e.g., in response to, upon, or after) wireless device 2100 not supporting simultaneous SBFD operation in more than one cell (or carrier).

[0477] In some aspects, SBFD operation may refer to using an SBFD configuration. SBFD operation may refer to transmission and / or reception of one or more signals via one or more SBFD symbols (e.g., of a cell like cell 2104 or cell 2114).

[0478] In some aspects, a special cell (eg., PCell, PSCell) may always be activated.Docket No.: 25-1055PCT

[0479] FIG. 22 illustrates a flow diagram as per an aspect of an embodiment of the present disclosure. The example of FIG.22 maybe used together with or independently from any of the previous examples (e.g., in FIGS. 1A-21).

[0480] In the example of FIG. 22, at step 2202, a wireless device (e.g., wireless device 2100, wireless device 2000, wireless device 1900, wireless device 1700, and / or any other wireless device of any embodiment of the present disclosure) receives one or more configuration parameters. The one or more configuration parameters may be the same as the one or more configuration parameters described in any of the previous examples. For example, configuration parameters 1708 may be or comprise the one or more configuration parameters.

[0481] The one or more configuration parameters (e.g., configuration parameters 2102 and / or configuration parameters 2112) may comprise a first SBFD configuration (e.g., SBFD configuration 2106) of, for, associated with, corresponding to, or configured for a first cell (e.g., cell 2104). The one or more configuration parameters may comprise or indicate a second SBFD configuration (e.g., SBFD configuration 2116) of, for, associated with, corresponding to, or configured fora second cell (e.g., cell 2114).

[0482] At step 2204, the wireless device may determine whether to use (e.g., apply) the first SBFD configuration and / or the second SBFD configuration based on whether the second cell is activated. In a first example, the second cell may be activated (e.g., the wireless device and / or the base station may activate the second cell). In an example, the second cell may be activated. For example, at step 2204, the wireless device may determine the second cell to be activated. The wireless device may perform step 2206 based on (e.g., in response to, upon, or after) the second cell being activated (or activating the second cell). The wireless device may perform step 2206 based on (e.g., in response to, upon, or after) the wireless device supporting simultaneous SBFD operation in, on, or via more than one cell.

[0483] In another example, the second cell may not be activated (e.g., may be deactivated). For example, at step 2204, the wireless device may determine the second cell to not be activated (e.g., to be deactivated). The wireless device may perform step 2208 based on (e.g., in response to, upon, or after) the second cell being deactivated (or deactivating the second cell). The wireless device may perform step 2208 based on (e.g., in response to, upon, or after) the wireless device not supporting simultaneous SBFD operation in, on, or via more than one cell.

[0484] Step 2206 may comprise the wireless device: using or applying the second SBFD configuration; not using or not applying the first SBFD configuration; releasing (e.g., stop using, discarding, deleting, clearing, flushing) the first SBFD configuration; and / or starting using the second SBFD configuration.

[0485] Step 2208 may comprise the wireless device: not using or not applying the second SBFD configuration; using or applying the first SBFD configuration; and / or continuing using the first SBFD configuration.

[0486] In an example, wireless device 2100 may not be a half-duplex wireless device. For example, wireless device 2100 may be capable of transmitting uplink transmissions and receiving downlink receptions at the same time.

[0487] FIG. 23 shows an example as per an aspect of an embodiment of the present disclosure. The example of FIG.23 may be used together with or independently from any of the previous examples (e.g., in FIGS. 1A-22)Docket No.: 25-1055PCT

[0488] In the example of FIG. 23, at step 2302, a wireless device (e.g., wireless device 2100, wireless device 2000, wireless device 1700, wireless device 1900, and / or any other wireless device described above) receives a first SBFD configuration of a first cell. For example, the first SBFD configuration may be SBFD configuration 2106. The first cell maybe, for example, cell 2104.

[0489] The first SBFD configuration may be, for example, SBFD configuration 2116.

[0490] The first cell may be, for example, cell 2114.

[0491] At step 2304, the wireless device may perform SBFD operation via the first cell. Step 2304 may comprise the wireless device performing SBFD operation using the first SBFD configuration. For example, step 2304 may comprise the wireless device transmitting one or more uplink transmissions via one or more SBFD symbols indicated by the first SBFD configuration. Step 2304 may comprise the wireless device receiving one or more downlink receptions via one or more SBFD symbols indicated by the first SBFD configuration.

[0492] At step 2306, the wireless device may receive a second SBFD configuration (e.g., SBFD configuration 2116) of, for, associated with, corresponding to, or configured for a second cell (e.g., cell 2114). In an example, step 2306 may be after step 2304.

[0493] In some aspects, step 2306 may be after step 2302 (e.g., without step 2304).

[0494] In an example, the wireless device may not support simultaneous SBFD operation via more than one cell. For example, the wireless device may transmit message 2122 indicating that the wireless device does not support simultaneous SBFD operation via more than one cell. In an example, the wireless device may perform step 2308 based on the wireless device not supporting simultaneous SBFD operation via more than one cell.

[0495] In an example, the wireless device may perform step 2308 based on (e.g., in response to, upon, or after) step 2306. The wireless device may perform step 2308 based on (e.g., in response to, upon, or after) receiving the second SBFD configuration of, for, associated with, corresponding to, or configured for the second cell.

[0496] In an example, the wireless device may perform step 2308 based on (e.g., in response to, upon, or after) activating the second cell (e.g., SCell). In another example, the wireless device may perform step 2308 based on (e.g., in response to, upon, or after) the second cell being activated. Step 2306 may, for example, comprise the wireless device activating the second cell. Step 2306 may comprise the wireless device receiving a command (e.g., configuration parameters 2112, MAC CE, SCell activation / deactivation MAC CE) that indicates activation of the second cell.

[0497] Step 2308 may comprise the wireless device deactivating the first SBFD configuration of the first cell.Deactivating an SBFD configuration (e.g., the first SBFD configuration, SBFD configuration 2106) may refer to the wireless device not using the first SBFD configuration. Deactivating the SBFD configuration may refer to the wireless device not performing one or more uplink transmissions and / or one or more downlink receptions via one or more SBFD symbols indicated by the SBFD configuration. At step 2308, based on (e.g., in response to, upon, or after) deactivating the SBFD configuration, the wireless device may not transmit one or more uplink transmissions via one or more SBFDDocket No.: 25-1055PCTsymbols of the first cell, wherein the one or more SBFD symbols are indicated by the first SBFD configuration At step 2308, based on (e.g., in response to, upon, or after) deactivating the first SBFD configuration, the wireless device may not receive one or more downlink receptions via one or more SBFD symbols of the first cell, wherein the one or more SBFD symbols are indicated by the first SBFD configuration.

[0498] Deactivating the first SBFD configuration based on receiving the second SBFD configuration allows the wireless device to (only) use a single SBFD configuration (e.g., the second SBFD configuration and not the first SBFD configuration). This allows the wireless device and the base station to be aligned on which SBFD configuration (among the first SBFD configuration and the second SBFD configuration) the wireless device applies when the wireless device receives (or has received) two different SBFD configurations (e.g., the first SBFD configuration and the second SBFD configuration). As a result, network operation may be enhanced.

[0499] In an example, step 2308 may comprise starting or restarting a timer (e.g., SCell deactivation timer).

[0500] In an example, configuration parameters 2112 may comprise or indicate the second SBFD configuration. Configuration parameters 2112 may comprise a field or parameter indicating whether SBFD operation is enabled in (e.g., on, via, for, to, and / or the like) the second cell. The field or parameter may indicate whether to enable SBFD operation.

[0501] In an example, the field or parameter may indicate to enable SBFD operation (or indicate that SBFD operation is enabled). For example, the presence of the field or parameter in configuration parameters 2112 may indicate to enable SBFD operation (or indicate that SBFD operation is enabled). In another example, a first value (e.g., 1, true, enable, activate) of the field or parameter may indicate to enable SBFD operation (or indicate that SBFD operation is enabled). The wireless device may perform step 2308 based on the field or parameter. For example, the wireless device may perform step 2308 based on the field or parameter indicating that SBFD operation is enabled (or indicating activation of SBFD operation). The field or parameter may be of, for, associated with, corresponding to, or configured for the second cell.

[0502] In another example, the field or parameter may indicate to disable SBFD operation (or indicate that SBFD operation is not enabled or disabled). For example, the absence of the field or parameter in configuration parameters 2112 may indicate to disable SBFD operation (or indicate that SBFD operation is not enabled or disabled). In another example, a second value (e.g., 0, false, disable, deactivate) of the field or parameter may indicate to disable SBFD operation (or indicate that SBFD operation is disabled or not enabled). The wireless device may not perform step 2308 based on the field or the parameter indicating that SBFD operation is disabled (or indicating deactivation of SBFD operation). The wireless device may perform SBFD operation via the first cell (e.g., using the first SBFD configuration) based on the field or the parameter indicating that SBFD operation is disabled (or indicating deactivation of SBFD operation). The wireless device may not perform SBFD operation via the second cell (e.g., using the second SBFD configuration) based on the field or the parameter indicating that SBFD operation is disabled (or indicating deactivation of SBFD operation).Docket No.: 25-1055PCT

[0503] In an example, the wireless device may perform step 2308 based on (e.g., in response to, upon, or after) receiving a control command. The control command may be, for example, a MAC CE. The control command may be, for example, a DCI. The control command may be or comprise, for example, configuration parameters 2112.

[0504] The control command may be, for example, SCell activation / deactivation MAC CE. The control command may activate the second cell. The control command may, for example, indicate activation of the second cell. The wireless device may activate the second cell based on (e.g., in response to, upon, or after) receiving the control command. The wireless device may activate the second cell based on (e.g., in response to, upon, or after) the control command. The wireless device may activate the second cell based on (e.g., in response to, upon, or after) the control command activating the second cell (or the control command indicating activation of the second cell).

[0505] Step 2308 may comprise the wireless device performing SBFD operation via the second cell (e.g., using the second SBFD configuration).

[0506] FIG. 24 illustrates an example as per an aspect of an embodiment of the present disclosure. The example of FIG. 24 may be used together with or independently from any of the previous examples (e.g., in FIGS. 1 A-23).

[0507] According to the example of FIG.24, at step 2402, a wireless device (e.g., wireless device 2100, wireless device 2000, wireless device 1700, wireless device 1900, and / or any other wireless device described above) receives a first SBFD configuration (e.g., SBFD configuration 2106) of a first cell (e.g., cell 2104). The wireless device may receive configuration parameters 2102 comprising the first SBFD configuration.

[0508] The wireless device receives a second SBFD configuration (e.g., SBFD configuration 2116) of, for, associated with, corresponding to, or configured for a second cell (e.g., cell 2114). The wireless device may receive configuration parameters 2112 comprising the second SBFD configuration.

[0509] At step 2404, the wireless device may perform SBFD operation via the second cell (e.g., using the second SBFD configuration). Step 2404 may, for example, comprise step 2308. In an example, step 2404 may be or occur after step 2308. Step 2404 may, for example, comprise the wireless device not performing SBFD operation via the first cell using the first SBFD configuration. For example, the wireless device may not perform SBFD operation via the first cell using the first SBFD configuration at step 2404 based on the wireless device not supporting simultaneous SBFD operation in more than one cell.

[0510] At step 2406, the wireless device may deactivate the second cell. In an example, step 2406 may comprise the wireless device receiving a control command The control command may be the same control command described in connection with the example of FIG. 23. The control command may deactivate the second cell. In an example, the control command may indicate deactivation of the second cell. The wireless device may deactivate the second cell based on (e.g., in response to, upon, or after) receiving the control command (indicating deactivation of the second cell).

[0511] In another example, at step 2406, the wireless device may deactivate the second cell based on (eg., in response to, upon, or after) an expiration of a timer. The timer may be an SCell deactivation timer. For example,Docket No.: 25-1055PCTconfiguration parameters 2102, configuration parameters 1708, and / or configuration parameters 2112 may comprise or indicate the timer. For example, configuration parameters 2102, configuration parameters 1708, and / or configuration parameters 2112 comprise or indicate a value (e.g., initial value) of the timer. In an example, the wireless device may start or restart the timer based on (e.g., in response to, upon, or after): receiving a PDCCH via the second cell, wherein the PDCCH indicates an uplink grant or downlink assignment; receiving PDCCH via a cell (e.g., the first cell, the second cell, or any other cell) scheduling the second cell, wherein the PDCCH indicates an uplink grant or a downlink assignment for the second cell; transmitting a protocol data unit (e.g., MAC PDU) in a configured uplink grant and LBT failure indication is not received from lower layers (e.g., of the wireless device); and / or receiving a MAC PDU in a configured downlink assignment.

[0512] In an example, the second cell may be activated before step 2406.

[0513] In an example, the second cell may not be activated after step 2406.

[0514] The wireless device may perform step 2408 based on (e.g., in response to, upon, or after) step 2406. Step 2408 may comprise the wireless device deactivating SBFD operation on or via the second cell (e.g., cell 2114). Step 2408 may comprise activating SBFD operation on or via the first cell (e.g., cell 2104).

[0515] In some aspects, step 2404 may comprise step 2304, step 2306, and / or step 2308.

[0516] In some aspects, step 2408 may comprise step 2304, step 2306, and / or step 2308.

[0517] FIG. 25 illustrates an example as per an aspect of an embodiment of the present disclosure. The example of FIG. 25 may be used together with or independently from any of the previous examples (e.g., in FIGS. 1 A-24).

[0518] According to the example of FIG.25, at step 2502, a wireless device (e.g., wireless device 1700, wireless device 1900, wireless device 2000, wireless device 2100, and / or any other wireless device described above) receives SBFD configurations of, for, associated with, corresponding to, or configured for cells. The cells may comprise the first cell. The cells may comprise the second cell. The cells may comprise cell 2104. The cell may comprise cell 2114. Each SBFD configuration, of the SBFD configurations, may be of, for, associated with, corresponding to, or configured for a respective cell of the cells

[0519] In an example, at step 2504, the wireless device may determine whether the wireless device supports simultaneous SBFD operation in (e.g., on, via, to, for, toward, and / or the like) more than one cell. In an example, the wireless device may support simultaneous SBFD operation in more than one cell. The wireless device may perform step 2512 based on (e.g., in response to, upon, or after) the wireless device supporting simultaneous SBFD operation in more than one cell.

[0520] At step 2512, the wireless device may apply the SBFD configurations to the cells. For example, the wireless device may apply each SBFD configuration, of the one or more SBFD configurations, to a respective cell of the one or more cells.Docket No.: 25-1055PCT

[0521] In an example, the wireless device may not support simultaneous SBFD operation in more than one cell. The wireless device may perform step 2506 based on thew wireless device not supporting simultaneous SBFD operation in more than one cell.

[0522] In an example, the wireless device may perform step 2506 based on (e.g., in response to, upon, or after) performing step 2406 and / or step 2306.

[0523] Step 2506 may comprise the wireless device determining a cell, among the cells, to apply SBFD configuration. In an example, the cells may be associated with (e.g., identified by or uniquely identified by) cell indexes. For example, each cell index, of the cell indexes, may indicate or identify (e.g., be associated with) a respective cell of the cells. In an example, at step 2506, the wireless device may determine the cell based on a cell index, of (e.g., identifying or associated with) the cell, being the lowest (e.g., smallest, least, below any other) among the cell indexes. In an example, at step 2506, the wireless device may determine the cell based on the cell index of (e.g., identifying or associated with) the cell, being the highest (e.g., largest, greatest, above any other) among the cell indexes. In an example, the one or more configuration parameters, configuration parameters 1708, configuration parameters 2102, and / or configuration parameters 2112 may comprise or indicate the cell indexes.

[0524] In an example, at step 2506, the wireless device may determine the cell based on the cell being an intra-band cell with a current serving cell (or a cell that is being deactivated, e.g., the second cell in step 2406). In an example, at step 2506, the wireless device may determine the cell based on the cell being an inter-band cell with a current serving cell (ora cell that is being deactivated, e.g., the second cell in step 2406).

[0525] In an example, at step 2506, the wireless device may determine the cell based on the cell having highest or lowest priority (or priority index) among priorities (or priority indexes) of the cells. In an example, the one or more configuration parameters, configuration parameters 1708, configuration parameters 2102, and / or configuration parameters 2112 may comprise or indicate the priorities (or priority indexes).

[0526] In an example, configuration parameters 1708, configuration parameters 2112, configuration parameters 2102 and / or the one or more configuration parameters may comprise or indicate the cell indexes.

[0527] In an example, an SBFD configuration (e.g., SBFD configuration 2106, SBFD configuration 2116), of the SBFD configurations, may be of, for, associated with, corresponding to, or configured for the cell. The wireless device may perform step 2508 after step 2506. At step 2508, the wireless device may use or apply the SBFD configuration to (eg., on, or via) the cell. At step 2508, the wireless device may not use or apply other SBFD configurations (other than the SBFD configuration), of the SBFD configurations.

[0528] In some aspects, "cell” may refer to “carrier'’ or “TDD carrier” and the terms may be used interchangeably.

[0529] In some aspects, cell 2104 and / or cell 2114 may be or comprise the cell described in connection with the example of FIG. 17A.

[0530] In some aspects, activating an SBFD configuration (e.g., SBFD configuration 2106, SBFD configuration 2116, the first SBFD configuration, the second SBFD configuration, and / or any other SBFD configuration or SBFDDocket No.: 25-1055PCTconfiguration parameters) may comprise or refer to determining the SBFD configuration to be available (e.g. , enabled, usable, on, valid, present, not invalid, and / or the like). Activating the SBFD configuration may comprise or refer to using or applying the SBFD configuration.

[0531] In some aspects, deactivating an SBFD configuration (e.g., SBFD configuration 2106, SBFD configuration 2116, the first SBFD configuration, the second SBFD configuration, and / or any other SBFD configuration or SBFD configuration parameters) may comprise or refer to determining the SBFD configuration to be unavailable (e.g., disabled, unusable, off, invalid, absent, invalid, and / or the like). Deactivating the SBFD configuration may comprise or refer to not using or not applying the SBFD configuration.

[0532] In some aspects, the terms SBFD configuration and one or more SBFD configuration parameters may be (or refer to) the same and / or may be used interchangeably. For example, an SBFD configuration may comprise or indicate one or more SBFD configuration parameters.

[0533] In some aspects, determining to activate the SBFD configuration may, for example, be the same as activating the SBFD configuration. In some aspects, determining to deactivate the SBFD configuration may, for example, be the same as deactivating the SBFD configuration.

[0534] Using or applying an SBFD configuration (e.g., SBFD configuration 2106, SBFD configuration 2116, the first SBFD configuration, the second SBFD configuration, and / or any other SBFD configuration or SBFD configuration parameters) may refer to or comprise transmitting a random-access preamble via a physical random access channel (PRACH) occasion, wherein the PRACH occasion is in (e.g., comprise, overlap in time with) one or more SBFD symbols indicated by the SBFD configuration. A wireless device (e.g., wireless device 2100) may transmit the randomaccess preamble, for example, via cell 2104 and / or cell 2114. The wireless device may transmit the random-access with or using a transmit power. The wireless device may determine the transmit power using random-access power control parameters (e.g., preamble received target power, power ramping step, power ramping counter, maximum output transmit power, and / or the like). The SBFD configuration may comprise or indicate the random-access power control parameters.

[0535] Using or applying an SBFD configuration (e.g., SBFD configuration 2106, SBFD configuration 2116, the first SBFD configuration, the second SBFD configuration, and / or any other SBFD configuration or SBFD configuration parameters) may refer to or comprise transmitting and / or receiving one or more signals (e.g., PUSCH, PUCCH, PRACH, SRS, PDCCH, PDSCH, and / or any other common or dedicated channel signal) via one or more occasions (e.g., one or more transmission occasions, one or more reception occasions). The one or more occasions may be in (e.g., comprise, overlap with, overlap in time with, and / or the like) one or more SBFD symbols indicated in the SBFD configuration (e.g., examples of how the SBFD configuration indicates the one or more SBFD symbols is explained above, e.g., in the example of FIG. 18A and / or FIG. 18B). Using or applying the SBFD configuration may comprise the wireless device (e.g., wireless device 2100) transmitting the one or more signals with or using a transmit power. The wireless device may determine the transmit power using or based on one or more power control parameters (e.g.,Docket No.: 25-1055PCTPUSCH power control parameters, PUCCH power control parameters, SRS power control parameters, PO, target received power, alpha, pathloss factor, pathloss scaling factor, f, g, h, closed-loop index, pathloss reference signal, and / or other parameter or signal that may be used to determine the transmit power). The SBFD configuration may comprise or indicate the one or more power control parameters.

[0536] Using or applying an SBFD configuration (e.g. , SBFD configuration 2106, SBFD configuration 2116, the first SBFD configuration, the second SBFD configuration, and / or any other SBFD configuration or SBFD configuration parameters) to (e.g., on or via) a cell may refer to the wireless device transmitting one or more uplink transmissions and / or receiving one or more downlink receptions via one or more SBFD symbols of the cell. Using or applying the SBFD configuration may refer to performing SBFD operation via the cell using the SBFD configuration.

[0537] In some aspects, the terms "SBFD configuration” and "one or more SBFD configuration parameters” may be used interchangeably (e.g., may refer to the same). The SBFD configuration may comprise or indicate the one or more SBFD configuration parameters.

[0538] In some aspects, the terms “enable” and “activate” may be the same and / or may be used interchangeably. In some aspects, “enable” and / or “activate" may refer to (or be replaced with) turn on, available, valid, on, permitted, allowed, and / or any other term that indicates a positive or usable connotation. For example, enabling SBFD operation may be the same as activating SBFD operation.

[0539] In some aspects, the terms “disable” and “deactivate” may be the same and / or may be used interchangeably. In some aspects, “disable” and / or “deactivate” may refer to (or be replaced with) turn off, unavailable, invalid, off, not permitted, disallowed, and / or any other term that indicates a negative or unusable connotation. For example, disabling SBFD operation may be the same as deactivating SBFD operation.

[0540] Performing SBFD operation via a cell (e.g., the first cell, the second cell, cell 2104, cell 2114) may comprise transmitting one or more uplink transmissions via one or more SBFD symbols of the cell. Performing SBFD operation via the cell (e.g., the first cell, the second cell, cell 2104, cell 2114) may comprise receiving one or more downlink receptions via one or more SBFD symbols of the cell. Performing SBFD operation using an SBFD configuration (eg., first SBFD configuration, SBFD configuration 2106, second SBFD configuration, SBFD configuration 2116) may comprise transmitting one or more uplink transmissions via one or more SBFD symbols indicated by the SBFD configuration. Performing SBFD operation using the SBFD configuration (e.g., first SBFD configuration, SBFD configuration 2106, second SBFD configuration, SBFD configuration 2116) may comprise receiving one or more downlink signals via one or more SBFD symbols indicated by the SBFD configuration. For example, performing SBFD operation via a first cell using a first SBFD configuration may comprise or refer to performing one or more uplink transmissions and / or one or more downlink receptions via the first cell and via one or more first SBFD symbols indicated by the first SBFD configuration. Performing SBFD operation via a second cell using a second SBFD configuration may comprise or refer to performing one or more uplink transmissions and / or one or more downlink receptions via the second cell and via one or more second SBFD symbols indicated by the second SBFD configuration.Docket No.: 25-1055PCT

[0541] In some aspects, a cell (e.g., the first cell, the second cell, cell 2104, cell 2114) may be activated based on (e.g., in response to, upon, or after) the wireless device activating the cell.

[0542] In some aspects, a cell (e.g., the first cell, the second cell, cell 2104, cell 2114) may be deactivated based on (e.g., in response to, upon, or after) the wireless device deactivating the cell. For example, the wireless device may deactivate the cell based on (e.g., in response to, upon, or after) an expiration of a timer (e.g., SCell deactivation timer).

[0543] In some aspects, using an SBFD configuration (e.g., SBFD configuration 2006, SBFD configuration 2016, SBFD configuration 2106, SBFD configuration 2116, the first SBFD configuration, the second SBFD configuration) may be the same as or refer to applying the SBFD configuration, selecting the SBFD configuration, determining the SBFD configuration, starting using the SBFD configuration, starting applying the SBFD configuration, starting a timer or window associated with the SBFD configuration, starting (using) SBFD operation, using or applying SBFD operation (e.g., according to or using the SBFD configuration), and / or the like. Using or applying SBFD operation may refer to or comprise transmitting one or more uplink transmissions via one or more SBFD symbols (e.g., uplink sub-bands of the one or more SBFD symbols) and / or receiv...

Claims

Docket No.: 25-1055PCTCLAIMSWhat is claimed is:

1. A method comprising:receiving, by a wireless device:first configuration parameters of a first cell, wherein the first configuration parameters indicate first symbols, of the first cell, as sub-band full duplex (SBFD) symbols; andsecond configuration parameters of a second cell, wherein the second configuration parameters indicate second symbols, of the second cell, as SBFD symbols;in response to the second cell being activated:transmitting, via the second cell, uplink transmissions via at least one symbol of the second symbols; and not transmitting, via the first cell, uplink transmissions via the first symbols;deactivating the second cell; andin response to the second cell being deactivated, transmitting, via the first cell, uplink transmissions via one or more symbols of the first symbols.

2. The method of claim 1 , wherein the first cell is at least one of:a special cell (SpCell);a primary cell (PCell); ora primary secondary cell (PSCell).

3. The method of claim 1 or 2, wherein the second cell is a secondary cell (SCell) .

4. The method of any one of claims 1 to 3, further comprising receiving one or more messages.

5. The method of claim 4, wherein the one or more messages are one or more downlink messages.

6. The method of claim 4 or 5, wherein the one or more messages are at least one of:one or more radio resource control (RRC) messages;one or more RRC setup messages;one or more RRC reconfiguration messages; orone or more system information block (SIB) messages.

7. The method of any one of claims 4 to 6, wherein the one or more messages comprise at least one of:the first configuration parameters; orthe second configuration parameters.

8. The method of any one of claims 1 to 7, wherein the first symbols and the second symbols do not overlap in time.

9. The method of any one of claims 1 to 8, further comprising transmitting a capability message.

10. The method of claim 9, wherein the capability message indicates that the wireless device does not support simultaneous SBFD operation via more than one cell.Docket No.: 25-1055PCT11. The method of claim 10, wherein the not transmitting, via the first cell, the uplink transmissions via the first symbols is further in response to the capability message indicating that the wireless device does not support simultaneous SBFD operation via more than one cell.

12. The method of any one of claims 1 to 11 , wherein the first configuration parameters indicate the first symbols as downlink (DL) symbols.

13. The method of any one of claims 1 to 12, wherein the second configuration parameters are cell-specific configuration parameters.

14. The method of any one of claims 1 to 13, wherein the first configuration parameters comprise a first SBFD configuration indicating the first symbols as SBFD symbols.

15. The method of claim 14, wherein not transmitting uplink transmissions via the first symbols is further based on deactivating the first SBFD configuration.

16. The method of claim 15, further comprising activating the first SBFD configuration in response to deactivating the second cell.

17. The method of claim 16, wherein transmitting, via the first cell, uplink transmissions via the one or more symbols is further in response activating the first SBFD configuration.

18. The method of any one of claims 1 to 17, wherein second configuration parameters indicate a deactivation timer.

19. The method of claim 18, wherein the deactivating the second cell is based on an expiration of the deactivation timer.

20. The method of any one of claims 1 to 19, further comprising receiving a medium access control (MAC) control element (CE) indicating deactivation of the second cell.

21. The method of claim 20, wherein deactivating the second cell is based on receiving the MAC CE indicating deactivation of the second cell.

22. The method of claim 20 or 21, wherein the MAC CE is an SCell activation / deactivation MAC CE.

23. The method of any one of claims 1 to 22, further comprising determining the first cell, to transmit uplink transmission via the one or more symbols, in response to deactivating the second cell.

24. The method of claim 23, wherein the determining is based on a cell index.

25. The method of claim 24, wherein the cell index identifies the first cell.

26. The method of claim 24 or 25, wherein the cell index is lowest among cell indexes.

27. The method of claim 26, wherein the cell indexes comprise the cell index.

28. The method of claim 26 or 27, wherein the cell indexes comprise a second cell index identifying the second cell.

29. The method of any one of claims 23 to 28, wherein the determining is based on the first cell being special cell (SpCell).Docket No.: 25-1055PCT30. The method of claim 29, wherein the second configuration parameters comprise a parameter to enable a SBFD operation of the second cell, wherein the transmitting, via the second cell, uplink transmissions via at least one symbol of the second symbols, is further based on the parameter.

31. The method of claim 30, wherein the parameter indicates to enable the SBFD operation of the second cell upon the second cell being activated.

32. The method of claim 31 , further comprising disabling a SBFD operation of the first cell based on the parameter of the second cell and the second cell being activated.

33. The method of claim 31 or 32, wherein the not transmitting, via the first cell, uplink transmissions via the first symbols is further based on the first cell being disabled with the SBFD operation.

34. The method of claim 32 or 33, wherein one or more messages, received by the wireless device, comprises a second parameter indicating a cell index for a default or fallback SBFD operation, wherein the first cell is configured with the cell index.

35. The method of claim 34, wherein at least one of:the second parameter is comprised in the second configuration parameters;the second parameter is comprised in the first configuration parameters; orthe second parameter is not comprised in the first configuration parameters or the second configuration parameters.

36. The method of claim 34 or 35, further comprising enabling a SBFD operation via a cell with the cell index in response to the second cell being deactivated, wherein the second cell is a current serving cell enabled with the SBFD operation. Upon deactivating the current serving cell enabled with the SBFD operation, enabling the cell with the SBFD operation wherein the cell index of the cell is indicated by the second parameter.

37. A method comprising:in response to a cell being activated:transmitting, via the cell, uplink transmissions overlapping in time with a plurality of first sub-band full duplex (SBFD) symbols of the cell; andnot transmitting, via a first cell, uplink transmissions overlapping in time with a plurality of second SBFD symbols of the first cell; andin response to the cell being deactivated, transmitting, via the first cell, uplink transmissions overlapping in time with the plurality of first SBFD symbols of the first cell.

38. A method comprising:receiving, by a wireless device:first configuration parameters of a first cell, wherein the first configuration parameters indicate a plurality of first symbols, of the first cell, as sub-band full duplex (SBFD) symbols; andDocket No.: 25-1055PCTsecond configuration parameters of a second cell, wherein the second configuration parameters indicate a plurality of second symbols, of the second cell, as SBFD symbols; andselecting a cell among the first cell and the second cell, or configuration among the first configuration parameters and the second configuration parameters, based on whether the second cell is activated.

39. The method of claim 37, further comprising:transmitting, via the selected cell, uplink transmissions via SBFD symbols of the cell.

40. An apparatus comprising:one or more processors; andmemory storing instructions that, when executed by the one or more processors, cause the apparatus to perform the method of any one of claims 1 to 39.

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

Images