Scheduling request

Abstract

A wireless device receives one or more configuration parameters comprising one or more first configuration parameters indicating a physical uplink control channel (PUCCH) resource for a first CSI report in a slot, one or more second configuration parameters configuring a symbol type associated with the first CSI report, wherein the symbol type is either sub-band full duplex (SBFD) or non-SBFD, and one or more third configuration parameters indicating scheduling request (SR) resource configurations for transmitting SRs in the slot. The wireless device determines, for transmitting the first CSI report, a first number of uplink control information (UCI) bits based on a second number of first SR resource configurations, among the SR resource configurations, that are associated with the symbol type. The wireless device transmits, in the slot and via the PUCCH resource, the CSI report comprising the first number of UCI bits.

Description

Docket No.: 25-1049PCTTITLEScheduling RequestCROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of U.S. Provisional Application No. 63 / 779,085, filed March 27, 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 station.Docket No.: 25-1049PCT

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

[0023] FIG. 17 illustrates an example of scheduling request procedure according to the present disclosure.

[0024] FIG. 18 illustrates an example of uplink control channel (UCI) transmission procedure according to the present disclosure.

[0025] FIG. 19 illustrates an example of a CSI report procedure according to the present disclosure.

[0026] FIG. 20 illustrates an example of UL / DL TDD configuration according to the present disclosure.

[0027] FIG. 21 illustrates an example of slot format in a TDD carrier according to the present disclosure.

[0028] FIG. 22 illustrates an example of sub-band full-duplex (SBFD) operation according to the present disclosure.

[0029] FIG. 23 illustrates an examples of sub-band full-duplex (SBFD) operation according to the present disclosure.

[0030] FIG. 24 illustrates an examples of sub-band full-duplex (SBFD) operation according to the present disclosure.

[0031] FIG. 25 illustrates an examples of sub-band full-duplex (SBFD) operation according to the present disclosure.

[0032] FIG. 26A and FIG. 26B illustrate UCI transmission procedures in a cell configured for SBFD operation according to the present disclosure.

[0033] FIG. 27A and FIG. 27B illustrate examples of uplink control information (UCI) transmission according to the present disclosure.

[0034] FIG. 28A and FIG. 28B illustrate examples of uplink control information (UCI) transmission according to the present disclosure.

[0035] FIG. 29A and FIG. 29B illustrate examples of uplink control information (UCI) transmission according to the present disclosure.

[0036] FIG. 30A, FIG. 30B, and FIG. 30C illustrate examples of UE-capabilities according to the present disclosure.

[0037] FIG. 31A and FIG. 31 B illustrate examples of a CSI report procedure according to the present disclosure.

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

[0039] FIG. 33A and FIG. 33B illustrate examples of a CSI report procedure according to the present disclosure.

[0040] FIG. 34A and FIG. 34B illustrate examples of a CSI report procedure according to the present disclosure.DETAILED DESCRIPTION

[0041] 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 functionalityDocket No.: 25-1049PCTand 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.

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

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

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

[0045] If A and B are sets and every element of A is an element of B, A is called a subset of B. In this specification, only non-empty sets and subsets are considered. For example, possible subsets of B = {celH , cell2} are: {celH }, {cell2}, and {celH, cell2}. The phrase “based on” (or equally “based at least on”) is indicative that the phrase following the term “based on” is an example of one of a multitude of suitable possibilities that may, or may not, be employed to one orDocket No.: 25-1049PCTmore 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.

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

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

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

[0049] 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 (eg. hardware with a biological element) ora combination thereof, which may be behaviorally equivalent. For example, modules may be implemented as a software routine written in a computer languageDocket No.: 25-1049PCTconfigured 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.

[0050] FIG. 1A illustrates an example of a mobile communication network 100 in which embodiments of the present disclosure may be implemented. The mobile communication network 100 may be, for example, a public land mobile network (PLMN) run by a network operator. As illustrated in FIG. 1A, the mobile communication network 100 includes a core network (CN) 102, a radio access network (RAN) 104, and a wireless device 106.

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

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

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

[0054] 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 basebandDocket No.: 25-1049PCTprocessing 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).

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

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

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

[0058] 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 inDocket No.: 25-1049PCTFIG. 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.

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

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

[0061] 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 / U PF 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- / i 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.

[0062] 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 / orDocket No.: 25-1049PCTsession 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.

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

[0064] 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 or more of the gNBs 160 and / or one or more of the ng-eNBs 162 may include three sets of antennas to respectively control three cells (or sectors). Together, the cells of the gNBs 160 and the ng-eNBs 162 may provide radio coverage to the UEs 156 over a wide geographic area to support UE mobility.

[0065] 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. 1B, gNB 160A maybe connected to the UE 156A by meansofa 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.

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

[0067] 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 EvolvedDocket No.: 25-1049PCTUMTS 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.

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

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

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

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

[0072] 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.Docket No.: 25-1049PCTFor reflective mapping, the SDAP 225 at the g NB 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.

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

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

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

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

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

[0078] 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+f, 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.

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

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

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

[0082] FIG. 4B further illustrates MAC control elements (CEs) inserted into the MAC PDU by a MAC, such as MAC 223 or MAC 222. For example, FIG. 4B illustrates two MAC CEs inserted into the MAC PDU. MAC CEs may be inserted at the beginning of a MAC PDU for downlink transmissions (as shown in FIG. 4B) and at the end of a MAC PDU for uplink transmissions. MAC CEs maybe used for in-band control signaling. Example MAC CEs include:Docket No.: 25-1049PCTscheduling-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.

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

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

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

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

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

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

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

[0090] 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 include, for example:

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

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

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

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

[0095] - a random access channel (RACH) for allowing a UE to contact the network without any prior scheduling.Docket No.: 25-1049PCT

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

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

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

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

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

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

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

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

[0104] 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 MACs212 and 222, the RLCs213and 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.

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

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

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

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

[0109] 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 receptionDocket No.: 25-1049PCTcycle) 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.

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

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

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

[0113] RAN areas may be used to track the UE at the RAN level. Fora UE in RRC inactive 606 state, the UE maybe 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.

[0114] 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 ofDocket No.: 25-1049PCTtime 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.

[0115] AgNB, such as gNBs 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.

[0116] In NR, the physical signals and physical channels (discussed with respect to FIG.5A and FIG. 5B) may be mapped onto orthogonal frequency divisional multiplexing (OFDM) symbols. OFDM is a multicarrier communication scheme that transmits data over F orthogonal subcarriers (or tones). Before transmission, the data may be mapped to a series of complex symbols (e.g., M-quadrature amplitude modulation (M-QAM) or M-phase shift keying (M-PSK) symbols), referred to as source symbols, and divided into F parallel symbol streams. The F parallel symbol streams may be treated as though they are in the frequency domain and used as inputs to an Inverse Fast Fourier Transform (IFFT) block that transforms them into the time domain. The IFFT block may take in F source symbols at a time, one from each of the F parallel symbol streams, and use each source symbol to modulate the amplitude and phase of one of F sinusoidal basis functions that correspond to the F orthogonal subcarriers. The output of the IFFT block may be F 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 (PARR). 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.

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

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

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

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

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

[0122] NR may support wide carrier bandwidths (e.g., up to 400 MHz for a subcarrier spacing of 120 kHz). Notall 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 U E’s receive bandwidth based on the amount of traffic the UE is scheduled to receive. This is referred to as bandwidth adaptation.

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

[0124] For unpaired spectra, a downlink BWP from a set of configured downlink BWPs may be linked with an uplink BWP from a set of configured uplink BWPs if a downlink BWP index of the downlink BWP and an uplink BWP index of the uplink BWP are the same. For unpaired spectra, a UE may expect that a center frequency for a downlink BWP is the same as a center frequency for an uplink BWP.Docket No.: 25-1049PCT

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

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

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

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

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

[0130] In an example, a base station may semi-statica I 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).

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

[0132] 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 timer and / or in response to receiving a DCI indicating BWP 904 as the active BWP. The UE may switch at a switching point 914 from active BWP 904 to BWP 902 in response to receiving a DCI indicating BWP 902 as the active BWP.

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

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

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

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

[0137] 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 differentDocket No.: 25-1049PCTPCells. 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 (ULSCC).

[0138] 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 indicate which SCells (e.g., in a subset of configured SCells) for the UE are activated or deactivated. Configured SCells may be deactivated in response to an expiration of an SCell deactivation timer (e.g., one SCell deactivation timer per SCell).

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

[0140] 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, may be transmitted in the uplink of the PCell 1021. Uplink control information (UCI) related to the downlink CCs of the PUCCH group 1050, shown as 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.

[0141] 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,Docket No.: 25-1049PCTfor 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.

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

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

[0144] 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 (e.g., every 2 frames or 20 ms). A burst may be restricted to a half-frame (e.g., a first half-frame having a duration of 5 ms). It will be understood that FIG. 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.

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

[0146] 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, theDocket No.: 25-1049PCTUE 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.

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

[0148] The PBCH may use a QPSK modulation and may use forward error correction (EEC). The EEC 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 (SEN) of the cell and / or a SS / PBCH block timing index. These parameters may facilitate time synchronization of the UE to the base station. The PBCH may include a master information block (MIB) used to provide the UE with one or more parameters. The MIB may be used by the UE to locate remaining minimum system information (RMSI) associated with the cell. The RMSI may include a System Information Block Type 1 (SIB1). The SIB1 may contain information needed by the UE to access the cell. The UE may use one or more parameters of the MIB to monitor PDCCH, which may be used to schedule PDSCH. The PDSCH may include the SIB1. The SIB1 may be decoded using parameters provided in the MIB. The PBCH may indicate an absence of SIB1. Based on the PBCH indicating the absence of SIB1 , the UE may be pointed to a frequency. The UE may search for an SS / PBCH block at the frequency to which the UE is pointed.

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

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

[0151] 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 aDocket No.: 25-1049PCTsecond 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.

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

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

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

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

[0156] 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 mayDocket No.: 25-1049PCTsupport 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.

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

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

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

[0160] 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 symbols of a PUSCH and / or a PUCCH. The base station may semi-statically configure the UE with a number (e.g. maximum number) of front-loaded DMRS symbols for the PUSCH and / or the PUCCH, which the UE may use to schedule a single-symbol DMRS and / or a double-symbol DMRS. An NR network may support (e.g., for cyclic prefix orthogonalDocket No.: 25-1049PCTfrequency 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.

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

[0162] Uplink PT-RS (which may be used by a base station for phase tracking and / or phase-noise compensation) may or may not be present depending on an RRC configuration of the UE. The presence and / or pattern of uplink PT-RS may be configured on a UE-specific basis by a combination of RRC signaling and / or one or more parameters employed for other purposes (e.g. , Modulation and Coding Scheme (MCS)), which may be indicated by DCI. When configured, a dynamic presence of uplink PT-RS may be associated with one or more DCI parameters comprising at least MCS. A radio network may support a plurality of uplink PT-RS densities defined in time / frequency domain. When present, a frequency domain density may be associated with at least one configuration of a scheduled bandwidth. The UE may assume a same precoding for a DMRS port and a PT-RS port. A number of PT-RS ports may be fewer than a number of DMRS ports in a scheduled resource. For example, uplink PT-RS may be confined in the scheduled time / frequency duration for the UE.

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

[0164] 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 domainDocket No.: 25-1049PCTbehavior 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.

[0165] 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 port is conveyed may be inferred from the channel over which a second symbol on a second antenna port is conveyed. The one or more large-scale properties may comprise at least one of: a delay spread; a Doppler spread; a Doppler shift; an average gain; an average delay; and / or spatial Receiving (Rx) parameters.

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

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

[0168] 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 aDocket No.: 25-1049PCTthird 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.

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

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

[0171] 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 beDocket No.: 25-1049PCTreferred 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.

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

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

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

[0175] 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 RRCJNACTIVE state may initiate the random access procedure to request a connection setup to a network. The UE may initiate the random access procedure from an RRC_CONNECTED state. The UE may initiate the random access procedure to request uplink resources (e.g., for uplink transmission of an SR when there is no PUCCH resource available) and / or acquire uplink timing (e.g., when uplink synchronization status is non-synchronized). The UE may initiate the random access procedure to request oneDocket No.: 25-1049PCTor 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.

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

[0177] The configuration message 1310 may be transmitted, for example, using one or more RRC messages. The one or more RRC messages may indicate one or more random access channel (RACH) parameters to the UE. The one or more RACH parameters may comprise at least one of following: general parameters for one or more random access procedures (e.g., RACH-configGenera , 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_I 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.

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

[0179] 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 UEDocket No.: 25-1049PCTmay 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).

[0180] 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 the association between the one or more preambles and the at least one reference signal is configured by an RRC message.

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

[0182] 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_RAMP / NG_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_TRANSM!SS!ON_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).Docket No.: 25-1049PCT

[0183] The Msg 2 1312 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 maybe scheduled on the DL-SCH and indicated on a PDCCH using a random access RNTI (RA-RNTI). The Msg 2 1312 may indicate that the Msg 1 1311 was received by the base station. The Msg 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-ResponseWindow) 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 be determined based on a numerology. The PDCCH may be in a common search space (e.g., a Typel -PDCCH common search space) configured by an RRC message. The UE may identify the RAR based on a Radio Network Temporary Identifier (RNTI). RNTIs may be used depending on one or more events initiating the random access procedure. The UE may use random access RNTI (RA-RNTI). The RA-RNTI may be associated with PRACH occasions in which the UE transmits a preamble. For example, the UE may determine the RA-RNTI based on: an OFDM symbol index; a slot index; a frequency domain index; and / or a UL carrier indicator of the PRACH occasions. An example of RA-RNTI may be as follows:

[0184] RA-RNTI= 1 +s_id + 14 x tjd + 14 x 80 xfjd + 14 x 80 x 8 x ul_carrier_id, 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., 02 tjd < 80), fjd may be an index of the PRACH occasion in the frequency domain (e.g., 02 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).

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

[0186] 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 baseDocket No.: 25-1049PCTstation), Msg 4 1314 will be received using a DL-SCH associated with the TC-RNTI. If a MAC PDU is successfully decoded and a MAC PDU comprises the UE contention resolution identity MAC CE that matches or otherwise corresponds with the CCCH SDU sent (e.g., transmitted) in Msg 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.

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

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

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

[0190] 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 aDocket No.: 25-1049PCTpreamble 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.

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

[0192] 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. The 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 2 1312 (e.g., an RAR) illustrated in FIGS. 13Aand 13B and / or the Msg 41314 illustrated in FIG. 13A.

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

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

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

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

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

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

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

[0200] 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 (eg., 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 forDocket No.: 25-1049PCTscheduling of PDSCH in a cell (e.g., with more DCI payloads than DCI format 1_0). DCI format 2_0 may be used for providing a slot format indication to a group of UEs. DCI format 2_1 may be used for notifying a group of UEs of a physical resource block and / or OFDM symbol where the UE may assume no transmission is intended to the UE. DCI format 2_2 may be used for transmission of a transmit power control (TPC) command for PUCCH or PUSCH. DCI format 2_3 may be used for transmission of a group of TPC commands for SRS transmissions by one or more UEs. DCI format(s) for new functions may be defined in future releases. DCI formats may have different DCI sizes, or may share the same DCI size.

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

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

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

[0204] 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 toDocket No.: 25-1049PCTbe 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).

[0205] 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 comprise decoding one or more PDCCH candidates of the set of the PDCCH candidates according to the monitored DCI formats. Monitoring may comprise decoding a DCI content of one or more PDCCH candidates with possible (or configured) PDCCH locations, possible (or configured) PDCCH formats (e.g., number of CCEs, number of PDCCH candidates in common search spaces, and / or number of PDCCH candidates in the UE-specific search spaces) and possible (or configured) DCI formats. The decoding may be referred to as blind decoding. The UE may determine a DCI as valid for the UE, in response to CRC checking (e.g., scrambled bits for CRC parity bits of the DCI matching a RNTI value). The UE may process information contained in the DCI (e.g., a scheduling assignment, an uplink grant, power control, a slot format indication, a downlink preemption, and / or the like).

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

[0207] 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 andDocket No.: 25-1049PCTfourteen 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.

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

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

[0210] 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 15021Docket No.: 25-1049PCTand 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.

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

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

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

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

[0215] 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 multiplexingDocket No.: 25-1049PCT(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.

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

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

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

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

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

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

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

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

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

[0225] For Automated Combination with RAN Master Specification

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

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

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

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

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

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

[0232] A base station may transmit one or more messages to a wireless device. The one or more messages may comprise (or be) the one or more MAC (or PDCP or RLC) PDUs. The wireless device may receive at least one message of the one or more messages via / using one or more PDSCHs / TBs comprising the one or more MAC PDUs.

[0233] The one or more messages may comprise (or be) one or more RRC messages. The one or more RRC messages may comprise at least one of an RRC connection message and / or an RRC establishment message and / or an RRC configuration message and / or an RRC setup message and / or an RRC release message. The one or more RRC messages may comprise at least one RRC reconnection / reestablishment / reconfiguration message.

[0234] The one or more messages may comprise one or more MAC CEs.Docket No.: 25-1049PCT

[0235] The one or more messages may comprise one or more DC Is. The one or more messages may be scheduled / triggered / indicated by at least one downlink control message (e.g., a DCI or a MAC CE or a downlink command). The one or more messages may comprise one or more downlink information for control.

[0236] The one or more messages may comprise one or more commands (e.g., control commands) for UL / DL communications via at least one cell / servi ng cell. The one or more messages may comprise one or more configuration parameters. The one or more configuration parameters may be / comprise / indicate one or more RRC configuration parameters. The one or more configuration parameters may correspond to (e.g., configure transmission / reception of) one or more signals / channels by the wireless device. The one or more channels / sig nals may comprise / be one or more DL signals / channels, e.g., PDSCH / CSI-RS / PDCCH / SSB (e.g., PSS and / or SSS) / WUS (wake up signal) / DL PRS / DL DM-RS / DL PT-RS or the like. The one or more channels / signals may comprise / be one or more UL signals / channels, e.g., PUSCH / SRS / PUCCH / WUS / PRACH / UL DM-RS / UL PT-RS or the like.

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

[0238] The one or more configuration parameters (e.g., CellGroupConfig and / or MAC-CellGroupConfig) may comprise one or more cell configuration parameters. The one or more cell configuration parameters may comprise / configure / indicate configuration parameters of the one or more cells (e.g., ServingCellConfigCommon, ServingCellConfigCommonSIB, and / or ServingCellConfig). The one or more cells may comprise one or more serving cell (equivalently one or more Serving Cells). The one or more cells may correspond to the plurality of CCs. The one or more cell configuration parameters may be for configuring one or more cells (e.g., the one or more Serving Cells) for UL / DL transmissions / receptions by the wireless device. For example, the one or more cells may comprise a master (or primary) cell group (MSG) and / or a secondary cell group (SCG). The one or more cell configuration parameters may comprise an MSG configuration configuring / indicating at least one cell of the MSG. The one or more cell configuration parameters may comprise an SSG configuration configuring / indicating at least one cell of the SSG.

[0239] In some cases, a cell of the one or more cells may be a primary secondary cell (PSCell), or a primary cell (PCell), or a secondary cell (SCell), or a special cell (SpCell). In some other cases, a cell of the one or more cells may belong to a first cell group or a second cell group. The first cell group may be also known / referred to by a primary TAGDocket No.: 25-1049PCT(pTAG) and / or a primary PUCCH group. The second cell group may be also known / referred to by a secondary TAG (sTAG) and / or a secondary PUCCH group.

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

[0241] For example, the one or more configuration parameters may configure the wireless device with uplink (UL) bandwidth parts (BWPs) and / or downlink (DL) BWPs. An initial active BWP may be a first BWP (of the UL BWPs and / or DL BWPs) used for initial access procedure (e.g., a random access procedure to obtain connection to the network) by the wireless device. In paired spectrum (e.g., FDD), the base station and / or the wireless device may independently switch across / between two DL BWPs (of the DL BWPs) and across / between two UL BWPs (of the UL BWPs). In unpaired spectrum (e.g., TDD), the base station and / or the wireless device may simultaneously switch across / between two DL BWPs (of the DL BWPs) and across / between two UL BWPs (of the UL BWPs).

[0242] In an example, the one or more configuration parameters may comprise configuration parameters of one or more BWPs (e.g., one or more BWP configuration parameters). The one or more BWPs (e.g., configured by dedicated BWP configuration of the one or more BWP configuration parameters) may be / comprise UL BWPs and / or DL BWPs. The one or more BWP configuration parameters may comprise / configure / indicate the UL BWPs and / or the DL BWPs. Among the one or more BWPs, at least one BWP may be configured as the first / initial active BWP (e.g., BWP 1), one BWP as the default BWP (e.g., BWP 0).

[0243] The one or more configuration parameters may comprise one or more SRS configuration parameters (e.g., SRS-config). The one or more SRS configuration parameters may configure / indicate sounding reference signal transmissions by the wireless device (e.g., to the base station). The one or more SRS configuration parameters defines / indicates / configures a list of SRS resources (e.g., SRS-Resources); and / or a list of SRS positioning resources (e.g., SRS-PosResources); and / or a list of SRS positioning resource set (e.g., SRSPosResourceSets); and / or a list of SRS resource set (e.g., SRS-ResourceSets). Each SRS positioning resource set of the list of SRS positioning resources may define / indicate a subset of SRS resources of the list of SRS resources and / or a subset of SRS positioning resources of the list of SRS positioning resources.

[0244] The one or more configuration parameters may comprise one or more CSI configuration parameters The one or more CSI configuration parameters may comprise at least: one or more CSI-RS resource settings (e.g., configurationDocket No.: 25-1049PCTparameters for one or more CSI-RS resources, e.g., CSI-ResourceConfig Resource Settings); one or more CSI reporting settings (e.g., configuration parameters for CSI reporting, e.g., CSI-ReportConfig Reporting Settings), and one or more CSI measurement settings (e.g., configuration parameters for one or more CSI-RS measurement / receptions, e.g., for channel measurement or interference measurement). The one or more CSI measurement settings may comprise one or two list(s) of trigger states (configured / indicated by CSI-AperiodicTriggerStateList and CSI-SemiPersistentOnPUSCH-TriggerStateList). Each trigger state in the CSI-AperiodicTriggerStateList contains at least one associated CSI reporting setting (e.g., CSI-ReportConfig) indicating Resource Set IDs (of the one or more CSI reporting settings) for channel (measurement) and / or optionally for interference (measurement). Each trigger state in the CSI-SemiPersistentOnPUSCH-TriggerStateList contains at least one associated CSI reporting setting (e.g., CSI-ReportConfig).

[0245] In an example, a CSI-RS resource setting of the one or more CSI-RS resource settings may comprise one or more CSI-RS resource sets (comprising one or more CSI-RS resources). The one or more CSI-RS resource sets may comprise a list of CSI Resource Sets (given by higher layer parameter csi-RS-ResourceSetList). For example, the list of CSI Resource Sets may comprise of references to either or both of NZP CSI-RS resource set(s) and SS / PBCH block set(s). In some examples, the list of CSI Resource Sets may comprise of references to CSI-IM resource set(s). Each CSI Resource Setting of the one or more CSI resource settings may be located in a DL BWP (e.g., identified by the higher layer parameter BWP-id). The one or more CSI Resource Settings may be linked to a CSI Report Setting of the one or more CSI report setting.

[0246] The wireless device may assume that NZP CSI-RS resource(s), of the one or more CSI-RS resource sets, for channel measurement and the CSI-IM resource(s) for interference measurement configured (by the one or more CSI configuration parameters) for one CSI reporting are resource-wise QCLed with respect to 'typeD'. When NZP CSI-RS resource(s) is used for interference measurement, the wireless device may assume that a NZP CSI-RS resource, of the one or more CSI-RS resource sets, for channel measurement and a CSI- IM resource (of the one or more CSI-RS resource sets) or NZP CSI-RS resource(s) (of the one or more CSI-RS resource sets) for interference measurement configured for one CSI reporting are QCLed with respect to 'typeD'

[0247] In an example, there may be one CSI-RS resource set for periodic CSI-RS, or semi-persistent (SP) CSI-RS or aperiodic CSI-RS. For example, the CSI-RS resource set may comprise at least one of: one CSI-RS type (e.g., periodic, aperiodic, or semi-persistent) and / or one or more CSI-RS resources. For example, a time domain behavior of the CSI-RS resources within the CSI-RS resource setting may be indicated / configured (e.g., by resourceType) as aperiodic, periodic, or semi-persistent. For example, the one or more CSI-RS resources may comprise at least one of: CSI-RS resource configuration identity (or index); number of CSI-RS ports; CSI-RS configuration (symbol and RE locations in a subframe); CSI-RS subframe configuration (subframe location, offset, and / or periodicity in radio frame); CSI-RS power parameter; CSI-RS sequence parameter; CDM type parameter; frequency density; transmission comb; and / or QCL parameters.Docket No.: 25-1049PCT

[0248] The CSI resource setting may indicate a semi-persistent resource type (e.g., the resourceType being set with ’semiPersistenf). In an example, the wireless device may receive a SP CSI-RS / CSI-IM Resource Set Activation MAC CE command indicating / activating at least one CSI-RS resource (or resource set) of the one or more CSI-RS resource sets (e.g., for channel / interference measurement(s)). For example, the one or more CSI-RS resource sets may comprise one or more CSI-IM / NZP CSI-RS resource sets for interference measurement associated with the at least one CSI-RS resource. The wireless device may receive a SP CSI-RS / CSI-IM Resource Set Deactivation MAC CE command for the (activated) at least one CSI-RS resource (or resource set).

[0249] The base station may transmit to the wireless device the one or more CSI-RS resources (e.g., during one or more CSI-RS transmission occasions). The wireless device may, during the one or more CSI-RS transmission / reception occasions, receive / measure the one or more CSI-RS (resources). The transmission of the one or more CSI resources may be periodically (e.g., when the resourceType is set to periodic) and / or aperiodic (e.g., when the resourceType is set to aperiodic), and / or semi-persistent (e.g., when the resourceType is set to semi-persistent).

[0250] In the periodic transmission (of the one or more CSI resources), the configured CSI-RS resource may be transmitted (by the base station) using a configured periodicity in time domain.

[0251] In the aperiodic transmission (of the one or more CSI resources), the configured CSI-RS resource may be transmitted (by the base station) in a dedicated time slot or subframe (by a DCI indicating the aperiodic CSI-RS resource).

[0252] In the semi-persistent (or a multi-shot) transmission (of the one or more CSI resources), the configured CSI-RS resource may be transmitted (by the base station) within a configured period (indicated by a MAC CE activation command). The base station may stop transmission of the one or more SP CSI-RSs if the CSI-RS is configured with a transmission duration. The base station may stop transmission of the one or SP CSI-RSs in response to transmitting a MAC CE or DCI for deactivating (or stopping the transmission of) the one or more SP CSI-RSs.

[0253] In the present disclosure, a CSI reporting setting may also referred to by a CSI report configuration.

[0254] The one or more CSI reporting settings (e.g., one or more CSI-ReportConfig) may configure / indicate at least one of the following: one or more periodic CSI reports; and / or one or more semi-persistent (SP) CSI reports on PUCCH (e.g., semiPersisteniOnPUCCH} and / or one or more SP CSI reports on PUSCH (e.g., semiPersisteniOnPUSCH} and / or one or more aperiodic CSI report (on PUSCH / PUCCH). Each CSI reporting setting (e.g., a CSI-ReportConfig with corresponding report configuration identifier reportConfigld) of the one or more CSI reporting settings may correspond to at least one of the following: a periodic CSI report of the one or more periodic CSI reports; a semi-persistent (SP) CSI reports on PUCCH of the one or more semi-persistent (SP) CSI reports on PUCCH; a SP CSI reports on PUSCH of the one or more SP CSI reports on PUSCH (e.g., semiPersistentOnPUSCH); ora aperiodic CSI report of the one or more aperiodic CSI report (on PUSCH / PUCCH).

[0255] In an example, a CSI reporting setting (e.g., CSI-ReportConfig) of the one or more CSI reporting settings may comprise at least one of: a report configuration identifier for the CSI report; a report type (e.g., indicated byDocket No.: 25-1049PCTreportConfigType); one or more reported CSI parameters; one or more CSI type (e.g., type I or type II); one or more codebook configuration parameters; one or more parameters indicating time-domain behavior; frequency granularity for CQI and PMI; and / or measurement restriction configurations. The CSI reporting setting may further comprise at least one of: one periodicity parameter (e.g., indicating a periodicity of a CSI report in case of periodic / SP CSI reports); one duration parameter (e.g., indicating a duration of the CSI report transmission); and / or one slot offset (e.g., indicating a value of timing offset of the CSI report), if the report type is a periodic CSI or a semi-persistent CSI report. For example, the one periodicity parameter and / or the one slot offset may apply in the numerology of an UL BWP (of the one or more BWPs) in which the CSI report is configured for transmission (e.g., indicated via BWP Id of the corresponding PUCCH resource). The wireless device may, via the cell, transmit the CSI report, e.g., based on the received one or more CSI-RS (resources) during / in the one or more CSI-RS transmission / reception occasions.

[0256] The report type of the CSI reporting setting may indicate a time domain behavior of the CSI report. For example, the time domain behavior may be indicated by a reportConfigType of the CSI reporting setting and may be set to 'aperiodic' (e.g., aperiodic CSI report using / on PUSCH), 'semiPersistentOnPUCCH' (e.g., semi-persistent CSI report using / on PUCCH), 'semiPersistentOnPUSCH' (e.g., semi-persistent CSI report using / on PUSCH that is activated by a DCI), or 'periodic' (e.g., periodic CSI report using / on PUCCH).

[0257] If the wireless device is configured (e.g., by the one or more CSI reporting settings) with the semi-persistent CSI reporting (on / using PUSCH or PUCCH), the wireless device may report CSI when both CSI-IM and NZP CSI-RS resources are configured as periodic or semi-persistent. If the wireless device is configured (e.g., by the one or more CSI reporting settings) with the aperiodic CSI reporting (on PUSCH), the wireless device may report CSI when both CSI-IM and NZP CSI-RS resources are configured as periodic, semi-persistent or aperiodic. For example, the CSI report may comprise Channel Quality Indicator (CQI), precoding matrix indicator (PMI), CSI-RS resource indicator (CRI), SS / PBCH Block Resource indicator (SSBRI), layer indicator (LI), rank indicator (Rl), Layer 1 reference signal received power (L1-RSRP) or Layer 1 signal-to-interference-plus-noise ratio (L1-SINR).

[0258] The CSI reporting (or report) may comprise transmitting / sending the CSI report via the serving cell. The wireless device may perform the CSI reporting by transmitting the CSI report at / during / in an uplink slot n. The wireless device may perform a semi-persistent CSI reporting on a PUSCH in response to the semi-persistent CSI reporting being activated (or triggered) by the base station. For example, the wireless device may perform the semi-persistent CSI reporting on the PUSCH upon (or in response to) successful decoding of a DCI format 0 J or a DCI format 0_2 which activates a semi-persistent CSI trigger state. The DCI format 0_1 and the DCI format 0_2 may contain a CSI request field which may indicate the semi-persistent CSI trigger state to activate or deactivate. The CSI reporting on PUSCH (e.g., the semi-persistent CSI reporting on PUSCH) may be multiplexed with uplink data (from the wireless device) on PUSCH. For example, when the semi-persistent CSI reporting on PUSCH, activated by a DCI format, is not expected to be multiplexed with the uplink data on the PUSCH, the wireless device may not multiplex the semi-Docket No.: 25-1049PCTpersistent CSI reporting with the uplink data. In an example, the CSI reporting on PUSCH may be performed without any multiplexing with the uplink data on the PUSCH.

[0259] For example, the wireless device may perform the semi-persistent CSI reporting (e.g., report the semi-persistent CSI) based on a command received from the base station. For example, for semi-persistent reporting on PUSCH, a set of trigger states maybe configured (e.g., by CSI-SemiPersistentOnPUSCH-TriggerStateListvia the one or more CSI configuration parameters), where the CSI request field in the DCI scrambled with SP-CSI-RNTI activates one of the trigger states.

[0260] In an example, the wireless device may perform the semi-persistent CSI reporting on PUCCH in response to the semi-persistent CSI reporting being activated (or triggered) by a MAC CE (e.g., SP CSI reporting on PUCCH activation MAC CE). For semi-persistent reporting on PUCCH, the PUCCH resource used for transmitting a CSI report may be configured by reportConfigType. The wireless device may perform the semi-persistent CSI reporting on PUCCH applied starting from the first slot after transmitting a HARQ-ACK information corresponding to a PDSCH carrying the SP CSI reporting on PUCCH activation MAC CE command. For example, the semi-persistent CSI reporting on PUCCH may support Type I CSI. In an example, the semi-persistent CSI reporting on PUCCH format 2 may support Type I CSI with wideband frequency granularity. In an example, the semi-persistent CSI reporting on PUCCH formats 3 or 4 may support Type I CSI with wideband and sub-band frequency granularities and Type II CSI Part 1.

[0261] For example, a report type (e.g., indicated by reportConfigType) of a CSI report may be periodic. A periodic CSI report, e.g., corresponding to a first CSI reporting setting (with a first report configuration identifier) of the one or more CSI reporting settings, may indicate a first list of PUCCH resources (configured / indicated by the one or more PUCCH-config(s)), e.g., indicated via pucch-CSI-ResourceList, for transmitting the periodic CSI report. The first list of PUCCH resources may correspond to at least one BWP of the one or more BWPs. A set of PUCCH resources indicated / configured by the one or more PUCCH-config(s) (across the one or more BWPs) for the one or more CSI reporting settings may comprise a first plurality of PUCCH resources indicated / configured by the one or more PUCCH-config(s) across the one or more BWPs. The first plurality of PUCCH resources may comprise all first list of PUCCH resources configured for the periodic CSI reports.

[0262] For example, a report type (e.g., indicated by reportConfigType) of a CSI report may be semi-persistent. An SP CSI report on PUCCH, e.g., corresponding to a second CSI reporting setting (with a second report configuration identifier) of the one or more CSI reporting settings, may correspond to a second list of PUCCH resources (configured / indicated by the one or more PUCCH-config(s)), e.g., indicated via pucch-CSI-ResourceList, for transmitting the SP CSI report on PUCCH. The second list of PUCCH resources may correspond to at least one BWP of the one or more BWPs. A set of PUCCH resources indicated / configured by the one or more PUCCH-config(s) (across the one or more BWPs) for the one or more CSI reporting settings may comprise a second plurality of PUCCH resources indicated / configured by the one or more PUCCH-config(s) across the one or more BWPs. The secondDocket No.: 25-1049PCTplurality of PUCCH resources may comprise all second list of PUCCH resources configured for the semi-persistent CSI reports.

[0263] The one or more configuration parameters (e.g., via BWP-DowniinkDedicated may comprise one or more semi-persistent scheduling (SPS) configuration parameters. For example, the one or more SPS configuration parameters may comprise one or more (e.g., 8) SPS configuration (SPS-Config) for PDSCH receptions with SPS (e.g., SPS PDSCH). A SPS configuration of the one or more SPS configurations may be a unicast SPS configuration or a multicast (or interchangeably broadcast / g roupcast) SPS configuration. The one or more SPS configuration may indicate one or more configured downlink assignments for SPS PDSCHs. The SPS configuration configures the wireless device for receiving DL SPS (e.g., SPS PDSCH) in downlink. The SPS configuration may comprise at least one of the following: SPS configuration I D / index; and / or a periodicity of the corresponding DL SPS; and / or a HARQ codebook ID indicating a HARQ-ACK codebook index for a corresponding HARQ-ACK codebook for SPS PDSCH and ACK for SPS PDSCH release; and / or a modulation and coding scheme (MCS) table (e.g., mcs-Tabte) corresponding to the DL SPS; a number of repetitions for the SPS PDSCH (e.g., pdsch-AggregationFacto and / or nrofHARQ-Processes indicating a number of HARQ processes for the DL SPS; and / or HARQ resource for PUCCH (e.g., n1PUCCH-AN). When the SPS configuration does not comprise / indicate the MCS table, the wireless device may use an MCS table provided / indicate via one or more PDSCH configuration parameters of the one or more configuration parameters (e.g., PDSCH-Config).

[0264] The one or more BWP configuration parameters may comprise parameters (e.g., PUSCH configuration, e.g., PUSCH-Config and / or PUSCH-ConfigCommon, and / or PUCCH configuration, e.g., PUCCH-config and / or PUCCH-configCommon) of a cell (of the one or more cells) and one or more BWPs associated with the cell.

[0265] The one or more BWP configuration parameters may configure / indicate UL / DL configuration parameters (e.g., PUSCH configuration, e.g., PUSCH-Config and / or PUSCH-ConfigCommon, and / or PUCCH configuration, e.g., PUCCH-config and / or PUCCH-configCommon) for each BWP of the one or more BWPs.

[0266] The one or more configuration parameters may comprise one or more PUCCH configuration parameters (e.g., PUCCH-config and / or PUCCH-configCommon) For example, the one or more PUCCH configuration parameters comprise one or more PUCCH-config(s) and / or one or more PUCCH-configCommon(s). Each PUCCH-config of the one or more PUCCH-config(s) may correspond to / be associated with each BWP of the one or more BWPs (e.g., for transmit PUCCHs via the BWP). Each PUCCH-configCommon of the one or more PUCCH-configCommon (s) may correspond to / be associated with each BWP of the one or more BWPs (e.g., for transmit PUCCHs via the BWP). Each PUCCH-config of the one or more PUCCH-config(s) may indicate / configure a maximum code rate (e.g., maxCodeRate) for determining hot to feedback UCI on PUCCH for format 2 or format 3 or format 4.

[0267] Each PUCCH-config of the one or more PUCCH-config(s) may indicate / configure a plurality of PUCCH resources (e.g., indicated / provided by resourceToAddModList and / or resourceSetToAddModList), each with corresponding PUCCH resource index pucch-Resoruceld; and / or a starting PRB (startingPRB) indicating an index of a first PRB (e.g., a PRB ID withing a carrier), e.g., before frequency hopping; and / or a configuration of a PUCCH formatDocket No.: 25-1049PCT(format); and / or a number of PRBs nrofPRBs (corresponding to the PUCCH format) of the PUCCH resource, e.g., M / CCHand / or a number of symbols nrofSymbols (corresponding to the PUCCH format) of the PUCCH resourceNsymb-uci'< and / orastarting symbol for the PUCCH resource in an slot (e.g., startingSymbollndex). The number of PRBs may be integer values 1,2,3,4,5,6,8,9,10,12,15 and 16.

[0268] The PUCCH format of a PUCCH resource (of the plurality of PUCCH resources) may be a PUCCH format 0 (formatO).

[0269] The PUCCH format of a PUCCH resource (of the plurality of PUCCH resources) may be a PUCCH format 1 (format!).

[0270] The PUCCH format of a PUCCH resource (of the plurality of PUCCH resources) may be a PUCCH format 2 (format2).

[0271] The PUCCH format of a PUCCH resource (of the plurality of PUCCH resources) may be a PUCCH format 3 (formats).

[0272] The PUCCH format of a PUCCH resource (of the plurality of PUCCH resources) may be a PUCCH format 4 (format4).

[0273] The one or more configuration parameters may comprise one or more PUSCH configuration parameters (e.g., PUSCH-config and / or PUSCH-configCommon). For example, the one or more PUSCH configuration parameters comprise one or more PUSCH-config(s) and / or one or more PUSCH-configCommon(s). Each PUSCH-config of the one or more PUSCH-config(s) may correspond to / be associated with each BWP of the one or more BWPs (e.g., for transmit PUSCHs via the BWP). Each PUSCH-configCommon of the one or more PUSCH-configCommon (s) may correspond to / be associated with each BWP of the one or more BWPs (e.g., for transmit PUSCHs via the BWP).

[0274] The one or more PUCCH configuration parameters may comprise one or more SR resource configuration parameters The one or more SR resource configuration parameters may configure / indicate a list of SR resource configurations. The list (ora plurality) of SR resource configurations may comprise a first number (e.g., maxNrofSR-Resources) of SR resource configurations (e.g., SchedulingRequestResourceConfig). The one or more SR resource configuration parameters may indicate (PHY layer) PUCCH resources (for sending / transmitting SRs) corresponding to the first number of SR resource configurations (e.g., SchedulingRequestResourceConfig). Each SR resource configuration of the first number of SR resource configurations may have an associated SR resource ID / identifier / number (e.g., schedulingRequestResourceld). The first number (e.g., maxNrofSR-Resources) may be 1 or 2 or 3 or ... or 8 or the like. The first number may be 0.

[0275] For example, a PUCCH-config (corresponding to a BWP of the one or more BWPs) of the one or more PUCCH-config(s) (e.g., configured / indicated by a BWP of the one or more BWPs) may correspond to (or indicate or be associated with) the list of SR resource configurations (e.g., schedulingRequestResourceToAddModList).Docket No.: 25-1049PCT

[0276] In another example, a PUCCH-config (corresponding to a second BWP of the one or more BWPs) of the one or more PUCCH-config(s) may correspond to (or indicate or be associated with) at least one SR resource configuration of the list of SR resource configurations.

[0277] In yet another example, a PUCCH-config (corresponding to a third BWP of the one or more BWPs) of the one or more PUCCH-config(s) may correspond to (or indicate or be associated with) to no SR resource configuration of the list of SR resource configurations.

[0278] Each SR resource configuration (of the first number of SR resource configurations) may comprise / indicate corresponding PUCCH resource with a PUCCH resource ID / identifier / indicator (e.g., PUCCH-Resourceld) for transmitting / sending SR(s) corresponding to the SR resource configuration. An SR resource configuration (of the first number of SR resource configurations) may comprise / indicate at least one of the following: a corresponding SR resource ID / identifier / number (e.g., schedulingRequestResourceld)] and / or a corresponding / associated SR configuration (e.g., schedulingRequestld) that uses the SR resource configuration for corresponding triggered / pending S Rs; and / or periodicity and offset of SR (e.g., periodicityAndOffset); and / or physical layer priority of the SR (e.g., phy-Prioritylndex).

[0279] The physical layer priority of the SR (associated with an SR resource configuration) may be a priority index 0 or a priority index 1. If an SR resource configuration (of the first number of SR resource configurations) does not indicate physical layer priority of the SR (associated with an SR resource configuration), e.g., the phy-Prioritylndex is absent from the corresponding SchedulingRequestResourceConfig, the wireless device may determine the priority index for SR to be a first value (eg., 0 or 1).

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

[0281] On an inactive (or deactivated or dormant) BWP of the cell (or for each activated serving cell configured with a BWP), the wireless device may perform at least one of the following: not transmit on UL-SCH; not transmit on RACH; not monitor a PDCCH; not transmit PUCCH; not transmits RS, not receive DL-SCH; clear any configured downlink assignment (e.g., configured / indicated by an SPS-config of the one or more configuration parameters) and the configured uplink grant of configured grant Type 2; and / or suspend any configured uplink grant of configured Type 1.Docket No.: 25-1049PCT

[0282] In the uplink, two schemes for transmission without a dynamic grant may be supported. The two schemes may differ in the way they are activated: 1 ) configured grant type 1 (or Type 1 configured grant), where an uplink grant is provided by the CG-Config of the one or more configuration parameters, 2) configured grant type 2 (or Type 2 configured grant), where the transmission periodicity is provided by the CG-Config of the one or more configuration parameters and L1 / L2 control signaling is used to activate / deactivate the transmission.

[0283] For example, the one or more configuration parameters (e.g. , one or more BWP configurations) may configu re / indicate / provide a list of CG configurations (e.g., a list of CG-Config or a list of ConfiguredGrantConfig). Each CG configuration of the list of CG configurations may be a Type 1 CG configuration (providing / indicating a configured grant type 1) or a Type 2 CG configuration (providing / indicating a configured grant type 2). A number of CG configurations in the list of CG configurations maybe 1 or 2 or 3 or .. or 12.

[0284] A DCI addressed to an RNTI may comprise a CRC of the DCI being scrambled with the RNTI. For detecting / receiving the DCI, the wireless device may monitor one or more PDCCH candidates (or monitoring occasions) for receiving / detecting a PDCCH addressed to (or for) the RNTI. For example, the PDCCH may carry (or be with) the DCI, e.g., the DCI is transported by the PDCCH.

[0285] The one or more configuration parameters (e.g., BWP-DownlinkDedicated) may comprise one or more PDCCH configuration parameters (e.g., PDCCH-Config) for configuring / indicating a set of PDCCH candidates for the wireless device to monitor via / in terms of one or more search space sets. For example, the one or more PDCCH configuration parameters may configure / indicate the one or more search space sets. The one or more PDCCH configuration parameters may comprise at least PDCCH-ConfigCommon and / or pdcch-ConfigSIB1 and / or PDCCH-Config.

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

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

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

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

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

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

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

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

[0294] The one or more configuration parameters may configure / indicate one or more logical channel (LCH) configuration parameters (e.g., LogicalChannelConfig) for logical channel prioritization (LCP) procedure. The one or more logical channel configuration parameters may configure / indicate a plurality of logical channels (e.g., in MAC layer). Each logical channel of the plurality of logical channels may have a unique LCH identity / identifier / ID. The one or more logical channel configuration parameters may configure / indicate mapping restrictions (e.g., LCP restriction) for a logical channel of the plurality of logical channels via at least one of the following parameters: allowedSCS-List which sets the allowed Subcarrier Spacing(s) for (PUSCH) transmission of data of the logical channel; and / or maxPUSCH-Duration which sets the maximum PUSCH duration allowed for (PUSCH) transmission of data of the logical channel; and / or con figuredGrantTypel Allowed which sets whether a configured grant Type 1 (e.g., Type 1 configured grant) can be used for (PUSCH) transmission of data of the logical channel; and / or allowedServingCells which sets the allowed cell(s) (e.g., of the one or more cells) for (PUSCH) transmission of data of the logical channel; and / or allowedCG-List which sets the allowed configured grant(s) for (PUSCH) transmission of data of the logical channel; and / or allowedPHY-Prioritylndex which sets the allowed PHY priority index(es) of a dynamic grant for (PUSCH) transmission of data of the logical channel; and / or allowedHARQ-mode which sets the allowed UL HARQ mode for (PUSCH) transmission of data of the logical channel. For each UL grant (e.g., either dynamic UL grant or CG UL grant), the wireless device may select one or more logical channels (with pending data) of the plurality of logical channels based on the LCP restriction of each logical channel (of the plurality of logical channels).

[0295] The a / lowedCG-List corresponding to a logical channel (of the plurality of logical channels) may indicate a second list of CG configurations (of the list of CG configurations) that UL MAC SDUs from the logical channel are allowed to mapped to (by the wireless device) for the CG PUSCH transmission. If the size of allowedCG-List corresponding to the logical channel is zero, the UL MAC SDUs from the logical channel are notallowed to mapped toDocket No.: 25-1049PCT(by the wireless device) for the CG PUSCH transmission (e.g., only dynamic grant PUSCH transmission can be used for transmitting the UL MAC SDUs from the logical channel). If configuredGrantTypel Allowed corresponding to the logical channel is also configured / indicated, only CG configuration of the second list of CG configurations that are Type 1 CG configuration (e.g., configured grant Type 1) are allowed to be used for mapping the UL MAC SDUs from the logical channel for the PUSCH transmission. If configuredGrantTypelAllowed corresponding to the logical channel is also configured / indicated, any CG configuration of the second list of CG configurations that are Type 2 CG configuration (e.g., configured grant Type 2) are not allowed to be used for mapping the UL MAC SDUs from the logical channel for the PUSCH transmission. For example, a number of CG configurations in the second list of CG configurations maybe 1 or 2 or....

[0296] For example, the one or more configuration parameters (e.g., MAC-CellGroupConfig) may be used to configure MAC parameters for a cell group (e.g., MCG or SCG). The MAC parameters (of the cell group) may comprise one or more DRX configuration parameters (e.g., DRX-Config and / or drx-ConfigSecondaryGroup ; one or more SR configuration parameters; and / or one or more PHR configuration parameters; one or more BSR configuration parameters.

[0297] The one or more SR configuration parameters (e.g., schedulingRequestConfig) may configure / indicate a plurality of SR configurations. The cardinality / number of SR configurations of the plurality of SR configurations may be 1 or 2 or more (e.g., less than 8 or 10 or the like). Each SR configuration of the plurality of SR configurations may have a unique SR ID / identifier / identity (e.g., schedulingRequestld). Each SR configuration of the plurality of SR configurations with corresponding SR ID (e.g , schedulingRequestld) may be associated with an SR resource configuration (of the list of SR resource configurations) with corresponding SR resource ID / identifier / number (e.g., schedulingRequestResourceld). Each SR configuration of the plurality of SR configurations may indicate at least one the following: a SR prohibit timer (e.g., sr_ProhibitTimer) corresponding to the SR configuration; and / or a maximum number of SR transmission (e.g., sr_TransMax) corresponding to the SR configuration. The SR prohibit timer may be a duration during which the wireless device may be not allowed to transmit the SR corresponding to the SR configuration. In an example, the wireless device may be in an (DRX) active state while sr_ProhibitTimer is running and / or may monitor PDCCH for detecting DCI (e.g., indicating uplink scheduling grants).

[0298] At least one first SR configuration (e.g., with / corresponding to a first set of SR IDs) of the plurality of SR configurations may correspond to one or more LCHs of the plurality of logical channels. For example, when at least one LOGICAL CHANNEL of the one or more logical channels are with pending data (e.g., when BSRs associated with at least one logical channel of the one or more logical channels is triggered / pending), the wireless device may trigger an SR corresponding to the at least one first SR configuration. Each logical channel may be mapped to zero or one SR configuration configured by the one or more logical channel configuration parameters. A SR configuration of a logical channel (LCH) of the plurality of logical channels that triggers a buffer status report (BSR) may be considered as a corresponding SR configuration for a triggered SR for SBR.Docket No.: 25-1049PCT

[0299] The at least one first SR configuration may further be associated with Positioning Measurement Gap Activation / Deactivation Request (e.g., when the MAC-CellGroupConfig indicates / configures schedulingRequestlD-PosMG-Request). The wireless device may trigger / send an SR corresponding to the at least one first SR configuration in response to an activation / deactivation of the Positioning Measurement Gap Activation / Deactivation Request.

[0300] The at least one first SR configuration may correspond to a first set of SR resource configurations (e.g., associated with a first set of SR resource IDs) of the list one SR resource configurations. Transmitting an SR corresponding to an SR configuration (e.g., with an SR ID) of the at least one first SR configuration may be via a PUCCH resource indicated by an SR resource configuration (with an SR resource ID associated with the SR ID) of the first set of SR resource configurations. The PUCCH resource indicated by the SR resource configuration may be an SR transmission occasion of the SR corresponding to the SR configuration

[0301] A second SR configuration (with an SR ID indicated by schedulingRequestID-BFR-SCell in the MAC-CellGroupConfig, e.g., a fourth SchedulingRequestConfig) of the plurality of SR configurations may configure the wireless device to trigger / send an SR (corresponding to the second SR configuration) upon detecting a third beam failure on an SCell (of the one or more cells). The second SR configuration may correspond to a second SR resource configuration (e.g., associated with a second SR resource ID) of the list one SR resource configurations. Transmitting an SR corresponding to the second SR configuration may be via a PUCCH resource indicated by the second SR resource configuration. The PUCCH resource indicated by the second SR resource configuration may be an SR transmission occasion of the SR corresponding to the second SR configuration.

[0302] A third SR configuration (with an SR ID indicated by schedulingRequestID-BFR in the MAC-CellGroupConfig, e.g., a third SchedulingRequestConfig) of the plurality of SR configurations may configure the wireless device to trigger / send an SR (corresponding to the third SR configuration) upon detecting a first beam failure of a serving cell (of the one or more cells), e.g., not the SCell. Detecting the first beam failure may correspond to a failureDetectionSetl of the serving cell while beam failure is not detected on resources configured in failureDetectionSet2 of the same serving cell. Transmitting an SR corresponding to the third SR configuration may be via a PUCCH resource indicated by the third SR resource configuration. The PUCCH resource indicated by the third SR resource configuration may be an SR transmission occasion of the SR corresponding to the third SR configuration.

[0303] A fourth SR configuration (with an SR ID indicated by schedulingRequestlD-BFR2 in the MAC-CellGroupConfig, e.g , a fourth SchedulingRequestConfig) of the plurality of SR configurations may configure the wireless device to trigger / send an SR (corresponding to the fourth SR configuration) upon detecting a second beam failure of the serving cell. Detecting the second beam failure may correspond to the failureDetectionSet2 of the serving cell while beam failure is not detected on resources configured in the failureDetectionSetl of the same serving cell. Transmitting an SR corresponding to the fourth SR configuration may be via a PUCCH resource indicated by the fourth SR resource configuration. The PUCCH resource indicated by the fourth SR resource configuration may be an SR transmission occasion of the SR corresponding to the fourth SR configuration.Docket No.: 25-1049PCT

[0304] A fifth SR configuration (with an SR ID indicated by schedulingRequestlD-LBT-SCell in the MAC-CellGroupConfig, e.g., a fifth SchedulingRequestConfig) of the plurality of SR configurations may configure the wireless device to trigger / send an SR (corresponding to the fifth SR configuration) upon detecting a consistent uplink LBT recovery on a SCell of the one or more cells. Transmitting an SR corresponding to the fifth SR configuration may be via a PUCCH resource indicated by the fifth SR resource configuration. The PUCCH resource indicated by the fifth SR resource configuration may be an SR transmission occasion of the SR corresponding to the fifth SR configuration.

[0305] FIG. 17 shows an example of scheduling request procedure. The SRprocedure shown in FIG. 17 may be for transmitting SR, e.g., for requesting UL grants, by the wireless device. The SR procedure shown in FIG. 17 may provide an example of UL scheduling request or transmission per some aspects of some embodiments in the present disclosure. Although not shown in FIG. 17, the wireless device may receive the one or more configuration parameters, e.g., from the base station. The one or more configuration parameters may comprise the one or more SR configuration parameters.

[0306] As shown in FIG. 17, the wireless device may trigger an SR (e.g., corresponding to an SR configuration of the plurality of SR configurations) 1700. Triggering the SR maybe duetopending BSR (e.g., in response to data becoming available for at least one LOGICAL CHANNEL, e.g., associated with the SR configuration) or a triggered BFR in the serving cell / SCell and / or consistent LBT failure or the like. The SR configuration (for the triggered SR) may be an SR of the at least one first SR configuration. The SR configuration (for the triggered SR) may be the second SR configuration. The SR configuration (for the triggered SR) may be the third SR configuration. The SR configuration (for the triggered SR) may be the fourth SR configuration. The SR configuration (for the triggered SR) may be the fifth SR configuration. Other examples that result in triggering the SR are possible although not discussed here. In the present disclosure, the SR may be also referred to as “resource request” or “scheduling indication” or the like.

[0307] The triggered SR is for requesting UL-SCH resource(s) for one or more UL transmissions. When the SR is triggered, the wireless device may consider the SR pending until it is cancelled. In an example, when one or more UL grants accommodate all pending data available for transmission, the wireless device may cancel the pending SRs (eg., including the SR).

[0308] As part of the SR procedure and as shown in FIG. 17, for the triggered / pending SR, the wireless device may set an SR counter (e.g., SR_COUNTER) 1700 of the SR configuration to a first value (e.g., 0). Setting the SR counter may comprise initializing the SR counter by the first value. For example, when there are no other SRs pending corresponding to the same SR configuration, the first value is 0. When there is at least one other SR pending / triggered (or not cancelled) corresponding to the same SR configuration, the first value may be equal to the SR_COUNTER of the SR configuration. In an example, during the SR procedure, the wireless device may maintain the SR counter (e.g., SR_COUNTER), e.g., SR transmission counter, associated with the SR configuration for counting a number of times that the SR being transmitted / retransmitted.Docket No.: 25-1049PCT

[0309] As part of the SR procedure and as shown in FIG. 17, the wireless device may determine whether there is a valid PUCCH resource for the triggered / pending SR 1702. The valid PUCCH resource (e.g., at the time of SR transmission occasion) maybe a PUCCH resource (with corresponding PUCCH resource ID, e.g., PUCCH-Resourceld) of an SR resource configuration (of the list of SR resource configurations) associated with the SR configuration. For example, when the SR configuration is one of the at least one first SR configuration, the PUCCH resource may be indicated by one of the first set of SR resource configurations. In another example, when the SR configuration is the second SR configuration, the PUCCH resource may be indicated by the second SR resource configuration. In another example, when the SR configuration is the third SR configuration, the PUCCH resource may be indicated by the third SR resource configuration. In yet another example, when the SR configuration is the fourth SR configuration, the PUCCH resource may be indicated by the fourth SR resource configuration. In yet another example, when the SR configuration is the fifth SR configuration, the PUCCH resource may be indicated by the fifth SR resource configuration.

[0310] The PUCCH resource is valid (for transmitting the SR) if the PUCCH resource (indicated / provided by a PUCCH-Config of the one or more PUSCH-config(s)) being associated with the active BWP of the one or more BWPs at the time of SR transmission occasion. The PUCCH resource is invalid (or is not valid) if the PUCCH resource (indicated / provided by the PUCCH-Config of the one or more PUSCH-config(s)) is not associated with the active BWP of the one or more BWPs at the time of SR transmission occasion.

[0311] As part of the SR procedure and as shown in FIG. 17, based on determining that there is no valid PUCCH resource for the pending / triggered SR (e.g , for transmitting the SR), the wireless device may initiate / trigger a random access (RA) procedure (e.g., on a PCell, ora PSCell and as discussed above in connection with FIG. 13A.FIG. 13B, and / or FIG. 13C) and / or cancel the pending SR.

[0312] As part of the SR procedure and as shown in FIG. 17, based on determining that there is valid PUCCH resource for the pending / triggered SR (e.g., for transmitting the SR), the wireless device 1703 may determine whether a SR prohibit time (sr-ProhibitTimer) corresponding to the SR configuration is running or not. Based on the SR prohibit time (sr-ProhibitTimef} corresponding to the SR configuration not being running, the wireless device may further determine 1704 whether the SR counter (corresponding to the SR configuration) is less than the maximum number of SR transmission (e.g., sr_TransMax) corresponding to the SR configuration or not, e.g., whether SR_COUNTER<sr_TransMax. When the SR_COUNTER>sr_TransMax, the wireless device may determine the SR (corresponding to the SR configuration) is failed. When the SR_COUNTER>sr_TransMax, the wireless device may determine the SR (corresponding to the SR configuration) is not failed.

[0313] As part of the SR procedure and as shown in FIG. 17, based on determining that the SR failed (e.g., SR_COUNTER>sr_TransMax) 1710, the wireless device may perform / execute / conduct a first set of actions. The first set of actions may comprise / be: notifying higher layers (RRC layer) of the wireless device to release PUCCH for all serving cells (e.g., the one or more cells); notifying higher layers (RRC layer) of the wireless device to release SRS forDocket No.: 25-1049PCTall serving cells (e.g., the one or more cells); clearing any configured downlink assignments (e.g., the one or more configured downlink assignments configured / indicated by the at least one SPS configuration) and uplink grants (e.g., configured uplink grants configured / indicated by the list of CG configurations); clearing any PUSCH resources for semi-persistent CSI reporting; and initiating a random access procedure on a PCell and canceling all the pending SRs.

[0314] As part of the SR procedure and as shown in FIG. 17, releasing PUCCH for all serving cells in step 1710 may comprise releasing / deleting / discarding / deactivating all PUCCH resources indicated by the list of SR resource configurations, e.g., a PUCCH-Config of the one or more PUSCH-config(s) or in the one or more PUCCH-Config(s). By releasing PUCCH for all serving cells (in response to the SR being failed), the wireless device may stop / halt / deactivate transmitting SRs (via all the serving cells).

[0315] As part of the SR procedure and as shown in FIG. 17, releasing PUCCH for all serving cells in step 1710 may comprise releasing / deleti ng / deactivating all PUCCH-CSI-Resources configured by CSI-ReportConfig. For example, releasing PUCCH for all serving cells in step 1710 may comprise releasing / deleting / discarding / deactivating the first plurality of PUCCH resources (indicated / configured by the one or more PUCCH-config(s) across the one or more BWPs) for periodic CSI reports on PUCCH. For example, releasing PUCCH for all serving cells in step 1710 may comprise releasing / deleting / deactivating the second plurality of PUCCH resources (indicated / configured by the one or more PUCCH-config(s) across the one or more BWPs) for SP CSI reports on PUCCH. By releasing PUCCH for all serving cells (in response to the SR being failed), the wireless device may stop / halt / deactivate transmitting periodic / SP CSI reports on PUCCH (via all the serving cells).

[0316] As part of the SR procedure and as shown in FIG. 17, releasing SRS for all serving cells in step 1710 may comprise releasing / deleting / deactivating SRS-Resource instances configured in SRS-Config. For example, releasing SRS for all serving cells in step 1710 may comprise releasing / deleting / discarding / deactivating the list of SRS resources (SRS-Resoruces). For example, releasing SRS for all serving cells in step 1710 may comprise releasing / deleting / deactivating all SRS resources indicated / defined by the list of SRS resource set (e.g., SRS-ResourceSets). By releasing SRS for all serving cells (in response to the SR being failed), the wireless device may stop / halt / deactivate transmitting SRSs (via all the serving cells).

[0317] As part of the SR procedure and as shown in FIG. 17, clearing any configured downlink assignments and uplink grants in step 1710 may comprise clearing / deleting / discarding / deactivating the one or more configured downlink assignments configured / indicated by the at least one SPS configuration and the configured uplink grants configured / indicated by the list of CG configurations. By clearing any configured downlink assignments (in response to the SR being failed), the wireless device may stop / halt / deactivate receiving the SPS PDSCHs using the one or more configured downlink assignments. By clearing any uplink grants (in response to the SR being failed), the wireless device may stop / halt / deactivate transmitting CG Typel / Type 2 PUSCHs using the configured uplink grants.

[0318] As part of the SR procedure and as shown in FIG. 17, clearing any PUSCH resources for semi-persistent CSI reporting in step 1710 may comprise clearing / deleting / discarding / deactivating PUSCH resources (configured by the oneDocket No.: 25-1049PCTor more CSI configuration parameters via sem / PersistentOnPUSCH) for one or more semi-persistent (SP) CSI reports on PUSCH. By clearing any PUSCH resources for semi-persistent CSI reporting (in response to the SR being failed), the wireless device may stop / halt / deactivate transmitting the SP CSI reports on PUSCH.

[0319] As part of the SR procedure and as shown in FIG. 17, based on determining that the SR is not failed (e.g., SR_COUNTER<sr_TransMax) 1705, the wireless device may perform / execute / conduct a second set of actions. The second set of actions may comprise / be: incrementing (increasing by one) the SR counter corresponding to the SR configuration; and / or transmitting the SR (via the valid PUCCH resource corresponding to the SR configuration); and / or starting the SR prohibit timer corresponding to the SR configuration. While the SR prohibit timer corresponding to the SR configuration is running, the wireless device may receive UL grant(s) 1706, e.g., based on monitored PDCCH. The second set of actions may further comprise instructing (by the MAC layer of the wireless device) the physical layer of the wireless device to signal / transmit the SR (on the SR transmission occasion) on the at least one valid PUCCH resource for the SR configuration.

[0320] As part of the SR procedure and as shown in FIG. 17, in response to the received UL grants 1706 and / or based on determining that the SR prohibit timer the SR configuration is running (is not stopped) 1703, the wireless device may determine whether there are sufficient / available UL resources (UL-SCH resources) for transmitting pending data 1707. If the available UL resources are sufficient (e.g., accommodate) all pending data for transmission, the wireless device may stop the SSR prohibit timer corresponding to the SR configuration; and / or cancel the SR corresponding to the SR configuration 1708. The wireless device may cancel all pending SR(s) for BSR triggered before a MAC PDU assembly of the pending data and / or stop each respective sr-ProhibitTimer in response to the MAC PDU being transmitted. In an example, the wireless device may cancel all pending SR(s) for BSR triggered according to the BSR procedure and stop each respective sr-ProhibitTimer by determining that the UL grant(s) accommodating all pending data available for transmission.

[0321] As part of the SR procedure and as shown in FIG. 17 in step 1707, based on the UL resources (UL-SCH resources) for transmitting pending data not being sufficient / available, the wireless device may repeat the SR procedure from step 1701.

[0322] For transmitting the SR (as part of the SR procedure) and when there is the valid PUCCH resource for the pending SR, the wireless device may determine the SR transmission occasion (not overlapping with measurement gap) corresponding to the PUCCH resource (e.g., the valid PUCCH resource) based on the periodicityAndOffset (a periodicity e.g., SRPERIODICITY in number of symbols and / or slots, and an offset SROFFSETin slots) of the corresponding SR resource configuration of the SR configuration. Based on determining that the SRPERIODICITYbeing larger than one slot, the wireless device may determine the SR transmission occasion in the PUCCH to be in a slot with number in a frame with number rtf if (nf■ N^e'^ + - SROFFSET^ mod SRPERIODICITY= 0, whereis a number of slots in a frame when numerology is configured. Based on determining that SRPERIODICITYbeing one slot, the wireless device may expect that SROFFSETbe zero, and each slot may be considered as the SRDocket No.: 25-1049PCTtransmission occasion. Based on determining that the SRPERIODICITYis smaller than one slot, the wireless device may determine the SR transmission occasion in the PUCCH to be started in a symbol (in each slot) with index I where (7 - l0mod SRpER]0D]CITY') mod SRPER10DICITY= 0, where l0is the value of startingSymbollndex of the SR resource configuration.

[0323] FIG. 18 shows an example of uplink control channel (UCI) transmission procedure. In some aspects, the UCI transmission procedure shown in FIG. 18 may show an example of SR multiplexing on PUCCH resource. For example, the UCI transmission procedure may comprise determining a number of UCI bits to be included in a transmission of a PUCCH. For example, the UCI transmission procedure may comprise determining a number of SR bits to be included in the transmission of the PUCCH.

[0324] The UCI transmission in FIG. 18 may be for transmitting at least one SR (e.g., K SRs in FIG. 18) of the plurality of SRs in a slot (also referred to by a first slot in this disclosure) and / or O_U Cl HARQ information bits and / or O_CSI CSI report bits. Each SR of the K SRs may be a positive SR (e.g., when the SR is triggered) ora negative SR (e.g., when the SR is not triggered). The first slot may comprise only UL / flexible symbols (e.g., UL / flexible slot).

[0325] The plurality of SRs may correspond to the plurality of SR configurations. Each SR of the plurality of SRs with corresponding PUCCH resource being in the slot may be part of the at least one SR in FIG. 18. Transmitting the at least one SR in the slot may be part of the SR procedure discussed above in FIG. 17. In example of FIG. 18, K is equal the number of SR configurations (of the plurality of SR configurations) that the corresponding PUCCH resource (configured with the corresponding SR resource configuration) is in the slot. When no SR configuration of the plurality of SR configurations has a PUCCH resource (configured with the corresponding SR resource configuration) in the slot, K=0.

[0326] As shown in FIG. 18, each SR of the K SRs may have a corresponding SR transmission occasion (e.g., corresponding PUCCH resource) in the slot. As shown the SR transmission occasions for transmitting K SRs overlap (in time domain) with a PUCCH resource for transmitting Q_UC I bits. An PUCCH of the K PUCCHs is associated with a SR configuration (of the plurality of SR configuration) with corresponding schedulingRequestld that is associated with the SR resource configuration (with corresponding schedulingRequestResourceld) comprising the PUCCH resource.

[0327] The slot in FIG. 18 may be a slot configured / indicated for transmitting HARQ-ACK information bits and / or CSI report on PUCCH.

[0328] Q_ _UC I bits may comprise O_ACK bits for transmitting HARQ-ACK information. For example, a DCI may indicate a HARQ-ACK timing K1 (e.g., via a field PDSCHdo-HARQJeedback timing indicator of the DCI). The wireless device may, based on the HARQ-ACK timing K1 and a PUCCH resource indication of the DCI, determine a PUCCH (transmission occasion and / or resource) for transmitting the HARQ-ACK information (orbits). The HARA information may be also referred to by HARQ-ACK feedback. The HARQ-ACK information may correspond to PDSCHs (e.g., scheduled by the DCI).Docket No.: 25-1049PCT

[0329] For example, when the wireless device successfully / correctly receives the PDSCH / TB (e.g , successfully / correctly decodes the TB indicated by the PDSCH), the HARQ-ACK information may comprise a positive value (e.g., acknowledgment, e.g., ACK). Alternatively, when the wireless device unsuccessfully / incorrectly receives the PDSCH / TB (e.g., unsuccessfully / incorrectly decodes the TB indicated by the PDSCH), the HARQ-ACK information may comprise a positive value (e.g., acknowledgment, e.g., ACK).

[0330] The Q_UC I bits may (further) comprise O_UC I bits for transmitting CSI report(s).

[0331] As shown in FIG. 18, K PUCCHs for respective K SRs overlap (in time domain, e.g., in at least one symbol of the slot) with the PUCCH resource for transmitting HARQ-ACK information bits and / or CSI report on PUCCH. The HARQ-ACK information bits may correspond to / or be associated with PDSCHs (e.g., SPS PDSCHs and / or dynamically scheduled PDSCHs, e.g., by DCI formats).

[0332] The PUCCH resource may be for transmission of a first PUCCH with HARQ-ACK information in the slot, e.g., for transmitting the O_HARQ information bits. The first PUCCH may be a resource corresponding to a PUCCH format 2 or a PUCCH format 3 or a PUCCH format 4.

[0333] The PUCCH resource may be for transmission of a second PUCCH with CSI report(s) in the slot, e.g., for transmitting O_C S I bits. The second PUCCH resource may be a PUCCH resource of the first plurality of PUCCH resources (for periodic CSI reports) or a PUCCH resource of the second plurality of PUCCH resources (for SP CSI reports on PUCCH). The second PUCCH may be a resource corresponding to a PUCCH format 2 or a PUCCH format 3 or a PUCCH format 4.

[0334] Based on the UCI transmission procedure, the wireless device may append / include / multiplex / add OSR= log2(K + 1)] bits in the PUCCH assigned / indicated / configured for the transmission of the Q_UCI bits. For example, the wireless device may multiplex OUCI= Qua+ [log2( + / )] bits in the PUCCH. OSR= [log2( + 1)] bits may represent the negative or positive SRs of the K SRs. An all-zero value for the log2(K + 1)] bits may represent a negative SR value across all K SRs (e.g., no SR of the K SRs is triggered in the slot). The wireless device may transmit the PUCCH comprising / carrying OUCI= Qucl+ log2(K + 1)] bits in the slot. The wireless device in FIG.18 may not transmit the K PUCCHs in the slot.

[0335] Based on the UCI transmission procedure, the wireless device may order the K SRs in ascending order of the values of: schedulingRequestResource / d (e.g., the first set of SR resource IDs of the first set of SR resource configurations and corresponding to the at least one first SR configuration) with corresponding PUCCH resource in the slot; and the second SR resource ID (e.g., schedulingRequestResource / d associated with schedulingRequest / D-BFR-SCell) with the corresponding PUCCH resource in the slot; and the third SR resource ID (e.g., schedulingRequestResource / d associated with schedulingRequestlD-BFR] and the fourth SR resource ID (e.g., schedulingRequestResource / d associated with schedulingRequestlD-BFR2 with the corresponding PUCCH resource in the slot; and the fifth SR resource ID (e.g., schedulingRequestResource / d associated with schedulingRequestlD-LBT-SCell) with the corresponding PUCCH resource in the slot.Docket No.: 25-1049PCT

[0336] In some examples of the present disclosure, the one or more configuration parameters (e.g. , the one or more PUCCH configuration parameters) may indicate / comprise a first parameter (e.g., simultaneousHARQ-ACK-CSI) allowing / indicating / enabling multiplexing of various UCIs (e.g., the HARQ-ACK information and / or SRs and / or CSI reports and / or the like) in the PUCCH resource (e.g., the first PUCCH resource). The first PUCCH resource may overlap with the second PUCCH resource assigned / allocated for the CSI reports. When the one or more configuration parameters indicate / comprise the first parameter (e.g., the first parameter sets by the value of true), the wireless device uses simultaneous transmission of CSI reports and HARQ-ACK feedback (e.g., the HARQ-ACK information) with or without SR with the PUCCH resource (e.g., using PUCCH Format 2, 3 or 4). For example, the UCI transmission procedure discussed above in relation to FIG. 18 may be further based on the one or more configuration parameters indicating / comprising the first parameter (e.g., simultaneousHARQ-ACK-CSI). The first PUCCH resource may be indicated by a PUCCH resource indication field in a DCI scheduling a PDSCH reception.

[0337] Corresponding to the UCI transmission procedure discussed above in relation to FIG. 18, based on determining the one or more configuration parameters (e.g., the one or more PUCCH configuration parameters) not indicating / comprising the first parameter (e.g., the first parameter is absent or is not set by value true), the wireless device may drop the CSI report(s) and includes only HARQ-ACK information, with or without SR, in the PUCCH resource.

[0338] FIG. 19 shows an example of a CSI report procedure. The CSI report procedure may be for reporting multiple UCI types. The multiple UCI types may comprise CSI report(s); and / or HARQ-ACK information; and / or SR. For example, the UCI transmission procedure may be for reporting the multiple UCI types

[0339] In some respects, the UCI transmission procedure shown in FIG. 18 may further comprise the CSI report procedure shown in FIG. 19. In some examples, the UCI transmission procedure discussed in FIG. 18 may be combined with the CSI report procedure, e.g., to determine the second PUCCH resource for transmitting the CSI report, e.g., when multiple PUCCH resources (e.g., J) are configured in the slot for transmitting the CSI report(s). For example, the plurality of PUCCH resources may comprise the multiple PUCCH resources. The multiple PUCCH resources may comprise at least two PUCCH resources. As shown in FIG. 19, the multiple PUCCH resources may overlap in time domain with each other, e.g., in at least one symbol.

[0340] For example, the CSI report procedure may be for multiplexing at least two CSI reports (e.g., also referred to by multiple CSI reports) in a PUCCH resource when a PUCCH resource (of the multiple PUCCH resources) associated with each CSI report (of the at least two CSI reports) in the slot overlaps with each other. The CSI report #1 may be associated with a PUCCH resource #3 and the CSI report #2 may be associated with a PUCCH resource #4. For example, the one or more configuration parameters may configure / indicate the multiple PUCCH resources (e.g., the PUCCH resource #3 and a PUCCH resource #4) may be indicated / configured for the at least two CSI reports (CSI report #1 and a CSI report #2) in the slot. The first plurality of PUCCH resources and / or the second plurality of PUCCH resources may indicate / comprise the at least two PUCCH resources.Docket No.: 25-1049PCT

[0341] Although FIG. 19 shows an example for two PUCCH resources for the at least two CSI reports, embodiments readily applicable for the multiple PUCCH resources assigned / allocated / configu red for the multiple CSI reports.

[0342] In a first embodiment of FIG. 19 corresponding to the CSI report procedure, the one or more PUCCH configuration parameters (e.g., a PUCCH-Config of the one or more PUCCH-Configs), e.g., corresponding to a BWP of the one or more BWPs, may indicate / comprise a second parameter (e.g., multi-CSI-PUCCH-ResourceList). The second parameter may indicate J<2 PUCCH resource IDs of the multiple PUCCH resources. In the example of FIG. 19, the second parameter may indicate a first PUCCH resource ID (corresponding to PUCCH resource #3 of the multiple PUCCH resources) and a second PUCCH resource ID (corresponding to the PUCCH resource #4 of the multiple PUCCH resources).

[0343] According to the first embodiment of FIG. 19: in response to the one or more PUCCH configuration parameters indicating / comprising the second parameter, the wireless device may select a PUCCH resource among the multiple PUCCH resources in the slot based on at least one of the following: O_UC I bits for transmission in the slot; and / or a number of physical resource blocks (PRBs) assigned / allocated / configured (e.g., by the one or more PUCCH configuration parameters) for each PUCCH resource of the multiple PUCCH resources; and / or a number of PUCCH symbols assigned / allocated / configured (e.g., by the one or more PUCCH configuration parameters) for each PUCCH resource of the multiple PUCCH resources; and / or a code rate (e.g., maxCodeRate) indicated by the one or more PUCCH configuration parameters; and / or a modulation scheme for transmission of each PUCCH of the multiple PUCCHs. The selected PUCCH resource may be the second PUCCH resource in FIG. 18. The selected PUCCH resource may be a j-th PUCCH resource of the multiple PUCCH resources. The wireless device may transmit (e.g , according to the UCI transmission procedure) the O_UC I bits via the selected PUCCH resoruce.

[0344] The O_UC I bits may be based on Q_U Cl bits. The O_U Cl bits may be based on at least one of the following: a total number of HARQ-ACK information bits (O_ACK) for transmission in the slot; and / or a total number of SR bits for transmission in the slot; a total number of CSI report bits; and / or a number of CRC bits for encoding HARQ-ACK feedbacks, K SRs, CSI report(s). The CSI reports may comprise Part 1 CSI report(s). The CSI reports may comprise Part 2 CSI report(s).

[0345] In a second embodiment of FIG. 19 corresponding to the CSI report procedure, the one or more PUCCH configuration parameters (e.g., a PUCCH-Config of the one or more PUCCH-Configs), e.g., corresponding to a BWP of the one or more BWPs, may not indicate / comprise the second parameter (eg., multi-CSI-PUCCH-ResourceLisf). According to the second embodiment of FIG. 19, the second parameter is absent from the one or more PUCCH configuration parameters (e.g., a PUCCH-Config of the one or more PUCCH-Configs).

[0346] According to the second embodiment of FIG. 19: in response to the one or more PUCCH configuration parameters indicating / comprising the second parameter, the wireless device may select a PUCCH resource among the multiple PUCCH resources in the slot based on priority of CSI reports. A priority of CSI report (of the CSI reports) may be a priority value PriiCS1(y, k, c, s). Parameter y may be determined based on whether the CSI report is aperiodic orDocket No.: 25-1049PCTsemi-persistent or periodic. Parameter k may be based on quantity of the CSI report (e.g., L1-RSRPor L1-SINR). Parameter c may correspond to an index of the cell (e.g., serving cell index) corresponding to the CSI report.Parameter s may be a report configuration ID of the CSI report. A first CSI report may have a priority over a second CSI report (e.g., a priority of the first CSI report is higher / greater than a priority of the second CSI report) based on Priicsl(y, k, c, s') of the first CSI report being lower / smaller that PrilCSI(y, k, c, s) of the second CSI report.

[0347] According to the second embodiment of FIG. 19, the selected PUCCH resource may be the PUCCH resource #3 based on the CSI report #1 has higher priority than the CSI report #2. The wireless device may transmit (e.g., according to the UCI transmission procedure) the O_UC I bits via the selected PUCCH resource. The O_UC I bits may comprise the CSI report #1 , C ACK bits; and / or the SR bits.

[0348] According to the second embodiment of FIG. 19, the selected PUCCH resource may be the PUCCH resource #4 based on the CSI report #2 has higher priority than the CSI report #1. The wireless device may transmit (e.g., according to the UCI transmission procedure) the O_UC I bits via the selected PUCCH resource. The O_UC I bits may comprise the CSI report #2, O_ACK bits; and / or the SR bits.

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

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

[0351] For a serving cell (of the one or more serving cells), one or more common TDD configuration parameters may indicate / configure slot format(s) of a plurality of slots. FIG. 21 showsexamplesof slot format in a TDD carrier per an aspect of the present disclosure.

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

[0353] A first symbol / slot of the plurality of slots may be an Uplink (‘U7UL) symbol. An UL sy mbol / slot may be used by the wireless device for uplink transmission(s), e.g., via the serving cell. The one or more DL slots / symbols may comprise the first symbol / slot.Docket No.: 25-1049PCT

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

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

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

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

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

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

[0360] From Stslots (i=1 corresponding to the first TDD pattern or i=2 corresponding to the second TDD pattern), a first / initial / starti ng / earliest dsiotsslots may comprise the one or more DL slots / symbols. From Stslots, aDocket No.: 25-1049PCTlast / fi nal / endi ng / latest uslotsslots may comprise the one or more UL slots / symbols. A dsymsymbols after the first d-siots slots may comprise the one or more DL symbols. A usymsymbols before the last uslotsslots may comprise the one or more UL symbols. A remaining (S - dsiots- usiots). N^b- dsym- usymsymbols may comprise the one or more flexible symbols / slots.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0383] A wireless device may transmit one or more capability messages (e.g., one or more UE capability messages) to a base station. The one or more capability messages may also refer to by one or more UE-capability messages. The one or more UE capability messages may comprise at least one set of capabilities. The at least one set of capabilities may comprise a first set of capabilities. The first set of capabilities (e.g., corresponding to the SBFD operation / configuraion) may comprise a first plurality of UE capabilities. The first plurality of UE capabilities may allow the base station to properly configure the wireless device via the one or more configuration parameters. The first set of capabilities may correspond to / appl icable for a TDD carrier or a FDD carrier Some capabilities of the first set of capabilities may correspond to / appl icable for a sub-band fullduplex (SBFD) operation with ing / in the TDD carrier / spectrum.

[0384] FIG. 22 shows an example of sub-band full-duplex (SBFD) operation as per an aspect of an embodiment of the present disclosure. FIG.22 shows two examples / configurations of SBFD operations in a carrier. Other examples are also possible. The carrier may be a TDD carrier. Using the SBFD operation, a wireless device may reduce UL transmission latency or UL transmission capacity, as the wireless device may be allowed / configured to transmit UL signals / channels in / during SBFD symbols / slots. The SBFD symbols / slots may also be referred to as a plurality of SBFD symbols / slots and / or a set of SBFD symbols / slots.

[0385] The carrier may be an FDD carrier.

[0386] The SBFD symbols / slots (configured / indicated for the SBFD operation) are among the plurality of symbols / slots. The plurality of slots / symbols may comprise the one or more DL / F slots / symbols configured by the one or more configuration parameters). The plurality of slots / symbols may not comprise the one or more UL slots / symbols configured by the one or more configuration parameters).

[0387] The one or more configuration parameters may configure a wireless device with the SBFD operation in the carrier. The one or more configuration parameters may comprise one or more SBFD configuration parameters. ForDocket No.: 25-1049PCTexample, the one or more TDD configuration parameters may comprise one or more SBFD configuration parameters. Other containers for the one or more SBFD configuration parameters are also possible.

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

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

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

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

[0392] The one or more SBFD configuration parameters may configure one or more SBFD subbands. The one or more SBFD configuration parameters may configure / indicate a SBFD subband time locations of a SBFD subband (of the one or more SBFD subbands). The one or more SBFD configuration parameters may configure / indicate a SBFD subband frequency locations of the SBFD subband. For example, the SBFD subband time locations may be within a first period. The first period may be a SBFD period (or a SBFD periodicity).

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

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

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

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

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

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

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

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

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

[0402] The one or more SBFD configuration parameters may indicate / configure the SBFD symbols / slots, e.g., based on / using one or more SBFD subbands. For example, any DL / F symbol / slot within / during the SBFD subband time locations (of a SBFD subband of the one or more SBFD subbands) may be an SBFD symbol / slot.

[0403] The one or more SBFD configuration parameters may indicate that a slot / symbol of the plurality of slots / symbols be an SBFD slot / symbol of the SBFD symbols / slots. The plurality of slots may be a plurality of DL / F symbols / slots (e.g., the one or more DL symbols / slots and / or the one or more flexible symbols / slots) configured by the one or more TDD configuration parameters.

[0404] The SBFD slots / symbols may comprise at least one SBFD slot / symbol. An SBFD slot / symbol of the at least one SBFD slot / symbol may be a DL slot / symbol (of the one or more DL slots / symbols) or a flexible slot / symbol (of the one or more flexible slots / symbols) configured for the SBFD operation. The SBFD slot / symbol may be within the SBFD time locationsDocket No.: 25-1049PCT

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

[0406] For the SBFD subband frequency locations (of a SBFD subband of the one or more SBFD subbands), FIG.22 provides two examples (or configurations or setups). As shown in FIG.22, a maximum number of UL sub-bands (UL SBs) for SBFD operation in an SBFD symbol within a TDD carrier is one.

[0407] A first example may correspond to a first (TDD) carrier. An UL subband (ULSB) in an SBFD symbol / slot may be located at one side of the first carrier. The first example may be referred to by a first type of SBFD operation. The first type of the SBFD operation may correspond to a first type of SBFD symbol / slot. Corresponding to the first type of the SBFD operation each / the SBFD symbol / slot (of the first type of SBFD symbol / slot) of the SBFD slots / symbols may correspond to / comprise a D-U or a U-D partitioning / configuration of frequency resources of the SBFD symbol / slot. The carrier may be the first carrier (or cell).

[0408] A second example may correspond to a second (TDD) carrier. An UL subband in an SBFD symbol / slot may be located at the middle part of the second carrier. The second example may be referred to by a second type of SBFD operation. The second type of the SBFD operation may correspond to a second type of SBFD symbol / slot.Corresponding to the second type of the SBFD operation each / the SBFD symbol / slot (of the second type of SBFD symbol / slot) of the SBFD slots / symbols may correspond to / comprise a D-U-D partitioning / configuration of frequency resources of the SBFD symbol / slot. The carrier may be the second carrier (or cell).

[0409] The D-U or the U-D or the D-U-D partitioning of the frequency resources of the SBFD symbol / slot (of the SBFD symbols / slots) may provide / indicate examples of the SBFD subband frequency location(s). The one or more SBFD configuration parameters may indicate / configure the SBFD subband frequency location(s), e.g., D-U or the U-D or the D-U-D partitioning of the frequency resources of the SBFD symbol / slot (of the SBFD symbols / slots). The SBFD subband frequency location (s) may correspond to (or applicable for) each SBFD symbol / slot within the SBFD subband time locations (comprising the SBFD symbols / slots).

[0410] The SBFD symbol / slot (of the SBFD symbols / slots) may comprise an UL subband and at least one DL subband. The one or more SBFD configuration parameters may configure / indicate the SBFD subband frequency locations corresponding to the UL subband. The one or more SBFD configuration parameters may configure / indicate the SBFD subband frequency locations corresponding to the at least one DL subband. The one or more SBFD configuration parameters may configure / indicate the SBFD subband frequency locations corresponding to a DL subband of the at least one DL subband. The SBFD subband frequency locations may comprise the frequency locations of the UL subband and the frequency locations of a DL subband of the the at least one DL subband. The SBFD subband frequency locations may comprise the frequency locations of the UL subband and the frequency locations of the at least one DL subband.Docket No.: 25-1049PCT

[0411] The frequency locations of the UL subbanci may comprise at least one subband frequency-domain resources (e.g., PRGs or PRBs or REs or RBs or subcarriers).

[0412] The frequency locations of each DL subband of the at least one DL subband may comprise at least one subband frequency-domain resources (e.g., PRGs or PRBs or REs or RBs or subcarriers).

[0413] The frequency locations of UL subband may comprise a first set of resource blocks (RBs). The first set of RBs may comprise / indicate (or equivalently be referred to as) a first set of resource elements (REs). The first set of RBs may comprise / indicate (or equivalently be referred to as) a first set of subcarriers. The first set of RBs may comprise / indicate (or equivalently be referred to as) a first set of PRBs (physical resource blocks). The first set of RBs may comprise / indicate (or equivalently be referred to as) a first set of PRGs (physical resource groups). Other relevant terminologies for the first set of RBs may be possible, although not mentioned here The first set of resource blocks may comprise / be the UL subband frequency resources. The UL subband may be a cell-specific UL subband. In another example, the UL subband may be a UE-specific UL subband.

[0414] The frequency locations of DL subband(s) may comprise a second set of resource blocks (RBs). The DL subband(s) frequency resources may comprise / indicate (or be) the frequency locations of the at least one DL subband. The second set of RBs may comprise / indicate (or equivalently be referred to as) a second set of resource elements (REs). The second set of RBs may comprise / indicate (or equivalently be referred to as) a second set of subcarriers. The second set of RBs may comprise / indicate (or equivalently be referred to as) a second set of PRBs (physical resource blocks). The second set of RBs may comprise / indicate (or equivalently be referred to as) a second set of PRGs (physical resource groups). Other relevant terminologies for the second set of RBs may be possible, although not mentioned here. The second set of resource blocks may comprise / be the DL subband frequency resources (of the at least one DL subband). Each DL subband (of the at least one DL subband) may be a cell-specific DL subband. Each DL subband (of the at least one DL subband) may be a UE-specific DL subband.

[0415] In one example, the one or more SBFD configuration parameters may configure / indicate the first set of RBs and the second set of RBs. The wireless device may determine / derive a third set of resource blocks (RBs) corresponding to frequency locations of Guardband(s). The frequency locations of Guardband(s) (of the carrier) are not within the UL subband or DL subband(s). In some implementations, the third set of RBs maybe empty (e.g., there is no Guardband(s) configured for the cell / UE) . The third set of RBs may comprise / indicate (or equivalently be referred to as) a third set of resource elements (REs). The third set of RBs may comprise / indicate (or equivalently be referred to as) a third set of subcarriers. The third set of RBs may comprise / indicate (or equivalently be referred to as) a third set of PRBs (physical resource blocks). The third set of RBs may comprise / indicate (or equivalently be referred to as) a third set of PRGs (physical resource groups). Other relevant terminologies for the third set of RBs may be possible, although not mentioned here.

[0416] In another example, the one or more SBFD configuration parameters may configure / indicate the first set of RBs and the third set of RBs. The wireless device may determine / derive the second set of resource blocks (RBs) basedDocket No.: 25-1049PCTon the RBs of the active DL BWP and / or the first set of RBs and / or the third set of RBs. For example, The wireless device may determine / derive the second set of resource blocks (RBs) by excluding the first set of RBs and the third set of RBs from RBs of an active DL BWP (or the carrier).

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

[0418] Union of the first set of RBs, the second set of RBs, and the third set of RBs may comprise RBs that are allocated for the carrier. Union of the first set of RBs, the second set of RBs, and the third set of RBs may comprise all RBs belonging to all the first set of RBs, the second set of RBs, and the third set of RBs.

[0419] The active DL BWP (or the carrier) may comprise a portion of the first set of RBs. The portion of the first set of RBs being / overlapping with RBs of the active DL BWP may be referred to as UL usable PRBs.

[0420] The active DL BWP (or the carrier) may comprise all RBs of the first set of RBs. The (all) RBs of the first set of RBs being / overlapping with RBs of the active DL BWP may be / comprise the UL usable PRBs.

[0421] The active DL BWP (or the carrier) may comprise no RBs of the first set of RBs. For example, the UL usable PRBs are empty (e.g., with zero number of PRBs or with cardinality / size of zero).

[0422] The active DL BWP (or the carrier) may comprise a portion of the second set of RBs. The portion of the second set of RBs being / overlapping with RBs of the active DL BWP may be referred to as DL usable PRBs.

[0423] The active DL BWP (or the carrier) may comprise all RBs of the second set of RBs. The (all) RBs of the second set of RBs being / overlapping with RBs of the active DL BWP may be / comprise the DL usable PRBs.

[0424] The active DL BWP (or the carrier) may comprise no RBs of the second set of RBs. For example, the DL usable PRBs are empty (e.g., with zero number of PRBs or with cardinality / size of zero).

[0425] The active DL BWP (or the carrier) may comprise a portion of the third set of RBs.

[0426] The active DL BWP (or the carrier) may comprise all RBs of the third set of RBs.

[0427] The active DL BWP (or the carrier) may comprise no RBs of the third set of RBs, e.g., the active DL BWP does not comprise any UL subband or DL subband(s).

[0428] The active UL BWP (or the carrier) may comprise a portion of the first set of RBs. The portion of the first set of RBs being / overlapping with RBs of the active UL BWP may be referred to as the UL usable PRBs.

[0429] The active UL BWP (or the carrier) may comprise all RBs of the first set of RBs. The (all) RBs of the first set of RBs being / overlapping with RBs of the active UL BWP may be / comprise the UL usable PRBs.

[0430] The active UL BWP (or the carrier) may comprise no RBs of the first set of RBs. For example, the UL usable PRBs are empty (e.g., with zero number of PRBs or with cardinality / size of zero).Docket No.: 25-1049PCT

[0431] The active UL BWP (or the carrier) may comprise a portion of the second set of RBs. The portion of the second set of RBs being / overlapping with RBs of the active UL BWP may be referred to as the DL usable PRBs.

[0432] The active UL BWP (or the carrier) may comprise all RBs of the second set of RBs. The (all) RBs of the second set of RBs being / overlapping with RBs of the active UL BWP may be / comprise the DL usable PRBs.

[0433] The active UL BWP (or the carrier) may comprise no RBs of the second set of RBs. For example, the DL usable PRBs are empty (e.g. , with zero number of PRBs or with cardinal ity / size of zero).

[0434] The active UL BWP (or the carrier) may comprise a portion of the third set of RBs.

[0435] The active UL BWP (or the carrier) may comprise all RBs of the third set of RBs.

[0436] The active UL BWP (or the carrier) may comprise no RBs of the third set of RBs.

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

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

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

[0440] FIG. 22 further shows an example of the UL usable PRBs. As also shown in FIG. 25, the UL subband frequency resources (e.g., the first set of RBs) within the active UL BWP are the UL usable PRBs. The UL usable PRBs may further referred to by UL valid PRBs. The UL usable PRBs may comprise UL usable / valid subcarriers / resource blocks / resource elements / PRBs / PRGs corresponding to each SBFD symbol / slot of the SBFD symbols / slots.

[0441] The wireless device may determine the UL usable PRBs based on at least RBs of the active DL BWP; and / or the UL subband frequency resources (e.g., the first set of RBs). The wireless device may determine the UL usable PRBs (or the first set of RBs) as an intersection between the UL subband frequency resources and the active DL BWP (eg., in the SBFD symbol(s) / slot(s)). The intersection between UL subband frequency resources and the active DL BWP may comprise RBs of the first set of RBs that are fully overlapping (in frequency domain) with the active DL BWP.

[0442] The wireless device may determine the UL usable PRBs based on at least RBs of the active UL BWP; and / or the UL subband frequency resources (e.g., the first set of RBs). The wireless device may determine the UL usable PRBs (or the first set of RBs) as an intersection between the UL subband frequency resources and the active UL BWP (eg., in the SBFD symbol(s) / slot(s)). The intersection between UL subband frequency resources and the active UL BWP may comprise RBs of the first set of RBs that are fully overlapping (in frequency domain) with the active UL BWP.Docket No.: 25-1049PCT

[0443] FIG. 22 further shows an example of the DL usable PRBs. The DL subband(s) frequency resources (e.g., the second set of RBs) within the active DL BWP may comprise / be the DL usable PRBs. The DL usable PRBs may comprise DL usable subcarriers / resource blocks / elements corresponding to each SBFD symbol / slot of the SBFD symbols / slots.

[0444] The wireless device may determine the DL usable PRBs based on at least RBs of the active DL BWP; and / or the DL subband(s) frequency resources (e.g., the second set of RBs). For example, the wireless device may determine the DL usable PRBs as an intersection between the DL subband(s) frequency resources and active DL BWP in the SBFD symbol(s) / slot(s). The intersection between DL subband(s) frequency resources and the active DL BWP may comprise RBs of the second set of RBs that are fully overlapping (in frequency domain) with the active DL BWP.

[0445] The wireless device may determine the DL usable PRBs based on at least RBs of the active UL BWP; and / or the DL subband(s) frequency resources (e.g., the second set of RBs). For example, the wireless device may determine the DL usable PRBs as an intersection between the DL subband(s) frequency resources and active UL BWP in the SBFD symbol(s) / slot(s). The intersection between DL subband(s) frequency resources and the active UL BWP may comprise RBs of the second set of RBs that are fully overlapping (in frequency domain) with the active UL BWP.

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

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

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

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

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

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

[0452] As shown in FIG. 22, when the link direction is the DL link direction corresponding to / in a SBFD symbol / slot #1 (of the at least one SBFD symbol / slot), the wireless device may determine to receive DL signals / channels using / via the DL usable PRBs during / in the SBFD symbol / slot #1.

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

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

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

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

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

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

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

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

[0461] FIG. 23, FIG. 24, and FIG.25 show examples of sub-band full-duplex (SBFD) operation. The SBFD operation may be based on the one or more SBFD configuration parameters discussed in relation to FIG.22. In the examples shown in FIG.23, FIG. 24, and FIG. 25, the one or more SBFD configuration parameters may indicate / comprise a first SBFD configuration (Configuration 1). Although embodiments of FIG.23, FIG.24, and FIG. 25 based on the D-U (or the U-D) partition, the embodiments of FIG. 23, FIG.24, and FIG. 2are equally applicable for the D-U-D partition of the SBFD operation.Docket No.: 25-1049PCT

[0462] The first SBFD configuration may be a default / basel ine SBFD configuration for UL / DL transmissions across SBFD symbols / slots and non-SBFD symbols / slot on an active BWP of the one or more BWPs of the serving cell. For example, when the one or more SBFD configuration parameters do not indicate / provide / configure a second SBFD configuration (e.g., Configuration 2) of the SBFD operation, the wireless device may assume the one or more SBFD configuration parameters indicate / comprise the first SBFD configuration. In another example, when the wireless device does not indicate a capability (e.g., via transmitting the one or more capability messages to the base station) for the second SBFD configuration (e.g., the first set of capabilities does not comprise / indicate the capability / support for the second SBFD configuration), the wireless device may assume the one or more SBFD configuration parameters indicate / comprise the first SBFD configuration.

[0463] The first SBFD configuration may indicate first UL transmissions (via the active BWP of the one or more BWPs) are only allowed / limited / restricted / enabled during slots / symbols with a first symbol / slot type (e.g., non-SBFD symbol / slot). The first symbol / slot type may be non-SBFD. The first symbol / slot type may be also referred to as a first valid symbol / slot type (e.g., for transmitting the first UL transmissions). The first UL transmissions may be via first UL resources. The one or more configuration parameters may indicate / configure / provide the first UL resources for the first UL transmissions. FIG. 23 and / or FIG. 24 show examples of the first UL resources. In some examples, the one or more configuration parameters may indicate / configure / provide a plurality of UL resources for UL transmissions via the BWP; and / or indicate the first UL resources of the plurality of UL resources are only valid for transmissions in non-SBFD symbols / slots, e.g., valid symbol / slot type of the first UL resources is the first symbol / slot type. The first UL resources may be associated with / configured for the active BWP (of the one or more BWPs).

[0464] As shown in FIG. 23 and / or FIG. 24, based on the first SBFD configuration indicating that the first UL transmissions are only allowed / limited / restricted / enabled during slots / symbols with the first symbol / slot type (e.g., a valid symbol type for the first UL transmissions / first UL resources is the first symbol / slot type), the wireless device may only transmit the first UL transmissions using the first UL resources when corresponding transmission occasions / opportu nities (symbols) of the first UL resources fully / partially overlapping (in time domain) with symbols / slots with the first symbol / slot type. When all transmission occasions / opportunities (symbols) of the first UL resources fully / partially overlapping (in time domain) with symbols / slots with the first symbol / slot type, the wireless device may transmit any first UL transmissions.

[0465] As shown in FIG 23 and / or FIG. 24, based on the first SBFD configuration indicating that the first UL transmissions are only allowed / limited / restricted / enabled during slots / symbols with the first symbol / slot type (e.g., a valid symbol type for the first UL transmissions / first UL resources is the first symbol / slot type), the wireless device may avoid / skip / drop transmitting the first UL transmissions using the first UL resources when corresponding transmission occasions / opportunities (symbols) of the first UL resources (fully / partially) overlapping (in time domain, e.g., in at least one symbol) with symbols / slots with the second symbol / slot type. When all transmission occasions / opportunitiesDocket No.: 25-1049PCT(symbols) of the first UL resources fully / partially overlapping (in time domain, e.g., in at least one symbol) with symbols / slots with the second symbol / slot type, the wireless device may not transmit any first UL transmissions.

[0466] As shown in FIG. 23 and / or FIG. 24, based on the first SBFD configuration indicating that the first UL transmissions are only allowed / limited / restricted / enabled during slots / symbols with the first symbol / slot type (e.g., a valid symbol type for the first UL transmissions / first UL resources is the first symbol / slot type), the wireless device may determine that the first UL resources that fully / partially overlap (in time domain, e.g., in at least one symbol) with symbols / slots with the second symbol / slot type are invalid for the first UL transmissions using the first UL resources.

[0467] The first SBFD configuration may indicate / configure second UL transmissions (via the active BWP of the one or more BWPs) are only allowed / limited / restricted / enabled during slots / symbols with a second symbol / slot type (e.g., SBFD symbol / slot) The second symbol / slot type may be SBFD. The second symbol / slot type may be also referred to as a second valid symbol / slot type (e.g., for transmitting the second UL transmissions). The second UL transmissions may be via second UL resources. The one or more configuration parameters may indicate / configure / provide the second UL resources of the plurality of UL resources for the second UL transmissions. FIG. 23 and / or FIG. 24 show examples of the second UL resources. In some examples, the one or more configuration parameters may indicate / configure / provide the second UL resources of the plurality of UL resources are only valid for transmissions in SBFD symbols / slots, e.g., valid symbol / slot types of the second UL resources are the second symbol / slot type. The second UL resources may be associated with the active BWP.

[0468] As shown in FIG. 23 and / or FIG. 24, based on the first SBFD configuration indicating that the second UL transmissions are only allowed / limited / restricted / enabled during slots / symbols with the second symbol / slot type (e.g., a valid symbol type for the second UL transmissions / second UL resources is the second symbol / slot type), the wireless device may only transmit the second UL transmissions using the second UL resources when corresponding transmission occasions / opportunities (symbols) of the second UL resources fully / partially overlapping (in time domain) with symbols / slots with the second symbol / slot type. When all transmission occasions / opportunities (symbols) of the second UL resources fully / partially overlapping (in time domain) with symbols / slots with the second symbol / slot type, the wireless device may transmit any second UL transmissions.

[0469] As shown in FIG. 23 and / or FIG. 24, based on the first SBFD configuration indicating that the second UL transmissions are only allowed / limited / restricted / enabled during slots / symbols with the second symbol / slot type (e.g., a valid symbol type for the second UL transmissions / second UL resources is the second symbol / slot type), the wireless device may avoid / skip / drop transmitting the second UL transmissions using the second UL resources when corresponding transmission occasions / opportunities (symbols) of the second UL resources overlapping (in time domain, e.g., in at least one symbol) with symbols / slots with the first symbol / slot type. When all transmission occasions / opportunities (symbols) of the second UL resources fully / partially overlapping (in time domain, e.g., in at least one symbol) with symbols / slots with the first symbol / slot type, the wireless device may not transmit any second UL transmissions.Docket No.: 25-1049PCT

[0470] As shown in FIG 23 and / or FIG. 24, based on the first SBFD configuration indicating that the second UL transmissions are only allowed / limited / restricted / enabled during slots / symbols with the second symbol / slot type (e.g., a valid symbol type for the second UL transmissions / second UL resources is the second symbol / slot type), the wireless device may determine that the second UL resources that fully / partially overlap (in time domain, e.g., in at least one symbol) with symbols / slots with the first symbol / slot type are invalid for the second UL transmissions using the second UL resources.

[0471] For example, the first UL resources may comprise / correspond to at least one of the following: first subset of CG configurations for first CG PUSCH transmissions; and / or first subset of PUCCH resource(s) for P / SP CSI report(s) of the one or more CSI reports; and / or first subset of PUCCH resource(s) for SR; and / or a first SRS resource set of the list of SRS resource set (e.g , SRS-ResourceSets); and / or first subset of PUSCH resource(s) for SP CSI report(s) of the one or more CSI reports; and / or first subset of RA resources.

[0472] The first UL transmissions may comprise at least one of the following: the first CG PUSCH transmissions using / via the first subset of CG configurations; and / or SRs via / using / corresponding to the first subset of PUCCH resource(s); and / or P / SP CSI report(s) via / using / corresponding to the first subset of PUCCH resource(s); and / or SRS transmissions via SRS resources indicated / associated with the first SRS resource set; and / or SP CSI reports(s) via / using / corresponding to the first subset of PUSCH resource(s); and / or PRACH / preamble transmissions via RA resources indicated / associated with the first subset of RA resources.

[0473] The one or more configuration parameters (e.g., one or more RA configuration parameters) may indicate / comprise / configure a plurality of RA resources (e.g., PRACH IDs / indexes and / or PRACH occasions or the like). The plurality of RA resources may comprise the first subset of RA resources for transmitting PRACHs during symbols / slots with the first valid symbol / slot type.

[0474] For example, the second UL resources may comprise / correspond to at least one of the following: second subset of CG configurations for second CG PUSCH transmissions; and / or second subset of PUCCH resource(s) for P / SP CSI report(s) of the one or more CSI reports; and / or second subset of PUCCH resource(s) for SR; and / or a second SRS resource set of the list of SRS resource set (e.g., SRS-ResourceSets); and / or second subset of PUSCH resource(s) for SP CSI report(s) of the one or more CSI reports; and / or second subset of RA resources.

[0475] The second UL transmissions may comprise at least one of the following: the second CG PUSCH transmissions using / via the second subset of CG configurations; and / or SRs via / using / corresponding to the second subset of PUCCH resource(s); and / or P / SP CSI report(s) via / using / corresponding to the second subset of PUCCH resource(s); and / or SRS transmissions via SRS resources indicated / associated with the second SRS resource set; and / or SP CSI reports(s) via / using / corresponding to the second subset of PUSCH resource(s); and / or PRACH / preamble transmissions via RA resources indicated / associated with the second subset of RA resources. The plurality of RA resources may comprise the second subset of RA resources for transmitting PRACHs during symbols / slots with the second valid symbol / slot type.Docket No.: 25-1049PCT

[0476] For example, the one or more PUCCH configuration parameters may comprise a first bitmap (e.g with a length equal to a number of resources in the plurality of PUCCH resources configured for the one or more CSI reports). Each bit of the first bitmap may be associated with each resource of the plurality of PUCCH resources, wherein if the bit is configured with a first value (e.g., 0), the valid symbol / slot type of the resource is SBFD (or non-SBFD alternatively) and if the bit is configured with a second value (e.g., 1), the valid symbol / slot type of the resource is non-SBFD (or SBFD alternatively).

[0477] Alternatively, a resource of the plurality of PUCCH resources configured for the one or more CSI reports may comprise a field indicating whether the valid symbol / slot type for the corresponding resource is the SBFD or non-SBFD. In some examples, the first valid symbol type for the resource may be the default symbol type of the resource, e.g., when the field is not indicated (or absent) for the resource, the wireless device may determine the valid symbol type for the resource is the first valid symbol type. In some other examples, the second valid symbol type for the resource may be the default symbol type of the resource, e.g., when the field is not indicated (or absent) for the resource, the wireless device may determine the valid symbol type for the resource is the second valid symbol type. In yet another examples, when the field is not indicated (or absent) for the resource and all PUCCH occasions of the resource overlap with SBFD symbols, the wireless device may determine the valid symbol type for the resource is the second valid symbol type. In yet another examples, when the field is not indicated (or absent) for the resource and all PUCCH occasions of the resource overlap with non-SBFD symbols, the wireless device may determine the valid symbol type for the resource is the first valid symbol type.

[0478] For example, the one or more CG configuration parameters may comprise a second bitmap (e.g., with a length equal to a number of CG configurations in the list of CG configurations). Each bit of the first bitmap may be associated with each CG configuration of the list of CG configurations, wherein if the bit is configured with a first value (e.g., 0), the valid symbol / slot type of the CG configuration is SBFD (or non-SBFD alternatively) and if the bit is configured with a second value (e.g., 1), the valid symbol / slot type of the CG configuration is non-SBFD (or SBFD alternatively).

[0479] Alternatively, an CG configuration of the list of CG configurations may comprise a field indicating whether the valid symbol / slot type for the corresponding CG configuration is the SBFD or non-SBFD. In some examples, the first valid symbol type for the CG configuration may be the default symbol type of the resource, e.g., when the field is not indicated (or absent) for the CG configuration, the wireless device may determine the valid symbol type for the CG configuration is the first valid symbol type. In some other examples, the second valid symbol type for the CG configuration may be the default symbol type of the resource, e.g., when the field is not indicated (or absent) for the CG configuration, the wireless device may determine the valid symbol type for the CG configuration is the second valid symbol type. In yet another examples, when the field is not indicated (or absent) for the CG configuration and all CG PUSCH occasions of the CG configuration overlap with SBFD symbols, the wireless device may determine the valid symbol type for the CG configuration is the second valid symbol type. In yet another examples, when the field is notDocket No.: 25-1049PCTindicated (or absent) for the resource and the CG configuration and all CG PUSCH occasions of the CG configuration overlap with non-SBFD symbols, the wireless device may determine the valid symbol type for the CG configuration is the first valid symbol type.

[0480] For example, the one or more PUCCH configuration parameters may comprise a third bitmap (e.g. , with a length equal to a number of resources in the list of SR resource configurations). Each bit of the first bitmap may be associated with each PUCCH resource of an SR resource configuration of the list of SR resource configurations, wherein if the bit is configured with a first value (e.g., 0), the valid symbol / slot type of the PUCCH resource is SBFD (or non-SBFD alternatively) and if the bit is configured with a second value (e.g., 1), the valid symbol / slot type of the PUCCH resource is non-SBFD (or SBFD alternatively).

[0481] Alternatively, an SR resource configuration of the list of SR resource configurations configured for the one or more CSI reports may comprise a field indicating whether the valid symbol / slot type for the corresponding SR resource configuration is the SBFD or non-SBFD. In some examples, the first valid symbol type for the SR resource configuration may be the default symbol type, e.g., when the field is not indicated (or absent) for the SR resource configuration, the wireless device may determine the valid symbol type for the SR resource configuration is the first valid symbol type. In some other examples, the second valid symbol type for the SR resource configuration may be the default symbol type, e.g., when the field is not indicated (or absent) for the SR resource configuration, the wireless device may determine the valid symbol type for the SR resource configuration is the second valid symbol type. In yet another examples, when the field is not indicated (or absent) for the SR resource configuration and all SR transmission occasion of the SR resource configuration overlap with SBFD symbols, the wireless device may determine the valid symbol type for the SR resource configuration is the second valid symbol type. In yet another examples, when the field is not indicated (or absent) for the SR resource configuration and all SR transmission occasion of the SR resource configuration overlap with non-SBFD symbols, the wireless device may determine the valid symbol type for the SR resource configuration is the first valid symbol type.

[0482] In some embodiments of the present disclosure, the first set of capabilities may further indicate a third capability. The third capability may be a baseline / default (or a required) SBFD capability allowing the wireless device to operate according to the SBFD configuration in the cell configured with the SBFD (e.g., via the one or more SBFD configuration parameters) and / or when the wireless device is an SBFD-aware wireless device. For example, the third capability may indicate / provide a support for UL / DL communications (transmissions / receptions) according to the first SBFD configuration discussed in embodiments of FIG. 23, FIG. 24 and / or FIG.25.

[0483] The third capability may indicate the wireless device supports determining (for UL transmissions) whether to use the first UL resources or the second UL resources for UL transmissions via the cell. The third capability may indicate the wireless device supports determining (for UL transmissions) at least one of the following: whether a CG configuration (of the list of CG configurations ) is one of the second subset of CG configurations or the first subset of CG configurations; and / or whether a PUCCH resource (indicated by the one or more CSI reporting settings) is one ofDocket No.: 25-1049PCTthe second subset of PUCCH resource(s) for P / SP CSI report(s) of the one or more CSI reports or one of the first subset of PUCCH resource(s) for P / SP CSI report(s) of the one or more CSI reports; and / or whether a PUCCH resource (indicated by the list of SR resource configurations) is among the second subset of PUCCH resource(s) for SR or the first subset of PUCCH resource(s) for SR; and / or a PUSCH resource for SP CSI report is one of the second subset of PUSCH resource(s) for SP CSI report(s) of the one or more CSI reports or one of the first subset of PUSCH resource(s) for SP CSI report(s) of the one or more CSI reports.

[0484] The list of CG configurations may comprise the first subset of CG configurations. The first CG PUSCH transmissions, using the first subset of CG configurations, may be via the active BWP, e.g., the first subset of CG configurations may be associated with the active BWP. The wireless device may determine the valid symbol type for a CG PUSCH transmission (of the first CG PUSCH transmissions) being the first valid symbol / slot type, based on the one or more configuration parameters indicating the valid symbol type for corresponding CG configuration of the first subset of CG configurations being the first valid symbol / slot type.

[0485] A first number of CG configurations in the first subset of CG configurations may be a first number. The first number may be 0, 1 or 2, 3 or the like. The first number may be equal to a number of CG configurations in the list of CG configurations that are associated with the first valid symbol / slot type The first number may be equal to a number of CG configurations in the list of CG configurations (e.g., when the one or more configuration parameters do not configure / indicate a second subset of CG configurations), e.g., by default or as a baseline the wireless device may consider / determine all CG configurations in the list of CG configurations belong to the first subset of CG configurations (eg., have the first valid symbol type) when / if the one or more configuration parameters do not configure / indicate the second subset of CG configurations. The first number may be zero, e.g., when no CG configuration of the list of CG configurations belong to the first subset of CG configurations, e.g., the first subset of CG configurations is empty or when the list of CG configurations do not comprise the first subset of CG configurations.

[0486] A CG PUSCH transmission of the first CG PUSCH transmissions (using the first subset of CG configurations) may be a Type 1 CG PUSCH transmission, e.g , when a first CG configuration of the first subset of CG configurations for the CG PUSCH transmission is a Type 1 CG configuration.

[0487] For example, when a valid symbol type of a CG configuration (e.g., Type 1 CG configuration) of the list of CG configurations is the first valid symbol / slot type, the wireless device does not expect that all CG PUSCH transmission occasions / opportunities configured by the CG configuration to (fully / partially) overlap / collide with SBFD slots / sy mbols . When the valid symbol type of a CG configuration (e.g., Type 1 CG configuration) of the list of CG configurations is the first valid symbol / slot type, the wireless device expects that at least one CG PUSCH transmission occasions / opportunities configured by the CG configuration to fully be in the non-SBFD slots / symbols.

[0488] A CG PUSCH transmission of the first CG PUSCH transmissions (using the first subset of CG configurations) may be a Type 2 CG PUSCH transmission, e.g, when a second CG configuration of the first subset of CG configurations for the CG PUSCH transmission is a Type 2 CG configuration. For example, the wireless device mayDocket No.: 25-1049PCTreceive a command (e.g., a DCI or MAC CE or an RRC message of the one or more RRC messages or a message of the one or more messages) activating / indicati ng the second CG configuration (of the first subset of CG configurations), e.g., for starting / activating the first CG RUSCH transmission(s) using configured uplink grants indicated by the second CG configuration and / or the command. In response to the command, the wireless device may determine the valid symbol type for the first CG PUSCH transmission(s) (using the second CG configuration) being the first valid symbol / slot type, based on a first / starting / initial / earliest (symbol of) transmission occasion of the second CG PUSCH transmission(s) being in / at / during the first valid symbol / slot type.

[0489] The list of CG configurations may comprise the second subset of CG configurations. The second CG PUSCH transmissions, using the second subset of CG configurations, may be via the active BWP, e.g., the second subset of CG configurations may be associated with the active BWP. The wireless device may determine the valid symbol type for a CG PUSCH transmission (of the second CG PUSCH transmissions) being the second valid symbol / slot type, based on the one or more configuration parameters indicating the valid symbol type for corresponding CG configuration of the second subset of CG configurations being second first valid symbol / slot type.

[0490] A first number of CG configurations in the second subset of CG configurations may be a first number. The first number may be 0, 1 or 2, 3 or the like The first number may be equal to a number of CG configurations in the list of CG configurations that are associated with the second valid symbol / slot type. The first number may be equal to a number of CG configurations in the list of CG configurations (e.g., when the one or more configuration parameters do not configure / indicate the first subset of CG configurations), e.g., by default or as a baseline the wireless device may consider / determine all CG configurations in the list of CG configurations belong to the second subset of CG configurations (e.g., have the second valid symbol type) when / if the one or more configuration parameters do not configure / indicate the first subset of CG configurations. The first number may be zero, e.g., when no CG configuration of the list of CG configurations belong to the second subset of CG configurations, e.g., the second subset of CG configurations is empty or when the list of CG configurations do not comprise the second subset of CG configurations.

[0491] A CG PUSCH transmission of the second CG PUSCH transmissions (using the second subset of CG configurations) may be a Type 1 CG PUSCH transmission, e.g., when a first CG configuration of the second subset of CG configurations for the second CG PUSCH transmission is a Type 1 CG configuration.

[0492] For example, when a valid symbol type of a CG configuration (e.g., Type 1 CG configuration) of the list of CG configurations is the second valid symbol / slot type, the wireless device does not expect that all CG PUSCH transmission occasions / opportunities configured by the CG configuration to (fully / partially) overlap / col I ide with non-SBFD slots / symbols . When the valid symbol type of a CG configuration (e.g., Type 1 CG configuration) of the list of CG configurations is the second valid symbol / slot type, the wireless device expects that at least one CG PUSCH transmission occasions / opportunities configured by the CG configuration to fully be in the SBFD slots / symbols.

[0493] A CG PUSCH transmission of the second CG PUSCH transmissions (using the second subset of CG configurations) may be a Type 2 CG PUSCH transmission, e.g., when a second CG configuration ...

Claims

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

1. A method comprising:receiving, by a wireless device, a plurality of configuration parameters comprising:one or more first configuration parameters indicating a physical uplink control channel (PUCCH) resource for a first channel state information (CSI) report in a slot;one or more second configuration parameters configuring a symbol type associated with the first CSI report, wherein the symbol type is either sub-band full duplex (SBFD) or non-SBFD; andone or more third configuration parameters indicating scheduling request (SR) resource configurations for transmitting SRs in the slot;determining, for transmitting the first CSI report, a first number of uplink control information (UCI) bits based on a second number of first SR resource configurations, among the SR resource configurations, that are associated with the symbol type; andtransmitting, in the slot and via the PUCCH resource, the first CSI report comprising the first number of UCI bits.

2. A method comprising:transmitting, by a wireless device, a first channel state information (CSI) report comprising a first number of uplink control information (UCI) bits, wherein the first number of UCI bits is based on whether a symbol type, associated with the first CSI report, is sub-band full duplex (SBFD).

3. The method of claim 2, further comprising receiving, by the wireless device, one or more configuration parameters.

4. The method of claim 3, wherein the one or more configuration parameters comprise one or more first configuration parameters indicating a physical uplink control channel (PUCCH) resource for the first CSI report in a slot.

5. The method of claim 4, wherein the one or more configuration parameters further comprise one or more second configuration parameters configuring the symbol type associated with the first CSI report.

6. The method of claim 5, wherein the symbol type is sub-band full duplex (SBFD).

7. The method of claim 5, wherein the symbol type is non-SBFD.

8. The method of any one of claims 4 to 7, wherein the one or more configuration parameters further comprise one or more third configuration parameters indicating scheduling request (SR) resource configurations for transmitting SRs in the slot.

9. The method of any one of claims 4 to 8, wherein the transmitting the first CSI report is in the slot.

10. The method of any one of claims 4 to 9, wherein the transmitting the first CSI report is via the PUCCH resource.

11. The method of any one of claims 4 to 10, wherein the PUCCH resource is for CSI reporting on PUCCH.Docket No.: 25-1049PCT12. The method of any one of claims 2 and 11 , wherein the first number of UCI bits is based on a second number of first SR resource configurations, among the SR resource configurations, that are associated with the symbol type of the first CSI report.

13. The method of claim 12, wherein the number of UCI bits is based on a logarithm of the second number of the first SR resource configurations and a number of CSI report bits of the first CSI report.

14. The method of any one of claims 2 to 13, wherein the symbol type is a valid symbol type for PUCCH carrying the first CSI report.

15. The method of any one of claims 2 to 14, wherein the first CSI report is a periodic CSI report or a semi-persistent CSI report.

16. The method of any one of claims 2 to 11 , wherein the first number of UCI bits is not based on a third number of second SR resource configurations, of the SR resource configurations, that are not associated with the symbol type of the CSI report.

17. The method of claim 16, wherein the first number of UCI bits excludes the third number of second SR resource configurations.

18. The method of any one of claims 16 to 17, wherein thefirst number of UCI bits is equal to a subtraction of the third number of second SR resource configurations from a fourth number of SR resource configurations.

19. The method of any one of claims 16 to 18, wherein the one or more third configuration parameters indicate each SR resource configuration of the first SR resource configurations is within a first valid symbol type.

20. The method of claim 19, wherein the first valid symbol type is SBFD.

21. The method of claim 19 wherein the first valid symbol type is non-SBFD.

22. The method of any one of claims 16 to 21, wherein the one or more third configuration parameters indicate each SR resource configuration of the second SR resource configurations is with a second valid symbol type.

23. The method of claim 22, wherein the second valid symbol type is non-SBFD.

24. The method of claim 22, wherein the second valid symbol type is SBFD.

25. The method of any one of claims 12 to 24, wherein a first SR resource configuration of the first SR resource configurations indicates a first PUCCH resource for transmitting a first SR of the SRs, wherein the first PUCCH resource overlaps with the PUCCH resource in time domain.

26. The method of claim 25, wherein a second SR resource configuration of the second SR resource configurations indicate a second PUCCH resource for transmitting a second SR of the SRs, wherein the second PUCCH resource overlaps with the PUCCH resource in time domain.

27. The method of any one of claims 2 to 26, wherein the one or more configuration parameters indicate:sub-band full-duplex (SBFD) symbols;frequency domain location and bandwidth of one or more downlink sub-bands of the SBFD symbols; and frequency domain location and bandwidth of an uplink sub-band of the SBFD symbols.Docket No.: 25-1049PCT28. The method of claim 27, wherein the PUCCH resource in the slot is within one or more SBFD symbol of the SBFD symbols, wherein the transmitting the PUCCH is using the uplink sub-band.

29. The method of claim 27, wherein the PUCCH resource in the slot is within one or more symbols of the slot, wherein the one or more symbols are not among the SBFD symbols.

30. A method comprising:receiving, by a base station from a wireless device, a first CSI report comprising a first number of uplink control information (UCI) bits, wherein the first number of UCI bits is based on whether a symbol type, associated with the first CSI report, is SBFD.

31. The method of claim 30, further comprising transmitting, to the wireless device, one or more configuration parameters.

32. The method of claim 31 , wherein the one or more configuration parameters comprise one or more first configuration parameters indicating a physical uplink control channel (PUCCH) resource for the first CSI report in a slot.

33. The method of claim 32, wherein the one or more configuration parameters comprise one or more second configuration parameters configuring the symbol type associated with the first CSI report.

34. The method of claim 33, wherein the symbol type is sub-band full duplex (SBFD).

35. The method of claim 33, wherein the symbol type is non-SBFD.

36. The method of any one of claims 32 to 35, wherein the one or more configuration parameters comprise one or more third configuration parameters indicating scheduling request (SR) resource configurations for receiving SRs in the slot.

37. The method of any one of claims 32 to 36, wherein the receiving the first CSI report is via at least one of:the slot; orthe PUCCH resource.

38. The method of any one of claims 32 to 37, wherein the PUCCH resource is for CSI reporting on PUCCH.

39. The method of any one of claims 30 to 38, wherein the first number of UCI bits is based on a second number of first SR resource configurations, among the SR resource configurations, that are associated with the symbol type of the first CSI report.

40. The method of claim 39, wherein the number of UCI bits is based on a logarithm of the second number of the first SR resource configurations and a number of CSI report bits of the first CSI report.

41. The method of any one of claims 30 to 40, wherein the symbol type is a valid symbol type for PUCCH carrying the first CSI report.

42. The method of any one of claims 30 to 41 , wherein the first CSI report is a periodic CSI report or a semi- persistent CSI report.Docket No.: 25-1049PCT43. The method of any one of claims 30 to 42, wherein the first number of UCI bits is not based on a third number of second SR resource configurations, of the SR resource configurations, that are not associated with the symbol type of the CSI report.

44. The method of claim 43, wherein the first number of UCI bits excludes the third number of second SR resource configurations.

45. The method of any one of claims 43 to 44, wherein the first number of UCI bits is equal to a subtraction of the third number of second SR resource configurations from a fourth number of SR resource configurations.

46. The method of any one of claims 43 to 45, wherein the one or more third configuration parameters indicate each SR resource configuration of the first SR resource configurations is within a first valid symbol type.

47. The method of claim 46, wherein the first valid symbol type is SBFD.

48. The method of claim 46 wherein the first valid symbol type is non-SBFD.

49. 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 48.

50. 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 48.

Images