Downlink communications under subband full-duplex operations

Abstract

A wireless device transmits to a base station, one or more user equipment (UE)-capability messages indicating the wireless device supports receiving physical downlink shared channel (PDSCH) with a resource mapping that excludes resource elements (REs), among REs assigned for the PDSCH reception, that are not within one or more downlink sub-bands of a sub-band full-duplex (SBFD) configuration. The wireless device receives one or more radio resource control (RRC) messages comprising a first SBFD configuration. The first SBFD configuration indicates one or more SBFD symbols and downlink sub-band frequency resources of at least one downlink sub-band. The wireless device determines at least one resource element (RE), among a plurality of REs assigned for PDSCH reception, based on the at least one RE not being within the at least one downlink sub-band. The wireless device receives, in the plurality of REs, the first PDSCH during the one or more SBFD symbols.

Description

TITLEDownlink Communications under Subband Full-Duplex Operations CROSS-REFERENCE TO RELATED APPLICATIONS

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0016] FIG. 11B 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 COE-to-REG mapping for DOI transmission on a CORESET and PDCCH processing.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0034] FIG. 28 illustrates an aspect of an example embodiment according to the present disclosure.

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

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

[0037] FIG. 31A and FIG. 31 B illustrate aspects of an example embodiments according to the present disclosure.

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

[0039] FIG. 33 illustrates an aspect of an example embodiment according to the present disclosure.

[0040] FIG. 34 illustrates an aspect of an example embodiment according to the present disclosure.

[0041] FIG. 35 illustrates an aspect of an example embodiment according to the present disclosure.

[0042] FIG. 36 illustrates an aspect of an example embodiment according to the present disclosure.

[0043] FIG. 37 illustrates an aspect of an example embodiment according to the present disclosure.

[0044] FIG. 38 illustrates an aspect of an example embodiment according to the present disclosure.

[0045] FIG. 39 illustrates an aspect of an example embodiment according to the present disclosure.

[0046] FIG. 40 illustrates an aspect of an example embodiment according to the present disclosure.

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

[0048] FIG. 42 illustrates an aspect of an example embodiment according to the present disclosure.

[0049] FIG. 43 illustrates an aspect of an example embodiment according to the present disclosure.

[0050] FIG. 44 illustrates an aspect of an example embodiment according to the present disclosure.

[0051] FIG. 45 illustrates an aspect of an example embodiment according to the present disclosure.

[0052] FIG. 46 illustrates an aspect of an example embodiment according to the present disclosure.

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

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

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

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

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

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

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

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

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

[0062] Many of the elements described in the disclosed embodiments may be implemented as modules. A module is defined here as an element that performs a defined function and has a defined interface to other elements. The modules described in this disclosure may be implemented in hardware, software in combination with hardware, firmware, wetware (e.g. hardware with a biological element) or a combination thereof, which may be behaviorally equivalent. For example, modules may be implemented as a software routine written in a computer language configured to be executed by a hardware machine (such as C, C++, Fortran, Java, Basic, MATLAB or the like) or a modeling / simulation program such as Simulink, Stateflow, GNU Octave, or LabVI EWMathScript. 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 (OPLDs). 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.

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

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

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

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

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

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

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

[0070] The RAN 104 may be deployed as a homogenous network of macrocell base stations that have similar antenna patterns and similar high-level transmit powers. The RAN 104 may be deployed as a heterogeneous network. In heterogeneous networks, small cell base stations may be used to provide small coverage areas, for example, coverage areas that overlap with the comparatively larger coverage areas provided by macrocell base stations. The small coverage areas may be provided in areas with high data traffic (or so-called “hotspots”) or in areas with weakmacrocell 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.

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

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

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

[0074] As illustrated in FIG. 1B, the 5G-CN 152 includes an Access and Mobility Management Function (AMF) 158A and a User Plane Function (UPF) 158B, which are shown as one component AMF / UPF 158 in FIG. 1 B for ease of illustration. The UPF 158B may serve as a gateway between the NG-RAN 154 and the one or more DNs. The UPF 158B may perform functions such as packet routing and forwarding, packet inspection and user plane policy rule enforcement, traffic usage reporting, uplink classification to support routing of traffic flows to the one or more DNs, quality of service (QoS) handling for the user plane (e.g., packet filtering, gating, uplink / downlink rate enforcement, and uplink traffic verification), downlink packet buffering, and downlink data notification triggering. The UPF 158B may serveas an anchor point for intra-Zinter-Radio Access Technology (RAT) mobility, an external protocol (or packet) data unit (PDU) session point of interconnect to the one or more D Ns, and / or a branching point to support a multi-homed PDU session. The UEs 156 may be configured to receive services through a PDU session, which is a logical connection between a UE and a DN.

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

[0076] The 5G-CN 152 may include one or more additional network functions that are not shown in FIG. 1B 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).

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

[0078] As shown in FIG. 1 B, the gNBs 160 and / or the ng-eNBs 162 may be connected to the 5G-CN 152 by means of an NG interface and to other base stations by an Xn interface. The NG and Xn interfaces may be established using direct physical connections and / or indirect connections over an underlying transport network, such as an internet protocol (IP) transport network. The gNBs 160 and / or the ng-eNBs 162 may be connected to the UEs 156 by means of a Uu interface. For example, as illustrated in FIG. 1B, gNB 160A may be connected to the UE 156A by means of a Uu interface. The NG, Xn, and Uu interfaces are associated with a protocol stack. The protocol stacks associated with the interfaces may be used by the network elements in FIG. 1 B to exchange data and signaling messages and may include two planes: a user plane and a control plane. The user plane may handle data of interest to a user. The control plane may handle signaling messages of interest to the network elements.

[0079] The gNBs 160 and / or the ng-eNBs 162 may be connected to one or more AMF / UPF functions of the 5G-CN 152, such as the AMF / UPF 158, by means of one or more NG interfaces. For example, the gNB 160A may beconnected 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-0 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.

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

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

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

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

[0084] 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 (MAGs) 212 and 222, radio link control layers (RLCs) 213 and 223, packet data convergence protocol layers (PDOPs) 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.

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

[0086] 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-gNB handover. The PDCPs 214 and 224 may perform packet duplication to improve the likelihood of the packet being received and, at the receiver, remove any duplicate packets. Packet duplication may be useful for services that require high reliability.

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

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

[0089] 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 ofdata units, belonging to the one or more logical channels, into / from Transport Blocks (TBs) delivered to / from the PHYs211 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 MACs212 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.

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

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

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

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

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

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

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

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

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

[0099] - a broadcast control channel (BOOH) 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;

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

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

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

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

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

[0105] - a broadcast channel (BOH) for carrying the MIB from the BCCH;

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

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

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

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

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

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

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

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

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

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

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

[0117] 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 MAGs 212 and 222, the RLCs 213 and 223, and the PDOPs 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.

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

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

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

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

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

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

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

[0125] T racking 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 mayperform a registration update with the ON to allow the ON to update the UE’s location and provide the UE with a new the UE registration area.

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

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

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

[0129] 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 may be transmitted over the air interface on a carrier frequency. The F parallel symbol streams may be mixed using an FFT block before being processed by the IFFT block. This operation produces Discrete Fourier Transform (DFT)-precoded OFDM symbols and may be used by UEs in the uplink to reduce the peak to average power ratio (PAPR). Inverse processing may be performed on the OFDM symbol at a receiver using an FFT block to recover the data mapped to the source symbols.

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

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

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

[0133] FIG. 8 illustrates an example configuration of a slot in the time and frequency domain for an NR carrier. The slot includes resource elements (REs) and resource blocks (RBs). An RE is the smallest physical resource in NR. An RE spans one OFDM symbol in the time domain by one subcarrier in the frequency domain as shown in FIG. 8. An RB spans twelve consecutive REs in the frequency domain as shown in FIG. 8. An NR carrier may be limited to a width of 275 RBs or 275x12 = 3300 subcarriers. Such a limitation, if used, may limit the NR carrier to 50, 100, 200, and 400 MHz for subcarrier 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.

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

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

[0136] 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 BMP may be defined by a subset of contiguous RBs on a carrier. A UEmay 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.

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

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

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

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

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

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

[0143] In an example, a base station may semi-statically configure a UE with one or more BWPs. A UE may switch an active BWP from a first BWP to a second BWP in response to receiving a DOI 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).

[0144] 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, DOI, expiration of a BWP inactivity timer, and / or an initiation of random access.

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

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

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

[0148] FIG. 10A illustrates the three GA configurations with two 00s. In the intraband, contiguous configuration 1002, the two 00s 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 00s are aggregated inthe 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).

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

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

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

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

[0153] 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 ormore other uplink CCs may be configured as a primary SCell (PSCell) 1061, an SCell 1062, and an SCell 1063. Uplink control information (UCI) related to the downlink CCs of the PUCCH group 1010, shown as UC1 1031, UC1 1032, and UC1 1033, may be transmitted in the uplink of the PCell 1021. Uplink control information (UCI) related to the downlink CCs of the PUCCH group 1050, shown as UC1 1071, UC1 1072, and UC1 1073, may be transmitted in the uplink of the PSCell 1061. In an example, if the aggregated cells depicted in FIG. 10B were not divided into the PUCCH group 1010 and the PUCCH group 1050, a single uplink PCell to transmit UCI relating to the downlink CCs, and the PCell may become overloaded. By dividing transmissions of UCI between the PCell 1021 and the PSCell 1061, overloading may be prevented.

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

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

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

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

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

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

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

[0161] The PBCH may use a QPSK modulation and may use forward error correction (FEC). The FEC may use polar coding. One or more symbols spanned by the PBCH may carry one or more DMRSs for demodulation of the PBCH. The PBCH may include an indication of a current system frame number (SFN) of the cell and / or a SS / PBCH block timing index. These parameters may facilitate time synchronization of the UE to the base station. The PBCH may include a master information block (MIB) used to provide the UE with one or more parameters. The MIB may be used by the UE to locate remaining minimum system information (RMSI) associated with the cell. The RMSI may include a System Information Block Type 1 (SIB1). The SIB1 may contain information needed by the UE to access the cell. The UE may use one or more parameters of the MIB to monitor PDCCH, which may be used to schedule PDSCH. The PDSCH may include the SIB1. The SIB1 may be decoded using parameters provided in the MIB. The PBCH may indicate an absence of SIB1. Based on the PBCH indicating the absence of SIB1 , the UE may be pointed to a frequency. The UE may search for an SS / PBCH block at the frequency to which the UE is pointed.

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

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

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

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

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

[0167] The base station may configure the UE to report CSI measurements. The base station may configure the UE to provide CSI reports periodically, aperiodically, or semi-persistently. For periodic CSI reporting, the UE may be configured with a timing and / or periodicity of a plurality of CSI reports. For aperiodic CSI reporting, the base station may request a CSI report. For example, the base station may command the UE to measure a configured CSI-RS resource and provide a CSI report relating to the measurements. For semi-persistent CSI reporting, the base station may configure the UE to transmit periodically, and selectively activate or deactivate the periodic reporting. The base station may configure the UE with a CSI-RS resource set and CSI reports using RRC signaling.

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

[0169] 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-MI MO, a DMRS configuration may support up to 4 orthogonal downlink DMRS ports per UE. A radio network may support (e.g., at least for CP-OFDM) a common DMRS structure for downlink and uplink, wherein a DMRS location, a DMRS pattern, and / or a scrambling sequence may be the same or different. The base station may transmit a downlink DMRS and a corresponding PDSCH using the same precoding matrix. The UE may use the one or more downlink DMRSs for coherent demodulation / channel estimation of the PDSCH.

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

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

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

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

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

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

[0176] 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 maytransmit 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 DOI formats. In an example, at least one DOI 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 DOI 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.

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

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

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

[0180] FIG. 11B illustrates an example of channel state information reference signals (CSI-RSs) that are mapped in the time and frequency domains. A square shown in FIG. 11 B may span a resource block (RB) within a bandwidth of a cell. A base station may transmit one or more RRC messages comprising CSI-RS resource configuration parameters indicating one or more CSI-RSs. One or more of the following parameters may be configured by higher layer signaling (e.g., RRC and / or MAC signaling) for a CSI-RS resource configuration: a CSI-RS resource configuration identity, anumber of CSI-RS ports, a OS I -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.

[0181] The three beams illustrated in FIG. 11 B may be configured for a UE in a UE-specific configuration. Three beams are illustrated in FIG. 11 B (beam #1 , beam #2, and beam #3), more or fewer beams may be configured. Beam #1 may be allocated with CSI-RS 1101 that may be transmitted in one or more subcarriers in an RB of a first symbol. Beam #2 may be allocated with CSI-RS 1102 that may be transmitted in one or more subcarriers in an RB of a second symbol. Beam #3 may be allocated with CSI-RS 1103 that may be transmitted in one or more subcarriers in an RB of a third symbol. By using frequency division multiplexing (FDM), a base station may use other subcarriers in a same RB (for example, those that are not used to transmit CSI-RS 1101) to transmit another CSI-RS associated with a beam for another UE. By using time domain multiplexing (TDM), beams used for the UE may be configured such that beams for the UE use symbols from beams of other UEs.

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

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

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

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

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

[0187] The UE may measure a quality of a beam pair link using one or more reference signals (RSs) comprising one or more SS / PBCH blocks, one or more CSI-RS resources, and / or one or more demodulation reference signals (DMRSs). A quality of the beam pair link may be based on one or more of a block error rate (BLER), an RSRP value, a signal to interference plus noise ratio (SINR) value, a reference signal received quality (RSRQ) value, and / or a CSI value measured on RS resources. The base station may indicate that an RS resource is quasi co-located (QCLed) with one or more DM-RSs of a channel (e.g., a control channel, a shared data channel, and / or the like). The RS resourceand 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.

[0188] 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 RRC_I DLE state and / or an RRC_I NACTI VE 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 PUCOH resource available) and / or acquire uplink timing (e.g., when uplink synchronization status is non-synchronized). The UE may initiate the random access procedure to request one or more system information blocks (SIBs) (e.g., other system information such as SIB2, SIB3, and / or the like). The UE may initiate the random access procedure for a beam failure recovery request. A network may initiate a random access procedure for a handover and / or for establishing time alignment for an SCell addition.

[0189] FIG. 13A illustrates a four-step contention-based random access procedure. Prior to initiation of the procedure, a base station may transmit a configuration message 1310 to the UE. The procedure illustrated in FIG. 13A comprises transmission of four messages: a Msg 1 1311, a Msg 2 1312, a Msg 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 2 1312 may include and / or be referred to as a random access response (RAR).

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

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

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

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

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

[0195] 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 preambletransmit 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_TRANSMISSION_COUNTER). The UE may determine that a random access procedure completed unsuccessfully, for example, if the number of preamble transmissions exceeds a threshold configured by the one or more RACH parameters (e.g., preambleTransMax).

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

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

[0198] The UE may transmit the Msg 3 1313 in response to a successful reception of the Msg 21312 (e.g., using resources identified in the Msg 21312). The Msg 3 1313 may be used for contention resolution in, for example, the contention-based random access procedure illustrated in FIG. 13A. In some scenarios, a plurality of UEs may transmita same preamble to a base station and the base station may provide an RAR that corresponds to a UE. Collisions may occur if the plurality of UEs interpret the RAR as corresponding to themselves. Contention resolution (e.g., using the Msg 3 1313 and the Msg 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 3 1313 (e.g., a C-RNTI if assigned, a TC-RNTI included in the Msg 2 1312, and / or any other suitable identifier).

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

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

[0201] 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 21312 illustrated in FIG. 13A, respectively. As will be understood from FIGS. 13A and 13B, the contention- free random access procedure may not include messages analogous to the Msg 3 1313 and / or the Msg 41314.

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

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

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

[0205] Msg A 1331 may be transmitted in an uplink transmission by the UE. Msg A 1331 may comprise one or more transmissions of a preamble 1341 and / or one or more transmissions of a transport block 1342. The transport block 1342 may comprise contents that are similar and / or equivalent to the contents of the Msg 3 1313 illustrated in FIG. 13A. The transport block 1342 may comprise UCI (e.g., an SR, a HARQ ACK / NACK, and / or the like). The UE may receive the Msg B 1332 after or in response to transmitting the Msg A 1331. The Msg B 1332 may comprise contents that are similar and / or equivalent to the contents of the Msg 2 1312 (e.g., an RAR) illustrated in FIGS. 13A and 13B and / or the Msg 41314 illustrated in FIG. 13A.

[0206] The UE may initiate the two-step random access procedure in FIG. 130 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.

[0207] 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 transportblock 1342 (e.g., a PUSCH) may be multiplexed using FDM, TDM, and / or CDM. The RACH parameters may enable the UE to determine a reception timing and a downlink channel for monitoring for and / or receiving Msg B 1332.

[0208] 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 (I MSI)). 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 MOS); 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).

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

[0210] 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 (DOI). In some scenarios, the PDCCH may be a group common PDCCH (GC-PDCCH) that is common to a group of UEs.

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

[0212] DCIs may be used for different purposes. A purpose may be indicated by the type of RNTI used to scramble the CRC parity bits. For example, a DCI having CRC parity bits scrambled with a paging RNTI (P-RNTI) may indicate paging information and / or a system information change notification. The P-RNTI may be predefined as “FFFE” in hexadecimal. A DCI having CRC parity bits scrambled with a system information RNTI (SI-RNTI) may indicate a broadcast transmission of the system information. The SI-RNTI may be predefined as “FFFF” in hexadecimal. A DCI having CRC parity bits scrambled with a random access RNTI (RA-RNTI) may indicate a random access response (RAR). A DCI having CRC parity bits scrambled with a cell RNTI (C-RNTI) may indicate a dynamically scheduled unicast transmission and / or a triggering of PDCCH-ordered random access. A DCI having CRC parity bits scrambled with a temporary cell RNTI (TC-RNTI) may indicate a contention resolution (e.g., a Msg 3 analogous to the Msg 3 1313illustrated in FIG. 13A). Other RNTIs configured to the UE by a base station may comprise a Configured Scheduling RNT I (CS-RNTI), a Transmit Power Control-PUCOH 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.

[0213] Depending on the purpose and / or content of a DCI, the base station may transmit the DCIs with one or more DCI formats. For example, DCI format 0_0 may be used for scheduling of PUSCH in a cell. DCI format 0_0 may be a fallback DCI format (e.g. , with compact DCI payloads). DCI format 0_1 may be used for scheduling of PUSCH in a cell (e.g., with more DCI payloads than DCI format 0_0). DCI format 1_0 may be used for scheduling of PDSCH in a cell. DCI format 1_0 may be a fallback DCI format (e.g., with compact DCI payloads). DCI format 1_1 may be used for scheduling of PDSCH in a cell (e.g., with more DCI payloads than DCI format 1_0). DCI format 2_0 may be used for providing a slot format indication to a group of UEs. DCI format 2_1 may be used for notifying a group of UEs of a physical resource block and / or OFDM symbol where the UE may assume no transmission is intended to the UE. DCI format 2_2 may be used for transmission of a transmit power control (TPC) command for PUCCH or PUSCH. DCI format 2_3 may be used for transmission of a group of TPC commands for SRS transmissions by one or more UEs. DCI format(s) for new functions may be defined in future releases. DCI formats may have different DCI sizes, or may share the same DCI size.

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

[0215] 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 at a third symbol in the slot. A fourth CORESET 1404 occurs at the seventh symbol in the slot. CORESETs may have a different number of resource blocks in frequency domain.

[0216] 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 frequencydiversity) or a non-interleaved mapping (e.g., for the purposes of facilitating interference coordination and / or frequency- selective transmission of control channels). The base station may perform different or same CCE-to-REG mapping on different CORESETs. A CORESET may be associated with a CCE-to-REG mapping by RRC configuration. A CORESET may be configured with an antenna port quasi co-location (QCL) parameter. The antenna port GCL parameter may indicate QCL information of a demodulation reference signal (DMRS) for PDCCH reception in the CORESET.

[0217] The base station may transmit, to the UE, RRC messages comprising configuration parameters of one or more CORESETs and one or more search space sets. The configuration parameters may indicate an association between a search space set and a CORESET. A search space set may comprise a set of PDCCH candidates formed by CCEs at a given aggregation level. The configuration parameters may indicate: a number of PDCCH candidates to be monitored per aggregation level; a PDCCH monitoring periodicity and a PDCCH monitoring pattern; one or more DCI formats to be monitored by the UE; and / or whether a search space set is a common search space set or a UE- specific search space set. A set of CCEs in the common search space set may be predefined and known to the UE. A set of CCEs in the UE-specific search space set may be configured based on the UE’s identity (e.g., C-RNTI).

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

[0219] 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 downlinktransmission. 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 (PUCOH) ora physical uplink shared channel (PUSCH). The UE may transmit the uplink control signaling via a PUCOH using one of several PUCOH formats.

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

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

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

[0223] FIG. 15 illustrates an example of a wireless device 1502 in communication with a base station 1504 in accordance with embodiments of the present disclosure. The wireless device 1502 and base station 1504 may be part of a mobile communication network, such as the mobile communication network 100 illustrated in FIG. 1A, the mobile communication network 150 illustrated in FIG. 1 B, or any other communication network. Only one wireless device 1502 and one base station 1504 are illustrated in FIG. 15, but it will be understood that a mobile communication network may include more than one UE and / or more than one base station, with the same or similar configuration as those shown in FIG. 15.

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

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

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

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

[0228] 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 Ml MO or multi-antenna techniques, such as spatial multiplexing (e.g., single-user MIMO or multi-user MIMO), transmit / receive diversity, and / or beamforming. In other examples, the wireless device 1502 and / or the base station 1504 may have a single antenna.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0242] 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 subheader of a second MAC CE. For example, an LCID given by 111011 in a MAC subheader may indicate that the MAC CE associated with the MAC subheader is a Long DRX command MAC CE.

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

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

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

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

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

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

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

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

[0251] In an example, the one or more cells may comprise a plurality of one or more SCells, depending on capabilities of the wireless device. When configured with CA, the base station and / or the wireless device may employ an activation / deactivation mechanism of an SCell to improve battery or power consumption of the wireless device.When the wireless device is configured with the one or more SCells, the base station may activate or deactivate (e.g., via MAC CE or DOI) 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 / Deactivation MAC CE.

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

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

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

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

[0256] 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 PDCOH; not transmit PUCOH; not transmit SRS, not receive DL-SCH; clear any configured downlink assignment and configured uplink grant of configured grant Type 2; and / or suspend any configured uplink grant of configured Type 1.

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

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

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

[0260] A search space set may be a TypeO-PDCCH CSS set configured by the pdcch-ConfigSI B 1 (e.g., in MIB) or by searchSpaceSI B 1 in the PDCCH-ConfigCommon or by searchSpaceZero in the PDCCH-ConfigCommon.

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

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

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

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

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

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

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

[0268] For example, the one or more serving cell configuration parameters (e.g., ServmgCellConfigCommon) may comprise / indicate the cell-specific UL / DL TDD configuration(s) (e.g., TDD-UL-DL-ConfigCommon).

[0269] The one or more serving cell configuration parameters (e.g., ServingCellConfig) may comprise / indicate the UE-specific UL / DL TDD configuration(s) (e.g., TDD-UL-DL-ConfigDedicated).

[0270] As shown in FIG. 17, the one or more configuration parameters may comprise one or more TDD configuration parameters. The one or more TDD configuration parameters may be / comprise configuration parameters provided / indicated / configured by the UL / DL TDD configuration(s). The one or more TDD configuration parameters may comprise one or more common TDD configuration parameters (e.g., TDD-UL-DL-ConfigCommon and / or TDD-UL-DL- ConfigDedicated).

[0271] For each serving cell, one or more common TDD configuration parameters may indicate / configure slot format of a plurality of slots. FIG. 18 shows examples of slot format in TDD carrier. The plurality of carriers may comprise one or more consecutive slots.

[0272] A symbol in a slot of the one or more consecutive slots may be an Uplink (‘U7UL) symbol for uplink transmission(s).

[0273] A symbol in a slot of the one or more consecutive slots may be a downlink (‘D7DL) for downlink reception(s).

[0274] In some implementations, a symbol in a slot of the one or more consecutive slots may be a flexible (‘F’) symbol, wherein the slot format / direction may be determined 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 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 for interference control and / or power saving. For example, the network may use a slot format ‘F’ on one or more symbols to selectively initiate / trigger random access (RA) for a particular wireless device. Other wireless devices may not be allowed to transmit or receive on the one or more symbols, resulting in reduced interference for the wireless device.

[0275] For example, the one or more common TDD configuration parameters may comprise at least one of: a reference subcarrier spacing (SOS) pref and / or at least one TDD pattern. As shown in FIG. 18, the at least one TDD pattern may comprise a first TDD pattern (e.g., patteml) and / or a second TDD pattern (e.g., pattern?).

[0276] A 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 ds(otswith only downlink symbols (e.g., DL slot(s)); a number of downlink symbols dsym(e.g., DL symbol(s)); a number of slots uslotswith only uplink symbols (e.g., UL slot(s)); a number of uplink symbols usym(e.g., UL symbol(s)). FIG. 18 also shows a DL slot, an UL slot, and a slot comprising both UL symbol(s) and DL symbol(s).

[0277] Corresponding to each TDD pattern, a TDD periodicity may comprise S = P. 2^ (consecutive) slots with SOS configuration pref. The one or more consecutive slots may comprise= P .2^ (consecutive) slots (of the first TDD pattern) and / or S2= P2.2^ (consecutive) slots (of the second TDD pattern). The TDD periodicity P may be a summation of a first TDD periodicity (of the first TDD pattern) and a second TDD periodicity P2(of the first TDD pattern), e.g., P = P±+ P2.

[0278] From Si slots (i=1 corresponding to the first TDD pattern or i=2 corresponding to the second TDD pattern), a first / initial / starting / earliest dslotsslots may comprise one or more downlink symbols. From Stslots, a last / fin al / endin g / latest uslotsslots may comprise one or more uplink symbols. A dsymsymbols after the first dslotsslots may comprise one or more downlink symbols. A usymsymbols before the last uslotsslots may comprise one or more uplink symbols. A remaining (S - dslots- uslots). N^b- dsym- usymsymbols may comprise one or more flexible symbols. The one or more flexible symbols may comprise at least one flexible slot (see FIG. 18).

[0279] 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 one or more flexible symbols / slots of the one or more consecutive slots configured by the TDD-UL-DL- ConfigCommon.

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

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

[0282] 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 slotconfiguration 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.

[0283] Using the one or more TDD configuration parameters the wireless device may determine slot format of the one or more consecutive slots. Using the one or more UE-specific TDD configuration parameters the wireless device may determine symbol format of the one or more symbols.

[0284] 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 DOI 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.

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

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

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

[0288] An SFI-index field value in the DOI 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 DOI format 2_0; and / or at least one slot format combination (e.g., slotFormatCombinations)of the plurality of slot format combinations.

[0289] 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 DOI format (e.g., slotFormatCombinationld); and / or at least one reference SOS configuration.

[0290] 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. 17 also shows some examples of the one or more TDD rules.

[0291] According to / based on the one or more TDD rules, a wireless device may consider (DL) symbols in a DL slot of the one or more consecutive slots to be available / allowable for DL receptions. The wireless device may receive DLsignals / 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.

[0292] According to / based on the one or more TDD rules, a wireless device may consider (UL) symbols in an UL slot of the one or more consecutive slots to be avai lable / allowable for UL transmissions. The wireless device may transmit UL signals / channels (e.g., PUSCH, PUCOH, 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.

[0293] The one or more configuration parameters may not configure a wireless device to monitor PDCOH for the DOI 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 one or more consecutive 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 DOI scheduling / indicating / triggering the reception of the DL signals / channels in during the set of flexible symbols.

[0294] The one or more configuration parameters may not configure a wireless device to monitor PDCOH 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 one or more consecutive slots, the wireless device may transmit UL signals / channels (e.g., PUSCH, PUCCH, PRACH, or SRS) in the set of symbols of the slot. For example, the wireless device may receive a DCI, a RAR UL grant, fallbackRAR UL grant, or successRAR scheduling / indicating / triggering the transmission of the UL signals / channels in during the set of flexible symbols.

[0295] 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 a slot of the one or more consecutive 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, or a SRS) in at least one symbol of the set of symbols. Based on detecting / receiving the DCI format scheduling / triggering / indicating the transmission of the UL signal / channel in at least one symbol of the set of symbols of the slot, the wireless device may not receive the DL signal / channel (e.g., PDCCH, or a PDSCH, or a CSI- RS, or a DL PRS) in the set of symbols of the slot. The wireless device may transmit the UL signal / channel (e.g., a PUSCH, a PUCCH, a PRACH, or an SRS) in at least one symbol of the set of symbols of the slot.

[0296] According to / based on the one or more TDD rules, for a set of flexible symbols of a flexible slot of the one or more consecutive 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 symbols and dedicated higher layer parameters configuring reception by the wireless device (e.g., SPS PDSCH, P / SP CSI-RS, SSB, CORESET) in the set of flexible symbols. For example, the one or more configuration parameters may not configure CG-PUSCH transmission occasions and SPS PDSCH reception occasions in the set of flexible symbols.

[0297] According to / based on the one or more TDD rules, for a set of symbols of a slot (of the one or more consecutive 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, PUCOH, 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-PositionsInBurst in ServmgCellConfigCommon').

[0298] According to / based on the one or more TDD rules, for a set of symbols of a slot (of the one or more consecutive 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.

[0299] According to / based on the one or more TDD rules, for a set of symbols of a slot (of the one or more consecutive 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.

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

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

[0302] FIG. 19 shows an example of PDSCH resource mapping per an aspect of the present disclosure. The PDSCH resource mapping may be based on one or more rate matching configuration parameters. The PDSCH resource mapping may be based on ZP CSI-RS resource sets.

[0303] The PDSCH resource mapping may be a PDSCH resource mapping with RB level granularity, e.g., when one or more rate matching configuration parameters configure / indicate the PDSCH resource mapping.

[0304] The PDSCH resource mapping may be a PDSCH resource mapping with RE level granularity, e.g., when the PDSCH resource mapping is based on the ZP CSI-RS resource sets.

[0305] Based on the PDSCH resource mapping the wireless device may determine reserved / unavailable (time / frequency) resources for receiving PDSCH(s). FIG. 20 and FIG. 21A show examples of rate matching configurations per an aspect of the present disclosure. The one or more configuration parameters (e.g. , pdsch- Conf / gMult / cast, ServingCellConfig ServingCellConfigCommon, pdsch-ConfigMCCH and / or pdsch-ConfigMTCH} may comprise the one or more rate matching configuration parameters.

[0306] The one or more rate matching configuration parameters may correspond to PDSCH. For example, the one or more rate matching configuration parameters may comprise / indicate one or more (a plurality) of rate match patterns (RMPs), e.g., rateMatchPattemToAddModList. rateMatchPattemToAddModList may comprise / configure / indicate at a plurality of RMP configurations. Each RMP configuration of the plurality of RMP configurations may correspond to an RMP of the one or more RMPs. In the present disclosure, an RMP may interchangeably use for an RMP configuration.

[0307] In the present disclosure, “an RMP” may interchangeably use “PDSCH rate matching pattern” or “PDSCH RMP”.

[0308] The example of FIG. 20 shows an example that the PDSCH-Config comprises / includes the one or more RMPs (e.g., one or more RMP configurations). Other cases that pdsch-ConfigMCCH and / or pdsch-ConfigMTCH comprise / include the one or more RMPs may be possible. In some cases, the PDSCH-Config and / or pdsch- ConfigMCCH and / or pdsch-ConfigMTCH may comprises / includes the one or more RMPs. Each RMP (configuration) of the one or more RMPs (RMP configurations) may be associated with / correspond to an RMP index / ID / number (e.g., rateMatchPattemld).

[0309] In some examples, the one or more rate matching configuration parameters may comprise / configure at least one RMP group (e.g., rateMatchPattemGroupI and rateMatchPattemGroup2). For example, an RMP group of the at least one RMP group may comprise a configured number (e.g., maxNrofRateMatchPatternsPerGroup, e.g., 6 or 8) RMPs of the one or more RMPs.

[0310] The wireless device may, based on the one or more RMPs, determine a fourth set of RBs in (DL or flexible) symbols of a slot. The fourth set of RBs may be reserved resources for PDSCH reception(s). The fourth set of RBs may not be available for PDSCH reception(s). As shown in FIG. 19 the fourth set of RBs may indicate a plurality of reserved RBs for receiving PDSCH in symbols of a slot. The fourth set of RBs may indicate a plurality of unavailable RBs in the symbols of the slot. The slot may belong to one or more consecutive slots. The slot may be a downlink slot or a flexible slot. The fourth set of RBs may comprise a set of unavailable / reserved REs for receiving PDSCHs. The set of unavailable / reserved REs may comprise time / frequency resources, e.g., the time-domain reserved resources and / or the frequency-domain reserved resources.

[0311] In some examples, a PDSCH of the PDSCH receptions may be (group-common) GC-PDSCH, e.g., multicast / broadcast PDSCH. The one or more configuration parameters (e.g., pdsch-ConfigMulticast) may configure the (group-common) GC-PDSCHs.

[0312] For example, an RMP of the one or more RMPs may be a cell-level RMP. An RMP of the one or more RMPs may be a bwp-level RMP. The one or more configuration parameters (e.g., PDSCH-conflg) may indicate whether an RMP of the one or more RMPs is the cell-level RMP or the bwp-level RMP (see also FIG. 20).

[0313] For example, the one or more rate matching configuration parameters may comprise / indicate a configured number (e.g., maxNrofRateMatchPatterns, e.g., 1, 2., 3, or 4) of RMPs per BWP, e.g., bwp-level RMPs. The one or more RMPs may comprise the configured number of RMPs per BWP.

[0314] For example, the one or more rate matching configuration parameters may comprise / indicate a configured number (e.g., maxNrofRateMatchPatterns, 1 , 2., 3, or 4) of RMPs per cell (e.g., serving cell). The one or more RMPs may comprise the configured number of RMPs per cell, e.g., cell-level RMPs.

[0315] FIG. 21A further shows an example of an RMP of the one or more RMPs. The RMP (within a BWP) may configure / indicate (a pair of) reserved (or unavailable) resources, e.g., for receiving PDSCH(s). In an example, an RMP configuration (e.g., RateMatchPattern corresponding to the RMP with index / ID rateMatchPatternld), of the one or more RMP configurations may indicate / configure (the pair of) reserved resources corresponding to / associated with a numerology subcarrlerSpacIng. The indicated numerology may be the numerology of a cell (e.g., a serving cell), e.g., when the RMP is a cell-level RMP. The numerology may be a numerology of the BWP, e.g., when the RMP is a bwp- level RMP.

[0316] In the present disclosure, “reserved resources” may refer to “unavailable resources” or “excluded resources” or “retrained resources” or “inaccessible resources”. The wireless device may avoid using the reserved resources for receiving PDSCHs (see FIG. 19). The reserved resources may comprise time-domain reserved resources (e.g., symbols) and / or frequency-domain reserved resources (RBs). In the present disclosure, time-domain reserved resources and frequency-domain reserved resources may be referred to by “the pair of reserved resources”.

[0317] The (the pair of) reserved resources may indicate / configure a subset of RBs, e.g., a subset of RBs of the fourth set of RBs. For example, the fourth set of RBs may comprise a plurality of subsets of RBs. Each subset of RBs of the fourth set of RBs may correspond to / be associated with an RMP (with index / ID of rateMatchPatternld).

[0318] In an example, the plurality of RMP configurations may configure / indicate a first plurality of bitmap groups. The wireless device may, for receiving PDSCH via a serving cell and / or using a BWP, determine the reserved / unavailable RBs in the symbols of the slot based on the plurality of bitmap groups. For example, in each symbol of a slot the wireless device may determine the fourth set of RBs based on the plurality of bitmap groups.

[0319] Each bitmap group of the first plurality of bitmap groups may correspond to an RMP configuration of the plurality of RMP configurations. Each bitmap group of the first plurality of bitmap groups may comprise one or more bitmaps corresponding to the RMP configuration.

[0320] A first RMP configuration of the RMP (with index rateMatchPatternld) may indicate one or more first bitmaps (e.g., bitmaps), e.g., a first bitmap group of the first plurality of the bitmap groups. A bitmap may be an RB level bitmap. The bitmap, of the one or more first bitmaps, may comprise an RB level bitmap and / or a symbol level bitmap (e.g., apair of RB level bitmap and the symbol level bitmap). The first bitmap group may configure / comprise / indicate (e.g., by resourceBlocks of the corresponding RateMatchPattern) a first subset of the RBs of the fourth set of RBs. A bitmap of the first bitmap group may indicate / configure the reserved / unavailable RBs for the PDSCH. The RB level bitmap of the bitmap may have a sin gle / on RB (e.g., 1 RB) granularity. The symbol level bitmap of the bitmap may span one or two slots (e.g., by symbolsinResourceBlock given by RateMatchPattern). For example, a bit value equal to 1 in the bitmap (e.g., the RB level bitmap and / or symbol level bitmap) may indicate that the corresponding resource (in time and frequency) is not available for PDSCH (see also FIG. 19). In a symbol of the slot, the pair of reserved resources may be based on the bitmap (e.g., the RB level bitmap and / or symbol level bitmap) corresponding to the symbol of the slot.

[0321] The first RMP configuration may indicated / configure one or more rate-matching time-domain patterns. For a first bitmap (e.g., for each pair of RB and symbol level bitmaps) of the one or more first bitmaps of a first RMP, the first RMP configuration may indicate a first rate-matching time-domain pattern (e.g., configured / indicated by periodicityAndPattern given by RateMatchPattern) of the one or more rate-matching time-domain patterns. The first rate matching time-domain pattern may correspond to / associated with the first bitmap of the first bitmap group. Each bit of the periodicityAndPattern may correspond to a unit equal to a duration of the symbol level bitmap of the bitmap of the one or more first bitmaps. A bit value equal to 1 may indicate that the pair of RB and symbol level bitmaps (the bitmap of the one or more bitmaps) is present in the unit, e.g., the subset of RB corresponding to the first RM comprises the RB identified by the RB level bitmap of the first bitmap. For example, periodicityAndPattern may indicate at least one bitmap of the one or more first bitmaps that are used for determining the subset of RBs correspond to / associated with the RMP. The periodicityAndPattern can be {1 , 2, 4, 5, 8, 10, 20 or 40} units long, but maximum of 40 msec. A first / starting / initial symbol of the periodicityAndPattern every 40 msec / XRMP periods may be a first / initial / starting symbol in frame r mod 4 = 0, where XRMP is the duration of periodicityAndPattern in units of msec.

[0322] When periodicityAndPattern is not configured for a bitmap of the one or more first bitmaps of the first RMP configuration, for a symbol level bitmap of the bitmap spanning two slots, the bits of the first and second slots correspond respectively to even and odd slots of a radio frame.

[0323] When periodicityAndPattern is not configured for a pair of the one or more first bitmaps of the first RMP configuration, for a symbol level bitmap of the bitmap spanning one slot, the bits of the slot correspond to every slot of a radio frame.

[0324] In one example, the at least one RMP group (rateMatchPatternGroupI and rateMatchPatternGroup2) may comprise a first bitmap of the one or more first bitmaps of the first RMP configuration of the rateMatchPattern ToAddModList.

[0325] In one example, the first bitmap of the one or more first bitmaps of the first RMP configuration may belong only to one RMP group of the at least one RMP group.

[0326] In another example, a second bitmap of the one or more first bitmaps of the first RMP configuration may belong to every / each RMP group of the at least one RMP group, e.g., both rateMatchPattemGroupI and rateMatchPattemGroup2 comprise the second bitmap of the one or more first bitmaps of the first RMP configuration.

[0327] In the present disclosure, “group” may refer to “combination” or “union” or “collection” or “grouping”.

[0328] An RMP group, of the at least one RMP group, may comprise a group of the subset of RBs. For example, a first RMP group (e.g., rateMatchPattemGroupI may comprise a first group of the subset of RBs. A second group (e.g., rateMatchPatternGroup2) may comprise a second group of the subset of RBs. The fourth set of RBs may comprise the first group of the subset of RBs and the second group of the subset of RBs.

[0329] In FIG. 19, a first RMP periodicity (e.g., a first a rate-matching time-domain pattern, with a duration of XRMPI units) may correspond to a first RMP (with a first RMP ID) of the one or more RMPs. A first RMP configuration of the rateMatchPatternToAddModList may configure the first RMP. A second RMP periodicity (e.g., a second a rate-matching time-domain pattern with a duration of XRMP2 units) may correspond to a second RMP (with a first RMP ID) of the one or more RMPs. A second RMP configuration of the rateMatchPatternToAddModList may configure the second RMP. In each symbol, and for receiving each PDSCH, the wireless device may determine the fourth set of RBs based on the plurality of bitmap groups configured by the plurality of RMP configurations.

[0330] In another example, the first RMP periodicity may correspond to a first bitmap of the one or more first bitmaps of the first RMP configuration. The second RMP periodicity may correspond to a second bitmap of the one or more first bitmaps of the first RMP configuration.

[0331] In yet another example, the first RMP periodicity may correspond to a first bitmap of the one or more first bitmaps of the first RMP configuration. The second RMP periodicity may correspond to a first bitmap of the one or more second bitmaps of a second RMP configuration.

[0332] FIG. 19 also shows one example that a symbol level bitmap (of an RMP configuration of an RMP of the one or more RMPs) spans / comprises one slot and another example that the symbol level bitmap (of the RMP configuration) spans / comprises two slots.

[0333] FIG. 19 further shows several examples of the reserved RBs configured by the one or more rate matching configuration parameters. The reserved RBs may correspond to an RMP of the one or more RMPs. The reserved RBs may corresponding to at least two RMPs of the one or more RMPs. The reserved RBs may corresponding to the at least one RMP group. The reserved RBs may comprise a union / combination of at least one RMP of the one or more RMPs.

[0334] In the example of FIG. 19, the fourth set of RBs may comprise N1 >1 RBs (e.g., in symbols of slots #m and nm), and / or N2>1 RBs (e.g., in symbols of slots #m and nm) and / or N3>1 RBs (e.g., in symbols of slots #n? and nm+i), and / or N 1 >4 RBs (e.g., in symbols of slots #n? and nm+i). The wireless device may exclude (or not use) the fourth set of RBs from time / frequency resources that are configured / indicated for receiving PDSCH(s).

[0335] For example, in a symbol of a slot, the corresponding reserved RBs may be based on the first bitmap of the one or more first bitmaps of the first RMP configuration. In one example, the wireless device may determine at least one of N1 RBs, N2 RBs, N3 RBs and / or N4 RBs based on the first bitmap of the one or more first bitmaps of the first RMP configuration.

[0336] For example, in the symbol of the slot, the corresponding reserved RBs may further be based on a first bitmap of one or more second bitmaps of the first RMP configuration. The wireless device may further determine at least one of N1 RBs, N2 RBs, N3 RBs and / or N4 RBs based on the first bitmap of the one or more second bitmaps of the first RMP configuration.

[0337] For example, in the symbol of the slot, the corresponding reserved RBs may further be based on a first bitmap of one or more first bitmaps of a second RMP configuration. The wireless device may further determine at least one of N1 RBs, N2 RBs, N3 RBs and / or N4 RBs based on the first bitmap of the one or more first bitmaps of the second RMP configuration.

[0338] The one or more RMPs may indicate / comprise / configure resources patterns for rate match PDSCH around. The wireless device may use the one or more RMPs (indicated resources patterns) for rate match PDSCH around. In some examples, the wireless device may rate match (the PDSCH) around a union (or combination) of all resources indicated in the one or more RMPs.

[0339] A PDSCH reception of the PDSCH receptions (in FIG. 19) may be scheduled / indicated by a DCI format. A PDCCH (in / during a PDCCH candidate) may provide the DCI format. The PDCCH / DCI format may be with CRC scrambled by C-RNTI, MCS-C-RNTI, CS-RNTI, G-RNTI, G-CS-RNTI, MCCH-RNTI, multicast-MCCH-RNTI. The wireless device may, for receiving the PDSCH in symbols of a slot, determine the fourth set of RBs being reserved (not being available) for receiving the PDSCH.

[0340] In an example, the wireless device may receive / detect the DCI (format) scheduling / indicating the PDSCH. The DCI may comprise a rate matching indicator (RMI) field. The RMI field of the DCI may comprise 0, 1 , or 2 bits corresponding to the at least one RMP group (rateMatchPattemGroupI and rateMatchPatternGroup2). For example, the RMI field of the DCI may indicate an RMP group of the at least one RMP group. The RMI field of the DCI may indicate a first RMP group of the at least one RMP group and / or a second RMP group of the at least one RMP group. The wireless device may determine the reserved resources (e.g., the fourth set of RBs) based on the indicated RMP group(s) by the DCI. For example, the fourth set of RBs may comprise a union of subset of RBs corresponding to the indicated RMP group(s) by the DCI. A subset of RBs of the union of subset of RBs may correspond to an RMP of the one or more RMP. The RMP may belong to at least one RMP group of the indicated RMP group(s) by the DCI. The union of subset of RBs may comprise REs that are not available for receiving the PDSCH. The wireless device may exclude the union of subset of RBs time-frequency resources for receiving the PDSCH.

[0341] If a PDCCH candidate that provides a DOI format is mapped to one or more REs that overlap with REs of any RB in the fourth set of RBs in symbols of the slot, the wireless device may not expect to monitor (or not monitor) the PDCCH candidate.

[0342] For example, at least one PDSCH reception(s) may be configured by the one or more configuration parameters (e.g., SPS-Config). The wireless device may receive (SPS) PDSCH receptions after activation by a DCI. The wireless device may, for receiving a SPS PDSCH in symbols of a slot, determine the fourth set of RBs being reserved (not being available) for receiving the SPS PDSCH.

[0343] In an example, the wireless device may receive / detect the DCI (format) activating the SPS PDSCH. The DCI may comprise the rate matching indicator (RMI) field. For example, the RMI field of the DCI may indicate an RMP group of the at least one RMP group. The RMI field of the DCI may indicate a first RMP group of the at least one RMP group and / or a second RMP group of the at least one RMP group. The wireless device may determine the reserved resources (e.g., the fourth set of RBs) based on the indicated RMP group(s) by the activating DCI. For example, the fourth set of RBs may comprise a union of subset of RBs corresponding to the indicated RMP group(s) by the DCI. A subset of RBs of the union of subset of RBs may correspond to an RMP of the one or more RMP. The RMP may belong to at least one RMP group of the indicated RMP group(s) by the DCI. The union of subset of RBs may comprise REs that are not available for receiving the SPS PDSCH. The wireless device may exclude the union of subset of RBs time-frequency resources for receiving the SPS PDSCH.

[0344] As shown in FIG. 20 and FIG. 21 A, an RMP of the one or more RMP may correspond to a CORESET with (or corresponding to) or coreset ID / index / number (e.g., contro / ResourceSetld, e.g., #1 ). The CORESET may correspond to ControlResourceSetZero. The CORESET may indicate a PDSCH rate matching pattern (e.g., the RMP). For example, within a BWP, the one or more configuration parameters (e.g., Contro / ResourceSet with contro / ResourceSetld or ControlResourceSetZero) may configure / indicate a frequency domain resource of the CORESET. The one or more configuration parameters (e.g., SearchSpace / searchSpaceZero associated with the CORESET) may configure / indicate a time domain resource of the CORESET. The time domain resource of the CORESET may be based on coreset periodicity (e.g., monitoringSlotPeriodicityAndOffset), duration and monitoringSymbolsWithinSlot of search-space-sets configured by SearchSpace and time domain resource of search-space-set zero configured by search SpaceZero associated with the CORESET as well as CORESET duration configured by Contro / ResourceSet with contro / ResourceSetld or ControlResourceSetZero.

[0345] A subset of RBs of the fourth set of RBs may comprise the frequency domain resource of the CORESET and time domain resource of the CORESET. If a PDSCH scheduled by a PDCCH overlaps (e.g., in slot #nn+c in FIG. 19) with resources in the CORESET (e.g., with index 1 ) containing the PDCCH, the fourth set of RBs may comprise timefrequency resources corresponding to a union of the detected PDCCH that scheduled the PDSCH and associated PDCCH DM-RS. When the PDCCH reception includes two PDCCH candidates from two respective search space sets, the fourth set of RBs may comprise time-frequency resources corresponding to a union of the two PDCCH candidatesscheduling the PDSCH and the associated PDCCH DM-RS. For example, the associated PDCCH DM-RS are DM-RS in all REGs of the CORESET. In another example, the associated DM-RS are DM-RS in REGs of the PDCCH.

[0346] In some examples, the wireless device may, for rate match PDSCH around, indicate at least one rate matching capability to the base station. FIG. 22 shows an example of UE capabilities for rate match PDSCH around. For example, the wireless device may transmit one or more capability (U E-capability) messages to the base station. The one or more capability may comprise / indicate a first set of capabilities. The first set of capabilities may comprise the at least one rate matching capability.

[0347] In one example, the at least one rate matching capability may comprise a first rate matching capability (e.g., rateMatchingResrcSetSemi-Static). FIG. 22 further shows an example definition of the first rate matching capability. The first rate matching capability may indicate whether the wireless device supports receiving PDSCH with resource mapping that excludes the REs (e.g., the fourth set of RBs) corresponding to resource sets configured with RB-symbol level granularity indicated by bitmaps (e.g., the plurality of bitmap groups) and controlResourceSet (see pattemType in RateMatchPattern) following the semi-static configuration (e.g., the plurality of RMP configurations).

[0348] In one implementation, the one or more capability may indicate that the wireless device supports receiving PDSCH with resource mapping that excludes the REs (e.g., the fourth set of RBs) corresponding to resource sets configured with RB-symbol level granularity indicated by bitmaps (e.g., the plurality of bitmap groups) and controlResourceSet (see pattemType in RateMatchPattern) following the semi-static configuration (e.g., the plurality of RMP configurations). For example, the first set of capabilities may comprise the first rate matching capability. The base station may transmit the one or more rate matching configuration parameters (e.g., the plurality of RMP configurations) to the wireless device. The wireless device may, based on indicating the first capability message, may determine / declare the fourth set of RBs as unavailable for receiving PDSCHs.

[0349] In another implementation, the one or more capability may indicate that the wireless device does not support receiving PDSCH with resource mapping that excludes the REs (e.g., the fourth set of RBs) corresponding to resource sets configured with RB-symbol level granularity indicated by bitmaps (e.g., the plurality of bitmap groups) and controlResourceSet (see pattemType in RateMatchPattern) following the semi-static configuration (e.g., the plurality of RMP configurations). In some aspects, the one or more capability may not indicate that the wireless device supports receiving PDSCH with resource mapping that excludes the REs (e.g., the fourth set of RBs) corresponding to resource sets configured with RB-symbol level granularity indicated by bitmaps (e.g., the plurality of bitmap groups) and controlResourceSet (see pattemType in RateMatchPattern) following the semi-static configuration (e.g., the plurality of RMP configurations). For example, the first set of capabilities may not comprise the first rate matching capability. The base station may not transmit the one or more rate matching configuration parameters (e.g., the plurality of RMP configurations) to the wireless device. The wireless device may, based on not indicating the first capability message, may avoid determining / declaring the fourth set of RBs as unavailable for receiving PDSCHs.

[0350] In another example, the at least one rate matching capability may comprise a second rate matching capability (e.g., rateMatchingResrcSetDynamic). FIG. 22 further shows an example definition of the second rate matching capability. The second rate matching capability may indicate whether the wireless device supports receiving PDSCH with resource mapping that excludes the REs (e.g., the fourth set of RBs) corresponding to resource sets configured with RB-symbol level granularity indicated by bitmaps (e.g., the plurality of bitmap groups) and controlResourceSet (see pattemType in RateMatchPattern) based on a dynamic indication (e.g., the RMI field) in a scheduling DOI. The scheduling DOI may schedule / indicate the receiving PDSCH. The scheduling DOI may activate SPS PDSCH. The PDSCH may be an SPS PDSCH activated by the scheduling DCI.

[0351] In one implementation, the one or more capability may indicate that the wireless device supports receiving PDSCH with resource mapping that excludes the REs (e.g., the fourth set of RBs) corresponding to resource sets configured with RB-symbol level granularity indicated by bitmaps (e.g., the plurality of bitmap groups) and controlResourceSet (see pattemType in RateMatchPattern) based on a dynamic indication (e.g., the RMI field) in the scheduling DCI. For example, the first set of capabilities may comprise the second rate matching capability. The base station may transmit the scheduling DCI scheduling the receiving the PDSCH. The scheduling DCI may indicate (via the RMI field) the first / second RMP group of the at least one RMP group. The wireless device may, based on indicating the second capability message and the RMI field of the scheduling DCI, may determine / declare the fourth set of RBs as unavailable for receiving PDSCHs. The wireless device may determine the fourth set of RBs based on the first / second RMP group of the at least one RMP group indicated by the scheduling DCI.

[0352] In another implementation, the one or more capability may indicate that the wireless device does not support receiving PDSCH with resource mapping that excludes the REs (e.g., the fourth set of RBs) corresponding to resource sets configured with RB-symbol level granularity indicated by bitmaps (e.g., the plurality of bitmap groups) and controlResourceSet (see pattemType in RateMatchPattern) based on a dynamic indication (e.g., the RMI field) in the scheduling DCI. In some aspects, the one or more capability may not indicate that the wireless device supports receiving PDSCH with resource mapping that excludes the REs (e.g., the fourth set of RBs) corresponding to resource sets configured with RB-symbol level granularity indicated by bitmaps (e.g., the plurality of bitmap groups) and controlResourceSet (see pattemType in RateMatchPattern) based on a dynamic indication (e.g., the RMI field) in a scheduling DCI. For example, the first set of capabilities may not comprise the second rate matching capability. The base station may transmit the scheduling DCI scheduling the receiving the PDSCH. The scheduling DCI may not indicate / configure (via the RMI field) the first / second RMP group of the at least one RMP group. The wireless device may, based on not indicating the second capability message, may avoid determining / declaring the fourth set of RBs as unavailable for receiving PDSCHs.

[0353] FIG. 19 also shows that the reserved resources (for receiving PDSCHs) may further comprise a fifth set of REs (e.g., N5> 1 REs). The fifth set of RE(s) may correspond to a plurality of zero-power (ZP) CSR-RS resource sets. The wireless device may determine / declare the fifth set of RE(s) not being available for receiving PDSCHs (e.g., CG-PDSCHs). FIG. 21 B shows an example of zero-power (ZP) OSR-RS resource set per an aspect of the present disclosure. The one or more configuration parameters may comprise one or more ZP CSI-RS configuration parameters. The one or more ZP CSI-RS configuration parameters may configure / indicate the plurality of ZP CSR-RS resource sets.

[0354] In some examples, the fourth set of RBs may comprise the fifth set of RE(s).

[0355] In another examples, the fourth set of RBs may not comprise the fifth set of RE(s).

[0356] The example of FIG. 20 also shows an example that the PDSCH-Config comprises / includes the plurality of ZP CSR-RS resource sets. Similarity, PDSCH-ConfigMulticast comprises / includes the plurality of ZP CSR-RS resource sets.

[0357] The one or more configuration parameters (e.g., PDSCH-Config and / or PDSCH-ConfigMulticast) may comprise the one or more ZP CSI-RS configuration parameters. For example, the one or more configuration parameters (e.g., PDSCH-Config and / or PDSCH-ConfigMulticast) configure / indicate the plurality of ZP CSI-RS resource set configuration(s).

[0358] A ZP CSI-RS resource set configuration may configure at least one aperiodic ZP CSI-RS resource set (aperiodic-ZP-CSI-RS-ResourceSetsToAddModList). The plurality of ZP CSR-RS resource sets may comprise the at least one aperiodic ZP CSI-RS resource set. The base station may, to the wireless device, transmit a DCI. The wireless device may receive the DCI. The DCI my trigger / indicate the at least one aperiodic ZP CSI-RS resource set. For example, the DCI may comprise a “ZP CSI-RS trigger” field triggering the at least one aperiodic ZP CSI-RS resource set. In response to the DCI triggering the at least one aperiodic ZP CSI-RS resource set, the wireless device may determine the fifth set of RE(s) based on (REs of) the at least one aperiodic ZP CSI-RS resource set. The wireless device may declare the fifth set of RE(s) as unavailable for receive PDSCH.

[0359] A ZP CSI-RS resource set configuration may configure at least one periodic ZP CSI-RS resource set (p-ZP- CSI-RS-ResourceSet). The the plurality of ZP CSR-RS resource sets may comprise the at least one periodic ZP CSI- RS resource set.

[0360] A ZP CSI-RS resource set configuration may configure at least one semi-persistent (SP) ZP CSI-RS resource set (sp-ZP-CSI-RS-ResourceSetsToAddModList). The plurality of ZP CSR-RS resource sets may comprise the at least one SP ZP CSI-RS resource set. The wireless device may receive an activation command (e.g., an activation MAC CE) activating a SP ZP CSI-RS resource set of the at least one SP ZP CSI-RS resource set. The wireless device may, in response to the activation command, determine / declare the fifth set of RE(s) for the PDSCH RE-level rate matching corresponding to the activated SP ZP CSI-RS resource set. The activation MAC CE may be based on receiving a unicast / multicast PDSCH.

[0361] In an example, the wireless device may receive a deactivation command (e.g., a deactivation MAC CE) deactivating the SP ZP CSI-RS resource set of the at least one SP ZP CSI-RS resource set. The wireless device may, in response to the deactivation command, exclude the deactivated SP ZP CSI-RS resource set from the fifth set ofRE(s) for the PDSCH RE-level rate matching. The deactivation MAC CE may be based on receiving a u n icast / mu Iticast PDSCH.

[0362] A ZP CSI-RS resource set of the plurality of ZP CSR-RS resource sets may comprise at least one (e.g. , 8 or 16 or the like) ZP CSI-RS resource, e.g., in numerology of the BWP. A ZP CSI-RS resource of the at least one ZP CSI- RS resources may correspond to / be associated with a ZP CSI-RS resource ID / index / number (e.g., zp-CSI-RS- Resourceld). A ZP-CSI-RS-Resource resource mapping (resourceMapping in ZP-CSI-RS-Resource) of the ZP CSI-RS resource may define a (OFDM) symbol and subcarrier occupancy of the ZP CSI-RS resource within a slot. In an example, a periodicityAndOffset in ZP-CSI-RS-Resource (e.g., ZP CSI-RS periodicity) may indicate / define a ZP -CSI- RS periodicity and slot offset for a periodic ZP CSI-RS resource of the ZP CSI-RS resource set or a SP ZP CSI-RS resource of the semi-persistent ZP CSI-RS resource set.

[0363] For example, the fifth set of RE(s) may comprise one or more ZP-CSI-RS-Resource resource mappings corresponding to one or more ZP CSI-RS resources. The plurality of ZP CSI-RS resource sets may comprise the one or more ZP CSI-RS resources.

[0364] For example, the fifth set of RE(s) for receiving GC-PDSCH may not comprise REs indicated by the plurality of ZP CSR-RS resource sets configured in PDSCH-Config for unicast.

[0365] The fifth set of RE(s) for receiving unicast (SPS) PDSCH may comprise REs indicated by the plurality of ZP CSR-RS resource sets configured in PDSCH-Config for unicast.

[0366] The fifth set of RE(s) for receiving unicast (SPS) PDSCH may not comprise REs indicated by the plurality of ZP CSR-RS resource sets configured in pdsch-ConfigMulticast for multicast.

[0367] The fifth set of RE(s) for receiving GC-PDSCH may comprise REs indicated by the plurality of ZP CSR-RS resource sets configured in pdsch-ConfigMulticast for multicast.

[0368] For example, the fifth set of RE(s) for receiving GC-PDSCH may not comprise REs indicated by at least one periodic ZP CSR-RS resource sets configured in PDSCH-Config for unicast.

[0369] The fifth set of RE(s) for receiving unicast (SPS) PDSCH may comprise REs indicated by at least one periodic ZP CSR-RS resource sets configured in PDSCH-Config for unicast.

[0370] The fifth set of RE(s) for receiving unicast (SPS) PDSCH may not comprise REs indicated by at least one periodic ZP CSR-RS resource sets configured in pdsch-ConfigMulticast for multicast.

[0371] The fifth set of RE(s) for receiving GC-PDSCH may comprise REs indicated by at least one periodic ZP CSR- RS resource sets configured in pdsch-ConfigMulticast for multicast.

[0372] The at least one rate matching capability may comprise a third rate matching capability (e.g., re- LevelRateMatchingForMulticast-r17). FIG. 22 further shows an example definition of the third rate matching capability.

[0373] The third rate matching capability may indicate whether the wireless device supports group-common (GC) PDSCH RE-level rate matching for multicast. For example, the third rate matching capability may comprise at least one of the following: Supports SP ZP-CSI-RS for group-common PDSCH RE-mapping patterns; Supports P ZP-CSI-RS forgroup-common PDSCH RE-mapping patterns; Supports p-ZP-CSI-RS-ResourceSet configured in PDSCH-Config- Multicast same as or different from the p-ZP-CSI-RS-ResourceSet configured in PDSCH-Config; and / or Supports AP ZP-CSI-RS for group-common PDSCH RE-mapping patterns.

[0374] In one implementation, the one or more capability messages may indicate that the wireless device supports group-common (GO) PDSCH RE-level rate matching for multicast. For example, the one or more capability messages may indicate the wireless device supports P ZP-CSI-RS for group-common PDSCH RE-mapping patterns. The base station may configure (for multicast reception) at least one p-ZP-CSI-RS-ResourceSet (e.g., in pdsch-ConfigMulticast) for GC-PDSCH rate matching. The wireless device may determine the fifth set of RE(s) based on REs indicated by p- ZP-CSI-RS-ResourceSet. The wireless device may determine / declare the fifth set of RE(s) as not being available for GC-PDSCH.

[0375] In one implementation, the one or more capability messages may not indicate that the wireless device supports group-common (GC) PDSCH RE-level rate matching for multicast. For example, the one or more capability messages may not indicate the wireless device supports P ZP-CSI-RS for group-common PDSCH RE-mapping patterns. For example, the one or more capability messages may indicate the wireless device does not support the P ZP-CSI-RS for group-common PDSCH RE-mapping patterns. The base station may not configure (for multicast reception) at least one p-ZP-CSI-RS-ResourceSet (e.g., in pdsch-ConfigMulticast) for GC-PDSCH rate matching. The wireless device may avoid determining the fifth set of RE(s) based on REs indicated by p-ZP-CSI-RS-ResourceSet. The wireless device may avoid determining / declaring the fifth set of RE(s) as being unavailable for GC-PDSCH.

[0376] In one implementation, the one or more capability messages may indicate that the wireless device supports group-common (GC) PDSCH RE-level rate matching for multicast. For example, the one or more capability messages may indicate the wireless device supports SP ZP-CSI-RS for group-common PDSCH RE-mapping patterns. The base station may configure (for multicast reception) at least one sp-ZP-CSI-RS-ResourceSet (e.g., in pdsch-ConfigMulticast) for GC-PDSCH rate matching. The base station may activate (e.g., via the activate command) at least one sp-ZP-CSI- RS-ResourceSet. The wireless device may determine the fifth set of RE(s) based on REs indicated by the (activated) at least one sp-ZP-CSI-RS-ResourceSet. The wireless device may determine / declare the fifth set of RE(s) as not being available for GC-PDSCH.

[0377] In one implementation, the one or more capability messages may not indicate that the wireless device supports group-common (GC) PDSCH RE-level rate matching for multicast. The one or more capability messages may indicate that the wireless device does not support group-common (GC) PDSCH RE-level rate matching for multicast. For example, the one or more capability messages may not indicate the wireless device supports SP ZP-CSI-RS for group-common PDSCH RE-mapping patterns. The base station may avoid configuring (for multicast reception) at least one sp-ZP-CSI-RS-ResourceSet (e.g., in pdsch-ConfigMulticast) for GC-PDSCH rate matching. The base station may avoid activating (e.g., via the activate command) at least one sp-ZP-CSI-RS-ResourceSet for GC-PDSCH rate matching. The wireless device may avoid determining the fifth set of RE(s) based on REs indicated by the at least onesp-ZP-CSI-RS-ResourceSet. The wireless device may avoid determining / declaring the fifth set of RE(s) as being unavailable for GC-PDSCH.

[0378] In one implementation, the one or more capability messages may indicate that the wireless device supports group-common (GO) PDSCH RE-level rate matching for multicast. For example, the one or more capability messages may indicate the wireless device supports AP ZP-CSI-RS for group-common PDSCH RE-mapping patterns. The base station may configure (for multicast reception) at least one ap-ZP-CSI-RS-ResourceSet (e.g., in pdsch-ConfigMulticast) for GC-PDSCH rate matching. The base station may trigger (e.g., via the “ZP CSI-RS trigger” of a DCI) at least one ap- ZP-CSI-RS-ResourceSet. The wireless device may determine the fifth set of RE(s) based on REs indicated by the (triggered) at least one sp-AP-CSI-RS-ResourceSet. The wireless device may determine / declare the fifth set of RE(s) as not being available for GC-PDSCH.

[0379] In one implementation, the one or more capability messages may not indicate that the wireless device supports group-common (GC) PDSCH RE-level rate matching for multicast. The one or more capability messages may indicate that the wireless device does not support group-common (GC) PDSCH RE-level rate matching for multicast. For example, the one or more capability messages may not indicate the wireless device supports AP ZP-CSI-RS for group-common PDSCH RE-mapping patterns. The base station may avoid configuring (for multicast reception) the at least one ap-ZP-CSI-RS-ResourceSet (e.g., in pdsch-ConfigMulticast) for GC-PDSCH rate matching. The base station may avoid triggering (e.g., via the “ZP CSI-RS trigger” of a DCI) the at least one ap-ZP-CSI-RS-ResourceSet. The wireless device may avoid determining the fifth set of RE(s) based on REs indicated by the (triggered) at least one sp- AP-CSI-RS-ResourceSet. The wireless device may avoid determining / declaring the fifth set of RE(s) as not being available for GC-PDSCH.

[0380] FIG. 24 shows an example of sub-band full duplex (SBFD) operation per an aspect of an embodiment of the present disclosure. FIG. 24 shows two examples of SBFD operations in a carrier. The carrier may be a TDD carrier. The carrier may be an FDD carrier. Other examples are also possible.

[0381] 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 are the DL slots / symbols (configured by the one or more configuration parameters) that are configured / indicated for the SBFD operation.

[0382] For example, the one or more messages may comprise / indicate an SBFD configuration. The SBFD configuration may comprise the one or more SBFD configuration parameters.

[0383] 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. In one example, the one or more TDD configuration parameters may comprise one or more SBFD configuration parameters.

[0384] The wireless device may be in an RRC connected 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 connected state.

[0385] In some implementations, the one or more SBFD configuration parameters may also configure / enable the wireless device for the SBFD operation when the wireless device is in an RRC idle / inactive state. For example, 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.

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

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

[0388] The one or more SBFD configuration parameters may configure one or more SBFD subbands. The one or more SBFD configuration parameters may configure 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 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).

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

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

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

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

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

[0394] 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 SBFDconfiguration parameters not indicating the second period), the wireless device may determine the SBFD subband(s) is only configured within / correspond to the first TDD pattern.

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

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

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

[0398] The one or more SBFD configuration parameters may indicate that a slot of a set of slots comprise of at least one SBFD symbol and non-SBFD symbols. The one or more consecutive slots may comprise the set of slots. The slot may be a DL slot or a flexible slot. The at least one SBFD symbol may be a DL / flexible symbol configured for SBFD operation. The SBFD symbol may be within the SBFD time locations. The non-SBFD symbols of the slot may not be within the SBFD time locations.

[0399] In the present disclosure, when the slot comprises only SBFD symbols, the slot may be referred to by / as an SBFD slot.

[0400] In the present disclosure, when the slot comprises at least one non-SBFD symbol, the slot may be referred to by / as a partial SBFD slot or a partial non-SBFD slot.

[0401] In the present disclosure, when the slot comprises only non-SBFD symbols, the slot may be referred to by / as a non-SBFD slot.

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

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

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

[0405] The D-U or the U-D or the D-U-D partitioning of the frequency resources of the SBFD symbol may provide / indicate examples of the SBFD subband frequency location(s). The one or more SBFD configuration parameters may indicate / configure the SBFD subband frequency location(s). The SBFD subband frequency location(s) may correspond to each SBFD symbol within the SBFD subband time locations.

[0406] The SBFD symbol / slot may comprise UL subband and DL subband(s). The one or more SBFD configuration parameters may configure / indicate the SBFD subband frequency locations. The SBFD subband frequency locations may comprise frequency locations of UL subband and DL subband(s). The frequency locations of UL subband may comprise subband frequency-domain resources. The first set of resource blocks may correspond to at least a cellspecific UL subband and / or a UE-specific UL subband.

[0407] The frequency locations of UL subband may comprise a first set of resource blocks (RBs). The first set of resource blocks may comprise / be DL subband(s) frequency resources. The second set of resource blocks may correspond to at least cell-specific DL subband(s) and / or UE-specific DL subband(s).

[0408] The frequency locations of DL subband(s) may comprise a second set of resource blocks (RBs). The second set of resource blocks may comprise / be DL subband frequency resources.

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

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

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

[0412] Union of the first set of RBs, the second set of RBs, and the third set of RBs may comprise the RBs of the DL BWP (or the carrier). The first set of RBs may belong to RBs of an UL BWP.

[0413] The first set of resource blocks may comprise one or more first resource elements. The one or more first resource elements may be contiguous. The first set of resource blocks (or the UL subband frequency resources) may be within an active UL BWP. The UL BWP may have a same BWP I D / index as the active DL BWP.

[0414] The first second of resource blocks may comprise one or more second resource elements. The one or more second resource elements may be contiguous (e.g., D-U or U-D partitioning of the frequency resources) or noncontiguous (e.g., D-U-D partitioning of the frequency resources).

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

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

[0417] As also shown in FIG. 24, For discussion purpose, the UL subband frequency resources (e.g., the first set of RBs) within the active UL BWP may also be referred to by UL usable PRBs. The wireless device may determine the UL usable PRBs (or the first set of RBs) determine as an intersection between the UL subband frequency resources and the active UL BWP in the SBFD symbol(s) / slot(s).

[0418] The DL subband(s) frequency resources (e.g., the second set of RBs) within the active DL BWP may also be referred to by DL usable PRBs. The 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).

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

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

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

[0422] 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 / m issing 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.

[0423] 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 as a DL symbol. In another example, if the first number is set to zero, the wireless device may consider / assume the SBFD symbol as an UL symbol.

[0424] In the present disclosure, an SBFD-aware wireless device refers to a wireless device that has hardware / software capabilities (e.g., a second set of capabilities) for communicating in UL / DL with an SBFD-enabled base station. The SBFD-aware wireless device communicates with the base station based on the SBFD operation. The SBFD-aware wireless device may be half-duplex. The SBFD-aware wireless device may be full-duplex.

[0425] In the present disclosure, “SBFD operation” may refer to “SBFD mode” or “SBFD communication mode” or “SBFD frame configuration” or “SBFD reception mode” or “SBFD transmission mode”.

[0426] In the present disclosure, “type” may refer to “mode” or “status” or “configuration” or “combination” or “operation” or the like.

[0427] In the present disclosure, “partitioning” may refer to “segmentation” or “division” or “split” or “subdivision” or “division” or “part” or “segment” or the like.

[0428] In the present disclosure, “subband” may refer to “sub-band”.

[0429] In the present disclosure, “Guardband” may refer to “Guard-band” or “guardband” or “guard-band” or “guard band”.

[0430] In the present disclosure, “location” may refer to “position” or “point” or “region”.

[0431] In the present disclosure, “frequency resources” may refer to “resource blocks” or “resource elements” or“subcarriers” or “bandwidth part”.

[0432] In the present disclosure, “overlap” may refer to “collide”.

[0433] In the present disclosure, “UL subband frequency resources” may refer to frequency resources that are configure / allocated for UL subband transmissions in the TDD carrier.

[0434] In the present disclosure, “DL subband frequency resources” may refer to frequency resources that are configure / allocated for DL subband receptions in the TDD carrier.

[0435] In the present disclosure, “UL subband transmissions” may refer to “transmissions using the first set of RBs”.

[0436] In the present disclosure, “DL subband receptions” may refer to “receptions using the second set of RBs”.

[0437] In the present disclosure, “communicating” may refer to “transmitting” or “receiving”.

[0438] In the present disclosure, “avoid” may refer to “omit” or “refuse” or “drop” or “ignore”.

[0439] In the present disclosure, “avoid communicating” may refer to “not communicating”.

[0440] In the present disclosure, “rate match” may refer to “rate-match” or “rateMatch”.

[0441] In the present disclosure, “linkage” may refer to “association” or “connection” or “correspondence” or “relation” or “relationship” or “mapping”.

[0442] In the present disclosure, “pairing” may refer to “associating”.

[0443] In the present disclosure, “declare” may refer to “state” or “announce” or “identify” or “determine” or “consider” or “assume”.

[0444] In the present disclosure, a first wireless device may be an SBFD-aware wireless device. The SBFD-aware wireless device may be referred to as “Type 1 UE” or “Type 1 wireless device”. The second wireless device may have capabilities for the SBFD operation in the TDD carrier, e.g., as discussed above in connection with FIG. 23.

[0445] In the present disclosure, a second wireless device may be a non-SBFD-aware wireless device. The non- SBFD-aware wireless device may refer to by “Type 2 UE” or “Type 2 wireless device” or “legacy UE” or “legacy wireless device” or “SBFD-unaware UE” or “SBFD-unaware wireless device”. The second wireless device may not have capabilities for SBFD operation in the TDD carrier. The wireless device may communicate with the base station based on TDD operations (e.g., discussed above in connection with embodiments of FIG. 18).

[0446] In the present disclosure, a base station may be a full-duplex (FD) base station. The full-duplex base station may be an SBFD-enabled base station. The first wireless device and / or the second wireless device may communicate with the FD base station via a serving cell of the one or more serving cells.

[0447] FIG. 24 shows an example of SBFD operation. An FD base station may transmit the one or more configuration parameters to the first wireless device. The one or more configuration parameters may comprise the one or more TDD configuration parameters and / or the one or more SBFD configuration parameters. The one or more TDD configuration parameters may configure (the first / second wireless device) with one or more DL / f lexible slots / symbols, e.g., DL / flexible slot / symbols #1 and DL / flexible slot / sym bols #2, DL / flexible slot / symbols #3, and DL / flexible slot / sy mbols #4. The one or more consecutive slots may comprise the one or more DL / flexible slots / symbols.

[0448] The first wireless device may, based on / using one or more SBFD configuration parameters, determine the SBFD subband frequency location(s), e.g., the first / second / third set of RBs for UL / DL subband transmissions / receptions. The first wireless device may, based on / using one or more SBFD configuration parameters, determine the SBFD subband time location(s), e.g., at least one SBFD symbol. As shown the one or more SBFD configuration parameters may configure the DL / flexible slot / symbols #3 and the DL / flexible slot / symbols #4 for SBFD operation for the first wireless device. For example, the DL / flexible slot / symbols #3 may be a SBFD slot / symbols #1 and the DL / flexible slot / symbols #4 may be a SBFD slot / symbols #2. For example, the one or more DL / flexible slots / symbols comprise at least one slot / symbol. The at least one slot / sym bol may correspond to the SBFD slot / symbols #1 and the SBFD slot / symbols #2. For example, the one or more SBFD configuration parameters may configure / indicate the SBFD slot / symbols #1 for DL subband receptions. The one or more SBFD configuration parameters may configure / indicate the SBFD slot / symbols #2 for UL subband transmissions.

[0449] For example, the first wireless device may receive one or more PDSCHs in the one or more DL / flexible slots / symbols. The one or more PDSCHs may comprise at least one CG-PDSCH and / or at least one SPS PDSCH and / or at least one dynamic PDSCH (scheduled by a scheduling DCI). The PDSCH#1 / #2 receptions may be in the DL / flexible slot / symbols #1 and the DL / flexible slot / symbols #2.

[0450] As shown in FIG. 24, the first wireless device may fail to receive the PDSCHS3 (in the DL / flexible slot / symbols #3), e.g., due to imposed cross-link interference imposed by other SBFD-aware UEs in the serving cell or neighborcells. Based on the implementation of existing technologies, there may be a misalignment between the FD base station and the SBFD-aware UE resulting in an increase of DL inefficiency / delay. For example, the base station may not be able to properly configure an RMP configuration allowing the wireless device to receive the PDSCHs in SBFD slot / symbols #1 / #2. In some other examples, for configuring the RMP configuration signaling overhead may grow.

[0451] Enhancements of rate matching and / or SBFD operation may improve / enhance performance of the SBFD- aware wireless device for receiving PDSCH(s) in the at least one symbol configured / indicated for DL subband receptions. There may be a need to improve / enhance capability reporting in existing technologies, in order to improve alignment between the wireless device and the base station.

[0452] Embodiments of the present disclosure are related to an approach for solving the problems described above. For example, certain examples can improve / enhance performance of the SBFD-aware wireless device for receiving PDSCH(s) in the at least one symbol configured / indicated for DL subband receptions. Certain examples can improve / enhance capability reporting in existing technologies, for example in order to improve alignment between the wireless device and the base station. These and other features of the present disclosure are described further below.

[0453] In an example embodiment, a wireless device (e.g., an SBFD-aware wireless device, e.g. , the first wireless device) may transmit the one or more capability messages to a base station (e.g., an SBFD-enabled base station). The one or more capability messages may comprise / indicate a first SBFD capability. The first SBFD capability may indicate whether the wireless device supports receiving PDSCH with resource mapping that excludes the RBs / REs corresponding to resource sets of SBFD subband frequency-time locations (e.g., the first / third set of RBs / REs in the at least one SBFD symbol) configured by semi-static SBFD configuration (e.g., the one or more SBFD configuration parameters).

[0454] In an example embodiment, the one or more capability messages may comprise / indicate the at least one rate matching capability and the first SBFD capability. The first rate matching capability (e.g., rateMatchingResrcSetSemi- Static) of the at least one rate matching capability may indicate whether the wireless device supports receiving PDSCH with resource mapping that excludes the REs (e.g., the fourth set of RBs) corresponding to resource sets configured with RB-symbol level granularity indicated by bitmaps (e.g., the plurality of bitmap groups) and controlResourceSet (see pattemType in RateMatchPattern) following the semi-static configuration (e.g., the plurality of RMP configurations).

[0455] In an example embodiment, a wireless device (e.g., an SBFD-aware wireless device, e.g., the first wireless device) may transmit the one or more capability messages to a base station (e.g., an SBFD-enabled base station). The one or more capability messages may comprise / indicate the first SBFD capability. Based on the one or more messages indicating / comprising the first SBFD capability and the plurality of first RBs / REs for receiving PDSCH in an SBFD symbol of at least one SBFD symbol overlapping / collid in g with guard-band / UL sub-band frequency resources (e.g., the first / third set of RBs) with the at least one RB / RE, the wireless device may receive, in the SBFD symbol, PDSCH, in the SBFD symbol, with resource mapping that excludes the at least one RB / RE from the plurality of first RBs / REs.

[0456] In an example embodiment, a wireless device (e.g., an SBFD-aware wireless device, e.g. , the first wireless device) may transmit the one or more capability messages to a base station (e.g., an SBFD-enabled base station). The one or more capability messages may comprise / indicate the first SBFD capability. Based on the one or more messages indicating / comprising the first SBFD capability and the plurality of first RBs / REs for receiving PDSCH in an SBFD symbol of at least one SBFD symbol overlapping / collid in g with guard-band / UL sub-band frequency resources (e.g., the first / third set of RBs) in the at least one RB / RE, the wireless device may determine the at least one RB / RE of the plurality of first RBs / REs being invalid for receiving the PDSCH in the SBFD symbol.

[0457] In an example embodiment, a wireless device (e.g., an SBFD-aware wireless device, e.g., the first wireless device) may transmit the one or more capability messages to a base station (e.g., an SBFD-enabled base station). The one or more capability messages may not comprise / indicate the first SBFD capability. The one or more capability messages may indicate the wireless device does not support receiving PDSCH with resource mapping that excludes the RBs / REs corresponding to resource sets of SBFD subband frequency-time locations (e.g., the first / third set of RBs / REs in the at least one SBFD symbol) configured by semi-static SBFD configuration (e.g., the one or more SBFD configuration parameters). Based on the one or more messages not indicating / comprising the first SBFD capability, the wireless device may not receive (or avoid receiving or drop receiving) PDSCH in an SBFD symbol of at least one SBFD symbol.

[0458] In an example embodiment, a wireless device (e.g., an SBFD-aware wireless device, e.g., the first wireless device) may transmit the one or more capability messages to a base station (e.g., an SBFD-enabled base station). The one or more capability messages may not comprise / indicate the first SBFD capability. The one or more capability messages may indicate the wireless device does not support receiving PDSCH with resource mapping that excludes the RBs / REs corresponding to resource sets of SBFD subband frequency-time locations (e.g., the first / third set of RBs / REs in the at least one SBFD symbol) configured by semi-static SBFD configuration (e.g., the one or more SBFD configuration parameters). Based on the one or more messages not indicating / comprising the first SBFD capability and the plurality of first RBs / REs for receiving PDSCH in an SBFD symbol of at least one SBFD symbol overlapping / collid in g with guard-band / UL sub-band frequency resources (e.g., the first / third set of RBs) in the at least one RB / RE, the wireless device may not receive (or avoid receiving or drop receiving) PDSCH in the SBFD symbol of at least one SBFD symbol.

[0459] In an example embodiment, a wireless device (e.g., an SBFD-aware wireless device, e.g., the first wireless device) may transmit the one or more capability messages to a base station (e.g., an SBFD-enabled base station). The one or more capability messages may comprise / indicate the first SBFD capability. The first SBFD capability may indicate the wireless device supports receiving PDSCH with resource mapping that excludes the RBs / REs corresponding to resource sets of SBFD subband frequency-time locations (e.g., the first / third set of RBs / REs in the at least one SBFD symbol) configured by semi-static SBFD configuration (e.g., the one or more SBFD configuration parameters). The wireless device may receive the one or more configuration parameters comprising the SBFDconfiguration (e.g., the one or more SBFD configuration parameters) indicating the one or more SBFD symbols. The one or more configuration parameters may comprise an RMP configuration (of the plurality of RMP configurations) comprising an RMP for at least one SBFD symbol of the one or more SBFD symbols.

[0460] In an example embodiment, a wireless device (e.g., an SBFD-aware wireless device, e.g., the first wireless device) may transmit the one or more capability messages to a base station (e.g., an SBFD-enabled base station). The one or more capability messages may comprise / indicate the first SBFD capability. The first SBFD capability may indicate the wireless device supports receiving PDSCH with resource mapping that excludes the RBs / REs corresponding to resource sets of SBFD subband frequency-time locations (e.g., the first / third set of RBs / REs in the at least one SBFD symbol) configured by semi-static SBFD configuration (e.g., the one or more SBFD configuration parameters). The wireless device may receive the one or more configuration parameters comprising the SBFD configuration (e.g., the one or more SBFD configuration parameters) indicating the one or more SBFD symbols. The one or more configuration parameters may comprise an RMP configuration (of the plurality of RMP configurations) comprising an indication associating (or linking or connecting) an RMP with the SBFD configuration.

[0461] In an example embodiment, a wireless device (e.g., an SBFD-aware wireless device, e.g., the first wireless device) may transmit the one or more capability messages to a base station (e.g., an SBFD-enabled base station). The one or more capability messages may comprise / indicate the first SBFD capability. The first SBFD capability may indicate the wireless device supports receiving PDSCH with resource mapping that excludes the RBs / REs corresponding to resource sets of SBFD subband frequency-time locations (e.g., the first / third set of RBs / REs in the at least one SBFD symbol) configured by semi-static SBFD configuration (e.g., the one or more SBFD configuration parameters). The wireless device may receive the one or more configuration parameters comprising the SBFD configuration (e.g., the one or more SBFD configuration parameters) comprising at least one SBFD pattern. The one or more configuration parameters may comprise an RMP configuration (of the plurality of RMP configurations) comprising an indication associating (or linking or connecting) an RMP with an SBFD pattern of the at least one SBFD pattern.

[0462] In an example embodiment, a wireless device (e.g., an SBFD-aware wireless device, e.g., the first wireless device) may transmit the one or more capability messages to a base station (e.g., an SBFD-enabled base station). The one or more capability messages may comprise / indicate the first SBFD capability. The first SBFD capability may indicate the wireless device supports receiving PDSCH with resource mapping that excludes the RBs / REs corresponding to resource sets of SBFD subband frequency-time locations (e.g., the first / third set of RBs / REs in the at least one SBFD symbol) configured by semi-static SBFD configuration (e.g., the one or more SBFD configuration parameters). The wireless device may receive the one or more configuration parameters comprising the SBFD configuration (e.g., the one or more SBFD configuration parameters) indicating the one or more SBFD symbols. The one or more configuration parameters may comprise an RMP configuration (of the plurality of RMP configurations) comprising an indication associating (or linking or connecting) an RMP with at least one SBFD symbol of the one or more SBFD symbols indicated by the SBFD configuration.

[0463] In an example embodiment, a wireless device (e.g., an SBFD-aware wireless device, e.g. , the first wireless device) may transmit the one or more capability messages to a base station (e.g., an SBFD-enabled base station). The one or more capability messages may comprise / indicate the first SBFD capability. The first SBFD capability may indicate the wireless device supports receiving PDSCH with resource mapping that excludes the RBs / REs corresponding to resource sets of SBFD subband frequency-time locations (e.g., the first / third set of RBs / REs in the at least one SBFD symbol) configured by semi-static SBFD configuration (e.g., the one or more SBFD configuration parameters). The wireless device may receive the one or more configuration parameters comprising the SBFD configuration (e.g., the one or more SBFD configuration parameters) comprising at least one SBFD pattern. A first SBFD pattern of the at least one SBFD pattern may indicate / comprise one or more SBFD symbols. The one or more configuration parameters may comprise an RMP configuration (of the plurality of RMP configurations) comprising an indication associating (or linking or connecting) an RMP with at least one SBFD symbol of the one or more SBFD symbols indicated / configured by the first SBFD pattern of the at least one SBFD pattern.

[0464] Some embodiments of the present disclosure may improve alignment between a wireless device (e.g., an SBFD-aware UE) and a base station (e.g., an FD base station) for performing the UL / DL communications based on the SBFD operation. Embodiments allow the wireless device to report one or more capability messages for rate matching. The base station may use the one or more capability messages (e.g., the first SBFD capability) for transmitting PDSCH in SBFD symbols. Embodiments may improve DL transmission efficiency, allowing the base station and the wireless device to properly rate match PDSCH around the first / third set of RBs for receiving the PDSCH in the SBFD symbols.

[0465] In an example embodiment, a wireless device (e.g., an SBFD-aware wireless device, e.g., the first wireless device) may, from a base station (e.g., an SBFD-enabled base station), receive the one or more configuration parameters comprising the SBFD configuration (e.g., the one or more SBFD configuration parameters) indicating the one or more SBFD symbols. The one or more configuration parameters may comprise an RMP configuration (of the plurality of RMP configurations) comprising an RMP for at least one SBFD symbol of the one or more SBFD symbols. The wireless device may, based on the RMP configuration, determine at least one RB / RE, of a PDSCH reception, among the plurality of the RBs / REs in an SBFD symbol of the at least one SBFD symbol. The wireless device may receive, using / in the plurality of the RBs / REs (by) excluding the at least one RB / RE, the PDSCH in the SBFD symbol.

[0466] In an example embodiment, a wireless device (e.g., an SBFD-aware wireless device, e.g., the first wireless device) may, from a base station (e.g., an SBFD-enabled base station), receive the one or more configuration parameters comprising the SBFD configuration (e.g., the one or more SBFD configuration parameters) indicating the one or more SBFD symbols. The one or more configuration parameters may comprise an RMP configuration (of the plurality of RMP configurations) comprising an RMP for at least one SBFD symbol of the one or more SBFD symbols. The wireless device may, based on the RMP configuration, determine at least one RB / RE, of a PDSCH reception, among the plurality of the RBs / REs in an SBFD symbol of the at least one SBFD symbol, being invalid (or reserved orunavailable) for receiving the PDSCH. The wireless device may receive, using / in the plurality of the RBs / REs (by) excluding the at least one RB / RE, the PDSCH in the SBFD symbol.

[0467] In an example embodiment, a wireless device (e.g., an SBFD-aware wireless device, e.g. , the first wireless device) may, from a base station (e.g., an SBFD-enabled base station), receive the one or more configuration parameters comprising the SBFD configuration (e.g., the one or more SBFD configuration parameters) indicating the one or more SBFD symbols for SBFD operation in a carrier. The one or more configuration parameters may comprise an RMP configuration (of the plurality of RMP configurations) comprising an indicating associating / linking / connecting an RMP with at least one SBFD symbol of the one or more SBFD symbols indicated / configured by the SBFD configuration. The wireless device may, based on the RMP configuration, determine at least one RB / RE, of a PDSCH reception, among the plurality of the RBs / REs in an SBFD symbol of the at least one SBFD symbol. The wireless device may receive, using / in the plurality of the RBs / REs (by) excluding the at least one RB / RE, the PDSCH in the SBFD symbol.

[0468] In an example embodiment, a wireless device (e.g., an SBFD-aware wireless device, e.g., the first wireless device) may, from a base station (e.g., an SBFD-enabled base station), receive the one or more configuration parameters comprising the SBFD configuration (e.g., the one or more SBFD configuration parameters) indicating the one or more SBFD symbols for SBFD operation in a carrier. The one or more configuration parameters may comprise an RMP configuration (of the plurality of RMP configurations) comprising an indicating associating / linking / connecting an RMP with at least one SBFD symbol of the one or more SBFD symbols indicated / configured by the SBFD configuration. The wireless device may, based on the RMP configuration, determine at least one RB / RE, of a PDSCH reception, among the plurality of the RBs / REs in an SBFD symbol of the at least one SBFD symbol being invalid (or reserved or unavailable) for receiving the PDSCH. The wireless device may receive, using / in the plurality of the RBs / REs (by) excluding the at least one RB / RE, the PDSCH in the SBFD symbol.

[0469] In an example embodiment, a wireless device (e.g., an SBFD-aware wireless device, e.g., the first wireless device) may, from a base station (e.g., an SBFD-enabled base station), receive the one or more configuration parameters comprising the SBFD configuration (e.g., the one or more SBFD configuration parameters) comprising / indicating at least one SBFD pattern. A first SBFD pattern of the at least one SBFD pattern may indicate / comprise one or more SBFD symbols. The one or more configuration parameters may comprise an RMP configuration (of the plurality of RMP configurations) comprising an indication associating (or linking or connecting) an RMP with at least one SBFD symbol of the one or more SBFD symbols indicated / configured by the first SBFD pattern of the at least one SBFD pattern. The wireless device may, based on the RMP configuration, determine at least one RB / RE, of a PDSCH reception, among the plurality of the RBs / REs in an SBFD symbol of the at least one SBFD symbol. The wireless device may receive, using / in the plurality of the RBs / REs (by) excluding the at least one RB / RE, the PDSCH in the SBFD symbol.

[0470] In an example embodiment, a wireless device (e.g., an SBFD-aware wireless device, e.g. , the first wireless device) may, from a base station (e.g., an SBFD-enabled base station), receive the one or more configuration parameters comprising the SBFD configuration (e.g., the one or more SBFD configuration parameters) comprising / indicating at least one SBFD pattern. A first SBFD pattern of the at least one SBFD pattern may indicate / comprise one or more SBFD symbols. The one or more configuration parameters may comprise an RMP configuration (of the plurality of RMP configurations) comprising an indication associating (or linking or connecting) an RMP with at least one SBFD symbol of the one or more SBFD symbols indicated / configured by the first SBFD pattern of the at least one SBFD pattern. The wireless device may, based on the RMP configuration, determine at least one RB / RE, of a PDSCH reception, among the plurality of the RBs / REs in an SBFD symbol of the at least one SBFD symbol being invalid (or reserved or unavailable) for receiving the PDSCH. The wireless device may receive, using / in the plurality of the RBs / REs (by) excluding the at least one RB / RE, the PDSCH in the SBFD symbol.

[0471] Some embodiments may provide enhancements for RMP configuration in SBFD operation by configuring a linkage (or association) between an RMP configuration (e.g., rateMatchPattem) of the plurality of RMP configurations and the one or more SBFD configuration parameters (e.g., SBFD-Config). Using the linkage, signaling overhead for configuring the one or more bitmaps of the RMP configuration may reduce. For example, the base station may not need to configure a new bitmap (e.g., a pair of RB-level bitmap and symbol-level bitmap) of the one or more bitmaps of the RMP configuration allowing the wireless device to determine the fourth set of RBs. Instead, by linking the RMP configuration with the SBFD configuration (or SBFD pattern), embodiments of the present disclosure allow the wireless device to properly determine the fourth set of RBs based on the linked SBFD configuration / pattern.

[0472] FIG. 25 illustrates an example of UL / DL communications as per an aspect of an embodiment of the present disclosure. For example, FIG. 25 may show an example of the SBFD operation in a TDD carrier. The SBFD operation may be based on the embodiment of FIG. 23 discussed above.

[0473] As shown in FIG. 25, the first wireless device may transmit the one or more capability messages to a base station. The base station may be the FD base station. For example, the one or more capability messages may not indicate / comprise the at least one rate matching capability.

[0474] In one implementation, the one or more capability may not indicate that the first wireless device supports receiving PDSCH with resource mapping that excludes the REs (e.g., the fourth set of RBs) corresponding to resource sets configured with RB-symbol level granularity indicated the plurality of RMP configurations. The plurality of RMP configurations may comprise the plurality of bitmap groups, e.g., bitmaps, and / or controlResourceSet. For example, the one or more capability messages may not comprise / indicate the first rate matching capability. For example, the first set of capabilities may not comprise / indicate the first rate matching capability.

[0475] In an example embodiment, based on the one or more capability messages not comprising / indicating the first rate matching capability, the first wireless device may avoid / om it receiving PDSCH in an SBFD symbol of the SBFD slot / symbols #1. For example, in frequency domain the PDSCH may comprise a plurality of first RE(s) / RB(s). Thewireless device may determine the plurality of first RE(s) / RB(s) in the SBFD slot / symbols #1 being invalid (or not being valid) for receiving the PDSCH in the SBFD slot / sym bol #1. As also shown in FIG. 25, the first wireless device may determine the plurality of first RE(s) / RB(s) overlapping / coll idin g (in frequency domain) with at least one RE / RB of the first set of RBs and / or the third set of RBs.

[0476] In an example embodiment, based on the one or more capability messages not comprising / indicating the first rate matching capability and the plurality of first RE(s) / RB(s) overlapping / colliding (in frequency domain) with the at least one RE / RB of the first set of RBs and / or the third set of RBs, the first wireless device may avoid / om it receiving PDSCH in the SBFD symbol of the SBFD slot / symbols #1.

[0477] In an example embodiment, based on the one or more capability messages not comprising / indicating the first rate matching capability and the plurality of first RE(s) / RB(s) not overlapping / colliding (in frequency domain) with the at least one RE / RB of the first set of RBs and / or the third set of RBs, the first wireless device may receive the PDSCH in the SBFD symbol of the SBFD slot / symbols #1. The first wireless device may receive the PDSCH using the second set of RBs.

[0478] The one or more configuration parameters (e.g., PDSCH-config and / or SPS-config and / or PDSCH- ConfigMulticast) may configure / indicate the plurality of first RE(s) / RB(s) for receiving the PDSCH, e.g., type 0 / 1 downlink resource allocation schemes. In some cases, the first wireless device may receive a scheduling DCI indicating / scheduling PDSCH reception. The scheduling DCI may indicate / configure the plurality of first RE(s) / RB(s), e.g., via a FDRA field of the scheduling DCI.

[0479] In an example embodiment, the base station may, based on the one or more capability messages may not comprising / indicating the first rate matching capability, configure / determine the plurality of first RE(s) / RB(s) (for the PDSCH reception in the SBFD symbol) being a subset of the second set of RBs. For example, the base station may determine the plurality of first RE(s) / RB(s) to not collide / overlap (in frequency domain) with at least one RE / RB of the first set of RBs and / or the third set of RBs.

[0480] In another implementation, the one or more capability messages may indicate that the first wireless device does not support receiving PDSCH with resource mapping that excludes the REs (e.g., the fourth set of RBs) corresponding to resource sets configured with RB-symbol level granularity indicated by the plurality of bitmap groups based on a dynamic indication (e.g., the RMI field) in the scheduling DCI. In some aspects, the one or more capability messages may not indicate that the first wireless device supports receiving PDSCH with resource mapping that excludes the REs (e.g., the fourth set of RBs) corresponding to resource sets configured with RB-symbol level granularity indicated by the plurality of bitmap groups based on the dynamic indication (e.g., the RMI field) in the scheduling DCI. For example, the first set of capabilities may not comprise the second rate matching capability.

[0481] In an example embodiment, based on the one or more capability messages not comprising / indicating the second rate matching capability, the first wireless device may avoid receiving PDSCH in the SBFD symbol of the SBFDslot / symbols #1. The wireless device may determine the plurality of first RE(s) / RB(s) in the SBFD symbols being invalid (or not being valid) for receiving the PDSCH in the SBFD symbol.

[0482] In an example embodiment, based on the one or more capability messages not comprising / indicating the second rate matching capability and the plurality of first RE(s) / RB(s) overlapping / colliding (in frequency domain) with at least one RE / RB of the first set of RBs and / or the third set of RBs, the first wireless device may avoid receiving PDSCH in the SBFD symbol of the SBFD slot / symbols #1. The wireless device may determine the plurality of first RE(s) / RB(s) in the SBFD symbols being invalid (or not being valid) for receiving the PDSCH in the SBFD symbol.

[0483] In an example embodiment, based on the one or more capability messages not comprising / indicating the second rate matching capability and the plurality of first RE(s) / RB(s) not overlapping / colliding (in frequency domain) with at least one RE / RB of the first set of RBs and / or the third set of RBs, the first wireless device may receive PDSCH in the SBFD symbol of the SBFD slot / symbols #1 (using the second set of RBs).

[0484] The base station may transmit a DCI (e.g., the scheduling DCI) indicating / scheduling the receiving the PDSCH in the SBFD symbol of the SBFD slot / symbols #1. Based on the one or more capability messages not comprising / indicating the second rate matching capability, the scheduling DCI may not indicate / configure (via the RMI field) the first / second RMP group of the at least one RMP group. The first wireless device may, based on not indicating the second capability message, may drop receiving PDSCH in the SBFD symbol. The first wireless device may determine the plurality of first RE(s) / RB(s) overlapping / colliding (in frequency domain) with at least one RE / RB of the first set of RBs and / or the third set of RBs.

[0485] In some examples, the base station may, based on the one or more capability messages not comprising / indicating the at least one rate matching capability, avoid configuring / indicating (e.g., using the one or more SBFD configuration parameters) the SBFD symbol for DL subband receptions. The base station may, based on the one or more capability messages not comprising / indicating the at least one rate matching capability, configure / indicate (e.g., using the one or more SBFD configuration parameters) the SBFD symbol for UL subband transmissions.

[0486] In some implementations, for the SBFD-aware UE it may be mandatory (not optional) to support receiving PDSCH with resource mapping that excludes the REs (e.g., the fourth set of RBs) corresponding to resource sets configured with RB-symbol level granularity indicated by the plurality of bitmap groups following the semi-static configuration (e.g., the plurality of RMP configurations).

[0487] In some other implementations, for the SBFD-aware UE it may be mandatory (not optional) to support receiving PDSCH with resource mapping that excludes the REs (e.g., the fourth set of RBs) corresponding to resource sets configured with RB-symbol level granularity indicated by the plurality of bitmap groups and a dynamic indication (e.g., the RMI field) in the scheduling DCI.

[0488] The embodiment of FIG. 25 may provide an example of improving alignment between the first wireless device (e.g., SBFD-aware UE) and the FD base station for performing the UL / DL communications based on the SBFD operation.

[0489] FIG. 26 illustrates an example of UL / DL communications as per an aspect of an embodiment of the present disclosure. For example, FIG. 26 may show an example of the SBFD operation in a TDD carrier. The SBFD operation may be based on the embodiment of FIG. 23 discussed above. In some cases, embodiment of FIG. 26 may provide enhancements for rate matching (e.g., PDSCH resource mapping) in the SBFD operation.

[0490] As shown in FIG. 26 the one or more capability messages may comprise / indicate a first SBFD capability.

[0491] In some examples, for the SBFD-aware UE (e.g., the first wireless device) it may be mandatory (not optional) to indicate the first SBFD capability.

[0492] In some other examples, for the SBFD-aware UE (e.g., the first wireless device) it may be optional to indicate the first SBFD capability.

[0493] FIG. 26 also shows an example definition of the first SBFD capability. Other definitions are also possible. For example, the first SBFD capability may indicate whether the first wireless device supports receiving PDSCH with resource mapping that excludes the RBs / REs corresponding to resource sets of SBFD subband frequency-time locations configured by semi-static SBFD configuration (e.g., the one or more SBFD configuration parameters).

[0494] When the first wireless device indicates the first SBFD capability, the wireless device may indicate the support for determining the fourth set of RBs as unavailable (for the PDSCH reception in an SBFD symbol of the at least one SBFD symbol) based on the one or more SBFD configuration parameters.

[0495] When the first wireless device indicates the first SBFD capability, the wireless device may indicate the support for determining the fourth set of RBs as unavailable (for the PDSCH reception in an SBFD symbol of the at least one SBFD symbol) based on the first set of RBs and / or the third set of RBs.

[0496] When the first wireless device indicates the first SBFD capability, the wireless device may indicate the support for determining the fourth set of RBs as invalid (for the PDSCH reception in an SBFD symbol of the at least one SBFD symbol) based on the first set of RBs and / or the third set of RBs.

[0497] The SBFD subband frequency locations and SBFD subband time locations may configure / indicate the at least one SBFD symbol. The one or more SBFD configuration parameters may configure / indicate the SBFD subband frequency locations and SBFD subband time locations.

[0498] In an example, the one or more SBFD configuration parameters may configure / indicate one or more SBFD symbols. The one or more SBFD symbols may comprise the SBFD slot / symbols #1 shown in FIG. 26. The one or more SBFD symbols may comprise the at least one SBFD symbol. For example, the at least one SBFD symbols may be usable for DL receptions using the second set of RBs.

[0499] As shown in FIG. 26 the base station may transmit a PDSCH to the wireless device the SBFD slot / symbols #1. For example, in frequency domain the PDSCH may comprise the plurality of first RE(s) / RB(s). As also shown in FIG. 26, the first wireless device may determine the plurality of first RE(s) / RB(s) overlapping / colliding (in frequency domain) with at least one RE / RB of the first set of RBs and / or the third set of RBs. For example, the SBFD slot / symbols #1 may comprise the at least one SBFD symbol.

[0500] In an example embodiment, based on the one or more capability messages comprising / indicating the first SBFD capability, the first wireless device may determine at least one RE / RB based on the one or more SBFD configurations.

[0501] In an example embodiment, based on the one or more capability messages comprising / indicating the first SBFD capability and the plurality of first RE(s) / RB(s) overlappi ng / collid ing (in frequency domain) with the at least one RE / RB of the first set of RBs and / or the third set of RBs, the first wireless device may determine the at least one RE / RB. The first wireless device may determine the plurality of first RE(s) / RB(s) overlapping / collid in g (in frequency domain) with at least one RE / RB of the first set of RBs and / or the third set of RBs.

[0502] The at least one RE / RB may comprise / indicate the unavailable RE(s) / RB(s) for receiving the PDSCH in an SBFD symbol of the at least one SBFD symbol. The wireless device may, for receiving the PDSCH in the SBFD symbol of the at least one SBFD symbol, rate match PDSCH around. For example, the wireless device may exclude the at least one RE / RB from the plurality of first RE(s) / RB(s) for receiving the PDSCH in the SBFD symbol.

[0503] Based on whether the one or more capability messages comprises / indicates the first SBFD capability or not, the base station may determine whether to transmit the PDSCH in the SBFD slot / sy mbols #1 or not. The base station may determine the plurality of first RE(s) / RB(s) based on whether the one or more capability messages comprises / indicates the first SBFD capability or not.

[0504] In some implementations, based on the one or more capability messages comprising / indicating the first SBFD capability, the base station may determine to transmit, to the first wireless device, the PDSCH in the SBFD slot / sy mbols #1. The base station may determine the plurality of first RE(s) / RB(s) based on the one or more capability messages comprising / indicating the first SBFD capability. For example, the plurality of first RE(s) / RB(s) may comprise the at least one RE / RB in the SBFD symbol of the at least one SBFD symbol.

[0505] In another implementation, based on the one or more capability messages not comprising / indicating the first SBFD capability, the base station may determine to transmit, to the first wireless device, the PDSCH in the SBFD slot / symbols #1. The base station may determine the plurality of first RE(s) / RB(s) based on the one or more capability messages not comprising / indicating the first SBFD capability. For example, the plurality of first RE(s) / RB(s) may not comprise the at least one RE / RB in the SBFD symbol of the at least one SBFD symbol.

[0506] In yet other implementation, based on the one or more capability messages not comprising / indicating the first SBFD capability, the base station may determine to not transmit, to the first wireless device, the PDSCH in the SBFD slot / symbols #1.

[0507] Some embodiments of the present disclosure may improve alignment between the first wireless device (e.g., SBFD-aware UE) and the base station (e.g., the FD base station) for performing the UL / DL communications based on the SBFD operation. Embodiments allow the wireless device to report one or more capability messages for rate matching. The base station may use the one or more capability messages (e.g., the first SBFD capability) for transmitting PDSCH in SBFD symbols. Embodiments may improve DL transmission efficiency, allowing the basestation and the wireless device to properly rate match PDSCH around the first / third set of RBs for receiving the PDSCH in the SBFD symbols.

[0508] FIG. 27, FIG. 28, FIG. 29, and FIG. 30 show examples of rate matching configuration for SBFD operation per aspects of embodiments of present disclosure. FIG. 27, FIG. 28, FIG. 29, and FIG. 30 may provide one or more new enhancements / aspects for the embodiment of FIG. 25, FIG. 24, and / or FIG. 26 discussed above.

[0509] Embodiments of FIG. 27, FIG. 28, FIG. 29, and FIG. 30 may provide several examples of a linkage (or association) between an RMP configuration (e.g., rateMatchPattem) of the plurality of RMP configurations and the one or more SBFD configuration parameters (e.g., SBFD-Config). Using the linkage, signaling overhead for configuring the one or more bitmaps of the RMP configuration may reduce. For example, the base station may not need to configure a new bitmap (e.g., a pair of RB-level bitmap and symbol-level bitmap) of the one or more bitmaps of the RMP configuration allowing the wireless device to determine the fourth set of RBs. Instead, by linking the RMP configuration with the SBFD configuration (or SBFD pattern), as example embodiments of FIG. 27, FIG. 28, and FIG. 29 below demonstrate, the base station may allow the wireless device to properly determine the fourth set of RBs based on the linked SBFD configuration / pattern.

[0510] The embodiment of FIG. 27 may allow the base station / a wireless device (e.g., the first wireless device and / or the second wireless device) to link (or establish a linkage) between a first RMP (e.g., configured via pattemType in a first rateMatchPattem for determining the fourth set of RBs (or the at least one RE / RB) as un avai lable / reserved resources for receiving the PDSCH in the SBFD symbol of the at least one SBFD symbol. FIG. 27 shows an example of a first RMP configuration (the first rateMatchPattem) of the plurality of RMP configuration. Compared to an RMP configuration shown in FIG. 21 A, the first RMP configuration may further indicate / configure a first indication for linking the first RMP with the SBFD configuration. The SBFD configuration may comprise the one or more SBFD configuration parameters.

[0511] The first indication may be a “subband-downlink” indication / parameter. Other names are also possible. For example, the first indication may also be referred to by “bitmap-Ext” or the like. The first indication provides / configures the linkage / association between the first RMP and the SBFD configuration.

[0512] FIG. 27 also shows an example of the SBFD configuration. The embodiment of FIG. 24 discussed above may provide examples of the SBFD configuration. For example, the SBFD configuration may configure the SBFD subband frequency-time resources, e.g., the one or more SBFD symbols. The SBFD configuration may comprise / indicate a periodicity (e.g., the first SBFD periodicity or the second SBFD periodicity). The SBFD subband time resources may comprise the periodicity and the one or more SBFD symbols. The SBFD subband frequency resources may comprise at least one of: UL sub-band frequency resources (e.g., the first set of RBs); and / or DL sub-band frequency resources (e.g., the second set of RBs); and guard-band frequency resources (e.g., the third set of RBs).

[0513] In some example, the symbols of the SBFD configuration may configure / indicate the at least one SBFD symbols for determining the PDSCH resource mapping / rate matching. The wireless device may use the at least oneSBFD symbols for determining the at least one RE / RB for rate match PDSCH around in an SBFD symbol of the at least one SBFD symbols. The wireless device may use the at least one SBFD symbols for determining unavailable / reserved resources for receiving the PDSCH in the SBFD symbol of the at least one SBFD symbols.

[0514] The embodiment of FIG. 28 may allow the base station / a wireless device (e.g., the first wireless device and / or the second wireless device) to link (or establish a linkage) between a second RMP (e.g., configured via pattemType in a second rateMatch Pattern) for determining the fourth set of RBs (or the at least one RE / RB) as unavailable / reserved resources for receiving the PDSCH in the SBFD symbol of the at least one SBFD symbol. FIG. 28 shows an example of a second RMP configuration (the second rateMatch Pattern) of the plurality of RMP configurations. Compared to an RMP configuration shown in FIG. 21 A, the second RMP configuration may further indicate / configure a second indication for linking the second RMP with an SBFD pattern. The SBFD pattern may have an SBFD pattern ID.

[0515] For example, the SBFD configuration may configure / indicate at least one SBFD pattern (e.g., SBFD pattern 1 and / or SBFD pattern 2). The second indication of the second RMP configuration may link the second RMP configuration with at least one of the SBFD pattern 1 or the SBFD pattern 2. For example, the SBFD pattern 1 has a first SBFD pattern ID and the SBFD pattern 2 has a second SBFD pattern ID.

[0516] The second indication may be a “subband-downlink” indication / parameter. Other names are also possible, e.g., “subband-pattern”. For example, the indication may also be referred to by “bitmap-Ext” or the like. The second indication provides / configures the linkage / association, using an SBFD pattern ID, between the first RMP and the SBFD pattern with the SBFD pattern ID.

[0517] FIG. 28 also shows an example of the SBFD pattern. The embodiment of FIG. 24 discussed above may provide examples of the SBFD pattern. The SBFD pattern may correspond to the SBFD pattern ID. In the example of FIG. 28, the second indication uses the SBFD pattern ID to indicate / link the SBFD pattern associated with / correspond to the second RMP. For example, the SBFD pattern may configure the SBFD subband frequency-time resources. The SBFD subband frequency-time resources may comprise / configure the one or more SBFD symbols. The SBFD configuration may comprise / indicate a periodicity (e.g., the first SBFD periodicity or the second SBFD periodicity). For example, when the SBFD pattern ID is the first the SBFD pattern ID, the periodicity may be the first SBFD periodicity. When the SBFD pattern ID is the second the SBFD pattern ID, the periodicity may be the second SBFD periodicity. The SBFD subband time resources may comprise the periodicity and the one or more SBFD symbols. The SBFD subband frequency resources may comprise at least one of: UL sub-band frequency resources (e.g., the first set of RBs); and / or DL sub-band frequency resources (e.g., the second set of RBs); and guard-band frequency resources (e.g., the third set of RBs).

[0518] In some examples, the symbols of the associated / l inked SBFD pattern may configure / indicate the at least one SBFD symbols for determining the PDSCH resource mapping / rate matching. The wireless device may use the at least one SBFD symbols for determining the at least one RE / RB for rate match PDSCH around in an SBFD symbol of the atleast one SBFD symbols. The wireless device may use the at least one SBFD symbols for determining unavailable / reserved resources for receiving the PDSCH in the SBFD symbol of the at least one SBFD symbols.

[0519] In some cases, the second indication of the second RMP configuration may link the second RMP configuration with the SBFD pattern 1. For example, the second indication of a fifth RMP configuration (of the plurality of RMP configurations) may link the fifth RMP configuration with the SBFD pattern 2. The fourth RMP configuration may configure / indicate a fourth RMP of the one or more RMPs. Embodiments may allow link different SBFD patterns to different RMP configurations.

[0520] The embodiment of FIG. 29 may allow the base station / a wireless device (e.g., the first wireless device and / or the second wireless device) to link (or establish a linkage) between a third RMP (e.g., configured via pattemType in a third rateMatchPattem) for determining the fourth set of RBs (or the at least one RE / RB) as unavailable / reserved resources for receiving the PDSCH in the SBFD symbol of the at least one SBFD symbol. FIG. 29 shows an example of a third RMP configuration (the second rateMatchPattem of the plurality of RMP configurations. Compared to an RMP configuration shown in FIG. 21 A, the third RMP configuration may further indicate / configure a third indication for linking the third RMP with an TDD configuration for rate matching (e.g., TDD-rateMatch-Pattern). The TDD configuration for rate matching may be associated with an identifier / ID / index (e.g., TDD-rateMatch-ID).

[0521] FIG. 29 also shows an example of the one or more TDD configuration parameters. In example of FIG. 29, the one or more TDD configuration parameters may be the one or more common TDD configuration parameters (e.g., TDD-UL-DL-con fig Common). Similarly, the one or more TDD configuration parameters may be the one or more dedicated TDD configuration parameters (e.g., TDD-UL-DL-configDedicated). Compared to the one or more common TDD configuration parameters provided in FIG. 17, as FIG. 29 also shows, the one or more TDD configuration parameters comprise an indication / parameterfor a TDD rate matching pattern (e.g., rateMatch-pattern). The TDD rate matching pattern indicating / parameter may indicate / identify the TDD configuration for rate matching with the identifier / ID / index (e.g., TDD-rateMatch-ID) identified / indicated by the third indication of the third RMP configuration.

[0522] As also shown in FIG. 29, the TDD configuration for rate matching may comprise the associated identifier / ID / index (e.g., TDD-rateMatch-ID) and / or the SBFD configuration or the SBFD pattern. As example of the SBFD configuration or the SBFD pattern provided in FIG. 29.

[0523] When only one SBFD pattern is configured by the one or more configuration parameters, the TDD configuration for rate matching may comprise the SBFD configuration. As also discussed above in connection with FIG. 27, the wireless device may use the SBFD configuration (linked by the third indication) for determining the fourth set of RBs (e.g., the at least one RE / RB) as unavailable for receiving the PDSCH in an SBFD symbol of the at least one SBFD symbol.

[0524] When more than one SBFD pattern (e.g., the SBFD pattern 1 and the SBFD pattern 2) is configured by the one or more configuration parameters, the TDD configuration for rate matching may comprise the SBFD pattern. As also discussed above in connection with FIG. 28, the wireless device may use the SBFD pattern (linked by the thirdindication) for determining the fourth set of RBs (e.g. , the at least one RE / RB) as unavailable for receiving the PDSCH in an SBFD symbol of the at least one SBFD symbol.

[0525] Using the linkage, signaling overhead for configuring the rate matching parent may reduce. For example, some embodiments of the present disclosure may reduce requirement for the base station to configure a new bitmap (e.g., a pair of RB-level bitmap and symbol-level bitmap) of the one or more bitmaps of the RMP configuration. Without the embodiments of the present disclosure, the new bitmap needs to be configured based on the one or more configuration parameters, which may increase the signaling overhead. Instead, by linking the RMP configuration with the SBFD configuration (or SBFD pattern), as example embodiments of FIG. 27, FIG. 28, and FIG. 29 below demonstrate, the base station may allow the wireless device to properly determine the fourth set of RBs based on the linked SBFD configuration / pattern.

[0526] FIG. 30 also shows another example of configuring the rate matching pattern based on the SBFD configuration (or SBFD pattern). In the example of FIG. 30, a fourth RMP configuration of the plurality of RMP configurations may comprise / indicate one or more fifth bitmaps (bitmaps in pattemType) and a first bitmap (new-bitmap in pattemType). The one or more fifth bitmaps may not comprise the first bitmap. The first bitmap may be associated with (or linked with) the SBFD operation (e.g., the SBFD configuration or the SBFD pattern). For example, the first bitmap may only comprise a symbol-level bitmap (e.g., indicated by symbols). The symbol-level bitmap may indicate the at least one SBFD symbol.

[0527] In one example, the symbols of the first bitmap may indicate / configure the at least one SBFD symbol. There may be a one-to-one mapping between symbols and the one or more SBFD symbols in the SBFD configuration. For example, there may be a (one-to-one) association / linkage or mapping between symbols and the one or more SBFD symbols in a SBFD pattern of the at least one SBFD pattern.

[0528] For example, a first symbol of the symbols may correspond to a first location (or bit) in the symbols. Based on the first location (or bit) being set to a first predefined value (e.g., 1), the wireless device may determine the first symbol of the symbols being indicated. For example, the wireless device may, based on the mapping / association (or linkage) between symbols and the one or more SBFD symbols, determine a first SBFD symbol of the one or more SBFD symbols being in the at least one SBFD symbol. The first SBFD symbol of the one or more SBFD symbols may be a first SBFD symbol of the at least one SBFD symbol.

[0529] For example, a second symbol of the symbols may correspond to a second location (or bit) in the symbols. Based on the second location (or bit) being set to a second predefined value (e.g., 0), the wireless device may determine the second symbol of the symbols not being indicated. For example, the wireless device may, based on the mapping / association (or linkage) between symbols and the one or more SBFD symbols, determine a second SBFD symbol of the one or more SBFD symbols not being in the at least one SBFD symbol. The second SBFD symbol of the one or more SBFD symbols may not be among the at least one SBFD symbol.

[0530] As shown in FIG. 30, a first periodicity (e.g., periodicityAndpattern of the first bitmap) may be the SBFD periodicity of the SBFD configuration / pattern. The first periodicity may comprise the one or more SBFD symbols. The first periodicity may comprise the symbols.

[0531] Compared to each bitmap of the one or more fifth bitmaps, the first bitmap may not comprise an RB-level bitmap. Using the fourth RMP configuration, the base station may reduce signaling overhead for configuring the rate matching pattern in the SBFD operation.

[0532] The wireless device may determine an RB-level bitmap corresponding to the first bitmap based on the symbols and the SBFD configuration / pattern (e.g., the first set of RBs and / or the third set of RBs). For example, when for an SBFD symbol of the at least one SBFD symbol indicated by the symbol-level bitmap, the wireless device may use the first set of RBs and / or the third set of RBs for determining the RB-level bitmap corresponding to the SBFD symbol. The RB-level bitmap may comprise at least one of the first set of RBs and / or the third set of RBs configured by the SBFD configuration. The wireless device may determine the subset of RBs that are not available (or valid) for the PDSCH reception in the corresponding symbol duration based on the determined RB-level bitmap.

[0533] For example, the wireless device may, corresponding to each SBFD symbol of the at least one SBFD symbol indicated by the symbols, determine a subset of RBs of the fourth set of RBs (associated with the fourth RMP) based on the determined RB-level bitmap. The wireless device may determine the at least one RE / RB based on the symbols indicated by the first bitmap of the fourth RMP configuration and the one or more SBFD configuration parameters (e.g., the determined RB-level bitmap).

[0534] FIG. 31A and FIG. 31 B show examples of rate matching for SBFD operation as per an aspect of the present disclosure. The embodiments of FIG. 31 A and FIG. 31 B may be use / based on at least one configuration of the RMP configurations (e.g., the first / second / third / fourth / fifth RMP configuration) that discussed above in connection with FIG. 27, FIG. 28, FIG. 29, or FIG. 30. In some cases, embodiments of FIG. 31 A and FIG. 31 B provide one or more enhancements for the SBFD operation discussed in connection with embodiment(s) of FIG. 24 and / or FIG. 25 and / or FIG. 26.

[0535] As shown in FIG. 31 B, a wireless device (e.g., the first wireless device and / or the second wireless device) may receive the one or more configuration parameters from the base station. The one or more configuration parameter. The one or more configuration parameters may comprise the one or more SBFD configuration parameters (e.g., configured by the SBFD configuration).

[0536] The one or more SBFD configuration parameters may comprise / indicate the one or more SBFD symbols. The one or more SBFD configuration parameters may configure / indicate UL sub-band frequency resources (e.g., the first set of RBs) and / or DL sub-band frequency resources (e.g., the second set of RBs). The one or more SBFD symbols may comprise (or be) the SBFD slot / symbols #1 in FIG. 31 A. The one or more SBFD symbols the at least one SBFD symbol.

[0537] In some cases, the one or more SBFD configuration parameters may configure / indicate guard-band frequency resources (e.g., the third set of RBs)

[0538] The one or more configuration parameters may comprise the plurality of the RMP configurations. An RMP configuration may comprise / indicate / configure an RMP for (or associated with or linked to) the at least one SBFD symbol.

[0539] In one example, the RMP configuration of the plurality of the RMP configurations may be the first RMP configuration shown in FIG. 27. As discussed above, the RMP configuration may indicate / comprise the at least one SBFD symbol. For example, the wireless device may, via the first indication of the RMP configuration (e.g., the first RMP configuration) identify / determine the at least one SBFD symbol.

[0540] In another example, the RMP configuration of the plurality of the RMP configurations may be the second RMP configuration shown in FIG. 28. As discussed above, the RMP configuration may indicate / comprise the at least one SBFD symbol. For example, the wireless device may via the second indication of the RMP configuration (e.g., the second RMP configuration) identify / determine the at least one SBFD symbol.

[0541] In yet another example, the RMP configuration of the plurality of the RMP configurations may be the third RMP configuration shown in FIG. 29. As discussed above, the RMP configuration may indicate / comprise the at least one SBFD symbol. For example, the wireless device may via the third indication of the RMP configuration (e.g., the third RMP configuration) identify / determine the at least one SBFD symbol.

[0542] In yet another example, the RMP configuration of the plurality of the RMP configurations may be the fourth RMP configuration shown in FIG. 30. As discussed above, the RMP configuration may indicate / comprise the at least one SBFD symbol. For example, the wireless device may, via the new-bitmap indication / parameter of the RMP configuration (e.g., the fourth RMP configuration) identify / determine the at least one SBFD symbol.

[0543] In an example embodiment, the wireless device may, for receiving the PDSCH in an SBFD symbol of the at least one SBFD symbol, determine the at least one RE / RB based on the RMP configuration. For example, the wireless device may determine the at least one RE / RB based on the first set of RBs and / or the third set of RBs. The wireless device may determine the plurality of first RBs / RE(s) for receiving the PDSCH overlapping / collid ing with the third set of RBs and / or the first set of RBs. The wireless device may exclude the at least one RE / RB for receiving the PDSCH in the SBFD symbol. The wireless device may determine the at least one RE / RB not being available for receiving the PDSCH in the SBFD symbol.

[0544] FIG. 32 shows an example of rate matching for SBFD operation as per an aspect of the present disclosure. The embodiment of FIG. 32 may be based on at least one RMP configuration of the RMP configurations (e.g., the first / second / third / fourth / fifth RMP configuration) that discussed above in connection with FIG. 27, FIG. 28, FIG. 29, or FIG. 30. In some cases, embodiment of FIG. 32 provides one or more enhancements for the SBFD operation discussed in connection with embodiment(s) of FIG. 24 and / or FIG. 25 and / or FIG. 26.

[0545] As shown in FIG. 32, a wireless device (e.g. , the first wireless device) transmit the one or more capability messages to the base station. The one or more capability messages may comprise / indicate the first SBFD capability (see also FIG. 26). In response to the one or more capability messages comprising / indicating the first SBFD capability, the one or more configuration parameters comprise / configure / indicate the RMP for (or associated with or linked to) the at least one SBFD symbol.

[0546] For example, the one or more configuration parameters may comprise the plurality of the RMP configurations. The RMP configuration may comprise / indicate / configure the RMP for (or associated with or linked to) the at least one SBFD symbol.

[0547] In one example, the RMP configuration of the plurality of the RMP configurations may be the first RMP configuration shown in FIG. 27. As discussed above, the RMP configuration may indicate / comprise the at least one SBFD symbol. For example, the RMP configuration may comprise the first indication (e.g., the first RMP configuration) for identifying / determining the at least one SBFD symbol. The first indication may indicate the RMP for (or associated with or linked to) the at least one SBFD symbol.

[0548] In another example, the RMP configuration of the plurality of the RMP configurations may be the second RMP configuration shown in FIG. 28. As discussed above, the RMP configuration may indicate / comprise the at least one SBFD symbol. For example, the RMP configuration may comprise the second indication (e.g., the second RMP configuration) for identifying / determining the at least one SBFD symbol. The second indication may indicate the RMP for (or associated with or linked to) the at least one SBFD symbol.

[0549] In yet another example, the RMP configuration of the plurality of the RMP configurations may be the third RMP configuration shown in FIG. 29. As discussed above, the RMP configuration may indicate / comprise the at least one SBFD symbol. For example, the RMP configuration may comprise the third indication (e.g., the third RMP configuration) for identifying / determining the at least one SBFD symbol. The third indication may indicate the RMP for (or associated with or linked to) the at least one SBFD symbol.

[0550] In yet another example, the RMP configuration of the plurality of the RMP configurations may be the fourth RMP configuration shown in FIG. 30. As discussed above, the RMP configuration may indicate / comprise the at least one SBFD symbol. For example, the RMP configuration may comprise the new-bitmap indication / parameter (e.g., the fourth RMP configuration) for identifying / determining the at least one SBFD symbol. The new-bitmap indication / parameter may indicate the RMP for (or associated with or linked to) the at least one SBFD symbol.

[0551] The one or more configuration parameter. The one or more configuration parameters may comprise the one or more SBFD configuration parameters (e.g., configured by the SBFD configuration).

[0552] The one or more SBFD configuration parameters may comprise / indicate the one or more SBFD symbols. The one or more SBFD configuration parameters may configure / indicate UL sub-band frequency resources (e.g., the first set of RBs) and / or DL sub-band frequency resources (e.g., the second set of RBs). The one or more SBFD symbols theat least one SBFD symbol. In some cases, the one or more SBFD configuration parameters may configure / indicate guard-band frequency resources (e.g. , the third set of RBs).

[0553] In the present disclosure, when the at least one RE / RB is unavailable for receiving the PDSCH in the SBFD symbol, the at least one RE / RB is invalid (or not valid) for receiving the PDSCH in the SBFD symbol. The wireless device may not use the at least one RE / RB for receiving the PDSCH in the SBFD symbol.

[0554] In the present disclosure, the plurality of first RBs / REs for PDSCH may be based on a frequency domain resource allocation Type 1.

[0555] In the present disclosure, the plurality of first RBs / REs for PDSCH may be based on a frequency domain resource allocation Type O.

[0556] FIG. 32 illustrates an example flowchart of SBFD operation as per an aspect of an embodiment of the present disclosure. A wireless device (e.g., an SBFD-aware wireless device, e.g., the first wireless device) may transmit the one or more capability messages to a base station (e.g., an SBFD-enabled base station). The one or more capability messages may comprise / indicate the first SBFD capability. The first SBFD capability may indicate whether the wireless device supports receiving PDSCH with resource mapping that excludes the RBs / REs corresponding to resource sets of SBFD subband frequency-time locations (e.g., the first / third set of RBs / REs in the at least one SBFD symbol) configured by semi-static SBFD configuration (e.g., the one or more SBFD configuration parameters).

[0557] In an example embodiment, the one or more capability messages may comprise / indicate the at least one rate matching capability and the first SBFD capability. The first rate matching capability (e.g., rateMatchingResrcSetSemi- Static) of the at least one rate matching capability may indicate whether the wireless device supports receiving PDSCH with resource mapping that excludes the REs (e.g., the fourth set of RBs) corresponding to resource sets configured with RB-symbol level granularity indicated by bitmaps (e.g., the plurality of bitmap groups) and contro / ResourceSet (see pattemType in RateMatchPattern) following the semi-static configuration (e.g., the plurality of RMP configurations).

[0558] In an example embodiment, a wireless device (e.g., an SBFD-aware wireless device, e.g., the first wireless device) may transmit the one or more capability messages to a base station (e.g., an SBFD-enabled base station). The one or more capability messages may comprise / indicate the at least one rate matching capability and the first SBFD capability. The first SBFD capability may indicate whether the wireless device supports receiving PDSCH with resource mapping that excludes the RBs / REs corresponding to resource sets of SBFD subband frequency-time locations (e.g., the first / third set of RBs / REs in the at least one SBFD symbol) configured by semi-static SBFD configuration (e.g., the one or more SBFD configuration parameters). The first rate matching capability (e.g., rateMatchingResrcSetSemi- Static) of the at least one rate matching capability may indicate the wireless device supports receiving PDSCH with resource mapping that excludes the REs (e.g., the fourth set of RBs) corresponding to resource sets configured with RB-symbol level granularity indicated by bitmaps (e.g., the plurality of bitmap groups) and contro / ResourceSet (see pattemType in RateMatchPattern) following the semi-static configuration (e.g., the plurality of RMP configurations).

[0559] The second rate matching capability (e.g. , rateMatchingResrcSetDynamic) of the at least one rate matching capability may indicate whether the wireless device supports receiving PDSCH with resource mapping that excludes the REs (e.g., the fourth set of RBs) corresponding to resource sets configured with RB-symbol level granularity indicated by bitmaps (e.g., the plurality of bitmap groups) and controlResourceSet (see patternType in RateMatchPattern) based on a dynamic indication (e.g., the RMI field) in a scheduling DOI. The scheduling DOI may schedule / indicate the receiving PDSCH. The scheduling DOI may activate SPS PDSCH. The PDSCH may be an SPS PDSCH activated by the scheduling DCI.

[0560] In an example embodiment, a wireless device (e.g., an SBFD-aware wireless device, e.g., the first wireless device) may transmit the one or more capability messages to a base station (e.g., an SBFD-enabled base station). The one or more capability messages may comprise / indicate the at least one rate matching capability and the first SBFD capability. The first SBFD capability may indicate whether the wireless device supports receiving PDSCH with resource mapping that excludes the RBs / REs corresponding to resource sets of SBFD subband frequency-time locations (e.g., the first / third set of RBs / REs in the at least one SBFD symbol) configured by semi-static SBFD configuration (e.g., the one or more SBFD configuration parameters). The second rate matching capability (e.g., rateMatchingResrcSetDynamic) of the at least one rate matching capability may indicate the wireless device supports receiving PDSCH with resource mapping that excludes the REs (e.g., the fourth set of RBs) corresponding to resource sets configured with RB-symbol level granularity indicated by bitmaps (e.g., the plurality of bitmap groups) and controlResourceSet (see patternType in RateMatchPattern) based on a dynamic indication (e.g., the RMI field) in a scheduling DCI. The scheduling DCI may schedule / indicate the receiving PDSCH. The scheduling DCI may activate SPS PDSCH. The PDSCH may be an SPS PDSCH activated by the scheduling DCI.

[0561] FIG. 33 illustrates an example flowchart of SBFD operation as per an aspect of an embodiment of the present disclosure. A wireless device (e.g., an SBFD-aware wireless device, e.g., the first wireless device) may transmit the one or more capability messages to a base station (e.g., an SBFD-enabled base station). The one or more capab...

Claims

CLAIMSWhat is claimed is:

1. A method comprising: transmitting, by a wireless device to a base station, one or more user equipment (UE)-capability messages indicating the wireless device supports receiving physical downlink shared channel (PDSCH) with a resource mapping that excludes resource elements (REs), among REs assigned for the PDSCH reception, that are not within one or more downlink sub-bands of a sub-band full-duplex (SBFD) configuration; receiving one or more radio resource control (RRC) messages comprising a first SBFD configuration, wherein the first SBFD configuration indicates: one or more SBFD symbols; and downlink sub-band frequency resources of at least one downlink sub-band; determining, for receiving a first PDSCH in the one or more SBFD symbols, at least one resource element (RE), among a plurality of REs assigned for PDSCH reception, based on the at least one RE not being within the at least one downlink sub-band; and receiving, in the plurality of REs excluding the at least one RE, the first PDSCH during the one or more SBFD symbols.

2. A method comprising: transmitting, by a wireless device to a base station, one or more user equipment (UE)-capability messages indicating the wireless device supports receiving physical downlink shared channel (PDSCH) with a first resource mapping that excludes resource elements (REs), among REs assigned for the PDSCH reception, that are not within one or more downlink sub-bands of a sub-band full-duplex (SBFD) configuration.

3. The method of claim 2, wherein the first resource mapping excludes REs, among the REs assigned for the PDSCH reception, that are within an uplink sub-band of the first SBFD configuration.

4. The method of any one of claims 2 to 3, wherein the first resource mapping excludes REs, among the REs assigned for the PDSCH reception, that are within one or more guard-bands of the first SBFD configuration.

5. The method of any one of claims 2 to 4, wherein the first resource mapping only includes REs, among the REs assigned for the PDSCH reception, that are within the one or more downlink sub-bands of the first SBFD configuration.

6. The method of any one of claims 2 to 5, further comprising receiving one or more radio resource control (RRC) messages comprising a first SBFD configuration, wherein the first SBFD configuration indicates: one or more SBFD symbols; and downlink sub-band frequency resources of at least one downlink sub-band.

7. The method of claims 6, wherein the one or more RRC messages indicate at least one rate matching pattern.

8. The method of claim 7, wherein the at least one rate matching pattern indicates the one or more SBFD symbols.

9. The method of any one of claims 7 to 8, wherein a first rate matching pattern, of the at least one rate matching pattern, comprises a first bitmap indicating first resource sets with a first resource block (RB)-symbol level granularity.

10. The method of claim 9, wherein the first bitmap comprises the one or more SBFD symbols.

11. The method of any one of claims 7 to 10, wherein a rate matching pattern, of the at least one rate matching pattern, corresponds to the SBFD configuration.

12. The method of any one of claims 7 to 11 , wherein the one or more RRC messages further indicate a serving cell configured with the SBFD configuration.

13. The method of claim 12, wherein the at least one rate matching pattern corresponds to at least one of: the serving cell; or a bandwidth part (BWP) of the serving cell.

14. The method of any one of claims 6 to 13, wherein the first SBFD configuration further indicates an uplink subband frequency resources of an uplink sub-band.

15. The method of any one of claims 6 to 14, wherein the first SBFD configuration further indicates guard-band frequency resources.

16. The method of any one of claims 6 to 15, wherein the first SBFD configuration further indicates a rate matching configuration corresponding to the first SBFD configuration.

17. The method of claim 16, wherein the rate matching configuration corresponds to at least one of: the serving cell; or the bandwidth part (BWP) of the serving cell.

18. The method of any one of claims 6 to 17, wherein the one or more RRC messages further indicates the first resource mapping.

19. The method of any one of claims 2 to 18, further comprising determining, for receiving a first PDSCH in one or more SBFD symbols, at least one resource element (RE), among a plurality of REs assigned for a first PDSCH reception, based on the at least one RE not being within at least one downlink sub-band.

20. The method of claim 19, further comprising receiving, in the plurality of REs excluding the at least one RE, the first PDSCH during the one or more SBFD symbols.

21. The method of claim 20, wherein receiving the first PDSCH is via the BWP of the serving cell.

22. The method of any one of claims 19 to 21 , wherein the at least one RE does not overlap in frequency domain with the downlink sub-band frequency resources.

23. The method of any one of claims 19 to 22, wherein the at least one resource element (RE) is within the uplink sub-band.

24. The method of claims 23, wherein the at least one RE overlaps in frequency domain with at least one frequency resource of the uplink sub-band frequency resources.

25. The method of any one of claims 19 to 24, wherein determining the at least one RE is further based on the rate matching pattern.

26. The method of claim 19 to 25, wherein the at least one RE overlaps in frequency domain with at least one frequency resource of the guard-band frequency resources.

27. The method of any one of claims 19 to 26, wherein receiving the PDSCH comprises receiving a repetition of the PDSCH.

28. The method of any one of claims 2 to 27, wherein the one or more UE-capability messages indicate whether the wireless device supports receiving PDSCH with a second resource mapping that excludes second resource elements (REs) indicated by a first matching pattern based on a dynamic indication in a scheduling downlink control information (DOI).

29. The method of claim 28, wherein: a first rate matching pattern comprises a first bitmap indicating first resource sets with a first resource block (RB)-symbol level granularity; and a first rate matching pattern is configured by an RRC message.

30. The method of any one of claims 28 to 29, wherein a scheduling DOI indicates the reception of the second PDSCH.

31. The method of any one of claims 2 to 30, wherein the one or more UE-capability messages indicate whether the wireless device supports receiving PDSCH with a third resource mapping that excludes third resource elements (REs) indicated by a second rate matching pattern following a semi-static configuration.

32. The method of claim 31 , wherein the second rate matching pattern comprises a second bitmap indicating second resource sets with a second resource block (RB)-symbol level granularity.

33. The method of any one of claims 31 to 32, wherein the semi-static configuration is an RRC configuration.

34. The method of any one of claims 28 to 33, the one or more RRC messages further indicates the first rate matching pattern.

35. The method of any one of claims 2 to 34, further comprising receiving a first DCI activating the first PDSCH reception, wherein the first PDSCH is a semi-persistent scheduling (SPS) PDSCH.

36. The method of claim 35, wherein the one or more RRC messages comprise an SPS configuration for the SPS PDSCH.

37. The method of claim 36, further comprising determining the plurality of REs based on at least one of: the first DCI activating the PDSCH reception; or the SPS configuration.

38. The method of any one of claims 36 to 37, wherein the SPS configuration indicates a number of repetitions for the SPS PDSCH.

39. The method of any one of claims 35 to 38, wherein the first DOI indicates the at least one rate matching pattern.

40. The method of any one of claims 2 to 39, further comprising receiving a second DOI scheduling the first PDSCH reception.

41. The method of claim 40, wherein the one or more RRC messages comprise a first PDSCH configuration.

42. The method of any one of claims 40 to 41 , further comprising determining the plurality of REs based on at least one of: the second DCI scheduling the first PDSCH reception; or the first PDSCH configuration.

43. The method of any one of claims 40 to 42, wherein the second DCI indicates the at least one rate matching pattern.

44. The method of any one of claims 41 to 43, wherein the first PDSCH configuration indicates a number of repetitions for the first PDSCH.

45. The method of any one of claims 2 to 44, further comprising determining at least one second resource element (RE), among a plurality of REs, based on at least one rate matching pattern.

46. The method of claim 45, wherein the receiving the first PDSCH further excludes the at least one second RE from the plurality of REs.

47. The method of any one of claims 45 to 46, wherein the at least one second RE is determined based on the first resource sets indicated by the first rate matching pattern.

48. A method comprising: receiving, by a base station from a wireless device, one or more user equipment (UE)-capability messages indicating the wireless device supports receiving physical downlink shared channel (PDSCH) with a first resource mapping that excludes resource elements (REs), among REs assigned for the PDSCH reception, that are not within one or more downlink sub-bands of a sub-band full-duplex (SBFD) configuration.

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

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

Images