Determination of the path loss reference signal 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 Art

[0001] Cross-reference of related applications This application claims the benefit of U.S. Provisional Patent Application No. 63 / 125,753, filed on December 15, 2020, which is hereby incorporated by reference in its entirety.

Summary of the Invention

Means for Solving the Problems

[0002] In the present disclosure, various embodiments are presented as examples of how the disclosed technology can be implemented and / or how the disclosed technology can be practiced in an environment and scenario. 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, a way to implement alternative embodiments will become apparent to those skilled in the relevant art. The present embodiments should not be limited by any of the exemplary embodiments. The embodiments of the present disclosure are described based on the accompanying drawings. Limitations, features, and / or elements from the disclosed exemplary embodiments can be combined to create further embodiments within the scope of the present disclosure. Figures highlighting functions and advantages are shown for illustrative purposes only. The disclosed architecture is sufficiently flexible and configurable to be utilized in ways other than those shown. For example, any action listed in any flowchart can be rearranged or optionally used only in some embodiments.

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

[0004] A base station may communicate with a mixture of radio devices. Radio devices and / or base stations may support multiple technologies and / or multiple releases of the same technology. Radio devices may have certain capabilities depending on the category and / or capabilities of the radio device. Where this disclosure refers to a base station communicating with multiple radio devices, this disclosure may refer to a subset of all radio devices in a coverage area. This disclosure may refer, for example, to multiple radio devices of a given LTE or 5G release that have a given capability and are located in a given sector of a base station. Multiple radio devices in this disclosure may refer to a selection of multiple radio devices and / or a subset of all radio devices in a coverage area that operate according to the disclosed method, etc. Multiple base stations or multiple radio devices may exist in a coverage area that do not conform to the disclosed method. For example, those radio devices or base stations may operate based on an older release of LTE or 5G technology. [Brief explanation of the drawing]

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

[0006] [Figure 1A] Examples of mobile communication networks in which embodiments of the present disclosure may be implemented are shown. [Figure 1B] Examples of mobile communication networks in which embodiments of the present disclosure may be implemented are shown. [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] Figure 2A shows an example of a service provided between the protocol layers of the NR user plane protocol stack. [Figure 4A] Figure 2A shows an exemplary downlink data flow through the NR user plane protocol stack. [Figure 4B] This shows an exemplary format for the MAC subheader in a MAC PDU. [Figure 5A] This shows the mapping between the logical channels, transport channels, and physical channels for downlink and uplink, respectively. [Figure 5B] This shows the mapping between the logical channels, transport channels, and physical channels for downlink and uplink, respectively. [Figure 6] This is an illustrative diagram showing the RRC state transitions of the UE. [Figure 7] This shows an example configuration of an NR frame with grouped OFDM symbols. [Figure 8] This shows an exemplary configuration of slots in the time and frequency domains of the NR carrier. [Figure 9] This example demonstrates bandwidth adaptation using three configured BWPs for an NR carrier. [Figure 10A] This shows three carrier aggregation configurations, each with two component carriers. [Figure 10B] This shows an example of how aggregation cells can be composed of one or more PUCCH groups. [Figure 11A] An example of the SS / PBCH block structure and location is shown. [Figure 11B] An example of CSI-RS mapped to the time and frequency domains is shown. [Figure 12A] Examples of three downlink and uplink beam management procedures are shown respectively. [Figure 12B] Examples of three downlink and uplink beam management procedures are shown respectively. [Figure 13A] Examples of a four-step contention-based random access procedure, a two-step contention-free random access procedure, and another two-step random access procedure are shown respectively. [Figure 13B] Examples of a four-step contention-based random access procedure, a two-step contention-free random access procedure, and another two-step random access procedure are shown respectively. [Figure 13C] Examples of a four-step contention-based random access procedure, a two-step contention-free random access procedure, and another two-step random access procedure are shown respectively. [Figure 14A] An example of CORESET configuration for a bandwidth part is shown. [Figure 14B] An example of CCE-to-REG mapping for DCI transmission in CORESET and PDCCH processing is shown. [Figure 15] An example of a wireless device communicating with a base station is shown. [Figure 16A] Exemplary structures for uplink and downlink transmissions are shown. [Figure 16B] Exemplary structures for uplink and downlink transmissions are shown. [Figure 16C] Exemplary structures for uplink and downlink transmissions are shown. [Figure 16D] Exemplary structures for uplink and downlink transmissions are shown. [Figure 17] An example of the repetition of an uplink channel according to one aspect of the exemplary embodiments of the present disclosure is shown. [Figure 18] An example of the repetition of an uplink channel according to one aspect of the exemplary embodiments of the present disclosure is shown. [Figure 19] An example of the repetition of an uplink channel according to one aspect of the exemplary embodiments of the present disclosure is shown. [Figure 20] An uplink repetition scheme according to one aspect of the exemplary embodiments of the present disclosure is shown. [Figure 21] A flowchart of power control in the repetition of an uplink channel according to one aspect of the exemplary embodiments of the present disclosure is shown. [Figure 22] A flowchart of power control in the repetition of an uplink channel according to one aspect of the exemplary embodiments of the present disclosure is shown. [Figure 23] A flowchart of power control in the repetition of an uplink channel according to one aspect of the exemplary embodiments of the present disclosure is shown. [Figure 24] A flowchart of power control in the repetition of an uplink channel according to one aspect of the exemplary embodiments of the present disclosure is shown.

MODE FOR CARRYING OUT THE INVENTION

[0007] (Detailed Description of the Invention) In this specification, “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.” In this specification, the term “may” is interpreted as “for example, may be.” In other words, the term “may” indicates that the phrase following the term “may” is one example of several preferred possibilities, which may or may not be used by one or more of the various embodiments. Where used herein, the terms “comprises” and “consists of” enumerate one or more components of the element described. The term “comprises” is interchangeable with “includes” and does not exclude unlisted components included in the element described. In contrast, “consists of” provides a complete enumeration of one or more components of the element described. Where used herein, the term “based on” should be interpreted as “at least partially based” rather than, for example, “based only on.” As used herein, the term "and / or" represents any possible combination of the enumerated elements. For example, "A, B, and / or C" could mean A, B, C, A and B, A and C, B and C, or A, B, and C.

[0008] If A and B are a set and all elements of A are also elements of B, then A is called a subset of B. In this specification, only non-empty sets and subsets are considered. For example, possible subsets of B = {cell 1, cell 2} are {cell 1}, {cell 2}, and {cell 1, cell 2}. The phrase "based on" (or equivalently "at least based on") indicates that the phrase following the term "based on" is one example of many preferred possibilities in which one or more of the various embodiments may or may not be used. 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 preferred possibilities in which one or more of the various embodiments may or may not be used. The phrase "according to" (or equivalently "at least in accordance with") indicates that the phrase following the phrase "according to" is one example of many preferred possibilities in which one or more of the various embodiments may or may not be used. The phrase “adopt / use” (or equivalently “at least adopt / use”) indicates that the phrase following “adopt / use” is one example of a number of preferred possibilities in which one or more of the various embodiments may or may not be used.

[0009] The term "configured" can relate to the capacity of a device, regardless of whether the device is operational or non-operating. "Configured" can refer to specific settings of a device that affect its operational characteristics, regardless of whether the device is operational or non-operating. In other words, hardware, software, firmware, registers, memory values, etc., can be "configured" within a device, regardless of whether the device is operational or non-operating, in order for the device to provide certain characteristics. Terms such as "control messages generated in the device" can mean that, regardless of whether the device is operational or non-operating, control messages have parameters that can be used to configure certain characteristics in the device or to implement certain actions in the device.

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

[0011] Many of the features presented are described as optional through the use of “may” or parentheses. For the sake of brevity and readability, this disclosure does not expressly describe all possible changes that may result from selecting from a set of optional features. This disclosure should be construed as expressly disclosing all such changes. For example, a system described as having three optional features can be embodied in seven ways: by just one of the three possible features, by any two of the three features, or by three of the three features.

[0012] Many of the elements described in the disclosed embodiments can be implemented as modules, where a module is defined as an element that performs a defined function and has a defined interface to other elements. Modules described in this disclosure may be implemented in hardware, software combined with hardware, firmware, wetware (e.g., hardware with biological elements), or a combination thereof, and they may be behaviorally equivalent. For example, a module may be implemented in a hardware machine (such as C, C++, Fortran, Java®, Basic, Matlab®) or in software routines written in a computer language configured to run in Simulink, Stateflow, GNU Octave, or LabVIEWMathScript. Modules may also be implemented using physical hardware that incorporates 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 hardware description languages ​​(HDLs) such as VHSIC (VHDL) or Verilog, which configure connections between internal hardware modules with limited functionality in the programmable device. These techniques are often used in combination to achieve the desired results for the functional modules.

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

[0014] CN102 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 interface function, CN102 may establish an end-to-end connection between the wireless device 106 and one or more DNs, authenticate the wireless device 106, and provide charging capabilities.

[0015] RAN104 can connect CN102 to wireless device 106 via wireless communication over the air interface. As part of the wireless communication, RAN104 can provide scheduling, wireless resource management, and retransmission protocols. The communication direction from RAN104 to wireless device 106 over the air interface is known as the downlink, and the communication direction from wireless device 106 to RAN104 over the air interface is known as the uplink. Downlink transmission can be isolated from uplink transmission using frequency division duplication (FDD), time division duplication (TDD), and / or some combination of the two duplication techniques.

[0016] The term "wireless device" may be used throughout this disclosure to mean and include any mobile or fixed (non-portable) device that requires or is capable of wireless communication. For example, a wireless device could be a telephone, smartphone, tablet, computer, laptop, sensor, meter, wearable device, Internet of Things (IoT) device, vehicle roadside unit (RSU), relay node, automobile, and / or any combination thereof. The term "wireless device" also includes other terms, including user equipment (UE), user terminal (UT), access terminal (AT), mobile station, handset, wireless transceiver unit (WTRU), and / or wireless communication device.

[0017] RAN104 may include one or more base stations (not shown). The term base station may be used throughout this disclosure to include and encompass Node B (associated with UMTS and / or 3G standards), evolved Node B (associated with eNB, E-UTRA and / or 4G standards), remote radio head (RRH), baseband processing unit coupled to one or more RRHs, repeater node or relay node used to extend the coverage area of ​​a donor node, next-generation evolved Node B (ng-eNB), generation Node B (associated with gNB, NR and / or 5G standards), access point (AP, associated with e.g., 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] A base station included in RAN104 may include one or more sets of antennas for communicating with the radio device 106 over an air interface. For example, one or more base stations may include three sets of antennas for controlling three cells (or sectors), each of which may be three cells. 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 radio device transmitter) operating in the cell. Together, the base station cells may provide radio coverage to the radio device 106 over a wide geographical area to support radio device mobility.

[0019] In addition to the three sector sites, other implementations of base stations are possible. For example, one or more base stations in RAN104 may be implemented as sector sites with more or fewer than three sectors. One or more base stations in RAN104 may be implemented as access points, as baseband processing units coupled to multiple remote radio heads (RRHs), and / or as repeaters or relay nodes used to extend the coverage area of ​​a donor node. Baseband processing units coupled to RRHs may be part of a centralized or cloud RAN architecture, and the baseband processing units may be centralized or virtualized within a pool of baseband processing units. Repeater nodes may amplify and rebroadcast radio signals received from donor nodes. Relay nodes may perform the same / similar functions as repeater nodes, but may decode radio signals received from donor nodes and remove noise before amplifying and rebroadcasting the radio signals.

[0020] RAN104 can be deployed as a homogeneous network of macrocell base stations having similar antenna patterns and similar high-level transmission power. RAN104 can also be deployed as a heterogeneous network. In a heterogeneous network, small cell base stations can be used to provide smaller coverage areas, for example, overlapping with the relatively large coverage areas provided by macrocell base stations. Smaller coverage areas can be provided in areas with high data traffic (or so-called hotspots) or in areas with weak macrocell coverage. Examples of small cell base stations, in order of decreasing coverage area, include microcell base stations, picocell base stations, and femtocell base stations or home base stations.

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

[0022] Figure 1B shows another example of a mobile communications network 150 in which embodiments of the present disclosure may be implemented. The mobile communications network 150 may be, for example, a PLMN operated by a network operator. As shown in Figure 1B, the mobile communications network 150 includes a 5G core network (5G-CN) 152, an NG-RAN 154, and UE156A and UE156B (collectively referred to as UE156). These components may be implemented and operate in the same or similar manner as the corresponding components described with respect to Figure 1A.

[0023] 5G-CN152 provides UE156 with an interface to one or more DNs, such as public DNs (e.g., the Internet), private DNs, and / or intra-operator DNs. As part of its interface function, 5G-CN152 may set up end-to-end connectivity between UE156 and one or more DNs, authenticate UE156, and provide charging capabilities. Compared to the CNs of 3GPP 4G networks, the basis of 5G-CN152 may be a service-based architecture. This means that the architecture of the nodes constituting 5G-CN152 may be defined as network functions that provide services through interfaces to other network functions. The network functions of 5G-CN152 may be implemented in several ways, such as network elements on dedicated or shared hardware, software instances running on dedicated or shared hardware, or virtualized functions instantiated on a platform (e.g., a cloud-based platform).

[0024] As shown in Figure 1B, the 5G-CN152 includes Access and Mobility Management Function (AMF) 158A and User Plane Function (UPF) 158B, which for ease of explanation are shown in Figure 1B as a single component AMF / UPF158. The UPF158B may function as a gateway between the NG-RAN154 and one or more DNs. The UPF158B may perform functions such as packet routing and forwarding, packet inspection and enforcement of user plane policy rules, traffic utilization reporting, uplink classification supporting 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 triggers. The UPF158B may support multi-homed PDU sessions by functioning 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 branch point. UE156 can be configured to receive services via a PDU session, which is a logical connection between the UE and the DN.

[0025] The AMF158A may perform functions such as termination of non-access layer (NAS) signaling, NAS signaling security, access layer (AS) security control, inter-CN node signaling for mobility between 3GPP® access networks, idle-mode UE reachability (e.g., control and execution of paging retransmission), registered area management, intra-system and inter-system mobility support, access authentication, access permission including roaming privilege checks, mobility management control (subscriptions and policies), network slicing support, and / or selection of session management functions (SMF). NAS may refer to functions operating between CN and UE, and AS may refer to functions operating between UE and RAN.

[0026] For clarity, 5G-CN152 may include one or more additional network functions not shown in Figure 1B. For example, 5G-CN152 may include one or more of the following: Session Management Function (SMF), NR Repository Function (NRF), Policy Control Function (PCF), Network Exposure Function (NEF), Unified Data Management (UDM), Application Function (AF), and / or Authentication Server Function (AUSF).

[0027] NG-RAN154 can connect 5G-CN152 to UE156 via wireless communication over the air interface. NG-RAN154 may include one or more gNBs (collectively gNB160) illustrated as gNB160A and gNB160B and / or one or more ng-eNBs (collectively ng-eNB162) illustrated as ng-eNB162A and ng-eNB162B. gNB160 and ng-eNB162 may more commonly be referred to as base stations. gNB160 and ng-eNB162 may include one or more sets of antennas for communicating with UE156 over the air interface. For example, one or more gNB160s and / or one or more ng-eNB162s may include three sets of antennas for controlling three cells (or sectors), each. In addition, the gNB160 and ng-eNB162 cells can provide wireless coverage to the UE156 over a wide geographical area to support UE mobility.

[0028] As shown in Figure 1B, gNB160 and / or ng-eNB162 may be connected to 5G-CN152 via the NG interface and to other base stations via the Xn interface. The NG and Xn interfaces may be established on an underlying transport network, such as an Internet Protocol (IP) transport network, using direct physical and / or indirect connections. gNB160 and / or ng-eNB162 may be connected to UE156 via the Uu interface. For example, as shown in Figure 1B, gNB160A may be connected to UE156A via the Uu interface. The NG, Xn, and Uu interfaces are associated with a protocol stack. The protocol stack associated with the interfaces may be used by the network elements in Figure 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 the user. The control plane may process signaling messages of interest to the network elements.

[0029] The gNB160 and / or ng-eNB162 may be connected to one or more AMF / UPF functions of the 5G-CN152, such as the AMF / UPF158, by one or more NG interfaces. For example, the gNB160A may be connected to the UPF158B of the AMF / UPF158 by an NG-User Plane (NG-U) interface. The NG-U interface may provide the supply of user plane PDUs between the gNB160A and the UPF158B (e.g., unguaranteed delivery). The gNB160A may be connected to the AMF158A 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, NAS message transport, paging, PDU session management and configuration transfer and / or warning message transmission.

[0030] The gNB160 can provide NR user plane and control plane protocol termination to UE156 on a Uu interface. For example, the gNB160A can provide NR user plane and control plane protocol termination to UE156A on a Uu interface associated with a first protocol stack. The ng-eNB162 can provide Evolved UMTS Terrestrial Radio Access (E-UTRA) user plane and control plane protocol termination to UE156 on a Uu interface, where E-UTRA refers to 3GPP 4G radio access technology. For example, the ng-eNB162B can provide E-UTRA user plane and control plane protocol termination to UE156B on a Uu interface associated with a second protocol stack.

[0031] The 5G-CN152 is described as being configured to handle NR and 4G radio access. Those skilled in the art will understand that it may be possible for NR to connect to the 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 / UPF158 is shown in Figure 1B, one gNB or ng-eNB may be connected to multiple AMF / UPF nodes to provide redundancy and / or load shares across multiple AMF / UPF nodes.

[0032] As can be considered, in Figure 1B, interfaces between network elements (e.g., Uu, Xn, and NG interfaces) may be associated with a protocol stack used by the network elements to exchange data and signaling messages. The protocol stack may include two planes: a user plane and a control plane. The user plane may process data of interest to the user, and the control plane may process signaling messages of interest to the network elements.

[0033] Figures 2A and 2B show examples of NR user plane and NR control plane protocol stacks for the Uu interface between UE210 and gNB220, respectively. The protocol stacks shown in Figures 2A and 2B may be the same or similar to those used for the Uu interface between UE156A and gNB160A shown in Figure 1B, for example.

[0034] Figure 2A shows the NR user plane protocol stack, which includes five layers, implemented in the UE210 and gNB220. At the bottom of the protocol stack, the physical layers (PHYs) 211 and 221 can provide transport services to the upper layers of the protocol stack and may correspond to layer 1 of the Open Systems Interconnection (OSI) model. The following four protocols above PHYs 211 and 221 include the Media Access Control Layer (MAC) 212 and 222, the Radio Link Control Layer (RLC) 213 and 223, the Packet Data Convergence Protocol Layer (PDCP) 214 and 224, and the Service Data Application Protocol Layer (SDAP) 215 and 225. Together, these four protocols may constitute layer 2 or the data link layer of the OSI model.

[0035] Figure 3 shows an example of services provided between protocol layers in the NR user plane protocol stack. Starting from the top of Figures 2A and 3, SDAP215 and 225 may perform QoS flow processing. UE210 may receive services via a PDU session, which may be a logical connection between UE210 and DN. A PDU session may have one or more QoS flows. CN's UPF (e.g., UPF158B) may map IP packets to one or more QoS flows in the PDU session based on QoS requirements (e.g., with respect to delay, data rate, and / or error rate). SDAP215 and 225 may perform mapping / unmapping between one or more QoS flows and one or more data radio bearers. Mapping / unmapping between QoS flows and data radio bearers may be determined by SDAP225 at gNB220. SDAP215 at UE210 may be notified about the mapping between QoS flows and data radio bearers via reflected mapping or control signaling received from gNB220. Regarding reflection mapping, the SDAP225 on the gNB220 can mark downlink packets with a QoS flow indicator (QFI), which can be observed by the SDAP215 on the UE210 to determine mapping / unmapping between the QoS flow and the data radio bearer.

[0036] PDCP214 and 224 can perform header compression / decompression to reduce the amount of data that needs to be transmitted over the air interface, encryption / decryption to prevent unauthorized decryption of data transmitted over the air interface, and integrity protection (to ensure that control messages originate from the intended source). PDCP214 and 224 can perform, for example, retransmission of untransmitted packets, intra-sequence delivery and rearrangement of packets, and removal of duplicate packets for handover within gNB. PDCP214 and 224 can perform packet duplication to improve the likelihood of received packets and to remove any duplicate packets at the receiver. Packet duplication may be useful for services requiring high reliability.

[0037] Although not shown in Figure 3, PDCP214 and 224 can perform mapping / unmapping between split radio bearers and RLC channels in a dual-connection scenario. Dual-connection 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 radio bearer is when a single radio bearer, such as one of the radio bearers provided by PDCP214 and 224 as a service to SDAP215 and 225, is handled by a cell group in a dual-connection. PDCP214 and 224 can map / unmap split radio bearers between RLC channels belonging to the cell group.

[0038] RLC213 and 223 can perform segmentation, retransmission via Automatic Repeat Request (ARQ), and removal of replicated data units received from MAC212 and 222, respectively. RLC213 and 223 can support three transmission modes: transparent mode (TM), unacknowledged response mode (UM), and acknowledgment 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 Figure 3, RLC213 and 223 may provide RLC channels as a service to PDCP214 and 224, respectively.

[0039] MAC212 and 222 may perform logical channel multiplexing / demultiplexing 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 PHY211 and 221. MAC222 may be configured to perform scheduling, scheduling information reporting, and priority processing between UEs by dynamic scheduling. Scheduling may be performed by gNB220 (on MAC222) for downlink and uplink. MAC212 and 222 may be configured to perform error correction, priority processing between logical channels of UE210 by logical channel prioritization, and / or padding through Hybrid Automatic Repeating Requests (HARQ) (e.g., one HARQ entity per carrier in the case of Carrier Aggregation (CA)). MAC212 and 222 may support one or more numerology and / or transmission timings. For example, mapping restrictions in logical channel prioritization can control which numerology and / or transmission timing a logical channel can use. As shown in Figure 3, MACs 212 and 222 may provide logical channels to RLCs 213 and 223 as a service.

[0040] PHY211 and 221 can perform transport channel mapping to physical channels and digital and analog signal processing functions for transmitting and receiving information over the air interface. These digital and analog signal processing functions may include, for example, coding / decoding and modulation / demodulation. PHY211 and 221 can perform multi-antenna mapping. As shown in Figure 3, PHY211 and 221 may provide one or more transport channels to MAC212 and 222 as a service.

[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 on the gNB220. 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 SDAP225 receives three IP packets from one or more QoS flows and maps the three packets to radio bearers. In Figure 4A, SDAP225 maps IP packets n and n+1 to the first radio bearer 402 and 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 lower protocol layers, and data units to / from lower protocol layers are referred to as Protocol Data Units (PDUs) of higher protocol layers. As shown in Figure 4A, the data unit from SDAP225 is an SDU of the lower protocol layer PDCP224 and a PDU of SDAP225.

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

[0044] Figure 4B shows an example of the MAC subheader format in a MAC PDU. The MAC subheader includes an SDU length field to indicate the length (in bytes, etc.) of the MAC SDU that the MAC subheader corresponds to, a logical channel identifier (LCID) field to identify the logical channel initiated by the MAC SDU to assist in the multiplexing process, a flag (F) to indicate the size of the SDU length field, and a reserved bit (R) field for future use.

[0045] Figure 4B further illustrates MAC control elements (CEs) inserted into a MAC PDU by MACs such as MAC223 or MAC222. For example, Figure 4B shows two MAC CEs inserted into a MAC PDU. MAC CEs may be inserted at the beginning of a MAC PDU for downlink transmission (as shown in Figure 4B) and at the end of a 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 reporting and power headroom reporting; start / stop MAC CEs for PDCP duplicate detection start / stop, channel status information (CSI) reporting, sounding reference signal (SRS) transmission, and pre-configured components; discontinuous receive (DRX)-related MAC CEs; timing progression MAC CEs; and random access-related MAC CEs. MAC CEs may be preceded by a MAC subheader in a format similar to that described for MAC SDUs and may be identified by a reserved value in the LCID field, which indicates the type of control information contained in the MAC CE.

[0046] Before describing the NR control plane protocol stack, we will first explain the logical channels, transport channels, and physical channels, as well as the mapping between channel types. One or more channels can be used to perform functions related to the NR control plane protocol stack, which will be discussed later.

[0047] Figures 5A and 5B show the mapping between logical channels, transport channels, and physical channels for downlink and uplink, respectively. Information is passed through channels between the RLC, MAC, and PHY of the NR protocol stack. Logical channels can be used between the RLC and MAC and can be classified as control channels that transmit control and configuration information within the NR control plane, or as traffic channels that transmit data within the NR user plane. Logical channels can be classified as dedicated logical channels for a particular UE, or as common logical channels that can be used by more than one UE. Logical channels can 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 not known to the network at the cell level, - A broadcast control channel (BCCH) for transmitting system information messages in the form of master information blocks (MIBs) and several system information blocks (SIBs), wherein the system information messages are used by the UE to obtain information about how the cell is configured and how it operates within the cell. - A common control channel (CCCH) for carrying control messages along with random access, -To configure the UE, a dedicated control channel (DCCH) is used to carry control messages to and from a specific UE. - Includes a dedicated traffic channel (DTCH) for transporting user data to and from specific UEs.

[0048] A transport channel is used between the MAC layer and the PHY layer and can be defined by how they transmit the information they carry over the air interface. The set of transport channels defined by NR includes, for example, - A paging channel (PCH) for carrying paging messages transmitted from the PCCH, - A broadcast channel (BCH) for carrying MIBs from BCCH, - A downlink shared channel (DL-SCH) for carrying downlink data and signaling messages, including SIBs from BCCH, - Uplink Shared Channel (UL-SCH) for carrying uplink data and signaling messages, - Includes Random Access Channels (RACH) that allow UEs to access the network without prior scheduling.

[0049] A PHY can pass information between its processing levels using physical channels. A physical channel may have an associated set of time-frequency resources for carrying information from one or more transport channels. The PHY can generate control information to support its low-level operation 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 is, for example, - A physical broadcast channel (PBCH) for carrying MIBs from the BCH, - A physical downlink shared channel (PDSCH) for carrying downlink data and signaling messages from DL-SCH, and paging messages from PCH, - A physical downlink control channel (PDCCH) for carrying downlink control information (DCI), which may include downlink scheduling commands, uplink scheduling authorization, and uplink power control commands. -UL-SCH and, as described below, in some examples, a physical uplink shared channel (PUSCH) for carrying uplink data and signaling messages from uplink control information (UCI), - A physical uplink control channel (PUCCH) for carrying UCI, which may include HARQ acknowledgment responses, channel quality indicators (CQI), precoding matrix indicators (PMI), rank indicators (RI), and scheduling requests (SR), - Includes 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 operation of the physical layer. As shown in Figures 5A and 5B, the physical layer signals defined by NR include the primary synchronization signal (PSS), secondary synchronization signal (SSS), channel state information reference signal (CSI-RS), demodulation reference signal (DMRS), sounding reference signal (SRS), and phase tracking reference signal (PT-RS). These physical layer signals are described in more detail below.

[0051] Figure 2B shows an example of an NR control plane protocol stack. In Figure 2B, the NR control plane protocol stack may use the same / similar first four protocol layers as in the example of the NR user plane protocol stack. These four protocol layers include PHY211 and 221, MAC212 and 222, RLC213 and 223, and PDCP214 and 224. Instead of having SDAP215 and 225 at the top of the stack, as in the NR user plane protocol stack, the NR control plane stack has Radio Resource Control (RRC)216 and 226, and NAS protocols217 and 237 at the top of the NR control plane protocol stack.

[0052] NAS protocols 217 and 237 can provide control plane functions between the UE210 and the AMF230 (e.g., AMF158A), or more generally, between the UE210 and the CN. NAS protocols 217 and 237 can provide control plane functions between the UE210 and the AMF230 via signaling messages referred to as NAS messages. There is no direct path for NAS messages to be transported between the UE210 and the AMF230. NAS messages can be transported using the AS of the Uu and NG interfaces. NAS protocols 217 and 237 can provide control plane functions such as authentication, security, connection setup, mobility management, and session management.

[0053] RRC216 and 226 may provide control plane functionality between UE210 and gNB220, or more generally, between UE210 and RAN. RRC216 and 226 may provide control plane functionality between UE210 and gNB220 via signaling messages referred to as RRC messages. RRC messages may be transmitted between UE210 and RAN using a signaling radio bearer and the same / similar PDCP, RLC, MAC, and PHY protocol layers. MAC may multiplex control plane and user plane data within the same transport block (TB). RRC216 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, establishing, maintaining, and releasing RRC connections between the UE210 and the RAN, security functions including key management, establishing, configuring, maintaining, and releasing signaling radio bearers 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 the RRC connection, RRC216 and 226 may establish an RRC context, which may involve setting parameters for communication between the UE210 and the RAN.

[0054] Figure 6 is an exemplary diagram illustrating the RRC state transitions of a UE. The UE may be identical or similar to the wireless device 106 shown in Figure 1A, the UE 210 shown in Figures 2A and 2B, or any other wireless device described herein. As shown in Figure 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 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 one or more base stations included in RAN104 shown in Figure 1A, one of gNB160 or ng-eNB162 shown in Figure 1B, gNB220 shown in Figures 2A and 2B, or any other base station similar to any other base station described herein. 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., related to 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 RRC connection 602, the UE's mobility may be managed by the RAN (e.g., RAN104 or NG-RAN154). The UE may measure signal levels (e.g., reference signal levels) from the serving cell and adjacent cells and report these measurements to the base station currently serving the UE. Based on the reported measurements, the UE's serving base station may request a handover to one of the adjacent base stations' cells. The RRC state may transition from RRC connection 602 to RRC idle 604 via connection release procedure 608, or to RRC inactive 606 via connection deactivation procedure 610.

[0056] During RRC idle 604, the RRC context may not be established for the UE. During RRC idle 604, the UE may not have an RRC connection with the base station. During RRC idle 604, the UE may be in a sleep state for most of the time (e.g., to conserve battery power). The UE may wake up periodically (e.g., once per discontinuous receive cycle) to monitor paging messages from the RAN. The mobility of the UE may be managed by the UE through a procedure known as cell reselection. The RRC state may transition from RRC idle 604 to RRC connection 602 via a connection establishment procedure 612, which may involve a random access procedure, as will be discussed in more detail below.

[0057] In RRC inactive 606, the previously established RRC context is maintained at the UE and base station. This reduces signaling overhead compared to the transition from RRC idle 604 to RRC connected 602, enabling a faster transition to RRC connected 602. In RRC inactive 606, the UE is in a sleep state, and the UE's mobility can be managed by the UE through cell reselection. The RRC state can transition from RRC inactive 606 to RRC connected 602 via connection restart procedure 614, or to RRC idle 604 via connection release procedure 616, which is identical or similar to connection release procedure 608.

[0058] The RRC state can 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 enable the network to notify the UE of events via paging messages without broadcasting paging messages across the entire mobile communications network. The mobility management mechanisms used in RRC idle 604 and RRC inactive 606 may enable the network to track the UE at the cell group level so that paging messages can be broadcast on the cells of the cell group in which the UE currently resides, instead of across the entire mobile communications network. The mobility management mechanisms in RRC idle 604 and RRC inactive 606 track the UE at the cell group level. They may do so using grouping at different granularities. For example, there may be three levels of granularity for cell grouping: individual cells, cells within a RAN area identified by a RAN Area Identifier (RAI), and cells within a group of RAN areas referred to as a tracking area, identified by a Tracking Area Identifier (TAI).

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

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

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

[0062] A gNB, such as the gNB160 in Figure 1B, can be divided into two parts: a central unit (gNB-CU) and one or more distributed units (gNB-DU). The gNB-CU can 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 (Figures 5A and 5B) can be mapped onto orthogonal frequency division multiplexing (OFDM) symbols. OFDM is a multicarrier communication scheme that transmits data over F orthogonal subcarriers (or tones). Before transmission, the data can be mapped to a series of complex symbols (e.g., M orthogonal amplitude modulation (M-QAM) or M phase shift keying (M-PSK) symbols) which are divided into F parallel symbol streams, referred to as source symbols. The F parallel symbol streams can be used as input to an inverse fast Fourier transform (IFFT) block that converts them to the time domain as if they were in the frequency domain. The IFFT block can take one from each of the F parallel symbol streams at a time into an F source symbol, 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 an F time domain sample representing the sum of the F orthogonal subcarriers. An F time domain sample can form a single OFDM symbol. After some processing (e.g., adding cyclic prefixes) and upconversion, the OFDM symbols provided by the IFFT block can be transmitted over the air interface at the carrier frequency. The parallel symbol streams can be mixed using an FFT block before being processed by the IFFT block. This process generates OFDM symbols pre-encoded with discrete Fourier transforms (DFTs), which can be used by the UE in the uplink to reduce the peak-to-average power ratio (PAPR). The reverse process can be performed at the receiver using an FFT block to reconstruct the data mapped to the source symbols.

[0064] Figure 7 shows an exemplary configuration of an NR frame in which OFDM symbols are grouped. An NR frame can be identified by a System Frame Number (SFN). An SFN may repeat over a period of 1024 frames. As shown, one NR frame may have a duration of 10 milliseconds (ms) and may contain 10 subframes, each with a duration of 1 millisecond. A subframe may be divided into slots, for example, containing 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 a maximum of mm-wavelengths). Numerology can be defined with respect to subcarrier spacing and cyclic prefix duration. For numerology in NR, subcarrier spacing can be scaled up by a power of 2 from a baseline subcarrier spacing of 15 kHz, and cyclic prefix duration can be scaled down by a power of 2 from a baseline cyclic prefix duration of 4.7 μs. For example, NR defines numerology 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 can have a fixed number of OFDM symbols (e.g., 14 OFDM symbols). Numerologies with higher subcarrier spacing have shorter slot durations and, accordingly, more slots per subframe. Figure 7 shows this numerology-dependent slot duration and slot transmission structure per subframe (for ease of illustration, numerologies with a 240 kHz subcarrier spacing are not shown in Figure 7). Subframes within the NR can be used as a numerology-independent time reference, while slots can be used as units on which uplink and downlink transmissions are scheduled. To support low latency, scheduling in the NR is separated from slot duration and can start with any OFDM symbol and continue for as many symbols as needed for transmission. These partial slot transmissions can be referred to as mini-slot transmissions or sub-slot transmissions.

[0067] Figure 8 shows an exemplary configuration of slots in the time and frequency domains of an NR carrier. A slot contains resource elements (REs) and resource blocks (RBs). An RE is the smallest physical resource in the NR. As shown in Figure 8, an RE spans one OFDM symbol in the time domain by one subcarrier in the frequency domain. 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 × 12 = 3300 subcarriers. When used, such limitations can restrict the NR carrier to 50, 100, 200, and 400 MHz for subcarrier spacings of 15, 30, 60, and 120 kHz, respectively, with the 400 MHz bandwidth being set based on a carrier bandwidth limit of 400 MHz per unit.

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

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

[0070] NR supports UEs that cannot receive the full carrier bandwidth and defines a Bandwidth Portion (BWP) that supports bandwidth adaptation. For example, a BWP may be defined by a subset of consecutive RBs on the carrier. A UE may consist of 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) (e.g., via the RRC layer). 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 consists of 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 spectra, a downlink BWP from a set of configured downlink BWPs can be linked to an uplink BWP from a set of configured uplink BWPs if the downlink BWP index of the downlink BWP is the same as the uplink BWP index of the uplink BWP. For unpaired spectra, the UE can expect that the center frequency of the downlink BWP is 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), a base station may configure a UE for at least one search space with one or more control resource sets (CORESETs). A search space is a set of locations in the time and frequency domains where a UE can find control information. A search space can be a UE-specific search space or a common search space (potentially usable by multiple UEs). For example, a base station may configure a UE in a common search space on an active downlink BWP, either on a PCell or on a primary / secondary cell (PSCell).

[0073] For an uplink BWP within 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) within 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) within the uplink BWP according to the configured numerology (e.g., subcarrier spacing and cyclic prefix length of the uplink BWP).

[0074] One or more BWP indicator fields may be provided to the Downlink Control Information (DCI). The values ​​of the BWP indicator fields may indicate which of the configured set of BWPs is the active downlink BWP for one or more downlink receptions. The values ​​of one or more BWP indicator fields may indicate the active uplink BWP for one or more uplink transmissions.

[0075] The base station may semi-statically configure the UE with the default downlink BWP in 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] A base station may configure the UE with the PCell BWP inactive timer value. The rUE may start or restart the BWP inactive timer at any appropriate time. For example, the UE may start or restart the BWP inactive timer when (a) the UE detects a DCI indicating an active downlink BWP other than the default downlink BWP for a paired spectral operation, or (b) the UE detects a DCI indicating an active downlink BWP or active uplink BWP other than the default downlink BWP or uplink BWP for an unpaired spectral operation. If the UE does not detect a DCI for a certain period (e.g., 1 millisecond or 0.5 milliseconds), the UE may run the BWP inactive timer toward expiration (e.g., increasing from zero to the BWP inactive timer value, or decreasing from the BWP inactive timer value to zero). When the BWP inactive 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 having one or more BWPs. The UE may switch the active BWP from the first BWP to the second BWP in response to receiving a DCI indicating a second BWP as the active BWP, and / or in response to the expiration of the BWP inactivity timer (for example, if the second BWP is the default BWP).

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

[0079] Figure 9 shows an example of bandwidth adaptation using three configured BWPs for an NR carrier. The UE, composed of the three BWPs, can switch from one BWP to another at the switching point. In the example shown in Figure 9, the BWPs include BWP902 with a bandwidth of 40 MHz and a subcarrier spacing of 15 kHz, BWP904 with a bandwidth of 10 MHz and a subcarrier spacing of 15 kHz, and BWP906 with a bandwidth of 20 MHz and a subcarrier spacing of 60 kHz. BWP902 may be the initial active BWP, and BWP904 may be the default BWP. The UE can switch between BWPs at the switching point. In the example in Figure 9, the UE may switch from BWP902 to BWP904 at switching point 908. Switching at switching point 908 may occur for any preferred reason, for example, in response to the expiration of a BWP inactive timer (indicating switching to the default BWP) and / or in response to receiving a DCI indicating BWP904 as the active BWP. The UE may switch from active BWP904 to BWP906 at switching point 910 in response to receiving a DCI indicating BWP906 as the active BWP. The UE may switch from active BWP906 to BWP904 at switching point 912 in response to the expiration of the BWP inactive timer and / or in response to receiving a DCI indicating BWP904 as the active BWP. The UE may switch from active BWP904 to BWP902 at switching point 914 in response to receiving a DCI indicating BWP902 as the active BWP.

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

[0081] To provide higher data rates, carrier aggregation (CA) can be used to aggregate two or more carriers and transmit them simultaneously to the same UE. The aggregated carriers in CA may be called 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 within the frequency domain.

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

[0083] In one example, up to 32 CCs can be aggregated. Aggregated CCs may have the same or different bandwidths, subcarrier spacings, and / or duplication schemes (TDD or FDD). A serving cell of a UE using a CA may have downlink CCs. 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 using a Carrier Aggregation (CA), one of the UE's aggregation cells may be referred to as a primary cell (PCell). A PCell may be the serving cell to which the UE first connects during RRC connection establishment, re-establishment, and / or handover. A PCell may provide the UE with NAS mobility information and security inputs. A UE may have different PCells. On the downlink, the carrier corresponding to a PCell may be referred to as the Downlink Primary CC (DL PCC). On the uplink, the carrier corresponding to a PCell may be referred to as the Uplink Primary CC (UL PCC). Other aggregation cells of the UE may be referred to as secondary cells (SCells). For example, an SCell may be configured after the PCell is configured for the UE. For example, an SCell may be configured via an RRC connection reconfiguration procedure. On the downlink, the carrier corresponding to an SCell may be referred to as the Downlink Secondary CC (DL SCC). On the uplink, the carrier corresponding to an SCell may be referred to as the Uplink Secondary CC (UL SCC).

[0085] SCells configured for a UE can be started and stopped, for example, based on traffic and channel conditions. Stopping a SCell may mean that PDCCH and PDSCH reception on the SCell is stopped, and PUSCH, SRS, and CQI transmission on the SCell is stopped. Configured SCells can be started and stopped using MAC CEs with respect to Figure 4B. For example, a MAC CE may use a bitmap (e.g., one bit per SCell) to indicate which SCells (e.g., from a subset of configured SCells) for the UE are started or stopped. Configured SCells can be stopped in response to the expiration of SCell stop timers (e.g., one SCell stop timer per SCell).

[0086] Downlink control information, such as cell scheduling assignments and scheduling authorizations, can be transmitted on the cell corresponding to the assignment and authorization, known as self-scheduling. DCIs for a cell can be transmitted on another cell, known as cross-carrier scheduling. Uplink control information for aggregated cells (e.g., HARQ acknowledgments and channel state feedback such as CQI, PMI, and / or RI) can be transmitted on the PCell's PUCCH. A large number of aggregated downlink CCs may overload the PCell's PUCCH. A cell can be divided into multiple PUCCH groups.

[0087] Figure 10B shows an example of how aggregation cells can be configured into one or more PUCCH groups. PUCCH group 1010 and PUCCH group 1050 may each contain one or more downlink CCs. In the example in Figure 10B, PUCCH group 1010 contains three downlink CCs: PCell 1011, SCell 1012, and SCell 1013. PUCCH group 1050, in this example, contains 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 S cells (PSCells) 1061, SCell 1062, and SCell 1063. Uplink control information (UCI) related to the downlink CC of PUCCH group 1010, indicated as UCI1031, UCI1032, and UCI1033, can be transmitted on the uplink of PCell 1021. Uplink control information (UCI) related to the downlink CC of PUCCH group 1050, indicated as UCI1071, UCI1072, and UCI1073, can be transmitted on the uplink of PSCell 1061. In one example, if the aggregation cell depicted in Figure 10B is not divided into PUCCH group 1010 and PUCCH group 1050, the single uplink PCell and PCell for transmitting the UCI related to the downlink CC may become overloaded. Overload can be prevented by dividing the transmission of UCI between PCell 1021 and PSCell 1061.

[0088] A cell containing 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, depending on the context in which the physical cell ID is used, identify the downlink carrier and / or uplink carrier of the cell. The physical cell ID may be determined using synchronization signals transmitted on the downlink component carrier. The cell index may be determined using RRC messages. In this disclosure, the physical cell ID may be referred to as the carrier ID, and the cell index may be referred to as the 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 containing 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 containing the first carrier is activated.

[0089] In a CA, the multi-carrier nature of the PHY can be exposed to MAC. For example, a HARQ entity may operate on a serving cell. Transport blocks may be generated per allocation / authorization per serving cell. Transport blocks and their potential HARQ retransmissions can be mapped to serving cells.

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

[0091] Figure 11A shows an example of the structure and location of an SS / PBCH block. A burst of SS / PBCH blocks may contain one or more SS / PBCH blocks (e.g., four SS / PBCH blocks as shown in Figure 11A). Bursts may be transmitted periodically (e.g., every two frames or every 20 milliseconds). Bursts may be limited to half frames (e.g., a first half frame with a duration of 5 milliseconds). Figure 11A is an example, and it will be understood that these parameters (number of SS / PBCH blocks per burst, burst period, burst location within a frame) may be configured based on, for example, the carrier frequency of the cell through which the SS / PBCH block is transmitted, the cell's numerology or subcarrier spacing, the network configuration (e.g., using RRC signaling), or any other preferred factor. In one example, the UE may assume a subcarrier spacing for an SS / PBCH block based on the monitored carrier frequency, unless the wireless network is configured 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 in Figure 11A) and one or more subcarriers in the frequency domain (e.g., 240 consecutive subcarriers). PSS, SSS, and PBCH may have a common center frequency. A PSS may be transmitted first, e.g., over one OFDM symbol and 127 subcarriers. An SSS may be transmitted after a PSS (e.g., after two symbols), e.g., over one OFDM symbol and 127 subcarriers. A PBCH may be transmitted after a PSS (e.g., over the next three OFDM symbols), e.g., over 240 subcarriers.

[0093] The location of SS / PBCH blocks in the time and frequency domains 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 of the PSS. For example, the UE may monitor the frequency position within the carrier. If the PSS is not found after a certain duration (e.g., 20 milliseconds), the UE may search for the PSS at a different frequency position within the carrier, as indicated by the synchronization raster. If the PSS is found at a location in the time and frequency domains, the UE may determine the locations of the SSS and PBCH, respectively, based on the known structure of the SS / PBCH block. The SS / PBCH block may be a cell-defining SS block (CD-SSB). In one example, a primary cell may be associated with a CD-SSB. The CD-SSB may be located on a synchronization raster. In one example, cell selection / search and / or re-selection may be based on the CD-SSB.

[0094] SS / PBCH blocks can be used by the UE to determine one or more parameters of a cell. For example, the UE may determine the physical cell identifier (PCI) of a cell based on the PSS and SSS sequences, respectively. The UE may also determine the location of a cell's frame boundary 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, and the SS / PBCH block in the transmission pattern is at a known distance from the frame boundary.

[0095] The PBCH may use QPSK modulation and forward error correction (FEC). FEC may use polar coding. One or more symbols spanned by the PBCH may carry one or more DMRS for demodulation of the PBCH. The PBCH may include a representation 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 find the remaining minimum system information (RMSI) used by the UE and associated with the cell. The RMSI may include a System Information Block Type 1 (SIB1). The SIB1 may contain 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 the SIB1. The SIB1 can be decoded using the parameters provided in the MIB. The PBCH may indicate the absence of the SIB1. Based on the PBCH indicating the absence of SIB1, the UE may point to a frequency. The UE may then search for the SS / PBCH block at the frequency pointed to by the UE.

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

[0097] SS / PBCH blocks (e.g., blocks within a half-frame) can be transmitted in a spatial direction (e.g., using different beams across the cell's coverage area). For 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 carrier frequency span, a base station may transmit multiple SS / PBCH blocks. In one example, the first PCI of the first SS / PBCH block of multiple SS / PBCH blocks may be different from the second PCI of the second SS / PBCH block of multiple SS / PBCH blocks. PCIs of SS / PBCH blocks transmitted at different frequency locations may be different or identical.

[0099] CSI-RS can be transmitted by a base station and used by an UE to obtain channel status information (CSI). A base station may configure an UE with one or more CSI-RS for channel estimation or any other preferred purpose. A base station may configure an UE with one or more identical / similar CSI-RS. An UE may measure one or more CSI-RS. Based on the measurement of one or more downlink CSI-RS, an UE may estimate the downlink channel status and / or generate a CSI report. An UE may provide the CSI report to the base station. The base station may perform link fitting using feedback provided by the UE (e.g., estimated downlink channel status).

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

[0101] A base station can configure a UE to report CSI measurements. The base station can configure a UE to provide CSI reports periodically, aperiodicly, or semi-persistently. For periodic CSI reporting, the UE can consist of multiple CSI reports with varying timings and / or periods. For aperiodic CSI reporting, the base station can request CSI reports. For example, the base station can instruct a UE to measure configured CSI-RS resources and provide CSI reports on the measurements. For semi-persistent CSI reporting, the base station can configure a UE to periodically transmit periodic reports and selectively activate or deactivate them. The base station can use RRC signaling to configure a UE with CSI-RS resource sets and CSI reports.

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

[0103] Downlink DMRS can be transmitted by a base station and used by an UE for channel estimation. For example, downlink DMRS can be used for coherent demodulation of one or more downlink physical channels (e.g., PDSCHs). An NR network may support one or more variable and / or configurable DMRS patterns for data demodulation. At least one downlink DMRS configuration may support a front-loaded DMRS pattern. A front-loaded DMRS can be mapped to one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). A base station can semi-statically configure an UE using the number of front-loaded DMRS symbols (e.g., maximum number) of the PDSCH. A DMRS configuration may support one or more DMRS ports. For example, in the case of single-user MIMO, a DMRS configuration may support up to eight orthogonal downlink DMRS ports per UE. In the case of multi-user MIMO, a DMRS configuration may support up to four orthogonal downlink DMRS ports per UE. A wireless network can support a common DMRS structure for downlink and uplink (e.g., at least for CP-OFDM). DMRS locations, DMRS patterns, and / or scrambling sequences may be the same or different. Base stations may transmit downlink DMRS and corresponding PDSCHs using the same precoding matrix. A UE may use one or more downlink DMRSs for coherent demodulation / channel estimation of PDSCHs.

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

[0105] A PDSCH may contain one or more layers. The UE may assume that at least one symbol with a DMRS exists on one or more layers of the PDSCH. The upper layers may constitute up to three DMRSs for the PDSCH.

[0106] Downlink PT-RS may be transmitted by the base station and used by the UE for phase noise compensation. Whether downlink PT-RS is present depends on the RRC configuration. The presence and / or pattern of downlink PT-RS can be configured on a UE-specific basis using a combination of RRC signaling and / or association with one or more parameters used for other purposes (e.g., Modulation and Encoding Scheme (MCS)), which may be indicated by DCI. If configured, the dynamic presence of downlink PT-RS may be associated with one or more DCI parameters, including at least the MCS. An NR network may support multiple PT-RS densities defined in the time and / or frequency domains. 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 DMRS ports and PT-RS ports. The number of PT-RS ports may be less than the number of DMRS ports in the scheduled resources. Downlink PT-RS may be limited to the UE's scheduled time / frequency duration. Downlink PT-RS may be transmitted on symbols to facilitate phase tracking at the receiver.

[0107] The UE can transmit uplink DMRS to the base station for channel estimation. For example, the base station may use uplink DMRS for coherent demodulation of one or more uplink physical channels. For example, the UE may transmit uplink DMRS on PUSCH and / or PUCCH. 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 front-loaded DMRS pattern. A front-loaded DMRS can 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 PUSCH and / or PUCCH. The base station may semi-statically configure the UE with a number (e.g., a maximum number) of front-loaded DMRS symbols for PUSCH and / or PUCCH that the UE can use to schedule single-symbol DMRS and / or dual-symbol DMRS. The NR network may support a common DMRS structure for downlink and uplink (e.g., for cyclic prefix orthogonal frequency division multiplexing (CP-OFDM)), where the DMRS location, DMRS pattern, and / or DMRS scrambling sequence may be the same or different.

[0108] A PUSCH may include one or more layers, and a UE may transmit at least one symbol having a DMRS present on one or more layers of the PUSCH. In one example, the upper layers may constitute up to three DMRSs relative to the PUSCH.

[0109] Uplink PT-RS (which may be used by base stations for phase tracking and / or phase noise compensation) may or may not be present depending on the UE's RRC configuration. The presence and / or pattern of 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 uplink PT-RS may be associated with one or more DCI parameters, including at least the MCS. A radio network may support multiple uplink PT-RS densities defined in the time / frequency domain. The frequency domain density may be associated with at least one configuration of the scheduled bandwidth, if it exists. A UE may assume the same precoding for DMRS ports and PT-RS ports. The number of PT-RS ports may be less than the number of DMRS ports in the scheduled resources. For example, uplink PT-RS may be limited to the UE's scheduled time / frequency duration.

[0110] SRS can be transmitted by the UE to the base station for channel state estimation to support uplink channel-dependent scheduling and / or link fitting. The SRS transmitted by the UE may enable the base station to estimate the uplink channel state at one or more frequencies. The base station's scheduler can use the estimated uplink channel state to allocate one or more resource blocks for uplink push transmissions from the UE. The base station may semi-statically configure the UE with one or more SRS resource sets. In the case of 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 within one or more SRS resource sets (e.g., having identical / similar time-domain behavior, periodicity, aperiodicity, and / or similar characteristics) may be transmitted instantaneously (e.g., simultaneously). The UE may transmit one or more SRS resources within an SRS resource set. NR networks may support aperiodic, periodic, and / or semi-persistent SRS transmissions. 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 for the UE to select at least one of one or more configured sets of SRS resources. 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 pusher and an SRS are transmitted in the same slot, the UE may be configured to transmit the SRS after the pusher and the corresponding uplink DMRS transmission.

[0111] A base station may quasi-statistically configure a UE with one or more SRS configuration parameters indicating at least one of the following: SRS resource configuration identifier, number of SRS ports, time-domain behavior of the SRS resource configuration (e.g., representation of periodic, semi-persistent, or aperiodic SRS), slots, minislots, and / or subframe-level periodicity, offsets for periodic and / or aperiodic SRS resources, number of OFDM symbols in the SRS resource, start OFDM symbol of the SRS resource, SRS bandwidth, frequency-hopping bandwidth, period shift, and / or SRS sequence ID.

[0112] Antenna ports are defined such that the channel on which a symbol on an antenna port is carried can be inferred from the channel on 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, the receiver can infer the channel for carrying the second symbol on the antenna port (e.g., fade gain, multipath delay, and / or similar) from the channel for carrying the first symbol on the antenna port. The first and second antenna ports may be said to be quasi-copositional (QCL) if one or more large-scale characteristics of the channel on which the first symbol on the first antenna port is carried can be inferred from the channel on which the second symbol on the second antenna port is carried. One or more large-scale characteristics may include at least one of delay spread, Doppler spread, Doppler shift, mean gain, mean delay, and / or spatial receive (Rx) parameters.

[0113] Beam management is required for channels using beamforming. Beam management may include beam measurement, beam selection, and beam display. 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. The UE may perform downlink beam measurement and generate a beam measurement report based on a downlink reference signal (e.g., Channel Status Information Reference Signal (CSI-RS)). The UE may perform downlink beam measurement procedures after the RRC connection is set up at the base station.

[0114] Figure 11B shows an example of a Channel State Information Reference Signal (CSI-RS) mapped to time and frequency domains. The square shown in Figure 11B can span resource blocks (RBs) within the cell bandwidth. A base station can transmit one or more RRC messages containing CSI-RS resource configuration parameters that indicate one or more CSI-RSs. One or more of the following parameters can 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., position of symbols and resource elements (REs) within subframes), CSI-RS subframe configuration (e.g., subframe position, offset, and periodicity of radio frames), CSI-RS power parameters, CSI-RS sequence parameters, code division multiplexing (CDM) type parameters, frequency density, transmission comb, pseudo-collocation (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 Figure 11B can be configured for a UE with a UE-specific configuration. Three beams are shown in Figure 11B (beam #1, beam #2, and beam #3), and more or fewer beams can be configured. Beam #1 may be assigned as CSI-RS1101, which can be transmitted on one or more subcarriers within the RB of a first symbol. Beam #2 may be assigned as CSI-RS1102, which can be transmitted on one or more subcarriers within the RB of a second symbol. Beam #3 may be assigned as CSI-RS1103, which can be transmitted on one or more subcarriers within the RB of a third symbol. By using frequency division multiplexing (FDM), a base station may transmit another CSI-RS associated with a beam from another UE using other subcarriers within the same RB (e.g., those not used to transmit CSI-RS1101). By using time-domain multiplexing (TDM), the beams used for a UE may be configured so that the UE's beam uses symbols from the beams of other UEs.

[0116] The CSI-RS (e.g., CSI-RS1101, 1102, 1103) shown in Figure 11B may be transmitted by a base station and used by a UE for one or more measurements. For example, a UE may measure the reference signal received power (RSRP) of a configured CSI-RS resource. A base station may configure a UE with a reporting configuration, and based on the reporting configuration, the UE may report the RSRP measurement to the network (e.g., via one or more base stations). In one example, a 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, a base station may indicate one or more TCI states to a UE (e.g., via RRC signaling, MAC CE, and / or DCI). A UE may receive a downlink transmission with a received (Rx) beam determined based on one or more TCI states. In one example, a UE may or may not have beam correspondence capability. If the UE has beam correspondence capability, it may determine the spatial domain filter of the transmission (Tx) beam based on the spatial domain filter of the corresponding Rx beam. If the UE does not have beam correspondence capability, it may perform an uplink beam selection procedure to determine the 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 display an uplink beam for the UE based on measurements of one or more SRS resources transmitted by the UE.

[0117] In beam management procedures, the UE may evaluate (e.g., measure) the channel quality of a beam pair link, including one or more beam pair links, a transmitted beam transmitted by a base station, and a received 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 identities (e.g., beam index, reference signal index, or similar), RSRP, precoding matrix indicator (PMI), channel quality indicator (CQI), and / or rank indicator (RI).

[0118] Figure 12A shows examples of three downlink beam management procedures, P1, P2, and P3. Procedure P1 may enable UE measurements on the transmission (Tx) beams of a transmission receiving point (TRP) (or multiple TRPs) to support the 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 the beam set (shown as ellipses rotating counterclockwise, as indicated by dashed arrows in the top rows of P1 and P2). Beamforming at a UE may include an Rx beam sweep for the beam set (shown as ellipses rotating counterclockwise, as indicated by dashed arrows, as shown in the bottom rows of P1 and P3). Procedure P2 may be used to enable UE measurements on the Tx beams of a TRP (shown as ellipses rotating counterclockwise, as indicated by dashed arrows in the top row of P2). The UE and / or base station may perform step P2 using a smaller set of beams than those used in step P1, or using a narrower beam than those used in step P1. This may be referred to as beam refinement. The UE may perform step P3 for Rx beam determination by using the same Tx beam at the base station and sweeping the Rx beam at the UE.

[0119] Figure 12B shows examples of three uplink beam management procedures, U1, U2, and U3. Procedure U1 may be used to allow a base station to perform measurements on a UE's Tx beam 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 rotated around a measurement, 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 rotated counterclockwise, as indicated by dashed arrows in the top rows of U1 and U2). Procedure U2 may be used to allow a base station to adjust its Rx beam when the UE is using 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 a narrower beam than the beam used in procedure P1. This may be referred to as beam refinement. The UE may perform procedure U3 to adjust the Tx beam when the base station is using a fixed Rx beam.

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

[0121] A UE may measure the quality of a beampair link using one or more reference signals (RS) including one or more SS / PBCH blocks, one or more CSI-RS resources, and / or one or more demodulated reference signals (DMRS). The quality of a beampair link may be based on one or more of the following: block error rate (BLER), RSRP value, signal-to-interference plus noise ratio (SINR) value, reference signal reception quality (RSRQ) value, and / or CSI values ​​measured on the RS resources. A base station may indicate that an RS resource is quasi-co-located (QCL) with one or more DMRS of a channel (e.g., a control channel, a shared data channel, and / or similar). An RS resource and one or more DMRS of a channel may be QCLed if the channel characteristics from the transmission to the UE via the RS resources (e.g., Doppler shift, Doppler spread, mean delay, delay spread, spatial Rx parameter, fade, and / or similar) are similar to or identical to the channel characteristics from the transmission to the UE via the channel.

[0122] A network (e.g., the network's gNB and / or ng-eNB) and / or UE may initiate a random access procedure. A UE in the RRC_IDLE state and / or the RRC_INACTIVE state may initiate a random access procedure to request network connection setup. A UE may initiate a random access procedure from the RRC_CONNECTED state. A UE may initiate a random access procedure to request uplink resources (e.g., for uplink transmission of SR when no PUCCH resources are available) and / or obtain uplink timing (e.g., if 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 ones). A UE may initiate a random access procedure for beam fault recovery requests. A network may initiate a random access procedure to establish time alignment for handover and / or SCell addition.

[0123] Figure 13A illustrates a four-step competition-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 contain and / or be referred to as a preamble (or random access preamble). Msg2 1312 may contain and / or be referred to as a random access response (RAR).

[0124] Configuration message 1310 may be transmitted, for example, using one or more RRC messages. One or more RRC messages may indicate one or more random access channel (RACH) parameters to the UE. One or more RACH parameters may include at least one of the following: one or more general parameters for random access procedures (e.g., RACH-configGeneral), cell-specific parameters (e.g., RACH-configCommon), and / or dedicated parameters (e.g., RACH-configDedicated). The base station may broadcast or multicast one or more RRC messages to one or more UEs. One or more RRC messages may be UE-specific (e.g., dedicated RRC messages transmitted to the UE in the RRC_CONNECTED state and / or RRC_INACTIVE state). Based on one or more RACH parameters, the UE may determine the time-frequency resources and / or uplink transmission power for the transmission of Msg1 1311 and / or Msg3 1313. 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] One or more RACH parameters provided in configuration message 1310 may indicate one or more physical RACH (PRACH) opportunities available for transmission of Msg1 1311. One or more PRACH opportunities may be predefined. One or more RACH parameters may indicate one or more available sets of one or more PRACH opportunities (e.g., prach-ConfigIndex). One or more RACH parameters may indicate an association between (a) one or more PRACH opportunities and (b) one or more reference signals. One or more RACH parameters may indicate an association between (a) one or more preambles and (b) one or more reference signals. One or more reference signals may be SS / PBCH blocks and / or CSI-RS. For example, one or more RACH parameters may indicate the number of SS / PBCH blocks mapped to PRACH opportunities and / or the number of preambles mapped to SS / PBCH blocks.

[0126] One or more RACH parameters provided in configuration message 1310 may be used to determine the uplink transmission power for Msg1 1311 and / or Msg3 1313. For example, one or more RACH parameters may indicate reference power for preamble transmission (e.g., received target power and / or initial power for preamble transmission). There may be one or more power offsets indicated by one or more RACH parameters. For example, one or more RACH parameters may indicate the power ramping step, the power offset between SSB and CSI-RS, the power offset between transmissions of Msg1 1311 and Msg3 1313, and / or the power offset value between preamble groups. One or more RACH parameters may indicate one or more thresholds for the UE to determine at least one reference signal (e.g., SSB and / or CSI-RS) and / or uplink carriers (e.g., normal uplink (NUL) carrier and / or 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). RRC messages may be used to constitute 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 groups based on the 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 that has an RSRP exceeding an RSRP threshold (e.g., rsrp-ThresholdSSB and / or rsrp-ThresholdCSI-RS). The UE may, for example, select at least one preamble to be associated with one or more reference signals and / or the selected preamble group, if the association between one or more preambles and at least one reference signal is constituted by the RRC message.

[0128] The UE may determine the preamble based on one or more RACH parameters provided in configuration message 1310. For example, the UE may determine the preamble based on path loss measurements, RSRP measurements, and / or the size of Msg3 1313. As another example, one or more RACH parameters may indicate the preamble format, the maximum number of preamble transmissions, and / or one or more thresholds for determining one or more preamble groups (e.g., group A and group B). The base station may use one or more RACH parameters to configure the UE with associations between one or more preambles and one or more reference signals (e.g., SSB and / or CSI-RS). If associations are configured, the UE may determine the preambles to include in Msg1 1311 based on the associations. 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 (e.g., ra-ssb-OccasionMskIndex and / or ra-OccasionList) may indicate an association between a PRACH opportunity 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 the uplink transmission power for the preamble retransmission. The UE may select an initial preamble transmission power based on path loss measurements and / or target received preamble power configured by the network. The UE may decide to retransmit the preamble and ramp up the uplink transmission power. The UE may receive one or more RACH parameters (e.g., PREAMBLE_POWER_RAMPING_STEP) indicating the ramping step of the preamble retransmission. The ramping step may be the amount of incremental increase in uplink transmission power for retransmission. The UE may ramp up the uplink transmission power if it determines that the reference signal (e.g., SSB and / or CSI-RS) is the same as the previous preamble transmission. The UE may count the number of preamble transmissions and / or retransmissions (e.g., PREAMBLE_TRANSMISSION_COUNTER). The UE may determine that a random access procedure has failed and completed if, for example, the number of preamble transmissions exceeds a threshold determined by one or more RACH parameters (e.g., preambleTransMax).

[0130] Msg2 1312 received by the UE may contain RARs. In some scenarios, Msg2 1312 may contain 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 displayed on the PDCCH using a Random Access RNTI (RA-RNTI). Msg2 1312 may indicate that Msg1 1311 has been received by the base station. Msg2 1312 may contain time alignment commands that the UE can use to adjust the transmission timing of the UE, scheduling permission for the transmission of Msg3 1313, and / or a temporary cell RNTI (TC-RNTI). After transmitting the preamble, the UE may initiate a time window (e.g., ra-ResponseWindow) to monitor the PDCCH of Msg2 1312. The UE may determine when to start a time window based on the PRACH opportunity the UE uses to transmit the preamble. For example, the UE may start a time window after one or more symbols of the last symbol of the preamble (e.g., on the first PDCCH opportunity from the end of preamble transmission). One or more symbols may be determined based on numerology. The PDCCH may be in a common lookup space composed of RRC messages (e.g., a Type1-PDCCH common lookup space). The UE may identify a 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 a PRACH opportunity in which the UE transmits the preamble. For example, the UE may determine the RA-RNTI based on the OFDM symbol index, slot index, frequency domain index, and / or the UL carrier indicator of the PRACH opportunity. An example of an RA-RNTI may be as follows: RA-RNTI=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id Here, s_id can be the index of the first OFDM symbol of the PRACH opportunity (e.g., 0 ≤ s_id < 14), t_id can be the index of the first slot of the PRACH opportunity in the system frame (e.g., 0 ≤ t_id < 80), f_id can be the index of the PRACH opportunity in the frequency domain (e.g., 0 ≤ f_id < 8), and ul_carrier_id can be the UL carrier used for preamble transmission (e.g., 0 for a NUL carrier, 1 for a SUL carrier). A UE may transmit Msg3 1313 in response to the successful reception of Msg2 1312 (for example, using the resources identified in Msg2 1312). Msg3 1313 may be used for conflict resolution in a conflict-based random access procedure, for example, as shown in Figure 13A. In some scenarios, multiple UEs may transmit the same preamble to a base station, and the base station may provide a RAR corresponding to the UEs. If multiple UEs interpret the RAR as corresponding to themselves, a mismatch may occur. Conflict resolution (e.g., the use of Msg3 1313 and Msg4 1314) can be used to increase the likelihood that a UE will not mistakenly use the identity of another UE. To implement conflict resolution, a UE may include a device identifier in Msg3 1313 (e.g., C-RNTI, if assigned, TC-RNTI included in Msg2 1312, and / or any other suitable identifier).

[0131] Msg4 1314 may be received after or in response to the transmission of Msg3 1313. If a C-RNTI was included in Msg3 1313, the base station uses the C-RNTI to address the UE on the PDCCH. If the UE's unique C-RNTI is found on the PDCCH, the random access procedure is determined to have completed successfully. If a TC-RNTI is included in Msg3 1313 (e.g., if the UE is in the RRC_IDLE state or 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 the MAC PDU matches the CCCH SDU transmitted (e.g., transmitted) in Msg3 1313, or otherwise contains the corresponding UE conflict resolution identity MAC CE, the UE may determine that conflict resolution was successful, and / or the UE may determine that the random access procedure has completed successfully.

[0132] A UE may consist of a complementary uplink (SUL) carrier and a normal uplink (NUL) carrier. Initial access (e.g., random access procedures) may be supported on the uplink carrier. For example, a base station may configure a UE with two separate RACH configurations, i.e., one for the SUL carrier and the other for the NUL carrier. For random access within a cell configured with SUL carriers, 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 below the broadcast threshold. Uplink transmission of a random access procedure (e.g., Msg1 1311 and / or Msg3 1313) may remain on the selected carrier. In one or more instances, the UE may switch the uplink carrier during a random access procedure (e.g., between Msg1 1311 and Msg3 1313). For example, the UE may determine and / or switch the uplink carriers for Msg1 1311 and / or Msg3 1313 based on a channel clear assessment (e.g., listen before talk).

[0133] Figure 13B illustrates a two-step, non-conflict random access procedure. Similar to the four-step, conflict-based random access procedure shown in Figure 13A, the base station may transmit a configuration message 1320 to the UE before the procedure begins. Configuration message 1320 may be similar in some respects to 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 shown in Figure 13A, respectively. As can be seen from Figures 13A and 13B, a non-conflict random access procedure may not include messages similar to Msg3 1313 and / or Msg4 1314.

[0134] The uncontested random access procedure shown in Figure 13B may be initiated for beam fault recovery, other SI requests, SCell additions, and / or handovers. For example, a base station may display or assign to the UE the preamble to be used for Msg1 1321. The UE may receive a display of the preamble (e.g., ra-PreambleIndex) from the base station via PDCCH and / or RRC.

[0135] After transmitting the preamble, the UE may initiate a time window (e.g., ra-ResponseWindow) to monitor the RAR's PDCCH. In the case of a beam fault recovery request, the base station may configure the UE with a separate time window and / or a separate PDCCH within the search space indicated by the RRC message (e.g., recoverySearchSpaceId). The UE may monitor PDCCH transmissions destined for Cell RNTI (C-RNTI) in the search space. In the uncontested random access procedure shown in Figure 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 C-RNTI. The UE may determine that the random access procedure has completed successfully, for example, if the UE receives a RAR containing a preamble identifier corresponding to the preamble transmitted by the UE, and / or if the RAR contains a MAC sub-PDU containing the preamble identifier. The UE may determine the response as an acknowledgment of the response to the SI request.

[0136] Figure 13C illustrates another two-step random access procedure. Similar to the random access procedures shown in Figures 13A and 13B, the base station may transmit a configuration message 1330 to the UE before the procedure begins. The configuration message 1330 may be similar in some respects to configuration messages 1310 and / or 1320. Figure 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 via uplink transmission. Msg A 1331 may include one or more transmissions of the preamble 1341 and / or one or more transmissions of the transport block 1342. Transport block 1342 may include content similar to and / or equivalent to the content of Msg 3 1313 shown in Figure 13A. Transport block 1342 may include UCI (e.g., SR, HARQ ACK / NACK, and / or similar). 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 to and / or equivalent to the content of Msg 2 1312 (e.g., RAR) shown in Figures 13A and 13B, and / or Msg 4 1314 shown in Figure 13A.

[0138] The UE may initiate the two-step random access procedure shown in Figure 13C for licensed and / or unlicensed spectra. The UE may decide whether to initiate the two-step random access procedure based on one or more factors. 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, cell size, the UE's RRC status, the spectrum type (e.g., licensed vs. unlicensed), and / or any other preferred factors.

[0139] The UE may determine the radio resources and / or uplink transmission power for the transport block 1342 contained in the preamble 1341 and / or Msg A 1331 based on the two-step RACH parameters contained in configuration message 1330. The RACH parameters may indicate the modulation and coding scheme (MCS), time-frequency resources, and / or power control for the preamble 1341 and / or 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] Transport block 1342 may include data (e.g., latency-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 the following: a preamble identifier, timing progress commands, power control commands, uplink authorization (e.g., radio resource allocation and / or MCS), a UE identifier for conflict resolution, and / or RNTI (e.g., C-RNTI or TC-RNTI). The UE may determine that the two-step random access procedure has been successfully completed if the preamble identifier in Msg B 1332 matches a preamble transmitted by the UE, and / or the UE identifier in Msg B 1332 matches the UE identifier in Msg A 1331 (e.g., transport block 1342).

[0141] UEs and base stations may exchange control signaling. Control signaling may be referred to as L1 / L2 control signaling and may originate from the PHY layer (e.g., layer 1) and / or the MAC layer (e.g., layer 2). 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] Downlink control signaling may include downlink scheduling assignments, uplink scheduling authorizations indicating uplink radio resources and / or transport formats, slot format information, preemption indications, power control commands, and / or other optional 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) common to a group of UEs.

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

[0144] DCIs can 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 notifications. A 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 broadcast transmission of system information. A 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 unicast transmission of dynamic scheduling and / or triggers for random access in PDCCH sequences. A DCI with a scrambled CRC parity bit in a temporary cell RNTI (TC-RNTI) may exhibit conflict resolution (e.g., Msg3 similar to Msg3 1313 shown in Figure 13A). Other RNTI encodings 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 similar.

[0145] Depending on the purpose and / or content of the DCI, the base station may transmit the DCI in one or more DCI formats. For example, DCI format 0_0 can be used for scheduling pushes within a cell. DCI format 0_0 may be a fallback DCI format (e.g., with a compact DCI payload). DCI format 0_1 ​​may be used for scheduling pushes within a cell (e.g., with a larger DCI payload than DCI format 0_0). DCI format 1_0 can be used for scheduling PDSCHs within a cell. DCI format 1_0 may be a fallback DCI format (e.g., with a compact DCI payload). DCI format 1_1 may be used for scheduling PDSCHs within a cell (e.g., with a larger DCI payload than DCI format 1_0). DCI format 2_0 may be used to provide a slot format display to a group of UEs. DCI format 2_1 may be used to notify a group of UEs of physical resource blocks and / or OFDM symbols that the UEs assume are not intended for transmission to the UEs. DCI format 2_2 may be used for transmitting Transmission Power Control (TPC) commands for PUCCH or PUSCH. DCI format 2_3 may be used for transmitting a group of TPC commands for SRS transmission by one or more UEs. New DCI formats may be defined in future releases. DCI formats may have different DCI sizes or may share the same DCI size.

[0146] After scrambling the DCI with RNTI, the base station may process the DCI with channel coding (e.g., polar 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 DCI payload size and / or base station coverage, the base station may transmit the DCI over a PDCCH occupying several consecutive control channel elements (CCEs). The number of consecutive CCEs (referred to as the aggregation level) can be 1, 2, 4, 8, 16, and / or any other suitable number. A CCE may contain a number of resource element groups (REGs) (e.g., 6). A REG may contain resource blocks within OFDM symbols. Mapping the coded and modulated DCI onto resource elements may be based on mapping CCEs and REGs (e.g., CCE-to-REG mapping).

[0147] Figure 14A shows an example of a CORESET configuration for a bandwidth portion. A base station may transmit DCI over a PDCCH on one or more control resource sets (CORESETs). A CORESET may contain time-frequency resources that the UE attempts to decode the DCI using one or more lookup spaces. A base station may configure a CORESET within a time-frequency domain. In the example in Figure 14A, the first CORESET 1401 and the second CORESET 1402 occur in the first symbol in the slot. The first CORESET 1401 overlaps with the second CORESET 1402 in the frequency domain. The third CORESET 1403 occurs in the third symbol in the slot. The fourth CORESET 1404 occurs in the seventh symbol in the slot. A CORESET may have a different number of resource blocks within a frequency domain.

[0148] Figure 14B shows an example of CCE-to-REG mapping for DCI transmissions on CORESET and PDCCH processing. CCE-to-REG mapping can be interleaved mapping (e.g., for the purpose of providing frequency diversity) or non-interleaved mapping (e.g., for the purpose of facilitating interference adjustment and / or frequency-selective transmission of control channels). A base station may perform different or identical CCE-to-REG mappings on different CORESETs. A CORESET may be associated with CCE-to-REG mappings in an RRC configuration. A CORESET may consist of antenna port pseudo-collocation (QCL) parameters. The antenna port QCL parameters may indicate QCL information for demodulated reference signals (DMRS) for PDCCH reception within the CORESET.

[0149] A base station may transmit an RRC message to the UE containing configuration parameters for one or more CORESETs and one or more search space sets. The configuration parameters may indicate the relationship between the search space set and the CORESET. A search space set may contain 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 a common search space set may be predefined and known to the UE. The set of CCEs in a UE-specific search space set may be configured based on the UE's identity (e.g., C-RNTI).

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

[0151] The UE may transmit uplink control signaling (e.g., uplink control information (UCI)) to the base station. Uplink control signaling may include a Hybrid Automatic Repeat Request (HARQ) acknowledgment for a received DL-SCH transport block. After receiving the DL-SCH transport block, the UE may transmit the HARQ acknowledgment. Uplink control signaling may include channel status information (CSI) indicating the channel quality of the physical downlink channel. The UE may transmit the CSI to the base station. Based on the received CSI, the base station may determine transmission format parameters for downlink transmission (e.g., multi-antenna and beamforming schemes). Uplink control signaling may include a scheduling request (SR). The UE may transmit an SR indicating that uplink data is available for transmission to the base station. The UE may transmit UCI (e.g., HARQ acknowledgment (HARQ-ACK), CSI report, SR, etc.) over the physical uplink control channel (PUCCH) or the physical uplink shared channel (PUSCH). The UE may transmit uplink control signaling via PUCCH using one of several PUCCH formats.

[0152] There are five possible PUCCH formats, and the UE may determine the PUCCH format based on the size of the UCI (e.g., the number of uplink symbols and the number of UCI bits in the UCI transmission). PUCCH format 0 may have the length of one or two OFDM symbols and may contain two or fewer bits. The UE may use PUCCH format 0 to transmit a UCI on a PUCCH resource if the transmission exceeds one or two symbols and the number of HARQ-ACK information bits with positive or negative SR (HARQ-ACK / SR bits) is one or two. PUCCH format 1 may occupy a number between 4 and 14 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 exceeds one or two symbols and the number of UCI bits is two or more. PUCCH format 3 may occupy a number between 4 and 14 OFDM symbols and may include more than 2 bits. A UE may use PUCCH format 3 if the transmission consists of four or more symbols, the number of UCI bits is two or more, and the PUCCH resource does not contain orthogonal cover codes. PUCCH format 4 may occupy a number between 4 and 14 OFDM symbols and may include more than 2 bits. A UE may use PUCCH format 4 if the transmission consists of four or more symbols, the number of UCI bits is two or more, and the PUCCH resource contains orthogonal cover codes.

[0153] A base station may transmit configuration parameters for multiple PUCCH resource sets to a UE, for example, using RRC messages. Multiple PUCCH resource sets (e.g., up to four sets) may be configured on a cell's uplink BWP. A PUCCH resource set may consist of multiple PUCCH resources, each having a PUCCH resource identified by a PUCCH resource set index, a PUCCH resource identifier (e.g., pucch-Resourceid), and / or the number of UCI information bits (e.g., maximum number) that the UE may transmit using one of the multiple PUCCH resources in the PUCCH resource set. When multiple PUCCH resource sets are configured, 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 2 or less, the UE may select the first PUCCH resource set whose 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 with 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 with 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 the third value (e.g., 1406), the UE may select a fourth PUCCH resource set with a PUCCH resource set index equal to "3".

[0154] After determining a PUCCH resource set from 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 a PUCCH resource based on the PUCCH resource indicator in the DCI (e.g., DCI format 1_0 or DCI format 1_1) received on the PDCCH. The 3-bit PUCCH resource indicator in the DCI may indicate one of the 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] Figure 15 shows 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 base station 1504 may be part of a mobile communication network, such as the mobile communication network 100 shown in Figure 1A, the mobile communication network 150 shown in Figure 1B, or other communication networks. Although only one wireless device 1502 and one base station 1504 are shown in Figure 15, it will be understood that a mobile communication network may include one or more UEs and / or one or more base stations having the same or similar configuration as shown in Figure 15.

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

[0157] In the downlink, data transmitted from base station 1504 to radio 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, the core network. In the uplink, data transmitted from radio device 1502 to base station 1504 may be provided to processing system 1518 of radio device 1502. Processing systems 1508 and 1518 may process the data for transmission by implementing OSI functions of layers 3 and 2. Layer 2 may include, for example, the SDAP layer, PDCP layer, RLC layer, and MAC layer with respect to Figures 2A, 2B, 3, and 4A. Layer 3 may include the RRC layer with respect to Figure 2B.

[0158] Data that has been processed by processing system 1508 and is to be transmitted to radio device 1502 may be provided to transmission processing system 1510 of base station 1504. Similarly, data that has been processed by processing system 1518 and is to be transmitted to base station 1504 may be provided to transmission processing system 1520 of radio device 1502. Transmission processing systems 1510 and 1520 may implement OSI functions of layer 1. Layer 1 may include a PHY layer with respect to Figures 2A, 2B, 3, and 4A. For transmission processing, the PHY layer may perform, for example, forward error correction coding of the transport channel, interleaving, rate matching, mapping of the transport channel to a physical channel, modulation of the physical channel, multiple input multiple output (MIMO) or multi-antenna processing, and / or similar.

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

[0160] As shown in Figure 15, the wireless device 1502 and the base station 1504 may include multiple antennas. 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), transmission / reception diversity, and / or beamforming. In other examples, the wireless device 1502 and / or the base station 1504 may have a single antenna.

[0161] Processing systems 1508 and 1518 may be associated with memories 1514 and 1524, respectively. Memories 1514 and 1524 (e.g., one or more non-temporary computer-readable media) may store computer program instructions or code that can be executed by processing systems 1508 and / or 1518 to perform one or more of the functions considered in this application. Although not shown in Figure 15, transmission processing systems 1510, 1520, reception processing system 1512, and / or reception processing system 1522 may be coupled to memories (e.g., one or more non-temporary computer-readable media) that store computer program instructions or code that can be executed to perform one or more of their respective functions.

[0162] Processing system 1508 and / or processing system 1518 may include one or more controllers and / or one or more processors. One or more controllers and / or one or more processors may include, for example, general-purpose processors, digital signal processors (DSPs), microcontrollers, application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs) and / or other programmable logic devices, discrete gates and / or transistor logic, discrete hardware components, onboard units, or any combination thereof. Processing system 1508 and / or processing system 1518 may perform at least one of signal coding / processing, data processing, power control, input / output processing, and / or any other functions that may enable the wireless device 1502 and 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 / or one or more peripheral devices 1526, respectively. One or more peripheral devices 1516 and one or more peripheral devices 1526 may include software and / or hardware that provide features and / or functions, such as speakers, microphones, keypads, display devices, touchpads, power supplies, satellite transceivers, Universal Serial Bus (USB) ports, hands-free headsets, frequency modulation (FM) radio units, media players, internet browsers, electronic control units (e.g., for vehicles), and / or one or more sensors (e.g., accelerometers, gyroscopes, temperature sensors, radar sensors, lidar sensors, ultrasonic sensors, light sensors, cameras, and / or similar). Processing system 1508 and / or processing system 1518 may receive user input data from one or more peripheral devices 1516 and / or one or more peripheral devices 1526, and / or provide user output data. The processing system 1518 within the wireless device 1502 may be configured to receive power from a power source and / or distribute power to other components within the wireless device 1502. The power source may 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 may be connected to GPS chipsets 1517 and 1527, respectively. The GPS chipsets 1517 and 1527 may be configured to provide geographic location information for the wireless device 1502 and the base station 1504, respectively.

[0164] Figure 16A shows an exemplary structure for uplink transmission. A baseband signal representing a physical uplink shared channel may perform one or more functions. These functions may include at least one of the following: scrambling, modulation of scrambled bits to generate complex-valued symbols, mapping of complex-valued modulated symbols onto one or more transmission layers, conversion precoding to generate complex-valued symbols, precoding of complex-valued symbols, mapping of precoded complex-valued symbols to resource elements, generation of complex-valued time-domain single-carrier frequency-division multiplexing (SC-FDMA) or CP-OFDM signals to antenna ports, and / or similar. In one example, if conversion precoding is enabled, an SC-FDMA signal for uplink transmission may be generated. In one example, if conversion precoding is not enabled, a CP-OFDM signal for uplink transmission may be generated by Figure 16A. These functions are shown as examples, and it is expected that other mechanisms may be implemented in various embodiments.

[0165] Figure 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 to the antenna port. Filtering may be used before transmission.

[0166] Figure 16C shows an exemplary structure of downlink transmission. The baseband signal representing the physical downlink channel can perform one or more functions. These functions may include scrambling the encoded bits in the codeword to be transmitted over the physical channel, modulating the scrambled bits to generate a complex-valued modulation symbol, mapping the complex-valued modulation symbol to one or more transmission layers, precoding the complex-valued modulation symbol on the layer for transmission over the antenna port, mapping the complex-valued modulation symbol to resource elements at the antenna port, generating a complex-valued time-domain OFDM signal for each antenna port, and / or similar. These functions are shown as examples, and it is expected that other mechanisms may be implemented in various embodiments.

[0167] Figure 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 the antenna port. Filtering can be used before transmission.

[0168] A wireless device may receive one or more messages (e.g., RRC messages) from a base station that include configuration parameters for multiple cells (e.g., primary cells, secondary cells). The wireless device may communicate with at least one base station (e.g., two or more base stations in a dual connection) via multiple cells. One or more messages (e.g., as part of configuration parameters) may include parameters for the physical, MAC, RLC, PCDP, SDAP, and RRC layers to configure the wireless device. For example, configuration parameters may include parameters for configuring physical and MAC layer channels, bearers, etc. For example, 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, once started, begins execution and may continue execution until stopped or expired. A timer can be started when it is not running, or restarted when it is running. A timer can be associated with a value (for example, a timer can start or restart from a certain value, or start from zero and expire when a value is reached). The duration of a timer may not be updated until the timer is stopped or expires (for example, by BWP switching). Timers can be used to measure the duration / window of a process. Where 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 the multiple ways to implement a timer may be used to measure the duration / window of a procedure. For example, a random access response window timer may be used to measure the window time for receiving a random access response. In one example, instead of the start and expiration of a random access response window timer, a time difference between two timestamps may be used. When a timer is restarted, the process for measuring the time window may be restarted. Other exemplary implementations may be provided for restarting the measurement of a time window.

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

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

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

[0173] In one example, a wireless device may receive an active command to activate one or more activated path loss reference signals among one or more path loss reference signals. In existing techniques, the default path loss reference signal may be one of one or more activated active path loss reference signals mapped to 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] A wireless device may determine the transmission power based on a default path loss reference signal. The wireless device may transmit a transport block with / using the transmission power.

[0175] For example, a wireless device may function with multiple TRPs, including a first TRP and a second TRP (e.g., transmitting to / receiving from multiple TRPs). The wireless device may receive a DCI that schedules the repetition of a transport block (e.g., PUSCH) among the first and second TRPs. The wireless device may transmit a transport block in one or more first transmission opportunities, for example, toward / to / for a first TRP, and in one or more second transmission opportunities, for example, toward / to / for a second TRP. This can increase the reliability of the transport block transmission. For example, when the first TRP experiences interference (e.g., due to a tree, building, etc.), the second TRP may receive the transport block.

[0176] For example, a DCI that schedules the repetition of a transport block may not include an SRI field. A DCI that does not include an SRI field may include, for example, a DCI that does not include a first SRI field and a DCI that does not include a second SRI field. A DCI that does not include an SRI field may include, for example, a DCI that includes a first SRI field and does not include a DCI that does not include a second SRI field. In implementations of existing technologies, 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 that does not include an SRI field. The wireless device may transmit the repetition of the transport block with / using a transmission power determined based on the default path loss reference signal. Using the (same) transmission power for two sets of transport block repetitions, or determining the transmission power based on the (same) default path loss reference signal, may not be efficient. For example, the repetition may be transmitted to a first TRP and a second TRP that may not be in the same location. The locations / directions of the first and second TRPs may differ. Because the first TRP and the second TRP may not be in the same location, the first and second TRPs may be subject to different channel conditions (e.g., channel fade, distance, interference, etc.). Using the (same) transmission power and / or determining the transmission power based on the (same) default path loss reference signal may result in inaccurate transmission power (e.g., lower or higher than the required transmission power) for repeated transport blocks. A wireless device may transmit a transport block toward at least one of the first and second TRPs with / using inaccurate transmission power, which may increase interference to other cells and / or wireless devices.

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

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

[0179] The first of 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 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 1 (e.g., sri-PUSCH-PowerControlId=1). The second of the two default path loss reference signals may be 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] A wireless device may determine two transmission powers based on two default path loss reference signals. The wireless device may transmit a transport block toward / to a first TRP in one or more first transmission opportunities using / with a first transmission power of the two transmission powers. The wireless device may determine a first transmission power based on a first default path loss reference signal. The wireless device may transmit a transport block toward / to a second TRP in one or more second transmission opportunities using / with a second transmission power of the two transmission powers. The wireless device may determine a second transmission power based on a second default path loss reference signal.

[0181] In exemplary embodiments, the DCI for scheduling the repetition of a transport block may include a first SRI field but 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 a transport block. The wireless device may transmit a transport block in one or more first transmission opportunities toward / to a first TRP with / using a first transmission power determined based on the path loss reference signal indicated by the first SRI field. The wireless device may transmit a transport block in one or more second transmission opportunities toward / to a second TRP with / using a second transmission power determined based on a second default path loss reference signal.

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

[0183] Figures 17, 18, and 19 show an example of power control in an uplink channel repeat according to one embodiment of the present disclosure. Figure 20 shows an example of an uplink repeat scheme according to one embodiment of the present disclosure.

[0184] A wireless device may receive one or more messages (for example, at time T0 in Figures 17-20). In one example, the wireless device may receive one or more messages from a base station. One or more messages may contain one or more configuration parameters. In one example, one or more configuration parameters may be RRC configuration parameters. In another example, one or more configuration parameters may be RRC reconfiguration parameters.

[0185] In one example, one or more configuration parameters may be for a cell. In one example, at least one of the one or more configuration parameters may be for a cell. In one example, a cell may be a primary cell (PCell). In one example, a cell may be a secondary cell (SCell). A cell may be a secondary cell composed of PUCCHs (e.g., a PUCCH SCell). In one example, a cell may be an unlicensed cell, for example, operating in an unlicensed band. In one example, a cell may be a licensed cell, for example, operating in a licensed band. In one example, a cell may operate in a first frequency range (FR1). FR1 may include, for example, a frequency band below 6 GHz. In one example, a 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 the cell at a first time and a first frequency. The wireless device may perform downlink reception (e.g., PDCCH, PDSCH) through the cell at a second time and a second frequency. In one example, the cell may operate in time-division duplex (TDD) mode. In TDD mode, the first and second frequencies may be the same. In TDD mode, the first and second times may be different. In one example, the cell may operate in frequency-division duplex (FDD) mode. In FDD mode, the first and second frequencies may be different. In FDD mode, the first and second times may be the same.

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

[0188] For example, a cell may contain multiple BWPs. Multiple BWPs may contain one or more uplink BWPs, including the cell's uplink BWP. Multiple BWPs may contain one or more downlink BWPs, including the cell's downlink BWP.

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

[0190] In one example, when one or more uplink BWPs are active, a wireless device may transmit uplink signals / channels (e.g., PUCCH, preamble, PUSCH, PRACH, SRS, etc.) over / through the uplink BWPs. In another example, when one or more uplink BWPs are inactive, a wireless device may not transmit uplink signals / channels (e.g., PUCCH, preamble, PUSCH, PRACH, SRS, etc.) over / through the uplink BWPs.

[0191] In one example, a wireless device may activate one of the downlink BWPs (Broadlink Power WPs) of a cell. In one example, activating a downlink BWP may include the wireless device setting (or switching to) the downlink BWP as the 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] For example, a wireless device may activate one or more uplink BWPs of a cell. For example, activating an uplink BWP may include the wireless device setting (or switching to) the uplink BWP as the cell's active uplink BWP. For example, activating an uplink BWP may include the wireless device setting the uplink BWP to an active state. For example, activating an uplink BWP may include switching the uplink BWP from an inactive state to an active state.

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

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

[0195] For example, a wireless device may transmit a UE capability message, which may include UE capability information, to a base station.

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

[0197] For example, UE capability information may indicate support for repeated transmission of uplink signals (e.g., PUCCH, PUSCH, transport block, SRS). Repeats may occur, for example, in TDM. Repeats may occur, for example, in FDM. Repeats may occur, for example, in SDM / SFN (e.g., spatial domain / division multiplexing). Repeats may occur, for example, in CDM (e.g., code domain / division multiplexing). A wireless device may repeat the transmission of uplink signals, for example, based on the UE capability information indicating support for repeated transmission of uplink signals.

[0198] In the embodiment, one or more configuration parameters may represent 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 represent multiple path loss reference RSs for a cell. One or more configuration parameters may represent multiple path loss reference RSs for the (active) uplink BWP of a 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 Figures 17-19, the multiple path loss reference RSs are path loss RS 0, path loss RS 1, ..., path loss RS M.

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

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

[0201] Multiple power control parameter sets include sri-PUSCH-PowerControl 0, sri-PUSCH-PowerControl 1, ..., sri-PUSCH-PowerControl N, as shown in Figure 19.

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

[0203] For example, 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 updates for PUSCH / SRS. Based on one or more configuration parameters indicating / include a path loss RS update parameter, the radio 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 out of a plurality of path loss reference RSs and one or more power control parameter sets out of a plurality of power control parameter sets. For example, the active command may update the mapping between the value of a power control parameter set index (e.g., sri-PUSCH-PowerControlId) that identifies / indicates a power control parameter set and the value of a path loss reference RS index (e.g., PUSCH-PathlossReferenceRS-Id) that identifies / indicates a path loss reference RS. The radio device may, for example, map a power control parameter set to a path loss reference RS based on receiving an active command that updates the mapping between the power control parameter set and the path loss reference RS. Multiple path loss criterion RSs may include path loss criterion RSs. Multiple power control parameter sets may include power control parameter sets. Multiple path loss criterion RS indices may include path loss criterion RS indices. Multiple power control parameter set indices may include power control parameter indices.

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

[0205] In one example, one or more active commands may indicate / activate / update a mapping between one or more path loss criterion RSs among several path loss criterion RSs and several power control parameter sets. One or more path loss criterion RSs may be mapped to (or linked to or associated with) several power control parameter sets based on receiving one or more active commands that indicate / activate / update the mapping. A wireless device may map (or update) one or more path loss criterion RSs to / for several power control parameter sets based on receiving one or more active commands. One or more active commands may indicate / activate / update one or more path loss criterion RSs among several path loss criterion RSs. In Figure 19, one or more path loss criterion RSs may be path loss RS 23, path loss RS 41, path loss RS 47, and path loss RS 62.

[0206] One or more configuration parameters may indicate one or more path loss reference RS indices / identifiers for one or more path loss reference RSs (e.g., provided by the higher-level parameter PUSCH-PathlossReferenceRS-Id,pucch-PathlossReferenceRS-Id). For example, each of the one or more path loss reference RSs may be identified / indicated by the respective path loss reference RS index of one or more path loss reference RS indices. 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 criterion RSs may be mapped (or linked or associated) with multiple power control parameter sets. Each power control parameter set may represent (or be mapped or linked) with one or more path loss criterion RSs.

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

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

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

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

[0212] For example, the mapping between one or more path loss criteria RS and multiple power control parameter sets may be a one-to-many mapping. For example, a first path loss criterion RS among the one or more path loss criterion RS may be mapped (or linked or associated) with a first power control parameter set among multiple power control parameter sets. The first path loss criterion RS may be mapped with a second power control parameter set among multiple power control parameter sets, which is different from the first power control parameter set.

[0213] In one example, multiple power control parameter sets may represent one or more path loss criterion RSs from among multiple path loss criterion RSs. Multiple power control parameter sets representing one or more path loss criterion RSs may include multiple power control parameter sets that are mapped (or linked or associated) to one or more path loss criterion RSs. In one example, one power control parameter set among multiple power control parameter sets may be mapped (or linked or associated) to one of one or more path loss criterion RSs. Power control parameter sets may represent path loss criterion RSs. In one example, each power control parameter set among multiple power control parameter sets may be mapped (or linked or associated) to each of one or more path loss criterion RSs from among multiple path loss criterion RSs.

[0214] In one example, one of several path loss criterion RSs may be mapped (or linked or associated) to one of several power control parameter sets. A power control parameter set may indicate (or be mapped to) a path loss criterion RS. In one example, one or more active commands may indicate (or include identifying / indicating) a path loss criterion RS for a power control parameter set (that is mapped / linked / associated). One or more path loss criterion RS indices may include path loss criterion RS indices. For example, in Figure 19, one or more active commands indicate (or map, 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] For example, one or more active commands may include one or more fields. The first 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 from among multiple path loss reference RS indices that identify / indicate the path loss reference RS (e.g., provided by the higher-layer parameter PUSCH-PathlossReferenceRS-Id). The second 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 from among multiple power control parameter set indices of multiple power control parameter sets that identify / indicate the power control parameter set. The wireless device may map / update the path loss reference RS to / for the 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 contain one or more power control parameter set indices from a plurality of power control parameter set indices. One or more power control parameter set indices may indicate / identify one or more power control parameter sets from a plurality of power control parameter sets. The wireless device may map / update the path loss criterion RS indicated by the first field to / for one or more power control parameter sets indicated by the second field.

[0217] In one example, one or more configuration parameters may indicate multiple SRS resource sets, each containing at least two SRS resource sets. These at least two SRS resource sets may include a first SRS resource set (e.g., SRS resource set 1 in Figure 17) and a second SRS resource set (e.g., SRS resource set 2 in Figure 17).

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

[0219] For example, one of at least two SRS resource sets (e.g., the first SRS resource set and / or the second SRS resource set) may be aperiodic. One or more configuration parameters may indicate an aperiodic resource type for an SRS resource set (e.g., the resource type of a higher-level parameter is set to aperiodic).

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

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

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

[0223] The SRS usage parameter can be (and set to) non-codebook (e.g., use = non-codebook). At least two SRS resource sets can be used for non-codebook-based uplink transmissions (e.g., PUSCH transmissions) based on the SRS usage parameter which is non-codebook (and is set to). Each of the at least two SRS resource sets can be used for non-codebook-based uplink transmissions.

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

[0225] For example, the first SRS usage parameter can be (or can be set to) a codebook. The second SRS usage parameter can be (or can be set to) a codebook.

[0226] For example, the first SRS usage parameter can be (or can be set to) non-codebook. The second SRS usage parameter can be (or can be set to) non-codebook.

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

[0228] DCI may not be DCI Format 0-0, for example.

[0229] For example, DCI may schedule the transmission of a transport block (e.g., PUSCH transmission). DCI may schedule the transmission of a transport block (e.g., TB in Figures 17-19) over / through an uplink channel (e.g., PUSCH, PUCCH). DCI may include a dynamic uplink grant for the transmission of the transport block. A wireless device may transmit a transport block (e.g., TB in Figures 17-19) via an uplink resource indicated by, for example, DCI (or a dynamic uplink grant). An uplink channel may include an uplink resource. An (active) uplink BWP may include an uplink resource.

[0230] For example, one or more configuration parameters may indicate one or more configured uplink grants (e.g., by the higher-layer parameter ConfiguredGrantConfig). One or more configured uplink grants may include a configured uplink grant. For example, a configured uplink grant may be a Type 2 configured uplink grant (or configured grant type 2). In a Type 2 configured uplink grant, PDCCH may indicate / provide the uplink grant. DCI (or Layer 1 signaling) may indicate a configured uplink grant active. A wireless device may store an uplink grant as a configured uplink grant based on receiving a DCI indicating a configured uplink grant active. For example, DCI may activate a configured uplink grant. For example, a wireless device may transmit a transport block (e.g., TB in Figures 17-19) for a configured uplink grant over / through an uplink channel (e.g., PUSCH, PUCCH). A wireless device may transmit a transport block (e.g., a PUSCH transmission) through one or more periodic uplink resources of a configured uplink grant. 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 uplink resources.

[0231] 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 the number of repetitions for a transport block (e.g., numberofrepetitions). The resource allocation table may include the 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] For example, the numberofrepetitions of a higher-level parameter may not exist in the resource allocation table indicated by the TDRA field in DCI. One or more configuration parameters may not include the number of repetitions of a higher-level parameter in the resource allocation table. For example, one or more configuration parameters may indicate the number of repetitions (e.g., push-AggregationFactor). In Figures 17 and 18, the number of repetitions is equal to 4 (e.g., push-AggregationFactor=4). In Figure 19, the number of repetitions is equal to 2 (e.g., push-AggregationFactor=2).

[0233] For example, the number of repetitions may be for the repetition of a transport block via an uplink resource (or uplink channel) (e.g., a PUCCH resource, an SRS resource, a PUSCH resource). For example, one or more configuration parameters may indicate multiple uplink signal / channel transmission / repetition opportunities (e.g., a PUSCH transmission opportunity, a PUCCH transmission opportunity) for the transmission / repetition of a transport block. For example, DCI may indicate multiple uplink signal / channel transmission / repetition opportunities (e.g., a PUSCH transmission opportunity, a PUCCH transmission opportunity) for the transmission / repetition of a transport block. For example, DCI may indicate the 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 the transmission / repetition of a transport block. A wireless device may determine the first / starting / earliest uplink signal / channel transmission / repeat opportunity based on one or more fields in the DCI (e.g., TDRA, FDRA, etc.). The number of uplink signal / channel transmission opportunities may be equal to, for example, the number of repetitions.

[0234] For example, a wireless device may transmit a transport block over / on / in / over multiple uplink signals / channel transmissions / repetition opportunities (e.g., times T2a-T2d in Figures 17 and 18, and times T3a-T3b in Figure 19). A wireless device may repeat the transmission of a transport block over / on / in / over multiple uplink signals / channel transmissions / repetition opportunities. A wireless device may transmit a transport block "number of repetitions" times. For example, when the number of repetitions is 4, the wireless device may transmit the transport block 4 times. When the number of repetitions is 2, the wireless device may transmit the transport block 2 times.

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

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

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

[0238] A repeating transport block may be, for example, a repeating frequency domain (e.g., FDM, FDMSchemeA, FDMSchemeB, etc. in Figure 20). In a repeating time domain, multiple uplink signal / channel transmission opportunities may or may not overlap in time. In a repeating frequency domain, multiple uplink signal / channel transmission opportunities may not overlap in frequency. Each uplink signal / channel transmission opportunity of multiple uplink signal / channel transmission opportunities may have non-overlapping frequency domain resource allocations with respect to other uplink signal / channel transmission opportunities of the multiple uplink signal / channel transmission opportunities. For example, the first uplink signal / channel transmission opportunity of multiple uplink signal / channel transmission opportunities may not overlap in frequency with respect to the second uplink signal / channel transmission opportunity of the multiple uplink signal / channel transmission opportunities. The first and second uplink signal / channel transmission opportunities may overlap in time. The first and second uplink signal / channel transmission opportunities may be different. Multiple uplink signal / channel transmission / repeating opportunities are the first TX opportunity, second TX opportunity, etc., in frequency domain repetition (e.g., FDM) in Figure 20. In frequency domain repetition, the repetition of a transport block can be / occur in, for example, frequency units (e.g., frequency, PRB, frequency band, subband, bandwidth portion, cell). A wireless device can repeat the transmission of a transport block over / on / in frequency units, for example. Frequency units can be, for example, continuous. Frequency units can be, for example, non-continuous (e.g., they can have frequency / PRB gaps). The number of frequency units can be equal to the number of repetitions. Frequency units can be, for example, frequency bands. Frequency units can be, for example, physical resource blocks (PRBs). Frequency units can be, for example, BWPs. Frequency units can be, for example, cells. Multiple uplink signal / channel transmission opportunities can be / occur in frequency units.For example, the first uplink signal / channel transmission opportunity among multiple uplink signal / channel transmission opportunities may be / occur as a first frequency unit in frequency units. The second uplink signal / channel transmission opportunity among multiple uplink signal / channel transmission opportunities may be / occur as a second frequency unit in frequency units, etc. The first frequency unit may be different from the second frequency unit. The first frequency unit may not overlap with the second frequency unit in frequency.

[0239] The repetition of a transport block can be, for example, a code / spatial domain repetition scheme (e.g., SDM / SFN, SDM scheme, CDM scheme, SDMScheme, CDMScheme, etc. in Figure 20). 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 a 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 in multiple uplink signal / channel transmission opportunities may be the same (or the same as an uplink signal / channel transmission opportunity or a single uplink signal / channel transmission opportunity). Each uplink signal / channel transmission opportunity in multiple uplink signal / channel transmission opportunities may have overlapping frequency domain resource allocations with respect to other uplink signal / channel transmission opportunities among the multiple uplink signal / channel transmission opportunities. Each uplink signal / channel transmission opportunity in a plurality of uplink signal / channel transmission opportunities may have time-domain resource allocations that overlap with other uplink signal / channel transmission opportunities in the plurality of uplink signal / channel transmission opportunities. For example, the first uplink signal / channel transmission opportunity in a plurality of uplink signal / channel transmission opportunities may overlap in time and frequency with the second uplink signal / channel transmission opportunity in the plurality of 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 plurality of 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 Figure 20. The first TX opportunity and the second TX opportunity may be the same in the code / spatial domain repetition (e.g., they may overlap in time and frequency).In a code / spatial domain iteration, multiple uplink signal / channel transmission opportunities may occur in the same frequency unit (e.g., frequency, PRB, frequency band, bandwidth portion, cell). For example, the first frequency unit of the first uplink signal / channel transmission opportunity and the second frequency unit of the 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 iteration, minislot, slot, subframe, etc.). For example, the first time unit of the first uplink signal / channel transmission opportunity and the second time unit of the 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., a first TX opportunity, a first time slot, and a first actual / nominal repetition), a second uplink signal / channel transmission opportunity (e.g., a second TX opportunity, a second time slot, and a second actual / nominal repetition), a third uplink signal / channel transmission opportunity (e.g., a third TX opportunity, a third time slot, and a third actual / nominal repetition), and a fourth uplink signal / channel transmission opportunity (e.g., a fourth TX opportunity, a fourth time slot, and a fourth actual / nominal repetition). In Figure 19, multiple uplink signal / channel transmission opportunities include a first uplink signal / channel transmission opportunity (e.g., a first TX opportunity, a first time slot, and a first actual / nominal repetition) and a second uplink signal / channel transmission opportunity (e.g., a second TX opportunity, a second time slot, and a second actual / nominal repetition).

[0241] In one example, one or more configuration parameters may indicate a repeating scheme (e.g., FDM-Scheme, TDM-Scheme, SFN-Scheme, SDM-Scheme, CDM-Scheme). In one example, DCI may indicate a repeating scheme. DCI may include one or more fields indicating a repeating scheme (e.g., SRI field, TCI field, antenna port field, etc.). A repeating scheme may be for the repetition of transmission of transport blocks (e.g., PUSCH transmission) over uplink resources (e.g., PUCCH resource, SRS resource, PUSCH resource). A repeating scheme may be, for example, a time-domain repeating scheme (e.g., TDM in Figure 20). A repeating scheme may be, for example, a frequency-domain repeating scheme (e.g., FDM in Figure 20). A repeating scheme may be, for example, a code / space-domain repeating scheme (e.g., SDM / SFN in Figure 20). In Figures 17-19, the repeating scheme is a time-domain repeating scheme.

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

[0243] For example, a wireless device may determine / calculate / calculate multiple transmission powers. A wireless device may determine / calculate / calculate multiple transmission powers for the transmission of a transport block.

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

[0245] A wireless device may determine / calculate / calculate multiple transmission powers, for example, for the repetition of a transport block. The wireless device may repeat the transmission of a transport block with / using multiple transmission powers (for example, at times T2a-T2d in Figures 17 and 18, and at times T3a-T3b in Figure 19). The wireless device may transmit the repetition of a transport block with / using multiple transmission powers.

[0246] For example, a wireless device may transmit a transport block over / on / in / at multiple uplink signal / channel transmission / repeat opportunities (e.g., times T2a-T2d in Figures 17 and 18, and times T3a-T3b in Figure 19) with multiple transmission powers. A wireless device may transmit a transport block over / on / at each of the multiple uplink signal / channel transmission opportunities with / using each of the multiple transmission powers. A wireless device may transmit a transport block at each of the multiple uplink signal / channel transmission opportunities with / using each of the multiple transmission powers.

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

[0248] In one example, the number of repetitions may be 2. 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., a second TX opportunity). A wireless device may transmit the transport block in the first uplink signal / channel transmission opportunity with / using a first transmission power. A wireless device may apply the first transmission power to the first uplink signal / channel transmission opportunity. A wireless device may transmit the transport block in the second uplink signal / channel transmission opportunity with / using a second transmission power. A wireless device may apply the second transmission power to the second uplink signal / channel transmission opportunity.

[0249] In one example, the number of repetitions may be greater than (or more than) 2. In one example, one or more configuration parameters may indicate periodic mapping. Periodic mapping can enable / indicate the mapping of multiple transmission powers to multiple uplink signal / channel transmission opportunities, for example, periodically (e.g., periodically switching transmission powers). A wireless device may transmit a transport block with / using a first transmission power on a first uplink signal / channel transmission opportunity (e.g., a first TX opportunity) of multiple uplink signal / channel transmission opportunities. A wireless device may apply the first transmission power to a first uplink signal / channel transmission opportunity. A wireless device may transmit a transport block with / using a second transmission power on a second uplink signal / channel transmission opportunity (e.g., a second TX opportunity) of multiple uplink signal / channel transmission opportunities. A wireless device may apply the second transmission power to a second uplink signal / channel transmission opportunity. The same transmission power mapping pattern can remain in multiple uplink signal / channel transmission opportunities, for example, based on one or more configuration parameters exhibiting periodic mapping. A retained uplink signal / channel transmission opportunity may not include the first and second uplink signal / channel transmission opportunities. For example, if the number of repetitions is equal to 4, multiple uplink signal / channel transmission opportunities may include the first uplink signal / channel transmission opportunity, the second uplink signal / channel transmission opportunity, the third uplink signal / channel transmission opportunity (e.g., the third TX opportunity), and the fourth uplink signal / channel transmission opportunity (e.g., the fourth TX opportunity). A wireless device may transmit a transport block in the first and third uplink signal / channel transmission opportunities with / using the first transmission power. The wireless device may transmit a transport block in a second uplink signal / channel transmission opportunity and a fourth uplink signal / channel transmission opportunity with / using a second transmission 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., the first TX opportunity), a second uplink signal / channel transmission opportunity (e.g., the second TX opportunity), a third uplink signal / channel transmission opportunity (e.g., the third TX opportunity), a fourth uplink signal / channel transmission opportunity (e.g., the fourth TX opportunity), a fifth uplink signal / channel transmission opportunity (e.g., the fifth TX opportunity), a sixth uplink signal / channel transmission opportunity (e.g., the sixth TX opportunity), a seventh uplink signal / channel transmission opportunity (e.g., the seventh TX opportunity), and eight uplink signal / channel transmission opportunities (e.g., the eighth TX opportunity). A wireless device may transmit the transport block 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 a first transmission 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 a second transmission power. Figures 17 and 18 show an example of periodic mapping (for example, 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 more than) 2. In one example, one or more configuration parameters may indicate sequential mapping. Sequential mapping may allow for the mapping of multiple transmission powers to multiple uplink signal / channel transmission opportunities sequentially (e.g., sequentially switching transmission powers). A wireless device may transmit a transport block in a first uplink signal / channel transmission opportunity (e.g., the first TX opportunity) and in a second uplink signal / channel transmission opportunity (e.g., the second TX opportunity) among multiple uplink signal / channel transmission opportunities, with / using a first transmission power. The wireless device may apply the first transmission power to the first uplink signal / channel transmission opportunity and to the second uplink signal / channel transmission opportunity. A wireless device may transmit a transport block in a third uplink signal / channel transmission opportunity (e.g., a third TX opportunity) and in a fourth uplink signal / channel transmission opportunity (e.g., a fourth TX opportunity) among multiple uplink signal / channel transmission opportunities, with / using a second transmission power. The wireless device may apply the second transmission power to the third uplink signal / channel transmission opportunity and to the fourth uplink signal / channel transmission opportunity. The same transmission power mapping pattern may remain in uplink signal / channel transmission opportunities of multiple uplink signal / channel transmission opportunities, for example, based on one or more configuration parameters indicating sequential mapping. The remaining uplink signal / channel transmission opportunities may not include the first, second, third, and fourth uplink signal / channel transmission opportunities. For example, if the number of repetitions is equal to 4, 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).A wireless device may transmit a transport block in a first uplink signal / channel transmission opportunity and a second uplink signal / channel transmission opportunity with / using a first transmission power. A wireless device may transmit a transport block in a third uplink signal / channel transmission opportunity and a fourth uplink signal / channel transmission opportunity with / using a second transmission 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., the first TX opportunity), a second uplink signal / channel transmission opportunity (e.g., the second TX opportunity), a third uplink signal / channel transmission opportunity (e.g., the third TX opportunity), a fourth uplink signal / channel transmission opportunity (e.g., the fourth TX opportunity), a fifth uplink signal / channel transmission opportunity (e.g., the fifth TX opportunity), a sixth uplink signal / channel transmission opportunity (e.g., the sixth TX opportunity), a seventh uplink signal / channel transmission opportunity (e.g., the seventh TX opportunity), and eight uplink signal / channel transmission opportunities (e.g., the eighth TX opportunity). A wireless device may transmit the 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 a first transmission 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 a second transmission power.

[0251] For example, a wireless device may transmit a transport block over / in / on

[0252] In the embodiment, one or more configuration parameters may include enable parameters (e.g., PUSCH repeat, PUCCH repeat, enableTwoPLForPUSCH repeat, enableTwoPowerControlForPUSCH repeat, etc.). Enable parameters may be set to "enabled". One or more configuration parameters may indicate "enabled" for an enable parameter. The value of an enable parameter may indicate / can indicate "enabled". Enable parameters may be for cells. Enable parameters may allow the determination / selection of multiple transmission powers for a repeat of a transport block (e.g., PUSCH transmission). Enable parameters may allow the determination / selection of multiple power control parameters (e.g., path loss criterion RS, etc.) for a repeat of a transport block. Enable parameters may allow the determination / selection of multiple transmission powers for the transmission of a transport block (e.g., PUSCH transmission). Enable parameters may allow the determination / selection of multiple transmission powers for transmitting a transport block to / to multiple TRPs. For example, a wireless device may transmit a transport block over / in / on

[0253] For example, a wireless device may transmit a transport block over / in / on

[0254] For example, a wireless device may transmit a transport block over / in / on

[0255] DCI may include antenna port fields.

[0256] In one example, the antenna port field may indicate a DM-RS port within a Code Division Multiplexing (CDM) group relative to a transport block.

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

[0258] In one example, the antenna port field may represent DM-RS ports within 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 transmission powers. A wireless device may transmit a first portion of a 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 an uplink signal / channel transmission opportunity) with / using a first transmission power of multiple transmission powers. A wireless device may transmit a second portion of a 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 an uplink signal / channel transmission opportunity) with / using a second transmission power of multiple transmission 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 contain one or more first symbols and one or more second symbols. For example, one or more first symbols may include symbols 0, 1, and 2 of the transport block, and one or more first symbols may include symbols 3, 4, and 5 of the transport block. A transport block may contain symbols 0, 1, ..., 4, and 5.

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

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

[0262] The wireless device may transmit a first portion of a transport block with / using a first transmission power and a second portion of the transport block with / using a second transmission power, for example, based on the repetition scheme being a repetition in the code / space domain (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). 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 be mapped to) a first power control parameter set out of a plurality of power control parameter sets. The first power control parameter set may indicate (or be mapped to) a first path loss reference RS out of 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 identify the first power control parameter set. The value of the first SRI field may be mapped (or indicate) to the first power control parameter set index.

[0266] In one example, the second SRI field may indicate (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 references RS. 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 identify the second power control parameter set. The value of the second SRI field may be mapped to (or indicate) the second power control parameter set index.

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

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

[0269] For example, a wireless device may determine / calculate / calculate a first transmission power among multiple transmission powers based on a first path loss criterion RS indicated by (or mapped to) a first set of power control parameters. The wireless device may determine / calculate / calculate a first transmission power based on a first reference signal indicated by the first path loss criterion RS. The wireless device may determine / calculate / calculate a second transmission power among multiple transmission powers based on a second path loss criterion RS indicated by (or mapped to) a second set of power control parameters. The wireless device may determine / calculate / calculate a second transmission power based on a second reference signal indicated by the second path loss criterion RS.

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

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

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

[0273] In Figure 17, the wireless device may determine a first default path loss reference RS from among several 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. Multiple path loss reference RS indices may include the first path loss reference RS index. The first value may be equal to zero, for example (e.g., path loss RS0 in Figure 17).

[0274] In Figure 19, the wireless device may determine a first default path loss criterion RS from among one or more path loss criterion RSs. The wireless device may determine a first default path loss criterion RS based on a DCI that does not include a first SRI field. The first default path loss criterion RS may be mapped to a first power control parameter set among several power control parameter sets indicated / identified by a first power control parameter set (e.g., sri-PUSCH-PowerControlId) equal to a first value. Multiple power control parameter set indices 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 Figure 19). The wireless device may determine a first default path loss criterion RS from among one or more path loss criterion RSs activated / indicated / updated by one or more active commands, for example, based on the fact that one or more configuration parameters include path loss RS update parameters.

[0275] One or more configuration parameters may indicate a first reference signal (e.g., CSI-RS, SS / PBCH block) for a first default path loss criterion RS. The first default path loss criterion 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] For example, a wireless device may determine / calculate / calculate a first transmission power among multiple transmission powers based on a first default path loss criterion RS. The wireless device may determine / calculate / calculate a first transmission power based on a first reference signal indicated by the first default path loss criterion RS. The wireless device may determine / calculate / calculate a second transmission power among multiple transmission powers based on a second path loss criterion RS indicated by (or mapped to) a second power control parameter set. The wireless device may determine / calculate / calculate a second transmission power based on a second reference signal indicated by the second path loss criterion RS.

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

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

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

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

[0281] A 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 the second value. Multiple path loss reference RS indices may include a second path loss reference RS index. The second value could be, for example, equal to 1 (e.g., path loss RS1 in Figure 17). The second value could be, for example, equal to 0.

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

[0283] One or more configuration parameters may, for example, indicate a second default path loss criterion RS.

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

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

[0286] The second default path loss criterion RS may be mapped to a second power control parameter set among multiple power control parameter sets, indicated / identified by the second power control parameter set index with the highest value among multiple power control parameter set indices (e.g., sri-PUSCH-PowerControlId) (for example, path loss RS41 in Figure 19 is mapped to sri-PUSCH-PowerControl N). Multiple power control parameter set indices may include the second power control parameter set index.

[0287] One or more configuration parameters may, for example, indicate a second default path loss criterion RS.

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

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

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

[0291] A DCI may not include a first SRI field (or first TCI field) based on a first SRS resource set containing a single SRS resource. A DCI may not include a second SRI field (or second TCI field) based on a second SRS resource set containing a single SRS resource. A DCI may not include a first SRI field based on a first SRS resource set containing more than one SRS resource. A DCI may not include a second SRI field based on a second SRS resource set containing more than one SRS resource. A DCI may not include the first and second SRI fields (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 criterion RS from among multiple path loss criterions RS. The wireless device may determine the first default path loss criterion RS based on a DCI that does not include the first SRI field. The wireless device may determine a second default path loss criterion RS from among multiple path loss criterions RS. The wireless device may determine a second default path loss criterion RS based on a DCI that does not include the second SRI field.

[0293] In Figure 19, the wireless device may determine a first default path loss criterion RS from among one or more path loss criterion RSs. The wireless device may determine a first default path loss criterion RS based on a DCI that does not include a first SRI field. The wireless device may determine a first default path loss criterion RS from among one or more path loss criterion 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 criterion RS from among one or more path loss criterion RSs. The wireless device may determine a second default path loss criterion RS based on a DCI that does not include a second SRI field. The wireless device may determine a second default path loss criterion RS from among one or more path loss criterion 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] One or more configuration parameters may, for example, indicate a second default path loss criterion RS.

[0295] In Figure 18, one or more configuration parameters may not represent multiple power control parameter sets, such as SRI-PUSCH-PowerControl.

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

[0297] For example, a wireless device may determine / select a first default path loss criterion RS from among several path loss criterions RS. The wireless device may determine the first default path loss criterion RS based on one or more configuration parameters that do not represent multiple power control parameter sets.

[0298] For example, a wireless device may determine a second default path loss criterion RS from among several path loss criterions RS. The wireless device may also determine the second default path loss criterion RS based on one or more configuration parameters that do not represent multiple power control parameter sets.

[0299] Referring to Figures 17 and 18, a 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. Multiple path loss reference RS indices may include the first path loss reference RS index. The first value may be equal to zero, for example (e.g., path loss RS0). Multiple path loss reference RSs may include the first default path loss reference RS.

[0300] Referring to Figure 19, the first default path loss criterion RS may be mapped to a first power control parameter set among several power control parameter sets, indicated / identified by a first power control parameter set index (e.g., sri-PUSCH-PowerControlId) equal to a first value. Multiple power control parameter set indices 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 Figure 19). One or more path loss criterion RSs may include the first default path loss criterion RS.

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

[0302] One or more configuration parameters may indicate a first reference signal (e.g., CSI-RS, SS / PBCH block) for a first default path loss criterion RS. The first default path loss criterion 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] Referring to Figures 17 and 18, a 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. Multiple path loss reference RS indices may include a second path loss reference RS index. The second value may be equal to, for example, 1 (e.g., path loss RS1). The second value may be equal to, for example, 0. Multiple path loss reference RSs may include a second default path loss reference RS.

[0304] Referring to Figures 17 and 18, the second default path loss reference RS may be indicated / identified by the highest second path loss reference RS index (e.g., PUSCH-PathlossReferenceRS-Id) among multiple path loss reference RS indices (e.g., path loss RS M). Multiple path loss reference RS indices may include the second path loss reference RS index. Multiple path loss reference RS may include the second default path loss reference RS.

[0305] Referring to Figure 19, the second default path loss criterion RS may be mapped to a second power control parameter set among several power control parameter sets, indicated / identified by a second power control parameter set (e.g., sri-PUSCH-PowerControlId) that is equal to the second value. Multiple power control parameter set indices 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 Figure 19). The second value may also be equal to 0. One or more path loss criterion RSs may include the second default path loss criterion RS.

[0306] Referring to Figure 19, the second default path loss criterion RS may be mapped to a second power control parameter set among multiple power control parameter sets, indicated / identified by the second highest second power control parameter set index among multiple power control parameter set indices (e.g., sri-PUSCH-PowerControlId) (for example, path loss RS41 in Figure 19 is mapped to sri-PUSCH-PowerControl N). Multiple power control parameter set indices may include the second power control parameter set index. One or more path loss criterion RSs may include the second default path loss criterion RS.

[0307] One or more configuration parameters may, for example, indicate a second default path loss criterion RS.

[0308] One or more configuration parameters may indicate a second reference signal (e.g., CSI-RS, SS / PBCH block) for a second default path loss criterion RS. The second default path loss criterion 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] For example, a wireless device may determine / calculate / determine a first transmission power among multiple transmission powers based on a first default path loss criterion RS. The wireless device may determine / calculate / determine a first transmission power based on a first reference signal indicated by the first default path loss criterion RS. The wireless device may determine / calculate / determine a second transmission power among multiple transmission powers based on a second default path loss criterion RS. The wireless device may determine / calculate / determine a second transmission power based on a second reference signal indicated by the second default path loss criterion 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 transmission power. A wireless device may transmit a transport block with / using a first transmission power at one or more first uplink signal / channel transmission opportunities (e.g., times T2a and T2c in Figures 17 and 18, and time T3a in Figure 19). A 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 transmission power. A wireless device may transmit a transport block with / using a second transmission power at one or more second uplink signal / channel transmission opportunities (e.g., times T2b and T2d in Figures 17 and 18, and time T3b in Figure 19).

[0311] Wireless devices can transmit transport blocks via the cell's active uplink BWP.

[0312] For example, a first reference signal, indicated by a first default path loss criterion RS or a first path loss criterion RS, may be periodic. A second reference signal, indicated by a second default path loss criterion RS or a second path loss criterion 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 exhibit a first periodicity. One or more configuration parameters may exhibit a second periodicity. Based on the periodicity of the first reference signal, the wireless device may periodically measure, for example, L1-RSRP, L3-RSRP of the first reference signal. Based on the periodicity of the second reference signal, the wireless device may periodically measure, for example, L1-RSRP, L3-RSRP of the second reference signal.

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

[0314] In one example, one or more configuration parameters may indicate a reference cell for a cell (e.g., by the higher-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 one or more configuration parameters indicating a reference cell for a cell, reference signals (e.g., the first reference signal, the second reference signal in Figures 17-19) may be indicated by path loss reference RS (e.g., the first path loss reference RS, the second path loss reference RS, the first default path loss reference RS, the second default path loss reference RS in Figures 17-19) and transmitted over / through the reference cell. Based on one or more configuration parameters indicating a reference cell for a cell, the base station may transmit reference signals over / through the reference cell. Based on one or more configuration parameters indicating a reference cell for a cell, the base station may configure reference signals for the reference cell. Based on one or more configuration parameters indicating a reference cell for a cell, one or more configuration parameters may indicate reference signals for the reference cell. In one example, the reference cell may be for path loss estimation of the cell. In one example, a wireless device may measure a reference signal from a reference cell for estimating the path loss of a cell. In one example, the RS resource for the reference signal may be located on the reference cell. The value of the upper-layer parameter pathlossReferenceLinking may indicate the reference cell.

[0315] Referring to Figures 17 to 19, a wireless device may determine a first default path loss criterion RS based, for example, on one or more configuration parameters indicating at least two SRS resource sets, along with a set of SRS usage parameters set in a codebook. A wireless device may determine a first default path loss criterion RS based, for example, on one or more configuration parameters indicating at least two SRS resource sets, along with a set of SRS usage parameters not set in a codebook.

[0316] Referring to Figures 17 to 19, a wireless device may determine a second default path loss criterion RS based, for example, on the fact that one configuration parameter indicates at least two SRS resource sets, along with a set of SRS usage parameters set in the codebook. A wireless device may determine a second default path loss criterion RS based, for example, on the fact that one or more configuration parameters indicate at least two SRS resource sets, along with a set of SRS usage parameters not set in the codebook.

[0317] In one example, a wireless device is supplied to multiple TRPs (e.g., transmitting and / or receiving from them). The wireless device may determine a first default path loss criterion RS and a second default path loss criterion RS based on being supplied by multiple TRPs. The wireless device may determine a first default path loss criterion RS based on being supplied by multiple TRPs. The wireless device may determine a second default path loss criterion RS based on being supplied by multiple TRPs.

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

[0319] A wireless device may determine a first default path loss criterion RS based on the DCI indicating, for example, a repetition of transport blocks toward / to multiple TRPs.

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

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

[0322] For example, a wireless device may determine a second default path loss criterion RS based on one or more configuration parameters, including an enablement parameter. The enablement parameter may be set to "enabled". One or more configuration parameters may indicate "enabled" for the enablement parameter.

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

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

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

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

[0327] In one example, a wireless device may determine a first default path loss criterion RS and a second default path loss criterion RS based on UE capability information indicating / including beam-aware support, without uplink beam sweeping.

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

[0329] In one example, a wireless device may determine a second default path loss criterion RS based on UE capability information indicating / including beam-aware support, without uplink beam sweeping.

[0330] For example, a wireless device may determine a first default path loss criterion RS and a second default path loss criterion RS based, for instance, on UE capability information indicating repeated support for the transmission of a transport block.

[0331] For example, a wireless device may determine a first default path loss criterion RS based on UE capability information indicating repeated support for the transmission of a transport block, for instance.

[0332] For example, a wireless device may determine a second default path loss criterion RS based on UE capability information indicating repeated support for the transmission of a transport block, for instance.

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

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

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

[0336] For example, determining / calculating / estimating a second transmission power based on a second reference signal may include determining / calculating / estimating a downlink path loss estimate (or second path loss measurement) for the second transmission power based on the second reference signal (e.g., L1-RSRP, L3-RSRP, or a higher filtered RSRP measurement). A wireless device may use a second downlink path loss estimate when determining / calculating / estimating a second transmission power for the transmission of a transport block (or a second part of a transport block, or one or more second data layers / streams of a transport block). The second transmission power may include a second downlink path loss estimate. For example, a wireless device may determine / calculate / estimate a second filtered RSRP (e.g., L1-RSRP, L3-RSRP) of the second reference signal for the downlink path loss estimate. A wireless device may determine / calculate / estimate a second filtered RSRP for the transmission of a transport block.

[0337] Figure 21 is an exemplary flowchart of power control in an uplink channel repeat, according to one 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. One or more messages may include one or more configuration parameters of a cell (e.g., RRC configuration parameters, RRC reconfiguration parameters).

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

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

[0341] One or more configuration parameters may include multiple power control parameter sets. One or more configuration parameters may indicate multiple power control parameter set indices for multiple power control parameter sets.

[0342] One or more configuration parameters may include multiple path loss criterion RSs. One or more configuration parameters may indicate multiple path loss criterion RS indices for multiple path loss criterion RSs.

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

[0344] In one example, a wireless device may receive one or more active commands that indicate / update / activate one or more of several path loss criteria RSs. Multiple power control parameter sets may be mapped to one or more path loss criteria RSs.

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

[0346] A wireless device may, for example, receive DCI signals.

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

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

[0349] For example, DCI may include a first SRI field. DCI may include a first SRI field based on the number of SRS resources in a first SRS resource set being 1 or greater. 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. A 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] For example, multiple path loss criteria RS may include a first path loss criterion RS.

[0351] In one example, one or more path loss criteria RS may include a first path loss criterion RS.

[0352] A wireless device may determine / calculate / calculate a first transmission power based on a first reference signal indicated by a first path loss criterion RS.

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

[0354] For example, DCI may include a second SRI field. DCI may include a second SRI field based on the number of SRS resources in a 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 multiple power control parameter sets. A 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, multiple path loss criteria RS may include a second path loss criterion RS. In another example, one or more path loss criteria RS may include a second path loss criterion RS.

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

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

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

[0359] For example, multiple path loss criterion RSs may include a first default path loss criterion RS. The first default path loss criterion RS may be identified / indicated by a first path loss criterion RS index equal to a first value (e.g., zero). Multiple path loss criterion RS indices may include a first path loss criterion RS index.

[0360] For example, one or more path loss criterion RS may include a first default path loss criterion RS. The first default path loss criterion RS may be mapped to (or indicated by) a first power control parameter set among 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). Multiple power control parameter set indices may include the first power control parameter set index.

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

[0362] A wireless device may determine a first spatial domain transmission 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] For example, DCI may not include a second SRI field. DCI may not include a second SRI field based on the number of SRS resources in the second SRS resource set being 1. A wireless device may determine a second default path loss criterion RS. The second SRS resource set may include a single SRS resource.

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

[0365] For example, one or more path loss criterion RS may include a second default path loss criterion RS. The second default path loss criterion RS may be mapped to (or indicated by) a second power control parameter set among 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 the second power control parameter set index that is the highest among multiple power control parameter set indices of multiple power control parameter sets. Multiple power control parameter set indices may include a second power control parameter set index.

[0366] One or more configuration parameters may, for example, indicate a second default path loss criterion RS.

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

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

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

[0370] 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, or one or more first symbols of a transport block) with / using a first transmission power. A wireless device may transmit a transport block in one or more first uplink signal / channel transmission opportunities of multiple uplink signal / channel transmission opportunities with / using a first transmission power.

[0371] A 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, or one or more second symbols of a transport block) with / using a second transmission power. A wireless device may transmit a transport block in one or more second uplink signal / channel transmission opportunities of multiple uplink signal / channel transmission opportunities with / using a second transmission power.

[0372] A wireless device may transmit a transport block in conjunction with / using a first spatial domain transmission filter and a second spatial domain transmission filter.

[0373] 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, or one or more first symbols of a transport block) in conjunction with / using a first spatial domain transmission filter. A wireless device may transmit a transport block in one or more first uplink signal / channel transmission opportunities of multiple uplink signal / channel transmission opportunities in conjunction with / using a first spatial domain transmission filter.

[0374] A 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, or one or more second symbols of a transport block) in conjunction with / using a second spatial domain transmission filter. A wireless device may transmit a transport block in one or more second uplink signal / channel transmission opportunities of multiple uplink signal / channel transmission opportunities in conjunction with / using a second spatial domain transmission filter.

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

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

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

[0378] Figure 22 is an exemplary flowchart of power control in an uplink channel repeat, according to one embodiment of the present disclosure.

[0379] The considerations for the first two steps in Figure 21 (e.g., receiving one or more configuration parameters and DCI) are also applicable to the first two steps in Figure 22.

[0380] For example, DCI may include a first SRI field. DCI may include a first SRI field based on the number of SRS resources in a first SRS resource set being 1 or greater. 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. A 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, multiple path loss criteria RS may include a first path loss criterion RS. In another example, one or more path loss criteria RS may include a first path loss criterion RS.

[0382] A wireless device may determine / calculate / calculate a first transmission power based on a first reference signal indicated by a first path loss criterion RS.

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

[0384] For example, DCI may not include a second SRI field. DCI may not include a second SRI field based on the fact that the number of SRS resources in the second SRS resource set is 1. The second SRS resource set may contain a single SRS resource.

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

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

[0387] For example, DCI may include a second SRI field. DCI may include a second SRI field based on the number of SRS resources in a 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 multiple power control parameter sets. A 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, multiple path loss criteria RS may include a second path loss criterion RS. In another example, one or more path loss criteria RS may include a second path loss criterion RS.

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

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

[0391] For example, DCI may not include the first SRI field. DCI may not include the first SRI field based on the fact that the number of SRS resources in the first SRS resource set is 1. The first SRS resource set may contain a single SRS resource.

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

[0393] A wireless device may determine a first spatial domain transmission 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] A wireless device may transmit a transport block with / using a first transmission power and a second transmission power.

[0395] 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, or one or more first symbols of a transport block) with / using a first transmission power. A wireless device may transmit a transport block in one or more first uplink signal / channel transmission opportunities of multiple uplink signal / channel transmission opportunities with / using a first transmission power.

[0396] A 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, or one or more second symbols of a transport block) with / using a second transmission power. A wireless device may transmit a transport block in one or more second uplink signal / channel transmission opportunities of multiple uplink signal / channel transmission opportunities with / using a second transmission power.

[0397] A wireless device may transmit a transport block in conjunction with / using a first spatial domain transmission filter and a second spatial domain transmission filter.

[0398] 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, or one or more first symbols of a transport block) in conjunction with / using a first spatial domain transmission filter. A wireless device may transmit a transport block in one or more first uplink signal / channel transmission opportunities of multiple uplink signal / channel transmission opportunities in conjunction with / using a first spatial domain transmission filter.

[0399] A 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, or one or more second symbols of a transport block) in conjunction with / using a second spatial domain transmission filter. A wireless device may transmit a transport block in one or more second uplink signal / channel transmission opportunities of multiple uplink signal / channel transmission opportunities in conjunction with / using a second spatial domain transmission filter.

[0400] Figure 23 is an exemplary flowchart of power control in an uplink channel repeat, according to one embodiment of the present disclosure.

[0401] The one or more configuration parameters discussed in Figure 21 may not represent one or more sets of power control parameters.

[0402] In one example, the DCI considered in Figure 21 may or may not include a first SRI field. A wireless device may determine a first default path loss criterion RS. The wireless device may determine the first default path loss criterion RS, for example, based on the fact that one or more configuration parameters do not indicate one or more power control parameter sets.

[0403] For example, multiple path loss criterion RSs may include a first default path loss criterion RS. The first default path loss criterion RS may be identified / indicated by a first path loss criterion RS index equal to a first value (e.g., zero). Multiple path loss criterion RS indices may include a first path loss criterion RS index.

[0404] A wireless device may determine / calculate / calculate a first transmission power based on a first reference signal indicated by a first default path loss criterion RS.

[0405] In one example, the DCI considered in Figure 21 may or may not include a second SRI field. A wireless device may determine a second default path loss criterion RS. For example, a wireless device may determine a second default path loss criterion RS based on the fact that one or more configuration parameters do not indicate one or more power control parameter sets.

[0406] For example, multiple path loss criterion RSs may include a second default path loss criterion RS. The second default path loss criterion RS may be identified / indicated, for example, by a second path loss criterion RS index equal to a second value (e.g., 1). The second default path loss criterion RS may be identified / indicated, for example, by the highest second path loss criterion RS index among the multiple path loss criterion RS indices of the multiple path loss criterion RSs. Multiple path loss criterion RS indices may include a second path loss criterion RS index.

[0407] One or more configuration parameters may, for example, indicate a second default path loss criterion RS.

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

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

[0410] 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, or one or more first symbols of a transport block) with / using a first transmission power. A wireless device may transmit a transport block in one or more first uplink signal / channel transmission opportunities of multiple uplink signal / channel transmission opportunities with / using a first transmission power.

[0411] A 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, or one or more second symbols of a transport block) with / using a second transmission power. A wireless device may transmit a transport block in one or more second uplink signal / channel transmission opportunities of multiple uplink signal / channel transmission opportunities with / using a second transmission power.

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

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

[0414] Figure 24 is an exemplary flowchart of power control in an uplink channel repeat, according to one embodiment of the present disclosure.

[0415] For example, a base station may decide to transmit one or more messages to a wireless device that include one or more configuration parameters for a cell (e.g., RRC configuration parameters, RRC reconfiguration parameters).

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

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

[0418] A base station may constitute multiple SRS resources in a second SRS resource set. A base station may constitute multiple SRS resources in a second SRS resource set based, for example, on the fact that one or more configuration parameters indicate at least two SRS resource sets. A base station may constitute multiple SRS resources in a second SRS resource set based, for example, on the fact that one or more configuration parameters indicate at least two SRS resource sets with SRS usage parameters set in a codebook or non-codebook. A base station may not constitute a single SRS resource in a second SRS resource set based, for example, on the fact that one or more configuration parameters indicate at least two SRS resource sets. A base station may not constitute a single SRS resource in a second SRS resource set based, for example, on the fact that one or more configuration parameters indicate at least two SRS resource sets with SRS usage parameters set in a codebook or 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 based, for example, on one or more configuration parameters indicating at least two SRS resource sets. A base station may configure multiple path loss reference RSs based, for example, on one or more configuration parameters indicating at least two SRS resource sets with SRS usage parameters set in a codebook or non-codebook. A base station may not configure a single path loss reference RS based, for example, on one or more configuration parameters indicating at least two SRS resource sets. A base station may not configure a single path loss reference RS based, for example, on one or more configuration parameters indicating at least two SRS resource sets with SRS usage parameters set in a codebook or 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 estimating path loss on uplink channels (e.g., PUSCH, PUCCH, SRS). A base station may configure multiple power control parameter sets based, for example, on one or more configuration parameters indicating at least two SRS resource sets. A base station may configure multiple power control parameter sets based, for example, on one or more configuration parameters indicating at least two SRS resource sets with SRS usage parameters set in a codebook or non-codebook. A base station may not configure a single power control parameter set based, for example, on one or more configuration parameters indicating at least two SRS resource sets. A base station may not configure a single power control parameter set based, for example, on one or more configuration parameters indicating at least two SRS resource sets with SRS usage parameters set in a codebook or non-codebook.

[0421] A base station can transmit one or more messages containing one or more configuration parameters.

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

[0423] One or more configuration parameters may indicate multiple path loss criteria RS.

[0424] One or more configuration parameters may represent multiple sets of power control parameters.

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

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

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

Claims

1. It is a method, The wireless device receives downlink control information (DCI) that schedules the repetition of uplinks for physical uplink shared channel (PUCH) transmissions, 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 transmission power based on a first path loss reference signal (RS) associated with a first sounding reference signal (SRS) resource set with an index equal to zero, and A method comprising transmitting a second iteration of the PUSCH transmission, with a second transmission power based on a second path loss criterion RS associated with a second SRS resource set having an index equal to 1.

2. The first path loss criterion RS is the first default path loss criterion RS. The method according to claim 1, wherein the second path loss criterion RS is the second default path loss criterion RS.

3. Based on the fact that the SRI field does not exist in the DCI, As the first default path loss criterion RS, the first path loss criterion RS has an index equal to zero, The method of claim 2, further comprising selecting the second path loss criterion RS having an index equal to 1 as the second default path loss criterion RS.

4. The method according to claim 1, wherein the transmission is further based on the absence of both the first SRI field and the second SRI field in the DCI, and the DCI does not contain any SRI fields.

5. The process further includes receiving one or more messages containing one or more configuration parameters, wherein the one or more configuration parameters are The first SRS resource set and, The method according to claim 4, wherein the second SRS resource set is shown.

6. Based on the fact that the number of SRS resources in the first SRS resource set is equal to 1, the first SRI field does not exist in the DCI, The method according to claim 5, wherein the second SRI field does not exist in the DCI based on the fact that the number of SRS resources in the second SRS resource set is equal to 1.

7. The one or more configuration parameters indicate multiple indices for a plurality of path loss criteria RSs, including the first path loss criterion RS and the second path loss criterion RS. The method according to claim 5, wherein each of the plurality of path loss criterion RSs is represented by the respective index of the plurality of indices, which includes the index of the first path loss criterion RS and the index of the second path loss criterion RS.

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

9. The method according to claim 5, wherein the one or more configuration parameters indicate SRS usage parameters that are set in a codebook or in a non-codebook resource set for both the first SRS resource set and the second SRS resource set.

10. The method according to claim 1, wherein the DCI includes a time-domain resource alignment (TDRA) field indicating the number of repetitions of the PUSCH transmission.

11. A wireless device, One or more processors, When executed by one or more processors, the wireless device The system receives Downlink Control Information (DCI) to schedule the repetition of uplink transmissions in 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 transmission power based on a first path loss reference signal (RS) associated with a first sounding reference signal (SRS) resource set with an index equal to zero, and A second repetition of the PUSCH transmission is transmitted, accompanied by a second transmission power based on a second path loss criterion RS, associated with a second SRS resource set with an index equal to 1. A wireless device equipped with memory for storing instructions.

12. The first path loss criterion RS is the first default path loss criterion RS. The wireless device according to claim 11, wherein the second path loss criterion RS is the second default path loss criterion RS.

13. The instruction further instructs the wireless device to: Based on the fact that the SRI field does not exist in the DCI, As the first default path loss criterion RS, the first path loss criterion RS has an index equal to zero, The wireless device according to claim 12, wherein the second default path loss criterion RS is selected as the second path loss criterion RS having an index equal to 1.

14. The wireless device according to claim 11, wherein the transmission is further based on the absence of both the first SRI field and the second SRI field in the DCI, and the DCI does not contain any SRI field.

15. The instruction further causes the wireless device to receive one or more messages containing one or more configuration parameters, The first SRS resource set and, The wireless device according to claim 14, wherein the second SRS resource set is shown.

16. Based on the fact that the number of SRS resources in the first SRS resource set is equal to 1, the first SRI field does not exist in the DCI, The wireless device according to claim 15, wherein the second SRI field does not exist in the DCI based on the number of SRS resources in the second SRS resource set being equal to 1.

17. The one or more configuration parameters indicate multiple indices for a plurality of path loss criteria RSs, including the first path loss criterion RS and the second path loss criterion RS. The wireless device according to claim 15, wherein each of the plurality of path loss criterion RSs is represented by the index of the plurality of indices, which includes the index of the first path loss criterion RS and the index of the second path loss criterion RS.

18. The instruction further instructs the wireless device to: The first transmission power based on a first reference signal indicated by the first path loss reference RS with an index of zero, The wireless device according to claim 17, which determines the second transmission power based on a second reference signal indicated by the second path loss reference RS having an index of 1.

19. The wireless device according to claim 15, wherein the one or more configuration parameters indicate SRS usage parameters that are set in a codebook or set in a non-codebook resource set for both the first SRS resource set and the second SRS resource set.

20. It is a system, A base station comprising one or more first processors and memory for storing instructions, wherein when an instruction is executed by the one or more first processors, the base station provides: A base station transmits downlink control information (DCI) that schedules the repetition of uplink transmissions for physical uplink shared channel (PUSCH) transmissions, A wireless device including one or more second processors and memory for storing instructions, wherein when an instruction is executed by the one or more second processors, the wireless device, The base station receives the DCI which schedules the repetition of the uplink for the PUSCH transmission. In response to the absence of a Sounding Reference Signal Resource Indicator (SRI) field in the DCI, A first repetition of the PUSCH transmission, with an index equal to zero, and a first transmission power based on a first path loss reference signal (RS) mapped to a first power control parameter set among the power control parameter sets associated with a first sounding reference signal (SRS) resource set, and A system comprising: a wireless device that transmits a second iteration 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 associated with a second SRS resource set, with an index equal to 1.

Images