Power headroom with duplexing

Abstract

A method can include receiving, by a wireless device and for uplink transmissions via a first cell, a downlink signal indicating: a first power control set for non-sub-band full-duplex (SBFD) symbols; and a second power control set for SBFD symbols. The method can also include transmitting, via a transmission occasion and a second cell, a power headroom report comprising a power headroom level that is computed using a power control set among the first power control set and the second power control set.

Description

Docket No.: 24-1222PCTTITLEPower Headroom with DuplexingCROSS REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of U.S. Provisional Application No. 63 / 699,465, filed September 26, 2024, and U.S. Provisional Application No. 63 / 754,309, filed February 5, 2025, all of which is hereby incorporated by reference in their entireties.BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0033] 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 andDocket No.: 24-1222PCT 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.

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

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

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

[0037] 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 = {cell 1 , cell2} are: {celH }, {cell2}, and {celH , cell2}. The phrase “based on" (or equally “based at least on") is indicative that the phrase following the term “based on” is an example of one of a multitude of suitable possibilities that may, or may not, be employed to one or more of the various embodiments. The phrase “in response to” (or equally “in response at least to”) is indicative that the phrase following the phrase “in response to” is an example of one of a multitude of suitable possibilities that may, or may not, be employed to one or more of the various embodiments. The phrase “depending on” (or equally “depending at least to”) is indicative that the phrase following the phrase “depending on” is an example of one of a multitude of suitable possibilities that may, or may not, be employed to one or more of the various embodiments. The phrase “employing / using” (or equally “employing / using at least”) is indicative that the phrase following the phrase “employing / using" is an example of one of a multitude of suitable possibilities that may, or may not, be employed to one or more of the various embodiments.

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

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

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

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

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

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

[0044] 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. DownlinkDocket No.: 24-1222PCT transmissions may be separated from uplink transmissions using frequency division duplexing (FDD), timedivision duplexing (TDD), and / or some combination of the two duplexing techniques.

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

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

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

[0048] 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 / similarDocket No.: 24-1222PCT 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.

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

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

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

[0052] The 5G-CN 152 provides the UEs 156 with an interface to one or more DNs, such as public DNs (e.g., the Internet), private DNs, and / or intra-operator DNs. As part of the interface functionality, the 5G-CN 152 may set up end-to-end connections between the UEs 156 and the one or more DNs, authenticate the UEs 156, and provide charging functionality. Compared to the CN of a 3GPP 4G network, the basis of the 5G-CN 152 may be a service-based architecture. This means that the architecture of the nodes making up the 5G-CN 152 may be defined as network functions that offer services via interfaces to other networkDocket No.: 24-1222PCT 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).

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

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

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

[0056] 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 ofDocket No.: 24-1222PCT 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.

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

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

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

[0060] 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). AlthoughDocket No.: 24-1222PCT 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.

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

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

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

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

[0065] 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 unauthorizedDocket No.: 24-1222PCT decoding of data transmitted over the air interface, and integrity protection (to ensure control messages originate from intended sources. The PDCPs 214 and 224 may perform retransmissions of undelivered packets, in-sequence delivery and reordering of packets, and removal of packets received in duplicate due to, for example, an intra-g NB handover. The PDCPs 214 and 224 may perform packet duplication to improve the likelihood of the packet being received and, at the receiver, remove any duplicate packets. Packet duplication may be useful for services that require high reliability.

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

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

[0068] The MACs 212 and 222 may perform multiplexing / demultiplexing of logical channels and / or mapping between logical channels and transport channels. The multiplexing / demultiplexing may include multiplexing / demultiplexing of data units, belonging to the one or more logical channels, into / from Transport Blocks (TBs) delivered to / from the PHYs 211 and 221 . The MAC 222 may be configured to perform scheduling, scheduling information reporting, and priority handling between UEs by means of dynamic scheduling. Scheduling may be performed in the gNB 220 (at the MAC 222) for downlink and uplink. The MACs 212 and 222 may be configured to perform error correction through Hybrid Automatic Repeat Request (HARQ) (e.g., one HARQ entity per carrier in case of Carrier Aggregation (CA)), priority handling between logical channels of the UE 210 by means of logical channel prioritization, and / or padding. The MACs 212 and 222 may support one or more numerologies and / or transmission timings. In an example, mapping restrictions in a logical channel prioritization may control which numerology and / or transmission timing a logical channel may use. As shown in FIG. 3, the MACs 212 and 222 may provide logical channels as a service to the RLCs 213 and 223.Docket No.: 24-1222PCT

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0100] 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 stationsDocket No.: 24-1222PCT 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.

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

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

[0103] 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 beDocket No.: 24-1222PCT 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).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0118] 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 cyclicDocket No.: 24-1222PCT 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).

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

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

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

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

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

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

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

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

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

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

[0129] 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 mobilityDocket No.: 24-1222PCT 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).

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

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

[0132] FIG. 10B illustrates an example of how aggregated cells may be configured into one or more PUCCH groups. A PUCCH group 1010 and a PUCCH group 1050 may include one or more downlink CCs, respectively. In the example of FIG. 10B, the PUCCH group 1010 includes three downlink CCs: a PCell 1011 , an SCell 1012, and an SCell 1013. The PUCCH group 1050 includes three downlink CCs in the present example: a PCell 1051 , an SCell 1052, and an SCell 1053. One or more uplink CCs may be configured as a PCell 1021 , an SCell 1022, and an SCell 1023. One or more other uplink CCs may be configured as a primary SCell (PSCell) 1061 , an SCell 1062, and an SCell 1063. Uplink control information (UCI) related to the downlink CCs of the PUCCH group 1010, shown as UC1 1031 , UC1 1032, and UCI 1033, may be transmitted in the uplink of the PCell 1021. Uplink control information (UCI) related to the downlink CCs of the PUCCH group 1050, shown as UC1 1071 , UC1 1072, and UC1 1073, may be transmitted in the uplink of the PSCell 1061 . In an example, if the aggregated cells depicted in FIG. 10B were not divided into the PUCCH group 1010 and the PUCCH group 1050, a single uplink PCell to transmitDocket No.: 24-1222PCTUCI 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.

[0133] 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 disclosure may mean that a cell comprising the first carrier is activated.

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

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

[0136] 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 may assume a subcarrier spacing for the SS / PBCH block based on the carrier frequency being monitored, unless the radio network configured the UE to assume a different subcarrier spacing.Docket No.: 24-1222PCT

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0154] 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 fewerDocket No.: 24-1222PCT 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.

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

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

[0157] An antenna port is defined such that the channel over which a symbol on the antenna port is conveyed can be inferred from the channel over which another symbol on the same antenna port is conveyed. If a first symbol and a second symbol are transmitted on the same antenna port, the receiver may infer the channel (e.g., fading gain, multipath delay, and / or the like) for conveying the second symbol on the antenna port, from the channel for conveying the first symbol on the antenna port. A first antenna port and a second antenna port may be referred to as quasi co-located (QCLed) if one or more large-scale properties of the channel over which a first symbol on the first antenna port is conveyed may be inferredDocket No.: 24-1222PCT 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.

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

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

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

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

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

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

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

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

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

[0167] A network (e.g., a gNB and / or an ng-eNB of a network) and / or the UE may initiate a random access procedure. A UE in an RRCJDLE state and / or an RRCJNACTIVE state may initiate the random access procedure to request a connection setup to a network. The UE may initiate the random access procedure from an RRC_CONNECTED state. The UE may initiate the random access procedure to request uplink resources (e.g., for uplink transmission of an SR when there is no PUCCH resource available) and / orDocket No.: 24-1222PCT 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.

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

[0169] 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 3 1313. Based on the one or more RACH parameters, the UE may determine a reception timing and a downlink channel for receiving the Msg 2 1312 and the Msg 4 1314.

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

[0171] 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 targetDocket No.: 24-1222PCT 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).

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

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

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

[0175] The Msg 2 1312 received by the UE may include an RAR. In some scenarios, the Msg 2 1312 may include multiple RARs corresponding to multiple UEs. The Msg 2 1312 may be received after or in response to the transmitting of the Msg 1 1311. The Msg 2 1312 may be scheduled on the DL-SCH and indicated on a PDCCH using a random access RNTI (RA-RNTI). The Msg 2 1312 may indicate that the Msg 1 1311 was received by the base station. The Msg 2 1312 may include a time-alignment command that may be used by the UE to adjust the UE's transmission timing, a scheduling grant for transmission of the Msg 3 1313, and / or a Temporary Cell RNTI (TC-RNTI). After transmitting a preamble, the UE may start a time window (e.g., ra-ResponseWindow) to monitor a PDCCH for the Msg 2 1312. The UE may determine when to start the time window based on a PRACH occasion that the UE uses to transmit 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:

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

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

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

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

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

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

[0182] 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 con tent! on -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.

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

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

[0185] The UE may initiate the two-step random access procedure in FIG. 13C for licensed spectrum and / or unlicensed spectrum. The UE may determine, based on one or more factors, whether to initiate theDocket No.: 24-1222PCT 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.

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

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

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

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

[0190] 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 ofDocket No.: 24-1222PCT 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).

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

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

[0193] After scrambling a DCI with a RNTI, the base station may process the DCI with channel coding (e.g , polar coding), rate matching, scrambling and / or QPSK modulation. A base station may map the coded and modulated DCI on resource elements used and / or configured for a PDCCH. Based on a payloadDocket No.: 24-1222PCT 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).

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

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

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

[0197] 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. TheDocket No.: 24-1222PCTUE 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).

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

[0199] 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 twoDocket No.: 24-1222PCT 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.

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

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

[0202] 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 networkDocket No.: 24-1222PCT100 illustrated in FIG. 1 A, 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.

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

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

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

[0206] 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 ofDocket No.: 24-1222PCT transport channels to physical channels, demodulation of physical channels, MIMO or multi-antenna processing, and / or the like.

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

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

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

[0210] The processing system 1508 and / or the processing system 1518 may be connected to one or more peripherals 1516 and one or more peripherals 1526, respectively. The one or more peripherals 1516 and the one or more peripherals 1526 may include software and / or hardware that provide features and / or functionalities, for example, a speaker, a microphone, a keypad, a display, a touchpad, a power source, a satellite transceiver, a universal serial bus (USB) port, a hands-free headset, a frequency modulated (FM) radio unit, a media player, an Internet browser, an electronic control unit (e.g., for a motor vehicle), and / or one or more sensors (e.g., an accelerometer, a gyroscope, a temperature sensor, a radar sensor, a lidar sensor, an ultrasonic sensor, a light sensor, a camera, and / or the like). The processing system 1508 and / or the processing system 1518 may receive user input data from and / or provide user output data to the one orDocket No.: 24-1222PCT 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.

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

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

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

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

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

[0216] 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 disclosure 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0023] The cell may be, for example, an NTN cell. For example, configuration parameters 1708 may comprise one or more NTN-specific / related configuration parameters. The cell may be an NTN cell, forDocket No.: 24-1222PCT example, based on configuration parameters 1708 comprising or indicating the one or more NTN- specific / related configuration parameters.

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

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

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

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

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

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

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

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

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

[0033] In some embodiments, a slot may comprise one or more symbols (e.g., 14 symbols).

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

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

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

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

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

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

[0040] Configuration parameters 1708 may be, comprise, or be referred to as TDD-DL-UL- ConfigCommon.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0070] In an example, message(s) 1706 and / or configuration parameters 1708 may indicate that symbol 1804 is a DL symbol. Message(s) 1706 and / or configuration parameters 1708 may indicate that symbol 1806 is a DL symbol. Message(s) 1706 and / or configuration parameters 1708 may indicate that symbol 1812 is a UL symbol.Docket No.: 24-1222PCT

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0104] In some embodiments, “flexible symbols” and “flexible TDD symbols" may be used interchangeably.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0122] SBFD may be referred to as sub-band FDD and / or “flexible duplex.”

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0140] In some embodiments, transmitting an RA preamble may be referred to as, for example, PRACH transmission or performing a PRACH transmission. An RA preamble may, for example, be referred to as Msg1 , Message 1 , PRACH, PRACH transmission, RACH, RACH transmission, preamble, MsgA PRACH, MsgA preamble, and / or the like. Msg 1 1311 is an example of an RA preamble. Msg A 1331 and / or preamble 1341 are examples of an RA preamble. The RA preamble may be transmitted (e.g., by the wireless device) via (e.g., on, in during, with, using, based on) a PRACH occasion. The PRACH occasion may be referred to as RO, RACH occasion, random access channel occasion, transmission occasion, and / or any other name that indicates a time, frequency, and / or beam related resource used for transmitting an RA preamble.Docket No.: 24-1222PCT

[0141] In some embodiments, PRACH transmission may comprise a plurality of repetitions of an RA preamble. In such cases, a PRACH occasion may comprise a plurality of (or a set of) PRACH occasions. For example, the wireless device may transmit the plurality of repetitions of the RA preamble via the plurality of PRACH occasions, wherein each of the plurality of repetitions of the RA preamble is transmitted via a respective PRACH occasion of the plurality of PRACH occasions.

[0142] In some embodiments, “PRACH occasion” may be replaced with “a set of PRACH occasions” or “a plurality of PRACH occasions .” Any of the embodiments described in the present disclosure for a PRACH occasion may be extended to the plurality of PRACH occasions (e.g., each of the plurality of PRACH occasions or at least one of the plurality of PRACH occasions).

[0143] Any of the embodiments described in the present disclosure for a PRACH transmission may be extended to a plurality of repetitions of an RA preamble (e.g., each of the plurality of repetitions or at least one of the plurality of repetitions).

[0144] In some embodiments, a plurality of repetitions of the RA preamble may be referred to as multiple PRACH transmissions. Any of the embodiments described in the present disclosure for a PRACH transmission may be extended to multiple PRACH transmissions (e.g., each of the multiple PRACH transmissions or at least one of the multiple PRACH transmissions).

[0145] In some embodiments, indicating a TCI state may be the same as indicating a TCI state ID (e.g., TCI state index or identity or identifier) that indicates the TCI state.

[0146] In some embodiments, “TCI state” may be referred to as “TCI state ID” that identifies the TCI state.

[0147] In some embodiments “TCI state” may be swapped for “TCI state ID” or vice versa.

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

[0149] In the example of FIG. 19A, a wireless device (e.g., wireless device 1700) receives a control command 1902. In an example, message(s) 1706 may be (or comprise) control command 1902.

[0150] In an example, control command 1902 may be (or comprise) a MAC CE. For example, control command 1902 may be a Unified TCI States Activation / Deactivation MAC CE or a TCI States Act! vation / Deactivation MAC CE.

[0151] In an example, control command 1902 may be (or comprise) a DCI. For example, control command 1902 may be a DCI format X_Y, where X = 0, 1, 2, 3, 4, ... and Y = 0, 1 , 2, 3, 4, ....

[0152] Control command 1902 may indicate a TCI state 1904. Control command 1902 may indicate a TCI state 1906. For example, control command 1902 may indicate (or comprise a field indicating) a TCI codepoint that indicates (or is mapped to) TCI state 1904 and / or TCI state 1906.Docket No.: 24-1222PCT

[0153] In an example, TCI state 1904 may be for non-SBFD mode. For example, the wireless device may use TCI state 1904 for UL transmissions (and / or DL receptions) via one or more non-SBFD symbols.

[0154] In an example, TCI state 1906 may be for SBFD mode. For example, the wireless device may use TCI state 1906 for UL transmissions (and / or DL receptions) via one or more SBFD symbols.

[0155] TCI state 1904 may be, for example, a DL or joint TCI state. In another example, TCI state 1904 may be a UL TCI state.

[0156] TCI state 1906 may be, for example, a DL or joint TCI state. In another example, TCI state 1906 may be a UL TCI state.

[0157] TCI state 1904 may comprise (or be associated with) power control sets 1908. For example, power control sets 1908 may be for TCI state 1904.

[0158] TCI state 1906 may comprise (or be associated with) power control sets 1912. For example, power control sets 1912 may be for TCI state 1906.

[0159] In an example, configuration parameters 1708 may indicate that power control sets 1908 are for TCI state 1904 and / or power control sets 1912 are for TCI state 1906. For example, configuration parameters 1708 may comprise or indicate a plurality of TCI states. The plurality of TCI states may comprise or indicate TCI state 1904 and / or TCI state 1906. Configuration parameters 1708 may indicate respective power control sets for each of the plurality of TCI states. For example, configuration parameters 1708 may indicate power control sets 1908 for TCI state 1904 and / or power control sets 1912 for TCI state 1906.

[0160] Control command 1902 may indicate (and / or activate) TCI state 1904 and / or TCI state 1906.

[0161] In an example, the wireless device may transmit a UL signal 1914. The wireless device may determine whether to use TCI state 1904 or TCI state 1906 to transmit UL signal 1914 based on whether UL signal 1914 is transmitted via one or more SBFD symbols.

[0162] In an example, the wireless device may transmit UL signal 1914 via one or more non-SBFD symbols (e.g., UL and / or flexible symbols). The wireless device may use TCI state 1904 to transmit UL signal 1914 based on transmitting UL signal 1914 via one or more non-SBFD symbols.

[0163] In an example, the wireless device may transmit UL signal 1914 via one or more SBFD symbols. The wireless device may use TCI state 1906 to transmit UL signal 1914 based on transmitting UL signal 1914 via one or more SBFD symbols.

[0164] In an example, the wireless device may transmit UL signal 1914 via one or more SBFD symbols and one or more non-SBFD symbols (e.g., a first repetition of UL signal 1914 via one or more SBFD symbols and a second repetition of UL signal 1914 via one or more non-SBFD symbols). The wireless device may transmit UL signal 1914 using both TCI state 1904 and TCI state 1906 based on transmitting UL signal 1914 via one or more SBFD symbols and one or more non-SBFD symbols (e.g., a first repetitionDocket No.: 24-1222PCT of UL signal 1914 via one or more SBFD symbols and a second repetition of UL signal 1914 via one or more non-SBFD symbols). For example, the wireless device may transmit the first repetition of UL signal 1914, via one or more SBFD symbols, using TCI state 1906. The wireless device may transmit the second repetition of UL signal 1914, via one or more non-SBFD symbols, using TCI state 1904.

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

[0166] In the example of FIG. 19B, a wireless device (e.g., wireless device 1700) receives a control command 1922. In an example, message(s) 1706 may be (or comprise) control command 1922. Control command 1922 may be, for example, the same as (or comprise) control command 1902.

[0167] Control command 1922 may indicate a TCI state 1924. For example, control command 1922 may indicate a TCI state codepoint (or control command 1922 may comprise a field indicating the TCI state codepoint). The TCI state codepoint may indicate (or be mapped to) TCI state 1924.

[0168] TCI state 1924 may be for both SBFD and non-SBFD modes. For example, the wireless device may use TCI state 1924 for UL transmissions (and / or DL receptions) via one or more SBFD symbols. The wireless device may use TCI state 1924 for UL transmissions (and / or DL receptions) via one or more non- SBFD symbols.

[0169] TCI state 1924 may be comprise (or be associated with) power control sets 1928 and power control sets 1932. Power control sets 1928 may be for non-SBFD mode. Power control sets 1932 may be for SBFD mode. Power control sets 1928 may be for TCI state 1924. Power control sets 1932 may be for TCI state 1924. In an example, the wireless device may use power control sets 1928 to transmit a UL signal via one or more non-SBFD symbols. The wireless device may use power control sets 1932 to transmit a UL signal via one or more SBFD symbols.

[0170] In an example, configuration parameters 1708 may indicate power control sets 1928 and power control sets 1932 being for TCI state 1924. For example, configuration parameters 1708 may indicate the plurality of TCI states. The plurality of TCI states may comprise TCI state 1924.

[0171] In the example of FIG. 19B, the wireless device transmits a UL signal 1934. The wireless device may use TCI state 1924 to transmit the UL signal. The wireless device may determine whether to use power control sets 1928 and / or power control sets 1932 for transmitting UL signal 1934 based on whether the wireless device transmits UL signal 1934 via one or more SBFD symbols. The wireless device may use TCI state 1924 to transmit UL signal 1934 regardless of whether UL signal 1934 is transmitted via one or more SBFD symbols. TCI state 1924 may be for both SBFD and non-SBFD mode.

[0172] In an example, the wireless device may transmit UL signal 1934 via one or more non-SBFD symbols. The wireless device may use TCI state 1924 to transmit UL signal 1934 based on the wirelessDocket No.: 24-1222PCT device transmitting UL signal 1934 via one or more non-SBFD symbols. The wireless device may use power control sets 1928 to transmit UL signal 1934, for example, based on transmitting UL signal 1934 via one or more non-SBFD symbols.

[0173] In another example, the wireless device may transmit UL signal 1934 via one or more SBFD symbols. The wireless device may use TCI state 1924 to transmit UL signal 1934 based on the wireless device transmitting UL signal 1934 via one or more SBFD symbols. The wireless device may use power control sets 1932 to transmit UL signal 1934, for example, based on transmitting UL signal 1934 via one or more SBFD symbols.

[0174] Power control sets (e.g ., power control sets 1908, power control sets 1912, power control sets 1928, power control sets 1932) may comprise one or more power control sets each for a specific channel. For example, the power control sets may comprise a power control set for PUSCH (e.g., pOAIphaSetforPUSCH), a power control set for PUCCH (e.g., pOAIphaSetforPUCCH), and / or a power control set for SRS (e.g., pOAIphaSetforSRS).

[0175] Using power control sets to transmit a UL signal (e.g., UL signal 1914, UL signal 1934) may comprise using a power control set, of the power control sets, to transmit the UL signal based on which channel the UL signal is transmitted on or via. For example, the UL signal may be a PUSCH transmission. Using the power control sets to transmit the UL signal may comprise using the power control set for PUSCH to transmit the UL signal based on the UL signal being a PUSCH transmission. For example, the UL signal may be a PUCCH transmission. Using the power control sets to transmit the UL signal may comprise using the power control set for PUCCH to transmit the UL signal based on the UL signal being a PUCCH transmission. For example, the UL signal may be an SRS transmission. Using the power control sets to transmit the UL signal may comprise using the power control set for SRS to transmit the UL signal based on the UL signal being an SRS transmission.

[0176] In some embodiments, using a power control set (e.g., the power control set for PUSCH, the power control set for PUCCH, the power control set for SRS) to transmit a UL signal (e.g., UL signal 1914, UL signal 1934) may comprise determining a transmission power of the UL signal based on or using the power control set (and / or transmitting the UL signal with or using the transmission power). For example, the power control set may comprise one or more power control parameters. For example, the power control parameters may be (or comprise) a received power value (e.g., pO), a resource index indicating a pathloss RS (e.g., q_d, SSB, CSI-RS), a pathloss factor (e.g., alpha), and / or a closed loop index (e.g., f, g, h). Determining the transmission power based on or using the power control set may comprise determining the transmission power using the power control parameters in (or indicated by or comprised in) the power control set. For example, the wireless device may determine the transmission power based on or using an equation. The equation may comprise the transmission power. The equation may comprise the powerDocket No.: 24-1222PCT control parameters For example, the equation may be, the transmission power = the received power value + the alpha * pathloss + the closed loop index, wherein the wireless device may determine pathloss based on measuring (or receiving) the pathloss RS. The wireless device may transmit the UL signal using or with the transmission power.

[0177] In some embodiments, transmission power may be referred to as transmit power.

[0178] Using a TCI state (e.g., TCI state 1904, TCI state 1906, TCI state 1924) to transmit a UL signal (e.g ., UL signal 1914, UL signal 1934) may comprise: determining a spatial filter (e.g., spatial domain filter, spatial domain transmission filter, transmit beam, beam, and / or any other transmission parameter in the spatial domain) to transmit the UL signal; determining a transmission power using or with power control sets associated with or for the TCI state; transmitting the UL signal using or with the transmission power; and / or transmitting the UL signal using or with the spatial filter.

[0179] In an example, configuration parameters 1708 may indicate power control sets 1928 and power control sets 1932 (e.g., explicitly). For example, configuration parameters 1708 may comprise parameters that each indicate a value for each power control parameter of each power control set of power control sets 1928 and / or power control sets 1932.

[0180] In another example, configuration parameters 1708 may indicate one or more offsets. The wireless device may determine power control sets 1932, for example, based on the one or more offsets and power control sets 1928. For example, the wireless device may determine power control sets 1932 = the one or more offsets + power control sets 1928.

[0181] In another example, the wireless device may determine power control sets 1928, for example, based on the one or more offsets and power control sets 1932. For example, the wireless device may determine power control sets 1928 = the one or more offsets + power control sets 1932.

[0182] UL signal 1914 may be, for example, a RUSCH transmission, a PUCCH transmission, an SRS transmission, a PRACH transmission, and / or any other uplink transmission.

[0183] UL signal 1934 may be, for example, a PUSCH transmission, a PUCCH transmission, an SRS transmission, a PRACH transmission, and / or any other uplink transmission.

[0184] Transmitting or receiving signals via a symbol (or slot) may be the same as or referred to as transmitting or receiving the signals on, in, with, during, based on, or using the symbol (or slot).

[0185] Transmitting or receiving signals via a cell may be the same as or referred to as transmitting or receiving the signals in, on, with, to, toward, from, towards, for, or of the cell.

[0186] The wireless device may transmit a PHR via PUSCH.

[0187] The wireless device may trigger a PHR, for example, based on a PHR prohibit timer (e.g., phr- ProhibitTimer) expiring or being expired and / or path loss has changed more than a pathloss threshold (e.g., phr-Tx-PowerFactorChange dB) for at least one RS used as pathloss reference for one activated ServingDocket No.: 24-1222PCTCell (e.g., a cell 2010 or a cell 2020) of which an active DL BWP is not dormant BWP since a last transmission of a PHR the wireless device has UL resources for new transmission.

[0188] The wireless device may trigger the PHR, for example, based on a PHR periodic timer (e.g., phr- PeriodicTimer) expiring. In an example, configuration parameters 1708 may indicate the PHR prohibit timer, the pathloss threshold, and / or the PHR periodic timer. For example, configuration parameters 1708 may comprise or indicate a parameter that indicates the PHR prohibit timer. Configuration parameters 1708 may comprise or indicate a parameter that indicates the pathloss threshold. Configuration parameters 1708 may comprise or indicate a parameter that indicates the PHR periodic timer.

[0189] The wireless device may trigger the PHR, for example, based on configuration parameters 1708 configuring or reconfiguring power headroom reporting functionality by upper layers, which does not disable the function.

[0190] The wireless device may trigger the PHR, for example, based on activation of an SCell (e.g., configuration parameters 1708 activating the SCell) of the wireless device with configured uplink of which firstActiveDownlinkBWP-ld is not set to dormant BWP.

[0191] The wireless device may trigger the PHR, for example, based on activation of an SCG (e.g., based on configuration parameters 1708 activating an SCG).

[0192] The wireless device may trigger the PHR, for example, based on addition of a PSCell (e.g., configuration parameters 1708 adding a PSCell to the wireless device).

[0193] The wireless device may trigger the PHR, for example, based on the PHR prohibit timer expiring, when the wireless device has UL resources for new transmission, and the following is true for any of the activated Serving Cells (e.g., cell 2010 and / or cell 2020) of with configured uplink: there are UL resources allocated for transmission or there is a PUCCH transmission on the cell (e.g., cell 2010 and / or cell 2020), and the required power backoff due to power management for the cell has changed more than the pathloss threshold (phr-Tx-PowerFactorChange dB) since the last transmission of a PHR when the wireless device had UL resources allocated for transmission or PUCCH transmission on the cell.

[0194] The wireless device may trigger the PHR, for example, based on switching of activated BWP from dormant BWP to non-dormant DL BWP of an SCell with configured uplink.

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

[0196] In the example of FIG. 20A, the wireless device (e.g., wireless device 1700) may trigger a power headroom report (PHR) at TO. The wireless device may trigger the PHR based on one or more of the factors explained above. TO may be a time instance, time interval, time duration, time window, time, timeDocket No.: 24-1222PCT slot, slot, symbol, time symbol, time period, sub-frame, radio frame, system frame, and / or any other unit of time or time interval.

[0197] In the example of FIG. 20A, the wireless device may transmit a PHR 2002 via cell 2010. The wireless device may transmit PHR 2002 via PUSCH or PUCCH.

[0198] PHR 2002 may be or comprise, for example, a PHR MAC CE. PHR 2002 may be or comprise, for example, a single entry PHR MAC CE. PHR 2002 may be or comprise, for example, a multiple entry PHR MAC CE. PHR 2002 may be or comprise, for example, Enhanced Single Entry PHR MAC CE. PHR 2002 may be or comprise, for example, Enhanced Multiple Entry PHR MAC CE. PHR 2002 may be or comprise, for example, Enhanced Single Entry PHR for multiple TRP MAC CE. PHR 2002 may be or comprise, for example, Enhanced Multiple Entry PHR for multiple TRP MAC CE.

[0199] In an example, PHR 2002 may comprise or indicate a PH value or level. The PH value or level may be of, for, associated with, or configured for cell 2020. The wireless device may transmit PHR 2002 via cell 2010. In an example, PHR 2002 may comprise or indicate a second PH value or level. The second PH value or level may be of, for, associated with, or configured for cell 2010.

[0200] In an example, the wireless device may determine (e.g., compute, calculate, estimate, measure) the PH value or level based on an actual or a real UL (e.g., PUSCH) transmission. For example, the wireless device may determine the PH value or level based on the PUSCH transmission via cell 2020 (e.g., shown as “PUSCH" in FIG. 20A), wherein the PUSCH transmission overlaps (in time) with PHR 2002 that is transmitted via cell 2010.

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

[0202] In the example of FIG. 20B, the wireless device (e.g., wireless device 1700) may trigger a power headroom report (PHR) at TO The wireless device may trigger the PHR based on the reasons explained above. TO may be a time instance, time interval, time duration, time window, time, time slot, slot, symbol, time symbol, time period, sub-frame, radio frame, system frame, and / or any other unit of time or time interval.

[0203] In the example of FIG. 20B, the wireless device transmits a PHR 2004. The wireless device transmits PHR 2004 via cell 2010. In an example, PHR 2002 may be different from PHR 2004. The wireless device may transmit PHR 2004 via PUSCH or PUCCH.

[0204] In an example, PHR 2004 may be the same as or comprise PHR 2002.

[0205] PHR 2004 may be or comprise, for example, a PHR MAC CE, a single entry PHR MAC CE, a multiple entry PHR MAC CE, an Enhanced Single Entry PHR MAC CE, an Enhanced Multiple Entry PHR MAC CE, an Enhanced Single Entry PHR for multiple TRP MAC CE, an Enhanced Multiple Entry PHR forDocket No.: 24-1222PCT multiple TRP MAC CE, an Enhanced Single Entry PHR for SPED MAC CE, and / or an Enhanced Multiple Entry PHR for SBFD MAC CE.

[0206] FIG. 20B shows an example of a virtual PHR. PHR 2004 may be or comprise, for example, a virtual PHR. In an example, PHR 2004 may comprise or indicate a PH value or level. The PH value or level may be of, for, associated with, or configured for cell 2020. The wireless device may transmit PHR 2004 via cell 2010, as shown in FIG. 20B.

[0207] In the example of FIG. 20B, there may not be any (actual or real) PUSCH transmission (that is scheduled) in a time interval that overlaps with a slot comprising PHR 2004. In such cases, the wireless device may determine the PH value or level based on a reference PUSCH transmission of cell 2020. For example, the reference PUSCH transmission may not be a real or actual PUSCH transmission. The reference PUSCH transmission may be a phantom (e.g., fake or imaginary) PUSCH transmission. The reference PUSCH transmission may be equivalent to a PUSCH transmission that the wireless device may have transmitted via cell 2020 had there been a PUSCH transmission scheduled for or in a time interval that overlaps (in time) with the slot comprising PHR 2004 (or the slot where PHR 2004 is transmitted).

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

[0209] In the example of FIG. 21 , the wireless device may transmit a PHR 2104. The wireless device may transmit PHR 2104 via cell 2010. PHR 2104 may be or comprise a virtual PHR as described above. For example, the wireless device may transmit PHR 2104 based on a reference PUSCH transmission via cell 2020 (e.g., there may be no (actual or real) PUSCH transmission scheduled via cell 2020 in a time interval that overlaps (in time) with the slot comprising PHR 2104). In the example of FIG. 21 , the wireless device may transmit PHR 2104 via or in a slot 2110. A slot 2120 may overlap (in time) with slot 2110. A slot 2130 may overlap (in time) with slot 2110. Slot 2110 may be of, for, associated with, or configured for cell 2010. Slot 2120 and slot 2130 may be of, for, associated with, or configured for cell 2020. There may be no (actual or real) PUSCH transmission scheduled for the wireless device via cell 2020 in slot 2120 and / or slot 2130.

[0210] In an example, the wireless device may receive control command 1902 indicating at least two TCI states (e.g., TCI state 1904 and TCI state 1906) for UL transmissions via non-SBFD and SBFD symbols, respectively. The wireless device may receive control command 1902 for cell 2020. For example, TCI state 1904 and TCI state 1906 may be of, for, associated with, or configured for cell 2020.

[0211] In the implementation of existing technologies, the wireless device may determine the PHR 2104 based on a first TCI state (i.e., TCI state 1904) of the at least two TCI states. The implementation of the existing technologies may be suitable for when the at least two TCI states are associated with, e.g., twoDocket No.: 24-1222PCT transmission and reception points (TRPs). However, in cases where the at least two TCI states are associated with two different symbol types (e.g., SBFD and non-SBFD), using the first TCI state (i.e., TCI state 1904) for determining PHR 2104 may not always be suitable. For example, TCI state 1904 may be for non-SBFD. Based on the wireless device determining PHR 2104 using TCI state 1904, the base station may not know a PH level associated with non-SBFD symbols but not know the PH value or level associated with UL transmissions via SBFD symbols. PHR may enable support for power-aware packet scheduling. Using an inaccurate PH value or level, or not using a PH value or level for packet scheduling may result in the base station scheduling UL transmissions that cause interference (e.g., due to indicating the wireless device to use a higher-than-required transmission power) and / or failed transmissions or receptions (e.g., due to indicating the wireless device to use a lower-than-required transmission power).

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

[0213] In an example embodiment, a wireless device receives, from a base station, and for uplink transmissions via a first cell, a downlink signal. The downlink signal indicates: a first power control set for non-SBFD symbols; and a second power control set for SBFD symbols. The wireless device transmits, via a transmission occasion and a second cell, a PHR comprising a PH level that is computed using a power control set, among the first power control set and the second control set, wherein the power control set is determined based on the transmission occasion.

[0214] Example embodiments of the present disclosure solve the problems identified above. Using example embodiments of the present disclosure, the wireless device may report accurate PH level(s). This may reduce interference and / or failed transmissions or receptions due to inaccurate packet scheduling.

[0215] In the example of FIG. 21 , the wireless device may receive a control command (e.g., control command 1902 or control command 1922) or a downlink signal. The control command may be an RRC message (e.g., RRC setup or RRC reconfiguration message). The control command may be, for example, a MAC CE. The control command may be, for example, a DCI.

[0216] The control command may indicate a power control set 2106 and a power control set 2108. The control command may indicate power control set 2106 and power control set 2108 for uplink transmissions via cell 2020.

[0217] In an example, power control set 2106 (e.g., pOAIphaSetforPUSCH) may be for PUSCH transmissions via cell 2020. In an example, power control set 2108 (e.g., pOAIphaSetforPUSCH) may be for PUSCH transmissions via cell 2020.

[0218] In an example, power control set 2106 may be for non-SBFD mode. For example, the wireless device may use power control set 2106 to determine transmission power of UL transmissions via non- SBFD symbol(s) of or via cell 2020.Docket No.: 24-1222PCT

[0219] In an example, power control set 2108 may be for SBFD mode. For example, the wireless device may use power control set 2108 to determine transmission power of UL transmissions via SBFD symbol(s) of or via cell 2020.

[0220] In an example, power control sets 1908 may comprise or indicate power control set 2106. For example, the control command may indicate power control set 2106 based on or by indicating TCI state 1904. In an example, power control sets 1912 may comprise or indicate power control set 2108. For example, the control command may comprise or indicate power control set 2108 based on or by indicating TCI state 1906.

[0221] In another example, power control sets 1928 may comprise or indicate power control set 2106 and power control sets 1932 may comprise or indicate power control set 2108. In this example, the control command may indicate power control set 2106 and power control set 2108 based on or by indicating TCI state 1924.

[0222] In the example of FIG. 21 , the wireless device may trigger (or determine to trigger) a PHR, e.g., at TO. TO may be same as TO in the examples of FIG. 20A and / or FIG. 20B. The wireless device may trigger the PHR as described in the examples of FIG. 20A and / or FIG. 20B.

[0223] The wireless device may transmit PHR 2104. The wireless device may transmit PHR 2104 via cell 2010. The wireless device may transmit PHR 2104 via (e.g., in, on, for, during, of, configured for, associated with, and / or the like) a transmission occasion. The transmission occasion may be, for example, a PUSCH transmission occasion. In an example, the wireless device may transmit PHR 2104 via PUSCH. PHR 2104 may be the same as or comprise, for example, PHR 2002 and / or PHR 2004.

[0224] As shown in FIG. 21 , slot 2110 may comprise the transmission occasion. For example, slot 2110 may comprise PHR 2104. In an example, slot 2110 may be of, for, associated with, or configured for cell 2010.

[0225] PHR 2104 may comprise or indicate a PH level. In some embodiments, "PH level” and "PH value” may be used interchangeably. PHR comprising or indicating a PH level may be the same as or be referred to the PHR comprising a field indicating the PH level. PHR may, for example, indicate the PH level. In some embodiments, “PH level” and “PHR” may be used interchangeably. It is to be understood that “PHR” comprises or indicates “PH level.”

[0226] PHR 2104 may be, for example, a virtual PHR. For example, the wireless device may determine the PH level based on a reference PUSCH transmission (of, for, associated with, or configured for cell 2020).

[0227] In an example, slot 2120 may be of, for, associated with, or configured for cell 2020. Slot 2130 may be of, for, associated with, or configured for cell 2020 Slot 2110 may be of, for, associated with, or configured for cell 2010.Docket No.: 24-1222PCT

[0228] Slot 2120 may overlap (in time) with slot 2110. Slot 2130 may overlap (in time) with slot 2110. As shown in FIG. 21 , slot 2120 may be earlier in time than slot 2130. For example, slot 2120 may be an earliest (or first, in time) slot that overlaps (in time) with slot 2110. Slot 2130 may be a latest or last slot that overlaps (in time) with slot 2110.

[0229] In an example, the wireless device may not be scheduled (e.g . , by the base station) with any UL transmissions (e.g., PUSCH transmissions), e.g., via cell 2020, in slot 2120 and / or slot 2130. The wireless device may determine a PH level for PHR 2104 (e.g., PH level of, for, associated with, configured for, comprised in, or indicated by PHR 2104) based on a reference PUSCH transmission in response to the wireless device not being scheduled with any UL transmissions (e.g., PUSCH transmissions), via cell 2020, in slot 2120 and / or slot 2130.

[0230] In an example, the reference PUSCH transmission (for determining the PH level for PHR 2104) may be in (e.g., of, for, associated with, or configured for) slot 2120 as shown in FIG. 21.

[0231] In an example, the wireless device may determine whether to use power control set 2106 or power control set 2108 to determine the PH level based on the transmission occasion.

[0232] In an example, determining the PH level may be referred to as computing, calculating, estimating, measuring, or inferring the PH level (or PHR, e.g., PHR 2104, which comprises or indicates the PH level).

[0233] In an example, the earliest (or first, in time) symbol of the transmission occasion may be (or comprise) a non-SBFD symbol (e.g., UL symbol or flexible symbol). The wireless device may use power control set 2106 to determine the PH level based on the earliest (or first, in time) symbol of the transmission occasion being (or comprising) a non-SBFD symbol.

[0234] In an example, the earliest (or first, in time) symbol of the transmission occasion may be (or comprise) an SBFD symbol. The wireless device may use power control set 2108 to determine the PH level based on the earliest (or first, in time) symbol of the transmission occasion being (or comprising) an SBFD symbol.

[0235] In an example, the latest (or last, in time) symbol of the transmission occasion may be (or comprise) a non-SBFD symbol (e.g., UL symbol or flexible symbol). The wireless device may use power control set 2106 to determine the PH level based on the latest (or last, in time) symbol of the transmission occasion being (or comprising) a non-SBFD symbol.

[0236] In an example, the latest (or last, in time) symbol of the transmission occasion may be (or comprise) an SBFD symbol. The wireless device may use power control set 2108 to determine the PH level based on the latest (or last, in time) symbol of the transmission occasion being (or comprising) an SBFD symbol.

[0237] In an example, the transmission occasion may comprise one or more non-SBFD symbols (or only non-SBFD symbols, e.g., may not comprise any SBFD symbols). The wireless device may use powerDocket No.: 24-1222PCT control set 2106 to determine the PH level based on the transmission occasion comprising one or more non-SBFD symbols (or only non-SBFD symbols, e.g., not comprising any SBFD symbols).

[0238] In an example, the transmission occasion may comprise one or more SBFD symbols (or only SBFD symbols, e.g., not comprise any non-SBFD symbols). The wireless device may use power control set 2108 to determine the PH level based on the transmission occasion comprising one or more SBFD symbols (or only SBFD symbols, e.g., not comprising any non-SBFD symbols).

[0239] In an example, the wireless device may determine whether to use power control set 2106 or power control set 2108 to determine the PH level based on slot 2110.

[0240] In an example, the earliest (or first, in time) symbol of slot 2110 may be (or comprise) a non-SBFD symbol. The wireless device may use power control set 2106 to determine the PH level based on the earliest (or first, in time) symbol of slot 2110 being (or comprising) a non-SBFD symbol.

[0241] In an example, the earliest (or first, in time) symbol of slot 2110 may be (or comprise) an SBFD symbol. The wireless device may use power control set 2108 to determine the PH level based on the earliest (or first, in time) symbol of slot 2110 being (or comprising) an SBFD symbol.

[0242] In an example, the latest (or last, in time) symbol of slot 2110 may be (or comprise) a non-SBFD symbol. The wireless device may use power control set 2106 to determine the PH level based on the latest (or last, in time) symbol of slot 2110 being (or comprising) a non-SBFD symbol.

[0243] In an example, the latest (or last, in time) symbol of slot 2110 may be (or comprise) an SBFD symbol. The wireless device may use power control set 2108 to determine the PH level based on the latest (or last, in time) symbol of slot 2110 being (or comprising) an SBFD symbol.

[0244] In an example, slot 2110 may comprise one or more non-SBFD symbols (or only non-SBFD symbols, e.g., not comprise any SBFD symbols). The wireless device may use power control set 2106 to determine the PH level based on slot 2110 comprising one or more non-SBFD symbols (or only non-SBFD symbols, e.g., not comprising any SBFD symbols).

[0245] In an example, slot 2110 may comprise one or more SBFD symbols (or only SBFD symbols, e.g., not comprise any non-SBFD symbols). The wireless device may use power control set 2108 to determine the PH level based on slot 2110 comprising one or more SBFD symbols (or only SBFD symbols, e.g., not comprising any non-SBFD symbols).

[0246] In an example, the wireless device may determine whether to use power control set 2106 or power control set 2108 to determine the PH level based on slot 2120.

[0247] In an example, the earliest (or first, in time) symbol of slot 2120 may be (or comprise) a non-SBFD symbol. The wireless device may use power control set 2106 to determine the PH level based on the earliest (or first, in time) symbol of slot 2120 being (or comprising) a non-SBFD symbol.Docket No.: 24-1222PCT

[0248] In an example, the earliest (or first, in time) symbol of slot 2120 may be (or comprise) an SBFD symbol. The wireless device may use power control set 2108 to determine the PH level based on the earliest (or first, in time) symbol of slot 2120 being (or comprising) an SBFD symbol.

[0249] In an example, the latest (or last, in time) symbol of slot 2120 may be (or comprise) a non-SBFD symbol. The wireless device may use power control set 2106 to determine the PH level based on the latest (or last, in time) symbol of slot 2120 being (or comprising) a non-SBFD symbol.

[0250] In an example, the latest (or last, in time) symbol of slot 2120 may be (or comprise) an SBFD symbol. The wireless device may use power control set 2108 to determine the PH level based on the latest (or last, in time) symbol of slot 2120 being (or comprising) an SBFD symbol.

[0251] In an example, slot 2120 may comprise one or more non-SBFD symbols (or only non-SBFD symbols, e.g., not comprise any SBFD symbols). The wireless device may use power control set 2106 to determine the PH level based on slot 2120 comprising one or more non-SBFD symbols (or only non-SBFD symbols, e.g., not comprising any SBFD symbols).

[0252] In an example, slot 2120 may comprise one or more SBFD symbols (or only SBFD symbols, e.g., not comprise any non-SBFD symbols) The wireless device may use power control set 2108 to determine the PH level based on slot 2120 comprising one or more SBFD symbols (or only SBFD symbols, e.g., not comprising any non-SBFD symbols).

[0253] In an example, the wireless device may determine whether to use power control set 2106 or power control set 2108 to determine the PH level based on slot 2130.

[0254] In an example, the earliest (or first, in time) symbol of slot 2130 may be (or comprise) a non-SBFD symbol. The wireless device may use power control set 2106 to determine the PH level based on the earliest (or first, in time) symbol of slot 2130 being (or comprising) a non-SBFD symbol.

[0255] In an example, the earliest (or first, in time) symbol of slot 2130 may be (or comprise) an SBFD symbol. The wireless device may use power control set 2108 to determine the PH level based on the earliest (or first, in time) symbol of slot 2130 being (or comprising) an SBFD symbol.

[0256] In an example, the latest (or last, in time) symbol of slot 2130 may be (or comprise) a non-SBFD symbol. The wireless device may use power control set 2106 to determine the PH level based on the latest (or last, in time) symbol of slot 2130 being (or comprising) a non-SBFD symbol.

[0257] In an example, the latest (or last, in time) symbol of slot 2130 may be (or comprise) an SBFD symbol. The wireless device may use power control set 2108 to determine the PH level based on the latest (or last, in time) symbol of slot 2130 being (or comprising) an SBFD symbol.

[0258] In an example, slot 2130 may comprise one or more non-SBFD symbols (or only non-SBFD symbols, e.g., not comprise any SBFD symbols). The wireless device may use power control set 2106 toDocket No.: 24-1222PCT determine the PH level based on slot 2130 comprising one or more non-SBFD symbols (or only non-SBFD symbols, e.g., not comprising any SBFD symbols).

[0259] In an example, slot 2130 may comprise one or more SBFD symbols (or only SBFD symbols, e.g., not comprise any non-SBFD symbols). The wireless device may use power control set 2108 to determine the PH level based on slot 2130 comprising one or more SBFD symbols (or only SBFD symbols, e.g., not comprising any non-SBFD symbols).

[0260] In an example, the wireless device may determine whether to use power control set 2106 or power control set 2108 to determine the PH level based on the reference PUSCH transmission.

[0261] In an example, the earliest (or first, in time) symbol of the reference PUSCH transmission may be (or comprise) a non-SBFD symbol. The wireless device may use power control set 2106 to determine the PH level based on the earliest (or first, in time) symbol of the reference PUSCH transmission being (or comprising) a non-SBFD symbol.

[0262] In an example, the earliest (or first, in time) symbol of the reference PUSCH transmission may be (or comprise) an SBFD symbol. The wireless device may use power control set 2108 to determine the PH level based on the earliest (or first, in time) symbol of the reference PUSCH transmission being (or comprising) an SBFD symbol.

[0263] In an example, the latest (or last, in time) symbol of the reference PUSCH transmission may be (or comprise) a non-SBFD symbol. The wireless device may use power control set 2106 to determine the PH level based on the latest (or last, in time) symbol of the reference PUSCH transmission being (or comprising) a non-SBFD symbol.

[0264] In an example, the latest (or last, in time) symbol of the reference PUSCH transmission may be (or comprise) an SBFD symbol. The wireless device may use power control set 2108 to determine the PH level based on the latest (or last, in time) symbol of the reference PUSCH transmission being (or comprising) an SBFD symbol.

[0265] In an example, the reference PUSCH transmission may comprise one or more non-SBFD symbols (or only non-SBFD symbols, e.g., not comprise any SBFD symbols). The wireless device may use power control set 2106 to determine the PH level based on the reference PUSCH transmission comprising one or more non-SBFD symbols (or only non-SBFD symbols, e.g., not comprising any SBFD symbols).

[0266] In an example, the reference PUSCH transmission may comprise one or more SBFD symbols (or only SBFD symbols, e.g., not comprise any non-SBFD symbols). The wireless device may use power control set 2108 to determine the PH level based on the reference PUSCH transmission comprising one or more SBFD symbols (or only SBFD symbols, e.g., not comprising any non-SBFD symbols).

[0267] In an example, the wireless device may determine one of power control set 2106 and power control set 2108 to determine the PH level (comprised in or indicated by PHR 2104). For example, the wirelessDocket No.: 24-1222PCT device may determine, one of power control set 2106 and power control set 2108 to determine the PH level, at random (e.g ., by wireless device or UE implementation).

[0268] The wireless device may indicate (e.g., via or in PHR 2104) which one of power control set 2106 and power control set 2108 that the wireless device used for determining the PH level. In an example, PHR 2104 may comprise a field indicating which one of power control set 2106 and power control set 2108 was used by the wireless device to determine the PH level. For example, the field may be a “duplex indicator” field. The field may be, for example, a “power control set indicator" field. The field may be, for example, a “DI" or “PI” field. The field may be, for example, a “pOAIphaSet Indicator” field. The field being set to a first value (by the wireless device), e.g., 0 or 1 , may indicate that the wireless device used (or uses) power control set 2106 to determine the PH level (that is indicated by PHR 2104). The field being set to a second value (by the wireless device), e.g., 1 or 0, may indicate that the wireless device used (or uses) power control set 2108 to determine the PH level (that is indicated by PHR 2104).

[0269] The field being set to the first value (by the wireless device), e.g., 0 or 1 , may indicate that the wireless device used (or uses) non-SBFD symbols (or power control set associated with non-SBFD symbols, e.g., power control set 2106) to determine the PH level. The field being set to a second value (by the wireless device), e.g., 1 or 0, may indicate that the wireless device used (or uses) SBFD symbols (or power control set associated with SBFD symbols, e.g., power control set 2108) to determine the PH level.

[0270] In an example, the wireless device may receive a second control command (e.g., RRC message, MAC CE, DCI, control command 1902, control command 1922, message(s) 1706, configuration parameters 1708, message(s) 1710) that indicates which one of power control set 2106 and power control set 2108 to use for determining the PH level. In an example, the second control command may be the same as the control command.

[0271] In an example, the second control command may indicate power control set 2106 to use for determining the PH level. The wireless device may use power control set 2106 to determine the PH level based on or in response to the second control command indicating power control set 2106 to use for determining the PH level.

[0272] In an example, the second control command may indicate power control set 2108 to use for determining the PH level. The wireless device may use power control set 2108 to determine the PH level based on or in response to the second control command indicating power control set 2108 to use for determining the PH level.

[0273] In an example, the wireless device may use power control set 2106 to determine a first PH level. The wireless device may use power control set 2108 to determine a second PH level. The wireless device may determine (e.g., select) one of the first PH level and the second PH level as the PH level (e g., indicated by or comprised in PHR 2104).Docket No.: 24-1222PCT

[0274] In an example, the first PH level may be higher (e.g., greater, larger, bigger, above, more) than or equal to the second PH level. The wireless device may determine the first PH level as the PH level based on the first PH level being higher (e.g., greater, larger, above, more) than or equal to the second PH level.

[0275] In an example, the first PH level may be lower (e.g., less, smaller, below) than or equal to the second PH level. The wireless device may determine the first PH level as the PH level based on the first PH level being lower (e.g., less, smaller, below) than or equal to the second PH level.

[0276] In an example, the wireless device may transmit a first PHR before transmitting PHR 2104. The wireless device may use a power control set, to determine the PH level, that is different from the power control set used to determine a PH level for the first PHR.

[0277] For example, the wireless device may use power control set 2106 to determine the first PHR (e.g., a first PH level). The wireless device may use power control set 2108 to determine the PH level based on or in response to using power control set 2108 to determine the first PHR (e.g., the first PH level).

[0278] In an example, the wireless device may use power control set 2108 to determine the first PHR (e.g., a first PH level). The wireless device may use power control set 2106 to determine the PH level based on or in response to using power control set 2106 to determine the first PHR (e.g., the first PH level).

[0279] In an example, cell 2010 (and / or cell 2020) may not be configured with SBFD operation. For example, the wireless device may not receive the one or more configuration parameters for SBFD mode of, for, associated with, or configured for cell 2010 (and / or cell 2020). For example, message(s) 1706 and / or configuration parameters 1708 may not comprise or indicate the one or more configuration parameters for SBFD mode of, for, associated with, or configured for cell 2010 (and / or cell 2020). The wireless device may use power control set 2106 to determine the PH level based on or in response to not receiving the one or more configuration parameters for SBFD mode for cell 2010 (and / or cell 2020) (or message(s) 1706 and / or configuration parameters 1708 not comprising or indicating the one or more configuration parameters for SBFD mode of, for, associated with, or configured for cell 2010 (and / or cell 2020)).

[0280] In an example, PHR 2104 may comprise a single PH level (e.g., the PH level). The wireless device may determine to transmit a single PH level (e.g., the PH level as described above) via PHR 2104 based on cell 2020 (and / or cell 2010) being configured with a first configuration type (e.g., configuration parameters 1708 may indicate cell 2020 (and / or cell 2010) being configured with the first configuration type). The first configuration type may be referred to as Configuration 1 . In Configuration 1 , UL transmissions and / or DL receptions may be restricted to SBFD symbols only or non-SBFD symbols only. In Configuration 1 , a valid symbol type may be determined by the wireless device as following: For semi- statically configured UL transmissions and / or DL receptions without activation DCI, the valid symbol type may explicitly be configured by RRC (e.g., message(s) 1706 and / or configuration parameters 1708); For dynamically scheduled UL transmissions and / or DL receptions, the valid symbol type may be determinedDocket No.: 24-1222PCT by the wireless device based on a symbol type (e.g., SBFD or non-SBFD) of a first (e.g., earliest or first in time) UL transmission and / or DL reception; and / or For SP-CSI on PUCCH or PUSCH, type 2 CG PUSCH, SPS PDSCH and semi-persistent SRS: The valid symbol type for SP-CSI on PUCCH or PUSCH may be explicitly configured in CSI-ReportConfig\ The valid symbol type for type 2 CG PUSCH may be explicitly configured in ConfiguredGrantConfig The valid symbol type for SPS PDSCH may be explicitly configured in SPS-Config] The valid symbol type for semi-persistent SRS may be explicitly configured in SRS-Config, SRS-ResourceSet, and / or SRS-Resource' The valid symbol type for SP-CSI on PUCCH or PUSCH may be determined by the wireless device based on a symbol type of the first (e.g., first in time or earliest) PUSCH / PUCCH after activation; The valid symbol type for type 2 CG PUSCH may be determined by the wireless device based on a symbol type of the first (e g., first in time or earliest) CG PUSCH associated with activation DCI; The valid symbol type for SPS PDSCH may be determined by the wireless device based on a symbol type of the first SPS PDSCH associated with activation DCI; and / or The valid symbol type for semi-persistent SRS may be determined by the wireless device based on a symbol type of the first SRS after activation.

[0281] In another example, the wireless device may determine to transmit the single PH level via PHR 2104 based on cell 2020 (and / or cell 2010) being configured with a second configuration type (e.g., configuration parameters 1708 may indicate cell 2020 (and / or cell 2010) being configured with the second configuration type). The second configuration type may be referred to as Configuration 2. In Configuration 2, UL transmissions and / or DL receptions may be in both SBFD symbols and non-SBFD symbols. Message(s) 1706 and / or configuration parameters 1708 may indicate Configuration 2 based on the wireless device transmitting a capability message indicating support for Configuration 2.

[0282] In an example, the wireless device may determine to transmit the single PH level via PHR 2104 based on or in response to message(s) 1706 and / or configuration parameters 1708 not comprising or indicating a parameter (e.g., twoPHRmode) that indicates if a PHR may be reported as two PHRs (each PHR associated with a SRS resource set or a TCI state), or in response to message(s) 1706 and / or configuration parameters 1708 comprising or indicating a parameter (e.g., twoPHRmode) that is set to "disabled."

[0283] In an example, PHR 2104 may comprise a plurality of PH levels. The plurality of PH levels may comprise a first PH level and a second PH level. The wireless device may use power control set 2106 to determine the first PH level. The wireless device may use power control set 2108 to determine the second PH level.

[0284] The wireless device may transmit PHR 2104 comprise the plurality of PH level, for example, based on cell 2020 being configured with the first configuration type. The wireless device may transmit PHR 2104Docket No.: 24-1222PCT comprise the plurality of PH level, for example, based on cell 2020 being configured with the second configuration type.

[0285] The wireless device may transmit PHR 2104 comprise the plurality of PH level, for example, based on message(s) 1706 and / or configuration parameters 1708 comprising or indicating a parameter (e.g., twoPHRmode) that is set to “enabled."

[0286] In an example, the wireless device may determine the PH level (e.g., transmit PHR 2104 comprising or indicating the PH level or transmit the single PH level in PHR 2104) based on configuration parameters 1708 and / or message(s) 1706 comprising or indicating the one or more configuration parameters for SBFD mode.

[0287] In some embodiments, determining a PHR and determining a PH level (for the PHR) may be used interchangeably. The PHR may comprise or indicate the PH level.

[0288] In an example, power control sets 1908 may be or comprise a power control set 2106. For example, using power control set 2106 to determine a PH level may be the same as, be referred to as, or comprise using TCI state 1904 (associated with power control sets 1908) to determine the PH level.

[0289] In an example, power control sets 1912 may be or comprise power control set 2108. For example, using power control set 2108 to determine a PH level may be the same as, be referred to as, or comprise using TCI state 1906 (associated with power control sets 1912) to determine the PH level.

[0290] In an example, control command 1902 may be of, for, associated with, or configured for cell 2020. In an example, control command 1922 may be of, for, associated with, or configured for cell 2020.

[0291] In an example, control command 1902 may be of, for, associated with, or configured for cell 2010. In an example, control command 1922 may be of, for, associated with, or configured for cell 2010.

[0292] In an example, control command 1902 indicating TCI state 1904 and TCI state 1904 may be equivalent to or the same as control command 1902 indicating power control sets 1908 and power control sets 1912 (or power control set 2106 and power control set 2108).

[0293] In an example, power control sets 1928 may be or comprise power control set 2106. In an example, power control sets 1932 may be or comprise power control set 2108. For example, using power control set 2106 and / or power control set 2108 to determine the PH level may be the same as, be referred to as, or comprise using TCI state 1924 to determine the PH level.

[0294] In an example, control command 1922 indicating TCI state 1924 may be the same as or equivalent to control command 1922 indicating power control sets 1928 and power control sets 1932 (or power control set 2106 and power control set 2108).

[0295] Using a power control set (e.g., power control set 2106, power control set 2108) to determine a PH level may comprise (e.g., be the same as or be referred to as) determining the PH level based on or using power control parameters indicated by or comprised in the power control set. For example, the powerDocket No.: 24-1222PCT control set may comprise a received signal power (or received signal level or power level), a resource index indicating a pathloss RS (e.g., SSB or CSI-RS), a pathloss factor, and / or a closed loop index. The wireless device may determine the PH level based on a first equation. The first equation may comprise the PH level. The first equation may comprise the power control set. The first equation may comprise the power control parameters. The first equation may comprise the received signal power. The first equation may comprise the pathloss factor. The first equation may comprise the closed loop index. The first equation may be, for example, the PH level = PCmax - (the received power level + the pathloss factor * pathloss + the closed loop index), wherein pathloss is determined by the wireless device by measuring the pathloss RS, and PCmax is the maximum output (or transmit or transmission) power of the wireless device for: the BWP, the cell (e g., cell 2010, cell 2020), and / or the transmission occasion.

[0296] In an example, the wireless device may transmit a PHR (e.g., PHR 2104, PHR 2002, PHR 2004) via a BWP of the cell (e.g., cell 2010, cell 2020). The BWP may be, for example, a UL BWP. The BWP may be, for example, an active UL BWP. The BWP may be, for example, any of the BWPs described above.

[0297] In some embodiments, determining a PH level may be referred to as computing, calculating, measuring, and / or estimating the PH level.

[0298] In some embodiments, cell 2010 may be an activated serving cell.

[0299] In some embodiments, cell 2020 may be an activated serving cell.

[0300] In some embodiments, cell 2010 and / or cell 2020 may be the cell described above (e.g., in connection with FIG. 17A).

[0301] In some embodiments, the wireless device may determine whether a PHR (or a PH level of the PHR), e.g., PHR 2104, PHR 2002, PHR 2004, is based on an actual PUSCH transmission or a reference PUSCH transmission based on a higher layer signaling (e.g., configuration parameters 1708) of configured grant and periodic / semi-persistent sounding reference signal transmissions and downlink control information the wireless device received until and including the PDCCH monitoring occasion where the wireless device detects a first DCI format scheduling an initial transmission of a transport block since a power headroom report was triggered if the power headroom report is reported on a PUSCH triggered by the first DCI format. Otherwise, the wireless device may determine whether a power headroom report is based on an actual PUSCH transmission or a reference PUSCH transmission based on the higher layer signaling of configured grant and periodic / semi-persistent sounding reference signal transmissions and downlink control information the wireless device received until the first uplink symbol of a configured PUSCH transmission minus T'proc, 2= Tproc, 2 where Tproc,2 is determined assuming d2, 1 = 1 , d2,2=0, and with piDL corresponding to the subcarrier spacing of the active downlink BWP of the scheduling cell for a configured grant if the power headroom report is reported on the PUSCH using the configured grant.Docket No.: 24-1222PCT

[0302] In some embodiments, a TCI state comprising (or being associated with) a power control set may be the same as or be referred to as the TCI state indicating the power control set.

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

[0304] In the example of FIG. 22, a wireless device (e.g., wireless device 1700) receives a downlink signal (e.g., control command 1902, control command 1922, message(s) 1706, configuration parameters 1708). The downlink signal may be for UL transmissions via a first cell (e.g., cell 2020).

[0305] The downlink signal (e.g., control command 1902 and / or control command 1922) may indicate a first power control set (e.g., power control set 2106) for non-SBFD symbols. The downlink signal may indicate a second power control set (e.g., power control set 2108) for SBFD symbols.

[0306] The wireless device may determine a PH level using one of the first power control set and the second power control set. The wireless device may transmit, in or on a transmission occasion and via a second cell (e.g., cell 2010), a PHR (e.g., PHR 2104, PHR 2002, PHR 2004) comprising or indicating the PH level.

[0307] In an example, the wireless device may use the first power control set to determine the PH level based on a first (in time) or a last symbol of the slot, that comprises the transmission occasion, being a non-SBFD symbol. In an example, the wireless device may use the second power control set to determine the PH level based on a first (in time) or a last symbol of the slot, that comprises the transmission occasion, being an SBFD symbol.

[0308] In an example, the wireless device may use the first power control set to determine the PH level based on a first (in time) or a last symbol of the transmission occasion being a non-SBFD symbol. In an example, the wireless device may use the second power control set to determine the PH level based on a first (in time) or a last symbol of the transmission occasion being an SBFD symbol.

[0309] In an example, the wireless device may use the first power control set to determine the PH level based on: a first (in time) or a last symbol of a slot (e.g., earliest slot), of the first cell, that overlaps (in time) with the transmission occasion being a non-SBFD symbol. In an example, the wireless device may use the second power control set to determine the PH level based on: a first (in time) or a last symbol of a slot (e g., earliest slot), of the first cell, that overlaps (in time) with the transmission occasion being an SBFD symbol.

[0310] In an example, the wireless device may use the first power control set to determine the PH level based on: a first (in time) or a last symbol of a slot (e.g., last or latest slot), of the first cell, that overlaps (in time) with the transmission occasion being a non-SBFD symbol. In an example, the wireless device may use the second power control set to determine the PH level based on: a first (in time) or a last symbol of aDocket No.: 24-1222PCT slot (e.g., last or latest slot), of the first cell, that overlaps (in time) with the transmission occasion being an SBFD symbol.

[0311] In an example, the wireless device may determine the PH level based on a reference PUSCH transmission. For example, the wireless device may use the first power control set to determine the PH level based on a first (in time) or last symbol of the reference PUSCH transmission being a non-SBFD symbol. In an example, the wireless device may use the second power control set to determine the PH level based on a first (in time) or last symbol of the reference PUSCH transmission being an SBFD symbol.

[0312] In an example, the wireless device may use the first power control set to determine the PH level based on the transmission occasion comprising one or more non-SBFD symbols (or only comprising non- SBFD symbols or not comprising any SBFD symbol). In an example, the wireless device may use the second power control set to determine the PH level based on the transmission occasion comprising one or more SBFD symbols (or only comprising SBFD symbols or not comprising any non-SBFD symbol).

[0313] In an example, the wireless device may use the first power control set to determine the PH level based on a slot comprising the transmission occasion comprising one or more non-SBFD symbols (or only comprising non-SBFD symbols or not comprising any SBFD symbol). In an example, the wireless device may use the second power control set to determine the PH level based on a slot comprising the transmission occasion comprising one or more SBFD symbols (or only comprising SBFD symbols or not comprising any non-SBFD symbol).

[0314] In an example, the wireless device may use the first power control set to determine the PH level based on a slot (e.g., earliest slot), of the first cell, that overlaps (in time) with the transmission occasion comprising one or more non-SBFD symbols (or only comprising non-SBFD symbols or not comprising any SBFD symbol). In an example, the wireless device may use the second power control set to determine the PH level based on a slot (e.g., earliest slot), of the first cell, that overlaps (in time) with the transmission occasion comprising one or more SBFD symbols (or only comprising SBFD symbols or not comprising any non-SBFD symbol).

[0315] In an example, the wireless device may use the first power control set to determine the PH level based on a slot (e.g., latest or last slot), of the first cell, that overlaps (in time) with the transmission occasion comprising one or more non-SBFD symbols (or only comprising non-SBFD symbols or not comprising any SBFD symbol). In an example, the wireless device may use the second power control set to determine the PH level based on a slot (e.g., latest or last slot), of the first cell, that overlaps (in time) with the transmission occasion comprising one or more SBFD symbols (or only comprising SBFD symbols or not comprising any non-SBFD symbol).

[0316] In an example, the wireless device may use the first power control set to determine the PH level based on the reference PUSCH transmission comprising one or more non-SBFD symbols (or onlyDocket No.: 24-1222PCT comprising non-SBFD symbols or not comprising any SBFD symbol). In an example, the wireless device may use the second power control set to determine the PH level based on the reference PUSCH transmission comprising one or more SBFD symbols (or only comprising SBFD symbols or not comprising any non-SBFD symbol).

[0317] Example embodiments may enable the wireless device to report an accurate PH level. This may allow the base station to schedule packets in a power-aware manner such that interference and / or failed transmissions (and thereby retransmissions) may be reduced.

[0318] If power control set 2106 and / or power control set 2108 are provided to wireless device (e.g by configuration parameters 1708), if the one or more configuration parameters are provided (e.g., comprised in configuration parameters 1708), if the wireless device is indicated TCI state 1904 and TCI state 1906, and / or if the wireless device is not provided with twoPHRmode, the wireless device may obtain or use a power control set, for determining the PH level, that is associated with a TCI state (e.g., TCI state 1904 or TCI state 1906) that is associated with the symbol type of the first symbol of the reference PUSCH transmission.

[0319] If power control set 2106 and / or power control set 2108 are provided to wireless device (e g., by configuration parameters 1708), and / or if the wireless device is indicated with one TCI state (e.g., TCI state 1924), the wireless device obtains or uses the power control set for determining the PH level, that is associated with the symbol type of the first symbol of the reference PUSCH transmission.

[0320] An example method comprising: receiving, by a wireless device and for uplink transmissions via a first cell (e.g., cell 2020), a downlink signal (e.g., control command 1902, control command 1922) indicating: a first power control set (e.g., power control set 2106, power control sets 1908, power control sets 1928) for non-sub-band full-duplex (SBFD) symbols (e.g., symbol 1812); and a second power control set (e.g., power control set 2108, power control sets 1912, power control sets 1932) for SBFD symbols (e.g , symbol 1808, symbol 1810); and transmitting, via a transmission occasion and a second cell (e.g., cell 2010), a power headroom report (e.g., PHR 2104, PHR 2002, PHR 2004) comprising a power headroom level that is computed using a power control set among the first power control set and the second power control set.

[0321] The above example method, wherein the power control set is determined based on a slot that comprises the transmission occasion.

[0322] One or more of the above example methods, wherein the power control set is the first power control set based on an earliest or last symbol of the slot being a non-SBFD symbol.

[0323] One or more of the above example methods, wherein the power control set is the second power control set based on an earliest or last symbol of the slot being an SBFD symbol.Docket No.: 24-1222PCT

[0324] One or more of the above example methods, wherein the power control set is determined based on a slot that overlaps in time with the transmission occasion.

[0325] One or more of the above example methods, wherein the slot is of the first cell.

[0326] One or more of the above example methods, wherein the power control set is the first power control set based on the slot not comprising any SBFD symbol.

[0327] One or more of the above example methods, wherein the power control is the second power control set based on the slot comprising an SBFD symbol.

[0328] One or more of the above example methods, wherein the power control set is the first power control set based on an earliest symbol of / in the slot being a non-SBFD symbol.

[0329] One or more of the above example methods, wherein the power control set is the second power control set based on an earliest symbol of / in the slot being an SBFD symbol.

[0330] One or more of the above example methods, wherein the power control set is determined at random from among the first power control set and the second power control set.

[0331] One or more of the above example methods, wherein the power headroom report indicates the power control set.

[0332] One or more of the above example methods, wherein the power headroom report comprises a field indicating whether the first power control set or the second power control set is used to determine the power headroom level.

[0333] One or more of the above example methods, further comprising receiving a second downlink signal.

[0334] One or more of the above example methods, wherein the second downlink signal is different from the downlink signal.

[0335] One or more of the above example methods, wherein the second downlink signal and the downlink signal are the same.

[0336] One or more of the above example methods, wherein the second downlink signal indicates the power control set from among the first power control set and the second power control set.

[0337] One or more of the above example methods, wherein the power control set is indicated by the second downlink signal.

[0338] One or more of the above example methods, wherein the power control set is the first power control set based on the second downlink signal indicating the first power control set.

[0339] One or more of the above example methods, wherein the power control set is the second power control set based on the second downlink signal indicating the second power control set.

[0340] One or more of the above example methods, wherein the power control set is the first power control set based on the transmission occasion comprising a non-SBFD symbol.Docket No.: 24-1222PCT

[0341] One or more of the above example methods, wherein the power control set is the first power control set based on the transmission occasion not comprising an SBFD symbol.

[0342] One or more of the above example methods, wherein the power control set is the second power control set based on the transmission occasion comprising an SBFD symbol.

[0343] One or more of the above example methods, wherein the power control set is the second power control set based on the transmission occasion not comprising a non-SBFD symbol.

[0344] One or more of the above example methods, wherein the power control set is determined based on a first or last symbol of the transmission occasion.

[0345] One or more of the above example methods, wherein the power control set is the first power control set based on the first or last symbol of the transmission occasion being an SBFD symbol.

[0346] One or more of the above example methods, wherein the power control set is the second power control set based on the first or last symbol of the transmission occasion being a non-SBFD symbol.

[0347] One or more of the above example methods, wherein the power control set is determined based on a second power headroom report.

[0348] One or more of the above example methods, wherein the second power headroom report is transmitted before the power headroom report.

[0349] One or more of the above example methods, wherein the power control set is the first power control set based on the second power headroom report being determined using the second power control set.

[0350] One or more of the above example methods, wherein the power control set is the second power control set based on the second power headroom report being determined using the first power control set.

[0351] One or more of the above example methods, wherein the power headroom level is determined based on a first power headroom level and a second power headroom level.

[0352] One or more of the above example methods, wherein the first power headroom level is determined based on the first power control set.

[0353] One or more of the above example methods, wherein the second power headroom level is determined based on the second power control set.

[0354] One or more of the above example methods, wherein the power headroom level is the first power headroom level based on the first power headroom level being greater than the second power headroom level.

[0355] One or more of the above example methods, wherein the power headroom level is the first power headroom level based on the first power headroom level being less than or equal to the second power headroom level.Docket No.: 24-1222PCT

[0356] One or more of the above example methods, wherein the power control set is the first power control set based on the second cell not being configured with SBFD mode.

[0357] One or more of the above example methods, wherein: the first power control set is for a first TCI state (e.g., TCI state 1904); and the second power control set is for a second TCI state (e.g ., TCI state 1906).

[0358] One or more of the above example methods, wherein: the first power control set is for a first TCI state (e.g., TCI state 1924); and the second power control set is for a first TCI state (e.g., TCI state 1924).

[0359] One or more of the above example methods, wherein transmitting the power headroom report is further based on the downlink signal not indicating twoPHRmode or not requesting two power headroom reports, each of which is associated with SBFD or non-SBFD mode.

[0360] One or more of the above example methods, comprising: transmitting, by a base station and for uplink transmissions via a first cell, the downlink signal indicating: the first power control set for non-SBFD symbols; and the second power control set for SBFD symbols; and receiving, via the transmission occasion and the second cell, the PHR comprising the power headroom level that is computer using a power control set among the first power control set and the second power control set.

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

[0362] In the example of FIG. 23, the wireless device receives a control command 2302. Control command 2302 may be the same as (or comprise) message(s) 1706. Control command 2302 may be the same as (or comprise) control command 1902. Control command 2302 may be the same as (or comprise) control command 1922.

[0363] Control command 2302 may comprise or indicate a parameter or a flag 2304. Flag 2304 may indicate or be set to 0 or 1 (or any other Boolean variant, e.g., true or false, yes or no, enabled or disabled, SBFD or non-SBFD, etc.).

[0364] The wireless device may receive a control command 2306. Control command 2306 may be, for example, the same as control command 2302. In another example, Control command 2306 may be different from control command 2302. Control command 2306 may be the same as (or comprise) message(s) 1706. Control command 2306 may be the same as (or comprise) configuration parameters 1708. Control command 2306 may be the same as (or comprise) control command 1902. Control command 2306 may be the same as (or comprise) control command 1922.

[0365] Control command 2306 may comprise or indicate a TCI state 2312 and a TCI state 2314. In an example, TCI state 2312 may be the same as, for example, TCI state 1904. In an example, TCI state 2314 may be the same as, for example, TCI state 1906.Docket No.: 24-1222PCT

[0366] In an example, the wireless device may determine which of TCI state 2312 and TCI state 2314 is for non-SBFD symbols and / or which of TCI state 2312 and TCI state 2314 is for SBFD symbols based on flag 2304 (or a value of flag 2304).

[0367] In an example, flag 2304 may be set to a first value (e.g., 0 (as shown in FIG. 23), or 1 , true, false, enabled, disabled, etc.). Based on flag 2304 being set to the first value, the wireless device may determine that: TCI state 2312 is for non-SBFD symbols and / or TCI state 2314 is for SBFD symbols.

[0368] In an example, flag 2304 may be set to a second value (e.g., 1 as shown in FIG. 23, or 0, true, false, enabled, disabled, etc.). Based on flag 2304 being set to the second value, the wireless device may determine that: TCI state 2312 is for SBFD symbols and / or TCI state 2314 is for non-SBFD symbols.

[0369] The wireless device may transmit a UL signal 2308. In an example, UL signal 2308 may be (or comprise) PHR 2104. UL signal 2308 may be (or comprise), for example, PHR 2002. UL signal 2308 may be (or comprise), for example, PHR 2004. UL signal 2308 may be (or comprise), for example, UL signal 1934. UL signal 2308 may be (or comprise), for example, UL signal 1914. UL signal 2308 may be (or comprise), for example, message(s) 1712.

[0370] The wireless device may transmit UL signal 2308, for example, via cell 2010. The wireless device may transmit UL signal 2308, for example, via cell 2020.

[0371] The wireless device may receive control command 2302 and / or control command 2306, for example, via cell 2010 and / or cell 2020.

[0372] Control command 2302 (and / or flag 2304) may be for cell 2010 and / or cell 2020. Control command 2306 (and / or TCI state 2312 and TCI state 2314) may be for cell 2010 and / or cell 2020.

[0373] The wireless device may transmit UL signal 2308 via a transmission occasion.

[0374] In an example, the transmission occasion may comprise one or more SBFD symbols (or a first, in time, symbol of the transmission occasion may be an SBFD symbol). The wireless device may use a TCI state for SBFD symbols (e.g., TCI state 2314 in response to flag 2304 being set to the first value and / or TCI state 2312 in response to flag 2304 being set to the second value) to transmit UL signal 2308, for example, based on the transmission comprising one or more SBFD symbols (or a first, in time, symbol of the transmission occasion being an SBFD symbol).

[0375] In an example, the transmission occasion may comprise one or more non-SBFD symbols (or a first, in time, symbol of the transmission occasion may be a non-SBFD symbol). The wireless device may use a TCI state for non-SBFD symbols (e.g., TCI state 2314 in response to flag 2304 being set to the second value and / or TCI state 2312 in response to flag 2304 being set to the first value) to transmit UL signal 2308, for example, based on the transmission occasion comprising one or more SBFD symbols (or a first, in time, symbol of the transmission occasion being a non-SBFD symbol).Docket No.: 24-1222PCT

[0376] In some embodiments, a transmission occasion comprising one or more SBFD symbols may, for example, be the same as the transmission occasion not comprising one or more non-SBFD symbols.

[0377] In some embodiments, a transmission occasion comprising one or more non-SBFD symbols may, for example, be the same as the transmission occasion not comprising one or more SBFD symbols.

[0378] The wireless device may transmit UL signal 2308 via cell 2010. The wireless device may transmit UL signal 2308 via cell 2020.

[0379] A TCI state (e.g., TCI state 2312, TCI state 2314, TCI state 1904, TCI state 1906, TCI state 1924) being for non-SBFD symbols may refer to or comprise the TCI state indicating power control sets, pathloss RS(s), and / or other transmission parameters used for UL transmissions and / or DL receptions via non- SBFD symbols. For example, the wireless device may use the TCI state to transmit a UL signal via one or more non-SBFD symbols.

[0380] A TCI state (e.g., TCI state 2312, TCI state 2314, TCI state 1904, TCI state 1906, TCI state 1924) being for SBFD symbols may refer to or comprise the TCI state indicating power control sets, pathloss RS(s), and / or other transmission parameters used for UL transmissions and / or DL receptions via SBFD symbols. For example, the wireless device may use the TCI state to transmit a UL signal via one or more SBFD symbols.

[0381] Using a TCI state (e.g., TCI state 1904, TCI state 1906, TCI state 1924, TCI state 2312, TCI state 2314) to transmit a UL signal (e.g., UL signal 1914, UL signal 1934, UL signal 2308) may comprise: determining a spatial filter (e.g., spatial domain filter, spatial domain transmission filter, transmit beam, beam, and / or any other transmission parameter in the spatial domain) to transmit the UL signal; determining a transmission power using or with power control sets associated with or for the TCI state; transmitting the UL signal using or with the transmission power; and / or transmitting the UL signal using or with the spatial filter.

[0382] A method comprising: receiving, by a wireless device, a first downlink signal (e.g., control command 2302) comprising a parameter (e.g., flag 2304) indicating whether a TCI state is associated with sub-band full duplex (SBFD) symbols or non-SBFD symbols; receiving a second downlink signal (e.g., control command 2306) indicating: a first TCI state (e.g., TCI state 2312) and a second TCI state (e.g., TCI state 2314); and transmitting, via one or more SBFD symbols, an uplink signal (e.g., UL signal 2308) using the first TCI state in response to a first value of the parameter (or the parameter being set to the first value); and the second TCI state in response to a second value of the parameter (or the parameter being set to the second value).

[0383] In some embodiments, a PHR (e.g., PHR 2104) comprising or indicating a plurality of PH levels (e.g , two PH levels) may be the same as or be referred to as the PHR comprising the plurality of PHRsDocket No.: 24-1222PCT(e.g., two PHRs) In such cases, the PHR (e.g., PHR 2104) may comprise the plurality of PHRs (e.g., each corresponding to a respective PH level of the plurality of PH levels).

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

[0385] In the example of FIG. 24, the wireless device transmits a message 2402. The wireless device may transmit message 2402, for example, via cell 2020. The wireless device may transmit message 2402, for example, via cell 2010. The wireless device may transmit message 2402 to a base station.

[0386] In an example, message 2402 may comprise or indicate a parameter 2406. Parameter 2406 may be, for example, mTRP-PUSCH-twoPHR-Reporting. Parameter 2406 may indicate whether the wireless device supports PHR reporting related to M-TRP PUSCH repetition (e.g., calculate or determine two PHRs (at least corresponding to a component carrier that applies m-TRP PUSCH repetitions), each associated with a first PUSCH occasion corresponding to each SRS resource set, and report two PHRs). In response to parameter 2406 indicating that the wireless device supports PHR reporting related to M-TRP PUSCH repetitions, the wireless device may transmit a PHR 2404 comprising or indicating a plurality of PH levels.

[0387] The plurality of PH levels may comprise a first PH level and a second PH level. The wireless device may determine the first PH level based on or using a first SRS resource set and the second PH level based on or using a second SRS resource set.

[0388] In response to parameter 2406 not indicating that the wireless device supports PHR reporting related to M-TRP PUSCH repetitions (or in response to message 2402 not comprising or indicating parameter 2406), the wireless device may transmit PHR 2404 comprising or indicating a single PH level. The wireless device may use a first TCI state (e.g., TCI state 2312), of two TCI states (e.g., TCI state 2312 and TCI state 2314), to determine the single PH level.

[0389] In some embodiments, SRS resource set and TCI state may be used interchangeably. For example, configuration parameters 1708 may indicate a plurality of TCI states and a plurality of SRS resource sets. Each TCI state, of the plurality of TCI states may be associated with (or be mapped to) a respective SRS resource set of the plurality of SRS resource sets. For example, the plurality of TCI states may comprise a first TCI state and a second TCI state. The plurality of SRS resource sets may comprise a first SRS resource set and a second SRS resource set. The first TCI state may be associated with (or mapped to) the first SRS resource set. The second TCI state may be associated with (or mapped to) the second SRS resource set. The first TCI state may indicate the first SRS resource set (e.g., in some embodiments, “the first TCI state” may be used to refer to “the first SRS resource set”). The second TCI state may indicate the second SRS resource set (e g., in some embodiments, “the second TCI state” mayDocket No.: 24-1222PCT be used to refer to “the second SRS resource set”). In some embodiments, the phrase “SRS resource set” may be swapped with “TCI state” or vice versa.

[0390] In an example, message 2402 may comprise or indicate a parameter 2408. Parameter 2408 may be, for example, twoPHR-Reporting. Parameter 2408 may indicate whether the wireless device supports two PHR reporting related to simultaneous transmission with two panels (STx2P). For example, in response to parameter 2408 indicating that the wireless device supports PHR reporting related to STx2P, the wireless device may transmit a PHR 2404 comprising a plurality of PH levels. The wireless device may transmit PHR 2404 using or with two panels of the wireless device. For example, the wireless device may transmit PHR 2404 comprising or indicating a first PH level, of the plurality of PH levels, using or with a first panel. The wireless device may transmit PHR 2404 comprising or indicating a second PH level, of the plurality of PH levels, using or with a second panel.

[0391] In response to parameter 2408 not indicating that the wireless device supports PHR reporting related to STx2P (or in response to message 2402 not comprising parameter 2408), the wireless device may transmit PHR 2404 comprising or indicating a single PH level. The wireless device may use a first TCI state (e.g., TCI state 2312), of two TCI states (e.g., TCI state 2312 and TCI state 2314), to determine the single PH level.

[0392] In an example, message 2402 may comprise or indicate a parameter 2412. Parameter 2412 may be, for example, twoPHR-Reporting-SBFD. Parameter 2412 may indicate whether the wireless device supports two PHR reporting related to SBFD Parameter 2412 may indicate whether the wireless device supports two PHR reporting related to SBFD, each associated with a first PUSCH occasion (e.g., the transmission occasion described above in the previous examples) corresponding to each symbol type (e.g., SBFD and non-SBFD) or TCI state (e.g., TCI state for non-SBFD (e.g., TCI state 1904) and TCI state for SBFD (e.g., TCI state 1906)), and report two PHRs.

[0393] In response to parameter 2412 indicating that the wireless device supports two PHR reporting related to SBFD, the wireless device may transmit PHR 2404 comprising or indicating a plurality of PH levels. The plurality of PH levels may comprise a first PH level and second PH level. The first PH level and the second PH level may be the same as described above in previous examples.

[0394] The wireless device may determine the first PH level using a first power control set (e.g., power control set 2106) and the second PH level using a second control set (e.g., power control set 2108).

[0395] In an example, PHR 2404 may be the same as or comprise PHR 2104.

[0396] In response to parameter 2412 not indicating that the wireless device supports two PHR reporting related to SBFD (or in response to message 2402 not comprising or indicating parameter 2412), the wireless device may transmit PHR 2404 comprising or indicating a single PHR (e g., the first PH level or the second PH level).Docket No.: 24-1222PCT

[0397] In an example, the wireless device may transmit message 2402 via PUSCH, PUCCH, SRS, and / or PRACH. In an example, a base station DU may receive message 2402 transmitted by the wireless device. The base station DU may transmit a second message to a base station CU. The second message may comprise message 2402. The second message may be, for example, a UE context message (e.g., UE context setup request message, UE context setup response message. UE context setup failure message, UE context release request message, UE context release command message, UE context release complete message, UE context modification request message, UE context modification response message, UE context modification failure message, UE context modification required message, UE context modification confirm message, UE context modification refuse message, UE inactivity notification message, and / or any other message related to UE context) The second message may comprise an information element (e.g., UE-RAT-ContainerList). The information element may comprise message 2402.

[0398] A method comprising: transmitting, by a wireless device, a capability message comprising a first field indicating whether the wireless device supporting two PHR reporting related to SBFD (and / or non- SBFD) symbols.

[0399] One or more of the above example methods, wherein the capability message further comprises a second field indicating whether the wireless device supports two PHR reporting related to STx2P.

[0400] One or more of the above example methods, wherein the capability message further comprises a third field indicating whether the wireless device supports two PHR reporting related to M-TRP PUSCH repetition.

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

[0402] In the example of FIG. 25, a wireless device (e.g., wireless device 1700) receives message 2502. Message 2502 may be, for example, the same as (or comprise) message(s) 1706 and / or configuration parameters 1708.

[0403] Message 2502 may comprise or indicate a parameter 2506. Parameter 2506 may be, for example, twoPHRmode. Parameter 2506 may indicate if a power headroom is to be reported as two PHRs (each PHR associated with an SRS resource set) is enabled or not.

[0404] In existing technologies, parameter 2506 may enable two PHRs or two PH levels in a PHR, each for a respective SRS resource set. Each SRS resource set may be associated with a respective TRP. As a result, parameter 2506 may enable two PHRs or two PH levels in a PHR, each for a respective TRP. This may be suitable for multi-TRP operation. However, using the existing technologies, the wireless device may not be able to report two PHRs or two PH levels in PHR, where each of the two PHRs or two PH levels are associated with a respective symbol type (e.g., SBFD or non-SBFD). This may result in the wireless deviceDocket No.: 24-1222PCT not transmitting (or a base station not being able to request) a PHR associated with SBFD symbols. As a result, the base station may not be able to perform power-aware packet scheduling, which may lead to an increase in network interference and / or failed transmissions and / or receptions and retransmissions.

[0405] Example embodiments of the present disclosure solve the above problems. In an example embodiment, the wireless device may re-use parameter 2506 to determine whether to transmit a single PH level in a PHR or two PH levels in a PHR. For example, in response to multi-TRP operation being configured (e.g., in response to configuration parameters 1708 indicating a plurality of SRS resource sets), the wireless device may transmit the PHR with two PH levels based on parameter 2506 enabling two PHRs, wherein each PH level, of the two PH levels, are associated with a respective TRP (or SRS resource set) of the multi-TRPs (or the plurality of SRS resource sets). In response to configuration parameters 1708 indicating SBFD operation (e.g., in response to configuration parameters 1708 comprising or indicating the one or more configuration parameters for SBFD mode), the wireless device may transmit the PHR with two PH levels based on parameter 2506 enabling two PHRs, wherein each PH level, of the two PH levels, are associated with a respective symbol type (e.g., SBFD or non-SBFD).

[0406] Example embodiments of the present disclosure may lead to a reduction in network interference and / or reduced number of failed transmissions and / or receptions and retransmissions.

[0407] In an example, message 2502 may comprise or indicate a parameter 2508. Parameter 2508 may be, for example, twoPHRmode-SBFD. Parameter 2508 may indicate whether power headroom is to be reported as two PHRs or two PH levels (each PHR or PH level associated with SBFD mode and non-SBFD mode, respectively).

[0408] In an example, parameter 2508 may indicate that power headroom is to be reported as two PHRs or PH levels. For example, parameter 2508 may be set to enabled. The wireless device may transmit a PHR 2504 comprising or indicating two PH levels based on parameter 2508 indicating that power headroom is to be reported as two PHRs or PH levels (or based on parameter 2508 being set to enabled). The two PH levels may comprise a first PH level and a second PH level. The first PH level and the second PH level may be the same as described above in previous examples.

[0409] The wireless device may determine the first PH level using a first power control set (e.g., power control set 2106) and the second PH level using a second control set (e.g., power control set 2108).

[0410] In an example, PHR 2504 may be the same as or comprise PHR 2404 and / or PHR 2104.

[0411] In an example, parameter 2508 may not indicate that power headroom is to be reported as two PHRs or PH levels. For example, parameter 2508 may be set to disabled. The wireless device may transmit PHR 2504 comprising or indicating a single (e.g., not more than one) PH level based on parameter 2508 not indicating power headroom is to be reported as two PHRs or PH levels (or based on parameterDocket No.: 24-1222PCT2508 being set to disabled). The wireless device may determine the single PH level based on power control set 2106. The wireless device may determine the single PH level based on power control set 2108.

[0412] The wireless device may determine the single PH level based on any power control set.

[0413] FIG. 26 shows an example flow diagram as per an aspect of an embodiment of the present disclosure. The example of FIG. 26 may be used together with or independently from any of the previous examples (e.g., in FIGs. 1A-25).

[0414] According to the example in FIG. 26, at step 2602, a wireless device (e.g., wireless device 1700 or any of the wireless devices described in any of the embodiments of the present disclosure) receives, from a base station, one or more RRC messages (e.g., message(s) 1706). The one or more RRC messages may comprise one or more configuration parameters (e.g., configuration parameters 1708).

[0415] The one or more configuration parameters may comprise or indicate a first SRS resource set. The first SRS resource set may be of, for, associated with, corresponding to, or configured for a cell. The cell may be the same cell as previously described in any of the above embodiments. The first SRS resource set may be of, for, associated with, corresponding to, or configured for non-SBFD symbols. For example, the wireless device may use the first SRS resource set to transmit one or more uplink transmissions via one or more non-SBFD symbols.

[0416] The one or more configuration parameters may comprise or indicate a second SRS resource set. The second SRS resource set may be of, for, associated with, corresponding to, or configured for a cell. The cell may be the same cell as previously described in any of the above embodiments. The second SRS resource set may be of, for, associated with, corresponding to, or configured for SBFD symbols. For example, the wireless device may use the first SRS resource set to transmit one or more uplink transmissions via one or more SBFD symbols.

[0417] Using an SRS resource set (e.g., the first SRS resource set or the second SRS resource set) may comprise transmitting one or more uplink transmissions using a transmission power that is determined based on the SRS resource set. Using an SRS resource set may comprise transmitting one or more uplink transmissions using a spatial filter that is determined based on the SRS resource set.

[0418] The one or more configuration parameters may comprise or indicate a two-PHR-mode parameter (e.g , parameter 2506, parameter 2508, parameter 2406, parameter 2408, parameter 2412). The two-PHR- mode parameter may indicate to report two PHR values (or two PHRs) for the cell. The two PHR values may comprise a first PHR value. The two PHR values may comprise a second PHR value. The first PHR value may be associated with (e.g., computed or determined based on) the first SRS resource set. The second PHR value may be associated with (e.g., computed or determined based on) the second SRS resource set

[0419] In an example, the two-PHR-mode parameter may be set to ‘enabled.’Docket No.: 24-1222PCT

[0420] In another example, the two-PHR-mode parameter may be set to 'disabled.'

[0421] The one or more configuration parameters may comprise or indicate a list of uplink power control for the cell. Each uplink power control, of the list of uplink power controls, may comprise at least one of: a respective first power control parameter (e.g., pOAIphaSetforPUSCH, pOAIphaSetforPUCCH, pOAIphaSetforSRS) indicating or configuring power control parameters for uplink transmission via non- SBFD symbols; and / or a respective second power control parameter (e.g., pOAIphaSetforPUSCH, pOAIphaSetforPUCCH, pOAIphaSetforSRS) indicating or configuring power control parameters for uplink transmission via SBFD symbols. The first power control parameter may be or comprise, for example, power control sets 1928. The second power control parameter may be or comprise, for example, power control sets 1932.

[0422] The wireless device may perform step 2604 after step 2602. At step 2604, the wireless device may receive a control command (e.g., control command 1922 or control command 1902). The control command may be a MAC CE or a DCI. The control command may indicate a TCI state (e.g., TCI state 1924) for the cell. The TCI state may be associated with an uplink power control among the list of uplink power controls. The uplink power control may comprise, for example, a first power control parameter (e.g., pOAIphaSetforPUSCH, pOAIphaSetforPUCCH, pOAIphaSetforSRS) indicating or configuring first power control parameters for uplink transmissions in non-SBFD symbols. As shown in FIG. 19B, the first power control parameter may be or comprise, for example, power control sets 1928. Power control sets 1928 may comprise or be, for example, the first power control parameter.

[0423] The uplink power control may comprise, for example, a second power control parameter (e.g., pOAIphaSetforPUSCH-SBFD, pOAIphaSetforPUCCH-SBFD, pOAIphaSetforSRS-SBFD) indicating or configuring second power control parameters for uplink transmissions in SBFD symbols. The second power control parameter may be or comprise, for example, power control sets 1932. Power control sets 1932 may comprise or be, for example, the second power control parameter.

[0424] At step 2606, the wireless device may transmit a PHR (e.g., PHR 2104). The PHR may comprise or indicate two Type-1 PHR values or reports for the cell. The wireless device may transmit the PHR in a slot (e.g., slot 2110). The wireless device may perform step 2606, e.g., after step 2604.

[0425] In some embodiments, the wireless device may perform step 2606 without performing step 2604.

[0426] In an example, the PHR may be an 'actual' PHR. In another example, the PHR may be 'virtual' PHR.

[0427] In an example, the two Type-1 PHR values may comprise a first Type-1 PHR value (e.g., PHR 2002). The two Type-1 PHR values may comprise a second Type-1 PHR value (e.g., PHR 2004). The first Type-1 PHR value may be, for example, for an actual PUSCH transmission (e.g., as shown in FIG 20A).Docket No.: 24-1222PCTThe actual PUSCH transmission may start earliest in the slot. The actual PUSCH transmission may be associated with the second SRS resource set.

[0428] The second Type-1 PHR value may be for a reference PUSCH transmission (e.g., as shown in FIG. 21 in slot 2120). The reference PUSCH transmission may be associated with the first SRS resource set.

[0429] The wireless device may determine (e.g., calculate) the second Type-1 PHR value based on or using: the first power control parameters indicated by the first power control parameter (e.g., power control sets 1928) of the uplink power control associated with the TCI state (e.g., TCI state 1924); and / or a pathloss reference signal (e.g., identified by pathiossReferenceRS-ld) associated with the TCI state (e.g., TCI state 1924).

[0430] In an example, the first Type-1 PHR value may be for an actual PUSCH transmission starting earliest in the slot and associated with the first SRS resource set; and the second Type-1 PHR value of is for a reference PUSCH transmission associated with the second SRS resource set. The wireless device may determine the second Type-1 PHR value based on or using: the second power control parameters indicated by the second power control parameter (e.g., power control sets 1932) of the uplink power control associated with the TCI state (e.g., TCI state 1924); and / or a pathloss reference signal (e.g., identified by pathlossReferenceRS-ld) associated with the TCI state (e.g., TCI state 1924).

[0431] In an example, a first Type 1 PHR value, of the two Type-1 PHR values, may be for a first reference PUSCH transmission associated with the first SRS resource set. A second Type-1 PHR value, of the two Type-1 PHR values, is for a second reference PUSCH transmission associated with the second SRS resource set. In an example, there may be no actual PUSCH transmission (e.g., similar to the example shown in FIG. 20B), in the slot, associated with an SRS resource set among the first SRS resource set and the second SRS resource set. the wireless device may determine (e.g., calculate) the first Type-1 PHR value based on or using the first power control parameters indicated by the first power control parameter (e.g., power control sets 1928) of the uplink power control associated with the TCI state (e.g., TCI state 1924); and / or a pathloss reference signal (e.g., identified by path'ossReferenceRS-ld) associated with the TCI state (e.g., TCI state 1924). The wireless device may determine (e.g., calculate) the second Type-1 PHR value based on or using: the second power control parameters indicated by the second power control parameter (e.g., power control sets 1932) of the uplink power control associated with the TCI state (e.g., TCI state 1924); and / or the pathloss reference signal (e.g., identified by pathlossReferenceRS-ld) associated with the TCI state (e.g., TCI state 1924).

[0432] In an example, the wireless device may receive one or more second RRC messages. For example, the wireless device may receive the one or more second RRC messages after step 2606.Docket No.: 24-1222PCT

[0433] The one or more second RRC messages may comprise one or more second configuration parameters. The one or more second configuration parameters may not comprise the two-PHR-mode parameter. The wireless device may transmit a second PHR indicating one (e.g., single, not two) Type-1 PHR value, e.g., based on (e.g., in response to, upon, or after) receiving the one or more second configuration parameter not comprising the two-PHR-mode parameter (e.g., parameter 2506, parameter 2508). The wireless device may determine (e.g., calculate) the one Type-1 PHR value based on or using: the first power control parameters indicated by the first power control parameter (e.g., power control sets 1928) associated with the TCI state (e.g...

Claims

1. Docket No.: 24-1222PCTCLAIMSWhat is claimed is:

1. A method comprising: receiving, by a wireless device, one or more radio resource control (RRC) messages comprising one or more configuration parameters that: indicate a first SRS resource set for a cell; and indicate a second SRS resource set for SBFD symbols for the cell; comprise a two power headroom report (PHR) mode parameter indicating to report two power headroom values, or two PHRs, is enabled, each power headroom value is associated with the first or the second SRS resource set; and indicate a list of uplink power controls for the cell, wherein each uplink power control in the list of uplink power controls comprises at least one of: a respective first power control parameter indicating / configuring power control parameters for uplink transmissions; or a respective second power control parameter indicating / configuring power control parameters for uplink transmissions in SBFD symbols; receiving a control command indicating a TCI state for the cell, wherein: the TCI state is associated with an uplink power control among the list of uplink controls; and the uplink power control comprises: a first power control parameter indicating / configuring first power control parameters for uplink transmissions; and a second power control parameter indicating / configuring second power control parameters for uplink transmissions in SBFD symbols; and transmitting, in a slot, a PHR indicating two Type 1 power headroom values / reports for the cell.

2. The method of claim 1 , wherein: a first Type 1 power headroom value of the two Type 1 power headroom values is for an actual PUSCH transmission starting earliest in the slot and associated with the second SRS resource set; and a second Type 1 power headroom value of the two Type 1 power headroom values is for a reference PUSCH transmission associated with the first SRS resource set.

3. The method of claim 1 or 2, further comprising calculating the second Type 1 power headroom value based on or using: the first power control parameters indicated by the first power control parameter of the uplink power control associated with the TCI state; and a pathloss reference signal associated with the TCI state.Docket No.: 24-1222PCT4. The method of any one of claims 1 to 3, wherein: a first Type 1 power headroom value of the two Type 1 power headroom values is for an actual PUSCH transmission starting earliest in the slot and associated with the first SRS resource set; and a second Type 1 power headroom value of the two Type 1 power headroom values is for a reference PUSCH transmission associated with the second SRS resource set.

5. The method of claim 4, further comprising calculating the second Type 1 power headroom value based on or using: the second power control parameters indicated by the second power control parameter of the uplink power control associated with the TCI state; and a pathloss reference signal associated with the TCI state.

6. The method of any one of claims 1 to 5, wherein: a first Type 1 power headroom value of the two Type 1 power headroom values is for a first reference PUSCH transmission associated with the first SRS resource set; and a second Type 1 power headroom value of the two Type 1 power headroom values is for a second reference PUSCH transmission associated with the second SRS resource set7. The method of claim 6, wherein there is no actual PUSCH transmission, in the slot, associated with an SRS resource set among the first SRS resource set and the second SRS resource set.

8. The method of claim 7, further comprising calculating the first Type 1 power headroom value based on or using: the first power control parameters indicated by the first power control parameter of the uplink power control associated with the TCI state; and a pathloss reference signal associated with the TCI state.

9. The method of claim 8, further comprising calculating the second Type 1 power headroom value based on or using: the second power control parameters indicated by the second power control parameter of the uplink power control associated with the TCI state; and the pathloss reference signal associated with the TCI state.

10. The method of any one of claims 1 to 9, further comprising: receiving one or more second RRC messages comprising one or more second configuration parameters that do not comprise a two power headroom report (PHR) mode parameter; and transmitting a second PHR indicating one Type 1 power headroom value / report.

11. The method of claim 10, further comprising calculating the one Type 1 power headroom value based on or using:Docket No.: 24-1222PCT the first power control parameters indicated by the first power control parameter of the uplink power control associated with the TCI state; and a pathloss reference signal associated with the TCI state.

12. The method of claim 10 or 11 , further comprising calculating the one Type 1 power headroom value based on or using: the first power control parameters indicated by the first power control parameter of the uplink power control associated with the TCI state or the second power control parameters indicated by the second power control parameter of the uplink power control associated with the TCI state; and a pathloss reference signal associated with the TCI state.

13. The method of claim 12, wherein the calculating the one Type 1 power headroom value based on or using: the first power control parameters indicated by the first power control parameter is based on transmitting the second PHR in one or more non-SBFD symbols of a second cell that the second PHR is transmitted on; or the second power control parameters indicated by the second power control parameter is based on transmitting the second PHR in one or more SBFD symbols of a second cell that the second PHR is transmitted on.

14. The method of claim 12 or 13, wherein the calculating the one Type 1 power headroom value based on or using: the first power control parameters indicated by the first power control parameter is based on transmitting the second PHR in one or more non-SBFD symbols of the cell; or the second power control parameters indicated by the second power control parameter is based on transmitting the second PHR in one or more SBFD symbols of the cell.

15. A method comprising: receiving, by a wireless device and for uplink transmissions via a first cell, a radio resource control (RRC) message indicating: a first power control set for non-sub-band full duplex (SBFD) symbols; and a second power control set for SBFD symbols; transmitting, via a transmission occasion of a second cell, a power headroom report that is calculated using the first power control set in response to: the first cell not being scheduled with an uplink transmission that overlaps with the transmission occasion; and an earliest symbol, of the first cell, that overlaps with the transmission occasion, being an SBFD symbol.Docket No.: 24-1222PCT16. A method comprising: receiving, by a wireless device and for uplink transmissions via a first cell, a downlink signal indicating: a first power control set for non-sub-band full-duplex (SBFD) symbols; and a second power control set for SBFD symbols; and transmitting, via a transmission occasion and a second cell, a power headroom report comprising a power headroom level that is computed using a power control set among the first power control set and the second power control set.

17. The method of claim 15 or 16, wherein the power control set is determined based on a slot that comprises the transmission occasion.

18. The method of claim 17, wherein the power control set is the first power control set based on an earliest or last symbol of the slot being a non-SBFD symbol.

19. The method of claim 17 or 18, wherein the power control set is the second power control set based on an earliest or last symbol of the slot being an SBFD symbol.

20. The method of any one of claims 15 to 19, wherein the power control set is determined based on a slot that overlaps in time with the transmission occasion.21 . The method of claim 20, wherein the slot is of the first cell.

22. The method of claim 21 , wherein the power control set is the first power control set based on the slot not comprising any SBFD symbol.

23. The method of claim 21 , wherein the power control is the second power control set based on the slot comprising an SBFD symbol.

24. The method of claim 21 , wherein the power control set is the first power control set based on earliest symbol in the slot being a non-SBFD symbol.

25. The method of claim 21 , wherein the power control set is the second power control set based on an earliest symbol in the slot being an SBFD symbol.

26. The method of any one of claims 15 to 25, wherein the power control set is determined at random from among the first power control set and the second power control set.

27. The method of claim 26, wherein the power headroom report indicates the power control set.

28. The method of claim 27, wherein the power headroom report comprises a field indicating whether the first power control set or the second power control set is used to determine the power headroom level.

29. The method of any one of claims 15 to 28, further comprising receiving a second downlink signal.

30. The method of claim 29, wherein the second downlink signal is different from the downlink signal.31 . The method of claim 29 or 30, wherein the second downlink signal and the downlink signal are the same.Docket No.: 24-1222PCT32. The method of any one of claims 29 to 31 , wherein the second downlink signal indicates the power control set from among the first power control set and the second power control set.

33. The method of claim 32, wherein the power control set is indicated by the second downlink signal.

34. The method of claim 32 or 33, wherein the power control set is the first power control set based on the second downlink signal indicating the first power control set.

35. The method of any one of claims 32 to 34, wherein the power control set is the second power control set based on the second downlink signal indicating the second power control set.

36. The method of any one of claims 15 to 35, wherein the power control set is the first power control set based on the transmission occasion comprising a non-SBFD symbol.

37. The method of any one of claims 15 to 36, wherein the power control set is the first power control set based on the transmission occasion not comprising an SBFD symbol.

38. The method of any one of claims 15 to 37, wherein the power control set is the second power control set based on the transmission occasion comprising an SBFD symbol.

39. The method of any one of claims 15 to 38, wherein the power control set is the second power control set based on the transmission occasion not comprising a non-SBFD symbol.

40. The method of any one of claims 15 to 39, wherein the power control set is determined based on a first or last symbol of the transmission occasion.41 . The method of claim 40, wherein the power control set is the first power control set based on the first or last symbol of the transmission occasion being an SBFD symbol.

42. The method of claim 40 or 41 , wherein the power control set is the second power control set based on the first or last symbol of the transmission occasion being a non-SBFD symbol.

43. The method of any one of claims 15 to 42, wherein the power control set is determined based on a second power headroom report.

44. The method of claim 43, wherein the second power headroom report is transmitted before the power headroom report.

45. The method of claim 43 or 44, wherein the power control set is the first power control set based on the second power headroom report being determined using the second power control set.

46. The method of any one of claims 43 to 45, wherein the power control set is the second power control set based on the second power headroom report being determined using the first power control set.

47. The method of any one of claims 15 to 46, wherein the power headroom level is determined based on a first power headroom level and a second power headroom level.

48. The method of claim 47, wherein the first power headroom level is determined based on the first power control set.Docket No.: 24-1222PCT49. The method of claim 47 or 48, wherein the second power headroom level is determined based on the second power control set.

50. The method of any one of claims 47 to 49, wherein the power headroom level is the first power headroom level based on the first power headroom level being greater than the second power head room level.51 . The method of any one of claims 47 to 50, wherein the power headroom level is the first power headroom level based on the first power headroom level being less than or equal to the second power head room level.

52. The method of any one of claims 15 to 51 , wherein the power control set is the first power control set based on the second cell not being configured with SBFD mode.

53. The method of any one of claims 15 to 52, wherein: the first power control set is for a first TCI state; and the second power control set is for a second TCI state.

54. The method of any one of claims 15 to 53, wherein: the first power control set is for a first TCI state; and the second power control set is for the first TCI state.

55. The method of any one of claims 15 to 54, wherein the transmitting the power headroom report is further based on the downlink signal not indicating twoPHRmode.

56. A method comprising: receiving, by a wireless device, a first downlink signal comprising a parameter indicating whether a TCI state is associated with sub-band full duplex (SBFD) symbols or non-SBFD symbols; receiving a second downlink signal indicating: a first TCI state; and a second TCI state; transmitting, via one or more SBFD symbols, a first uplink signal using: the first TCI state in response to a first value of the parameter; and the second TCI state in response to a second value of the parameter.

57. A method comprising: transmitting, by a wireless device, a capability message comprising: a first field indicating whether the wireless device supports up to two NZP CSI-RS resources associated with two SRS resource sets for non-codebook-based mTRP PUSCH; a second field indicating whether the wireless device supports two PHR reporting related to STx2P; andDocket No.: 24-1222PCT a third field indicating whether the wireless device supports two PHR reporting related to SBFD and non-SBFD modes.

58. A method comprising: receiving, by a wireless device, a downlink signal comprising: a first parameter indicating whether a power headroom is reported as a first plurality of PHRs is enabled, wherein each PHR, of the first plurality PHRs, is associated with a respective SRS resource set; a second parameter indicating whether a power headroom is reported as a second plurality of PHRs is enabled, wherein: a first PHR, of the second plurality of PHRs, is associated with non-SBFD symbols; and a second PHR, of the second plurality of PHRs, is associated with SBFD symbols; transmitting, a power headroom report comprising at least two PH levels, in response to59. 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 58.

60. 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 58.

Images