Determination of path loss reference signals in uplink channel repetitions

Abstract

A wireless device may receive downlink control information (DCI) scheduling uplink repetitions of a transport block. Based on the absence of a sounding reference signal resource indicator (SRI) field in the DCI, the wireless device may transmit a first repetition of the transport block with a first transmit power based on a first path loss reference signal (RS) and a second repetition of the transport block with a second transmit power based on a second path loss RS.

Description

[Background technology]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This application claims the benefit of U.S. Provisional Patent Application No. 63 / 125,753, filed December 15, 2020, which is incorporated herein by reference in its entirety. Summary of the Invention [Means for solving the problem]

[0002] In this disclosure, various embodiments are presented as examples of how the disclosed technology may be implemented and / or how the disclosed technology may be practiced in environments and scenarios. It will be apparent to those skilled in the relevant art that various changes in form and detail can be made without departing from the scope. Indeed, after reading the specification, it will become apparent to those skilled in the relevant art how to implement alternative embodiments. The present embodiments should not be limited by any of the exemplary embodiments. Embodiments of the present disclosure are described with reference to the accompanying drawings. Limitations, features, and / or elements from the disclosed exemplary embodiments may be combined to create further embodiments within the scope of the present disclosure. Figures highlighting features and advantages are shown by way of example only. The disclosed architecture is sufficiently flexible and configurable to be utilized in ways other than those shown. For example, the actions listed in any flowchart may be rearranged or used only optionally in some embodiments.

[0003] Embodiments may be configured to operate as needed. The disclosed mechanisms may be executed when certain criteria are met, for example, in a wireless device, a base station, a wireless environment, a network, a combination of the above, etc. Exemplary criteria may be based at least in part on, for example, wireless device or network node configuration, traffic load, initial system settings, packet size, traffic characteristics, a combination of the above, etc. Once one or more criteria are met, various exemplary embodiments may be applied. Thus, it may be possible to implement exemplary embodiments that selectively implement the disclosed protocols.

[0004] 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 certain capabilities depending on the category and / or capabilities of the wireless devices. When this disclosure refers to a base station communicating with multiple wireless devices, this disclosure may also refer to a subset of all wireless devices in the coverage area. This disclosure may refer, for example, to multiple wireless devices of a given LTE or 5G release that include a given capability and are in a given sector of the base station. Multiple wireless devices in this disclosure may refer to selected wireless devices and / or a subset of all wireless devices in the coverage area that perform according to the disclosed methods, etc. There may be multiple base stations or multiple wireless devices in the coverage area that may not comply with the disclosed methods. For example, the wireless devices or base stations may perform based on older releases of LTE or 5G technology. [Brief explanation of the drawings]

[0005] Some examples of various embodiments of the present disclosure are described herein with reference to the drawings.

[0006] [Figure 1A] 1 illustrates an example of a mobile communication network in which embodiments of the present disclosure may be implemented. [Figure 1B] 1 illustrates an example of a mobile communication network in which embodiments of the present disclosure may be implemented. [Figure 2A] The new radio (NR) user plane and control plane protocol stacks are shown, respectively. [Figure 2B] The new radio (NR) user plane and control plane protocol stacks are shown, respectively. [Figure 3] 2B illustrates an example of services provided between protocol layers of the NR user plane protocol stack of FIG. 2A. [Figure 4A] 2B illustrates an exemplary downlink data flow through the NR user plane protocol stack of FIG. 2A. [Figure 4B] 1 illustrates an exemplary format of a MAC subheader in a MAC PDU. [Figure 5A] The mapping between downlink and uplink logical, transport, and physical channels is shown, respectively. [Figure 5B] The mapping between downlink and uplink logical, transport, and physical channels is shown, respectively. [Figure 6] FIG. 1 is an exemplary diagram illustrating RRC state transitions of a UE. [Figure 7] 1 illustrates an example structure of an NR frame in which OFDM symbols are grouped. [Figure 8] 1 illustrates an example configuration of slots in the time and frequency domain of an NR carrier. [Figure 9] An example of bandwidth adaptation using three configured BWPs for an NR carrier is shown. [Figure 10A] Three carrier aggregation configurations with two component carriers are shown. [Figure 10B] 1 shows an example of how aggregation cells can be configured into one or more PUCCH groups. [Figure 11A] 1 shows an example of an SS / PBCH block structure and location. [Figure 11B] 1 shows an example of CSI-RS mapped to the time and frequency domain. [Figure 12A] Three examples of downlink and uplink beam management procedures are shown, respectively. [Figure 12B] Three examples of downlink and uplink beam management procedures are shown, respectively. [Figure 13A] A four-step contention-based random access procedure, a two-step contention-free random access procedure, and an alternative two-step random access procedure are shown, respectively. [Figure 13B] A four-step contention-based random access procedure, a two-step contention-free random access procedure, and an alternative two-step random access procedure are shown, respectively. [Figure 13C] A four-step contention-based random access procedure, a two-step contention-free random access procedure, and an alternative two-step random access procedure are shown, respectively. [Figure 14A] 1 shows an example of a CORESET configuration for a bandwidth portion. [Figure 14B] 10 shows an example of CCE-to-REG mapping for DCI transmission on CORESET and PDCCH processing. [Figure 15] 1 illustrates an example of a wireless device communicating with a base station. [Figure 16A] 1 shows an exemplary structure for uplink and downlink transmission. [Figure 16B] 1 shows an exemplary structure for uplink and downlink transmission. [Figure 16C] 1 shows an exemplary structure for uplink and downlink transmission. [Figure 16D] 1 shows an exemplary structure for uplink and downlink transmission. [Figure 17] 1 illustrates an example of uplink channel repetition in accordance with an aspect of an exemplary embodiment of the present disclosure. [Figure 18] 1 illustrates an example of uplink channel repetition in accordance with an aspect of an exemplary embodiment of the present disclosure. [Figure 19] 1 illustrates an example of uplink channel repetition in accordance with an aspect of an exemplary embodiment of the present disclosure. [Figure 20] 1 illustrates an uplink repetition scheme according to an aspect of an exemplary embodiment of the present disclosure. [Figure 21] 1 illustrates a flow diagram of power control in uplink channel repetition, according to an aspect of the exemplary embodiment of the present disclosure. [Figure 22] 1 illustrates a flow diagram of power control in uplink channel repetition, according to an aspect of the exemplary embodiment of the present disclosure. [Figure 23] 1 illustrates a flow diagram of power control in uplink channel repetition, according to an aspect of the exemplary embodiment of the present disclosure. [Figure 24] 1 illustrates a flow diagram of power control in uplink channel repetition, according to an aspect of the exemplary embodiment of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0007] (Detailed Description of the Invention) As used herein, "a" and "an" and similar phrases are interpreted as "at least one" and "one or more." Similarly, any term ending in the suffix "(s)" should be interpreted as "at least one" and "one or more." As used herein, the term "may" is interpreted as "may, for example." In other words, the term "may" indicates that the phrase following the term "may" is one example of multiple suitable possibilities and may or may not be used by one or more of various embodiments. As used herein, the terms "comprises" and "consists of" list one or more components of a described element. The term "comprises" is interchangeable with "includes" and does not exclude unlisted components included in a described element. In contrast, "consists of" provides a complete list of one or more components of a described element. As used herein, the term "based on" should be interpreted as "based at least in part on," rather than, for example, "based only on." As used herein, the term "and / or" refers to any possible combination of the listed elements. For example, "A, B, and / or C" can refer to A, B, C, A and B, A and C, B and C, or A, B, and C.

[0008] If A and B are sets and every element of A is also an element of B, then A is said to be a subset of B. Only non-empty sets and subsets are considered herein. For example, possible subsets of B = {cell1, cell2} are {cell1}, {cell2}, and {cell1, cell2}. The phrase "based on" (or equivalently, "based at least on") indicates that the phrase following the term "based on" is one example of many suitable possibilities that may or may not be used in one or more of various embodiments. The phrase "responsive to" (or equivalently, "at least in response to") indicates that the phrase following the phrase "responsive to" is one example of many suitable possibilities that may or may not be used in one or more of various embodiments. The phrase "in response to" (or equivalently, "at least in response to") indicates that the phrase following the phrase "in response to" is one example of many suitable possibilities that may or may not be used in one or more of various embodiments. The phrase "adopted / used" (or equivalently "adopted / used at least") indicates that the phrase following the phrase "adopted / used" is one example of many suitable possibilities that may or may not be used in one or more of the various embodiments.

[0009] The term configured may relate to the capacity of a device, regardless of whether the device is in an operational or non-operational state. Configured may refer to a particular setting of a device that affects the operational characteristics of the device, regardless of whether the device is in an operational or non-operational state. In other words, hardware, software, firmware, registers, memory values, etc. may be "configured" within a device, regardless of whether the device is in an operational or non-operational state, to provide the device with particular characteristics. A term such as "a control message originating in a device" may mean that the control message has parameters that can be used to configure particular characteristics in the device or to implement particular actions in the device, regardless of whether the device is in an operational or non-operational state.

[0010] In this disclosure, a parameter (or equivalently referred to as a field, or information element: IE) may contain one or more information objects, which in turn may contain one or more other objects. For example, if parameter (IE) N contains parameter (IE) M, which contains parameter (IE) K, which in turn contains parameter (information element) J, then N contains K and N contains J. In an exemplary embodiment, when one or more messages contain multiple parameters, it means that a parameter of the multiple parameters is included in at least one of the one or more messages, but need not be included in each of the one or more messages.

[0011] Many presented features are described as optional through the use of "may" or parentheses. For the sake of brevity and readability, this disclosure does not explicitly describe each and every variation that may be obtained by selecting from a set of optional features. This disclosure should be construed as explicitly disclosing all such variations. For example, a system described as having three optional features may be embodied in seven ways: with only one of the three possible features, with any two of the three features, or with three of the three features.

[0012] Many of the elements described in the disclosed embodiments may be implemented as modules. Here, a module is defined 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 biological components), or a combination thereof, which may be behaviorally equivalent. For example, a module may be implemented as a software routine written in a computer language configured to run on a hardware machine (e.g., C, C++, Fortran, Java, Basic, Matlab, etc.) or Simulink, Stateflow, GNU Octave, or LabVIEW MathScript. It may also be possible to implement a module using physical hardware incorporating discrete or programmable analog, digital, and / or quantum hardware. Examples of programmable hardware include 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, and C++. FPGAs, ASICs, and CPLDs are often programmed using a hardware description language (HDL) such as Verilog or Verilog Hardware Description Language (VHDL), which configures the connections between the programmable device's less functional internal hardware modules. The above techniques are often used in combination to achieve a functional modular result.

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

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

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

[0016] The term wireless device may be used throughout this disclosure to refer to and encompass any mobile or fixed (non-portable) device for which wireless communication is required or available. For example, a wireless device may be a phone, a smartphone, a tablet, a computer, a laptop, a sensor, a meter, a wearable device, an Internet of Things (IoT) device, a vehicular roadside unit (RSU), a relay node, an automobile, and / or any combination thereof. The term wireless device encompasses other terms, including user equipment (UE), user terminal (UT), access terminal (AT), mobile station, handset, wireless transmit / receive unit (WTRU), and / or wireless communication device.

[0017] 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, e.g., associated with WiFi or other suitable wireless communication standards), and / or any combination thereof. A base station may include at least one gNB central unit (gNB-CU) and at least one gNB distributed unit (gNB-DU).

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

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

[0020] The RAN 104 may be deployed as a homogeneous network of macrocell base stations having similar antenna patterns and similar high levels of transmit power. The RAN 104 may be deployed as a heterogeneous network. In a heterogeneous network, small cell base stations may be used to provide small coverage areas, such as coverage areas that overlap with the relatively large coverage areas provided by macrocell base stations. The small coverage areas may be provided in areas of high data traffic (or so-called hot spots) or areas where macrocell coverage is weak. Examples of small cell base stations include, in order of decreasing coverage area, microcell base stations, picocell base stations, and femtocell or home base stations.

[0021] The 3rd 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 of 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 Systems (5GS). Embodiments of the present disclosure are described with reference to a RAN for a 3GPP 5G network, referred to as a Next Generation RAN (NG-RAN). Embodiments may be applicable to the RAN 104 of FIG. 1A, RANs for earlier 3G and 4G networks, and RANs for other mobile communication networks, such as future networks not yet specified (e.g., a 3GPP 6G network). NG-RAN implements 5G radio access technology known as New Radio (NR) and can be provisioned to implement other radio access technologies, including 4G radio access technology or non-3GPP radio access technologies.

[0022] 1B illustrates another example mobile communication network 150 in which embodiments of the present disclosure may be implemented. The mobile communication network 150 may be, for example, a PLMN run by a network operator. As shown in FIG. 1B, the 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 the corresponding components described with respect to FIG. 1A.

[0023] The 5G-CN 152 provides the UE 156 with an interface to one or more DNs, such as a public DN (e.g., the Internet), a private DN, and / or an intra-operator DN. As part of its interfacing functions, the 5G-CN 152 may set up an end-to-end connection between the UE 156 and one or more DNs, authenticate the UE 156, and provide charging functions. Compared to the CNs of 3GPP 4G networks, the 5G-CN 152 may be based on a service-based architecture. This means that the architecture of the nodes that make up the 5G-CN 152 may be defined as network functions that provide services through interfaces to other network functions. The network functions of the 5G-CN 152 may be implemented in several ways: 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).

[0024] As shown in FIG. 1B, the 5G-CN 152 includes an Access and Mobility Management Function (AMF) 158A and a User Plane Function (UPF) 158B, which are shown in FIG. 1B as one component, AMF / UPF 158, for ease of explanation. The UPF 158B may act as a gateway between the NG-RAN 154 and 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 one or more DNs, quality of service (QoS) processing for the user plane (e.g., packet filtering, gating, uplink / downlink rate enforcement, and uplink traffic validation), downlink packet buffering, and downlink data notification triggering. The UPF 158B may function as an anchor point for intra / inter-radio access technology (RAT) mobility, an external protocol (or packet) data unit (PDU) session point interconnected to one or more DNs, and / or a branching point to support multi-homed PDU sessions. The UE 156 may be configured to receive services via a PDU session, which is a logical connection between the UE and the DN.

[0025] The AMF 158A may perform functions such as termination of Non-Access Stratum (NAS) signaling, 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 retransmissions), registration area management, intra-system and inter-system mobility support, access authentication, access authorization including checking roaming rights, mobility management control (subscription and policy), support for network slicing, and / or session management function (SMF) selection. NAS may refer to a function operating between the CN and the UE, and AS may refer to a function operating between the UE and the RAN.

[0026] 5G-CN 152 may include one or more additional network functions not shown in FIG. 1B for clarity. For example, 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).

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

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

[0029] The gNB 160 and / or ng-eNB 162 may be connected to one or more AMF / UPF functions of the 5G-CN 152, such as the AMF / UPF 158, by one or more NG interfaces. For example, the gNB 160A may be connected to the UPF 158B of the AMF / UPF 158 by an NG-User Plane (NG-U) interface. The NG-U interface may provide for the provisioning of user plane PDUs between the gNB 160A and the UPF 158B (e.g., non-guaranteed delivery). The gNB 160A may be connected to the AMF 158A using 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 alert message transmission.

[0030] The gNB 160 may provide NR user plane and control plane protocol terminations toward the UE 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 the Uu interface associated with a first protocol stack. The ng-eNB 162 may provide Evolved UMTS Terrestrial Radio Access (E-UTRA) user plane and control plane protocol terminations toward the UE 156 over the Uu interface, where E-UTRA refers to a 3GPP 4G radio access technology. For example, the ng-eNB 162B may provide E-UTRA user plane and control plane protocol terminations toward the UE 156B over the Uu interface associated with a second protocol stack.

[0031] The 5G-CN 152 has been described as being configured to handle NR and 4G radio access. Those skilled in the art will understand that it may be possible for the NR to connect to a 4G core network in a mode known as "non-standalone operation." In non-standalone operation, the 4G core network is used to provide (or at least support) control plane functions (e.g., initial access, mobility, and paging). Although only one AMF / UPF 158 is shown in FIG. 1B, one gNB or ng-eNB may be connected to multiple AMF / UPF nodes to provide redundancy and / or load sharing across multiple AMF / UPF nodes.

[0032] 1B, interfaces between network elements (e.g., Uu, Xn, and NG interfaces) may be associated with protocol stacks that the network elements use to exchange data and signaling messages. The protocol stacks may include two planes: a user plane and a control plane. The user plane may handle data of interest to the user, and the control plane may handle signaling messages of interest to the network elements.

[0033] Figures 2A and 2B show example NR user plane and NR control plane protocol stacks, respectively, for the Uu interface between UE 210 and gNB 220. The protocol stacks shown in Figures 2A and 2B may be the same as or similar to those used for the Uu interface between UE 156A and gNB 160A shown in Figure 1B, for example.

[0034] 2A shows an NR user plane protocol stack including 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 the PHYs 211 and 221 include media access control layers (MAC) 212 and 222, radio link control layers (RLC) 213 and 223, packet data convergence protocol layers (PDCP) 214 and 224, and service data application protocol layers (SDAP) 215 and 225. Together, these four protocols may constitute Layer 2, or the data link layer, of the OSI model.

[0035] FIG. 3 illustrates an example of services provided between protocol layers in the NR user plane protocol stack. Starting from the top of FIGS. 2A and 3, the SDAPs 215 and 225 may perform QoS flow processing. The UE 210 may receive services via a PDU session, which may be a logical connection between the UE 210 and the DN. A PDU session may have one or more QoS flows. The CN's UPF (e.g., UPF 158B) may map IP packets to 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 one or more QoS flows and one or more data radio bearers. The mapping / de-mapping between QoS flows and 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 QoS flows and data radio bearers via reflected 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) that may be observed by the SDAP 215 at the UE 210 to determine mapping / demapping between QoS flows and data radio bearers.

[0036] PDCPs 214 and 224 may perform header compression / decompression to reduce the amount of data that needs to be transmitted over the air interface, encryption / decryption to prevent unauthorized decoding of data transmitted over the air interface, and integrity protection (to ensure that control messages originate from the intended source). PDCPs 214 and 224 may perform, for example, retransmission of untransmitted packets, in-sequence delivery and reordering of packets, and elimination of duplicate received packets for intra-gNB handover. PDCPs 214 and 224 may perform packet duplication to improve the likelihood of a packet being received and to eliminate any duplicate packets at the receiver. Packet duplication may be useful for services that require high reliability.

[0037] Although not shown in FIG. 3 , the PDCPs 214 and 224 may perform mapping / demapping between split radio bearers 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 a cell group in dual connectivity. The PDCPs 214 and 224 may map / demap the split radio bearer between the RLC channels belonging to the cell group.

[0038] The RLCs 213 and 223 may perform segmentation, retransmission via automatic repeat request (ARQ), and removal of duplicate data units received from the 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 in which the RLC is operating, the RLC may perform one or more of the indicated functions. This RLC configuration may be per logical channel, independent of numerology and / or transmission time interval (TTI) duration. As shown in FIG. 3, the RLCs 213 and 223 may provide RLC channels as services to the PDCPs 214 and 224, respectively.

[0039] The MACs 212 and 222 may perform multiplexing / demultiplexing of logical channels and / or mapping between logical channels and transport channels. Multiplexing / demultiplexing may include multiplexing / demultiplexing of data units belonging to one or more logical channels to / 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 through dynamic scheduling. Scheduling may be performed at the gNB 220 (at the MAC 222) for the downlink and uplink. The MACs 212 and 222 may be configured to perform error correction, priority handling between the logical channels of the UE 210 through logical channel prioritization, and / or padding through hybrid automatic repeat request (HARQ) (e.g., one HARQ entity per carrier in the case of carrier aggregation (CA)). The MACs 212 and 222 may support one or more numerologies and / or transmission timings. In one example, mapping restrictions in logical channel prioritization may control which numerology and / or transmission timing a logical channel may use. As shown in Figure 3, MACs 212 and 222 may offer logical channels as services to RLCs 213 and 223.

[0040] The PHYs 211 and 221 may perform mapping of transport channels to physical channels and digital and analog signal processing functions to transmit and receive information over the air interface. These digital and analog signal processing functions may include, for example, encoding / 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 services to the MACs 212 and 222.

[0041] Figure 4A shows an example of downlink data flow through the NR user plane protocol stack. Figure 4A shows the downlink data flow of three IP packets (n, n+1, and m) through the NR user plane protocol stack, generating two TBs at gNB 220. The uplink data flow through the NR user plane protocol stack may be similar to the downlink data flow shown in Figure 4A.

[0042] The downlink data flow in Figure 4A begins when the SDAP 225 receives three IP packets from one or more QoS flows and maps the three packets to radio bearers. In Figure 4A, the SDAP 225 maps IP packets n and n+1 to the first radio bearer 402 and maps IP packet m to the second radio bearer 404. An SDAP header (labeled "H" in Figure 4A) is added to the IP packets. Data units from / to higher protocol layers are referred to as service data units (SDUs) of the lower protocol layers, and data units to / from lower protocol layers are referred to as protocol data units (PDUs) of the higher protocol layers. As shown in Figure 4A, the data units from the SDAP 225 are SDUs of the lower protocol layer PDCP 224 and PDUs of the SDAP 225.

[0043] The remaining protocol layers in FIG. 4A may perform associated functions (e.g., with respect to FIG. 3), add corresponding headers, and forward their respective outputs to the next lower layer. For example, PDCP 224 may perform IP header compression and encryption and forward its output to RLC 223. RLC 223 may optionally perform segmentation (e.g., as shown for IP packet m in FIG. 4A) and forward its output to MAC 222. MAC 222 may multiplex several RLC PDUs and attach MAC subheaders to the RLC PDUs to form transport blocks. In NR, the MAC subheaders may be distributed throughout the MAC PDU, as shown in FIG. 4A. In LTE, the MAC subheader may be located entirely at the beginning of the MAC PDU. The NR MAC PDU structure may reduce processing time and associated delays because the MAC PDU subheaders may be calculated before the complete MAC PDU is assembled.

[0044] 4B shows an example format of a MAC subheader in a MAC PDU. The MAC subheader includes an SDU length field to indicate the length (e.g., in bytes) of the MAC SDU to which the MAC subheader corresponds, a logical channel identifier (LCID) field to identify the logical channel on which the MAC SDU originated to assist in the demultiplexing process, a flag (F) to indicate the size of the SDU length field, and a reserved bit (R) field for future use.

[0045] FIG. 4B further illustrates a MAC Control Element (CE) inserted into a MAC PDU by a MAC, such as MAC 223 or MAC 222. For example, FIG. 4B illustrates two MAC CEs inserted into a MAC PDU. A MAC CE may be inserted at the beginning of the MAC PDU for downlink transmission (as shown in FIG. 4B) and at the end of the MAC PDU for uplink transmission. MAC CEs may be used for in-band control signaling. Examples of MAC CEs include scheduling-related MAC CEs such as buffer status reports and power headroom reports, enable / disable MAC CEs such as those for PDCP duplicate detection enable / disable, channel state information (CSI) reports, sounding reference signal (SRS) transmissions, and pre-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 of a format similar to that described for the MAC SDU and may be identified with a reserved value in the LCID field, which indicates the type of control information included in the MAC CE.

[0046] Before describing the NR control plane protocol stack, we first describe logical, transport, and physical channels and the mapping between channel types. One or more channels may be used to perform functions related to the NR control plane protocol stack, as described below.

[0047] 5A and 5B show the mapping between logical channels, transport channels, and physical channels for the downlink and uplink, respectively. Information is passed through channels between the RLC, MAC, and PHY of the NR protocol stack. Logical channels may be used between the RLC and MAC and may be classified as control channels, which carry control and configuration information in the NR control plane, or as traffic channels, which carry data in the NR user plane. Logical channels may be classified as dedicated logical channels, which are dedicated to a specific UE, or as common logical channels, which can be used by more than one UE. Logical channels may also be defined by the type of information they carry. The set of logical channels defined by NR includes, for example, a paging control channel (PCCH) for displaying paging messages used to page UEs whose location is unknown to the network at the cell level; a Broadcast Control Channel (BCCH) for conveying system information messages in the form of a Master Information Block (MIB) and several System Information Blocks (SIBs), which can be used by UEs to obtain information about how the cell is configured and how to operate within the cell; - a Common Control Channel (CCCH) for carrying control messages along with random access; - a dedicated control channel (DCCH) for carrying control messages to and from a specific UE for configuring the UE; - Dedicated Traffic Channel (DTCH) for carrying user data to and from a specific UE.

[0048] 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: a paging channel (PCH) for carrying paging messages originating from the PCCH; a Broadcast Channel (BCH) for carrying the MIB from the BCCH; A downlink shared channel (DL-SCH) for carrying downlink data and signaling messages, including SIBs from the BCCH; an uplink shared channel (UL-SCH) for carrying uplink data and signaling messages; A Random Access Channel (RACH) that allows a UE to contact the network without prior scheduling.

[0049] 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 information for one or more transport channels. The PHY may generate control information to support the lower level operation of the PHY and provide 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 may include, for example: a physical broadcast channel (PBCH) for carrying the MIB from the BCH; a Physical Downlink Shared Channel (PDSCH) for carrying downlink data and signaling messages from the DL-SCH and paging messages from the PCH; 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; A Physical Uplink Shared Channel (PUSCH) for carrying uplink data and signaling messages from the UL-SCH and, in some cases, uplink control information (UCI), as described below; A physical uplink control channel (PUCCH) for carrying UCI, which may include a HARQ acknowledgement, a channel quality indicator (CQI), a precoding matrix indicator (PMI), a rank indicator (RI), and a scheduling request (SR); - A Physical Random Access Channel (PRACH) for random access.

[0050] Similar to the physical control channel, the physical layer generates physical signals to support the low-level operations of the physical layer. As shown in Figures 5A and 5B, the physical layer signals defined by NR include the Primary Synchronization Signal (PSS), the Secondary Synchronization Signal (SSS), the Channel State Information Reference Signal (CSI-RS), the Demodulation Reference Signal (DMRS), the Sounding Reference Signal (SRS), and the Phase Tracking Reference Signal (PT-RS). These physical layer signals are described in more detail below.

[0051] 2B shows an example of an NR control plane protocol stack. 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 PHY 211 and 221, MAC 212 and 222, RLC 213 and 223, and PDCP 214 and 224. Instead of having SDAP 215 and 225 at the top of the stack like the NR user plane protocol stack, the NR control plane stack has radio resource control (RRC) 216 and 226 and NAS protocols 217 and 237 at the top of the NR control plane protocol stack.

[0052] The NAS protocols 217 and 237 may provide control plane functions 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 functions between the UE 210 and the AMF 230 via signaling messages called NAS messages. There is no direct path between the UE 210 and the AMF 230 over which NAS messages can be transported. NAS messages can be transported using the ASs of the Uu and NG interfaces. The NAS protocols 217 and 237 may provide control plane functions such as authentication, security, connection setup, mobility management, and session management.

[0053] The RRCs 216 and 226 may provide a control plane function 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 a control plane function between the UE 210 and the gNB 220 via signaling messages referred to as RRC messages. The RRC messages may be transmitted between the UE 210 and the RAN using signaling radio bearers and the same / similar PDCP, RLC, MAC, and PHY protocol layers. The MAC may multiplex control plane and user plane data within the same transport block (TB). The RRCs 216 and 226 may provide control plane functions such as broadcasting system information related to the AS and NAS, paging initiated by the CN or 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 and data radio bearers, mobility functions, QoS management functions, UE measurement reporting and reporting control, radio link failure (RLF) detection and recovery, and / or NAS message forwarding. As part of establishing an RRC connection, the RRCs 216 and 226 may establish an RRC context, which may involve setting parameters for communications between the UE 210 and the RAN.

[0054] 6 is an example diagram illustrating RRC state transitions for a UE. The UE may be the same as or similar to the wireless device 106 shown in FIG. 1A, the UE 210 shown in FIG. 2A and FIG. 2B, or any other wireless device described in this disclosure. As shown in FIG. 6, the UE may be in at least one of three RRC states: RRC connected 602 (e.g., RRC_CONNECTED), RRC idle 604 (e.g., RRC_IDLE), and RRC inactive 606 (e.g., RRC_INACTIVE).

[0055] In the RRC connection 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 base stations included in the RAN 104 shown in FIG. 1A, one of the gNB 160 or ng-eNB 162 shown in FIG. 1B, the gNB 220 shown in FIGS. 2A and 2B, or any other base station described in this disclosure. The base station to which the UE is connected may have the UE's RRC context. The RRC context, referred to as the UE context, may include 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., associated with data radio bearers, signaling radio bearers, logical channels, QoS flows, and / or PDU sessions), security information, and / or PHY, MAC, RLC, PDCP, and / or SDAP layer configuration information. In the RRC connection 602, the UE's mobility may be managed by the RAN (e.g., the RAN 104 or the NG-RAN 154). The UE may measure signal levels (e.g., reference signal levels) from the 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 via a Connection Release procedure 608 or to RRC Inactive 606 via a Connection Deactivation procedure 610.

[0056] 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 a base station. During RRC idle 604, the UE may be in a sleep state most of the time (e.g., to conserve battery power). The UE may wake up periodically (e.g., once per discontinuous reception cycle) to monitor for paging messages from the RAN. UE mobility 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 via a connection establishment procedure 612, which may involve a random access procedure as discussed in more detail below.

[0057] In RRC Inactive 606, the previously established RRC context is maintained in the UE and the base station. This reduces signaling overhead and allows for a faster transition to RRC Connected 602 compared to transitioning from RRC Idle 604 to RRC Connected 602. In RRC Inactive 606, the UE is in a sleep state and UE mobility may be managed by the UE through cell reselection. The RRC state may transition from RRC Inactive 606 to RRC Connected 602 by a Connection Resume procedure 614 or to RRC Idle 604 via a Connection Release procedure 616 that is the same as or similar to the Connection Release procedure 608.

[0058] 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 notify the UE of events via paging messages without broadcasting the paging messages throughout the entire mobile communication 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 paging messages can be broadcast on cells of the cell group in which the UE currently resides instead of the entire mobile communication network. The mobility management mechanisms in RRC Idle 604 and RRC Inactive 606 track the UE on a cell group level. They may do so using different granularity of grouping. For example, there may be three levels of granularity of cell grouping: individual cells, cells within a RAN area identified by a RAN Area Identifier (RAI), and cells within a group of RAN areas called a Tracking Area and identified by a Tracking Area Identifier (TAI).

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

[0060] The RAN area may be used to track the UE at the RAN level. For a UE in the RRC inactive 606 state, the UE may be assigned a RAN notification area. The RAN notification area may include one or more cell identities, a list of RAIs, or a list of TAIs. In one example, a base station may belong to one or more RAN notification areas. In one example, a cell may belong to one or more RAN notification areas. If the UE moves, through cell reselection, to a cell that is 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 RAN notification area of ​​the UE.

[0061] A base station that stores the RRC context for a UE, or the last serving base station for the UE, may be referred to as an anchor base station. The anchor base station may maintain the RRC context for the UE at least while the UE remains in the RAN notification area of ​​the anchor base station and / or while the UE remains in RRC inactive 606.

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

[0063] In NR, physical signals and physical channels (FIGS. 5A and 5B) may be mapped onto orthogonal frequency division multiplexing (OFDM) symbols. OFDM is a multicarrier communication scheme that transmits data on 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, which are divided into F parallel symbol streams. The F parallel symbol streams may be treated as if they were in the frequency domain and used as input to an inverse fast Fourier transform (IFFT) block, which converts them to the time domain. The IFFT block may take F source symbols, one from each of the F parallel symbol streams at a time, and use each source symbol to modulate the amplitude and phase of one of the F sinusoidal basis functions corresponding to the F orthogonal subcarriers. The output of the IFFT block may be F time-domain samples representing a sum of the F orthogonal subcarriers. The F time-domain samples may form a single OFDM symbol. After some processing (e.g., adding a cyclic prefix) and upconversion, the OFDM symbols provided by the IFFT block can be transmitted over the air interface at a carrier frequency. The F parallel symbol streams can be mixed using an FFT block before being processed by the IFFT block. This processing generates discrete Fourier transform (DFT) pre-coded OFDM symbols, which can be used by UEs in the uplink to reduce the peak-to-average power ratio (PAPR). Inverse processing can be performed on the OFDM symbols at the receiver using an FFT block to recover the data mapped to the source symbols.

[0064] Figure 7 shows an example configuration of an NR frame in which OFDM symbols are grouped. NR frames may be identified by a system frame number (SFN). The SFN may repeat at a period of 1024 frames. As shown, one NR frame may be 10 milliseconds (ms) in duration and may include 10 subframes, each 1 ms in duration. The subframes may be divided into slots, each including, for example, 14 OFDM symbols per slot.

[0065] The duration of a slot may depend on the numerology used for the OFDM symbol of the slot. NR supports flexible numerology to accommodate different cell deployments (e.g., cells with carrier frequencies less than 1 GHz up to cells with carrier frequencies in the mm-wave range). Numerologies may be defined in terms of subcarrier spacing and cyclic prefix duration. For numerology in NR, subcarrier spacing may be scaled up by a power of two from the baseline subcarrier spacing of 15 kHz, and cyclic prefix duration may be scaled down by a power of two from the baseline cyclic prefix duration of 4.7 μs. For example, NR defines numerologies with the following subcarrier spacing / cyclic prefix duration combinations: 15 kHz / 4.7 μs, 30 kHz / 2.3 μs, 60 kHz / 1.2 μs, 120 kHz / 0.59 μs, and 240 kHz / 0.29 μs.

[0066] A slot may have a fixed number of OFDM symbols (e.g., 14 OFDM symbols). Numerologies with higher subcarrier spacing have shorter slot durations and correspondingly more slots per subframe. Figure 7 illustrates this numerology-dependent slot duration and slot-per-subframe transmission structure (for ease of illustration, a numerology with 240 kHz subcarrier spacing is not shown in Figure 7). While a subframe in NR may be used as a numerology-independent time reference, a slot may be used as the unit by which uplink and downlink transmissions are scheduled. To support low latency, scheduling in NR is decoupled from the slot duration and can begin with any OFDM symbol and continue for as many symbols as necessary for transmission. These partial slot transmissions may be referred to as minislot or subslot transmissions.

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

[0068] Figure 8 shows a single numerology used across the entire bandwidth of an NR carrier. In other example configurations, multiple numerologies may be supported on the same carrier.

[0069] NR may support a wide range of carrier bandwidths (e.g., up to 400 MHz with 120 kHz subcarrier spacing). Not all UEs may be able to receive the entire carrier bandwidth (e.g., due to hardware limitations). Also, receiving the entire carrier bandwidth may be prohibitive from a UE power consumption perspective. In one example, to reduce power consumption and / or for other purposes, the UE may adapt the size of its reception bandwidth based on the amount of traffic the UE intends to receive. This is referred to as bandwidth adaptation.

[0070] NR defines bandwidth portions (BWPs) to support UEs that cannot receive the entire carrier bandwidth and support bandwidth adaptation. In one example, a BWP may be defined by a subset of contiguous RBs on a carrier. A UE may be configured (e.g., via the 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 BWPs configured for a serving cell may be active. These one or more BWPs may be referred to as the 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 on the uplink carrier and one or more second active BWPs on the secondary uplink carrier.

[0071] For unpaired spectrum, 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 the downlink BWP index of the downlink BWP and the uplink BWP index of the uplink BWP are the same. For unpaired spectrum, the UE may expect the center frequency of the downlink BWP to be the same as the center frequency of the uplink BWP.

[0072] For a downlink BWP within a set of configured downlink BWPs on a primary cell (PCell), the base station may configure the 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 domain where the UE can find control information. The search space may be a UE-specific search space or a common search space (potentially usable by multiple UEs). For example, the base station may configure the UE with a common search space on the PCell or on a primary secondary cell (PSCell) for an active downlink BWP.

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

[0074] One or more BWP indicator fields may be provided in downlink control information (DCI). The value of the BWP indicator field may indicate which BWP of 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.

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

[0076] The base station may configure the UE with a BWP inactivity timer value for the PCell. The UE may start or restart the 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 the default downlink BWP for paired spectrum operation, or (b) when the UE detects a DCI indicating an active downlink BWP or an active uplink BWP other than the default downlink BWP or uplink BWP for unpaired spectrum operation. If the UE does not detect a DCI for a certain period of time (e.g., 1 ms or 0.5 ms), the UE may run the BWP inactivity timer towards expiration (e.g., increasing it from zero to the BWP inactivity timer value or decreasing it 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.

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

[0078] Downlink and uplink BWP switching (BWP switching refers to switching from a currently active BWP to a non-currently active BWP) can be performed independently in paired spectrum. In unpaired spectrum, downlink and uplink BWP switching can be performed simultaneously. Switching between configured BWPs can occur based on RRC signaling, DCI, expiration of the BWP inactivity timer, and / or initiation of random access.

[0079] FIG. 9 shows an example of bandwidth adaptation using three configured BWPs for an NR carrier. A UE configured with three BWPs may switch from one BWP to another at a switching point. In the example shown in FIG. 9, the BWPs include BWP 902 with a 40 MHz bandwidth and 15 kHz subcarrier spacing, BWP 904 with a 10 MHz bandwidth and 15 kHz subcarrier spacing, and BWP 906 with a 20 MHz bandwidth and 60 kHz subcarrier spacing. BWP 902 may be the initial active BWP, and BWP 904 may be the default BWP. A UE may switch between BWPs at a switching point. In the example of FIG. 9, the UE may switch from BWP 902 to BWP 904 at switching point 908. Switching at switching point 908 may occur for any suitable reason, such as in response to expiration 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 be switched from the active BWP 904 to BWP 906 at switching point 910 in response to receiving a DCI indicating BWP 906 as the active BWP. The UE may be switched from the active BWP 906 to BWP 904 at switching point 912 in response to expiration of a BWP inactivity timer and / or in response to receiving a DCI indicating BWP 904 as the active BWP. The UE may be switched from the active BWP 904 to BWP 902 at switching point 914 in response to receiving a DCI indicating BWP 902 as the active BWP.

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

[0081] To provide greater data rates, carrier aggregation (CA) can be used to aggregate two or more carriers and transmit simultaneously to the same UE. The aggregated carriers in CA can be referred to as component carriers (CCs). When using CA, there are many serving cells for the UE and one cell for the CC. A CC can have three configurations in the frequency domain:

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

[0083] In one 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 of a UE using CA may have a downlink CC. For FDD, one or more uplink CCs may optionally be configured for the serving cell. The ability to aggregate more downlink carriers than uplink carriers may be useful, for example, when a UE has more data traffic on the downlink than on the uplink.

[0084] When CA is used, one of the aggregation cells of the UE may be referred to as a Primary Cell (PCell). The PCell may be a serving cell to which the UE initially connects during RRC connection establishment, re-establishment, and / or handover. The PCell may provide the UE with NAS mobility information and security inputs. A UE may have different PCells. In the downlink, a carrier corresponding to a PCell may be referred to as a Downlink Primary CC (DL PCC). In the uplink, a carrier corresponding to a PCell may be referred to as an Uplink Primary CC (UL PCC). Other aggregation cells of the UE may be referred to as Secondary Cells (SCells). In one example, an SCell may be configured after a PCell is configured for the UE. For example, the SCell may be configured via an RRC connection reconfiguration procedure. In the downlink, a carrier corresponding to a SCell may be referred to as a Downlink Secondary CC (DL SCC). In the uplink, a carrier corresponding to a SCell may be referred to as an Uplink Secondary CC (UL SCC).

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

[0086] 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, known as self-scheduling. DCI for a cell may be transmitted on another cell, known as cross-carrier scheduling. Uplink control information for aggregation cells (e.g., HARQ acknowledgments and channel state feedback such as CQI, PMI, and / or RI) may be transmitted on the PUCCH of the PCell. A large number of aggregated downlink CCs may overload the PUCCH of the PCell. A cell may be divided into multiple PUCCH groups.

[0087] 10B shows an example of how aggregation cells may be configured into one or more PUCCH groups. PUCCH group 1010 and PUCCH group 1050 may each include one or more downlink CCs. In the example of FIG. 10B, PUCCH group 1010 includes three downlink CCs: PCell 1011, SCell 1012, and SCell 1013. PUCCH group 1050 includes three downlink CCs: PCell 1051, SCell 1052, and SCell 1053. One or more uplink CCs may be configured as PCell 1021, SCell 1022, and SCell 1023. One or more other uplink CCs may be configured as Primary SCells (PSCells) 1061, SCell 1062, and SCell 1063. Uplink control information (UCI) associated with downlink CCs of PUCCH group 1010, denoted as UCI 1031, UCI 1032, and UCI 1033, may be transmitted on the uplink of PCell 1021. Uplink control information (UCI) associated with downlink CCs of PUCCH group 1050, denoted as UCI 1071, UCI 1072, and UCI 1073, may be transmitted on the uplink of PSCell 1061. In one example, if the aggregation cell depicted in FIG. 10B were not divided into PUCCH group 1010 and PUCCH group 1050, a single uplink PCell and PCell for transmitting UCI associated with downlink CCs may be overloaded. By dividing the transmission of UCI between PCell 1021 and PSCell 1061, the overload may be prevented.

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

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

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

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

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

[0093] The location of the SS / PBCH block in the time and frequency domain may be unknown to the UE (e.g., when the UE is searching for a cell). To find and select a cell, the UE may monitor the carrier for a 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 milliseconds), the UE may search for a PSS at a different frequency location within the carrier as indicated by the synchronization raster. If the PSS is found at a location in the time and frequency domain, the UE may determine the location of the SSS and PBCH, respectively, based on the known structure of the SS / PBCH block. The SS / PBCH block may be a cell-defined SS block (CD-SSB). In one example, the primary cell may be associated with the CD-SSB. The CD-SSB may be located on the synchronization raster. In one example, cell selection / search and / or reselection may be based on the CD-SSB.

[0094] 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 PSS and SSS sequences, respectively. The UE may determine the 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 was transmitted according to a transmission pattern, where the SS / PBCH block in the transmission pattern is a known distance from the frame boundary.

[0095] The PBCH may use 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 the cell's current system frame number (SFN) and / or 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 one or more parameters to the UE. The MIB may be used by the UE to find the remaining minimum system information (RMSI) associated with the cell. The RMSI may include system information block type 1 (SIB1). SIB1 may include information necessary for the UE to access the cell. The UE may use one or more parameters of the MIB to monitor the PDCCH, which may be used to schedule the PDSCH. The PDSCH may include SIB1. SIB1 may be decoded using the parameters provided in the MIB. The PBCH may indicate the absence of SIB1. Based on the PBCH indicating that SIB1 is not present, the UE may point to a frequency, and the UE may search for an SS / PBCH block on the frequency to which the UE is pointed.

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

[0097] SS / PBCH blocks (e.g., blocks within a half frame) may be transmitted in spatial directions (e.g., using different beams across the coverage area of ​​a cell). In one 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.

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

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

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

[0101] A base station may configure a 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 the timing and / or periodicity of CSI reports. For aperiodic CSI reporting, the base station may request a CSI report. For example, the base station may instruct the UE to measure configured CSI-RS resources and provide a CSI report regarding the measurements. For semi-persistent CSI reporting, the base station may configure the UE to periodically transmit and selectively activate or deactivate periodic reports. The base station may configure the UE with a CSI-RS resource set and CSI report using RRC signaling.

[0102] The CSI-RS configuration may include, for example, one or more parameters indicating up to 32 antenna ports. The UE may be configured to use the same OFDM symbol for the downlink CSI-RS and control resource set (CORESET) if the downlink CSI-RS and CORESET are spatially QCL'd and resource elements associated with the downlink CSI-RS are outside the physical resource block (PRB) configured for CORESET. The UE may be configured to use the same OFDM symbol for the downlink CSI-RS and SS / PBCH block if the downlink CSI-RS and SS / PBCH block are spatially QCL'd and resource elements associated with the downlink CSI-RS are outside the PRB configured for the SS / PBCH block.

[0103] The downlink DMRS 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 frontloaded DMRS pattern. The frontloaded DMRS may be mapped to one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). The base station may semi-statically configure the UE with the number (e.g., maximum number) of frontloaded DMRS symbols for the PDSCH. The DMRS configuration may support one or more DMRS ports. For example, in the case of single-user MIMO, the DMRS configuration may support up to eight orthogonal downlink DMRS ports per UE. In the case of multi-user MIMO, the DMRS configuration may support up to four orthogonal downlink DMRS ports per UE. The wireless network can support a common downlink and uplink DMRS structure (e.g., at least for CP-OFDM). The DMRS position, DMRS pattern, and / or scrambling sequence can be the same or different. The base station can transmit the downlink DMRS and corresponding PDSCH using the same precoding matrix. The UE can use one or more downlink DMRSs for coherent demodulation / channel estimation of the PDSCH.

[0104] In one example, a transmitter (e.g., a base station) may use a precoder matrix for a portion 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 differ based on the first bandwidth being different from the second bandwidth. The UE may assume that the same precoding matrix is ​​used across a set of PRBs. The set of PRBs may be denoted as a precoding resource block group (PRG).

[0105] The PDSCH may include one or more layers. The UE may assume that at least one symbol with a DMRS is present on one or more layers of the PDSCH. Higher layers may configure up to three DMRSs for the PDSCH.

[0106] The downlink PT-RS may be transmitted by the base station and may be used by the UE for phase noise compensation. Whether the downlink PT-RS is present depends on the RRC configuration. The presence and / or pattern of the downlink PT-RS may be configured on a UE-specific basis using a combination of RRC signaling and / or an association with one or more parameters used for other purposes (e.g., modulation and coding scheme (MCS)) that may be indicated by DCI. If configured, the dynamic presence of the downlink PT-RS may be associated with one or more DCI parameters, including at least the MCS. The NR network may support multiple PT-RS densities defined in the time and / or frequency domain. The frequency domain density, if present, may be associated with at least one configuration of the scheduled bandwidth. The UE may assume the same precoding for the DMRS port and the PT-RS port. The number of PT-RS ports may be less than the number of DMRS ports within the scheduled resource. The downlink PT-RS may be limited to the UE's scheduled time / frequency duration. The downlink PT-RS may be transmitted over symbols to facilitate phase tracking at the receiver.

[0107] A 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 the uplink DMRS on a PUSCH and / or a PUCCH. The uplink DMRS may span a frequency range similar to the frequency range 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 frontloaded DMRS pattern. The frontloaded DMRS may be mapped to one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). One or more uplink DMRS may be configured to transmit on one or more symbols of the PUSCH and / or the PUCCH. The base station may semi-statically configure the UE with the number (e.g., maximum number) of frontloaded DMRS symbols for the PUSCH and / or the PUCCH that the UE may use to schedule single-symbol DMRS and / or dual-symbol DMRS. An NR network may support a common DMRS structure for the downlink and uplink (e.g., for cyclic prefix orthogonal frequency division multiplexing (CP-OFDM)), where the DMRS position, DMRS pattern, and / or DMRS scrambling sequence may be the same or different.

[0108] The PUSCH may include one or more layers, and the UE may transmit at least one symbol having a DMRS present on one or more layers of the PUSCH. In one example, higher layers may configure up to three DMRSs for the PUSCH.

[0109] The uplink PT-RS (which may be used by the base station for phase tracking and / or phase noise compensation) may be present or absent depending on the UE's RRC configuration. The presence and / or pattern of the uplink PT-RS may be configured on a UE-specific basis by a combination of one or more parameters used for other purposes (e.g., Modulation and Coding Scheme (MCS)), which may be indicated by RRC signaling and / or DCI. If configured, the dynamic presence of the uplink PT-RS may be associated with one or more DCI parameters, including at least the MCS. The wireless network may support multiple uplink PT-RS densities defined in the time / frequency domain. The frequency domain density, if present, may be associated with at least one configuration of the scheduled bandwidth. The UE may assume the same precoding for the DMRS port and the PT-RS port. The number of PT-RS ports may be less than the number of DMRS ports within the scheduled resources. For example, the uplink PT-RS may be limited to the UE's scheduled time / frequency duration.

[0110] The SRS may be transmitted by the UE to a base station for channel condition estimation to support uplink channel-dependent scheduling and / or link adaptation. The SRS transmitted by the UE may enable the base station to estimate uplink channel conditions at one or more frequencies. The base station scheduler may use the estimated uplink channel conditions to allocate one or more resource blocks for 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. SRS resource set applicability may be configured by higher layer (e.g., RRC) parameters. For example, if higher layer parameters indicate beam management, SRS resources in one or more SRS resource sets (e.g., having the same / similar time-domain behavior, periodicity, aperiodicity, and / or similar) may be transmitted instantaneously (e.g., simultaneously). The UE may transmit one or more SRS resources in an SRS resource set. An NR network may support aperiodic, periodic, and / or semi-persistent SRS transmission. A UE may transmit SRS resources based on one or more trigger types, which may include higher layer signaling (e.g., RRC) and / or one or more DCI formats. In one example, at least one DCI format may be used by a UE to select at least one of one or more configured SRS resource sets. SRS trigger type 0 may refer to an SRS triggered based on higher layer signaling. SRS trigger type 1 may refer to an SRS triggered based on one or more DCI formats. In one example, if a PUSCH and an SRS are transmitted in the same slot, the UE may be configured to transmit an SRS after the transmission of the PUSCH and the corresponding uplink DMRS.

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

[0112] Antenna ports are defined such that the channel through which a symbol on an antenna port is carried can be inferred from the channel through which another symbol on the same antenna port is carried. When a first symbol and a second symbol are transmitted on the same antenna port, a receiver can infer the channel (e.g., fade gain, multipath delay, and / or the like) through which a second symbol on the antenna port is carried from the channel through which the first symbol on the antenna port is carried. A first antenna port and a second antenna port may be referred to as quasi-colocated (QCL) if one or more large-scale characteristics of the channel through which the first symbol on the first antenna port is carried can be inferred from the channel through which the second symbol on the second antenna port is carried. The one or more large-scale characteristics may include at least one of delay spread, Doppler spread, Doppler shift, average gain, average delay, and / or spatial receive (Rx) parameters.

[0113] In a channel using beamforming, beam management is required. Beam management may include 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 beamforming reference signals. A UE may perform downlink beam measurement based on a downlink reference signal (e.g., a channel state information reference signal (CSI-RS)) and generate a beam measurement report. A UE may perform a downlink beam measurement procedure after an RRC connection is set up with a base station.

[0114] Figure 11B shows an example of a channel state information reference signal (CSI-RS) mapped to the time and frequency domain. The squares shown in Figure 11B may span resource blocks (RBs) within the bandwidth of a cell. A base station may transmit one or more RRC messages containing CSI-RS resource configuration parameters indicating one or more CSI-RS. One or more of the following parameters may be set by higher layer signaling (e.g., RRC and / or MAC signaling) for the CSI-RS resource configuration: CSI-RS resource configuration identity, number of CSI-RS ports, CSI-RS configuration (e.g., symbol and resource element (RE) location within a subframe), CSI-RS subframe configuration (e.g., subframe position, offset, and radio frame periodicity), CSI-RS power parameters, CSI-RS sequence parameters, code division multiplexing (CDM) type parameters, frequency density, transmit comb, quasi-colocation (QCL) parameters (e.g., QCL-scramblingidentity, crs-portscount, mbsfn-subframeconfiglist, csi-rs-configZPid, qcl-csi-rs-configNZPid), and / or other radio resource parameters.

[0115] The three beams shown in FIG. 11B may be configured for a UE with a UE-specific configuration. Three beams are shown in FIG. 11B (Beam #1, Beam #2, and Beam #3), and more or fewer beams may be configured. Beam #1 may be assigned with CSI-RS 1101, which may be transmitted on one or more subcarriers in the RB of the first symbol. Beam #2 may be assigned with CSI-RS 1102, which may be transmitted on one or more subcarriers in the RB of the second symbol. Beam #3 may be assigned with CSI-RS 1103, which may be transmitted on one or more subcarriers in the RB of the third symbol. By using frequency division multiplexing (FDM), the base station may transmit another CSI-RS associated with another UE's beam using other subcarriers in the same RB (e.g., those not used to transmit CSI-RS 1101). By using time domain multiplexing (TDM), the beam used for a UE may be configured so that the UE's beam uses symbols from the other UE's beam.

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

[0117] In a beam management procedure, a UE may evaluate (e.g., measure) the channel quality of one or more beam pair links, including a transmit beam transmitted by a base station and a receive beam received by the UE. Based on the evaluation, the UE may transmit a beam measurement report indicating one or more beam pair quality parameters, including, for example, one or more beam identifications (e.g., beam index, reference signal index, or the like), RSRP, precoding matrix indicator (PMI), channel quality indicator (CQI), and / or rank indicator (RI).

[0118] FIG. 12A shows three example downlink beam management procedures, P1, P2, and P3. Procedure P1 may enable UE measurements at the transmit (Tx) beams of a transmit receive point (TRP) (or multiple TRPs) to support selection of one or more base station Tx beams and / or UE Rx beams (shown as ellipses in the top and bottom rows of P1, respectively). Beamforming at a TRP may include a Tx beam sweep of a set of beams (shown as an ellipse rotating counterclockwise as indicated by the dashed arrows in the top rows of P1 and P2). Beamforming at a UE may include an Rx beam sweep of a set of beams (shown as an ellipse rotating clockwise as indicated by the dashed arrows in the bottom rows of P1 and P3). Procedure P2 may be used to enable UE measurements at the Tx beams of a TRP (shown as an ellipse rotating counterclockwise as indicated by the dashed arrows in the top row of P2). The UE and / or base station may perform procedure P2 using a smaller set of beams than used in procedure P1, or using narrower beams than 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 the Rx beam at the UE.

[0119] FIG. 12B shows three example uplink beam management procedures, U1, U2, and U3. Procedure U1 may be used, for example, to enable the base station to perform measurements on the UE's Tx beams to support the selection of one or more UE Tx beams and / or base station Rx beams (shown as ellipses in the top and bottom rows of U1, respectively). Beamforming at the UE may include, for example, a Tx beam sweep from a set of beams (shown as ellipses rotating clockwise as indicated by dashed arrows in the bottom rows of U1 and U3). Beamforming at the base station may include, for example, an Rx beam sweep from a set of beams (shown as ellipses rotating counterclockwise as indicated by dashed arrows in the top rows of U1 and U2). 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 base station may perform procedure U2 using a smaller set of beams than used in procedure P1 or using narrower beams than 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.

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

[0121] A UE may measure the quality of a beam pair link using one or more reference signals (RSs), including one or more SS / PBCH blocks, one or more CSI-RS resources, and / or one or more demodulation reference signals (DMRSs). The 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 the 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 one or more DMRSs of a channel may be QCLed when the channel characteristics (e.g., Doppler shift, Doppler spread, mean delay, delay spread, spatial Rx parameters, fading, and / or the like) from a transmission to the UE over the RS resource are similar or identical to the channel characteristics from a transmission to the UE over the channel.

[0122] The network (e.g., a gNB and / or ng-eNB of the network) and / or the UE may initiate a random access procedure. A UE in an RRC_IDLE state and / or a UE in an RRC_INACTIVE state may initiate a random access procedure to request connection setup to the network. A UE may initiate a random access procedure from an RRC_CONNECTED state. A UE may initiate a random access procedure to request uplink resources (e.g., for uplink transmission of SR when there are no available PUCCH resources) and / or to acquire uplink timing (e.g., when the uplink synchronization state is not synchronized). A UE may initiate a random access procedure to request one or more system information blocks (SIBs) (e.g., SIB2, SIB3, and / or other system information such as similar). A UE may initiate a random access procedure for a beam failure recovery request. The network may initiate a random access procedure to establish time alignment for handover and / or for SCell addition.

[0123] Figure 13A shows a four-step contention-based random access procedure. Before the procedure begins, the base station may transmit a configuration message 1310 to the UE. Figure 13A includes the transmission of four messages: Msg1 1311, Msg2 1312, Msg3 1313, and Msg4 1314. Msg1 1311 may include and / or be referred to as a preamble (or random access preamble). Msg2 1312 may include and / or be referred to as a random access response (RAR).

[0124] 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 include at least one of general parameters (e.g., RACH-configGeneral), cell-specific parameters (e.g., RACH-ConfigCommon), and / or dedicated parameters (e.g., RACH-configDedicated) for one or more random access procedures. 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 the UE in RRC_CONNECTED and / or RRC_INACTIVE states). The UE may determine time-frequency resources and / or uplink transmit power for transmission of Msg1 1311 and / or Msg3 1313 based on the one or more RACH parameters. Based on one or more RACH parameters, the UE may determine the receive timing and downlink channel for receiving Msg2 1312 and Msg4 1314.

[0125] The one or more RACH parameters provided in the configuration message 1310 may indicate one or more physical RACH (PRACH) opportunities available for transmission of Msg1 1311. The one or more PRACH opportunities may be predefined. The one or more RACH parameters may indicate one or more available sets of one or more PRACH opportunities (e.g., prach-ConfigIndex). The one or more RACH parameters may indicate an association between (a) one or more PRACH opportunities 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-RS. For example, the one or more RACH parameters may indicate the number of SS / PBCH blocks mapped to the PRACH opportunity and / or the number of preambles mapped to the SS / PBCH block.

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

[0127] Msg1 1311 may include one or more preamble transmissions (e.g., a preamble transmission and one or more preamble retransmissions). The RRC message may be used to configure one or more preamble groups (e.g., Group A and / or Group B). A preamble group may include one or more preambles. The UE may determine the preamble group based on a path loss measurement and / or the size of Msg3 1313. The UE may measure the RSRP of one or more reference signals (e.g., SSB and / or CSI-RS) 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 the selected preamble group, for example, if an association between one or more preambles and at least one reference signal is configured by the RRC message.

[0128] The UE may determine the preamble based on one or more RACH parameters provided in the configuration message 1310. For example, the UE may determine the preamble based on a path loss measurement, an RSRP measurement, and / or the size of Msg3 1313. As another example, the one or more RACH parameters may indicate one or more thresholds for determining a preamble format, a maximum number of preamble transmissions, and / or one or more preamble groups (e.g., Group A and Group B). The base station may configure the UE with an association between one or more preambles and one or more reference signals (e.g., SSB and / or CSI-RS) using the one or more RACH parameters. If an association is configured, the UE may determine a preamble to include in Msg1 1311 based on the association. Msg1 1311 may be transmitted to the base station via one or more PRACH opportunities. The UE may use one or more reference signals (e.g., SSB and / or CSI-RS) for preamble selection and PRACH opportunity determination. One or more RACH parameters (eg, ra-ssb-OccasionMskIndex and / or ra-OccasionList) may indicate an association between a PRACH occasion and one or more reference signals.

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

[0130] The UE receives Msg2 1312, which may include an RAR. In some scenarios, Msg2 1312 may include multiple RARs corresponding to multiple UEs. Msg2 1312 may be received after or in response to the transmission of Msg1 1311. Msg2 1312 may be scheduled on the DL-SCH and indicated on the PDCCH using the Random Access RNTI (RA-RNTI). Msg2 1312 may indicate that Msg1 1311 has been received by the base station. Msg2 1312 may include a time alignment command that the UE may use to adjust its transmission timing, a scheduling grant for transmission of Msg3 1313, and / or a Temporary Cell RNTI (TC-RNTI). After transmitting the preamble, the UE may begin a time window (e.g., ra-ResponseWindow) in which it monitors the PDCCH for Msg2 1312. The UE may determine when to start the time window based on the PRACH opportunity the UE uses to transmit the preamble. For example, the UE may start the time window one or more symbols after the last symbol of the preamble (e.g., on the first PDCCH opportunity from the end of the preamble transmission). The one or more symbols may be determined based on numerology. The PDCCH may be within a common search space configured by an RRC message (e.g., a Type1-PDCCH common search space). The UE may identify the RAR based on a Radio Network Temporary Identifier (RNTI). The RNTI may be used in response to one or more events that initiate a random access procedure. The UE may use a Random Access RNTI (RA-RNTI). The RA-RNTI may be associated with the PRACH opportunity on which the UE transmits the 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 an UL carrier indicator of the PRACH opportunity. Examples of RA-RNTI may be as follows: RA-RNTI=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id where s_id may be the index of the first OFDM symbol of the PRACH opportunity (e.g., 0≦s_id<14), t_id may be the index of the first slot of the PRACH opportunity within the system frame (e.g., 0≦t_id<80), f_id may be the index of the PRACH opportunity in the frequency domain (e.g., 0≦f_id<8), and ul_carrier_id may be the UL carrier used for preamble transmission (e.g., 0 for NUL carrier and 1 for SUL carrier). The UE may transmit Msg3 1313 in response to successful reception of Msg2 1312 (e.g., using the resources identified in Msg2 1312). Msg3 1313 may be used for contention resolution, for example, in the contention-based random access procedure shown in FIG. 13A. In some scenarios, multiple UEs may transmit the same preamble to the base station, and the base station may provide the UE with a corresponding RAR. If multiple UEs interpret the RAR as corresponding to themselves, a discrepancy may occur. Contention resolution (e.g., use of Msg3 1313 and Msg4 1314) may be used to increase the likelihood that a UE will not mistakenly use the identity of another UE. To perform contention resolution, the UE may include a device identifier (e.g., C-RNTI, if assigned, TC-RNTI included in Msg2 1312, and / or any other suitable identifier) ​​in Msg3 1313.

[0131] Msg4 1314 may be received after or in response to transmission of Msg3 1313. If a C-RNTI was included in Msg3 1313, the base station addresses 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 have completed successfully. If a TC-RNTI is included in Msg3 1313 (e.g., the UE is in RRC_IDLE state or is otherwise not connected to the base station), Msg4 1314 is received using the DL-SCH associated with the TC-RNTI. If the MAC PDU is successfully decoded and matches the CCCH SDU sent (e.g., transmitted) in Msg3 1313 or otherwise includes the corresponding UE contention resolution identity MAC CE, the UE may determine that contention resolution was successful and / or the UE may determine that the random access procedure was completed successfully.

[0132] A UE may be configured with a complementary uplink (SUL) carrier and a normal uplink (NUL) carrier. Initial access (e.g., random access procedure) may be supported on the uplink carrier. For example, a base station may configure a UE with two separate RACH configurations, one for the SUL carrier and one for the NUL carrier. For random access in a cell configured with an SUL carrier, the network may indicate which carrier (NUL or SUL) to use. The UE may determine the SUL carrier, for example, if the measured quality of one or more reference signals is lower than a broadcast threshold. Uplink transmissions of the random access procedure (e.g., Msg1 1311 and / or Msg3 1313) can remain on the selected carrier. The UE may switch uplink carriers during the random access procedure (e.g., between Msg1 1311 and Msg3 1313) in one or more instances. For example, the UE may determine and / or switch the uplink carrier for Msg1 1311 and / or Msg3 1313 based on a channel clear assessment (eg, listen-before-talk).

[0133] Figure 13B shows a two-step contention-free random access procedure. Similar to the four-step contention-based random access procedure shown in Figure 13A, the base station may transmit a configuration message 1320 to the UE before the procedure begins. The configuration message 1320 may be similar in some respects to the configuration message 1310. Figure 13B includes the transmission of two messages, Msg1 1321 and Msg2 1322. Msg1 1321 and Msg2 1322 may be similar in some respects to Msg1 1311 and Msg2 1312, respectively, shown in Figure 13A. As can be seen from Figures 13A and 13B, the contention-free random access procedure may not include messages similar to Msg3 1313 and / or Msg4 1314.

[0134] 13B may be initiated for beam failure recovery, other SI requests, SCell addition, and / or handover. For example, the base station may indicate or assign to the UE the preamble to be used for Msg1 1321. The UE may receive an indication of the preamble (e.g., ra-PreambleIndex) from the base station via PDCCH and / or RRC.

[0135] After transmitting the preamble, the UE may start a time window (e.g., ra-ResponseWindow) in which it monitors the PDCCH for the RAR. In the case of a beam failure recovery request, the base station may configure the UE with a separate time window and / or separate PDCCH within the search space indicated by the RRC message (e.g., recoverySearchSpaceId). The UE may monitor for PDCCH transmissions addressed to the Cell RNTI (C-RNTI) over the search space. In the contention-free random access procedure shown in FIG. 13B, the UE may determine that the random access procedure has completed successfully after or in response to the transmission of Msg1 1321 and the reception of the corresponding Msg2 1322. The UE may determine that the random access procedure has completed successfully, for example, if the PDCCH transmission is addressed to the C-RNTI. The UE may determine that the random access procedure is successfully completed, for example, if the UE receives an RAR including a preamble identifier corresponding to a preamble transmitted by the UE and / or if the RAR includes a MAC sub-PDU including the preamble identifier. The UE may determine the response as an indication of a response acknowledgment to the SI request.

[0136] 13C shows another two-step random access procedure. Similar to the random access procedures shown in FIGS. 13A and 13B, the base station may transmit a configuration message 1330 to the UE before the procedure begins. Configuration message 1330 may be similar in some respects to configuration message 1310 and / or configuration message 1320. FIG. 13C includes the transmission of two messages, namely, Msg A 1331 and Msg B 1332.

[0137] Msg A 1331 may be transmitted by the UE in an uplink transmission. Msg A 1331 may include one or more transmissions of preamble 1341 and / or one or more transmissions of transport block 1342. Transport block 1342 may include content similar and / or equivalent to the content of Msg3 1313 shown in FIG. 13A. Transport block 1342 may include UCI (e.g., SR, HARQ ACK / NACK, and / or the like). The UE may receive Msg B 1332 after or in response to the transmission of Msg A 1331. Msg B 1332 may include content similar and / or equivalent to the content of Msg2 1312 (e.g., RAR) shown in FIGS. 13A and 13B and / or Msg4 1314 shown in FIG. 13A.

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

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

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

[0141] The UE and the base station may exchange control signaling, which 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 include downlink control signaling transmitted from the base station to the UE and / or uplink control signaling transmitted from the UE to the base station.

[0142] The downlink control signaling may include downlink scheduling assignments, uplink scheduling grants indicating uplink radio resources and / or transport formats, slot format information, preemption indications, power control commands, and / or any other suitable signaling. A UE may receive downlink control signaling in a payload transmitted by a 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.

[0143] The base station may attach one or more cyclic redundancy check (CRC) parity bits to the DCI to facilitate detection of transmission errors. If the DCI is intended for a UE (or a group of UEs), the base station may scramble the CRC parity bits with the UE's identifier (or the identifier of the group of UEs). Scrambling the CRC parity bits with the identifier may include modulo-2 addition (or exclusive-OR) of the identifier value and the CRC parity bits. The identifier may include a 16-bit value, the Radio Network Temporary Identifier (RNTI).

[0144] DCIs may be used for different purposes. The purpose may be indicated by the type of RNTI used to scramble the CRC parity bits. For example, a DCI with CRC parity bits scrambled with a paging RNTI (P-RNTI) may indicate paging information and / or system information change notification. The P-RNTI may be predefined as "FFFE" in hexadecimal. A DCI with CRC parity bits scrambled with a system information RNTI (SI-RNTI) may indicate a broadcast transmission of system information. The SI-RNTI may be predefined as "FFFF" in hexadecimal. A DCI with CRC parity bits scrambled with a random access RNTI (RA-RNTI) may indicate a random access response (RAR). A DCI with CRC parity bits scrambled with a cell RNTI (C-RNTI) may indicate a unicast transmission of dynamic scheduling and / or a random access of PDCCH order trigger. A DCI with CRC parity bits scrambled with the Temporary Cell RNTI (TC-RNTI) may indicate contention resolution (e.g., Msg3 similar to Msg3 1313 shown in FIG. 13A). Encodings of other RNTIs configured in the UE by the base station include Configured Scheduling RNTI (CS-RNTI), Transmit Power Control-PUCCH RNTI (TPC-PUCCH-RNTI), Transmit Power Control-PUSCH RNTI (TPC-PUSCH-RNTI), Transmit Power Control-SRS RNTI (TPC-SRS-RNTI), Interruption RNTI (INT-RNTI), Slot Format Indication RNTI (SFI-RNTI), Semi-Persistent CSI RNTI (SP-CSI-RNTI), Modulation and Coding Scheme Cell RNTI (MCS-C-RNTI), and / or the like.

[0145] Depending on the purpose and / or content of the DCI, a base station may transmit the DCI in one or more DCI formats. For example, DCI format 0_0 may be used for scheduling the PUSCH in a cell. DCI format 0_0 may be a fallback DCI format (e.g., has a compact DCI payload). DCI format 0_1 ​​may be used for scheduling the PUSCH in a cell (e.g., has a larger DCI payload than DCI format 0_0). DCI format 1_0 may be used for scheduling the PDSCH in a cell. DCI format 1_0 may be a fallback DCI format (e.g., has a compact DCI payload). DCI format 1_1 may be used for scheduling the PDSCH in a cell (e.g., has a larger DCI payload than DCI format 1_0). DCI format 2_0 may be used to provide a slot format indication to a group of UEs. DCI format 2_1 may be used to inform a group of UEs of physical resource blocks and / or OFDM symbols that the UE assumes are not intended for transmission to the UE. DCI format 2_2 may be used to transmit transmit power control (TPC) commands for PUCCH or PUSCH. DCI format 2_3 may be used to transmit a group of TPC commands for SRS transmission by one or more UEs. DCI formats for new features may be defined in future releases. DCI formats may have different DCI sizes or share the same DCI size.

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

[0147] FIG. 14A shows an example of CORESET configuration for bandwidth portions. A base station may transmit DCI via a PDCCH on one or more control resource sets (CORESETs). A CORESET may include time-frequency resources on which a UE attempts to decode DCI using one or more search spaces. A base station may configure CORESETs 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. The third CORESET 1403 occurs at the third symbol in a slot. The fourth CORESET 1404 occurs at the seventh symbol of the slot. The CORESETs may have different numbers of resource blocks in the frequency domain.

[0148] Figure 14B shows an example of CCE-to-REG mapping for DCI transmission on a CORESET and PDCCH processing. The CCE-to-REG mapping may be interleaved (e.g., to provide frequency diversity) or non-interleaved (e.g., to facilitate frequency-selective transmission of interference coordination and / or control channels). A base station may perform different or identical CCE-to-REG mappings 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 QCL parameter of an antenna port may indicate the QCL information of a demodulation reference signal (DMRS) for PDCCH reception within the CORESET.

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

[0150] As shown in FIG. 14B, the UE may determine time-frequency resources of the CORESET based on the RRC message. The UE may determine CCE-to-REG mapping (e.g., interleaved or non-interleaved, and / or mapping parameters) for the CORESET based on configuration parameters of the CORESET. The UE may determine the number of search space sets (e.g., up to 10) configured on the CORESET based on the RRC message. The UE may monitor a set of PDCCH candidates according to the configuration parameters of the search space sets. The UE may monitor a set of PDCCH candidates in one or more CORESETs to detect one or more DCIs. The monitoring may include decoding one or more PDCCH candidates of the set of PDCCH candidates according to the monitored DCI format. The monitoring may include decoding DCI content of one or more PDCCH candidates having possible (or configured) PDCCH positions, possible (or configured) PDCCH formats (e.g., the number of CCEs in the common search space, the number of PDCCH candidates, and / or the number of PDCCH candidates in the UE-specific search space), and possible (or configured) DCI formats. The decoding may be referred to as blind decoding. The UE may determine the valid DCI for the UE in response to a CRC check (e.g., scrambling bits against CRC parity bits of the DCI matching the RNTI value). The UE may process information included in the DCI (e.g., scheduling assignment, uplink grant, power control, slot format indication, downlink preemption, and / or the like).

[0151] The UE may transmit uplink control signaling (e.g., uplink control information (UCI)) to the base station. The uplink control signaling may include a hybrid automatic repeat request (HARQ) acknowledgment for a received DL-SCH transport block. The UE may transmit the HARQ acknowledgment after receiving the DL-SCH transport block. The uplink control signaling may include channel state information (CSI) indicating the channel quality of the physical downlink channel. The UE may transmit the CSI to the base station. The base station may determine transmission format parameters (e.g., including multiple antennas and beamforming schemes) for downlink transmission based on the received CSI. The uplink control signaling may include a scheduling request (SR). The UE may transmit the SR indicating that uplink data is available for transmission to the base station. The UE may transmit the UCI (e.g., a HARQ acknowledgment (HARQ-ACK), a CSI report, an SR, etc.) via a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH). A UE may transmit uplink control signaling over the PUCCH using one of several PUCCH formats.

[0152] There may be five PUCCH formats, and the UE may determine the PUCCH format based on the size of the UCI (e.g., the number of uplink symbols for UCI transmission and the number of UCI bits). PUCCH format 0 may have a length of one or two OFDM symbols and may contain two or fewer bits. The UE may transmit UCI on PUCCH resources using PUCCH format 0 if the transmission is more than 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 between four and fourteen OFDM symbols and may contain 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 contain more than two bits. A UE may use PUCCH format 2 if the transmission is more than one or two symbols and the number of UCI bits is two or more. PUCCH format 3 may occupy between 4 and 14 OFDM symbols and may include more than two bits. A UE may use PUCCH format 3 if the transmission is four or more symbols, the number of UCI bits is two or more, and the PUCCH resources do not include an orthogonal cover code. PUCCH format 4 may occupy between 4 and 14 OFDM symbols and may include more than two bits. A 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 resources include an orthogonal cover code.

[0153] The base station may transmit configuration parameters of multiple PUCCH resource sets to the UE, for example, using an RRC message. Multiple PUCCH resource sets (e.g., up to four sets) may be configured on the uplink BWP of the cell. A PUCCH resource set may be configured with a PUCCH resource set index, multiple PUCCH resources with the PUCCH resource identified by a PUCCH resource identifier (e.g., pucch-Resourceid), and / or the number (e.g., maximum number) of UCI information bits that the UE may transmit using one of the multiple PUCCH resources in the PUCCH resource set. When configured with multiple PUCCH resource sets, the UE may select one of the multiple PUCCH resource sets based on the total bit length of the UCI information bits (e.g., HARQ-ACK, SR, and / or CSI). If the total bit length of the UCI information bits is less than or equal to two, the UE may select the first PUCCH resource set whose PUCCH resource set index is equal to '0'. If the total bit length of the UCI information bits is greater than 2 and less than or equal to the first configuration 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 the UCI information bits is greater than the first configuration value and less than or equal to the second configuration 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 the UCI information bits is greater than the second configuration 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'.

[0154] After determining a PUCCH resource set from the multiple 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 DCI (e.g., DCI format 1_0 or DCI format 1_1) received on the PDCCH. The 3-bit PUCCH resource indicator of the DCI may indicate one of eight PUCCH resources in the PUCCH resource set. Based on the PUCCH resource indicator, the UE may transmit UCI (HARQ-ACK, CSI, and / or SR) using the PUCCH resource indicated by the PUCCH resource indicator in the DCI.

[0155] 15 illustrates an example of a wireless device 1502 communicating with a base station 1504 according to an embodiment of the present disclosure. The wireless device 1502 and the base station 1504 may be part of a mobile communication network, such as the mobile communication network 100 shown in FIG. 1A, the mobile communication network 150 shown in FIG. 1B, or another communication network. While only one wireless device 1502 and one base station 1504 are shown in FIG. 15, it will be understood that a mobile communication network may include more than one UE and / or more than one base station having the same or similar configuration as that shown in FIG. 15.

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

[0157] On the downlink, data transmitted from base station 1504 to wireless device 1502 may be provided to processing system 1508 of base station 1504. The data may be provided to processing system 1508 by, for example, a core network. On the uplink, data transmitted from wireless device 1502 to base station 1504 may be provided to processing system 1518 of wireless device 1502. Processing system 1508 and processing system 1518 may implement Layer 3 and Layer 2 OSI functions to process the data for transmission. Layer 2 may include, for example, the SDAP layer, the PDCP layer, the RLC layer, and the MAC layer with respect to Figures 2A, 2B, 3, and 4A. Layer 3 may include the RRC layer with respect to Figure 2B.

[0158] After being processed by processing system 1508, data to be transmitted to wireless device 1502 may be provided to transmission processing system 1510 of base station 1504. Similarly, after being processed by processing system 1518, data to be transmitted to base station 1504 may be provided to transmission processing system 1520 of wireless device 1502. Transmission processing system 1510 and transmission processing system 1520 may implement the OSI functions of Layer 1. Layer 1 may include the PHY layer with respect to FIGS. 2A, 2B, 3, and 4A. For transmission 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 channels, multiple-input multiple-output (MIMO) or multi-antenna processing, and / or the like.

[0159] At the base station 1504, a receive processing system 1512 may receive uplink transmissions from the wireless device 1502. At the wireless device 1502, a receive processing system 1522 may receive downlink transmissions from the base station 1504. The receive processing system 1512 and the receive processing system 1522 may implement the OSI functions of Layer 1. Layer 1 may include the PHY layer with respect to FIGS. 2A, 2B, 3, and 4A. For receive processing, the PHY layer may perform, for example, error detection, forward error correction decoding, deinterleaving, demapping of transport channels to physical channels, demodulation of the physical channels, MIMO or multi-antenna processing, and / or the like.

[0160] 15, the wireless device 1502 and the base station 1504 may include multiple antennas. The multiple antennas may be used to implement 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.

[0161] Processing system 1508 and processing system 1518 may be associated with memory 1514 and memory 1524, respectively. Memory 1514 and memory 1524 (e.g., one or more non-transitory computer-readable media) may store computer program instructions or code that may be executed by processing system 1508 and / or processing system 1518 to perform one or more functions discussed herein. Although not shown in FIG. 15 , transmit processing system 1510, transmit processing system 1520, receive processing system 1512, and / or receive processing system 1522 may be coupled to memory (e.g., one or more non-transitory computer-readable media) that stores computer program instructions or code that may be executed to perform one or more of their respective functions.

[0162] The processing system 1508 and / or the processing system 1518 may include one or more controllers and / or one or more processors. The one or more controllers and / or one or more processors may include, 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 devices, discrete gate and / or transistor logic, discrete hardware components, on-board units, 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.

[0163] Processing system 1508 and / or processing system 1518 may be connected to one or more peripheral devices 1516 and one or more peripheral devices 1526, respectively. The one or more peripheral devices 1516 and one or more peripheral devices 1526 may include software and / or hardware that provide features and / or functionality, such as 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 modulation (FM) radio unit, a media player, an internet browser, an electronic control unit (e.g., for a vehicle), and / or one or more sensors (e.g., an accelerometer, gyroscope, temperature sensor, radar sensor, lidar sensor, ultrasonic sensor, light sensor, camera, and / or the like). Processing system 1508 and / or processing system 1518 may receive user input data and / or provide user output data from the one or more peripheral devices 1516 and / or one or more peripheral devices 1526. The processing system 1518 in the wireless device 1502 can receive power from a power source and / or can be configured to distribute power to other components in the wireless device 1502. The power source can include one or more power sources, such as a battery, a solar cell, a fuel cell, or any combination thereof. The processing system 1508 and / or the processing system 1518 can be connected to a GPS chipset 1517 and a GPS chipset 1527, respectively. The GPS chipset 1517 and the GPS chipset 1527 can be configured to provide geographic location information for the wireless device 1502 and the base station 1504, respectively.

[0164] Figure 16A shows 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 include at least one of scrambling, modulation of scramble bits to generate complex-valued symbols, mapping of 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 the precoded complex-valued symbols to resource elements, generation of complex-valued time-domain single-carrier frequency division multiple access (SC-FDMA) or CP-OFDM signals to antenna ports, and / or the like. In one example, if transform precoding is enabled, an SC-FDMA signal for uplink transmission may be generated. In one example, if transform precoding is not enabled, a CP-OFDM signal for uplink transmission may be generated according to Figure 16A. These functions are shown as examples, and it is expected that other mechanisms may be implemented in various embodiments.

[0165] 16B shows an exemplary structure for modulation and upconversion of a baseband signal to a carrier frequency. The baseband signal may be a complex-valued SC-FDMA or CP-OFDM baseband signal and / or a complex-valued Physical Random Access Channel (PRACH) baseband signal for an antenna port. Filtering may be used before transmission.

[0166] 16C shows an example structure of a downlink transmission. The baseband signal representing the physical downlink channel can perform one or more functions. The one or more functions may include scrambling coded bits in a codeword to be transmitted on the physical channel, modulating the scrambled bits to generate complex-valued modulation symbols, mapping the complex-valued modulation symbols onto one or several transmission layers, precoding the complex-valued modulation symbols on the layers for transmission on the antenna ports, mapping the complex-valued modulation symbols of the antenna ports to resource elements, generating a complex-valued time-domain OFDM signal per antenna port, and / or the like. These functions are shown as examples, and it is anticipated that other mechanisms may be implemented in various embodiments.

[0167] 16D shows another exemplary structure for modulation and upconversion 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 used before transmission.

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

[0169] A timer may begin execution when started and continue to run until it is stopped or 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., a timer may be started or restarted from a value, or may start from zero and expire when the value is reached). A timer's duration 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 period / window of a process. When this specification refers to implementations and procedures related to one or more timers, it will be understood that there are multiple ways to implement one or more timers. For example, it will be understood that one or more of multiple ways for implementing a timer may be used to measure the period / window of a procedure. For example, a random access response window timer may be used to measure a window time for receiving a random access response. In one example, the time difference between two timestamps may be used instead of the start and expiration of the random access response window timer. When the timer is restarted, the process for measuring the time window may be restarted. Other example implementations may be provided for restarting the measurement of the time window.

[0170] The wireless device may receive, for example, from a base station, one or more messages including one or more configuration parameters. The one or more configuration parameters may indicate one or more power control parameter sets (e.g., SRI-PUSCH-PowerControl). Each power control parameter set of the one or more power control parameter sets may be identified / indicated by a respective power control parameter set index. The one or more configuration parameters may indicate one or more path loss reference signals, for example, for PUSCH power control. Each path loss reference signal of the one or more path loss reference signals may be identified / indicated by a respective path loss reference signal index.

[0171] The wireless device may receive downlink control information (DCI) that schedules a transport block (e.g., a PUSCH). The DCI may not include an SRI field. The wireless device may determine a default path loss reference signal based on, for example, the DCI not including an SRI field.

[0172] In existing technology, the default path loss reference signal may be a path loss reference signal that is identified / indicated by a path loss reference signal index equal to zero (e.g., PUSCH-PathlossReferenceRS-Id=0) among one or more path loss reference signals.

[0173] In one example, a wireless device may receive an activate command to activate one or more activated path loss reference signals among one or more path loss reference signals. In existing technology, a default path loss reference signal may be a path loss reference signal among one or more activated active path loss reference signals that is mapped to a power control parameter set among one or more power control parameter sets. A power control parameter set may be identified / indicated by a power control parameter set index equal to zero (e.g., sri-PUSCH-PowerControlId=0).

[0174] The wireless device may determine a transmit power based on the default path loss reference signal. The wireless device may transmit a transport block with / using the transmit power.

[0175] In one example, a wireless device may be served by (e.g., transmit to / receive from) multiple TRPs, including a first TRP and a second TRP. The wireless device may, for example, receive DCI scheduling repetition of a transport block (e.g., a PUSCH) among the first TRP and the second TRP. The wireless device may transmit a transport block in one or more first transmission opportunities, e.g., toward / for / the first TRP, and may transmit a transport block in one or more second transmission opportunities, e.g., toward / for / the second TRP. This may increase the reliability of transport block transmission. For example, when the first TRP experiences interference (e.g., due to trees, buildings, etc.), the second TRP may receive the transport block.

[0176] In one example, a DCI scheduling a repetition of a transport block may not include an SRI field. A DCI without an SRI field may include, for example, a DCI without a first SRI field and a second SRI field. A DCI without an SRI field may include, for example, a DCI including a first SRI field but not a second SRI field. In an implementation of existing technology, a wireless device may determine a default path loss reference signal (e.g., PUSCH-PathlossReferenceRS-Id=0, sri-PUSCH-PowerControlId=0) based on a DCI without an SRI field. The wireless device may transmit repetitions of a transport block with / using a transmit power determined based on the default path loss reference signal. Using the same transmit power for two sets of repetitions of a transport block or determining the transmit power based on the same default path loss reference signal may not be efficient. As an example, repetitions may be transmitted to a first TRP and a second TRP, which may not be in the same location. The locations / orientations of the first TRP and the second TRP may be different. Because the first TRP and the second TRP may not be co-located, the first TRP and the second TRP may be subject to different channel conditions (e.g., channel fade, distance, interference, etc.). Using the same transmit power and / or determining the transmit power based on the same default path loss reference signal may result in an inaccurate transmit power (e.g., lower or higher than required) for repeated transport blocks. A wireless device may transmit a transport block toward at least one of the first TRP and the second TRP with / using an inaccurate transmit power, which may increase interference to other cells and / or wireless devices.

[0177] Exemplary embodiments enhance / improve path loss reference signal determination when a wireless device transmits transport block repetitions to / at / for multiple TRPs. In exemplary embodiments, when a DCI scheduling a transport block repetition does not include an SRI field (e.g., both a first SRI field and a second SRI field), the wireless device may determine two default path loss reference signals among one or more path loss reference signals. Exemplary embodiments further enhance / improve path loss reference signal determination by aligning understanding between the wireless device and the base station.

[0178] The first of the two default path loss reference signals may be the first path loss reference signal of one or more path loss reference signals identified / indicated with a path loss reference signal index equal to zero (e.g., PUSCH-PathlossReferenceRS-Id=0). The second of the two default path loss reference signals may be, for example, the second path loss reference signal of one or more path loss reference signals identified / indicated with a path loss reference signal index equal to one (e.g., PUSCH-PathlossReferenceRS-Id=1). The second of the two default path loss reference signals may be, for example, the second path loss reference signal of one or more path loss reference signals identified / indicated with the highest path loss reference signal index.

[0179] The first of the two default path loss reference signals may be the first of one or more activated path loss reference signals mapped to a power control parameter set identified / indicated by a power control parameter set index equal to zero (e.g., sri-PUSCH-PowerControlId=0). The second of the two default path loss reference signals may be, for example, the second of one or more activated path loss reference signals mapped to a power control parameter set identified / indicated by a power control parameter set index equal to one (e.g., sri-PUSCH-PowerControlId=1). The second of the two default path loss reference signals may be, for example, the second of one or more activated path loss reference signals mapped to a power control parameter set identified / indicated by the highest power control parameter set index.

[0180] The wireless device may determine two transmit powers based on the two default path loss reference signals. The wireless device may transmit a transport block in one or more first transmission opportunities toward / to a first TRP with / using a first transmit power of the two transmit powers. The wireless device may determine the first transmit power based on the first default path loss reference signal. The wireless device may transmit a transport block in one or more second transmission opportunities toward / to a second TRP with / using a second transmit power of the two transmit powers. The wireless device may determine the second transmit power based on the second default path loss reference signal.

[0181] In an example embodiment, the DCI scheduling the repetition of a transport block may include a first SRI field and may not include a second SRI field. In this case, the wireless device may determine a second default path loss reference signal for the repetition of the transport block. The wireless device may transmit the transport block in one or more first transmission opportunities toward / to a first TRP with / using a first transmit power determined based on the path loss reference signal indicated by the first SRI field. The wireless device may transmit the transport block in one or more second transmission opportunities toward / to a second TRP with / using a second transmit power determined based on the second default path loss reference signal.

[0182] Using two (different) transmit powers based on two (different) default path loss reference signals for repetition of a transport block for different TRPs, or determining the transmit power based on two (different) default path loss reference signals, may result in accurate transmit power determination. A wireless device may transmit a transport block for each TRP with / using the accurate transmit power. This may result in reduced uplink interference to other cells and / or wireless devices. This may result in reliable reception of the transport block and reduced error rates.

[0183] 17, 18, and 19 illustrate examples of power control for uplink channel repetition according to an aspect of an embodiment of the present disclosure. FIG. 20 is an example of an uplink repetition scheme according to an aspect of an embodiment of the present disclosure.

[0184] The wireless device may receive one or more messages (e.g., at time T0 in FIGS. 17-20). In one example, the wireless device may receive one or more messages from a base station. The one or more messages may include one or more configuration parameters. In one example, the one or more configuration parameters may be RRC configuration parameters. In one example, the one or more configuration parameters may be RRC reconfiguration parameters.

[0185] In one example, the one or more configuration parameters may be for a cell. In one example, at least one configuration parameter of the one or more configuration parameters may be for a cell. In one example, the cell may be a primary cell (PCell). In one example, the cell may be a secondary cell (SCell). The cell may be a secondary cell (e.g., a PUCCH SCell) configured with a PUCCH. In one example, the cell may be an unlicensed cell, for example, operating in an unlicensed band. In one example, the cell may be a licensed cell, for example, operating in a licensed band. In one example, the cell may operate in a first frequency range (FR1). FR1 may include, for example, a frequency band below 6 GHz. In one example, the cell may operate in a second frequency range (FR2). FR2 may include, for example, a frequency band from 24 GHz to 52.6 GHz.

[0186] In one example, a wireless device may perform uplink transmission (e.g., PUSCH, PUCCH, SRS) through a cell at a first time and a first frequency. The wireless device may perform downlink reception (e.g., PDCCH, PDSCH) through a cell at a second time and a second frequency. In one example, the cell may operate in a time division duplex (TDD) mode. In the TDD mode, the first frequency and the second frequency may be the same. In the TDD mode, the first time and the second time may be different. In one example, the cell may operate in a frequency division duplex (FDD) mode. In the FDD mode, the first frequency and the second frequency may be different. In the FDD mode, the first time and the second time may be the same.

[0187] In one example, the wireless device may be in an RRC connected mode, in one example, the wireless device may be in an RRC idle mode, or in one example, the wireless device may be in an RRC inactive mode.

[0188] In one example, a cell may include multiple BWPs. The multiple BWPs may include one or more uplink BWPs including the uplink BWP of the cell. The multiple BWPs may include one or more downlink BWPs including the downlink BWP of the cell.

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

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

[0191] In one example, a wireless device may activate a downlink BWP of one or more downlink BWPs of a cell. In one example, activating a downlink BWP may include the wireless device setting the downlink BWP as (or switching to) an active downlink BWP of the cell. In one example, activating a downlink BWP may include the wireless device setting the downlink BWP to an active state. In one example, activating a downlink BWP may include switching the downlink BWP from an inactive state to an active state.

[0192] In one example, a wireless device may activate an uplink BWP of one or more uplink BWPs of a cell. In one example, activating an uplink BWP may include the wireless device setting (or switching to) the uplink BWP as the active uplink BWP of the cell. In one example, activating an uplink BWP may include the wireless device setting the uplink BWP to an active state. In one example, activating an uplink BWP may include switching the uplink BWP from an inactive state to an active state.

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

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

[0195] In one example, the wireless device may transmit a UE capability message including, for example, UE capability information to the base station.

[0196] In one example, the UE capability information may indicate / configure support for beam correspondence without uplink beam sweeping (e.g., beamCorrespondenceWithoutUL-BeamSweeping). In one example, the wireless device may set the value of beamCorrespondenceWithoutUL-BeamSweeping in the UE capability message to a first value (e.g., one) to indicate support for beam correspondence without uplink sweeping. Based on the UE capability information indicating support for beam correspondence without uplink beam sweeping, the wireless device may determine / select a (preferred) beam (or spatial-domain transmit filter) for uplink transmission based on downlink measurements without relying on uplink beam sweeping. The wireless device may not determine / select a (preferred) beam (or spatial-domain transmit filter) for uplink transmission based on uplink beam sweeping.

[0197] In one example, the UE capability information may indicate support for repetition of transmission of an uplink signal (e.g., PUCCH, PUSCH, transport block, SRS). The repetition may be, for example, in TDM. The repetition may be, for example, in FDM. The repetition may be, for example, in SDM / SFN (e.g., spatial domain / division multiplexing). The repetition may be, for example, in CDM (e.g., code domain / division multiplexing). The wireless device may repeat transmission of an uplink signal, for example, based on the UE capability information indicating support for repetition of the uplink signal.

[0198] In an embodiment, one or more configuration parameters may indicate multiple path loss reference RSs (e.g., PUSCH-PathlossReferenceRS, pathlossReferenceRS, PUCCH-PathlossReferenceRS, PathlossReferenceRS-Config, pathlossReferenceRS-List-r16, pathlossReferenceRS-List, SRS-PathlossReferenceRS). One or more configuration parameters may indicate multiple path loss reference RSs for a cell. One or more configuration parameters may indicate multiple path loss reference RSs for the (active) uplink BWP of the cell. The wireless device may measure / evaluate multiple path loss reference RSs for path loss estimation of uplink channels (e.g., PUSCH, PUCCH, SRS). In FIGS. 17-19, the multiple path loss reference RSs are path loss RS 0, path loss RS 1, ..., path loss RS M.

[0199] In one example, the one or more configuration parameters may indicate multiple path loss reference RS indices / identifiers (e.g., provided by upper layer parameters PUSCH-PathlossReferenceRS-Id, pucch-PathlossReferenceRS-Id) for the multiple path loss reference RSs. In one example, each path loss reference RS of the multiple path loss reference RSs may be identified / indicated by a respective path loss reference RS index of the multiple path loss reference RS indices. In one example, a first path loss reference RS of the multiple path loss reference RSs may be identified by a first path loss reference RS index of the multiple path loss reference RS indices. In one example, a second path loss reference RS of the multiple path loss reference RSs may be identified by a second path loss reference RS index of the multiple path loss reference RS indices.

[0200] In one example, the one or more configuration parameters may indicate multiple power control parameter sets (e.g., SRI-PUSCH-PowerControl). The multiple power control parameter sets may indicate (or be mapped to) multiple path loss reference RSs. Each power control parameter set of the multiple power control parameter sets may indicate (or be mapped to) a respective path loss reference RS of the multiple path loss reference RSs. For example, a first power control parameter set of the multiple power control parameter sets may indicate (or be mapped to) a first path loss reference RS of the multiple path loss reference RSs. The one or more configuration parameters may indicate, for the first power control parameter set, a first path loss reference RS index (e.g., PUSCH-PathlossReferenceRS-Id) of the first path loss reference RS. A second power control parameter set of the multiple power control parameter sets may indicate (or be mapped to) a second path loss reference RS of the multiple path loss reference RSs. The one or more configuration parameters may indicate a second path loss reference RS index (e.g., PUSCH-PathlossReferenceRS-Id) of the second path loss reference RS for the second power control parameter set. A third power control parameter set of the multiple power control parameter sets may indicate (or be mapped to) the first path loss reference RS. The one or more configuration parameters may indicate a first path loss reference RS index of the first path loss reference RS for the third power control parameter set. The multiple path loss reference RS indexes may include a first path loss reference RS index and a second path loss reference RS index. The one or more configuration parameters may, for example, indicate a mapping between the multiple power control parameter sets and the multiple path loss reference RSs. The mapping between the multiple power control parameter sets and the multiple path loss reference RSs may be, for example, predefined / fixed / preconfigured. The mapping between the multiple power control parameter sets and the multiple path loss reference RSs may be, for example, a one-to-one mapping.The mapping between the multiple power control parameter sets and the multiple path loss reference RSs may be, for example, a one-to-many mapping.The mapping between the multiple power control parameter sets and the multiple path loss reference RSs may be, for example, a many-to-one mapping.

[0201] The multiple power control parameter sets include sri-PUSCH-PowerControl 0, sri-PUSCH-PowerControl 1, . . . , sri-PUSCH-PowerControl N in FIG.

[0202] In one example, the one or more configuration parameters may indicate multiple power control parameter set indices / identifiers (e.g., provided by the upper layer parameter sri-PUSCH-PowerControlId) for multiple power control parameter sets. In one example, each power control parameter set of the multiple power control parameter sets may be identified / indicated by a respective power control parameter set index of the multiple power control parameter set indexes. In one example, a first power control parameter set of the multiple power control parameter sets may be identified by a first power control parameter set index of the multiple power control parameter set indexes. A second power control parameter set of the multiple power control parameter sets may be identified by a second power control parameter set index of the multiple power control parameter set indexes.

[0203] In one example, the one or more configuration parameters may indicate / include a path loss RS update parameter (e.g., enablePLRS-UpdateForPUSCH-SRS). The path loss RS update parameter may enable MAC CE-based path loss reference RS update for PUSCH / SRS. Based on the one or more configuration parameters indicating / including the path loss RS update parameter, the wireless device may receive an active command (e.g., PUSCH Pathloss Reference RS Update MAC CE, DCI, RRC) that updates the mapping between one or more path loss reference RSs of the multiple path loss reference RSs and one or more power control parameter sets of the multiple power control parameter sets. For example, the active command may update the mapping between a value of a power control parameter set index (e.g., sri-PUSCH-PowerControlId) that identifies / indicates a power control parameter set and a value of a path loss reference RS index (e.g., PUSCH-PathlossReferenceRS-Id) that identifies / indicates a path loss reference RS. The wireless device may map a power control parameter set to a path loss reference RS based on receiving an active command that updates the mapping between, for example, a power control parameter set and a path loss reference RS. The plurality of path loss reference RSs may include a path loss reference RS. The plurality of power control parameter sets may include a power control parameter set. The plurality of path loss reference RS indices may include a path loss reference RS index. The plurality of power control parameter set indices may include a power control parameter index.

[0204] In one example, the wireless device may receive one or more active commands (eg, PUSCH Pathloss Reference RS Update MAC CE, DCI, RRC) at time T1 in FIG.

[0205] In one example, one or more active commands may indicate / activate / update a mapping between one or more path loss reference RSs among the plurality of path loss reference RSs and a plurality of power control parameter sets. The one or more path loss reference RSs may be mapped to (or linked to, or associated with) a plurality of power control parameter sets, for example, based on receiving one or more active commands indicating / activating / updating the mapping. The wireless device may map (or update) one or more path loss reference RSs to / for a plurality of power control parameter sets based on receiving one or more active commands. The one or more active commands may indicate / activate / update one or more path loss reference RSs among the plurality of path loss reference RSs. In FIG. 19, the one or more path loss reference RSs may be path loss RS 23, path loss RS 41, path loss RS 47, and path loss RS 62.

[0206] The one or more configuration parameters may indicate one or more path loss reference RS indices / identifiers (e.g., provided by higher layer parameters PUSCH-PathlossReferenceRS-Id, pucch-PathlossReferenceRS-Id) for the one or more path loss reference RSs. In one example, each path loss reference RS of the one or more path loss reference RSs may be identified / indicated by a respective path loss reference RS index of the one or more path loss reference RS indexes. The multiple path loss reference RS indices may include one or more path loss reference RS indices.

[0207] In one example, one or more path loss reference RSs may be mapped (or linked or associated) to multiple power control parameter sets, and each power control parameter set of the multiple power control parameter sets may indicate (or be mapped or linked to) a respective path loss reference RS of the one or more path loss reference RSs.

[0208] In one example, a first power control parameter set (e.g., sri-PUSCH-PowerControl 0 in FIG. 19) among the multiple power control parameter sets may indicate (or be mapped to) a first path loss reference RS (e.g., Path loss RS47) among the one or more path loss reference RSs. For example, one or more active commands may indicate / update / activate the first path loss reference RS for the first power control parameter set. A second power control parameter set (e.g., sri-PUSCH-PowerControl 1 in FIG. 19) among the multiple power control parameter sets may indicate (or be mapped to) a second path loss reference RS (e.g., Path loss RS23) among the one or more path loss reference RSs. For example, one or more active commands may indicate / activate / update the second path loss reference RS for the second power control parameter set. A third power control parameter set (e.g., sri-PUSCH-PowerControl N in FIG. 19) among the multiple power control parameter sets may indicate (or be mapped to) a third path loss reference RS (e.g., Path loss RS41) among the one or more path loss reference RSs, etc. For example, one or more active commands may indicate / activate / update the third path loss reference RS for the third power control parameter set.

[0209] A power control parameter set among the multiple power control parameter sets may indicate (or be mapped to) a path loss reference RS among one or more path loss reference RSs. The power control parameter set may include a path loss reference RS index among one or more path loss reference RS indices (e.g., sri PUSCH-PathlossReferenceRS-Id) that identifies / indicates the path loss reference RS. For example, one or more active commands may indicate / activate / update the path loss reference RS index for the power control parameter set.

[0210] In one example, one or more path loss reference RSs may be mapped (or linked) to multiple power control parameter sets. One or more path loss reference RSs that are mapped (or linked) to multiple power control parameter sets may include multiple power control parameter sets that indicate (or are mapped to) the one or more path loss reference RSs. In one example, a path loss reference RS of the one or more path loss reference RSs may be mapped (or linked or associated) to a power control parameter set of the multiple power control parameter sets. In one example, each path loss reference RS of the one or more path loss reference RSs may be mapped (or linked) to a respective power control parameter set of the multiple power control parameter sets.

[0211] In one example, the mapping between the one or more path loss reference RSs and the multiple power control parameter sets may be a one-to-one mapping. A first path loss reference RS of the one or more path loss reference RSs may be mapped to (or linked or associated with) a first power control parameter set of the multiple power control parameter sets. The first path loss reference RS may not be mapped to a second power control parameter set of the multiple power control parameter sets that is different from the first power control parameter set.

[0212] In one example, the mapping between the one or more path loss reference RSs and the multiple power control parameter sets may be a one-to-many mapping. In one example, a first path loss reference RS of the one or more path loss reference RSs may be mapped (or linked or associated) to a first power control parameter set of the multiple power control parameter sets. The first path loss reference RS may be mapped to a second power control parameter set of the multiple power control parameter sets that is different from the first power control parameter set.

[0213] In one example, the multiple power control parameter sets may indicate one or more path loss reference RSs of the multiple path loss reference RSs. The multiple power control parameter sets indicating the one or more path loss reference RSs may include multiple power control parameter sets that are mapped to (or linked or associated with) the one or more path loss reference RSs. In one example, a power control parameter set of the multiple power control parameter sets may be mapped to (or linked or associated with) a path loss reference RS of the one or more path loss reference RSs. A power control parameter set may indicate a path loss reference RS. In one example, each power control parameter set of the multiple power control parameter sets may be mapped to (or linked or associated with) a respective path loss reference RS of the one or more path loss reference RSs of the multiple path loss reference RSs.

[0214] In one example, a path loss reference RS among one or more path loss reference RSs may be mapped (or linked or associated) to a power control parameter set among a plurality of power control parameter sets. The power control parameter set may indicate (or be mapped to) the path loss reference RS. In one example, one or more active commands may indicate (or include identifying / indicating) a path loss reference RS for (the mapped / linked / associated) power control parameter set. The one or more path loss reference RS indices may include a path loss reference RS index. For example, in FIG. 19, one or more active commands indicate (or map or activate or update) Path loss RS 23 for (or to) sri-PUSCH-PowerControl 1, Path loss RS 41 for (or to) sri-PUSCH-PowerControl N, and Path loss RS 47 for (or to) sri-PUSCH-PowerControl 0.

[0215] In one example, the one or more active commands may include one or more fields. A first field of the one or more fields (e.g., PUSCH Pathloss Reference RS ID) may indicate a path loss reference RS. The first field may include a path loss reference RS index (e.g., provided by a higher layer parameter PUSCH-PathlossReferenceRS-Id) among multiple path loss reference RS indices that identifies / indicates the path loss reference RS. A second field of the one or more fields may indicate a power control parameter set (e.g., sri-PUSCH-PowerControlId). The second field may include a power control index (e.g., sri-PUSCH-PowerControlId) among multiple power control parameter set indices that identifies / indicates the power control parameter set. The wireless device may map / update the path loss reference RS to / for a power control parameter set based on receiving one or more active commands that indicate the path loss reference RS and the power control parameter set.

[0216] In one example, the second field may include one or more power control parameter set indexes of a plurality of power control parameter set indexes. The one or more power control parameter set indexes may indicate / identify one or more power control parameter sets of the plurality of power control parameter sets. The wireless device may map / update the path loss reference RS indicated by the first field to / for the one or more power control parameter sets indicated by the second field.

[0217] In one example, the one or more configuration parameters may indicate a plurality of SRS resource sets including at least two SRS resource sets, which may include a first SRS resource set (e.g., SRS resource set 1 in FIG. 17) and a second SRS resource set (e.g., SRS resource set 2 in FIG. 17).

[0218] In one example, one SRS resource set (e.g., the first SRS resource set and / or the second SRS resource set) of the at least two SRS resource sets may be periodic, and the one or more configuration parameters may indicate a periodic resource type of the SRS resource set (e.g., the resource type of the higher layer parameters is set to periodic).

[0219] In one example, one SRS resource set (e.g., the first SRS resource set and / or the second SRS resource set) of the at least two SRS resource sets may be aperiodic, and the one or more configuration parameters may indicate the aperiodic resource type of the SRS resource set (e.g., the resource type of the higher layer parameters is set to aperiodic).

[0220] In one example, one SRS resource set (e.g., the first SRS resource set and / or the second SRS resource set) of the at least two SRS resource sets may be semi-persistent, and one or more configuration parameters may indicate the semi-persistent resource type of the SRS resource set (e.g., the resource type of the higher layer parameters is set to semi-persistent).

[0221] In one example, the one or more configuration parameters may include certain SRS usage parameters for at least two SRS resource sets.

[0222] The SRS usage parameter may be (is set to be) a codebook (e.g., usage = codebook), for example. Based on the SRS usage parameter being (is set to be) a codebook, the at least two SRS resource sets may be used for codebook-based uplink transmission (e.g., PUSCH transmission). Each SRS resource set of the at least two SRS resource sets may be used for codebook-based uplink transmission.

[0223] The SRS usage parameter may be (set as) a non-codebook (e.g., usage = non-codebook), for example. The at least two SRS resource sets may be used for non-codebook-based uplink transmission (e.g., PUSCH transmission) based on the SRS usage parameter being (set as) a non-codebook. Each SRS resource set of the at least two SRS resource sets may be used for non-codebook-based uplink transmission.

[0224] The one or more configuration parameters may include a first SRS usage parameter for the SRS resource set. The one or more configuration parameters may include a second SRS usage parameter for the SRS resource set.

[0225] In one example, the first SRS usage parameter may be (may be set to) a codebook, and the second SRS usage parameter may be (may be set to) a codebook.

[0226] In one example, the first SRS usage parameter may be (may be set to) non-codebook, and the second SRS usage parameter may be (may be set to) non-codebook.

[0227] In one example, a wireless device may receive / detect a DCI (e.g., at time T1 in FIGS. 17 and 18 and at time T2 in FIG. 19). The DCI may be, for example, DCI format 0-1. The DCI may be, for example, DCI format 0-2. The DCI format may be, for example, DCI format 0-x, where x=0, 1, 2, 3, ...

[0228] The DCI may not be in DCI format 0-0, for example.

[0229] In one example, the DCI may schedule transmission of a transport block (e.g., a PUSCH transmission). The DCI may schedule transmission of a transport block (e.g., a TB in FIGS. 17-19) on / via an uplink channel (e.g., a PUSCH, a PUCCH). The DCI may include a dynamic uplink grant for transmission of the transport block. The wireless device may transmit the transport block (e.g., a TB in FIGS. 17-19) via, for example, uplink resources indicated by the DCI (or the dynamic uplink grant). The uplink channel may include uplink resources. The (active) uplink BWP may include uplink resources.

[0230] In one example, the one or more configuration parameters may indicate one or more configured uplink grants (e.g., via the higher layer parameter ConfiguredGrantConfig). The one or more configured uplink grants may include a configured uplink grant. In one example, the configured uplink grant may be a Type 2 configured uplink grant (or a configured grant Type 2). In a Type 2 configured uplink grant, the PDCCH may indicate / provide the uplink grant. A DCI (or layer 1 signaling) may indicate a configured uplink grant active. The wireless device may store the uplink grant as a configured uplink grant based on receiving a DCI indicating a configured uplink grant active. In one example, the DCI may activate the configured uplink grant. In one example, the wireless device may transmit a transport block (e.g., TB in FIGS. 17-19) for the configured uplink grant on / via an uplink channel (e.g., PUSCH, PUCCH). A wireless device may transmit a transport block (e.g., a PUSCH transmission) over one or more periodic uplink resources of a configured uplink grant. The one or more periodic uplink resources may include uplink resources (e.g., a PUSCH resource, a PUCCH resource, an SRS resource). An uplink channel may include one or more uplink resources. An (active) uplink BWP may include the uplink resources.

[0231] The DCI may include a Time Domain Resource Alignment (TDRA) field. The TDRA field may indicate a resource allocation table. The resource allocation table may be indicated, for example, by one or more configuration parameters. The resource allocation table may be, for example, pre-configured / fixed. The TDRA field may indicate a number of repetitions (e.g., numberofrepetitions) for a transport block. The resource allocation table may include a number of repetitions (e.g., numberofrepetitions). The number of repetitions (e.g., numberofrepetitions) may be present in the resource allocation table. In Figures 17 and 18, the number of repetitions is equal to 4 (e.g., numberofrepetitions=4). In Figure 19, the number of repetitions is equal to 2 (e.g., numberofrepetitions=2).

[0232] In one example, the numberofrepetitions of the higher layer parameter may not be present in the resource allocation table indicated by the TDRA field of the DCI. One or more configuration parameters may not include the number of repetitions of the higher layer parameter in the resource allocation table. In one example, one or more configuration parameters may indicate the number of repetitions (e.g., pusch-AggregationFactor). In Figures 17 and 18, the number of repetitions is equal to 4 (e.g., pusch-AggregationFactor=4). In Figure 19, the number of repetitions is equal to 2 (e.g., pusch-AggregationFactor=2).

[0233] In one example, the repetition number may be for repetition of a transport block over uplink resources (or uplink channels) (e.g., PUCCH resources, SRS resources, PUSCH resources). In one example, the one or more configuration parameters may indicate multiple uplink signal / channel transmission / repetition opportunities (e.g., PUSCH transmission opportunities, PUCCH transmission opportunities) for transmission / repetition of a transport block. In one example, the DCI may indicate multiple uplink signal / channel transmission / repetition opportunities (e.g., PUSCH transmission opportunities, PUCCH transmission opportunities) for transmission / repetition of a transport block. In one example, the DCI may indicate a first / starting / earliest uplink signal / channel transmission / repetition opportunity. Based on the first / starting / earliest uplink signal / channel transmission / repetition opportunity, the wireless device may determine multiple uplink signal / channel transmission / repetition opportunities, including the first / starting / earliest uplink signal / channel transmission / repetition opportunity, for transmission / repetition of a transport block. The wireless device may determine the first / starting / earliest uplink signal / channel transmission / repetition opportunity, for example, based on one or more fields in the DCI (e.g., TDRA, FDRA, etc.). The number of multiple uplink signal / channel transmission opportunities may be equal to the number of repetitions, for example.

[0234] In one example, a wireless device may transmit a transport block over / on / in multiple uplink signal / channel transmission / repetition opportunities (e.g., times T2a-T2d in FIGS. 17 and 18 and times T3a-T3b in FIG. 19). The wireless device may repeat (the transmission of) a transport block over / on / in multiple uplink signal / channel transmission / repetition opportunities. The wireless device may transmit a transport block "repetition number" times. For example, when the repetition number is 4, the wireless device may transmit the transport block four times. When the repetition number is 2, the wireless device may transmit the transport block two times.

[0235] The wireless device may repeat (transmission of) the transport block over / on / in multiple uplink signal / channel transmission / repetition opportunities, for example, based on the TDRA field indicating the repetition number.

[0236] The wireless device may repeat (transmission of) a transport block over / on / in multiple uplink signal / channel transmission / repetition opportunities, for example, based on one or more configuration parameters indicating the number of repetitions.

[0237] The repetition of the transport block may be, for example, time-domain repetition (e.g., TDM, TDMSchemeA, TDMSchemeB, etc. in FIG. 20). In time-domain repetition, the multiple uplink signal / channel transmission opportunities may not overlap in time. Each uplink signal / channel transmission opportunity of the multiple uplink signal / channel transmission opportunities may have a non-overlapping time-domain resource allocation with respect to other uplink signal / channel transmission opportunities of the multiple uplink signal / channel transmission opportunities. For example, a first uplink signal / channel transmission opportunity of the multiple uplink signal / channel transmission opportunities may not overlap in time with a second uplink signal / channel transmission opportunity of the multiple uplink signal / channel transmission opportunities. The first uplink signal / channel transmission opportunity and the second uplink signal / channel transmission opportunity may be different. In time-domain repetition, the multiple uplink signal / channel transmission opportunities may or may not overlap in frequency. The multiple uplink signal / channel transmission / repetition opportunities are the first TX opportunity, the second TX opportunity, the third TX opportunity, and the fourth TX opportunity in time domain repetition (e.g., TDM) in FIG. 20 . In time domain repetition, the repetition of the transport block may be, for example, a time unit (e.g., TDM-ed). The wireless device may, for example, repeat transmission of the transport block over / on / in the time unit. The time unit may, for example, be continuous. The time unit may, for example, not be continuous (e.g., may have a time / symbol / slot gap). The number of time units may be equal to the number of repetitions. The time unit may, for example, be a time slot. The time unit may, for example, be a minislot. The time unit may, for example, be a time symbol (e.g., OFDM symbol). The time unit may, for example, be a subframe. The time unit may, for example, be an actual / nominal repetition. The multiple uplink signal / channel transmission opportunities may be / occur in time units.For example, a first uplink signal / channel transmission opportunity of the plurality of uplink signal / channel transmission opportunities may be / occur in a first time unit of time units. A second uplink signal / channel transmission opportunity of the plurality of uplink signal / channel transmission opportunities may be / occur in a second time unit of time units, etc. The first time unit may be different from the second time unit. The first time unit may not overlap in time with the second time unit.

[0238] The repetition of the transport block may be, for example, frequency-domain repetition (e.g., FDM, FDMSchemeA, FDMSchemeB, etc. in FIG. 20). In time-domain repetition, the multiple uplink signal / channel transmission opportunities may or may not overlap in time. In frequency-domain repetition, the multiple uplink signal / channel transmission opportunities may not overlap in frequency. Each uplink signal / channel transmission opportunity of the multiple uplink signal / channel transmission opportunities may have a non-overlapping frequency-domain resource allocation with respect to other uplink signal / channel transmission opportunities of the multiple uplink signal / channel transmission opportunities. For example, a first uplink signal / channel transmission opportunity of the multiple uplink signal / channel transmission opportunities may not overlap in frequency with a second uplink signal / channel transmission opportunity of the multiple uplink signal / channel transmission opportunities. The first uplink signal / channel transmission opportunity and the second uplink signal / channel transmission opportunity may overlap in time. The first uplink signal / channel transmission opportunity and the second uplink signal / channel transmission opportunity may be different. The multiple uplink signal / channel transmission / repetition opportunities are the first TX opportunity and the second TX opportunity in frequency domain repetition (e.g., FDM) in FIG. 20 . In frequency domain repetition, the repetition of the transport block can be / occur, for example, in frequency units (e.g., frequencies, PRBs, frequency bands, subbands, bandwidth portions, cells). The wireless device can, for example, repeat transmission of the transport block across / on / in the frequency units. The frequency units can, for example, be contiguous. The frequency units may, for example, not be contiguous (e.g., may have frequency / PRB gaps). The number of frequency units can be equal to the repetition number. The frequency unit can, for example, be a frequency band. The frequency unit can, for example, be a physical resource block (PRB). The frequency unit can, for example, be a BWP. The frequency unit can, for example, be a cell. The multiple uplink signal / channel transmission opportunities can be / occur, for example, in frequency units.For example, a first uplink signal / channel transmission opportunity of the plurality of uplink signal / channel transmission opportunities may be / occur in a first frequency unit of frequency units. A second uplink signal / channel transmission opportunity of the plurality of uplink signal / channel transmission opportunities may be / occur in a second frequency unit of frequency units, etc. The first frequency unit may be different from the second frequency unit. The first frequency unit may not overlap in frequency with the second frequency unit.

[0239] The repetition of the transport block may be, for example, a code / spatial domain repetition scheme (e.g., SDM / SFN in FIG. 20, SDM scheme, CDM scheme, SDMS scheme, CDMS scheme, etc.). In a code / spatial domain repetition scheme, multiple uplink signal / channel transmission opportunities may overlap in time. In a code / spatial domain repetition scheme, multiple uplink signal / channel transmission opportunities may overlap in frequency. In code / spatial domain repetition, multiple uplink signal / channel transmission opportunities may be uplink signal / channel transmission opportunities (e.g., or a single uplink signal / channel transmission opportunity). Each uplink signal / channel transmission opportunity of the multiple uplink signal / channel transmission opportunities may be the same (or the same as the uplink signal / channel transmission opportunity or the single uplink signal / channel transmission opportunity). Each uplink signal / channel transmission opportunity of the multiple uplink signal / channel transmission opportunities may have overlapping frequency domain resource allocations with respect to other uplink signal / channel transmission opportunities of the multiple uplink signal / channel transmission opportunities. Each uplink signal / channel transmission opportunity of the multiple uplink signal / channel transmission opportunities may have a time-domain resource allocation that overlaps with other uplink signal / channel transmission opportunities of the multiple uplink signal / channel transmission opportunities. For example, a first uplink signal / channel transmission opportunity of the multiple uplink signal / channel transmission opportunities may overlap in time and frequency with a second uplink signal / channel transmission opportunity of the multiple uplink signal / channel transmission opportunities. The first uplink signal / channel transmission opportunity (e.g., the first TX opportunity) and the second uplink signal / channel transmission opportunity (e.g., the second TX opportunity) may be the same. The multiple uplink signal / channel transmission / repetition opportunities are the first TX opportunity and the second TX opportunity in the code / spatial domain repetition (e.g., SDM / SFN) in FIG. 20. The first TX opportunity and the second TX opportunity may be the same in the code / spatial domain repetition (e.g., overlap in time and frequency).In a code / spatial domain repetition, multiple uplink signal / channel transmission opportunities may occur in the same frequency unit (e.g., frequency, PRB, frequency band, bandwidth portion, cell). For example, a first frequency unit of a first uplink signal / channel transmission opportunity and a second frequency unit of a second uplink signal / channel transmission opportunity may overlap in frequency. Multiple uplink signal / channel transmission opportunities may occur in the same time unit (e.g., symbol, actual / nominal repetition, minislot, slot, subframe, etc.). For example, a first time unit of a first uplink signal / channel transmission opportunity and a second time unit of a second uplink signal / channel transmission opportunity may overlap in time.

[0240] For example, in Figures 17 and 18, the multiple uplink signal / channel transmission opportunities include a first uplink signal / channel transmission opportunity (e.g., first TX opportunity, first time slot, first actual / nominal repeat), a second uplink signal / channel transmission opportunity (e.g., second TX opportunity, second time slot, second actual / nominal repeat), a third uplink signal / channel transmission opportunity (e.g., third TX opportunity, third time slot, third actual / nominal repeat), and a fourth uplink signal / channel transmission opportunity (e.g., fourth TX opportunity, fourth time slot, fourth actual / nominal repeat). In FIG. 19, the multiple uplink signal / channel transmission opportunities include a first uplink signal / channel transmission opportunity (e.g., first TX opportunity, first time slot, first actual / nominal repetition) and a second uplink signal / channel transmission opportunity (e.g., second TX opportunity, second time slot, second actual / nominal repetition).

[0241] In one example, the one or more configuration parameters may indicate a repetition scheme (e.g., an FDM scheme, a TDM scheme, an SFN scheme, an SDM scheme, or a CDM scheme). In one example, the DCI may indicate the repetition scheme. The DCI may include one or more fields (e.g., an SRI field, a TCI field, an antenna port field, etc.) that indicate the repetition scheme. The repetition scheme may be for repetition of transmission of a transport block (e.g., a PUSCH transmission) over uplink resources (e.g., a PUCCH resource, an SRS resource, a PUSCH resource). The repetition scheme may be, for example, time-domain repetition (e.g., TDM in FIG. 20). The repetition scheme may be, for example, frequency-domain repetition (e.g., FDM in FIG. 20). The repetition scheme may be, for example, code / spatial-domain repetition (e.g., SDM / SFN in FIG. 20). In FIGS. 17 to 19, the repetition scheme is time-domain repetition.

[0242] The wireless device may repeat a transport block (of transmission) across / over / in multiple uplink signal / channel transmission / repetition opportunities, for example, based on one or more configuration parameters indicating a repetition scheme.

[0243] In one example, the wireless device may determine / calculate / compute multiple transmit powers. The wireless device may determine / calculate / compute multiple transmit powers for transmission of the transport block.

[0244] A wireless device may perform transmission of a transport block with / using multiple transmit powers. A wireless device may transmit a transport block with / using multiple transmit powers.

[0245] The wireless device may determine / calculate / compute multiple transmit powers, for example, for repetitions of a transport block. The wireless device may repeat transmissions of a transport block with / using multiple transmit powers (e.g., at times T2a-T2d in FIGS. 17 and 18 and at times T3a-T3b in FIG. 19). The wireless device may transmit repetitions of a transport block with / using multiple transmit powers.

[0246] In one example, a wireless device may transmit a transport block across / on / in multiple uplink signal / channel transmission / repetition opportunities (e.g., times T2a-T2d in FIGS. 17 and 18 and times T3a-T3b in FIG. 19) with multiple transmit powers. The wireless device may transmit a transport block across / on / in each uplink signal / channel transmission opportunity of the multiple uplink signal / channel transmission opportunities with / using a respective transmit power of the multiple transmit powers. The wireless device may transmit a transport block in each uplink signal / channel transmission opportunity of the multiple uplink signal / channel transmission opportunities with / using a respective transmit power of the multiple transmit powers.

[0247] The wireless device may transmit a transport block across / on / in one or more first uplink signal / channel transmission opportunities of the plurality of uplink signal / channel transmission opportunities with / using a first transmit power of the plurality of transmit powers. The wireless device may transmit a transport block across / on / in one or more second uplink signal / channel transmission opportunities of the plurality of uplink signal / channel transmission opportunities with / using a second transmit power of the plurality of transmit powers. In Figures 17 and 18, the one or more first uplink signal / channel transmission opportunities are the first uplink signal / channel transmission opportunity (e.g., first TX opportunity, first time slot, first actual / nominal repetition at time T2a) and the third uplink signal / channel transmission opportunity (e.g., third TX opportunity, third time slot, third actual / nominal repetition at time T2c). The one or more second uplink signal / channel transmission opportunities are a second uplink signal / channel transmission opportunity (e.g., a second TX opportunity, a second time slot, a second actual / nominal repetition at time T2b) and a fourth uplink signal / channel transmission opportunity (e.g., a fourth TX opportunity, a fourth time slot, a fourth actual / nominal repetition at time T2d). In Figure 19, the one or more first uplink signal / channel transmission opportunities are a first uplink signal / channel transmission opportunity (e.g., a first TX opportunity, a first time slot, a first actual / nominal repetition at time T3a). The one or more second uplink signal / channel transmission opportunities are a second uplink signal / channel transmission opportunity (e.g., a second TX opportunity, a second time slot, a second actual / nominal repetition at time T3b).

[0248] In one example, the number of repetitions may be two. The multiple uplink signal / channel transmission opportunities may include a first uplink signal / channel transmission opportunity (first TX opportunity) and a second uplink signal / channel transmission opportunity (e.g., second TX opportunity). The wireless device may transmit a transport block in the first uplink signal / channel transmission opportunity with / using a first transmit power. The wireless device may apply the first transmit power to the first uplink signal / channel transmission opportunity. The wireless device may transmit a transport block in the second uplink signal / channel transmission opportunity with / using a second transmit power. The wireless device may apply the second transmit power to the second uplink signal / channel transmission opportunity.

[0249] In one example, the number of repetitions may be greater than (or greater than) two. In one example, one or more configuration parameters may indicate periodic mapping. Periodic mapping may enable / indicate mapping of multiple transmit powers to multiple uplink signal / channel transmission opportunities, for example, periodically (e.g., periodically switching transmit powers). The wireless device may transmit a transport block on a first uplink signal / channel transmission opportunity (e.g., a first TX opportunity) of the multiple uplink signal / channel transmission opportunities with / using a first transmit power. The wireless device may apply the first transmit power to the first uplink signal / channel transmission opportunity. The wireless device may transmit a transport block on a second uplink signal / channel transmission opportunity (e.g., a second TX opportunity) of the multiple uplink signal / channel transmission opportunities with / using a second transmit power. The wireless device may apply the second transmit power to the second uplink signal / channel transmission opportunity. The same transmit power mapping pattern may remain on uplink signal / channel transmission opportunities of the multiple uplink signal / channel transmission opportunities, for example, based on one or more configuration parameters indicating periodic mapping. The remained on uplink signal / channel transmission opportunities may not include the first uplink signal / channel transmission opportunity and the second uplink signal / channel transmission opportunity. For example, if the number of repetitions is equal to four, the multiple uplink signal / channel transmission opportunities may include the first uplink signal / channel transmission opportunity, the second uplink signal / channel transmission opportunity, a third uplink signal / channel transmission opportunity (e.g., the third TX opportunity), and a fourth uplink signal / channel transmission opportunity (e.g., the fourth TX opportunity). The wireless device may transmit a transport block on the first uplink signal / channel transmission opportunity and the third uplink signal / channel transmission opportunity with / using the first transmit power. The wireless device may transmit a transport block in the second uplink signal / channel transmission opportunity and the fourth uplink signal / channel transmission opportunity with / using the second transmit power.For example, when the number of repetitions is equal to 8, the multiple uplink signal / channel transmission opportunities may include a first uplink signal / channel transmission opportunity (e.g., a first TX opportunity), a second uplink signal / channel transmission opportunity (e.g., a second TX opportunity), a third uplink signal / channel transmission opportunity (e.g., a third TX opportunity), a fourth uplink signal / channel transmission opportunity (e.g., a fourth TX opportunity), a fifth uplink signal / channel transmission opportunity (e.g., a fifth TX opportunity), a sixth uplink signal / channel transmission opportunity (e.g., a sixth TX opportunity), a seventh uplink signal / channel transmission opportunity (e.g., a seventh TX opportunity), and eight uplink signal / channel transmission opportunities (e.g., an eighth TX opportunity). The wireless device may transmit transport blocks in the first uplink signal / channel transmission opportunity, the third uplink signal / channel transmission opportunity, the fifth uplink signal / channel transmission opportunity, and the seventh uplink signal / channel transmission opportunity with / using the first transmit power. The wireless device may transmit transport blocks in the second uplink signal / channel transmission opportunity, the fourth uplink signal / channel transmission opportunity, the sixth uplink signal / channel transmission opportunity, and the eighth uplink signal / channel transmission opportunity with / using the second transmission power. Figures 17 and 18 show examples of periodic mapping (e.g., the first transmission power is used for the first and third uplink signal / channel transmission opportunities, and the second transmission power is used for the second and fourth uplink signal / channel transmission opportunities).

[0250] In one example, the number of repetitions may be greater than (or greater than) two. In one example, one or more configuration parameters may indicate sequential mapping. Sequential mapping may enable mapping of multiple transmit powers to multiple uplink signal / channel transmission opportunities, for example, sequentially (e.g., sequentially switching transmit powers). The wireless device may transmit a transport block with / using a first transmit power in a first uplink signal / channel transmission opportunity (e.g., a first TX opportunity) of the multiple uplink signal / channel transmission opportunities and in a second uplink signal / channel transmission opportunity (e.g., a second TX opportunity) of the multiple uplink signal / channel transmission opportunities. The wireless device may apply the first transmit power to the first uplink signal / channel transmission opportunity and to the second uplink signal / channel transmission opportunity. The wireless device may transmit a transport block with / using a second transmit power in a third uplink signal / channel transmission opportunity (e.g., a third TX opportunity) of the multiple uplink signal / channel transmission opportunities and in a fourth uplink signal / channel transmission opportunity (e.g., a fourth TX opportunity) of the multiple uplink signal / channel transmission opportunities. The wireless device may apply the second transmit power to the third uplink signal / channel transmission opportunity and to the fourth uplink signal / channel transmission opportunity. The same transmit power mapping pattern may remain on the uplink signal / channel transmission opportunities of the multiple uplink signal / channel transmission opportunities, for example, based on one or more configuration parameters indicating sequential mapping. The remained on uplink signal / channel transmission opportunities may not include the first uplink signal / channel transmission opportunity, the second uplink signal / channel transmission opportunity, the third uplink signal / channel transmission opportunity, and the fourth uplink signal / channel transmission opportunity. For example, if the number of repetitions is equal to four, the multiple uplink signal / channel transmission opportunities may include a first uplink signal / channel transmission opportunity, a second uplink signal / channel transmission opportunity, a third uplink signal / channel transmission opportunity (e.g., a third TX opportunity), and a fourth uplink signal / channel transmission opportunity (e.g., a fourth TX opportunity).The wireless device may transmit a transport block on the first uplink signal / channel transmission opportunity and the second uplink signal / channel transmission opportunity with / using a first transmit power. The wireless device may transmit a transport block on the third uplink signal / channel transmission opportunity and the fourth uplink signal / channel transmission opportunity with / using a second transmit power. For example, when the number of repetitions is equal to 8, the multiple uplink signal / channel transmission opportunities may include a first uplink signal / channel transmission opportunity (e.g., first TX opportunity), a second uplink signal / channel transmission opportunity (e.g., second TX opportunity), a third uplink signal / channel transmission opportunity (e.g., third TX opportunity), a fourth uplink signal / channel transmission opportunity (e.g., fourth TX opportunity), a fifth uplink signal / channel transmission opportunity (e.g., fifth TX opportunity), a sixth uplink signal / channel transmission opportunity (e.g., sixth TX opportunity), a seventh uplink signal / channel transmission opportunity (e.g., seventh TX opportunity), and eight uplink signal / channel transmission opportunities (e.g., eighth TX opportunity). The wireless device may transmit transport blocks in the first uplink signal / channel transmission opportunity, the second uplink signal / channel transmission opportunity, the fifth uplink signal / channel transmission opportunity, and the sixth uplink signal / channel transmission opportunity with / using the first transmit power. The wireless device may transmit transport blocks in the third uplink signal / channel transmission opportunity, the fourth uplink signal / channel transmission opportunity, the seventh uplink signal / channel transmission opportunity, and the eighth uplink signal / channel transmission opportunity with / using the second transmission power.

[0251] In one example, a wireless device may transmit a transport block with / using multiple transmit powers across / on / in multiple uplink signal / channel transmission opportunities based on one or more configuration parameters indicating a repetition scheme.

[0252] In an embodiment, the one or more configuration parameters may include an enabling parameter (e.g., PUSCH repetition, PUCCH repetition, enableTwoPLForPUSCH repetition, enableTwoPowerControlForPUSCH repetition, etc.). The enabling parameter may be set to "enabled". The one or more configuration parameters may indicate "enabled" for the enabling parameter. The value of the enabling parameter may / can indicate "enabled". The enabling parameter may be for a cell. The enabling parameter may enable determination / selection of multiple transmit powers for a repetition of a transport block (e.g., PUSCH transmission). The enabling parameter may enable determination / selection of multiple power control parameters (e.g., path loss criterion RS, etc.) for a repetition of a transport block. The enabling parameter may enable determination / selection of multiple transmit powers for transmission of a transport block (e.g., PUSCH transmission). The enabling parameter may enable determination / selection of multiple transmit powers for transmitting a transport block towards / to multiple TRPs. In one example, a wireless device may transmit a transport block with / using multiple transmit powers across / on / in multiple uplink signal / channel transmission opportunities based on one or more configuration parameters, including an enabled parameter set to enabled.

[0253] In one example, a wireless device may transmit a transport block across / on / at multiple uplink signal / channel transmission opportunities based on one or more configuration parameters indicating at least two SRS resource sets, with / using multiple transmit powers and setting an SRS usage parameter in a codebook.

[0254] In one example, a wireless device may transmit a transport block across / on / at multiple uplink signal / channel transmission opportunities based on one or more configuration parameters indicating at least two SRS resource sets with / using multiple transmit powers and setting SRS usage parameters to a non-codebook.

[0255] The DCI may include an antenna port field.

[0256] In one example, the antenna port field may indicate a DM-RS port within a code division multiplexing (CDM) group for a transport block.

[0257] In one example, a wireless device may transmit a transport block with / using multiple transmit powers across / on / in multiple uplink signal / channel transmission opportunities based on the antenna port field indicating a DM-RS port within a CDM group.

[0258] In one example, the antenna port field may indicate the DM-RS ports in at least two CDM groups.

[0259] A wireless device may transmit a transport block in an uplink signal / channel transmission opportunity (or uplink resource) with / using multiple transmit powers. The wireless device may transmit a first portion of the transport block (or one or more first data layers / streams or one or more first DM-RS portions or one or more first symbols) in an uplink signal / channel transmission opportunity (or in a first symbol of the uplink signal / channel transmission opportunity) with / using a first transmit power of the multiple transmit powers. The wireless device may transmit a second portion of the transport block (or one or more second data layers / streams or one or more second DM-RS portions or one or more second symbols) in an uplink signal / channel transmission opportunity (or in a second symbol of the uplink signal / channel transmission opportunity) with / using a second transmit power of the multiple transmit powers. A transport block may comprise a first portion and a second portion. A transport block may comprise one or more first data layers / streams and one or more second data layers / streams. A transport block may include one or more first symbols and one or more second symbols. For example, the one or more first symbols may include symbol 0, symbol 1, and symbol 2 of a transport block, and the one or more first symbols may include symbol 3, symbol 4, and symbol 5 of a transport block. A transport block may include symbol 0, symbol 1, ..., symbol 4, and symbol 5.

[0260] The wireless device may transmit a first portion of a transport block with / using a first transmit power and a second portion of the transport block with / using a second transmit power, for example, based on the antenna port field indicating a DM-RS port in at least two CDM groups.

[0261] The wireless device may, for example, transmit a first portion of a transport block at a first transmit power and a second portion of the transport block at a second transmit power based on one or more fields of the DCI.

[0262] The wireless device may transmit a first portion of a transport block with / using a first transmit power and a second portion of the transport block with / using a second transmit power, for example, based on the repetition scheme being code / spatial domain repetition (SDM / SFN in FIG. 20).

[0263] In one example, the first SRS resource set may include a first plurality of SRS resources (e.g., SRS resource 1, SRS resource 2), and the second SRS resource set may include a second plurality of SRS resources (e.g., SRS resource 3, SRS resource 4).

[0264] The DCI may include two SRI fields (or two TCI fields), including a first SRI field and a second SRI field. The DCI may include two SRI fields based on a first SRS resource set including a first plurality of SRS resources and a second SRS resource set including a second plurality of SRS resources. The DCI may include two SRI fields based on a first SRS resource set including more than one SRS resource and a second SRS resource set including more than one SRS resource.

[0265] In one example, the first SRI field may indicate (or may be mapped to) a first power control parameter set among a plurality of power control parameter sets. The first power control parameter set may indicate (or may be mapped to) a first path loss reference RS among a plurality of path loss reference RSs. The value of the first SRI field may indicate the first power control parameter set. The value of the first SRI field may be equal to a first power control parameter set index among a plurality of power control parameter set indexes that identifies the first power control parameter set. The value of the first SRI field may be mapped to (or may indicate) the first power control parameter set index.

[0266] In one example, the second SRI field may indicate (or may be mapped to) a second power control parameter set among a plurality of power control parameter sets. The second power control parameter set may indicate (or may be mapped to) a second path loss reference RS among a plurality of path loss reference RSs. The value of the second SRI field may indicate the second power control parameter set. The value of the second SRI field may be equal to a second power control parameter set index among a plurality of power control parameter set indexes that identifies the second power control parameter set. The value of the second SRI field may be mapped to (or may indicate) the second power control parameter set index.

[0267] The one or more configuration parameters may indicate a first reference signal (e.g., CSI-RS, SS / PBCH block) for the first path loss reference RS. The first path loss reference RS may include a first reference signal index (e.g., provided by higher layer parameters referenceSignal, ssb-index, csi-RS-Index, NZP-CSI-RS-ResourceId) that indicates / identifies the first reference signal.

[0268] The one or more configuration parameters may indicate a second reference signal (e.g., CSI-RS, SS / PBCH block) for the second path loss reference RS. The second path loss reference RS may include a second reference signal index (e.g., provided by higher layer parameters referenceSignal, ssb-index, csi-RS-Index, NZP-CSI-RS-ResourceId) that indicates / identifies the second reference signal.

[0269] In one example, the wireless device may determine / calculate / compute a first transmit power of the plurality of transmit powers based on a first path loss reference RS indicated by (or mapped to) a first power control parameter set. The wireless device may determine / calculate / compute the first transmit power based on a first reference signal indicated by the first path loss reference RS. The wireless device may determine / calculate / compute a second transmit power of the plurality of transmit powers based on a second path loss reference RS indicated by (or mapped to) a second power control parameter set. The wireless device may determine / calculate / compute the second transmit power based on a second reference signal indicated by the second path loss reference RS.

[0270] In one example, the first SRS resource set may include a single SRS resource (e.g., SRS resource 1), and the second SRS resource set may include multiple SRS resources (e.g., SRS resource 3, SRS resource 4).

[0271] The DCI may not include a first SRI field (or a first TCI field) based on a first SRS resource set that includes a single SRS resource. The DCI may include a second SRI field (or a second TCI field) based on a second SRS resource set that includes multiple SRS resources. The DCI may include a second SRI field based on a second SRS resource set that includes more than one SRS resource.

[0272] In one example, the second SRI field may indicate (or be mapped to) a second power control parameter set among a plurality of power control parameter sets. The second power control parameter set may indicate (or be mapped to) a second path loss reference RS among a plurality of path loss reference RSs. The second path loss reference RS may indicate a second reference signal.

[0273] In FIG. 17, the wireless device may determine a first default path loss reference RS from among the multiple path loss reference RSs. The wireless device may determine the first default path loss reference RS based on a DCI that does not include a first SRI field. The first default path loss reference RS may be indicated / identified by a first path loss reference RS index (e.g., PUSCH-PathlossReferenceRS-Id) equal to a first value. The multiple path loss reference RS indexes may include a first path loss reference RS index. The first value may be equal to zero, for example (e.g., path loss RS0 in FIG. 17).

[0274] In FIG. 19, the wireless device may determine a first default path loss reference RS among one or more path loss reference RSs. The wireless device may determine the first default path loss reference RS based on a DCI that does not include a first SRI field. The first default path loss reference RS may be mapped to a first power control parameter set among multiple power control parameter sets indicated / identified by a first power control parameter set (e.g., sri-PUSCH-PowerControlId) equal to a first value. The multiple power control parameter set indexes may include a first power control parameter set index. For example, the first value may be equal to zero (e.g., path loss RS47 mapped to sri-PUSCH-PowerControl0 in FIG. 19). The wireless device may determine the first default path loss reference RS among one or more path loss reference RSs activated / indicated / updated by one or more active commands, for example, based on one or more configuration parameters including a path loss RS update parameter.

[0275] The one or more configuration parameters may indicate a first reference signal (e.g., CSI-RS, SS / PBCH block) for the first default path loss reference RS. The first default path loss reference RS may include a first reference signal index (e.g., provided by higher layer parameters referenceSignal, ssb-index, csi-RS-Index, NZP-CSI-RS-ResourceId) that indicates / identifies the first reference signal.

[0276] In one example, the wireless device may determine / calculate / compute a first transmit power of the plurality of transmit powers based on a first default path loss reference RS. The wireless device may determine / calculate / compute the first transmit power based on a first reference signal indicated by the first default path loss reference RS. The wireless device may determine / calculate / compute a second transmit power of the plurality of transmit powers based on a second path loss reference RS indicated by (or mapped to) a second power control parameter set. The wireless device may determine / calculate / compute the second transmit power based on a second reference signal indicated by the second path loss reference RS.

[0277] In one example, the first SRS resource set may include multiple SRS resources (e.g., SRS resource 1 and SRS resource 2), and the second SRS resource set may include a single SRS resource (e.g., SRS resource 3).

[0278] The DCI may not include a second SRI field (or a second TCI field) based on a second SRS resource set that includes a single SRS resource. The DCI may include a first SRI field (or a first TCI field) based on a first SRS resource set that includes multiple SRS resources. The DCI may include a first SRI field based on a first SRS resource set that includes more than one SRS resource.

[0279] In one example, the first SRI field may indicate (or may be mapped to) a first power control parameter set among a plurality of power control parameter sets. The first power control parameter set may indicate (or may be mapped to) a first path loss reference RS among a plurality of path loss reference RSs. The first path loss reference RS may include a first reference signal.

[0280] 17, the wireless device may determine a second default path loss reference RS from among the plurality of path loss reference RSs. The wireless device may determine the second default path loss reference RS based on a DCI that does not include a second SRI field.

[0281] The second default path loss reference RS may be indicated / identified by a second path loss reference RS index (e.g., PUSCH-PathlossReferenceRS-Id) equal to a second value. The multiple path loss reference RS indexes may include a second path loss reference RS index. The second value may be, for example, equal to 1 (e.g., Path Loss RS1 in FIG. 17). The second value may be, for example, equal to 0.

[0282] The second default path loss reference RS may be indicated / identified by a highest second path loss reference RS index (e.g., PUSCH-PathlossReferenceRS-Id) among multiple path loss reference RS indexes among the multiple path loss reference RSs (e.g., path loss RS M in FIG. 17). The multiple path loss reference RS indexes may include the second path loss reference RS index.

[0283] The one or more configuration parameters may, for example, indicate a second default path loss reference RS.

[0284] 19, the wireless device may determine a second default path loss reference RS among one or more path loss reference RSs. The wireless device may determine the second default path loss reference RS based on a DCI that does not include a second SRI field. The wireless device may determine the second default path loss reference RS among one or more path loss reference RSs activated / indicated / updated by one or more active commands based, for example, on one or more configuration parameters including a path loss RS update parameter.

[0285] The second default path loss reference RS may be mapped to a second power control parameter set among a plurality of power control parameter sets indicated / identified by a second power control parameter set index (e.g., sri-PUSCH-PowerControlId) equal to a second value. The plurality of power control parameter set indexes may include the second power control parameter index. For example, the second value may be equal to 1 (e.g., path loss RS23 mapped to sri-PUSCH-PowerControl 1 in FIG. 19). The second value may be equal to 0, for example.

[0286] The second default path loss reference RS may be mapped to a second power control parameter set among the multiple power control parameter sets that is indicated / identified by a highest second power control parameter set index (e.g., sri-PUSCH-PowerControlId) among the multiple power control parameter set indices (e.g., path loss RS41 in FIG. 19 is mapped to sri-PUSCH-PowerControlN). The multiple power control parameter set indices may include the second power control parameter set index.

[0287] The one or more configuration parameters may, for example, indicate a second default path loss reference RS.

[0288] The one or more configuration parameters may indicate a second reference signal (e.g., CSI-RS, SS / PBCH block) for the second default path loss reference RS. The second default path loss reference RS may include a second reference signal index (e.g., provided by higher layer parameters referenceSignal, ssb-index, csi-RS-Index, NZP-CSI-RS-ResourceId) that indicates / identifies the second reference signal.

[0289] In one example, the wireless device may determine / calculate / compute a first transmit power of the plurality of transmit powers based on a first path loss reference RS indicated by (or mapped to) a first power control parameter set. The wireless device may determine / calculate / compute the first transmit power based on a first reference signal indicated by the first path loss reference RS. The wireless device may determine / calculate / compute a second transmit power of the plurality of transmit powers based on a second default path loss reference RS. The wireless device may determine / calculate / compute the second transmit power based on a second reference signal indicated by the second default path loss reference RS.

[0290] 17 and 19, the first SRS resource set may include a single SRS resource (e.g., SRS resource 1 in FIG. 17), and the second SRS resource set may include a single SRS resource (e.g., SRS resource set 2 in FIG. 17).

[0291] The DCI may not include the first SRI field (or the first TCI field) based on a first SRS resource set that includes a single SRS resource. The DCI may not include the second SRI field (or the second TCI field) based on a second SRS resource set that includes a single SRS resource. The DCI may not include the first SRI field based on a first SRS resource set that does not include more than one SRS resource. The DCI may not include the second SRI field based on a second SRS resource set that does not include more than one SRS resource. The DCI may not include the first SRI field and the second SRI field (e.g., SRI fields not shown in Figures 17 and 19).

[0292] In Figure 17, the wireless device may determine / select a first default path loss reference RS from among multiple path loss reference RSs. The wireless device may determine the first default path loss reference RS based on a DCI that does not include a first SRI field. The wireless device may determine a second default path loss reference RS from among the multiple path loss reference RSs. The wireless device may determine the second default path loss reference RS based on a DCI that does not include a second SRI field.

[0293] In FIG. 19, the wireless device may determine a first default path loss reference RS among one or more path loss reference RSs. The wireless device may determine the first default path loss reference RS based on a DCI that does not include a first SRI field. The wireless device may determine the first default path loss reference RS among one or more path loss reference RSs activated / indicated / updated by one or more active commands, for example, based on one or more configuration parameters including a path loss RS update parameter. The wireless device may determine a second default path loss reference RS among one or more path loss reference RSs. The wireless device may determine the second default path loss reference RS based on a DCI that does not include a second SRI field. The wireless device may determine the second default path loss reference RS among one or more path loss reference RSs activated / indicated / updated by one or more active commands, for example, based on one or more configuration parameters including a path loss RS update parameter.

[0294] The one or more configuration parameters may, for example, indicate a second default path loss reference RS.

[0295] In FIG. 18, one or more configuration parameters may not indicate multiple power control parameter sets (eg, SRI-PUSCH-PowerControl), for example.

[0296] For example, the DCI may or may not include a first SRI field. For example, the DCI may or may not include a second SRI field.

[0297] In one example, the wireless device may determine / select a first default path loss reference RS from among the plurality of path loss reference RSs. The wireless device may determine the first default path loss reference RS based on one or more configuration parameters that do not indicate the plurality of power control parameter sets.

[0298] In one example, the wireless device may determine a second default path loss reference RS from among the plurality of path loss reference RSs. The wireless device may determine the second default path loss reference RS based on one or more configuration parameters that do not indicate the plurality of power control parameter sets.

[0299] 17 and 18, the first default path loss reference RS may be indicated / identified by a first path loss reference RS index (e.g., PUSCH-PathlossReferenceRS-Id) equal to a first value. The multiple path loss reference RS indexes may include the first path loss reference RS index. The first value may be equal to zero (e.g., path loss RS0), for example. The multiple path loss reference RSs may include the first default path loss reference RS.

[0300] 19, the first default path loss reference RS may be mapped to a first power control parameter set among a plurality of power control parameter sets indicated / identified by a first power control parameter set index (e.g., sri-PUSCH-PowerControlId) equal to a first value. The plurality of power control parameter set indexes may include the first power control parameter set index. For example, the first value may be equal to zero (e.g., path loss RS47 mapped to sri-PUSCH-PowerControl0 in FIG. 19). The one or more path loss reference RSs may include the first default path loss reference RS.

[0301] The first value may be, for example, predefined / fixed / preconfigured. The second value may be, for example, predefined / fixed / preconfigured.

[0302] The one or more configuration parameters may indicate a first reference signal (e.g., CSI-RS, SS / PBCH block) for the first default path loss reference RS. The first default path loss reference RS may include a first reference signal index (e.g., provided by higher layer parameters referenceSignal, ssb-index, csi-RS-Index, NZP-CSI-RS-ResourceId) that indicates / identifies the first reference signal.

[0303] 17 and 18, the second default path loss reference RS may be indicated / identified by a second path loss reference RS index (e.g., PUSCH-PathlossReferenceRS-Id) equal to a second value. The multiple path loss reference RS indices may include the second path loss reference RS index. The second value may be equal to 1 (e.g., Path Loss RS1), for example. The second value may be equal to 0, for example. The multiple path loss reference RSs may include the second default path loss reference RS.

[0304] 17 and 18, the second default path loss reference RS may be indicated / identified by a highest second path loss reference RS index (e.g., PUSCH-PathlossReferenceRS-Id) among multiple path loss reference RS indexes among the multiple path loss reference RSs (e.g., path loss RS M). The multiple path loss reference RS indexes may include the second path loss reference RS index. The multiple path loss reference RSs may include the second default path loss reference RS.

[0305] 19, the second default path loss reference RS may be mapped to a second power control parameter set among a plurality of power control parameter sets indicated / identified by a second power control parameter set (e.g., sri-PUSCH-PowerControlId) equal to a second value. The plurality of power control parameter set indexes may include the second power control parameter set index. For example, the second value may be equal to 1 (e.g., path loss RS23 mapped to sri-PUSCH-PowerControl 1 in FIG. 19). The second value may be equal to 0, for example. The one or more path loss reference RSs may include the second default path loss reference RS.

[0306] 19, the second default path loss reference RS may be mapped to a second power control parameter set among a plurality of power control parameter sets indicated / identified by a highest second power control parameter set index (e.g., sri-PUSCH-PowerControlId) among a plurality of power control parameter set indexes (e.g., path loss RS41 in FIG. 19 is mapped to sri-PUSCH-PowerControlN). The plurality of power control parameter set indexes may include the second power control parameter set index. The one or more path loss reference RSs may include the second default path loss reference RS.

[0307] The one or more configuration parameters may, for example, indicate a second default path loss reference RS.

[0308] The one or more configuration parameters may indicate a second reference signal (e.g., CSI-RS, SS / PBCH block) for the second default path loss reference RS. The second default path loss reference RS may include a second reference signal index (e.g., provided by higher layer parameters referenceSignal, ssb-index, csi-RS-Index, NZP-CSI-RS-ResourceId) that indicates / identifies the second reference signal.

[0309] In one example, the wireless device may determine / calculate / compute a first transmit power of the plurality of transmit powers based on a first default path loss reference RS. The wireless device may determine / calculate / compute the first transmit power based on a first reference signal indicated by the first default path loss reference RS. The wireless device may determine / calculate / compute a second transmit power of the plurality of transmit powers based on a second default path loss reference RS. The wireless device may determine / calculate / compute the second transmit power based on a second reference signal indicated by the second default path loss reference RS.

[0310] A wireless device may transmit a transport block (or a first portion of a transport block or one or more first data layers / streams of a transport block) with / using a first transmit power. The wireless device may transmit a transport block at one or more first uplink signal / channel transmission opportunities (e.g., times T2a and T2c in FIGS. 17 and 18 and time T3a in FIG. 19) with / using a first transmit power. The wireless device may transmit a transport block (or a second portion of a transport block or one or more second data layers / streams of a transport block) with / using a second transmit power. The wireless device may transmit a transport block at one or more second uplink signal / channel transmission opportunities (e.g., times T2b and T2d in FIGS. 17 and 18 and time T3b in FIG. 19) with / using a second transmit power.

[0311] The wireless device may transmit the transport block over the active uplink BWP of the cell.

[0312] In one example, the first reference signal indicated by the first default path loss reference RS or the first path loss reference RS may be periodic. The second reference signal indicated by the second default path loss reference RS or the second path loss reference RS may be periodic. The first reference signal may be periodic with a first periodicity (e.g., 2 slots, 5 slots, 10 slots, 2 symbols, 5 symbols, etc.). The second reference signal may be periodic with a second periodicity (e.g., 3 slots, 7 slots, 10 slots, 2 symbols, 4 symbols, etc.). One or more configuration parameters may indicate the first periodicity. One or more configuration parameters may indicate the second periodicity. The wireless device may periodically measure, for example, L1-RSRP, L3-RSRP, of the first reference signal based on the first reference signal being periodic. The wireless device may periodically measure, for example, L1-RSRP, L3-RSRP, of the second reference signal based on the second reference signal being periodic.

[0313] In one example, one or more configuration parameters may not indicate a reference cell for the cell (e.g., by the higher layer parameter pathlossReferenceLinking). When one or more configuration parameters do not indicate a reference cell, a reference signal (e.g., the first reference signal, the second reference signal in FIGS. 17-19) may be indicated by a pathloss reference RS (e.g., the first pathloss reference RS, the second pathloss reference RS, the first default pathloss reference RS, the second default pathloss reference RS in FIGS. 17-19) and may be transmitted on / via the cell. When one or more configuration parameters do not indicate a reference cell, the base station may transmit a reference signal on / via the cell. When one or more configuration parameters do not indicate a reference cell, the base station may configure a reference signal for the cell. When one or more configuration parameters do not indicate a reference cell, the one or more configuration parameters may indicate a reference signal for the cell. In one example, an RS resource for the reference signal may be on the cell.

[0314] In one example, the one or more configuration parameters may indicate a reference cell for the cell (e.g., via the upper layer parameter pathlossReferenceLinking). In one example, the reference cell may be different from the cell. In one example, the reference cell may be the same as the cell. Based on the one or more configuration parameters indicating a reference cell for the cell, a reference signal (e.g., the first reference signal, the second reference signal in FIGS. 17-19) may be indicated by a pathloss reference RS (e.g., the first pathloss reference RS, the second pathloss reference RS, the first default pathloss reference RS, the second default pathloss reference RS in FIGS. 17-19) and transmitted on / via the reference cell. Based on the one or more configuration parameters indicating the reference cell for the cell, the base station may transmit the reference signal on / via the reference cell. Based on the one or more configuration parameters indicating the reference cell for the cell, the base station may configure the reference signal for the reference cell. Based on the one or more configuration parameters indicating the reference cell for the cell, the one or more configuration parameters may indicate a reference signal for the reference cell. In one example, the reference cell may be for pathloss estimation of the cell. In one example, the wireless device may measure a reference signal of a reference cell for cell path loss estimation. In one example, the RS resource for the reference signal may be on the reference cell. The value of a higher layer parameter pathlossReferenceLinking may indicate the reference cell.

[0315] 17 to 19, the wireless device may determine a first default path loss reference RS based on, for example, one or more configuration parameters indicating at least two SRS resource sets with an SRS usage parameter set set in a codebook. The wireless device may determine a first default path loss reference RS based on, for example, one or more configuration parameters indicating at least two SRS resource sets with an SRS usage parameter set set in a non-codebook.

[0316] 17 to 19, the wireless device may determine the second default path loss reference RS based on, for example, one configuration parameter indicating at least two SRS resource sets accompanied by an SRS usage parameter set in a codebook. The wireless device may determine the second default path loss reference RS based on, for example, one or more configuration parameters indicating at least two SRS resource sets accompanied by an SRS usage parameter set in a non-codebook.

[0317] In one example, a wireless device is provided with (e.g., transmits to and / or receives from) multiple TRPs. The wireless device may determine a first default path loss reference RS and a second default path loss reference RS based on being provided by the multiple TRPs. The wireless device may determine the first default path loss reference RS based on being provided by the multiple TRPs. The wireless device may determine the second default path loss reference RS based on being provided by the multiple TRPs.

[0318] The wireless device may determine the first default path loss reference RS and the second default path loss reference RS based on the DCI indicating repetition of the transport block, for example, towards / to multiple TRPs.

[0319] The wireless device may determine the first default path loss reference RS based on the DCI indicating repetition of a transport block, for example, towards / to multiple TRPs.

[0320] The wireless device may determine the second default path loss reference RS based on the DCI indicating repetition of the transport block, for example, towards / to multiple TRPs.

[0321] In one example, the wireless device may determine the first default path loss reference RS and the second default path loss reference RS based on one or more configuration parameters including an enablement parameter. The enablement parameter may be set to “enabled.” The one or more configuration parameters may indicate “enabled” for the enablement parameter.

[0322] In one example, the wireless device may determine the second default path loss reference RS based on one or more configuration parameters including an enablement parameter. The enablement parameter may be set to “enabled.” The one or more configuration parameters may indicate “enabled” for the enablement parameter.

[0323] In one example, the wireless device may determine the first default path loss reference RS based on one or more configuration parameters including an enablement parameter. The enablement parameter may be set to “enabled.” The one or more configuration parameters may indicate “enabled” for the enablement parameter.

[0324] In one example, the wireless device may determine the first default path loss reference RS and the second default path loss reference RS based on one or more configuration parameters indicating a repetition scheme (e.g., FDM-Scheme, TDM-Scheme, SDM-Scheme, CDM-Scheme). The repetition scheme may be for repetition of transmission of a transport block (e.g., PUSCH repetition).

[0325] In one example, the wireless device may determine the second default path loss reference RS based on one or more configuration parameters indicating a repetition scheme (e.g., FDM-Scheme, TDM-Scheme, SDM-Scheme, CDM-Scheme). The repetition scheme may be for repetition of transmission of a transport block (e.g., PUSCH repetition).

[0326] In one example, the wireless device may determine the first default path loss reference RS based on one or more configuration parameters indicating a repetition scheme (e.g., FDM-Scheme, TDM-Scheme, SDM-Scheme, CDM-Scheme). The repetition scheme may be for repetition of transmission of a transport block (e.g., PUSCH repetition).

[0327] In one example, the wireless device may determine a first default path loss reference RS and a second default path loss reference RS based on UE capability information that indicates / includes support for beam capability without uplink beam sweeping.

[0328] In one example, the wireless device may determine a first default path loss criterion based on UE capability information that indicates / includes support for beam capability without uplink beam sweeping.

[0329] In one example, the wireless device may determine a second default path loss reference RS based on UE capability information that indicates / includes support for beam capability without uplink beam sweeping.

[0330] In one example, the wireless device may determine the first default path loss reference RS and the second default path loss reference RS based on UE capability information indicating, for example, support for repetition for transmission of a transport block.

[0331] In one example, the wireless device may determine the first default path loss reference RS based on, for example, UE capability information indicating support for repetition for transmission of the transport block.

[0332] In one example, the wireless device may determine the second default path loss reference RS based on, for example, UE capability information indicating support for repetition for transmission of the transport block.

[0333] In one example, determining / calculating / calculating transmit power based on a path loss reference RS may include determining / calculating / calculating transmit power based on a reference signal indicated by the path loss reference RS. Determining / calculating / calculating transmit power based on a reference signal may include determining / calculating / calculating a downlink path loss estimate (or path loss measurement) for the transmit power based on one or more measurement qualities of the reference signal (e.g., L1-RSRP, L3-RSRP, or higher filtered RSRP measurements). The wireless device may use the downlink path loss estimate when determining / calculating / calculating transmit power for transmission of a transport block. The transmit power may include the downlink path loss estimate. In one example, the wireless device may determine / calculate / calculate / measure a filtered RSRP value (e.g., L1-RSRP, L3-RSRP) of the reference signal for the downlink path loss estimate. The wireless device may determine / calculate / calculate / measure the filtered RSRP value for transmission of the transport block.

[0334] In one example, the transmit power may be a first transmit power. The transmit power may be a second transmit power. In one example, the path loss reference RS may be a first path loss reference RS. The path loss reference RS may be a first default path loss reference RS. The path loss reference RS may be a second path loss reference RS. The path loss reference RS may be a second default path loss reference RS. In one example, the reference signal may be a first reference signal. The reference signal may be a second reference signal.

[0335] In one example, determining / calculating / computing the first transmit power based on the first reference signal may include determining / calculating / computing a downlink path loss estimate (or first path loss measurement) for the first transmit power based on the first reference signal (e.g., an L1-RSRP, L3-RSRP, or higher filtered RSRP measurement). The wireless device may use the first downlink path loss estimate in determining / calculating / computing the first transmit power for transmission of the transport block (or a first portion of the transport block, or one or more first data layers / streams of the transport block). The first transmit power may include the first downlink path loss estimate. In one example, the wireless device may determine / calculate / computate / measure a first filtered RSRP (e.g., L1-RSRP, L3-RSRP) of the first reference signal relative to the first downlink path loss estimate. The wireless device may determine / calculate / computate / measure the first filtered RSRP for transmission of the transport block.

[0336] In one example, determining / calculating / computing the second transmit power based on the second reference signal may include determining / calculating / computing a downlink path loss estimate (or second path loss measurement) for the second transmit power based on the second reference signal (e.g., an L1-RSRP, L3-RSRP, or higher filtered RSRP measurement). The wireless device may use the second downlink path loss estimate in determining / calculating / computing the second transmit power for transmission of the transport block (or a second portion of the transport block, or one or more second data layers / streams of the transport block). The second transmit power may include the second downlink path loss estimate. In one example, the wireless device may determine / calculate / computate / measure a second filtered RSRP (e.g., L1-RSRP, L3-RSRP) of the second reference signal for the downlink path loss estimate. The wireless device may determine / calculate / computate / measure the second filtered RSRP for transmission of the transport block.

[0337] FIG. 21 is an example flow diagram of power control in uplink channel repetition according to one aspect of an embodiment of the present disclosure.

[0338] In one example, a wireless device may receive one or more messages. In one example, a wireless device may receive one or more messages from a base station. The one or more messages may include one or more configuration parameters (e.g., RRC configuration parameters, RRC reconfiguration parameters) for a cell.

[0339] The one or more configuration parameters may indicate at least two SRS resource sets. In one example, the one or more configuration parameters may include codebook-configured SRS usage parameters for the at least two SRS resource sets. In one example, the one or more configuration parameters may include non-codebook-configured SRS usage parameters for the at least two SRS resource sets.

[0340] The one or more configuration parameters may indicate a first SRS usage parameter for a first SRS resource set of the at least two SRS resource sets. The first SRS usage parameter may be (or may be set to), for example, a codebook. The first SRS usage parameter may be (or may be set to), for example, a non-codebook. The second SRS usage parameter may be (or may be set to), for example, a codebook. The second SRS usage parameter may be (or may be set to), for example, a non-codebook. The first SRS usage parameter and the second SRS usage parameter may be the same (e.g., both codebooks or both non-codebooks).

[0341] The one or more configuration parameters may include multiple power control parameter sets. The one or more configuration parameters may indicate multiple power control parameter set indexes for the multiple power control parameter sets.

[0342] The one or more configuration parameters may include a plurality of path loss reference RSs. The one or more configuration parameters may indicate a plurality of path loss reference RS indices for the plurality of path loss reference RSs.

[0343] In one example, multiple power control parameter sets may be mapped to multiple path loss reference RSs.

[0344] In one example, the wireless device may receive one or more activate commands to indicate / update / activate one or more path loss reference RSs of the plurality of path loss reference RSs, and the plurality of power control parameter sets may be mapped to the one or more path loss reference RSs.

[0345] The wireless device may transmit a transport block. The wireless device may transmit a transport block via the cell's active uplink BWP. The wireless device may repeat a transport block transmission. The wireless device may transmit a transport block repetition. The wireless device may transmit a transport block over / on / in multiple uplink signal / channel transmission / repetition opportunities (e.g., time slots, subslots, nominal / actual repetitions, symbols). The wireless device may transmit a transport block over / on / in multiple uplink signal / channel transmission / repetition opportunities due to transport block repetition.

[0346] The wireless device may receive, for example, the DCI.

[0347] The DCI may, for example, schedule a transport block, the DCI may schedule a repetition of a transport block, or the DCI may indicate a repetition of a transport block.

[0348] The DCI may, for example, activate a configured uplink grant (e.g., a type 2 configured uplink grant). The wireless device may transmit a transport block for the configured uplink grant. The DCI may indicate repetition of the transport block.

[0349] In one example, the DCI may include a first SRI field. The DCI may include the first SRI field based on the number of SRS resources in the first SRS resource set being greater than or equal to one. The first SRI field (or the value of the first SRI field) may indicate (or be mapped to) a first power control parameter set among multiple power control parameter sets. The wireless device may determine a first path loss criterion RS mapped to (or indicated by or associated with) the first power control parameter set.

[0350] In one example, the plurality of path loss reference RSs may include a first path loss reference RS.

[0351] In one example, the one or more path loss reference RSs may include a first path loss reference RS.

[0352] The wireless device may determine / calculate / compute a first transmit power based on a first reference signal indicated by a first path loss reference RS.

[0353] The wireless device may determine a first spatial-domain transmit filter based on the first SRS resource indicated by the first SRI field. The first SRS resource set may include the first SRS resource.

[0354] In one example, the DCI may include a second SRI field. The DCI may include the second SRI field based on the number of SRS resources in the second SRS resource set being one or more. The second SRI field (or the value of the second SRI field) may indicate (or be mapped to) a second power control parameter set of the multiple power control parameter sets. The wireless device may determine a second path loss criterion RS mapped to (or indicated by or associated with) the second power control parameter set.

[0355] In one example, the plurality of path loss reference RSs may include a second path loss reference RS. In one example, the one or more path loss reference RSs may include a second path loss reference RS.

[0356] The wireless device may determine / calculate / compute a second transmit power based on a second reference signal indicated by a second path loss reference RS.

[0357] The wireless device may determine a second spatial-domain transmit filter based on the second SRS resource indicated by the second SRI field. The second SRS resource set may include the second SRS resource.

[0358] In one example, the DCI may not include a first SRI field. The DCI may not include the first SRI field based on the number of SRS resources in the first SRS resource set being 1. The wireless device may determine a first default path loss reference RS. The first SRS resource set may include a single SRS resource.

[0359] In one example, the plurality of path loss reference RSs may include a first default path loss reference RS. The first default path loss reference RS may be identified / indicated by a first path loss reference RS index equal to a first value (e.g., zero). The plurality of path loss reference RS indexes may include the first path loss reference RS index.

[0360] In one example, the one or more path loss reference RSs may include a first default path loss reference RS. The first default path loss reference RS may be mapped to (or indicated by) a first power control parameter set of the multiple power control parameter sets. The first power control parameter set may be identified / indicated by a first power control parameter set index equal to a first value (e.g., zero). The multiple power control parameter set indexes may include the first power control parameter set index.

[0361] The wireless device may determine / calculate / calculate a first transmit power based on a first reference signal indicated by a first default path loss reference RS.

[0362] The wireless device may determine a first spatial-domain transmit filter based on a first SRS resource in a first SRS resource set. The first SRS resource may be a single SRS resource in the first SRS resource set.

[0363] In one example, the DCI may not include a second SRI field. The DCI may not include a second SRI field based on the number of SRS resources in the second SRS resource set being 1. The wireless device may determine a second default path loss reference RS. The second SRS resource set may include a single SRS resource.

[0364] In one example, the multiple path loss reference RSs may include a second default path loss reference RS. The second default path loss reference RS may be identified / indicated, for example, by a second path loss reference RS index equal to a second value (e.g., 1). The second default path loss reference RS may be identified / indicated, for example, by a highest second path loss reference RS index among the multiple path loss reference RS indexes of the multiple path loss reference RSs. The multiple path loss reference RS indexes may include the second path loss reference RS index. The one or more configuration parameters may indicate, for example, the second default path loss reference RS.

[0365] In one example, the one or more path loss reference RSs may include a second default path loss reference RS. The second default path loss reference RS may be mapped to (or indicated by) a second power control parameter set of the multiple power control parameter sets. The second power control parameter set may be identified / indicated, for example, by a second power control parameter set index equal to a second value (e.g., 1). The second power control parameter set may be identified / indicated, for example, by a highest second power control parameter set index among multiple power control parameter set indexes of the multiple power control parameter sets. The multiple power control parameter set indexes may include the second power control parameter set index.

[0366] The one or more configuration parameters may, for example, indicate a second default path loss reference RS.

[0367] The wireless device may determine / calculate / compute a second transmit power based on a second reference signal indicated by a second default path loss reference RS.

[0368] The wireless device may determine a second spatial-domain transmit filter based on a second SRS resource in the second SRS resource set. The second SRS resource may be a single SRS resource in the second SRS resource set.

[0369] The wireless device may transmit a transport block with / using a first transmit power and a second transmit power.

[0370] The wireless device may transmit a transport block (or a first portion of the transport block, or one or more first data layers / streams of the transport block, or one or more first symbols of the transport block) with / using a first transmit power. The wireless device may transmit the transport block in one or more first uplink signal / channel transmission opportunities of a plurality of uplink signal / channel transmission opportunities with / using the first transmit power.

[0371] The wireless device may transmit the transport block (or a second portion of the transport block, or one or more second data layers / streams of the transport block, or one or more second symbols of the transport block) with / using a second transmit power. The wireless device may transmit the transport block in one or more second uplink signal / channel transmission opportunities of the multiple uplink signal / channel transmission opportunities with / using the second transmit power.

[0372] The wireless device may transmit a transport block with / using a first spatial-domain transmit filter and a second spatial-domain transmit filter.

[0373] The wireless device may transmit a transport block (or a first portion of the transport block, or one or more first data layers / streams of the transport block, or one or more first symbols of the transport block) with / using a first spatial-domain transmit filter. The wireless device may transmit the transport block in one or more first uplink signal / channel transmission opportunities of a plurality of uplink signal / channel transmission opportunities with / using the first spatial-domain transmit filter.

[0374] The wireless device may transmit the transport block (or a second portion of the transport block, or one or more second data layers / streams of the transport block, or one or more second symbols of the transport block) with / using a second spatial-domain transmit filter. The wireless device may transmit the transport block in one or more second uplink signal / channel transmission opportunities of the multiple uplink signal / channel transmission opportunities with / using the second spatial-domain transmit filter.

[0375] The wireless device may determine the first default path loss reference RS, for example, based on the DCI not including the first SRI field. The wireless device may determine the first default path loss reference RS, for example, based on the DCI indicating transport block repetition. The wireless device may determine the first default path loss reference RS, for example, based on one or more configuration parameters (or values ​​of one or more parameters in the one or more configuration parameters). The wireless device may determine the first default path loss reference RS, for example, based on the DCI (or values ​​of one or more fields in the DCI). The wireless device may determine the first default path loss reference RS, for example, based on the one or more configuration parameters indicating at least two SRS resource sets, accompanied by a codebook (or non-codebook).

[0376] The wireless device may determine the second default path loss reference RS, for example, based on the DCI not including a second SRI field. The wireless device may determine the second default path loss reference RS, for example, based on the DCI indicating transport block repetition. The wireless device may determine the second default path loss reference RS, for example, based on one or more configuration parameters (or values ​​of one or more parameters in the one or more configuration parameters). The wireless device may determine the second default path loss reference RS, for example, based on the DCI (or values ​​of one or more fields in the DCI). The wireless device may determine the second default path loss reference RS, for example, based on the one or more configuration parameters indicating at least two SRS resource sets with a codebook (or non-codebook).

[0377] In one example, the one or more configuration parameters may indicate a number of repetitions. In one example, the DCI may indicate a number of repetitions. For example, the number of repetitions may be for repetitions of transmission of a transport block (e.g., PUSCH, PDSCH) over uplink resources (e.g., PUCCH resources, SRS resources, PUSCH resources). In one example, the number of repetitions may indicate a number of uplink signal / channel transmission opportunities (e.g., PUSCH transmission opportunities, PUCCH transmission opportunities) for transmission of the transport block. The number of the multiple uplink signal / channel transmission opportunities may be equal to the number of repetitions.

[0378] FIG. 22 is an example flow diagram of power control in uplink channel repetition according to one aspect of an embodiment of the present disclosure.

[0379] The discussion of the first two steps in FIG. 21 (eg, receiving one or more configuration parameters and DCI) is also applicable for the first two steps in FIG.

[0380] In one example, the DCI may include a first SRI field. The DCI may include the first SRI field based on the number of SRS resources in the first SRS resource set being greater than or equal to one. The first SRI field (or the value of the first SRI field) may indicate (or be mapped to) a first power control parameter set among multiple power control parameter sets. The wireless device may determine a first path loss criterion RS mapped to (or indicated by or associated with) the first power control parameter set.

[0381] In one example, the plurality of path loss reference RSs may include a first path loss reference RS. In one example, the one or more path loss reference RSs may include a first path loss reference RS.

[0382] The wireless device may determine / calculate / compute a first transmit power based on a first reference signal indicated by a first path loss reference RS.

[0383] The wireless device may determine a first spatial-domain transmit filter based on the first SRS resource indicated by the first SRI field. The first SRS resource set may include the first SRS resource.

[0384] In one example, the DCI may not include a second SRI field. The DCI may not include a second SRI field based on the number of SRS resources in the second SRS resource set being 1. The second SRS resource set may include a single SRS resource.

[0385] The wireless device may determine / calculate / compute the second transmit power based on a first reference signal indicated by the first path loss reference RS. The wireless device may determine / calculate / compute the second transmit power based on the first reference signal indicated by the first path loss reference RS, for example, in response to a DCI including a first SRI field indicating (or associated with) the first path loss reference RS. The wireless device may determine / calculate / compute the second transmit power based on the first reference signal indicated by the first path loss reference RS, for example, in response to a DCI that does not include a second SRI field.

[0386] The wireless device may determine a second spatial-domain transmit filter based on a second SRS resource in the second SRS resource set. The second SRS resource may be a single SRS resource in the second SRS resource set.

[0387] In one example, the DCI may include a second SRI field. The DCI may include the second SRI field based on the number of SRS resources in the second SRS resource set being one or more. The second SRI field (or the value of the second SRI field) may indicate (or be mapped to) a second power control parameter set of the multiple power control parameter sets. The wireless device may determine a second path loss criterion RS mapped to (or indicated by or associated with) the second power control parameter set.

[0388] In one example, the plurality of path loss reference RSs may include a second path loss reference RS. In one example, the one or more path loss reference RSs may include a second path loss reference RS.

[0389] The wireless device may determine / calculate / compute a second transmit power based on a second reference signal indicated by a second path loss reference RS.

[0390] The wireless device may determine a second spatial-domain transmit filter based on the second SRS resource indicated by the second SRI field. The second SRS resource set may include the second SRS resource.

[0391] In one example, the DCI may not include a first SRI field. The DCI may not include a first SRI field based on the number of SRS resources in the first SRS resource set being 1. The first SRS resource set may include a single SRS resource.

[0392] The wireless device may determine / calculate / compute the first transmit power based on a second reference signal indicated by the second path loss reference RS. The wireless device may determine / calculate / compute the first transmit power based on a second reference signal indicated by the second path loss reference RS, for example, in response to a DCI including a second SRI field indicating (or associated with) the second path loss reference RS. The wireless device may determine / calculate / compute the first transmit power based on a second reference signal indicated by the second path loss reference RS, for example, in response to a DCI that does not include a first SRI field.

[0393] The wireless device may determine a first spatial-domain transmit filter based on a first SRS resource in a first SRS resource set. The first SRS resource may be a single SRS resource in the first SRS resource set.

[0394] The wireless device may transmit a transport block with / using a first transmit power and a second transmit power.

[0395] The wireless device may transmit a transport block (or a first portion of the transport block, or one or more first data layers / streams of the transport block, or one or more first symbols of the transport block) with / using a first transmit power. The wireless device may transmit the transport block in one or more first uplink signal / channel transmission opportunities of a plurality of uplink signal / channel transmission opportunities with / using the first transmit power.

[0396] The wireless device may transmit the transport block (or a second portion of the transport block, or one or more second data layers / streams of the transport block, or one or more second symbols of the transport block) with / using a second transmit power. The wireless device may transmit the transport block in one or more second uplink signal / channel transmission opportunities of the multiple uplink signal / channel transmission opportunities with / using the second transmit power.

[0397] The wireless device may transmit a transport block with / using a first spatial-domain transmit filter and a second spatial-domain transmit filter.

[0398] The wireless device may transmit a transport block (or a first portion of the transport block, or one or more first data layers / streams of the transport block, or one or more first symbols of the transport block) with / using a first spatial-domain transmit filter. The wireless device may transmit the transport block in one or more first uplink signal / channel transmission opportunities of a plurality of uplink signal / channel transmission opportunities with / using the first spatial-domain transmit filter.

[0399] The wireless device may transmit the transport block (or a second portion of the transport block, or one or more second data layers / streams of the transport block, or one or more second symbols of the transport block) with / using a second spatial-domain transmit filter. The wireless device may transmit the transport block in one or more second uplink signal / channel transmission opportunities of the multiple uplink signal / channel transmission opportunities with / using the second spatial-domain transmit filter.

[0400] FIG. 23 is an example flow diagram of power control in uplink channel repetition according to one aspect of an embodiment of the present disclosure.

[0401] One or more configuration parameters discussed in FIG. 21 may not indicate one or more power control parameter sets.

[0402] In one example, the DCI discussed in Figure 21 may or may not include a first SRI field. The wireless device may determine a first default path loss reference RS. The wireless device may determine the first default path loss reference RS, for example, based on one or more configuration parameters not indicating one or more power control parameter sets.

[0403] In one example, the plurality of path loss reference RSs may include a first default path loss reference RS. The first default path loss reference RS may be identified / indicated by a first path loss reference RS index equal to a first value (e.g., zero). The plurality of path loss reference RS indexes may include the first path loss reference RS index.

[0404] The wireless device may determine / calculate / compute a first transmit power based on a first reference signal indicated by a first default path loss reference RS.

[0405] In one example, the DCI discussed in Figure 21 may or may not include a second SRI field. The wireless device may determine a second default path loss reference RS. The wireless device may determine the second default path loss reference RS, for example, based on one or more configuration parameters not indicating one or more power control parameter sets.

[0406] In one example, the multiple path loss reference RSs may include a second default path loss reference RS. The second default path loss reference RS may be identified / indicated, for example, by a second path loss reference RS index equal to a second value (e.g., 1). The second default path loss reference RS may be identified / indicated, for example, by a second path loss reference RS index that is the highest among the multiple path loss reference RS indexes of the multiple path loss reference RSs. The multiple path loss reference RS indexes may include the second path loss reference RS index.

[0407] The one or more configuration parameters may, for example, indicate a second default path loss reference RS.

[0408] The wireless device may determine / calculate / compute a second transmit power based on a second reference signal indicated by a second default path loss reference RS.

[0409] The wireless device may transmit a transport block with / using a first transmit power and a second transmit power.

[0410] The wireless device may transmit a transport block (or a first portion of the transport block, or one or more first data layers / streams of the transport block, or one or more first symbols of the transport block) with / using a first transmit power. The wireless device may transmit the transport block in one or more first uplink signal / channel transmission opportunities of a plurality of uplink signal / channel transmission opportunities with / using the first transmit power.

[0411] The wireless device may transmit the transport block (or a second portion of the transport block, or one or more second data layers / streams of the transport block, or one or more second symbols of the transport block) with / using a second transmit power. The wireless device may transmit the transport block in one or more second uplink signal / channel transmission opportunities of the multiple uplink signal / channel transmission opportunities with / using the second transmit power.

[0412] The wireless device may determine the first default path loss reference RS, for example, based on the DCI indicating transport block repetition. The wireless device may determine the first default path loss reference RS, for example, based on one or more configuration parameters (or values ​​of one or more parameters in the one or more configuration parameters). The wireless device may determine the first default path loss reference RS, for example, based on the DCI (or values ​​of one or more fields in the DCI). The wireless device may determine the first default path loss reference RS, for example, based on the one or more configuration parameters indicating at least two SRS resource sets accompanied by a codebook (or non-codebook).

[0413] The wireless device may determine the second default path loss reference RS, for example, based on the DCI indicating transport block repetition. The wireless device may determine the second default path loss reference RS, for example, based on one or more configuration parameters (or values ​​of one or more parameters in the one or more configuration parameters). The wireless device may determine the second default path loss reference RS, for example, based on the DCI (or values ​​of one or more fields in the DCI). The wireless device may determine the second default path loss reference RS, for example, based on the one or more configuration parameters indicating at least two SRS resource sets with a codebook (or non-codebook).

[0414] FIG. 24 is an example flow diagram of power control in uplink channel repetition according to one aspect of an embodiment of the present disclosure.

[0415] In one example, the base station may decide to transmit, for example, to the wireless device, one or more messages including one or more configuration parameters for the cell (eg, RRC configuration parameters, RRC reconfiguration parameters).

[0416] The one or more configuration parameters may indicate at least two SRS resource sets. In one example, the one or more configuration parameters may include codebook-configured SRS usage parameters for the at least two SRS resource sets. In one example, the one or more configuration parameters may include non-codebook-configured SRS usage parameters for the at least two SRS resource sets.

[0417] The one or more configuration parameters may indicate a first SRS usage parameter for a first SRS resource set of the at least two SRS resource sets. The first SRS usage parameter may be (may be set to), for example, a codebook. The first SRS usage parameter may be (may be set to), for example, a non-codebook. The second SRS usage parameter may be (may be set to), for example, a codebook. The second SRS usage parameter may be (may be set to), for example, a non-codebook. The first SRS usage parameter and the second SRS usage parameter may be the same (e.g., both codebooks or both non-codebooks).

[0418] The base station may configure multiple SRS resources in the second SRS resource set. The base station may configure multiple SRS resources in the second SRS resource set, for example, based on one or more configuration parameters indicating at least two SRS resource sets. The base station may configure multiple SRS resources in the second SRS resource set, for example, based on one or more configuration parameters indicating at least two SRS resource sets with an SRS usage parameter set to a codebook or a non-codebook. The base station may not configure a single SRS resource in the second SRS resource set, for example, based on one or more configuration parameters indicating at least two SRS resource sets. The base station may not configure a single SRS resource in the second SRS resource set, for example, based on one or more configuration parameters indicating at least two SRS resource sets with an SRS usage parameter set to a codebook or a non-codebook.

[0419] A base station may configure multiple path loss reference RSs (e.g., PUSCH-PathlossReferenceRS). A base station may configure multiple path loss reference RSs for path loss estimation of uplink channels (e.g., PUSCH, PUCCH, SRS). A base station may configure multiple path loss reference RSs, for example, based on one or more configuration parameters indicating at least two SRS resource sets. A base station may configure multiple path loss reference RSs, for example, based on one or more configuration parameters indicating at least two SRS resource sets with an SRS usage parameter set to a codebook or a non-codebook. A base station may not configure a single path loss reference RS, for example, based on one or more configuration parameters indicating at least two SRS resource sets with an SRS usage parameter set to a codebook or a non-codebook. A base station may not configure a single path loss reference RS, for example, based on one or more configuration parameters indicating at least two SRS resource sets with an SRS usage parameter set to a codebook or a non-codebook.

[0420] A base station may configure multiple power control parameter sets (e.g., SRI-PUSCH-PowerControl). A base station may configure multiple power control parameter sets for path loss estimation of uplink channels (e.g., PUSCH, PUCCH, SRS). A base station may configure multiple power control parameter sets, for example, based on one or more configuration parameters indicating at least two SRS resource sets. A base station may configure multiple power control parameter sets, for example, based on one or more configuration parameters indicating at least two SRS resource sets with an SRS usage parameter set in a codebook or a non-codebook. A base station may not configure a single power control parameter set, for example, based on one or more configuration parameters indicating at least two SRS resource sets with an SRS usage parameter set in a codebook or a non-codebook. A base station may not configure a single power control parameter set, for example, based on one or more configuration parameters indicating at least two SRS resource sets with an SRS usage parameter set in a codebook or a non-codebook.

[0421] The base station may transmit one or more messages containing one or more configuration parameters.

[0422] The one or more configuration parameters may indicate multiple SRS resource sets in the second SRS resource set.

[0423] The one or more configuration parameters may indicate multiple path loss reference RSs.

[0424] The one or more configuration parameters may indicate multiple power control parameter sets.

[0425] In Figures 17 to 24, the DCI may include an SRI field (or a single SRI field). The SRI field may include (or consist of) a first SRI field and a second SRI field. The size / length of the SRI field may be 2*n. The size / length of the first SRI field may be n. The size / length of the second SRI field may be n. For example, the size / length of the SRI field may be 2. The size / length of the first SRI field may be 1. The size / length of the second SRI field may be 1. For example, the size / length of the SRI field may be 4. The size / length of the first SRI field may be 2. The size / length of the second SRI field may be 2. For example, the size / length of the SRI field may be 6. The size / length of the first SRI field may be 3. The size / length of the second SRI field may be 3. For example, the SRI field may include multiple bits. The plurality of bits may be bit 0, bit 1, bit 2, and bit 3. The first half of the plurality of bits in the SRI field may indicate a first SRI field (e.g., bit 0, bit 1). The second half of the plurality of bits in the SRI field may indicate a second SRI field (e.g., bit 2, bit 3).

[0426] A DCI that does not include a first SRI field may include an SRI field that does not include the first SRI field, and a DCI that does not include a second SRI field may include an SRI field that does not include the second SRI field.

[0427] The example embodiments of Figures 17-24 may be applicable to DCI scheduling multiple transport blocks. A wireless device may transmit a first transport block of the multiple transport blocks over / on / in one or more first uplink signal / channel transmission opportunities of the multiple uplink signal / channel transmission opportunities. The wireless device may transmit the first transport block with / using (or based on) a first transmit power. The wireless device may transmit a second transport block of the multiple transport blocks over / on / in one or more second uplink signal / channel transmission opportunities of the multiple uplink signal / channel transmission opportunities. The wireless device may transmit the second transport block with / using (or based on) a second transmit power.

Claims

1. 1. A method comprising: receiving, by a wireless device, downlink control information (DCI) that schedules uplink repetitions of a physical uplink shared channel (PUSCH) transmission; Based on the absence of a sounding reference signal resource indicator (SRI) field in the DCI, a first repetition of the PUSCH transmission with a first transmit power based on a first path loss reference signal (RS) with an index equal to zero; and transmitting a second repetition of the PUSCH transmission with a second transmit power based on a second path loss criterion RS with an index equal to one.

2. the first path loss reference RS is a first default path loss reference RS; The method of claim 1 , wherein the second path loss reference RS is a second default path loss reference RS.

3. Based on the SRI field not being present in the DCI, the first path loss reference RS with an index equal to zero as the first default path loss reference RS; The method of claim 2 , further comprising: selecting the second path loss reference RS with an index equal to 1 as the second default path loss reference RS.

4. 2. The method of claim 1, wherein the transmitting is further based on both a first SRI field and a second SRI field being absent from the DCI, and the DCI does not include any SRI fields.

5. The method further includes receiving one or more messages including one or more configuration parameters, the one or more configuration parameters being: a first sounding reference signal (SRS) resource set; and and a second SRS resource set.

6. based on the number of SRS resources in the first SRS resource set being equal to one, the first SRI field is not present in the DCI; The method of claim 5 , wherein the second SRI field is not present in the DCI based on a number of SRS resources in the second SRS resource set being equal to one.

7. the one or more configuration parameters indicate a plurality of indexes for a plurality of path loss criterion RSs, including the first path loss criterion RS and the second path loss criterion RS; 6. The method of claim 5, wherein each path loss criterion RS of the plurality of path loss criterion RSs is indicated by a respective index of the plurality of indexes including the index of the first path loss criterion RS and the index of the second path loss criterion RS.

8. the first transmit power based on a first reference signal indicated by the first path loss reference RS with an index of zero; The method of claim 7 , further comprising: determining the second transmit power based on a second reference signal indicated by the second path loss reference RS with an index of 1.

9. 6. The method of claim 5, wherein the one or more configuration parameters indicate an SRS usage parameter set to a codebook or a non-codebook resource set for both the first SRS resource set and the second SRS resource set.

10. 2. The method of claim 1, wherein the DCI includes a Time Domain Resource Alignment (TDRA) field indicating a number of repetitions of the PUSCH transmission.

11. 1. A wireless device, comprising: one or more processors; When executed by the one or more processors, the wireless device receiving downlink control information (DCI) that schedules uplink repetitions of a physical uplink shared channel (PUSCH) transmission; Based on the absence of a sounding reference signal resource indicator (SRI) field in the DCI, a first repetition of the PUSCH transmission with a first transmit power based on a first path loss reference reference signal (RS) with an index equal to zero; and transmit a second repetition of the PUSCH transmission with a second transmit power based on a second path loss criterion RS with an index equal to 1; A wireless device comprising: a memory that stores instructions.

12. the first path loss reference RS is a first default path loss reference RS; The wireless device of claim 11 , wherein the second path loss reference RS is a second default path loss reference RS.

13. The instructions further include causing the wireless device to: Based on the SRI field not being present in the DCI, the first path loss reference RS with an index equal to zero as the first default path loss reference RS; The wireless device of claim 12 , further comprising: selecting the second path loss reference RS with an index equal to 1 as the second default path loss reference RS.

14. 12. The wireless device of claim 11, wherein the transmitting is further based on both a first SRI field and a second SRI field being absent from the DCI, the DCI not including any SRI fields.

15. The instructions further cause the wireless device to receive one or more messages including one or more configuration parameters, the one or more configuration parameters comprising: a first sounding reference signal (SRS) resource set; and and a second SRS resource set.

16. based on the number of SRS resources in the first SRS resource set being equal to one, the first SRI field is not present in the DCI; 16. The wireless device of claim 15, wherein the second SRI field is not present in the DCI based on a number of SRS resources in the second SRS resource set being equal to one.

17. the one or more configuration parameters indicate a plurality of indexes for a plurality of path loss criterion RSs, including the first path loss criterion RS and the second path loss criterion RS; 16. The wireless device of claim 15, wherein each path loss reference RS of the plurality of path loss reference RSs is indicated by a respective index of the plurality of indexes including the index of the first path loss reference RS and the index of the second path loss reference RS.

18. The instructions further include causing the wireless device to: the first transmit power based on a first reference signal indicated by the first path loss reference RS with an index of zero; and the second transmit power based on a second reference signal indicated by the second path loss reference RS having an index of 1.

19. 16. The wireless device of claim 15, wherein the one or more configuration parameters indicate an SRS usage parameter set to a codebook or a non-codebook resource set for both the first SRS resource set and the second SRS resource set.

20. 1. A system comprising:

1. A base station including one or more first processors and a memory storing instructions, the instructions, when executed by the one or more first processors, causing the base station to: a base station transmitting downlink control information (DCI) scheduling uplink repetitions of a physical uplink shared channel (PUSCH) transmission; 1. A wireless device including one or more second processors and a memory storing instructions, the instructions, when executed by the one or more second processors, causing the wireless device to: receiving, from the base station, the DCI scheduling the uplink repetition of the PUSCH transmission; In response to a sounding reference signal resource indicator (SRI) field not being present in the DCI, a first repetition of the PUSCH transmission with a first transmit power based on a first path loss reference signal (RS) mapped to a first one of the power control parameter sets with an index equal to zero; and and a wireless device that transmits a second repetition of the PUSCH transmission with a second transmission power based on a second path loss criterion RS mapped to a second power control parameter set of the power control parameter sets with an index equal to 1.

Images