Resource configuration for duplicate transmissions

Abstract

The present invention provides a method, apparatus, and storage medium for configuring resources for duplicate transmission. [Solution] The method comprises a wireless device receiving one or more messages. One or more messages indicate that there is no reporting of a first CORESET pool index and a second CORESET pool index, two SRS resource sets, and two PHRs for the two SRS resource sets. The method also comprises transmitting a PHR for a first PUSCH associated with the first CORESET pool index. The transmission of the PHR is based on a second PUSCH transmission that is associated with the second CORESET pool index and temporally overlaps with the first PUSCH transmission, and that there is no reporting of two PHRs for the two SRS resource sets.

Description

Technical Field

[0001] (Cross - Reference to Related Applications) This application claims the benefit of U.S. Provisional Patent Application No. 63 / 307,299, filed on February 7, 2022; U.S. Provisional Patent Application No. 63 / 307,301, filed on February 7, 2022; U.S. Provisional Patent Application No. 63 / 308,699, filed on February 10, 2022; and U.S. Provisional Patent Application No. 63 / 307,703, filed on February 8, 2022. The above - referenced applications are hereby incorporated by reference in their entirety.

Background Art

[0002] Wireless communication includes repeating transmissions to increase the likelihood of normal message reception. The repetitions are transmitted using time - division multiplexing.

Summary of the Invention

[0003] The following summary shows a simplified summary of specific functions. The summary is not an extensive overview and is not intended to identify key or important elements.

[0004] A wireless device may communicate with a base station by using duplicate transmissions. For example, duplicate transmissions may include using time-division multiplexing (TDM), frequency-division multiplexing (FDM), and / or spatial-division multiplexing (SDM) for temporally overlapping transmissions (e.g., using FDM and / or SDM), frequency (e.g., using TDM and / or SDM), and / or spatial domains (e.g., using TDM and / or FDM). A wireless device may use multiplexing to transmit repetitions of a message / transmission, which may increase the likelihood of successful reception. In at least some repetitions, a wireless device may multiplex information within a repeated message / transmission. Multiplexed information may include, for example, a channel status information (CSI) report multiplexed in a repetition of a physical uplink shared channel (PUSCH) transmission, a physical uplink control channel (PUCCH) transmission multiplexed in a repetition of a PUSCH transmission (e.g., including uplink control information (UCI)), and / or any other information included in the transmission. The rules are applied by radio devices and base stations to indicate / determine which of several repetitions contains the multiplexed information, so that the multiplexed information can be successfully communicated. For example, the rules may include the lowest (or highest) frequency or frequency range, the lowest (or highest) start (or end) resource block, the lowest (or highest) transmit configuration indicator (TCI) state, the lowest (or highest) TCI state index, the lowest (or highest) panel or panel index, and / or any other parameters / indicators that may distinguish a transmit (containing the multiplexed information) from other transmits.Additionally or alternatively, rules may be applied by radio devices and base stations to display / determine values / parameters associated with transmissions, such as the lowest / start or highest / end resource block using the lowest or highest frequency, the lowest or highest TCI state or TCI state index, the lowest or highest panel or panel index, etc., for example, power headroom report values ​​that may indicate the path loss reference signal used to determine the power headroom report (for example, then indicating which of multiple transmit / receive points the power headroom report corresponds to). Additionally or alternatively, the rules may include power prioritization rules that can be applied and displayed / determined by the radio device and base station (e.g., using the lowest or highest frequency, lowest / start or highest / end resource block, lowest or highest TCI state / TCI state index, lowest or highest panel / panel index, etc.), power prioritization for temporally overlapping transmissions, the power prioritization rule may indicate which of multiple transmissions of the same type / channel (e.g., PUSCH, PUCCH, etc.) the multiple transmissions otherwise include at least one of the power thresholds (e.g., the maximum transmit power of the radio device), as described herein. Establishing one or more rules for overlapping transmissions as described herein may result in benefits such as increased synchronization between the radio device and base station, reduced retransmission, reduced latency, and / or reduced power consumption.

[0005] These and other features and benefits are described in more detail below.

[0006] Some features are shown in the attached drawings as examples, not as limitations. In the drawings, similar numbers refer to similar elements. [Brief explanation of the drawing]

[0007] [Figure 1A] Figure 1A shows an example of a communication network. [Figure 1B] Figure 1B shows an example of a communication network. [Figure 2A] Figure 2A shows an exemplary user plane. [Figure 2B] Figure 2B shows an example of a control plane configuration. [Figure 3] Figure 3 shows an example of the protocol layer. [Figure 4A] Figure 4A shows an example of a downlink data flow in a user plane configuration. [Figure 4B] Figure 4B shows an exemplary format of the Media Access Control (MAC) subheader of a MAC Protocol Data Unit (PDU). [Figure 5A] Figure 5A shows an example of downlink channel mapping. [Figure 5B] Figure 5B shows an example of uplink channel mapping. [Figure 6] Figure 6 shows an example of the Radio Resource Control (RRC) state and RRC state transition. [Figure 7] Figure 7 shows an example of a frame configuration. [Figure 8] Figure 8 shows an exemplary resource configuration for one or more carriers. [Figure 9] Figure 9 shows an example configuration of the bandwidth portion (BWP). [Figure 10A] Figure 10A shows an exemplary carrier aggregation configuration based on component carriers. [Figure 10B] Figure 10B shows an example of cell grouping. [Figure 11A] Figure 11A shows an exemplary mapping of one or more synchronous signal / physical broadcast channel (SS / PBCH) blocks. [Figure 11B] Figure 11B shows an example of mapping one or more channel status information reference signals (CSI-RS). [Figure 12A] Figure 12A shows an example of the downlink beam management procedure. [Figure 12B]FIG. 12B shows an example of an uplink beam management procedure. [Figure 13A] FIG. 13A shows an example of a 4-step random access procedure. [Figure 13B] FIG. 13B shows an example of a 2-step random access procedure. [Figure 13C] FIG. 13C shows an example of a 2-step random access procedure. [Figure 14A] FIG. 14A shows an example of a control resource set (CORESET) configuration. [Figure 14B] FIG. 14B shows an example of the mapping of control channel elements to resource element groups (CCE-to-REG). [Figure 15A] FIG. 15A shows an example of communication between a wireless device and a base station. [Figure 15B] FIG. 15B shows exemplary elements of a computing device that can be used to implement any of the various devices described herein. [Figure 16A] FIG. 16A shows an example of uplink and downlink signal transmission. [Figure 16B] FIG. 16B shows an example of uplink and downlink signal transmission. [Figure 16C] FIG. 16C shows an example of uplink and downlink signal transmission. [Figure 16D] FIG. 16D shows an example of uplink and downlink signal transmission. [Figure 17] FIG. 17 shows an exemplary TCI state update. [Figure 18] FIG. 18 shows an example of an uplink repetition scheme. [Figure 19] FIG. 19 shows an example of report multiplexing. [Figure 20] FIG. 20 shows an example of report multiplexing. [Figure 21A] FIG. 21A shows an example of report multiplexing. [Figure 21B] FIG. 21B shows an example of report multiplexing. [Figure 22] Figure 22 shows an example of uplink control information multiplexing. [Figure 23] Figure 23 shows an example of uplink control information multiplexing. [Figure 24A] Figure 24A shows an example of uplink control information multiplexing. [Figure 24B] Figure 24B shows an example of uplink control information multiplexing. [Figure 25] Figure 25 shows an example of unified beam replacement. [Figure 26] Figure 26 shows an example of a Power Headroom Report (PHR). [Figure 27A] Figure 27A shows an example of a Personal Health Record (PHR). [Figure 27B] Figure 27B shows an example of a Personal Health Record (PHR). [Figure 28A] Figure 28A shows an example of a Personal Health Record (PHR). [Figure 28B] Figure 28B shows an example of a Personal Health Record (PHR). [Figure 29A] Figure 29A shows an example of a Personal Health Record (PHR). [Figure 29B] Figure 29B shows an example of a Personal Health Record (PHR). [Figure 30] Figure 30 shows an example of power prioritization. [Figure 31] Figure 31 shows an example of power prioritization. [Figure 32] Figure 32 shows an example of power prioritization. [Figure 33] Figure 33 shows an example of power prioritization. [Modes for carrying out the invention]

[0008] The accompanying drawings and description provide examples. The examples shown in the drawings and / or description are non-exclusive, and it should be understood that the illustrated and described features may be practiced in other examples. Examples are provided for the operation of wireless communication systems that may be used in the field of multi-carrier communication systems. More specifically, the techniques disclosed herein may relate to wireless communication exposure detection and / or reporting.

[0009] Figure 1A shows an embodiment of the communication network 100. The communication network 100 may include a mobile communication network. The communication network 100 may include, for example, a public land mobile network (PLMN) operated / managed / executed by a network operator. The communication network 100 may include one or more of the core network (CN) 102, a radio access network (RAN) 104, and / or wireless devices 106. The communication network 100 may include one or more data networks (DNs) 108, and / or devices within the communication network 100 may communicate with them (e.g., via the CN 102). Wireless devices 106 may communicate with one or more DNs 108, such as public DNs (e.g., the Internet), private DNs, and / or intra-operator DNs. Wireless devices 106 may communicate with one or more DNs 108 via the RAN 104 and / or CN 102. CN 102 may provide / configure a wireless device 106 having one or more interfaces to one or more DN 108. As part of its interface function, CN 102 may set up an end-to-end connection between the wireless device 106 and one or more DN 108, authenticate the wireless device 106, and provide / configure charging functionality.

[0010] The wireless device 106 may communicate with RAN 104 via wireless communication over an air interface. RAN 104 may communicate with CN 102 via various communications (e.g., wired communications and / or wireless communications). The wireless device 106 may establish a connection with CN 102 via RAN 104. RAN 104 may, for example, provide / configure scheduling, radio resource management, and / or retransmission protocols as part of wireless communication. The communication direction from RAN 104 to the wireless device 106 via the air interface may be referred to as the downlink and / or downlink communication direction. The communication direction from the wireless device 106 to RAN 104 via the air interface may be referred to as the uplink and / or uplink communication direction. Downlink transmissions may be separated and / or distinguished from uplink transmissions based on, for example, frequency division duplication (FDD), time division duplication (TDD), any other duplication scheme, and / or at least one of a combination thereof.

[0011] When used as a whole, the term “wireless device” can include one or more mobile devices, fixed (e.g., non-portable) devices on which wireless communication is configured or enabled, computing devices, nodes, wirelessly radioactive devices, or any other devices capable of transmitting and / or receiving signals. In non-limiting embodiments, wireless devices can include, for example, telephones, mobile phones, Wi-Fi phones, smartphones, tablets, computers, laptops, sensors, meters, wearable devices, Internet of Things (IoT) devices, hotspots, cellular repeaters, roadside units (RSUs), relay nodes, automobiles, wireless user equipment (e.g., user equipment (UE), user terminal (UT), etc.), access terminals (AT), mobile stations, handsets, wireless transceiver units (WTRUs), wireless communication equipment, and / or any combination thereof.

[0012] RAN 104 may include one or more base stations (not shown). As used throughout, the term “base station” may include one or more base stations, nodes, node B (NB), evolutionary node B (eNB), gNB, ng-eNB, transit nodes (e.g., integrated access and backhaul (IAB) nodes), donor nodes (e.g., donor eNB, donor gNB), access points (e.g., Wi-Fi access points), transmit / receive points (TRPs), computing equipment, wireless communication-capable devices, or other devices capable of transmitting and / or receiving signals. A base station may include one or more of the elements listed above. For example, a base station may include one or more TRPs. In other non-limiting embodiments, a base station may include, for example, one or more of the following: Node B (e.g., associated with Universal Mobile Communications System (UMTS) and / or third-generation (3G) standards), Evolutionary Node B (eNB) (e.g., associated with Evolutionary Universal Terrestrial Radio Access (E-UTRA) and / or fourth-generation (4G) standards), Remote Radio Head (RRH), Baseband Processing Unit coupled to one or more Remote Radio Heads (RRH), Repeater Nodes or Transit Nodes used to extend the coverage area of ​​a donor node, Next-Generation Evolutionary Node B (ng-eNB), Generation Node B (gNB) (e.g., associated with NR and / or fifth-generation (5G) standards), Access Point (AP) (e.g., associated with Wi-Fi or other suitable wireless communication standards), other generations of base stations, and / or any combination thereof. A base station may also include one or more devices such as at least one base station central unit (e.g., a gNB central unit (gNB-CU)) and at least one base station distributed unit (e.g., a gNB distributed unit (gNB-DU)).

[0013] A base station (e.g., within RAN 104) may include one or more sets of antennas for communicating wirelessly (e.g., via an air interface) with a radio device 106. One or more base stations may include sets of antennas (e.g., three sets or any other set of antennas) for controlling multiple cells or sectors (e.g., three cells, three sectors, any other number of cells, or any other number of sectors), respectively. The size of a cell may be determined by the range over which a receiver (e.g., a base station receiver) can successfully receive transmissions from a transmitter (e.g., a radio device transmitter) operating within the cell. One or more cells of a base station (e.g., alone or in combination with other cells) may provide / configure radio coverage to the radio device 106 over a wide geographical area to support radio device mobility. A base station including three sectors (e.g., or n sectors, where n refers to any number n) may be referred to as a 3-sector site (e.g., or an n-sector site) or a 3-sector base station (e.g., an n-sector base station).

[0014] One or more base stations (e.g., in RAN 104) may be implemented as sector sites having more or fewer than three sectors. One or more base stations in RAN 104 may be implemented as access points, as baseband processing units coupled to multiple RRHs, and / or as repeaters or relay nodes used to extend the coverage area of ​​a node (e.g., a donor node). Baseband processing units coupled to RRHs may be part of a centralized or cloud RAN architecture, for example, the baseband processing units may be centralized within a pool of baseband processing units, or they may be virtualized. Repeater nodes may amplify and transmit (e.g., transmission, retransmission, rebroadcast, etc.) radio signals received from donor nodes. Relay nodes may perform substantially the same / similar functions as repeater nodes. Relay nodes may decode radio signals received from donor nodes to remove noise before amplifying and transmitting the radio signals.

[0015] RAN 104 can be deployed as a homogeneous network of base stations (e.g., macrocell base stations) having similar antenna patterns and / or similar high-level transmit power. RAN 104 can also be deployed as a heterogeneous network of base stations (e.g., different base stations with different antenna patterns). In a heterogeneous network, small cell base stations can be used to provide / configure small coverage areas, e.g., coverage areas that overlap with relatively large coverage areas provided / configured by other base stations (e.g., macrocell base stations). Small coverage areas can be provided / configured in areas with high data traffic (or so-called hotspots) or areas with weak macrocell coverage. Embodiments of small cell base stations may include, in order of decreasing coverage area, microcell base stations, picocell base stations, and femtocell base stations or home base stations.

[0016] The embodiments described herein may be used in various types of communications. For example, the communications may be provided by the Third Generation Partnership Project (3GPP®) (e.g., one or more network elements similar to those of communications network 100), by the Institute of Electrical and Electronics Engineers (IEEE), by the International Telecommunication Union (ITU), or by the International Organization for Standardization (ISO). 3GPP® has produced specifications for multiple generations of mobile networks, including 3G networks known as UMTS, 4G networks known as Long-Term Evolution (LTE) and LTE Advanced (LTE-A), and 5G networks known as 5G systems (5GS) and NR systems. 3GPP® may produce specifications for additional generations of communications networks (e.g., 6G and / or any other generations of communications networks). The examples may be described with reference to one or more elements (e.g., RANs) of a 3GPP® 5G network called Next Generation RAN (NG-RAN), or to any other communication networks such as 3GPP® networks and / or non-3GPP® networks. The examples described herein may be applied to other communication networks such as 3G and / or 4G networks, and communication networks that have not yet been finalized / documented (e.g., 3GPP® 6G networks), satellite communication networks, and / or any other communication networks. NG-RAN may be provided to implement and update 5G radio access technology called NR, and to implement other radio access technologies such as 4G radio access technology and / or other 3GPP® and / or non-3GPP® radio access technologies.

[0017] Figure 1B shows an embodiment of the communication network 150. The communication network may include a mobile communication network. The communication network 150 may include, for example, a PLMN operated / managed / executed by a network operator. The communication network 150 may include one or more of the following: CN 152 (e.g., 5G core network (5G-CN)), RAN 154 (e.g., NG-RAN), and / or radio devices 156A and 156B (collectively, radio device 156). The communication network 150 may include one or more data networks (DNs) 170, and / or devices within the communication network 150 may communicate with them (e.g., via CN 152). These components can be implemented and operated in substantially the same or similar manner as the corresponding components described with respect to Figure 1A.

[0018] CN 152 (e.g., 5G-CN) may provide / configure a radio device 156 with one or more interfaces to one or more DNs 170, such as a public DN (e.g., the Internet), a private DN, and / or an intra-operator DN. As part of its interface functionality, CN 152 (e.g., 5G-CN) may set up an end-to-end connection between the radio device 156 and one or more DNs, authenticate the radio device 156, and / or provide / configure charging functionality. CN 152 (e.g., 5G-CN) may be a service-based architecture that differs from other CNs (e.g., 3GPP® 4G CN). The node architecture of CN 152 (e.g., 5G-CN) may be defined as a network function that provides services via interfaces to other network functions. The network functionality of CN 152 (e.g., 5G CN) can be implemented in several ways, for example, as a network element on dedicated or shared hardware, as a software instance running on dedicated or shared hardware, and / or as a virtualized function instantiated on a platform (e.g., a cloud-based platform).

[0019] CN 152 (e.g., 5G-CN) may include an Access and Mobility Management Function (AMF) device 158A and / or a User Plane Function (UPF) device 158B, which may be separate components or a single component AMF / UPF device 158. The UPF device 158B may function as a gateway between RAN 154 (e.g., NG-RAN) and one or more DN170s. The UPF device 158B may perform functions such as packet routing and forwarding, packet inspection and enforcement of user plane policy rules, traffic utilization reporting, uplink classification to support routing of traffic flows to one or more DN170s, 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 / or downlink data notification triggers. UPF device 158B 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. Radio device 156 may be configured to receive services via PDU sessions, which may be logical connections between the radio device and the DN.

[0020] The AMF device 158A may perform functions such as termination of non-access layer (NAS) signaling, NAS signaling security, access layer (AS) security management, inter-CN node signaling for mobility between access networks (such as 3GPP® access networks and / or non-3GPP® networks), reachability of idle-mode wireless devices (e.g., idle-mode UE reachability for control and execution of paging retransmissions), registration area management, intra-system and inter-system mobility support, access authentication, roaming rights verification, access permissions including mobility management controls (e.g., subscriptions and policies), network slicing support, and / or selection of session management functions (SMF). NAS may refer to functions operating between CN and wireless devices, and AS may refer to functions operating between wireless devices and RAN.

[0021] CN 152 (e.g., 5G-CN) may include one or more additional network functions not shown in Figure 1B. CN 152 (e.g., 5G-CN) may include one or more devices implementing at least one of the following functions: Session Management Function (SMF), NR Repository Function (NRF), Policy Control Function (PCF), Network Exposure Function (NEF), Unified Data Management (UDM), Application Function (AF), Authentication Server Function (AUSF), and / or any other functions.

[0022] RAN 154 (e.g., NG-RAN) may communicate with radio device 156 via radio communication (e.g., via an air interface). Radio device 156 may communicate with CN 152 via RAN 154. RAN 154 (e.g., NG-RAN) may communicate with one or more base stations of the first type (e.g., gNB 160A and gNB RAN 154 may include gNBs (including 160B (collectively gNB 160)) and / or one or more second types of base stations (e.g., ng-eNB 162A and ng-eNB 162B (collectively ng eNB 162)). RAN 154 may include one or more of any number of base station types. gNB 160 and ng eNB 162 may also be called base stations. 162) may include one or more sets of antennas for wirelessly communicating with the wireless device 156 (e.g., via an air interface). One or more base stations (e.g., gNB 160 and / or ng eNB 162) may include multiple sets of antennas for controlling multiple cells (or sectors), each of them. The cells of the base stations (e.g., gNB 160 and ng-eNB 162) can provide wireless coverage to the wireless device 156 over a wide geographical area to support wireless device mobility.

[0023] Base stations (e.g., gNB 160 and / or ng-eNB 162) connect to CN 152 (e.g., 5G) via the first interface (e.g., NG interface). NG and Xn interfaces may be connected to a CN, and may also be connected to other base stations via a second interface (e.g., an 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. A base station (e.g., gNB 160 and / or ng-eNB 162) may communicate with radio device 156 via a third interface (e.g., a Uu interface). A base station (e.g., gNB 160A) may communicate with radio device 156A via the Uu interface. The NG, Xn, and Uu interfaces may be associated with a protocol stack. The protocol stack associated with an interface may be used by the network elements shown in Figure 1B to exchange data and signaling messages. The protocol stack may include two planes, namely a user plane and a control plane. Any other number of planes may be used (e.g., within the protocol stack). The user plane may process data of interest to the user. The control plane may process signaling messages of interest to the network elements.

[0024] One or more base stations (e.g., gNB 160 and / or ng-eNB 162) may communicate with one or more AMF / UPF devices, such as AMF / UPF 158, via one or more interfaces (e.g., NG interfaces). A base station (e.g., gNB 160A) may communicate with and / or connect to the UPF 158B of the AMF / UPF 158 via the NG user plane (NG-U) interface. The NG-U interface may provide / implement the delivery (e.g., unguaranteed delivery) of user plane PDUs between the base station (e.g., gNB 160A) and the UPF device (e.g., UPF 158B). A base station (e.g., gNB 160A) may also communicate with and / or connect to AMF devices (e.g., AMF 158A) via the NG control plane (NG-C) interface. The NG-C interface may provide / perform, for example, NG interface management, wireless device context management (e.g., UE context management), wireless device mobility management (e.g., UE mobility management), NAS message transport, paging, PDU session management, configuration transfer, and / or warning message sending.

[0025] A radio device may access a base station via an interface (e.g., a Uu interface) for user plane and control plane configurations. A base station (e.g., gNB 160) may provide user plane and control plane protocol terminations to radio device 156 via a Uu interface. A base station (e.g., gNB 160A) may provide user plane and control plane protocol terminations to radio device 156A on a Uu interface associated with a first protocol stack. A base station (e.g., ng-eNB 162) may provide Evolutionary UMTS Terrestrial Radio Access (E UTRA) user plane and control plane protocol terminations to radio device 156 via a Uu interface (e.g., E UTRA may refer to 3GPP® 4G radio access technology). A base station (e.g., ng-eNB 162B) may provide E UTRA user plane and control plane protocol terminations to radio device 156B via a Uu interface associated with a second protocol stack. User plane and control plane protocol terminations may include, for example, NR user plane and control plane protocol terminations, 4G user plane and control plane protocol terminations, and so on.

[0026] CN 152 (e.g., 5G-CN) may be configured to handle one or more radio accesses (e.g., NR, 4G, and / or any other radio access). Furthermore, an NR network / device (or any first network / device) may be connected to a 4G core network / device (or any second network / device) in non-standalone mode (e.g., non-standalone operation). In non-standalone mode / operation, the 4G core network may be used to provide (or at least support) control plane functions (e.g., initial access, mobility, and / or paging). Although only one AMF / UPF 158 is shown in Figure 1B, one or more base stations (e.g., one or more gNBs and / or one or more ng-eNBs) may be connected to multiple AMF / UPF nodes, for example, to provide redundancy and / or load sharing across multiple AMF / UPF nodes.

[0027] Interfaces between network elements (e.g., network elements shown in Figure 1B) (e.g., Uu, Xn, and / or NG interfaces) may be associated with a protocol stack that the network elements can use to exchange data and signaling messages. The protocol stack may include two planes: a user plane and a control plane. Any other number of planes may be used (e.g., within the protocol stack). The user plane may process data associated with a user (e.g., data of interest to the user). The control plane may process data associated with one or more network elements (e.g., signaling messages of interest to the network elements).

[0028] The communication network 100 in Figure 1A and / or the communication network 150 in Figure 1B may include any number and / or types of devices, such as computing devices, wireless devices, mobile devices, handsets, tablets, laptops, Internet of Things (IoT) devices, hotspots, cellular repeaters, computing devices, and / or more generally, user equipment (e.g., UEs). One or more of the above-mentioned types of devices may be referenced herein (e.g., UEs, wireless devices, computing devices, etc.), but it should be understood that any device herein may include any one or more of the above-mentioned types of devices or similar devices. The communication network, and any other network referenced herein, may include LTE networks, 5G networks, satellite networks, and / or any other networks for wireless communication (e.g., any 3GPP® network and / or any non-3GPP® network). The apparatus, systems, and / or methods described herein may generally be described as being implemented in one or more devices (e.g., wireless devices, base stations, eNBs, gNBs, computing devices, etc.) within one or more networks, but it will be understood that one or more features and steps may be implemented in any device and / or any network.

[0029] Figure 2A shows an example of a user plane configuration. The user plane configuration may include, for example, an NR user plane protocol stack. Figure 2B shows an example of a control plane configuration. The control plane configuration may include, for example, an NR control plane protocol stack. One or more of the user plane configurations and / or control plane configurations may use a possible Uu interface between the radio device 210 and the base station 220. The protocol stacks shown in Figure 2A and Figure 2A may be substantially the same as or similar to those used for the Uu interface between the radio device 156A and the base station 160A shown in Figure 1B.

[0030] The user plane configuration (e.g., the NR user plane protocol stack) may include multiple layers (e.g., five or any other number of layers) implemented in the radio device 210 and base station 220 (e.g., as shown in Figure 2A). At the bottom of the protocol stack, physical layers (PHYs) 211 and 221 may 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 protocol layer above PHY 211 may include a medium access control layer (MAC) 212, a radio link control layer (RLC) 213, a packet data convergence protocol layer (PDCP) 214, and / or a service data application protocol layer (SDAP) 215. The protocol layer above PHY 221 may include a medium access control layer (MAC) 222, a radio link control layer (RLC) 223, a packet data convergence protocol layer (PDCP) 224, and / or a service data application protocol layer (SDAP) 225. One or more of the four protocol layers on PHY 211 may correspond to layer 2 or the data link layer of the OSI model. One or more of the four protocol layers on PHY 221 may correspond to layer 2 or the data link layer of the OSI model.

[0031] Figure 3 shows an embodiment of the protocol layer. The protocol layer may include, for example, the protocol layer of the NR user plane protocol stack. One or more services may be provided between the protocol layers. SDAP (e.g., SDAPS shown in Figures 2A and 3) 215 and 225) may perform Quality of Service (QoS) flow processing. A radio device (e.g., radio devices 106, 156A, 156B, and 210) may receive services via / through a PDU session, which may be a logical connection between the radio device and the DN. A PDU session may have one or more QoS flows 310. The CN's UPF (e.g., UPF 158B) may map IP packets to one or more QoS flows in a PDU session based on, for example, one or more QoS requirements (e.g., delay, data rate, error rate, and / or any other quality / service requirements). SDAPs 215 and 225 may perform mapping / unmapping between one or more QoS flows 310 and one or more radio bearers 320 (e.g., data radio bearers). The mapping / unmapping between one or more QoS flows 310 and radio bearers 320 may be determined by the SDAP 225 of base station 220. The SDAP 215 of the wireless device 210 may be informed of the mapping between QoS flows 310 and the wireless bearer 320 via reflection mapping and / or control signaling received from the base station 220. For reflection mapping, the SDAP 225 of the base station 220 may determine mapping / unmapping between one or more QoS flows 310 and the wireless bearer 320 by marking downlink packets with QoS flow indicators (QFIs) that can be monitored / detected / identified / indicated / observed by the SDAP 215 of the wireless device 210.

[0032] PDCP (e.g., PDCP 214 and 224 shown in Figures 2A and 3) may perform, for example, header compression / decompression to reduce the amount of data that may need to be transmitted (or sent) over the air interface, encryption / decryption to prevent unauthorized decryption of data transmitted (or sent) over the air interface, and / or integrity protection (e.g., to ensure that control messages originate from the intended source). PDCP 214 and 224 may perform, for example, retransmission of undelivered packets, sequential delivery and rearrangement of packets, and / or removal of duplicate packets for handover (e.g., intra-gNB handover). PDCP 214 and 224 may perform packet duplication, for example, to improve the likelihood of receiving packets. A receiver may receive duplicate packets and may remove any duplicate packets. Packet duplication may be useful for certain services, such as services requiring high reliability.

[0033] The PDCP layer (e.g., PDCP 214 and 224) may perform mapping / unmapping between a segmented radio bearer and an RLC channel (e.g., RLC channel 330) (e.g., in a dual-connection scenario / configuration). Dual-connection may refer to a technique that enables a radio device to communicate with multiple cells (e.g., two cells), or more broadly, multiple cell groups, including a master cell group (MCG) and a secondary cell group (SCG). A segmented bearer may be configured and / or used, for example, when a single radio bearer (e.g., one of the radio bearers provided / configured by PDCP 214 and 224 as a service to SDAP 215 and 225) is handled by a cell group in a dual-connection. PDCP 214 and 224 may perform mapping / unmapping between the segmented radio bearer and an RLC channel 330 belonging to a cell group.

[0034] The RLC layer (e.g., RLC 213 and 223) may perform segmentation, retransmission via automatic repeat requests (ARQ), and / or removal of duplicate data units received from the MAC layer (e.g., MAC 212 and 222, respectively). The RLC layer (e.g., RLC 213 and 223) may support multiple transmission modes (e.g., three transmission modes: transparent mode (TM), unacknowledged response mode (UM), and acknowledgment mode (AM)). The RLC layer may perform one or more of the indicated functions, for example, based on the transmission mode in which the RLC layer is operating. The RLC configuration may be per logical channel. The RLC configuration may not depend on the duration of the numerology and / or the transmission time interval (TTI) (or other durations). 213 and 223) may provide / configure an RLC channel as a service to the PDCP layer (e.g., PDCP 214 and 224, respectively) as shown in Figure 3.

[0035] The MAC layer (e.g., MAC 212 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 / data portions belonging to one or more logical channels to / from transport blocks (TBs) delivered to / from the PHY layer (e.g., PHY 211 and 221, respectively). The MAC layer of a base station (e.g., MAC 222) may be configured to perform scheduling between radio devices, scheduling information reporting, and / or priority processing via dynamic scheduling. Scheduling may be performed by the base station (e.g., base station 220 of MAC 222) for downlink / or uplink. The MAC layer (e.g., MAC 212 and 222) may be configured to perform error correction via hybrid automatic repeating requests (HARQ) (e.g., one HARQ entity per carrier in the case of carrier aggregation (CA)), priority processing between logical channels of radio device 210 via logical channel prioritization, and / or padding. The MAC layer (e.g., MAC 212 and MAC 222) may support one or more numerologies and / or transmit timings. Commands for mapping logical channel priority may control which numerologies and / or transmit timings a logical channel can use. The MAC layer (e.g., MAC 212 and 222) may, as a service, provide / configure logical channels 340 to the RLC layer (e.g., RLC 213 and 223).

[0036] The PHY layer (e.g., PHY 211 and 221) may perform mapping of transport channels to physical channels and / or digital and analog signal processing functions for transmitting and / or receiving information (e.g., via an air interface). Digital and / or analog signal processing functions may include, for example, coding / decoding and / or modulation / demodulation. The PHY layer (e.g., PHY 211 and 221) may perform multi-antenna mapping. The PHY layer (e.g., PHY 211 and 221) may provide / configure one or more transport channels (e.g., transport channel 350) as a service to the MAC layer (e.g., MAC 212 and 222, respectively).

[0037] Figure 4A shows an example of a downlink data flow in a user plane configuration. The user plane configuration may include, for example, the NR user plane protocol stack shown in Figure 2A. One or more TBs may be generated, for example, based on the data flow through the user plane protocol stack. As shown in Figure 4A, a downlink data flow of three IP packets (n, n+1, and m) through the NR user plane protocol stack may generate two TBs (e.g., base station 220). An uplink data flow through the NR user plane protocol stack may be similar to the downlink data flow shown in Figure 4A. The three IP packets (n, n+1, and m) may be determined from two TBs, for example, based on the uplink data flow through the NR user plane protocol stack. A first quantity of packets (e.g., three or any other quantity) may be determined from a second quantity of TBs (e.g., two or another quantity).

[0038] A downlink data flow may be initiated, for example, when SDAP 225 receives three IP packets (or other quantities of IP packets) from one or more QoS flows and maps the three packets (or other quantities of packets) to radio bearers (e.g., radio bearers 402 and 404). SDAP 225 may map 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" before each SDAP SDU shown in Figure 4A) can be added to the IP packets to generate an SDAP PDU, which may be called a PDCP SDU. Data units transmitted to and from higher protocol layers may be called lower protocol layer service data units (SDUs), and data units transmitted to and from lower protocol layers may be called higher protocol layer protocol data units (PDUs). As shown in Figure 4A, the data unit from SDAP 225 may be an SDU of a lower protocol layer, PDCP 224 (e.g., a PDCP SDU), or it may be a PDU of SDAP 225 (e.g., an SDAP PDU).

[0039] Each protocol layer (e.g., the protocol layer as shown in Figure 4A), or at least some protocol layers, may perform its own function (e.g., one or more functions of each protocol layer described with respect to Figure 3), add the corresponding header, and / or forward its respective output to the next lower layer (e.g., the layer below it). The PDCP 224 may perform IP header compression and / or encryption. The PDCP 224 may forward its output (e.g., a PDCP PDU which is an RLC SDU) to the RLC 223. The RLC 223 may optionally perform segmentation (e.g., as shown for the IP packet in Figure 4A). The RLC 223 may forward its output (e.g., two RLC PDUs which are two MAC SDUs generated by adding their respective subheaders to two SDU segments (SDU Segs)) to the MAC 222. The MAC 222 may multiplex several RLC PDUs (MAC SDUs). MAC 222 can connect a MAC subheader to an RLC PDU (MAC SDU) to form a TB. The MAC subheader can be distributed across the MAC PDU (e.g., in an NR configuration, as shown in Figure 4A). The MAC subheader can be located entirely at the beginning of the MAC PDU (e.g., in an LTE configuration). The NR MAC PDU structure can reduce processing time and / or associated delays if, for example, the MAC PDU subheader is computed before assembling the complete MAC PDU.

[0040] Figure 4B shows an exemplary format of a MAC subheader in a MAC PDU. A MAC PDU may include a MAC subheader (H) and a MAC SDU. Each of the one or more MAC subheaders may include an SDU length field to indicate the length (e.g., bytes) of the corresponding MAC SDU, a logical channel identifier (LCID) field to identify / indicate 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.

[0041] One or more MAC control elements (CEs) may be added to or inserted into a MAC PDU by a MAC layer such as MAC 223 or MAC 222. As shown in Figure 4B, two MAC CEs may be inserted / added before two MAC PDUs. MAC CEs may be inserted / added at the beginning of a MAC PDU for downlink transmission (as shown in Figure 4B). For uplink transmission, one or more MAC CEs may be inserted / added at the end of a MAC PDU. MAC CEs may be used for in-band control signaling. Examples of MAC CEs may include scheduling-related MAC CEs such as buffer status reports and power headroom reports, start / stop MAC CEs (e.g., start / stop for PDCP duplicate detection, channel status information (CSI) reports, sounding reference signal (SRS) transmission, and MAC CEs for pre-configured components), discontinuous receive (DRX)-related MAC CEs, timing advance MAC CEs, and random access-related MAC CEs. A MAC CE may be preceded by a MAC subheader in a format similar to that described in the MAC subheader for a MAC SDU, and may be identified by a reserved value in the LCID field indicating the type of control information contained in the corresponding MAC CE.

[0042] Figure 5A shows an example of downlink channel mapping. Uplink channel mapping may include mapping between downlink channels (e.g., logical channels, transport channels, and physical channels). Figure 5B shows an example of uplink channel mapping. Uplink channel mapping may include mapping between uplink channels (e.g., logical channels, transport channels, and physical channels). Information may be transmitted through / through channels between the RLC, MAC, and PHY layers of the protocol stack (e.g., the NR protocol stack). Logical channels may be used between the RLC layer and the MAC layer. Logical channels may be classified / represented as control channels that can carry control and / or configuration information (e.g., within the NR control plane) or as traffic channels that can carry data (e.g., within the NR user plane). Logical channels may be classified / represented as dedicated logical channels that may be exclusive to a particular radio device, and / or as common logical channels that may be used by two or more radio devices (e.g., a group of radio devices).

[0043] A logical channel can be defined by the type of information it carries. A set of logical channels (e.g., in an NR configuration) may include one or more channels as described below: A paging control channel (PCCH) may include, or carry, one or more paging messages used for paging wireless devices whose location is unknown to the network at the cell level. A broadcast control channel (BCCH) may include / carry system information messages in the form of master information blocks (MIBs) and some system information blocks (SIBs). System information messages may be used by wireless devices to obtain information about how a cell is configured and how it operates within the cell. A common control channel (CCCH) may include / carry control messages along with random access. A dedicated control channel (DCCH) may include / carry control messages to / from a specific wireless device and configure the wireless device with configuration information. A dedicated traffic channel (DTCH) may include / carry user data to / from a specific wireless device.

[0044] Transport channels can be used between the MAC layer and the PHY layer. Transport channels can be defined by how the information they carry is transmitted / transmitted (e.g., via an air interface). A set of transport channels (e.g., defined by an NR configuration or any other configuration) may include one or more of the following channels: Paging Channel (PCH) can contain / carry paging messages originating from the PCCH. Broadcast Channel (BCH) can contain / carry MIBs from the BCCH. Downlink Shared Channel (DL-SCH) can contain / carry downlink data and signaling messages, including SIBs from the BCCH. Uplink Shared Channel (UL-SCH) can contain / carry uplink data and signaling messages. Random Access Channel (RACH) can provide wireless devices with access to the network without prior scheduling.

[0045] The PHY layer may pass / transfer information between processing levels of the PHY layer 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 layer may generate control information to support the low-level operation of the PHY layer. The PHY layer may provide / transfer control information to lower levels of the PHY layer via physical control channels (e.g., called L1 / L2 control channels). The set of physical channels and physical control channels (e.g., which may be defined by an NR configuration or any other configuration) may include one or more of the following channels: A physical broadcast channel (PBCH) may contain / carry MIBs from a BCH. A physical downlink shared channel (PDSCH) may contain / carry downlink data and signaling messages from a DL-SCH, as well as paging messages from a PCH. A physical downlink control channel (PDCCH) may contain / carry downlink control information (DCI), which may include downlink scheduling commands, uplink scheduling grants, and uplink power control commands. The physical uplink shared channel (PUSCH) may include / carry uplink data and signaling messages from the UL-SCH, as well as, in some embodiments, uplink control information (UCI), as described below. The physical uplink control channel (PUCCH) may include / carry UCI, which may include HARQ acknowledgments, channel quality indicators (CQI), pre-recording matrix indicators (PMI), rank indicators (RI), and scheduling requests (SR). The physical random access channel (PRACH) may be used for random access.

[0046] The physical layer may generate physical signals to support the low-level operation of the physical layer, which may be analogous to a physical control channel. As shown in Figures 5A and 5B, physical layer signals (which may be defined, for example, by an NR configuration or other configurations) may include a primary synchronization signal (PSS), a secondary synchronization signal (SSS), a channel state information reference signal (CSI-RS), a demodulation reference signal (DM-RS), a sounding reference signal (SRS), a phase tracking reference signal (PT-RS), and / or other arbitrary signals.

[0047] One or more channels (e.g., logical channels, transport channels, physical channels, etc.) can be used to perform functions associated with a control plan protocol stack (e.g., an NR control plane protocol stack). Figure 2B shows an example of a control plane configuration (e.g., an NR control plane protocol stack). In Figure 2B, the control plane configuration (e.g., an NR control plane protocol stack) may use one or more substantially identical / similar protocol layers (e.g., PHY 211 and 221, MAC 212 and 222, RLC 213 and 223, and PDCP 214 and 224) as an exemplary user plane configuration (e.g., an NR user plane protocol stack). The four similar protocol layers may include PHY 211 and 221, MAC 212 and 222, RLC 213 and 223, and PDCP 214 and 224. The control plane configuration (e.g., NR control plane stack) may have, for example, the Radio Resource Control (RRC) 216 and 226 and NAS protocols 217 and 237 at the top of the control plane configuration (e.g., NR control plane protocol stack), instead of having SDAP 215 and 225. The control plane configuration may also include an AMF 230 which includes the NAS protocol 237.

[0048] NAS protocols 217 and 237 may provide control plane functions between the wireless device 210 and the AMF 230 (e.g., AMF 158A or any other AMF), and / or more broadly, between the wireless device 210 and the CN (e.g., CN 152 or any other CN). NAS protocols 217 and 237 may provide control plane functions between the wireless device 210 and the AMF 230 via signaling messages called NAS messages. There may not be a direct path between the wireless device 210 and the AMF 230 through which NAS messages can be transmitted. NAS messages may be transported using the AS of the Uu and NG interfaces. NAS protocols 217 and 237 may provide control plane functions such as authentication, security, connection setup, mobility management, session management, and / or any other functions.

[0049] RRC layers 216 and 226 may provide / configure control plane functionality between the radio device 210 and the base station 220, and / or more broadly, between the radio device 210 and the RAN (e.g., base station 220). RRC layers 216 and 226 may provide / configure control plane functionality between the radio device 210 and the base station 220 via signaling messages, which may be called RRC messages. RRC messages may be transmitted / transmitted between the radio device 210 and the RAN (e.g., base station 220) using a signaling radio bearer and identical / similar PDCP, RLC, MAC, and PHY protocol layers. The MAC layer may multiplex control plane and user plane data into the same TB. RRC layers 216 and 226 may provide / configure 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 radio device 210 and the RAN (e.g., base station 220), security functions including key management, establishing, configuring, maintaining, and releasing signaling radio bearers and data radio bearers, mobility functions, QoS management functions, radio device measurement reports (e.g., radio device measurement reports) and report control, detection and recovery from radio link failures (RLFs), and / or NAS message forwarding functions. As part of establishing an RRC connection, RRC layers 216 and 226 may establish an RRC context, which may involve configuring parameters for communication between the radio device 210 and the RAN (e.g., base station 220).

[0050] Figure 6 shows an example of an RRC state and an RRC state transition. The RRC state of a wireless device can be changed to another RRC state (e.g., an RRC state transition for the wireless device). A wireless device may be substantially identical or similar to wireless devices 106, 210, or any other wireless device. A wireless device may be in at least one of several states, such as three RRC states including RRC connected 602 (e.g., RRC_CONNECTED), RRC idle 606 (e.g., RRC_IDLE), and RRC inactive 604 (e.g., RRC_INACTIVE). RRC inactive 604 may be RRC connected but inactive.

[0051] An RRC connection may be established with respect to a radio device. For example, this may occur during an RRC connection state. During an RRC connection state (e.g., during RRC connection 602), the radio device may have an established RRC context and may have at least one RRC connection with a base station. The base station may be similar to one or more base stations (e.g., one or more base stations of RAN 104 shown in Figure 1A, one of gNB 160 or ng-eNB 162 shown in Figure 1B, base station 220 shown in Figures 2A and 2B, or other base stations). The base station to which the radio device is connected (e.g., with which an RRC connection has been established) may have an RRC context with respect to the radio device. The RRC context, which may be called a radio device context (e.g., UE context), may include parameters for communication between the radio device and the base station. These parameters may include, for example, one or more of the following: AS context, radio link configuration parameters, bearer configuration information (e.g., data radio bearer, signaling radio bearer, logical channel, QoS flow, and / or related to PDU session), security information, and / or layer configuration information (e.g., PHY, MAC, RLC, PDCP, and / or SDAP layer configuration information). During an RRC connection state (e.g., RRC connection 602), the mobility of the radio device may be managed / controlled by the RAN (e.g., RAN 104 or NG RAN 154). The radio device may measure received signal levels (e.g., reference signal level, reference signal received power, reference signal received quality, received signal strength indicator, etc.) based on one or more signals transmitted from the serving cell and adjacent cells. The radio device may report these measurements to the serving base station (e.g., the base station currently providing service to the radio device). The serving base station of the radio device may, for example, request a handover to one of the adjacent base stations' cells based on the reported measurements. The RRC state may transition from an RRC connected state (e.g., RRC connected 602) to an RRC idle state (e.g., RRC idle 606) via the connection release procedure 608.The RRC state can transition from an RRC connected state (e.g., RRC connected 602) to an RRC inactive state (e.g., RRC inactive 604) via the connection termination procedure 610.

[0052] An RRC context does not have to be established for the radio device. For example, this can be during an RRC idle state. During an RRC idle state (e.g., RRC idle 606), an RRC context does not have to be established for the radio device. During an RRC idle state (e.g., RRC idle 606), the radio device does not have to have an RRC connection with the base station. During an RRC idle state (e.g., RRC idle 606), the radio device may be in a sleep state (e.g., to conserve battery power) for most of the time. The radio device may wake up periodically (e.g., discontinuous reception (per DRX) cycle) to monitor paging messages (e.g., paging messages set from the RAN). The mobility of the radio device may be managed by the radio device through a cell reselection procedure. The RRC state may transition from an RRC idle state (e.g., RRC idle 606) to an RRC connected state (e.g., RRC connected 602) via a connection establishment procedure 612 which may involve a random access procedure.

[0053] A previously established RRC context may be maintained for a radio device. For example, this may be during an RRC inactive state. During an RRC inactive state (e.g., RRC inactive 604), a previously established RRC context may be maintained within the radio device and base station. Maintaining the RRC context may enable a fast transition to an RRC connected state (e.g., RRC connected 602) with less signaling overhead compared to the transition from an RRC idle state (e.g., RRC idle 606) to an RRC connected state (e.g., RRC connected 602). During an RRC inactive state (e.g., RRC inactive 604), the radio device is in a sleep state, and the mobility of the radio device may be managed / controlled by the radio device via cell reselection. The RRC state may transition from an RRC inactive state (e.g., RRC inactive 604) to an RRC connected state (e.g., RRC connected 602) via a connection restart procedure 614. The RRC state may transition from an RRC inactive state (e.g., RRC inactive 604) to an RRC idle state (e.g., RRC idle 606) via a connection release procedure 616 that is the same as or similar to the connection release procedure 608.

[0054] The RRC state may be associated with a mobility management mechanism. During the RRC idle state (e.g., RRC idle 606) and the RRC inactive state (e.g., RRC inactive 604), mobility may be managed / controlled by the radio device via cell reselection. The purpose of mobility management during the RRC idle state (e.g., RRC idle 606) or the RRC inactive state (e.g., RRC inactive 604) may be to enable / enable the network to notify radio devices of events via paging messages without having to broadcast paging messages across the entire mobile communications network. The mobility management mechanism used during the RRC idle state (e.g., RRC idle 606) or the RRC idle state (e.g., RRC inactive 604) may enable / enable the network to track radio devices at the cell group level so that paging messages can be broadcast across cells in the cell group in which the radio device is currently (e.g., rather than sending paging messages across the entire mobile communications network). The mobility management mechanism in the RRC idle state (e.g., RRC idle 606) and the RRC inactive state (e.g., RRC inactive 604) may track wireless devices at the cell group level. The mobility management mechanism may perform tracking using, for example, different levels of grouping. There may be multiple levels of cell grouping granularity (e.g., three levels of cell grouping granularity: individual cells, cells within a RAN area identified by a RAN area identifier (RAI), and cells within a group of RAN areas identified by a tracking area identifier (TAI), called a tracking area).

[0055] A tracking area may be used to track a radio device (e.g., to track the location of a radio device at the CN level). A CN (e.g., CN 102, 5G CN 152, or any other CN) may send a list of TAIs associated with a radio device registration area (e.g., a UE registration area) to the radio device. The radio device may perform a registration update in the CN to allow the CN to update the radio device's location, for example, if the radio device moves to a cell associated with a TAI that is not included in the list of TAIs associated with a UE registration area (e.g., via cell reselection), providing the radio device with a new UE registration area.

[0056] RAN areas may be used to track radio devices (e.g., the location of a radio device at the RAN level). For radio devices in an RRC inactive state (e.g., RRC inactive 604), the radio device may be assigned / provided / configured in a RAN notification area. A RAN notification area may contain one or more cell identities (e.g., a list of RAIs and / or a list of TAIs). A base station may belong to one or more RAN notification areas. A cell may belong to one or more RAN notification areas. If a radio device moves (e.g., via cell reselection) to a cell not included in the RAN notification area to which the radio device is assigned / provided / configured, the notification area may be updated in the RAN to update the RAN notification area for the radio device.

[0057] A base station that stores an RRC context for a radio device, or the final serving base station of a radio device, may be called an anchor base station. The anchor base station may maintain an RRC context for the radio device for at least the duration that the radio device remains in the anchor base station's RAN notification area and / or the duration that the radio device remains in an RRC inactive state (e.g., RRC inactive 604).

[0058] A base station (e.g., gNB 160 in Figure 1B or any other base station) can be divided into two parts: a central unit (e.g., a base station central unit such as gNB CU) and one or more distributed units (e.g., base station distributed units such as gNB DU). The base station central unit (CU) can be coupled to one or more base station distributed units (DU) using an F1 interface (e.g., an F1 interface as defined in the NR configuration). The base station CU may include the RRC layer, PDCP layer, and SDAP layer. The base station distributed unit (DU) may include the RLC layer, MAC layer, and PHY layer.

[0059] Physical signals and physical channels (e.g., Figures 5A and 5B) can be mapped onto one or more symbols (e.g., orthogonal frequency division multiplexing (OFDM) symbols in an NR configuration, or any other symbols). OFDM is a multicarrier communication scheme that transmits / transmits data via F orthogonal subcarriers (or tones). The data, called source symbols, can be mapped to a set of complex symbols (e.g., M orthogonal amplitude modulation (M-QAM) symbols or M phase shift key (M PSK) symbols or any other modulation symbols) which are divided into F parallel symbol streams before the data is transmitted. The F parallel symbol streams can be treated as if they were in the frequency domain. The F parallel symbols can be used as input to an inverse fast Fourier transform (IFFT) block that converts them to the time domain. The IFFT block can take one F source symbol at a time from each of the F parallel symbol streams. The IFFT block can 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. F time-domain samples can form a single OFDM symbol. The OFDM symbol provided / output by the IFFT block can be transmitted / transmitted over the air interface at the carrier frequency after, for example, one or more processes (e.g., addition of cyclic prefixes) and upconversion. F parallel symbol streams can be mixed using a Fast Fourier Transform (FFT) block before being processed by the IFFT block. This operation may generate OFDM symbols pre-encoded with a Discrete Fourier Transform (DFT), which can be used by one or more uplink radio devices to reduce the peak-to-average power ratio (PAPR). Inverse processing can be performed on the OFDM symbols at the receiver using an FFT block to recover the data mapped to the source symbols.

[0060] Figure 7 shows an example of a frame configuration. A frame may include, for example, an NR radio frame in which OFDM symbols may be grouped. A frame (e.g., an NR radio frame) can be identified / indicated by a system frame number (SFN) or any other value. The SFN may repeat over a period of 1024 frames. A single 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 one or more slots (e.g., depending on the numerology and / or different subcarrier intervals). Each of the one or more slots may contain, for example, 14 OFDM symbols per slot. Any number of symbols, slots, or durations can be used for any time interval.

[0061] The duration of a slot may depend on the numerology used for the OFDM symbol of the slot. For example, flexible numerology may be supported to accommodate different deployments (e.g., from cells with carrier frequencies less than 1 GHz to cells with carrier frequencies in the mm-wave range). Flexible numerology may be supported, for example, in an NR configuration or any other radio configuration. Numerology may be defined in terms of subcarrier spacing and / or cyclic prefix duration. Subcarrier spacing may be scaled up by a power of 2 from a baseline subcarrier spacing of 15 kHz. Cyclic prefix duration may be scaled down by a power of 2 from a baseline cyclic prefix duration of 4.7 microseconds, for example, for numerology in an NR configuration or any other radio configuration. Numerology can be defined by the following combinations of subcarrier intervals / cyclic prefix durations: 15 kHz / 4.7 microseconds, 30 kHz / 2.3 microseconds, 60 kHz / 1.2 microseconds, 120 kHz / 0.59 microseconds, 240 kHz / 0.29 microseconds, and / or any other combination of subcarrier intervals / cyclic prefix durations.

[0062] A slot may have a fixed number / quantity of OFDM symbols (e.g., 14 OFDM symbols). Numerologies with higher subcarrier spacing may have shorter slot durations and more slots per subframe. An example of a numerology-dependent slot duration and slot-per-subframe transmission structure is shown in Figure 7 (a numerology with a subcarrier spacing of 240 kHz is not shown in Figure 7). A subframe (e.g., in an NR configuration) may be used as a numerology-independent time reference. A slot may be used as a unit on which uplink and downlink transmissions are scheduled. Scheduling (e.g., in an NR configuration) may be separated from slot duration. Scheduling can be started with any OFDM symbol. Scheduling may continue for as many symbols as needed for transmission, for example, to support low latency. These partial slot transmissions may be called minislot or subslot transmissions.

[0063] Figure 8 shows an exemplary resource configuration for one or more carriers. The resource configuration may include slots in the time and frequency domains for an NR carrier or any other carrier. The slots may include resource elements (REs) and resource blocks (RBs). A resource element (RE) may be the smallest physical resource (e.g., an NR configuration). An RE may span one OFDM symbol in the time domain by one subcarrier in the frequency domain, as shown in Figure 8. An RB may span 12 consecutive REs in the frequency domain, as shown in Figure 8. A carrier (e.g., an NR carrier) may be limited to a width of a certain amount of RBs and / or subcarriers (e.g., 275 RBs or 275 × 12 = 3300 subcarriers). Such limitations, if used, may limit the carrier (e.g., NR carrier) frequency based on subcarrier spacing (e.g., carrier frequencies of 50, 100, 200, and 400 MHz for subcarrier spacings of 15, 30, 60, and 120 kHz, respectively). A 400MHz bandwidth can be set based on a 400MHz bandwidth limit per carrier. Any other bandwidth can be set based on a bandwidth limit per carrier.

[0064] A single numerology can be used across the entire bandwidth of a carrier (e.g., NR as shown in Figure 8). In other exemplary configurations, multiple numerologies may be supported on the same carrier. NR and / or other access technologies may support a wide range of carrier bandwidths (e.g., up to 400 MHz for a 120 kHz subcarrier spacing). Not all radio devices can receive the entire carrier bandwidth (e.g., due to hardware limitations and / or different radio device capabilities). Receiving and / or utilizing the entire carrier bandwidth may be prohibited, for example, with respect to the power consumption of the radio device. A radio device may adapt the size of its receiving bandwidth based on the amount of traffic it is expected to receive (e.g., to reduce power consumption and / or for other purposes). Such adaptation may be called bandwidth adaptation.

[0065] The configuration of one or more bandwidth parts (BWPs) may support one or more radio devices that cannot receive the full carrier bandwidth. BWPs may, for example, support bandwidth adaptation for such radio devices that cannot receive the full carrier bandwidth. A BWP (e.g., a BWP in an NR configuration) may be defined by a subset of consecutive RBs on the carrier. A radio device 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). One or more of the BWPs configured for a serving cell may be active, for example, at a given time. One or more BWPs may be called the active BWPs of a serving cell. A serving cell may have one or more first active BWPs on the uplink carrier and, for example, one or more second active BWPs on the secondary uplink carrier if the serving cell consists of a secondary uplink carrier.

[0066] A downlink BWP from a configured set of downlink BWPs can be linked to an uplink BWP from a configured set of uplink BWPs (for example, for a non-paired spectrum). Downlink BWPs and uplink BWPs can be linked, for example, if the downlink BWP index of one downlink BWP and the uplink BWP index of the other uplink BWP are the same. A wireless device may expect that the center frequency of a downlink BWP is the same as the center frequency of an uplink BWP (for example, for a non-paired spectrum).

[0067] A base station may configure a radio device with one or more control resource sets (CORESETs) for at least one search space. A base station may configure a radio device with one or more CORESETs for a set of downlink BWPs configured on a primary cell (PCell) or secondary cell (SCell). The search space may include a set of locations in the time and frequency domain where a radio device can monitor / detect / discover / identify control information. The search space may be a radio device-specific search space (e.g., a UE-specific search space) or a common search space (e.g., potentially available to a group of multiple radio devices or radio user equipment). A base station may configure a group of radio devices in an active downlink BWP in a common search space on a PCell or on a primary / secondary cell (PSCell).

[0068] A base station may configure a radio device with one or more resource sets for one or more PUCCH transmissions for uplink BWPs within a configured set of uplink BWPs. The radio device may receive downlink receptions (e.g., PDCCH or PDSCH) within a downlink BWP according to a configured numerology (e.g., configured subcarrier interval and / or configured cyclic prefix duration) for a downlink BWP. The radio device may transmit / transmit uplink transmissions (e.g., PUCCH or PUSCH) on an uplink BWP according to a configured numerology (e.g., configured subcarrier interval and / or configured cyclic prefix length for an uplink BWP).

[0069] One or more BWP indicator fields may be provided / included in the Downlink Control Information (DCI). The value of a BWP indicator field may indicate which BWP in the configured set is the active downlink BWP for one or more downlink receives. The value of one or more BWP indicator fields may indicate the active uplink BWP for one or more uplink transmits.

[0070] A base station may semi-statically configure a radio device with a default downlink BWP within a set of configured downlink BWPs associated with the PCell. The default downlink BWP may be the initial active downlink BWP, for example, if the base station does not provide / configure a default downlink BWP for / to the radio device. The radio device may determine which BWP is the initial active downlink BWP, for example, based on a CORESET configuration obtained using a PBCH.

[0071] A base station may configure a radio device with a BWP inactivity timer value for a PCell. The radio device may start or restart the BWP inactivity timer at any appropriate time. The radio device may start or restart the BWP inactivity timer if, for example, one or more conditions are met. One or more conditions may include at least one of the following: the radio device detects a DCI indicating an active downlink BWP other than the default downlink BWP for paired-spectrum operation; the radio device detects a DCI indicating an active downlink BWP other than the default downlink BWP for non-paired-spectrum operation; and / or the radio device detects a DCI indicating an active uplink BWP other than the default uplink BWP for non-paired-spectrum operation. The radio device may start / run the BWP inactivity timer toward expiration (e.g., incrementing from zero to the BWP inactivity timer value or decreasing from the BWP inactivity timer value to zero) if, for example, the radio device does not detect a DCI during a time interval (e.g., 1 millisecond or 0.5 milliseconds). A wireless device may switch from active downlink BWP to default downlink BWP if, for example, the BWP inactivity timer expires.

[0072] A base station may semi-statically configure a radio device with one or more BWPs. The radio device may switch the active BWP from the first BWP to the second BWP based on (for example, subsequently or in response to) receiving a DCI indicating a second BWP as the active BWP. The radio device may also switch the active BWP from the first BWP to the second BWP based on (for example, subsequently or in response to) the expiration of a BWP inactivity timer (for example, if the second BWP is the default BWP).

[0073] Downlink BWP switching may refer to switching the active downlink BWP from the first downlink BWP to the second downlink BWP (e.g., the second downlink BWP is activated and the first downlink BWP is deactivated). Uplink BWP switching may refer to switching the active uplink BWP from the first uplink BWP to the second uplink BWP (e.g., the second uplink BWP is activated and the first uplink BWP is deactivated). Downlink and uplink BWP switching may occur independently (e.g., paired spectrum / spectrum). Downlink and uplink BWP switching may occur simultaneously (e.g., non-paired spectrum / spectrum). Switching between configured BWPs may occur based on, for example, RRC signaling, DCI signaling, expiration of a BWP non-activity timer, and / or the start of random access.

[0074] Figure 9 shows an example of a configured BWP. Bandwidth matching using multiple BWPs (e.g., three BWPs configured for an NR carrier) may be available. A wireless device configured with multiple BWPs (e.g., three BWPs) may switch from one BWP to another at a switching point. The BWPs may include BWP 902 with a bandwidth of 40 MHz and a subcarrier spacing of 15 kHz, BWP 904 with a bandwidth of 10 MHz and a subcarrier spacing of 15 kHz, and BWP 906 with a bandwidth of 20 MHz and a subcarrier spacing of 60 kHz. BWP 902 may be the initial active BWP, and BWP 904 may be the default BWP. The wireless device may switch between BWPs at a switching point. The wireless device may switch from BWP 902 to BWP 904 at switching point 908. The switch at switching point 908 may be made for any appropriate reason. A switch at switching point 908 may occur, for example, based on (e.g., after or in response to) the expiration of a BWP inactivity timer (e.g., indicating a switch to the default BWP). A switch at switching point 908 may occur, for example, based on (e.g., after or in response to) the receipt of a DCI indicating BWP 904 as the active BWP. The wireless device may switch at switching point 910 from active BWP 904 to BWP 906, for example, after or in response to receiving a DCI indicating BWP 906 as the new active BWP. The wireless device may switch the active BWP based on (e.g., after or in response to) the expiration of a BWP inactivity timer. The switch may occur at the switching point 912 from BWP 906 to BWP 904. The wireless device may switch at the switching point 912 from active BWP 906 to BWP 904 after receiving, for example, a DCI indicating BWP 904 as the new active BWP. The wireless device may switch at the switching point 914 from active BWP 904 to BWP 902 after receiving, for example, a DCI indicating BWP 902 as the new active BWP.

[0075] The wireless device procedure for switching BWPs on a secondary cell may be identical / similar to that on a primary cell, for example, if the wireless device is configured for the secondary cell with a set of configured downlink BWPs and a default downlink BWP with a timer value. The wireless device may use timer values ​​and a default downlink BWP for the secondary cell in the same / similar manner as the wireless device uses timer values ​​and / or a default BWP for the primary cell. Timer values ​​(e.g., BWP inactivity timers) may be configured for each cell (e.g., for one or more BWPs) for example, via RRC signaling or other arbitrary signaling. One or more active BWPs may switch to another BWP, for example, based on the expiration of a BWP inactivity timer.

[0076] Two or more carriers may be aggregated, and data may be transmitted / transmitted simultaneously between the same radio device using carrier aggregation (CA) (for example, to increase the data rate). The aggregated carriers in CA may be called component carriers (CC). For example, when CA is configured / used, there may be multiple numbers / quantities of serving cells for the radio device (e.g., one serving cell for the CC). A CC may have multiple configurations within the frequency domain.

[0077] Figure 10A shows an example of a CA configuration based on CCs. As shown in Figure 10A, the three types of CA configurations may include an in-band (continuous) configuration 1002, an in-band (discontinuous) configuration 1004, and / or an in-band configuration 1006. In the in-band (continuous) configuration 1002, the two CCs may be aggregated in the same frequency band (frequency band A) and may be located directly adjacent to each other within the frequency band. In the in-band (discontinuous) configuration 1004, the two CCs may be aggregated in the same frequency band (frequency band A), but may be separated from each other within the frequency band by a gap. In the in-band configuration 1006, the two CCs may be located in different frequency bands (e.g., frequency band A and frequency band B, respectively).

[0078] The network can set a maximum number of CCs that can be aggregated (for example, up to 32 CCs may be aggregated in NR, or any other number may be aggregated in other systems). Aggregated CCs may have the same or different bandwidths, subcarrier spacings, and / or duplication schemes (TDD, FDD, or any other duplication scheme). Serving cells for wireless devices using CA may have downlink CCs. One or more uplink CCs may optionally be configured for serving cells (for example, against FDD). The ability to aggregate more downlink carriers than uplink carriers may be useful, for example, when a wireless device has more data traffic on the downlink than on the uplink.

[0079] One of the aggregation cells for a wireless device may be called a primary cell (PCell), for example, when a CA is configured. A PCell may be the serving cell to which the wireless device initially connects or accesses, for example, during or to RRC connection establishment, RRC connection re-establishment, and / or handover. A PCell may provide / configure NAS mobility information and security inputs to the wireless device. A wireless device may have different PCells. For downlinks, the carrier corresponding to a PCell may be called a downlink primary cell CC (DL PCC). For uplinks, the carrier corresponding to a PCell may be called an uplink primary cell CC (UL PCC). Other aggregation cells for wireless devices (e.g., associated with CCs other than DL PCC and UL PCC) may be called secondary cells (SCells). SCells may be configured, for example, after a PCell has been configured for the wireless device. SCells may be configured via an RRC connection reconfiguration procedure. For downlinks, the carrier corresponding to a SCell may be called a downlink secondary CC (DL SCC). For uplinks, the carrier compatible with SCell is the uplink secondary CC (UL). You can also call it SCC.

[0080] A SCell configured for a wireless device can be started or stopped, for example, based on traffic and channel conditions. Stopping the SCell can cause the wireless device to stop PDCCH and PDSCH reception on the SCell, and PUSCH, SRS, and CQI transmission on the SCell. A configured SCell can be started or stopped using, for example, MACCE (e.g., MAC CE as described in relation to Figure 4B). The CE may use a bitmap (e.g., one bit per SCell) to indicate to the wireless device which SCell (e.g., within a subset of the configured SCells) should be started or stopped. The configured SCells may be stopped (e.g., after or in response to) the expiration of a SCell stop timer (e.g., one SCell stop timer may be configured per SCell).

[0081] DCI may include control information such as scheduling assignments and scheduling grants for cells. DCI may be transmitted / transmitted via cells corresponding to scheduling assignments and / or scheduling grants, which may be called self-scheduling. DCI containing control information for a cell may be transmitted / transmitted via another cell, which may be called cross-carrier scheduling. Uplink control information (UCI) may include control information such as HARQ acknowledgments and channel state feedback (e.g., CQI, PMI, and / or RI) for aggregation cells. UCI may be transmitted / transmitted via the uplink control channel (e.g., PUCCH) of a PCell or a specific SCell (e.g., a SCell composed of PUCCHs). A large number of aggregated downlink CCs may overload the PUCCH of a PCell. A cell may be divided into multiple PUCCH groups.

[0082] Figure 10B shows an example of a cell group. An aggregation cell may consist of one or more PUCCH groups (for example, as shown in Figure 10B). One or more cell groups or one or more uplink control channel groups (e.g., PUCCH group 1010 and PUCCH group 1050) may each include one or more downlink CCs. PUCCH group 1010 may include one or more downlink CCs, for example, three downlink CCs, i.e., PCell 1011 (e.g., DL PCC), SCell 1012 (e.g., DL SCC), and SCell 1013 (e.g., DL SCC). PUCCH group 1050 may include one or more downlink CCs, for example, three downlink CCs, i.e., PUCCH SCell (or PSCell) 1051 (e.g., DL SCC), SCell 1052 (e.g., DL SCC), and SCell 1053 (e.g., DL SCC). One or more uplink CCs of PUCCH group 1010 may be configured as PCell 1021 (e.g., UL PCC), SCell 1022 (e.g., UL SCC), and SCell 1023 (e.g., UL SCC). One or more uplink CCs of PUCCH group 1050 may be configured as PUCCH SCell (or PSCell) 1061 (e.g., UL SCC), SCell 1062 (e.g., UL SCC), and SCell 1063 (e.g., UL SCC). UCIs associated with downlink CCs of PUCCH group 1010, indicated as UCI 1031, UCI 1032, and UCI 1033, may be transmitted / transmitted via the uplink of PCell 1021 (e.g., via the PUCCH of PCell 1021). The UCIs associated with the downlink CC of PUCCH group 1050, indicated as UCI 1071, UCI 1072, and UCI 1073, may be transmitted / transmitted via the uplink of PUCCH SCell (or PSCell) 1061 (e.g., via the PUCCH of PUCCH SCell 1061).A single uplink PCell can be configured to transmit / transmit UCIs associated with six downlink CCs, for example, if the aggregation cell shown in Figure 10B is not divided into PUCCH group 1010 and PUCCH group 1050. PCell 1021 may become overloaded if, for example, UCIs 1031, 1032, 1033, 1071, 1072, and 1073 are transmitted / transmitted through PCell 1021. Overload can be prevented and / or reduced by separating the transmission of UCIs between PCell 1021 and PUCCH SCell (or PSCell) 1061.

[0083] A PCell may include a downlink carrier (e.g., PCell 1011) and an uplink carrier (e.g., PCell 1021). An SCell may include only a downlink carrier. 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, for example, display / identify the cell's downlink carrier and / or uplink carrier, depending on the context in which the physical cell ID is used. The physical cell ID may be determined, for example, using synchronization signals (e.g., PSS and / or SSS) transmitted / transmitted over the downlink component carrier. The cell index may be determined, for example, using one or more RRC messages. The physical cell ID may also be called a carrier ID, and the cell index may also be called a carrier index. A first physical cell ID for a first downlink carrier may refer to a first physical cell ID for a cell containing a first downlink carrier. Substantially the same / similar concepts may apply, for example, to carrier initiation. The activation of the first carrier may refer to the activation of the cell containing the first carrier.

[0084] The multi-carrier nature of the PHY layer may be exposed / indicated in the MAC layer (e.g., in a CA configuration). HARQ entities may operate on serving cells. Transport blocks may be generated per serving cell allocation / grant. Transport blocks and potential HARQ retransmissions of transport blocks may be mapped to serving cells.

[0085] For downlink, a base station may transmit / propagate (e.g., unicast, multicast, and / or broadcast) one or more reference signals (RS) (e.g., PSS, SSS, CSI-RS, DM-RS, and / or PT-RS) to one or more radio devices. For uplink, one or more radio devices may transmit / propagate one or more RS to a base station (e.g., DM-RS, PT-RS, and / or SRS). PSS and SSS may be transmitted / propagate by the base station and used by one or more radio devices to synchronize one or more radio devices with the base station. A synchronization signal (SS) / physical broadcast channel (PBCH) block may include PSS, SSS, and PBCH. The base station may periodically transmit / propagate bursts of SS / PBCH blocks, which may be called SSB.

[0086] Figure 11A shows an example mapping of one or more SS / PBCH blocks. An SS / PBCH block burst may consist of one or more SS / PBCH blocks (e.g., four SS / PBCH blocks as shown in Figure 11A). Bursts may be transmitted / transmitted periodically (e.g., every two frames, every 20 milliseconds, or at any other duration). Bursts may be limited to half frames (e.g., the first half frame having a duration of 5 milliseconds). These parameters (e.g., the number of SS / PBCH blocks per burst, the periodicity of the burst, the location of the burst within a frame) may be configured based on at least one of the following factors: for example, the carrier frequency of the cell on which the SS / PBCH block is transmitted / transmitted, the cell's numerology or subcarrier spacing, the network configuration (e.g., using RRC signaling), and / or any other appropriate factor. A radio device may assume subcarrier spacings for an SS / PBCH block based on the monitored carrier frequency, unless the radio network, for example, configures a radio device that assumes different subcarrier spacings.

[0087] An SS / PBCH block may span one or more OFDM symbols in the time domain (e.g., four OFDM symbols as shown in Figure 11A, or any other number of symbols) and one or more subcarriers in the frequency domain (e.g., 240 consecutive subcarriers or any other number of subcarriers). PSS, SSS, and PBCH may have a common center frequency. PSS may be transmitted / transmitted first, for example, spanning one OFDM symbol and 127 subcarriers. SSS may be transmitted / transmitted after PSS (e.g., after two symbols), spanning one OFDM symbol and 127 subcarriers. PBCH may be transmitted / transmitted after PSS (for example, across the following three OFDM symbols), and may span 240 subcarriers (for example, in the second and fourth OFDM symbols as shown in Figure 11A), and / or span fewer than 240 subcarriers (for example, in the third OFDM symbol as shown in Figure 11A).

[0088] The location of the SS / PBCH block in the time and frequency domains may not be known to the wireless device (e.g., when the wireless device is searching for a cell). The wireless device may monitor the carrier of the PSS to find and select a cell, for example. The wireless device may monitor the frequency location within the carrier. If the wireless device does not find the PSS after a certain period (e.g., 20 milliseconds), it may search for the PSS at a different frequency location within the carrier. The wireless device may search for the PSS at a different frequency location within the carrier, for example, as indicated by a synchronous raster. If the wireless device finds the PSS at a location in the time and frequency domains, it may determine the locations of the SSS and PBCH, respectively, based on the known structure of the SS / PBCH block, for example. The SS / PBCH block may be a cell-defining SS block (CD-SSB). A primary cell may be associated with a CD-SSB. A CD-SSB may be located on a synchronous raster. Cell selection / searching and / or re-selection may be based on the CD-SSB.

[0089] SS / PBCH blocks can be used by a radio device to determine one or more parameters of a cell. For example, a radio device may determine the physical cell identifier (PCI) of a cell based on the PSS and SSS arrays, respectively. A radio device may determine the location of a cell's frame boundary based on the location of an SS / PBCH block. An SS / PBCH block may indicate that it was transmitted / transmitted according to a transmission pattern. In a transmission pattern, an SS / PBCH block may be a known distance from the frame boundary (e.g., a predefined distance for a RAN configuration between one or more networks, one or more base stations, and one or more radio devices).

[0090] The PBCH may use QPSK modulation and / or forward error correction (FEC). The FEC may use polar coding. One or more symbols spanned by the PBCH may include or carry one or more DM-RS 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 radio device to the base station. The PBCH may include an MIB used to transmit / transmit one or more parameters to the radio device. The MIB can find the remaining minimum system information (RSSI) used by the radio device and associated with the cell. The RMSI may include system information block type 1 (SIB1). The SIB1 may include information for the radio device to access the cell. The radio device 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 parameters provided / included in the MIB. A PBCH can indicate the absence of SIB1. For example, based on the PBCH indicating the absence of SIB1, a wireless device may point to a frequency. The wireless device may then search the SS / PBCH block at the frequency to which it is directed.

[0091] A wireless device may assume that one or more SS / PBCH blocks transmitted / transmitted with the same SS / PBCH block index are quasi-collocated (QCL-ified) (e.g., have substantially the same / similar Doppler spread, Doppler shift, mean gain, mean delay, and / or spatial Rx parameters). The wireless device does not have to assume QCL for SS / PBCH block transmissions with different SS / PBCH block indices. An SS / PBCH block (e.g., a block within a half-frame) may be transmitted / transmitted in a spatial direction (e.g., using different beams across the coverage area of ​​a cell). A first SS / PBCH block may be transmitted / transmitted in a first spatial direction using a first beam, a second SS / PBCH block may be transmitted / transmitted in a second spatial direction using a second beam, a third SS / PBCH block may be transmitted / transmitted in a third spatial direction using a third beam, and a fourth SS / PBCH block may be transmitted / transmitted in a fourth spatial direction using a fourth beam.

[0092] A base station may transmit / transmit multiple SS / PBCH blocks, for example, within the carrier frequency span. The first PCI of the first SS / PBCH block of the multiple SS / PBCH blocks may be different from the second PCI of the second SS / PBCH block of the multiple SS / PBCH blocks. The PCIs of SS / PBCH blocks transmitted / transmitted at different frequency positions may be different or substantially identical.

[0093] CSI-RS can be transmitted / transmitted by a base station and used by a radio device to obtain / acquire / determine channel status information (CSI). A base station may configure a radio device with one or more CSI-RS for channel estimation or any other appropriate purpose. A base station may configure a radio device with one or more identical / similar CSI-RS. A radio device may measure one or more CSI-RS. A radio device may estimate the downlink channel status and / or generate a CSI report, for example, based on measurements of one or more downlink CSI-RS. A radio device may transmit / transmit CSI reports to a base station (e.g., based on periodic CSI reports, semi-persistent CSI reports, and / or irregular CSI reports). A base station may perform link fitting using feedback provided by the radio device (e.g., estimated downlink channel status).

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

[0095] A base station may configure a radio device to report CSI measurements. A base station may configure a radio device to provide CSI reports periodically, irregularly, or semi-permanently. For periodic CSI reports, a radio device may be configured with multiple CSI report sets based on timing and / or periodicity. For non-periodic CSI reports, a base station may request a CSI report. A base station may instruct a radio device to measure configured CSI-RS resources and provide a CSI report related to the measurements. For semi-persistent CSI reports, a base station may configure a radio device to periodically transmit / transmit and selectively activate or deactivate periodic reports (e.g., via one or more activate / deactivate MAC CEs and / or one or more DCIs). A base station may configure a radio device with a CSI-RS resource set and CSI reports using, for example, RRC signaling.

[0096] A CSI-RS configuration may include one or more parameters, for example, indicating up to 32 antenna ports (or any other number of antenna ports). A wireless device may be configured to use / adopt the same OFDM symbols for downlink CSI-RS and CORESET, for example, when downlink CSI-RS and CORESET are spatially QCL-ified and the resource elements associated with downlink CSI-RS are outside the physical resource block (PRB) configured for CORESET. A wireless device may be configured to use / adopt the same OFDM symbols for downlink CSI-RS and SS / PBCH blocks, for example, when downlink CSI-RS and SS / PBCH blocks are spatially QCL-ified and the resource elements associated with downlink CSI-RS are outside the PRB configured for SS / PBCH blocks.

[0097] Downlink DM-RS can be transmitted / transmitted by a base station and received / used by a radio device for channel estimation. Downlink DM-RS can be used for coherent demodulation of one or more downlink physical channels (e.g., PDSCHs). A network (e.g., an NR network) may support one or more variable and / or configurable DM-RS patterns for data demodulation. At least one downlink DM-RS configuration may support a frontloaded DM-RS pattern. Frontloaded DM-RS can be mapped onto one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). A base station may semi-statically configure a radio device with a number / quantity (e.g., maximum number / quantity) of frontloaded DM-RS symbols on a PDSCH. A DM-RS configuration may support one or more DM-RS ports. A DM-RS configuration may support up to eight orthogonal downlink DM-RS ports per radio device (e.g., for a single user MIMO). A DM-RS configuration may support up to four orthogonal downlink DM-RS ports per radio device (e.g., for multi-user MIMO). A radio network may support a common DM-RS structure for downlink and uplink (e.g., for at least CP-OFDM). DM-RS locations, DM-RS patterns, and / or scramble arrays may be identical or different. A base station may transmit / transmit downlink DM-RS and the corresponding PDSCH using, for example, the same precoding matrix. A radio device may use one or more downlink DM-RS for coherent demodulation / channel estimation of the PDSCH.

[0098] A transmitter (e.g., a base station transmitter) may use a precoder matrix for a portion of the transmission bandwidth. 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, for example, based on the first bandwidth being different from the second bandwidth. A wireless device may assume that the same precoder matrix is ​​used across a set of PRBs. A set of PRBs can be determined / suggested / identified / represented as a precoder resource block group (PRG).

[0099] A PDSCH may include one or more layers. A radio device may assume that at least one symbol having a DM-RS exists on one or more layers of the PDSCH. The upper layers may constitute one or more DM-RS relative to the PDSCH (e.g., up to three DMRS relative to the PDSCH). Downlink PT-RS may be transmitted / transmitted by a base station and may be used by a radio device, for example, for phase noise compensation. Whether downlink PT-RS exists may depend on the RRC configuration. The presence and / or pattern of downlink PT-RS is configured using associations with one or more parameters used / adopted for one or more purposes, for example, a combination of RRC signaling and / or for other purposes (e.g., modulation and coding scheme (MCS)), based on radio device-specific criteria, which may be indicated by DCI. The dynamic presence of downlink PT-RS may be associated with one or more DCI parameters, including at least MCS, if configured. A network (e.g., an NR network) may support multiple PT-RS densities defined in the time and / or frequency domain. The frequency domain density (configuration / if any) may be associated with at least one configuration of the planned bandwidth. A wireless device may assume the same precoding for DM-RS ports and PT-RS ports. The number of PT-RS ports may be less than the number of DM-RS ports in the planned resources. Downlink PT-RS may be configured / allocated / limited to the wireless device for a planned time / frequency duration. Downlink PT-RS may be transmitted / transmitted via symbols, for example, to facilitate phase tracking at the receiver.

[0100] A wireless device may transmit / transmit uplink DM-RS to a base station, for example, for channel estimation. A base station may use uplink DM-RS for coherent demodulation of one or more uplink physical channels. A wireless device may transmit / transmit uplink DM-RS on PUSCH and / or PUCCH. Uplink DM-RS may span frequency ranges similar to the frequency range associated with the corresponding physical channel. A base station may configure a wireless device with one or more uplink DM-RS configurations. At least one DM-RS configuration may support a front-loaded DM-RS pattern. Front-loaded DM-RS may be mapped onto one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). One or more uplink DM-RS may be configured to transmit / transmit on one or more symbols of PUSCH and / or PUCCH. A base station may semi-statically configure a radio device with a number / quantity (e.g., maximum number / quantity) of front-loaded DM-RS symbols for PUSCH and / or PUCCH that the radio device can use to schedule single-symbol DM-RS and / or double-symbol DM-RS. A network (e.g., an NR network) may support a common DM-RS structure for downlink and uplink (e.g., for cyclic prefix orthogonal frequency division multiplexing (CP-OFDM)). The DM-RS locations, DM-RS patterns, and / or DM-RS scramble arrangements may be substantially identical or different.

[0101] PUSCH may include one or more layers. A wireless device may transmit / transmit at least one symbol using DM-RS present on one or more layers of PUSCH. The upper layers may constitute one or more DM-RS (e.g., up to three DMRS) relative to PUSCH. Uplink PT-RS (which may be used by the base station for phase tracking and / or phase noise compensation) may or may not be present, for example, depending on the RRC configuration of the wireless device. The presence and / or pattern of uplink PT-RS may be configured on a wireless device-specific base (e.g., UE-specific base) by a combination of one or more parameters configured / adopted for, for example, RRC signaling and / or other purposes (e.g., MCS), which may be indicated by DCI. The dynamic presence of uplink PT-RS, if configured, may be associated with one or more DCI parameters, including at least MCS. A wireless network may support multiple uplink PT-RS densities defined in the time / frequency domain. The frequency domain density (if configured / present) may be associated with at least one configuration of the planned bandwidth. A wireless device may assume the same precoding for DM-RS and PT-RS ports. The number of PT-RS ports may be less than the number of DM-RS ports in the allocated resources. Uplink PT-RS may be configured / allocated / limited for the wireless device for a predetermined time / frequency duration.

[0102] One or more SRSs may be transmitted / transmitted by a radio device to a base station for channel state estimation, for example, to support uplink channel-dependent scheduling and / or link fitting. SRS transmitted / transmitted by a radio device may enable / enable the base station to estimate the uplink channel state at one or more frequencies. The base station scheduler may use / adopt the estimated uplink channel state to allocate one or more resource blocks for uplink push transmissions for the radio device. A base station may semi-statically configure a radio device with one or more SRS resource sets. In the case of an SRS resource set, a base station may configure a radio device with one or more SRS resources. SRS resource set applicability may be configured, for example, by higher-layer (e.g., RRC) parameters. SRS resources within one or more SRS resource sets (e.g., having identical / similar time-domain behavior, periodic, aperiodic, and / or homogeneous) may be transmitted / transmitted instantaneously (e.g., simultaneously), for example, when higher-layer parameters indicate beam management. A wireless device may transmit / transmit one or more SRS resources within an SRS resource set. A network (e.g., an NR network) may support aperiodic, periodic, and / or semi-persistent SRS transmissions. A wireless device may transmit / transmit SRS resources based, for example, one or more trigger types. One or more trigger types may include upper-layer signaling (e.g., RRC) and / or one or more DCI formats. At least one DCI format may be used / adopted for a wireless device to select at least one of one or more configured SRS resource sets. SRS trigger type 0 may refer to an SRS triggered based on upper-layer signaling. SRS trigger type 1 may refer to an SRS triggered based on one or more DCI formats. A wireless device may be configured to transmit / transmit an SRS after a PUSCH and its corresponding uplink DM-RS transmission, for example, if a PUSCH and an SRS are transmitted / transmitted in the same slot.A base station can quasi-statistically configure a radio device using one or more SRS configuration parameters that indicate 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, starting OFDM symbol of the SRS resource, SRS bandwidth, frequency-hopping bandwidth, cyclic shift, and / or SRS sequence ID.

[0103] Antenna ports can be determined / defined such that the channel through which a symbol on an antenna port is transmitted can be inferred from the channel through which another symbol on the same antenna port is transmitted. A receiver can infer / determine the channel for carrying a second symbol on an antenna port (e.g., fade gain, multipath delay, and / or similar) from the channel for carrying a first symbol on an antenna port, for example, when a first and second symbol are transmitted / transmitted on the same antenna port. The first and second antenna ports may be said to be roughly located in the same place (QCL) if, for example, one or more large-scale characteristics of the channel through which the first symbol on the first antenna port is transmitted can be inferred from the channel through which the second symbol on the second antenna port is transmitted. 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.

[0104] Channels that use beamforming may require beam management. Beam management may include beam measurement, beam selection, and / or beam display. A beam may be associated with one or more reference signals. A beam may be identified by one or more beamforming reference signals. A wireless device may perform downlink beam measurement and generate a beam measurement report based, for example, one or more downlink reference signals (e.g., CSI-RS). A wireless device may perform a downlink beam measurement procedure after, for example, an RRC connection has been set up with a base station.

[0105] Figure 11B shows an example of mapping one or more CSI-RS. CSI-RS can be mapped in the time domain and the frequency domain. Each rectangular block shown in Figure 11B may correspond to a resource block (RB) within the cell bandwidth. A base station may transmit / transmit one or more RRC messages containing CSI-RS resource configuration parameters that indicate one or more CSI-RS. One or more parameters may be configured by higher-layer signaling for CSI-RS resource configuration (e.g., RRC and / or MAC signaling). One or more parameters may include at least one of the following: CSI-RS resource configuration identity, number of CSI-RS ports, CSI-RS configuration (e.g., location of symbols and resource elements (REs) within a subframe), CSI-RS subframe configuration (e.g., subframe location, offset, and periodicity of radio frames), CSI-RS power parameters, CSI-RS sequence parameters, code division multiplexing (CDM) type parameters, frequency density, transmit 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.

[0106] One or more beams may be configured for a radio device with a configuration specific to that radio device. Three beams are shown in Figure 11B (beam #1, beam #2, and beam #3), but more or fewer beams may be configured. Beam #1 may be assigned to a CSI-RS 1101 that can be transmitted / transmitted on one or more subcarriers of the first symbol of the RB. Beam #2 may be assigned to a CSI-RS 1102 that can be transmitted / transmitted on one or more subcarriers of the second symbol of the RB. Beam #3 may be assigned to a CSI-RS 1103 that can be transmitted / transmitted on one or more subcarriers in the third symbol of the RB. The base station may transmit another CSI-RS associated with a beam for another radio device using other subcarriers in the same RB (e.g., those not used to transmit / transmit CSI-RS 1101), for example by using frequency division multiplexing (FDM). The beam used for a wireless device may be configured, for example, by using time-domain multiplexing (TDM), so that the beam for the wireless device uses different symbols than those used by the beams of other wireless devices. The wireless device may be delivered with a beam of orthogonal symbols (e.g., no overlapping symbols) by using TDM, for example.

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

[0108] A wireless device may determine / evaluate (e.g., measure) the channel quality of one or more beampair links, for example, in a beam management procedure. A beampair link may include the base station's Tx beam and the wireless device's Rx beam. The base station's Tx beam may transmit / transmit downlink signals, and the wireless device's Rx beam may receive downlink signals. Based on the evaluation / determination, the wireless device may transmit / transmit a beam measurement report. The beam measurement report may indicate one or more beampair quality parameters, including one or more beam identifiers (e.g., beam index, reference signal index, or similar), RSRP, precoding matrix indicator (PMI), channel quality indicator (CQI), and / or rank indicator (RI).

[0109] Figure 12A shows an embodiment of a downlink beam management procedure. One or more downlink beam management procedures (e.g., downlink beam management procedures P1, P2, and P3) can be performed. Procedure P1 may enable measurements on the Tx beam of a TRP (or multiple TRPs) (e.g., radio device measurements) (e.g., to support the selection of one or more base station Tx beams and / or radio device Rx beams). The base station Tx beam and the radio device Rx beam are shown as ellipses in the upper and lower rows of P1, respectively. Beamforming (e.g., at a TRP) may include a Tx beam sweep for a set of beams (e.g., a beam sweep shown in the upper rows of P1 and P2 as ellipses rotated counterclockwise, indicated by dashed arrows). Beamforming (e.g., at a radio device) may include an Rx beam sweep for a set of beams (e.g., a beam sweep shown in the lower rows of P1 and P3 as ellipses rotated counterclockwise, indicated by dashed arrows). Procedure P2 may be used to enable measurements on the Tx beam of the TRP (indicated in the upper column of P2 as an ellipse rotated counterclockwise, indicated by a dashed arrow) (e.g., radio device measurements). A radio device and / or base station may perform procedure P1 using, for example, a smaller set of beams than the set of beams used in procedure P2, or a narrower beam than the beams used in procedure P1. Procedure P2 may also be called beam refinement. A radio device may perform procedure P3 for Rx beam determination, for example, by using the same Tx beam of the base station and sweeping the radio device's Rx beam.

[0110] Figure 12B shows an embodiment of an uplink beam management procedure. One or more uplink beam management procedures (e.g., uplink beam management procedures U1, U2, and U3) can be performed. Procedure U1 may be used to enable a base station to perform measurements on the Tx beam of a radio device (e.g., to support the selection of one or more Tx beams of the radio device and / or Rx beams of the base station). The Tx beam of the radio device and the Rx beam of the base station are shown as ellipses in the top row and bottom row of U1, respectively. Beamforming (e.g., in the radio device) may include one or more beam sweeps, e.g., a Tx beam sweep from a set of beams (shown in the bottom rows of U1 and U3 as ellipses rotated in a counterclockwise direction indicated by dashed arrows). Beamforming (e.g., in the base station) may include one or more beam sweeps, e.g., an Rx beam sweep from a set of beams (shown in the top rows of U1 and U2 as ellipses rotated in a counterclockwise direction indicated by dashed arrows). Procedure U2 can be used, for example, to allow a base station to tune its Rx beam when a wireless device (such as a UE) is using a fixed Tx beam. The wireless device and / or base station may perform procedure U2 using, for example, a smaller set of beams than the set of beams used in procedure P1, or a narrower beam than the beam used in procedure P1. Procedure U2 may also be called beam refinement. The wireless device may perform procedure U3 to tune its Tx beam, for example, when the base station is using a fixed Rx beam.

[0111] A wireless device may initiate / start / execute a beam fault recovery (BFR) procedure, for example, based on the detection of a beam fault. A wireless device may transmit / transmit a BFR request (e.g., a preamble, UCI, SR, MAC CE, and / or similar) based on the initiation of a BFR procedure. A wireless device may detect a beam fault, for example, based on the determination that the quality of the beam pair link of the relevant control channel is insufficient (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).

[0112] A wireless device may measure the quality of a beampair link using, for example, one or more reference signals (RS) including one or more SS / PBCH blocks, one or more CSI-RS resources, and / or one or more DM-RS. 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, RSRQ value, and / or CSI values ​​measured on the RS resources. A base station may indicate that an RS resource has been QCL-ified with one or more DM-RS of a channel (e.g., a control channel, a shared data channel, and / or similar). An RS resource and one or more DM-RS of a channel may be QCL-ified if, for example, the channel characteristics transmitted to the wireless device via the RS resource (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 transmitted to the wireless device via the channel.

[0113] A network (e.g., an NR network including gNB and / or ng-eNB) and / or a radio device may initiate / start / execute a random access procedure. A radio device in an RRC idle (e.g., RRC_IDLE) state and / or RRC inactive (e.g., RRC_INACTIVE) state may initiate / execute a random access procedure to request network connection setup. A radio device may initiate / start / execute a random access procedure from an RRC connected (e.g., RRC_CONNECTED) state. A radio device may initiate / start / execute a random access procedure to request uplink resources (e.g., for uplink transmission of an SR if no PUCCH resources are available) and / or obtain / determine uplink timing (e.g., if the uplink synchronization state is asynchronous). A radio device may initiate / start / execute a random access procedure to request one or more System Information Blocks (SIBs) (e.g., other System Information Blocks such as SIB2, SIB3, etc., and / or similar). A wireless device may initiate / start / execute a random access procedure for beam fault recovery requests. A network may initiate / start / execute a random access procedure, for example, to establish time alignment for handover and / or SCell addition.

[0114] Figure 13A shows an embodiment of a four-step random access procedure. The four-step random access procedure may include a four-step competition-based random access procedure. The base station may send / transmit a configuration message 1310 to the radio device, for example, before initiating the random access procedure. The four-step random access procedure may include the transmission of four messages, including a first message (e.g., Msg 1 1311), a second message (e.g., Msg 2 1312), a third message (e.g., Msg 3 1313), and a fourth message (e.g., Msg 4 1314). The first message (e.g., Msg 1 1311) may include a preamble (or random access preamble). The first message (e.g., Msg 1 1311) may be called a preamble. The second message (e.g., Msg 2 1312) may include a random access response (RAR). The second message (for example, Msg 2 1312) may be called RAR.

[0115] Configuration message 1310 may be transmitted / 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 a radio device. 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). A base station may transmit / transmit (e.g., broadcast or multicast) one or more RRC messages to one or more radio devices. One or more RRC messages may be radio device-specific. One or more radio device-specific RRC messages may be dedicated RRC messages transmitted / transmitted to radio devices in an RRC connected state (e.g., RRC_CONNECTED) and / or RRC inactive state (e.g., RRC_INACTIVE). A wireless device may determine the time-frequency resources and / or uplink transmit power for transmitting a first message (e.g., Msg 1 1311) and / or a third message (e.g., Msg 3 1313) based on one or more RACH parameters. The wireless device may, for example, determine the time-frequency resources and / or uplink transmit power for transmitting a second message (e.g., Msg 3 1313) based on one or more RACH parameters. The reception timing and downlink channel for receiving messages 2 (1312) and the fourth message (e.g., Msg 4 1314) can be determined.

[0116] One or more RACH parameters provided / configured / included in configuration message 1310 may indicate one or more physical RACH (PRACH) opportunities available for sending the first message (e.g., Msg 1 1311). One or more PRACH opportunities may be predefined (e.g., by a network including one or more base stations). 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. One or more RACH parameters may indicate the quantity / number of SS / PBCH blocks mapped to PRACH opportunities and / or the quantity / number of preambles mapped to SS / PBCH blocks.

[0117] One or more RACH parameters provided / configured / included in configuration message 1310 may be used to determine the uplink transmit power for the first message (e.g., Msg 1 1311) and / or the third message (e.g., Msg 3 1313). One or more RACH parameters may indicate the reference power for preamble transmission (e.g., the received target power and / or the initial power for preamble transmission). One or more power offsets may be indicated by one or more RACH parameters. One or more RACH parameters may indicate the power ramping step, the power offset between the SSB and CSI-RS, the power offset between the transmission of the first message (e.g., Msg 1 1311) and the third message (e.g., Msg 3 1313), and / or the power offset values ​​between preamble groups. One or more RACH parameters may indicate one or more thresholds, for example, based on the fact that the wireless device can determine at least one reference signal (e.g., SSB and / or CSI-RS) and / or uplink carriers (e.g., a normal uplink (NUL) carrier and / or a complementary uplink (SUL) carrier).

[0118] The first message (e.g., Msg 1 1311) may include one or more preamble transmissions (e.g., a preamble transmission and one or more preamble retransmissions). The RRC message may be used to constitute one or more preamble groups (e.g., group A and / or group B). A preamble group may include one or more preambles. The wireless device may determine the preamble group based, for example, on the size of a path loss measurement and / or a third message (e.g., Msg 3 1313). The wireless device may measure the RSRP of one or more reference signals (e.g., SSB and / or CSI-RS) and determine at least one reference signal having an RSRP exceeding an RSRP threshold (e.g., rsrp-ThresholdSSB and / or rsrp-ThresholdCSI-RS). The wireless device may select at least one preamble to be associated with one or more reference signals and / or a selected preamble group, for example, if the association between one or more preambles and at least one reference signal is constituted by the RRC message.

[0119] A wireless device may determine the preamble based on one or more RACH parameters provided / configured / included in, for example, configuration message 1310. The wireless device may also determine the preamble based on, for example, path loss measurement, RSRP measurement, and / or a third message (e.g., Msg The preamble can be determined based on the size of 3 1313). One or more RACH parameters may indicate the preamble format, the maximum quantity / number of preamble transmissions, and / or one or more thresholds for determining one or more preamble groups (e.g., group A and group B). A base station can use one or more RACH parameters to configure a radio device having associations between one or more preambles and one or more reference signals (e.g., SSB and / or CSI-RS). The radio device can determine the preamble, for example, based on the association if the association is configured, so that it is included in a first message (e.g., Msg 1 1311). The first message (e.g., Msg 1 1311) can be transmitted / transmitted to the base station via one or more PRACH opportunities. The radio device can 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.

[0120] A wireless device may perform a preamble retransmission if no response is received (e.g., subsequently or in response to) a preamble transmission, for example (e.g., a monitoring window for monitoring RAR). The wireless device may increase the uplink transmit power for preamble retransmission. The wireless device may select an initial preamble transmit power based, for example, on a target received preamble power configured by path loss measurement and / or the network. The wireless device may decide to retransmit / re-transmit the preamble and ramp up the uplink transmit power. The wireless device may receive one or more RACH parameters (e.g., PREAMBLE_POWER_RAMPING_STEP) indicating a ramping step for preamble retransmission. The ramping step may be the amount of incremental increase in uplink transmit power for retransmission. The wireless device may increase the uplink transmit power if, for example, the wireless device determines the same reference signal (e.g., SSB and / or CSI-RS) as the previous preamble transmission. A wireless device may, for example, use a counter parameter (e.g., PREAMBLE_TRANSMISSION_counter) to count the quantity / number of preamble transmissions and / or retransmissions. A wireless device may determine that a random access procedure has failed, for example, if the quantity / number of preamble transmissions exceeds a threshold configured by one or more RACH parameters (e.g., preambleTransMax) without receiving a success response (e.g., RAR).

[0121] The second message (e.g., Msg 2 1312) (e.g., received by a radio device) may include a RAR. The second message (e.g., Msg 2 1312) may include multiple RARs corresponding to multiple radio devices. The second message (e.g., Msg 2 1312) may be received based on (e.g., subsequently in response to) the transmission of the first message (e.g., Msg 1 1311). The second message (e.g., Msg 2 1312) may be scheduled on the DL-SCH and may be indicated by the PDCCH using, for example, a Random Access Radio Network Temporary Identifier (RA RNTI). The second message (e.g., Msg 2 1312) may indicate that the first message (e.g., Msg 1 1311) was received by a base station. A second message (e.g., Msg 2 1312) may include a time alignment command that can be used by the radio device to adjust the transmission timing of the radio device, a scheduling grant for the transmission of a third message (e.g., Msg 3 1313), and / or a temporary cell RNTI (TC-RNTI). The radio device may, for example, determine / start a time window (e.g., ra-ResponseWindow) to monitor PDCCH for the second message (e.g., Msg 2 1312) after transmitting / transmitting the first message (e.g., Msg 1 1311) (e.g., preamble). The radio device may determine the start time of the time window based on the PRACH opportunity that the radio device uses to transmit / transmit the first message (e.g., Msg 1 1311) (e.g., preamble). A wireless device may initiate a time window after one or more symbols of the last symbol of a first message (e.g., Msg 1 1311) that includes a preamble (e.g., a symbol that marks the completion of the first message (e.g., Msg 1 1311) which includes the transmission of a symbol preamble, or a symbol that is in the first PDCCH opportunity from the end of the preamble transmission). One or more symbols may be determined based on numerology.PDCCH may be mapped to a common search space (e.g., a Type1-PDCCH common search space) composed of RRC messages. A wireless device may identify / determine a RAR, for example, based on an RNTI. A wireless network temporary identifier (RNTI) may be used in response to one or more events that initiate / start a random access procedure. A wireless device may use an RA-RNTI for one or more communications related to random access or any other purpose, for example. An RA-RNTI may be associated with a PRACH opportunity in which the wireless device transmits / transmits a preamble. A wireless device may determine an RA-RNTI, for example, based on at least one of the OFDM symbol index, slot index, frequency domain index, and / or UL carrier indicator of a PRACH opportunity. Embodiments of an RA-RNTI may be determined as follows:

number

[0122] A wireless device may send / transmit a third message (e.g., Msg 3 1313) based on (e.g., subsequently or in response to) the successful reception of a second message (e.g., Msg 2 1312), for example (using the resource identified in Msg 2 1312). The third message (e.g., Msg 3 1313) may be used, for example, for conflict resolution in a conflict-based random access procedure. Multiple wireless devices may send / transmit the same preamble to a base station, and the base station may send / transmit RARs corresponding to the wireless devices. Conflicts may occur, for example, if multiple wireless devices interpret the RAR as corresponding to themselves. Conflict resolution (e.g., using a third message (e.g., Msg 3 1313) and a fourth message (e.g., Msg 4 1314)) may be used to increase the likelihood that a wireless device will not mistakenly use the identity of another wireless device. A wireless device may include a device identifier in a third message (e.g., Msg 3 1313) (e.g., C-RNTI, if assigned, TC RNTI, included in the second message (e.g., Msg 2 1312), and / or any other appropriate identifier) ​​in order to perform conflict resolution, for example.

[0123] A fourth message (e.g., Msg 4 1314) may be received based on (e.g., subsequently or in response to) the transmission of a third message (e.g., Msg 3 1313). The base station may use the C-RNTI to address a radio on the PDCCH (e.g., the base station may send the PDCCH to the radio device), for example, if the C-RNTI was included in the third message (e.g., Msg 3 1313). The random access procedure may be determined to be successful if, for example, the radio device's unique C-RNTI is found on the PDCCH (e.g., the PDCCH is scrambled by the C-RNTI). A fourth message (e.g., Msg 4 1314) may be received using the DL-SCH associated with the TC RNTI if, for example, the TC RNTI is included in the third message (e.g., Msg 3 1313) (e.g., if the radio device is in an RRC idle state (e.g., RRC_IDLE) or otherwise connected to a base station). For example, if the MAC PDU is successfully decoded and the MAC PDU matches the CCCH SDU transmitted / transmitted in the third message (e.g., Msg 3 1313), or otherwise contains a corresponding radio device conflict resolution identity MAC CE, the radio device may determine that conflict resolution was successful and / or that the random access procedure was successfully completed.

[0124] A wireless device may consist of a SUL carrier and / or a NUL carrier. Initial access (e.g., random access) may be supported via the uplink carrier. A base station may configure a wireless device having multiple RACH configurations (e.g., two separate RACH configurations, one for the SUL carrier and the other for the NUL carrier). For random access within a cell consisting of a SUL carrier, the network may indicate which carrier (NUL or SUL) to use. A wireless device may decide to use the SUL carrier, for example, if the measured quality of one or more reference signals (e.g., one or more reference signals associated with the NUL carrier) is lower than the broadcast threshold. Uplink transmission of a random access procedure (e.g., the first message (e.g., Msg 1 1311) and / or the third message (e.g., Msg 3 1313)) may remain on or be transmitted over the selected carrier. A wireless device may switch uplink carriers during a random access procedure (e.g., between Msg 1 1311 and Msg 3 1313). The wireless device may determine and / or switch uplink carriers for a first message (e.g., Msg 1 1311) and / or a third message (e.g., Msg 3 1313) based, for example, on a channel clear evaluation (e.g., listen before talk).

[0125] Figure 13B illustrates a two-step random access procedure. A two-step random access procedure may include a two-step non-conflict random access procedure. Similar to a four-step conflict-based random access procedure, the base station may send / transmit a configuration message 1320 to the radio device before the procedure begins. The configuration message 1320 may be similar in some respects to the configuration message 1310. The procedure shown in Figure 13B involves two messages, a first message (e.g., Msg 1321) and a second message (e.g., Msg 1321). This may include sending the first message (e.g., Msg 1 1321) and the second message (e.g., Msg 2 1322), respectively. The procedure described in 1312) may be similar in some respects. A two-step, contention-free random access procedure does not need to include messages similar to a third message (e.g., Msg 3 1313) and / or a fourth message (e.g., Msg 4 1314).

[0126] A two-step (e.g., no-conflict) random access procedure may be configured / initiated for beam fault recovery, other SI requests, SCell addition, and / or handover. The base station may display or assign to the radio device the preamble used for the first message (e.g., Msg 1 1321). The radio device may receive a display of the preamble (e.g., ra-PreambleIndex) from the base station via PDCCH and / or RRC.

[0127] A radio device may initiate a time window (e.g., ra-ResponseWindow) for monitoring the PDCCH for the RAR based on (e.g., subsequently or in response to) the transmission of a preamble. A base station may configure a radio device with one or more beam fault recovery parameters, including a separate time window and / or a separate PDCCH, in the search space indicated by an RRC message (e.g., recoverySearchSpaceId). A base station may configure one or more beam fault recovery parameters in relation to a beam fault recovery request, for example. A separate time window for monitoring the PDCCH and / or RAR may be configured to begin after the transmission of a beam fault recovery request (e.g., the window may begin any number of symbols and / or slots after the transmission of a beam fault recovery request). A radio device can monitor for PDCCH transmissions addressed to a Cell RNTI (C-RNTI) in the search space. During a two-step (e.g., no-conflict) random access procedure, the wireless device sends / transmits, for example, a first message (e.g., Msg 1 1321) and a corresponding second message (e.g., Msg 2 A radio device may determine that the random access procedure was successful based on (for example, subsequently or in response to) the receipt of 1322). A radio device may determine that the random access procedure was successfully completed if, for example, the PDCCH transmission is addressed to the corresponding C-RNTI. A radio device may determine that the random access procedure was successfully completed if, for example, the radio device receives a RAR containing a preamble identifier corresponding to the preamble transmitted / transmitted by the radio device, and / or the RAR contains a MAC sub-PDU having the preamble identifier. A radio device may determine the response as an acknowledgment of the SI request.

[0128] Figure 13C shows an embodiment of a two-step random access procedure. Similar to the random access procedures shown in Figures 13A and 13B, the base station may send / transmit a configuration message 1330 to the radio device before the procedure begins. The configuration message 1330 may be similar in some respects to the configuration messages 1310 and / or 1320. The procedure shown in Figure 13C may involve sending multiple messages (e.g., two messages, including a first message (e.g., Msg A 1331) and a second message (e.g., Msg B 1332)).

[0129] Msg A 1320 may be transmitted / transmitted by a wireless device via uplink transmission. Msg A 1320 may include one or more transmissions of the preamble 1341 and / or one or more transmissions of the transport block 1342. The transport block 1342 may include content similar to and / or equivalent to the content of a third message (e.g., Msg 3 1313) (e.g., shown in Figure 13A). The transport block 1342 may include UCI (e.g., SR, HARQ ACK / NACK, and / or similar). The wireless device may receive a second message (e.g., Msg B 1332) based on having transmitted / transmitted a first message (e.g., Msg A 1331) (e.g., subsequently in response to it). The second message (e.g., Msg B 1332) may be followed by the second message (e.g., Msg 2 It may include the content of the second message (e.g., Msg 2 1322) (e.g., the RAR shown in Figure 13A), the content of the fourth message (e.g., Msg 4 1314) (e.g., shown in Figure 13A), and / or content similar to and / or equivalent to the second message (e.g., Msg 2 1322) (e.g., the RAR shown in Figure 13B).

[0130] A wireless device may start / initiate a two-step random access procedure (e.g., the two-step random access procedure shown in Figure 13C) for licensed and / or unlicensed spectra. The wireless device may decide whether to start / initiate a two-step random access procedure based on one or more factors. One or more factors may include at least one of the following: the wireless access technology in use (e.g., LTE, NR, and / or similar), whether the wireless device has a valid TA, cell size, the wireless device's RRC status, the spectrum type (e.g., licensed versus unlicensed), and / or any other appropriate factors.

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

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

[0133] Radio devices and base stations may exchange control signaling (e.g., control information). This control signaling may also be called L1 / L2 control signaling and may originate from the PHY layer (e.g., layer 1) and / or MAC layer (e.g., layer 2) of the radio device or base station. The control signaling may include downlink control signaling transmitted from the base station to the radio device and / or uplink control signaling transmitted from the radio device to the base station.

[0134] Downlink control signaling may include at least one of the following: downlink scheduling assignments, uplink scheduling grants indicating uplink radio resources and / or transport format, slot format information, preemption indications, power control commands, and / or other appropriate signaling. A radio device may receive downlink control signaling in a payload transmitted / transmitted by a base station via a PDCCH. The payload transmitted / transmitted via a PDCCH may be called downlink control information (DCI). The PDCCH may be a group-common PDCCH (GC-PDCCH) common to a group of radio devices. The GC-PDCCH may be scrambled by a group-common RNTI.

[0135] A base station may connect one or more cyclic redundancy check (CRC) parity bits to the DCI, for example, to facilitate the detection of transmission errors. If the DCI is intended for a radio device (or group of radio devices), the base station may scramble the CRC parity bits with the radio device identifier (or group of radio devices identifier). 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 the RNTI.

[0136] DCIs can be used for different purposes. The purpose may be indicated by the type of RNTI used to scramble the CRC parity bits. A DCI with scrambled CRC parity bits in a paging RNTI (P-RNTI) may indicate paging information and / or system information change notifications. P-RNTI may be predefined as "FFFE" in hexadecimal. A DCI with scrambled CRC parity bits in a system information RNTI (SI-RNTI) may indicate broadcast transmissions of system information. SI-RNTI may be predefined as "FFFF" in hexadecimal. A DCI with scrambled CRC parity bits in a random access RNTI (RA-RNTI) may indicate random access responses (RARs). A DCI with scrambled CRC parity bits in a cell RNTI (C-RNTI) may indicate unicast transmissions of dynamic schedules and / or triggers for random access in PDCCH sequences. DCI with scrambled CRC parity bits in a temporary cell RNTI (TC-RNTI) can show race resolution (e.g., Msg 3 similar to Msg 31313 shown in Figure 13A). Other RNTI encodings configured by base stations for radio devices include configured scheduling RNTI (CS RNTI), transmit power controlled PUCCH RNTI (TPC PUCCH-RNTI), and transmit power controlled PUCCH This includes RNTI (TPC-PUSCH-RNTI), Transmit Power Controlled SRS RNTI (TPC-SRS-RNTI), Interruption RNTI (INT-RNTI), Slot Format Indication RNTI (SFI-RNTI), Semi-Persistent CSI RNTI (SP-CSI-RNTI), Modulation and Encoding Scheme Cell RNTI (MCS-C RNTI), and / or similar.

[0137] A base station may transmit / transmit DCI in one or more DCI formats, depending on the purpose and / or content of the DCI. DCI format 0_0 may 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 may 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 representation to a group of radio devices. DCI format 2_1 may be used to inform / notify a group of radio devices of a physical resource block and / or OFDM symbol that a group of radio devices may not have intended for that group of radio devices. DCI format 2_2 may be used to send Transmit Power Control (TPC) commands to PUCCH or PUSCH. DCI format 2_3 may be used to send a group of TPC commands for SRS transmission by one or more radio devices. DCI formats for new features may be defined in future releases. DCI formats may have different DCI sizes or may share the same DCI size.

[0138] A base station may process a DCI using channel coding (e.g., polar coding), rate matching, scrambling, and / or QPSK modulation after scrambling the DCI with RNTI. The base station may map the coded and modulated DCI onto resource elements used and / or configured for a PDCCH. The base station may transmit / transmit a DCI via a PDCCH occupying several consecutive control channel elements (CCEs) based, for example, the DCI payload size and / or the base station's coverage. The number of consecutive CCEs (referred to as the aggregation level) may be 1, 2, 4, 8, 16, and / or any other preferred number. A CCE may include a number of resource element groups (REGs) (e.g., 6). A REG may include resource blocks in OFDM symbols. Mapping the coded and modulated DCI onto resource elements may be based on mappings of CCEs and REGs (e.g., CCE-REG mappings).

[0139] Figure 14A shows an embodiment of a CORESET configuration. A CORESET configuration may be for a bandwidth portion or any other frequency band. A base station may transmit / transmit DCIs via PDCCHs on one or more control resource sets (CORESETs). A CORESET may include time-frequency resources on which radio devices attempt to decode DCIs using one or more search spaces. A base station may configure the size and location of the CORESETs in the time-frequency domain. The first CORESET 1401 and the second CORESET 1402 may occur or be set / configured in the first symbol in the slot. The first CORESET 1401 may overlap with the second CORESET 1402 in the frequency domain. The third CORESET 1403 may occur or be set / configured in the third symbol in the slot. The fourth CORESET 1404 may occur or be set / configured in the seventh symbol in the slot. A CORESET can have a different number of resource blocks within the frequency domain.

[0140] Figure 14B shows an example of CCE~REG mapping. CCE~REG mapping can be performed for DCI transmissions via CORESET and PDCCH processing. CCE~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 control channel frequency-selective transmission). A base station may perform different or identical CCE~REG mappings with different CORESETs. A CORESET may be associated with a CCE~REG mapping (e.g., by an RRC configuration). A CORESET may consist of antenna port QCL parameters. The antenna port QCL parameters may indicate DM-RS QCL information for PDCCH reception via a CORESET.

[0141] A base station may transmit / transmit one or more RRC messages to a radio device, which include one or more CORESET and one or more search space set configuration parameters. The configuration parameters may indicate the relationship between the search space set and the CORESET. The search space set may include a set of PDCCH candidates formed by CCEs (e.g., at a given aggregation level). The configuration parameters may indicate at least one of the following: several PDCCH candidates monitored at each aggregation level, PDCCH monitoring periodicity and PDCCH monitoring patterns, one or more DCI formats monitored by the radio device, and / or whether the search space set is a common search space set or a radio device-specific search space set (e.g., a UE-specific search space set). The set of CCEs in a common search space set may be predefined and known to the radio device. The set of CCEs in a radio device-specific search space set (e.g., a UE-specific search space set) may be configured, for example, based on the identity of the radio device (e.g., C-RNTI).

[0142] In Figure 14B, a wireless device may determine the time-frequency resources of a CORESET based on one or more RRC messages. The wireless device may determine the CCE~REG mapping of a CORESET (e.g., interleaved or non-interleaved, and / or mapping parameters) based on, for example, the configuration parameters of a CORESET. The wireless device may determine several (e.g., up to 10) search space sets configured on / for a CORESET based on, for example, one or more RRC messages. The wireless device may monitor a set of PDCCH candidates according to the configuration parameters of the search space sets. The wireless device 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 contents of one or more PDCCH candidates in possible (or configured) PDCCH locations, possible (or configured) PDCCH formats (e.g., the number of CCEs, the number of PDCCH candidates in a common search space, and / or the number of PDCCH candidates in a radio device-specific search space), and possible (or configured) DCI formats. Decoding may be referred to as blind decoding. The radio device may determine that the DCI is valid for the radio device based on (e.g., a CRC check, such as a scrambled bit of the CRC parity bit of the DCI matching an RNTI value) (e.g., then in response to it). The radio device may process the information contained in the DCI (e.g., scheduling assignments, uplink grants, power control, slot format indications, downlink preemption, and / or similar).

[0143] Uplink control signaling (such as UCI) may be transmitted to the base station. Uplink control signaling may include HARQ acknowledgments for received DL-SCH transport blocks. A radio device may transmit a HARQ acknowledgment, for example, based on (e.g., subsequently in response to) the reception of a DL-SCH transport block. Uplink control signaling may include CSI indicating the channel quality of the physical downlink channel. A radio device may transmit a CSI to the base station. Based on the received CSI, the base station may determine the transmission format parameters for downlink transmission (e.g., multi-antenna and beamforming schemes). Uplink control signaling may include scheduling requests (SRs). A radio device may transmit an SR indicating that uplink data is available for transmission to the base station. A radio device may transmit UCI (e.g., HARQ acknowledgment (HARQ-ACK), CSI report, SR, etc.) via PUCCH or PUSCH. A wireless device may transmit / transmit uplink control signaling via PUCCH using one of several PUCCH formats.

[0144] There may be multiple PUCCH formats (e.g., five PUCCH formats). A wireless device may determine the PUCCH format based, for example, 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. A wireless device may use PUCCH format 0 to transmit / transmit a UCI via a PUCCH resource, for example, if the transmission spans / intercepts 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 several OFDM symbols (e.g., between 4 and 14 OFDM symbols) and may contain two or fewer bits. A wireless device may use PUCCH format 1, for example, if the transmission spans / intercepts 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 wireless device may use PUCCH format 2 if, for example, the transmission spans / intersects one or two symbols and the number of UCI bits is two or more. PUCCH format 3 may occupy several OFDM symbols (e.g., between 4 and 14 OFDM symbols) and may contain more than two bits. A wireless device may use PUCCH format 3 if, for example, the transmission is four or more symbols, the number of UCI bits is two or more, and the PUCCH resource does not contain orthogonal cover codes (OCCs). PUCCH format 4 may occupy several OFDM symbols (e.g., between 4 and 14 OFDM symbols) and may contain more than two bits. A wireless device may use PUCCH format 4 if, for example, the transmission is four or more symbols, the number of UCI bits is two or more, and the PUCCH resource contains OCCs.

[0145] A base station may transmit / transmit configuration parameters to a radio device of multiple PUCCH resource sets, for example, using RRC messages. Multiple PUCCH resource sets (e.g., up to 4 sets in NR, or up to any other number of sets in other systems) 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 several (e.g., up to a maximum number) UCI ​​information bits that a radio device can transmit using one of the multiple PUCCH resources in the PUCCH resource set. If a radio device consists of multiple PUCCH resource sets, it may select one of the multiple PUCCH resource sets, for example, based on the total bit length of the UCI information bits (e.g., HARQ-ACK, SR, and / or CSI). For example, a radio device may select the first PUCCH resource set whose PUCCH resource set index is equal to "0" if the total bit length of the UCI information bits is 2 or less. If the wireless device, for example, has a total bit length of UCI information bits greater than 2 and equal to or less than the first configuration value, it may select a second PUCCH resource set with a PUCCH resource set index equal to "1". If the wireless device, for example, has a total bit length of UCI information bits greater than the first configuration value and less than or equal to the second configuration value, it may select a third PUCCH resource set with a PUCCH resource set index equal to "2". If the wireless device, for example, has a total bit length of UCI information bits greater than the second configuration value and less than or equal to the third value (e.g., 1406, 1706, or any other number of bits), it may select a fourth PUCCH resource set with a PUCCH resource set index equal to "3".

[0146] A wireless device may, for example, determine a PUCCH resource set from multiple PUCCH resource sets, and then determine a PUCCH resource from the PUCCH resource set for UCI (HARQ-ACK, CSI, and / or SR) transmission. A wireless device may determine a PUCCH resource based on a PUCCH resource indicator in a DCI (e.g., in DCI format 1_0 or DCI format 1_1) received over / via a PDCCH. An n-bit (e.g., 3-bit) PUCCH resource indicator in a DCI may indicate one of several (e.g., eight) PUCCH resources in a PUCCH resource set. A wireless device may, for example, transmit / transmit UCI (HARQ-ACK, CSI, and / or SR) using the PUCCH resource indicated by the PUCCH resource indicator in the DCI, based on the PUCCH resource indicator.

[0147] Figure 15A shows an example of communication between a wireless device and a base station. The wireless device 1502 and base station 1504 may be part of a communication network, such as the communication network 100 shown in Figure 1A, the communication network 150 shown in Figure 1B, or other communication networks. The communication network may include two or more wireless devices and / or two or more base stations having substantially the same or similar configuration as shown in Figure 15A.

[0148] 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 may be called downlink. The communication direction from radio device 1502 to base station 1504 over air interface may be called uplink. Downlink transmissions may be separated from uplink transmissions using, for example, various duplication schemes (e.g., FDD, TDD, and / or some combination of duplication techniques).

[0149] For downlink, data transmitted from base station 1504 to radio device 1502 may be provided / transmitted / reported to processing system 1508 of base station 1504. The data may be provided / transmitted / reported to processing system 1508 by, for example, the core network. For uplink, data transmitted from radio device 1502 to base station 1504 may be provided / transmitted / reported to processing system 1518 of radio device 1502. Processing systems 1508 and 1518 may process the data for transmission by implementing Layer 3 and Layer 2 OSI functions. Layer 2 may include, for example, the SDAP layer, PDCP layer, RLC layer, and MAC layer as described with respect to Figures 2A, 2B, 3, and 4A. Layer 3 may include, for example, the RRC layer as described with respect to Figure 2B.

[0150] Data transmitted to the wireless device 1502 may, for example, be processed by the processing system 1508 and then provided / transmitted to the transmission processing system 1510 of the base station 1504. Data transmitted to the base station 1504 may, for example, be processed by the processing system 1518 and then provided / transmitted to the transmission processing system 1520 of the wireless device 1502. The transmission processing systems 1510 and 1520 may implement the OSI functions of layer 1. Layer 1 may include, for example, the PHY layer described 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.

[0151] The receiving processing system 1512 of base station 1504 may receive uplink transmissions from radio device 1502. The receiving processing system 1512 of base station 1504 may include one or more TRPs. The receiving processing system 1522 of radio device 1502 may receive downlink transmissions from base station 1504. The receiving processing system 1522 of radio device 1502 may include one or more antenna panels. Receiving processing systems 1512 and 1522 may implement OSI functions of layer 1. Layer 1 may include, for example, the PHY layer described 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.

[0152] The base station 1504 may include multiple antennas (e.g., multiple antenna panels, multiple TRPs, etc.). The wireless device 1502 may include multiple antennas (e.g., multiple antenna panels, etc.). Multiple antennas may be used to implement one or more MIMO or multi-antenna techniques such as spatial multiplexing (e.g., single-user MIMO or multi-user MIMO), transmit / receive diversity, and / or beamforming. The wireless device 1502 and / or the base station 1504 may have a single antenna.

[0153] 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, respectively, to perform one or more functions (e.g., one or more functions described herein, and other functions of a general computer, processor, memory, and / or other peripheral device). Transmitting processing system 1510 and / or receiving processing system 1512 may be coupled to memory 1514 and / or another memory (e.g., one or more non-temporary computer-readable media) that stores computer program instructions or code that can be executed to perform one or more of their respective functions. The transmission processing system 1520 and / or the reception processing system 1522 may be coupled to memory 1524 and / or another memory (e.g., one or more non-temporary computer-readable media) that stores computer program instructions or code that can be executed to perform one or more of their respective functions.

[0154] 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 wireless devices 1502 and / or base stations 1504 to operate in a wireless environment.

[0155] The processing system 1508 may be connected to one or more peripheral devices 1516. The processing system 1518 may be connected to one or more peripheral devices 1526. 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). The processing system 1508 and / or the processing system 1518 may receive input data (e.g., user input data) from one or more peripheral devices 1516 and / or one or more peripheral devices 1526, and / or provide output data (e.g., user output data) to them. The processing system 1518 of the wireless device 1502 may receive power from a power source and / or may be configured to distribute power to other components of 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 may be connected to a global positioning system (GPS) chipset 1517. The processing system 1518 may be connected to a global positioning system (GPS) chipset 1527. The GPS chipset 1517 and the GPS chipset 1527 may be configured to determine and provide geographical location information for the wireless device 1502 and the base station 1504, respectively.

[0156] Figure 15B shows exemplary elements of a computing device that may be used to implement any of the various devices described herein, including, for example, base stations 160A, 160B, 162A, 162B, 220, and / or 1504, radio devices 106, 156A, 156B, 210, and / or 1502, or any other base stations, radio devices, AMFs, UPFs, network devices, or computing devices described herein. The computing device 1530 may include one or more processors 1531 capable of executing instructions stored in random access memory (RAM) 1533, removable media 1534 (such as a Universal Serial Bus (USB) drive, a compact disk (CD) or digital multipurpose disk (DVD), or a floppy disk drive), or any other desired storage medium. Instructions may also be stored in an attached (or internal) hard drive 1535. The computing device 1530 may also include a security processor (not shown) capable of executing instructions for one or more computer programs to monitor processes running on the processor 1531 and any processes requesting access to any hardware and / or software components of the computing device 1530 (e.g., ROM 1532, RAM 1533, removable media 1534, hard drive 1535, device controller 1537, network interface 1539, GPS 1541, Bluetooth interface 1542, WiFi interface 1543, etc.). The computing device 1530 may also include one or more output devices such as a display 1536 (e.g., a screen, display device, monitor, television, etc.) and one or more output device controllers 1537 such as a video processor. There may also be one or more user input devices 1538 such as a remote control, keyboard, mouse, touchscreen, microphone, etc.The computing device 1530 may also include one or more network interfaces, such as a network interface 1539, which may be a wired interface, a wireless interface, or a combination of both. The network interface 1539 may provide an interface for the computing device 1530 to communicate with a network 1540 (e.g., a RAN, or any other network). The network interface 1539 may include a modem (e.g., a cable modem), and the external network 1540 may include a communication link, an external network, a home network, a provider's wireless, coaxial, fiber, or hybrid fiber / coaxial distribution system (e.g., a DOCSIS network), or any other desired network. Furthermore, the computing device 1530 may include a location detection device, such as a global positioning system (GPS) microprocessor 1541, which may be configured to receive and process global positioning signals and determine the geographical location of the computing device 1530 with possible assistance from external servers and antennas.

[0157] Figure 15B may show a hardware configuration, but the components shown may also be implemented as software. Modifications may be made to add, remove, combine, or split components of the computing device 1530, if desired. Furthermore, components may be implemented using basic computing devices and components, and the same components (e.g., processor 1531, ROM storage 1532, display 1536, etc.) may be used to implement any of the other computing devices and components described herein. For example, the various components described herein may be implemented using a computing device having components such as a processor that executes computer-executable instructions stored in a computer-readable medium, as shown in Figure 15B. Some or all of the entities described herein may be software-based and may coexist on a common physical platform (e.g., a requesting entity may be a separate software process and program from a dependent entity, both of which may run as software on a common computing device).

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

[0159] 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, CP-OFDM baseband signal (or any other baseband signal) relative to an antenna port and / or complex-valued physical random access channel (PRACH) baseband signal. Filtering may be performed / adopted, for example, before transmission.

[0160] Figure 16C shows an exemplary structure for downlink transmission. Processing of the baseband signal representing the physical downlink channel may include / perform one or more functions. These one or more functions may include scrambling of encoded bits in a codeword to be transmitted / transmitted over / through 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 of the complex-valued modulation symbol on layers for transmission over antenna ports, mapping of the complex-valued modulation symbol to resource elements at antenna ports, generating a complex-valued time-domain OFDM signal for each antenna port, and / or similar. These functions are embodiments for downlink transmission, and other mechanisms may be implemented.

[0161] Figure 16D shows an 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 to an antenna port or any other signal. Filtering may be performed / applied, for example, before transmission.

[0162] 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., a primary cell, one or more 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 PHY, MAC, RLC, PCDP, SDAP, and RRC layers for configuring the wireless device. Configuration parameters may include parameters for configuring PHY and MAC layer channels, bearers, etc. Configuration parameters may include parameters indicating timer values ​​for the PHY, MAC, RLC, PCDP, SDAP, RRC layers, and / or communication channels.

[0163] A timer, for example, can start execution once started and continue execution until it is stopped or expires. A timer can be started when it is not running, or restarted when it is running. A timer may be associated with a value (for example, a timer may start or restart from a certain value, or start from zero and expire when a value is reached). The duration of a timer cannot be updated until the timer is stopped or expires, for example (e.g., by BWP switching). Timers can be used to measure the time duration / window of a process. It will be understood that there can be multiple ways to enforce one or more timers or other parameters with respect to implementations and / or procedures associated with one or more timers or other parameters. One or more of the multiple ways of enforcing a timer can be used to measure the time duration / window of a procedure. A random access response window timer can be used to measure the time window for receiving a random access response. The time difference between two timestamps can be used, for example, instead of starting a random access response window timer and determining the timer's expiration. A process for measuring a time window can be restarted, for example, when the timer is restarted. Implementation of other embodiments may be configured / provided to restart the measurement of the time window.

[0164] Figure 17 shows an exemplary TCI state update. The TCI state update may include a unified beam update. The radio device 1701 may receive one or more messages (e.g., at time T0). The radio device 1701 may receive one or more messages from a computing device 1702, which may include any computing device described herein (e.g., a base station, a relay node, a radio device, etc.). For example, the radio device 1701 may receive one or more messages from a base station. The radio device 1701 may receive one or more messages from a relay node. The radio device 1701 may receive one or more messages from another radio device (e.g., a TRP, a vehicle, a remote radio head, etc.). One or more messages may include one or more configuration parameters (e.g., configuration parameters at time T0 in Figure 17). One or more configuration parameters may include RRC configuration parameters. One or more configuration parameters may include RRC reconfiguration parameters.

[0165] One or more configuration parameters may be for one or more cells (e.g., multiple cells). One or more cells may include other cells. A cell may be, for example, a serving cell. At least one of the one or more configuration parameters may be for a cell. A cell may be a primary cell (PCell). A cell may be a secondary cell (SCell). A cell may be a secondary cell for / composed of a PUCCH (e.g., a PUCCH SCell). A cell may be, for example, an unlicensed cell operating in an unlicensed band. A cell may be, for example, a licensed cell operating in a licensed band. A cell may operate in a first frequency range (e.g., FR1). FR1 may include, for example, frequency bands below 6 GHz (or any other frequency or frequency range). A cell may operate in a second frequency range (e.g., FR2). FR2 may include, for example, frequency bands from 24 GHz to 52.6 GHz (or any other frequency or frequency range). A cell may operate in a third frequency range (FR3). FR3 may include, for example, the frequency band from 52.6 GHz to 71 GHz (or any other frequency or frequency range). FR3 may include, for example, the frequency band starting at (or exceeding) 52.6 GHz (or any other frequency).

[0166] A wireless device may perform uplink transmissions (e.g., PUSCH, PUCCH, SRS) through / to the cell at a first time and a first frequency. A wireless device may perform downlink receptions (e.g., PDCCH, PDSCH) through / to the cell at a second time and a second frequency. The cell may operate in time-division duplication (TDD) mode. For example, in TDD mode, the first frequency and the second frequency may be the same. The first time and the second time may be different, for example, in TDD mode. The cell may operate in frequency-division duplication (FDD) mode. For example, in FDD mode, the first frequency and the second frequency may be different. For example, in FDD mode, the first time and the second time may be the same. The cell may operate in code-division multiplexing (CDM) mode, for example, where the first frequency and the second frequency may be the same or different, and / or the first time and the second time may be the same or different. The cell may operate in spatial domain multiplexing (SDM) mode, for example, where the first and second frequencies may be the same or different, and / or the first and second times may be the same or different. The cell may operate in one or more of the following modes: TDD mode, FDD mode, CDM mode, and / or SDM mode.

[0167] A wireless device can be in one of several RRC modes. For example, a wireless device can be in RRC connected mode, RRC idle mode, or RRC inactive mode.

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

[0169] One of several BWPs can be either active or inactive. If one of the downlink BWPs is active, the radio device may monitor downlink channels / signals (e.g., PDCCH, DCI, CSI-RS, PDSCH) on / through / on the downlink BWP. If one of the downlink BWPs is active, the radio device may receive PDSCH on / through / for the downlink BWP. If one of the downlink BWPs is inactive, the radio device cannot monitor downlink channels / signals (e.g., PDCCH, DCI, CSI-RS, PDSCH) on / through / for the downlink BWP. If one of the downlink BWPs is inactive, the radio device may stop monitoring (or receiving) downlink channels / signals (e.g., PDCCH, DCI, CSI-RS, PDSCH) on / through / for the downlink BWP. If one or more downlink BWPs are inactive, the radio device cannot receive PDSCH on / through / for the downlink BWP. If one of the downlink BWPs is inactive, the radio device may stop receiving PDSCH on / through / for the downlink BWP.

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

[0171] A wireless device may activate one or more downlink BWPs of a cell. Activating a downlink BWP may include setting (or switching) the downlink BWP as the active downlink BWP of the cell. Activating a downlink BWP may include setting the downlink BWP to an active state. Activating a downlink BWP may include switching the downlink BWP from an inactive state to an active state.

[0172] A wireless device may activate one or more uplink BWPs of a cell. Activating an uplink BWP may include the wireless device setting (or switching to) the uplink BWP as the cell's active uplink BWP. Activating an uplink BWP may include setting the uplink BWP to an active state. Activating an uplink BWP may include switching the uplink BWP from an inactive state to an active state.

[0173] One or more configuration parameters may be for the cell's (active) downlink BWP. At least one of the one or more configuration parameters may be for the cell's downlink BWP.

[0174] One or more configuration parameters may be for the cell's (active) uplink BWP. At least one of the one or more configuration parameters may be for the cell's uplink BWP. One or more configuration parameters may indicate the subcarrier spacing (or numerology) for the downlink BWP. One or more configuration parameters may indicate the subcarrier spacing (or numerology) for the uplink BWP.

[0175] The subcarrier spacing value (for downlink BWP and / or uplink BWP) may be, for example, 15 kHz (μ=0), or any other frequency or frequency range. The subcarrier spacing value may be, for example, 30 kHz (μ=1). The subcarrier spacing value may be, for example, 60 kHz (μ=2). The subcarrier spacing value may be, for example, 120 kHz (μ=3). The subcarrier spacing value may be, for example, 240 kHz (μ=4). The subcarrier spacing value may be, for example, 480 kHz (μ=5). The subcarrier spacing value may be, for example, 960 kHz (μ=6). For example, 480 kHz may be valid / applicable in FR3. For example, 960 kHz may be valid / applicable in FR3. For example, 240 kHz may be valid / applicable in FR3. For example, 120 kHz may be valid / applicable in FR3. Any frequency or range of frequencies may be valid / applicable in any FR(n) (for example, μ may be equal to any value).

[0176] One or more configuration parameters may indicate multiple control resource sets (CORESETs). One or more configuration parameters may indicate multiple CORESETs of a cell's (active) downlink BWP. An (active) downlink BWP may contain multiple CORESETs.

[0177] One or more configuration parameters may indicate multiple CORESET indices / identifiers / indicators (e.g., provided by the higher-level parameter ControlResourceSetId) for multiple CORESETs. Each of the multiple CORESETs may be identified / indicated by its respective CORESET index in the multiple CORESET indices. The first CORESET of the multiple CORESETs may be identified by the first CORESET index in the multiple CORESET indices. The second CORESET of the multiple CORESETs may be identified by the second CORESET index in the multiple CORESET indices.

[0178] One or more configuration parameters may indicate multiple TCI states (provided by higher-level parameters such as PDSCH_Config, PUSCH_Config, PDCCH_Config, PUCCH_Config, etc., provided by tci-StatesToAddModList). One or more configuration parameters may be sent / received in one or more messages 1710 at time T0, as shown in Figure 17. One or more configuration parameters may indicate multiple TCI states of, for example, a cell's downlink BWP. In Figure 17, the multiple TCI states may include TCI state 1, TCI state 2, ..., TCI state M.

[0179] The number of TCI states may be equal to, for example, 128 (e.g., M=128) or any other value. The number of TCI states may be equal to, for example, 64 (e.g., M=64). The number of TCI states may be equal to, for example, 32 (e.g., M=32). The number of TCI states may be based on the capabilities of the wireless device. The wireless device may transmit a capability message (e.g., a UE capability message) indicating the maximum number of TCI states. The number of TCI states indicated by one or more configuration parameters may be less than or equal to the maximum number of TCI states.

[0180] One or more configuration parameters may indicate multiple TCI state indices / identifiers / indicators (e.g., provided by the higher-level parameter TCI-StateId) for multiple TCI states. Each TCI state among multiple TCI states may be identified / indicated by its respective TCI state index among multiple TCI state indices. A first TCI state among multiple TCI states may be identified by a first TCI state index among multiple TCI state indices. A second TCI state among multiple TCI states may be identified by a second TCI state index among multiple TCI state indices.

[0181] Multiple TCI states (or at least one of multiple TCI states) may be for (decoding) PDSCH transmit / receive for / of a cell. One or more configuration parameters may indicate multiple TCI states (or at least one of multiple TCI states) for decoding PDSCH transmit / receive for / of a cell's downlink BWP. One of the multiple TCI states may indicate a quasi-collocation reference signal (e.g., by SourceRs-Info) for / of a DM-RS (or DM-RS antenna port) PDSCH transmit / receive.

[0182] Multiple TCI states (or at least one of multiple TCI states) may be for PDCCH transmit / receive for / of a cell. One or more configuration parameters may indicate multiple TCI states (or at least one of multiple TCI states) for PDCCH transmit / receive for / of a cell's downlink BWP. A TCI state among multiple TCI states may indicate a quasi-collocation reference signal for / of a DM-RS (or DM-RS antenna port) for PDCCH transmit / receive.

[0183] Multiple TCI states (or at least one of multiple TCI states) may be for CSI-RS transmission / reception of / for a cell. One or more configuration parameters may indicate multiple TCI states (or at least one of multiple TCI states) for CSI-RS transmission / reception of / for a cell's downlink BWP. A TCI state among multiple TCI states may indicate a reference signal for quasi-collocation of / for CSI-RS transmission / reception.

[0184] Multiple TCI states (or at least one of multiple TCI states) may be for the transmission of uplink signals (e.g., UCI, dynamic grant PUSCH, configured uplink grant-based PUSCH, SRS, PUCCH, transport block, SR, CSI, HARQ-ACK) via / for / on / the uplink resources of the cell. One or more configuration parameters may indicate multiple TCI states (or at least one of multiple TCI states) for the transmission of uplink signals via / for / on / the uplink resources of the cell's uplink BWP. A wireless device may determine a spatial domain transmit filter / beam for uplink signal transmission based on a reference signal indicated by (or in) one of the multiple TCI states.

[0185] Multiple TCI state pools / groups can contain multiple TCI states. For example, two TCI state pools / groups can contain multiple TCI states. The first of the two TCI state pools can contain multiple downlink TCI states. The second of the two TCI state pools can contain multiple uplink TCI states.

[0186] A (single) TCI state pool / group may contain multiple TCI states. Multiple TCI states may contain multiple downlink TCI states. Multiple TCI states may contain multiple uplink TCI states.

[0187] A wireless device may apply / use multiple downlink TCI states for receiving / decoding (or PDSCH transmission / reception) of transport blocks. A wireless device may use multiple downlink TCI states for receiving / decoding (or PDSCH transmission / reception) of transport blocks scheduled for a cell's downlink BWP. A wireless device may use multiple downlink TCI states for receiving downlink signals (e.g., PDSCH transmission / reception, PDCCH transmission / reception, DCI, transport block, CSI-RS, etc.) via a cell's downlink BWP. For example, a wireless device may not use multiple downlink TCI states (or each TCI state of multiple downlink TCI states) for transmitting uplink signals (e.g., PUSCH transmission, PUCCH transmission, UCI, transport block, SRS, etc.). A TCI state among multiple downlink TCI states may indicate / have / include a reference signal for DM-RS quasi-collocation of downlink signals (e.g., PDSCH / PDCCH transmission / reception). A reference signal can be quasi-collocated with the DM-RS of a downlink signal. A reference signal can be quasi-collocated with the DM-RS of a downlink signal with respect to a quasi-collocation type (e.g., QCL type A, QCL type B, QCL type C, QCL type D, QCL type E, etc.). A TCI state can indicate / include / have a quasi-collocation type with respect to a reference signal. A TCI state among multiple downlink TCI states can indicate a reference signal for a quasi-collocation of a downlink signal (e.g., CSI-RS). Each TCI state among multiple downlink TCI states can indicate its respective reference signal for a quasi-collocation of a downlink signal (e.g., PDSCH / PDCCH transmit / receive). Each TCI state among multiple downlink TCI states can indicate its respective reference signal for a quasi-collocation of a downlink signal (e.g., CSI-RS) receive.

[0188] A wireless device may apply / use multiple uplink TCI states for the transmission (or push transmission) of a transport block. A wireless device may use multiple uplink TCI states for the transmission (or push transmission) of a transport block scheduled / configured for the cell's uplink BWP, for example. A wireless device may use multiple uplink TCI states for the transmission of uplink signals (e.g., push transmission, push transmission, UCI, transport block, SRS, etc.) via the cell's uplink BWP. A wireless device may not use multiple uplink TCI states (or each TCI state of multiple uplink TCI states) for the reception of downlink signals (e.g., PDSCH transmission / reception, PDCCH transmission / reception, DCI, transport block, CSI-RS, etc.). A wireless device may determine the spatial domain transmit filter / beam based on a reference signal indicated by (or in) one of the multiple uplink TCI states for the transmission of an uplink signal. A wireless device can determine its respective spatial domain transmit filter / beam for uplink signal transmission based on a reference signal indicated by (or present in) each of the multiple uplink TCI states. A wireless device can determine its transmit power based on one or more power control parameters (e.g., target received power, closed-loop index, path loss compensation coefficient, alpha, path loss reference signal, etc.) indicated by (or included in, associated with, or mapped to) one or more of the multiple uplink TCI states for uplink signal transmission. A wireless device can determine its respective transmit power based on one or more power control parameters indicated by (or included in, associated with, or mapped to) each of the multiple uplink TCI states for uplink signal transmission.

[0189] A (single) TCI state pool / group may contain multiple TCI states. One or more configuration parameters may indicate joint / common UL / DL TCI state modes and separate UL / DL TCI state modes, for example, based on the number of TCI state pools. One or more configuration parameters may indicate joint / common UL / DL TCI state modes, for example, based on one or more configuration parameters indicating a (single) TCI state pool / group. One or more configuration parameters may indicate separate UL / DL TCI state modes, for example, based on one or more configuration parameters indicating two TCI state pools / groups.

[0190] One or more configuration parameters may include, for example, a TCI type parameter indicating a joint / common UL / DL TCI state mode or a separate UL / DL TCI state mode. The TCI type parameter may be set to "joint" or "joint UL / DL TCI state" to indicate a joint / common UL / DL TCI state mode. The TCI type parameter may be set to "separated" or "separated UL / DL TCI state" to indicate a separate UL / DL TCI state mode.

[0191] Multiple TCI states may be / include multiple common / joint TCI states (or multiple common / joint uplink and downlink TCI states). A wireless device may use multiple common / joint TCI states for receiving downlink signals (e.g., PDSCH, PDCCH, CSI-RS, DCI, transport block, etc.) over a cell's downlink BWP. A wireless device may use multiple common / joint TCI states for transmitting uplink signals (e.g., PUSCH, PUCCH, UCI, transport block, SRS, etc.) over a cell's uplink BWP. A wireless device may use each TCI state of multiple common / joint TCI states for receiving downlink signals and transmitting uplink signals. The TCI states of multiple TCI states (or multiple common / joint TCI states) may indicate a reference signal for quasi-collocation of DM-RS for / for downlink signals (e.g., PDSCH / PDCCH transmit / receive). Multiple TCI states (or multiple common / joint TCI states) may indicate a reference signal for quasi-collocation for / to the reception of downlink signals (e.g., CSI-RS). Each TCI state (or multiple common / joint TCI states) may indicate its respective reference signal for quasi-collocation for / to DM-RS of downlink signals (e.g., PDSCH / PDCCH transmit / receive). Each TCI state (or multiple common / joint TCI states) may indicate its respective reference signal for quasi-collocation for / to the reception of downlink signals (e.g., CSI-RS). A wireless device may determine a spatial domain transmit filter / beam for uplink signal transmission based on the reference signal indicated by (or in) one of the multiple TCI states (or multiple common / joint TCI states). A wireless device may determine its respective spatial domain transmit filter / beam for uplink signal transmission based on a reference signal indicated by (or in) each of multiple TCI states (or multiple common / joint TCI states).

[0192] One or more configuration parameters may not indicate one or more TCI states of a cell's downlink BWP. One or more TCI state parameters / configurations may not exist in one or more configuration parameters. One or more configuration parameters may not include one or more TCI state parameters / configurations in / for a cell's downlink BWP. One or more configuration parameters may indicate multiple TCI states for, for example, a reference cell's reference BWP (e.g., a reference downlink BWP). Multiple cells may include the reference cell. A wireless device may apply / use (or associate) multiple TCI states of the reference cell's reference BWP to a cell's downlink BWP. One or more configuration parameters may indicate the reference cell's reference BWP in order to apply / use multiple TCI states of (or may associate with) the reference cell's reference BWP to a cell (or a cell's downlink BWP).

[0193] A wireless device may receive an activation command 1720 as shown in Figure 17. The activation command may be transmitted / received in one or more messages (e.g., activation / deactivation of the DCI, MAC-CE, and UE-specific MAC CE TCI states at time T1 in Figure 17, activation command) indicating the activation of a subset of multiple TCI states. The activation command may activate / select / display / update a subset of multiple TCI states. A subset of multiple TCI states may include, for example, one or more TCI states of a plurality of TCI states. A subset of multiple TCI states may include, for example, a first plurality of TCI states of a plurality of TCI states. For example, in Figure 17, the subset of multiple TCI states is TCI state 4, TCI state 5, TCI state 8, TCI state 26, TCI state 61, and TCI state 42.

[0194] An activation command may include one or more fields that indicate / contain at least one TCI state index that identifies / indicates / identifies a subset of multiple TCI states. Multiple TCI state indices may contain at least one TCI state index. Each TCI state in a subset of multiple TCI states may be identified / indicated by its respective TCI state index of at least one TCI state index. One or more fields may be set to a value (e.g., 1) indicating the activation of a subset of multiple TCI states. Based on one or more fields indicating that a subset of multiple TCI states is set to a value, a wireless device may activate a subset of multiple TCI states. A wireless device may activate a subset of multiple TCI states, for example, based on receiving an activation command that activates / selects / indicates / updates a subset of multiple TCI states.

[0195] A wireless device may map a subset of multiple TCI states to one or more TCI code points (e.g., 000, 001, ..., 110, and 011 in the TCI code point in Figure 17). Mapping a subset of multiple TCI states to one or more TCI code points may include grouping the subset of multiple TCI states in / within one or more TCI code points. Each TCI code point in one or more TCI code points may contain / represent each of the TCI states of the subset of multiple TCI states. For example, in Figure 17, TCI state 4 may be mapped to TCI code point 000, TCI states 5 and 8 may be mapped to TCI code point 001, TCI states 26 and 61 may be mapped to TCI code point 110, and TCI state 42 may be mapped to TCI code point 111. Each TCI code point in one or more TCI code points may be equal to the value of a TCI field in DCI. A DCI may or may not schedule transport blocks (e.g., PDSCH, PUSCH). A TCI field within a DCI may indicate (or be equivalent to) one or more TCI code points. A TCI code point may contain / indicate at least one TCI state from a subset of multiple TCI states.

[0196] A subset of multiple TCI states may indicate a reference signal having / for a quasi-collocation type (e.g., QCL type A, QCL type D). A TCI state may not include / indicate a BWP index / ID and / or cell index / ID for the reference signal. A wireless device may assume that the reference signal consists of the downlink BWP of the cell to which the TCI state applies.

[0197] Multiple TCI state subsets may be used to decode PDSCH transmit / receive for / of a cell. An activation command may indicate the activation of multiple TCI state subsets to decode PDSCH transmit / receive for / of a cell's downlink BWP.

[0198] Multiple TCI states may be for the transmission of uplink signals (e.g., UCI, PUSCH transmit, SRS, PUCCH, transport block, SR, CSI, CSI report, HARQ-ACK) on / about / through / the uplink resources of a cell (e.g., PUSCH resource, PUCCH resource, SRS resource). An activation command may indicate the activation of a subset of multiple TCI states for the transmission of uplink signals on / through / for / the uplink resources of a cell's uplink BWP.

[0199] A subset of multiple TCI states may be one or more downlink TCI states. A wireless device may use one or more downlink TCI states for receiving / decoding transport blocks (or PDSCH transmit / receive). A wireless device may use one or more downlink TCI states for receiving / decoding transport blocks (or PDSCH transmit / receive) scheduled / configured for a cell's downlink BWP, for example. A wireless device may use one or more downlink TCI states for receiving downlink signals (e.g., PDSCH, PDCCH, DCI, CSI-RS, transport blocks, etc.) via a cell's downlink BWP, for example.

[0200] A subset of multiple TCI states may be one or more uplink TCI states. A wireless device may use one or more uplink TCI states for transmitting transport blocks (or push transmits). A wireless device may use one or more uplink TCI states for transmitting transport blocks (or push transmits) scheduled / configured to a cell's uplink BWP, for example. A wireless device may use one or more uplink TCI states for transmitting uplink signals (e.g., push, pucch, UCI, transport blocks, SRS, etc.) over a cell's uplink BWP, for example.

[0201] A subset of multiple TCI states may be one or more common / joint TCI states. A wireless device may use one or more common / joint TCI states for receiving downlink signals (e.g., PDSCH, PDCCH, DCI, CSI-RS, transport block, etc.) via a cell's downlink BWP. A wireless device may use one or more common / joint TCI states for transmitting uplink signals (e.g., PUSCH, PUCCH, UCI, transport block, SRS, etc.) via a cell's uplink BWP. For example, a wireless device may use one or more common / joint TCI states for receiving downlink signals via a cell's downlink BWP and for transmitting uplink signals via a cell's uplink BWP.

[0202] A wireless device may receive a downlink signal 1730, as shown in Figure 17. The downlink signal may be transmitted / received in one or more messages. The downlink signal may include date and / or control information (e.g., transport block, PDCCH / PDSCH transmission, CSI-RS, aperiodic CSI-RS, DCI, etc.). The wireless device may receive a downlink signal based on a TCI state of a subset of multiple TCI states, for example. The wireless device may receive a DCI that schedules / triggers the reception / transmission of a downlink signal, for example. A DCI may indicate a dynamic uplink / downlink grant, for example. A DCI may indicate the activation of an SPS PDSCH transmission, for example. The wireless device may receive the downlink signal for / of an SPS PDSCH transmission (e.g., a transport block). A DCI may include a TCI field (or a TCI code point that contains / indicates a TCI state) indicating a TCI state. One or more configuration parameters may indicate / configure / schedule / trigger the transmission / reception of downlink signals (e.g., periodic CSI-RS, PDCCH / PDSCH transmissions, etc.). One or more configuration parameters may include / indicate a TCI field (or a TCI code point containing / indicating a TCI state) indicating a TCI state for the transmission / reception of downlink signals.

[0203] Receiving a downlink signal based on the TCI state may include quasi-collocation of at least one DMRS antenna port of the downlink signal (e.g., PDSCH / PDCCH transmit, transport block) with a reference signal (e.g., CSI-RS, SS / PBCH block, SRS, PUCCH, etc.) indicated by the TCI state. At least one DMRS antenna port of the downlink signal may quasi-collocation with a reference signal with respect to a quasi-collocation type (e.g., QCL Type A, QCL Type B, QCL Type C, QCL Type D, etc.). The TCI state may indicate / include / have a quasi-collocation type. The TCI state may include / have a reference signal index that indicates / identifies the reference signal. One or more configuration parameters may indicate a reference signal index with respect to the TCI state.

[0204] Receiving a downlink signal based on the TCI state may include the quasi-collocation of the downlink signal (e.g., CSI-RS, DM-RS) with a reference signal (e.g., CSI-RS, SS / PBCH block, SRS, PUCCH, etc.) indicated by the TCI state. The downlink signal may be quasi-collocated with the reference signal with respect to the quasi-collocation type (e.g., QCL Type A, QCL Type B, QCL Type C, QCL Type D, etc.). The TCI state may indicate / include / have the quasi-collocation type. The TCI state may include / have a reference signal index that indicates / identifies the reference signal. One or more configuration parameters may indicate the reference signal index with respect to the TCI state.

[0205] Receiving a downlink signal based on the TCI state may include receiving the downlink signal using a spatial domain receiver / receive filter / beam used to receive a reference signal indicated by the TCI state. The spatial domain receiver / receive filter / beam used to receive the downlink signal may be the same (or substantially the same, x-degree interval, x=0, 1, 5, 10, etc.) as the spatial domain receiver / receive filter / beam used to receive the reference signal.

[0206] A wireless device may transmit (e.g., transmit) uplink signals (e.g., transport blocks, PUCCH / PUSCH transmits, SRS, aperiodic SRS, PUCCH, aperiodic PUCCH, UCI, etc.) based on TCI states of a subset of multiple TCI states. A wireless device may receive DCIs that schedule / trigger the transmission of uplink signals, for example. A DCI may indicate, for example, a dynamic uplink / downlink grant. A DCI may indicate the activation of a configured uplink grant (e.g., a configured uplink grant of type 2). A wireless device may transmit (e.g., transmit) uplink signals (transport blocks, etc.) for / of a configured uplink grant. A DCI may include a TCI field (or a TCI code point that contains / indicates a TCI state) indicating a TCI state. One or more configuration parameters may indicate / configure / schedule / trigger the transmission of uplink signals (e.g., periodic SRS, PUCCH / PUSCH transmits, periodic PUCCH, configured uplink grant, etc.). One or more configuration parameters may include / indicate a TCI field (or a TCI code point containing / indicating a TCI state) indicating a TCI state for transmitting uplink signals. One or more configuration parameters indicate the TCI state of a configured uplink grant (e.g., a Type 1 configured uplink grant). A wireless device may transmit (e.g., transmit) for / its uplink signals (e.g., transport blocks) for the configured uplink grant (e.g., a Type 1 configured uplink grant).

[0207] Transmitting an uplink signal based on the TCI state may include transmitting the uplink signal using a spatial domain transmit / transmit filter / beam determined based on a reference signal (e.g., CSI-RS, SS / PBCH block, SRS, PUCCH) indicated by the TCI state. The spatial domain transmit / transmit filter / beam used to transmit the uplink signal may be the same (or substantially the same, x-degree interval, x=0, 1, 5, 10, etc.) as the spatial domain transmit / transmit filter / beam used to transmit the reference signal (e.g., SRS, PUCCH). The spatial domain transmit / transmit filter / beam used to transmit the uplink signal may be the same (or substantially the same, x-degree interval, x=0, 1, 5, 10, etc.) as the spatial domain receive / receive filter / beam used to receive the reference signal (e.g., CSI-RS, SS / PBCH block).

[0208] A wireless device may monitor PDCCH transmissions in / through a CORESET based on the TCI state for DCI. Multiple CORESETs may contain CORESETs. A cell's downlink BWP (or one or more CORESETs in a downlink BWP) may contain CORESETs. A subset of multiple TCI states may contain TCI states. A subset of TCI states may or may not contain TCI states. A wireless device may receive a second activation command indicating the activation of a TCI state for a CORESET. The second activation command may or may not be the same as the activation command (time T1 in Figure 17). Monitoring PDCCH transmissions in a CORESET based on the TCI state may include quasi-collocation of at least one DMRS antenna port of the PDCCH transmission in the CORESET with a reference signal indicated by the TCI state (e.g., CSI-RS, SS / PBCH block, SRS, etc.). At least one DMRS antenna port may be quasi-collocated with a reference signal with respect to a quasi-collocation type (e.g., QCL Type A, QCL Type B, QCL Type C, QCL Type D, etc.). The TCI state may indicate / include / have a quasi-collocation type.

[0209] The number of one or more TCI code points may be equal to 1. One or more TCI code points may be a (single) TCI code point. A (single) TCI code point may indicate at least two TCI states out of a plurality of TCI states. A subset of a plurality of TCI states may be at least two TCI states. A wireless device may not receive a DCI indicating the activation of one or more TCI states out of at least two TCI states based, for example, on the number of one or more TCI code points being equal to 1. A wireless device may not receive a DCI indicating the activation of one or more TCI states out of at least two TCI states based, for example, on an activation command indicating the activation of at least two TCI states.

[0210] The number of one or more TCI code points may be greater than 1. A wireless device may receive a DCI (e.g., DCI 1 at time T2 in Figure 17). The DCI may be, for example, DCI format 1_1. The DCI may be, for example, DCI format 1_2. The DCI may be, for example, DCI format 1_x, where x = 0, 1, 2, ... The DCI may be, for example, DCI format 0_x, where x = 0, 1, 2, ...

[0211] A DCI may include a TCI field. A TCI field may indicate one of one or more TCI code points. The value of a TCI field (e.g., 110 in step 1730 of Figure 17) may be equal to, for example, a TCI code point. The value of a TCI field may indicate, for example, a TCI code point. A TCI code point (e.g., 110) may indicate / include at least two TCI states. A DCI may indicate (or can activate) the activation of at least two TCI states. The at least two TCI states may include a first TCI state and a second TCI state. For example, in Figure 17, the first TCI state is TCI state 26. The second TCI state is TCI state 61. Any TCI code point may indicate / include any one or more TCI states (e.g., one TCI state, two TCI states, or any number of TCI states). A DCI may indicate the activation of one TCI state (e.g., TCI state 42). DCI may indicate the activation of at least two TCI states (or any other number of TCI states).

[0212] The first TCI state of at least two TCI states can be identified / indicated by the first TCI state index. The second TCI state of at least two TCI states can be identified / indicated by the second TCI state index. Multiple TCI state indices can include the first TCI state. Multiple TCI state indices can include the second TCI state index. At least one TCI state indicator / index of multiple TCI states can include the first TCI state indicator / index. At least one TCI state indicator / index of multiple TCI states can include the second TCI state indicator / index.

[0213] At least two TCI states may be / include at least two unified TCI states. The first TCI state may be / include the first unified TCI state. The second TCI state may be / include the second unified TCI state.

[0214] The first TCI state (e.g., TCI state 26) may be the first / initial / earliest / beginning TCI state in a vector / set / list of at least two TCI states. The first TCI state may be the first / initial / earliest element in a vector / set / list of at least two TCI states. The first TCI state may be the first / initial / earliest TCI state of at least two TCI states in (or indicated by) a TCI code point. The location / position of the first TCI state may be the earliest / highest / lowest in a vector of at least two TCI states. The location / position of the first TCI state may be earlier (or earlier) than the location / position of the second TCI state in a vector of at least two TCI states. The first TCI state may occur first in a vector / set / list of at least two TCI states. The first / initial / earliest TCI state (or first TCI state) is, for example, TCI state 26 if the vector of at least two TCI states is equal to [TCI state 26, TCI state 61]. The first / initial / earliest TCI state (or first TCI state) is, for example, TCI state 2 if the vector of at least two TCI states is equal to [TCI state 2, TCI state 1].

[0215] The second TCI state (e.g., TCI state 61) may be the second / second-starting / second-earliest TCI state in a vector / set / list of at least two TCI states. The second TCI state may be the second / second-starting / second-earliest element in a vector / set / list of at least two TCI states. The second TCI state may be the second / second-starting / second-earliest TCI state of at least two TCI states in a TCI code point (or indicated by it). The location / position of the second TCI state may be the second-earliest / second-highest / second-lowest in a vector of at least two TCI states. The location / position of the first TCI state may be earlier (or before) the location / position of the second TCI state in a vector of at least two TCI states. The location / position of the second TCI state may be later (e.g., after) the location / position of the first TCI state in a vector of at least two TCI states. The second TCI state may occur second in a vector / set / list of at least two TCI states. The second / second start / second earliest TCI state (or second TCI state) is, for example, TCI state 61 if the vector of at least two TCI states is equal to [TCI state 26, TCI state 61]. The second / second start / second earliest TCI state (or second TCI state) is, for example, TCI state 1 if the vector of at least two TCI states is equal to [TCI state 2, TCI state 1].

[0216] DCI can schedule the transmission of transport blocks (e.g., PDSCH, PUSCH). DCI may include, for example, downlink allocations indicating resources for transport blocks. DCI may include, for example, uplink grants / allocations indicating resources for transport blocks. A wireless device can transmit (e.g., transmit) transport blocks through resources.

[0217] DCI cannot schedule transport block transmissions (e.g., PDSCH / PUSCH transmissions). DCI cannot include, for example, downlink allocations. DCI cannot include, for example, uplink grants / allocations. For DCI / its CRC may be scrambled with RNTI (e.g., CS-RNTI). The RV field of DCI may be set (or indicate, or equal to) 1 (e.g., all "1") by the base station. The MCS field of DCI may be set (or indicate, or equal to) one (e.g., all "1") by the base station. The New Data Indicator (NDI) field of DCI may be set (or indicate, or equal to) zero by the base station. The FDRA field of DCI may be set (or indicate, or equal to) zero (e.g., all "0") for FDRA type 0. The FDRA field in DCI can be set (or indicate, or be equal to) 1 (e.g., all "1") for FDRA type 1, for example. The FDRA field in DCI can be set (or indicate, or be equal to) zero (e.g., all "0") for dynamic switches, for example.

[0218] A wireless device may transmit (e.g., transmit) an uplink signal (e.g., a HARQ-ACK or a PUCCH containing HARQ-ACK information) via a PUCCH resource. A wireless device may transmit (e.g., transmit) an uplink signal for a transport block scheduled by DCI. A wireless device may transmit (e.g., transmit) an uplink signal to DCI (e.g., if DCI does not schedule the transmission of a transport block).

[0219] A wireless device, for example, counts the number of symbols (e.g., beam application time, MAC-CE activation time) from the last / end / latest symbol of the uplink signal (or PUCCH with HARQ-ACK information) to the number of symbols thereafter.

number

[0220] A wireless device may apply (or begin using) at least two TCI states (e.g., DCI1 at time T1 in Figure 17) indicated / activated by a startup command that starts from the initiating / initial / earliest / first slot, for example, based on the number of one or more TCI code points being equal to 1.

[0221] A wireless device may apply (or initiate use of) at least two TCI states indicated / activated by a DCI (e.g., at time T2 in Figure 17) starting from the initiating / initial / earliest / first slot, based on, for example, that the number of one or more TCI code points is greater than 1.

[0222] At least two TCI states may include at least two uplink TCI states. Multiple uplink TCI states may include at least two uplink TCI states. A first TCI state may be the first uplink TCI state of at least two uplink TCI states. A second TCI state may be the second uplink TCI state of at least two uplink TCI states. A wireless device may apply / use at least two uplink TCI states for transmitting uplink signals (e.g., PUSCH transmit, PUCCH transmit, UCI, transport block, SRS, etc.) over the uplink BWP of a cell.

[0223] Using / applying at least two uplink TCI states for transmitting an uplink signal may include transmitting (e.g., transmitting) one or more first uplink signals (e.g., PUSCH transmit, PUCCH transmit, UCI, transport block, SRS, etc.) using a first spatial domain transmit filter / beam determined based on a first reference signal indicated by the first uplink TCI state. The first spatial domain transmit filter / beam may be the same as (or substantially the same as, x-degree interval, x=0, 1, 5, 10, etc.) used to receive the first reference signal. The first spatial domain transmit filter / beam may be the same as (or substantially the same as, x-degree interval, x=0, 1, 5, 10, etc.) used to transmit (e.g., transmit) the first reference signal. Using / applying at least two uplink TCI states for transmitting an uplink signal may include transmitting (e.g., transmitting) one or more first uplink signals at a first transmit power determined based on one or more first power control parameters (e.g., target received power, closed-loop index, path loss compensation coefficient, alpha, path loss reference signal, etc.) indicated by (or included in, associated with, or mapped to) a first uplink TCI state. The uplink signal may include one or more first uplink signals. Using / applying at least two uplink TCI states for transmitting an uplink signal may include transmitting (e.g., transmitting) one or more second uplink signals (e.g., PUSCH transmit, PUCCH transmit, UCI, transport block, SRS, etc.) using a second spatial domain transmit filter / beam determined based on a second reference signal indicated by a second uplink TCI state. The second spatial domain transmit / transmit filter / beam may be the same as (or substantially the same as, for example, the spatial domain receive / receive filter / beam used to receive the second reference signal, with x-degree intervals, x=0, 1, 5, 10, etc.).The second spatial domain transmit / transmit filter / beam may be the same as (or substantially the same as, x-degree interval, x=0, 1, 5, 10, etc.) the spatial domain transmit / transmit filter / beam used to transmit (e.g., transmit) the second reference signal. Using / applying at least two uplink TCI states for transmitting uplink signals may include transmitting (e.g., transmitting) one or more second uplink signals at a second transmit power determined based on one or more second power control parameters (e.g., target received power, closed-loop index, path loss compensation coefficient, alpha, path loss reference signal, etc.) indicated by (or included in, associated with, or mapped to) the second uplink TCI states. The uplink signals may include one or more second uplink signals.

[0224] At least two TCI states may be / include at least two downlink TCI states. Multiple downlink TCI states may include at least two downlink TCI states. A first TCI state may be / include the first downlink TCI state of at least two downlink TCI states. A second TCI state may be / include the second downlink TCI state of at least two downlink TCI states. A wireless device may apply / use at least two downlink TCI states for receiving downlink signals via a cell's downlink BWP (e.g., PDSCH transmit / receive, PDCCH transmit / receive, CSI-RS, DMRS, etc.).

[0225] Using / applying at least two downlink TCI states for receiving a downlink signal may include receiving one or more first downlink signals (e.g., PDSCH, PDCCH, CSI-RS, DMRS, etc.) using a first spatial domain receive / receive filter / beam determined based on a first reference signal indicated by a first downlink TCI state. The first spatial domain receive / receive filter / beam may be the same (or substantially the same, x-degree interval, x=0, 1, 5, 10, etc.) as the spatial domain receive / receive filter / beam used to receive the first reference signal. The first spatial domain receive / receive filter / beam may be the same (or substantially the same, x-degree interval, x=0, 1, 5, 10, etc.) as the spatial domain transmit / transmit filter / beam used to transmit (e.g., transmit) the first reference signal. The downlink signal may include one or more first downlink signals. Using / applying at least two downlink TCI states for receiving a downlink signal may include receiving one or more second downlink signals (e.g., PDSCH, PDCCH, CSI-RS, DMRS, etc.) using a second spatial domain receive / receive filter / beam determined based on a second reference signal indicated by the second downlink TCI state. The second spatial domain receive / receive filter / beam may be the same (or substantially the same, x-degree interval, x=0, 1, 5, 10, etc.) as the spatial domain receive / receive filter / beam used to receive the second reference signal. The second spatial domain receive / receive filter / beam may be the same (or substantially the same, x-degree interval, x=0, 1, 5, 10, etc.) as the spatial domain transmit / transmit filter / beam used to transmit (e.g., transmit) the second reference signal. The downlink signal may include one or more second downlink signals.

[0226] Using / applying at least two downlink TCI states for receiving a downlink signal may include the DM-RS (or DM-RS antenna port) of one or more first downlink signals (e.g., PDSCH, PDCCH, CSI-RS, DMRS, etc.) being quasi-collocated with a first reference signal indicated by the first downlink TCI state. The DM-RS (or DM-RS antenna port) of one or more first downlink signals may be quasi-collocated with a first reference signal with respect to a first quasi-collocation type (e.g., QCL type A, QCL type B, QCL type C, QCL type D, QCL type E, etc.) indicated by the first downlink TCI state. Using / applying at least two downlink TCI states for receiving a downlink signal may include the DM-RS (or DM-RS antenna port) of one or more second downlink signals (e.g., PDSCH, PDCCH, CSI-RS, DMRS, etc.) being quasi-collocated with a second reference signal indicated by a second downlink TCI state. One or more second downlink signals' DM-RS (or DM-RS antenna ports) may be quasi-collocated with a second reference signal with respect to a second quasi-collocation type (e.g., QCL type A, QCL type B, QCL type C, QCL type D, QCL type E, etc.) indicated by the second downlink TCI state.

[0227] Using / applying at least two downlink TCI states for receiving downlink signals may include one or more first downlink signals (e.g., CSI-RS, DMRS, etc.) being quasi-collocated with a first reference signal indicated by the first downlink TCI state. One or more first downlink signals may be quasi-collocated with a first reference signal with respect to a first quasi-collocation type indicated by the first downlink TCI state. Using / applying at least two downlink TCI states for receiving downlink signals may include one or more second downlink signals (e.g., CSI-RS, DMRS, etc.) being quasi-collocated with a second reference signal indicated by a second downlink TCI state. One or more second downlink signals may be quasi-collocated with a second reference signal with respect to a second quasi-collocation type indicated by the second downlink TCI state.

[0228] At least two TCI states may be / include at least two common / joint TCI states (or at least two common / joint uplink and downlink TCI states). Multiple common / joint TCI states may include at least two common / joint TCI states. A first TCI state may be / include the first common / joint TCI state of at least two common / joint TCI states. A second TCI state may be / include the second common / joint TCI state of at least two common / joint TCI states. A wireless device may apply / use at least two common / joint TCI states for receiving downlink signals (e.g., PDSCH, PDCCH, CSI-RS, DMRS, etc.) via a cell's downlink BWP. A wireless device may apply / use at least two common / joint TCI states for transmitting uplink signals (e.g., PUSCH, PUCCH, UCI, transport block, SRS, etc.) via a cell's uplink BWP. A wireless device may apply / use at least two common / joint TCI states for receiving downlink signals and transmitting uplink signals.

[0229] Using / applying at least two common / joint TCI states for receiving downlink signals may include receiving one or more first downlink signals (e.g., PDSCH, PDCCH, CSI-RS, DMRS, etc.) using a first spatial domain receive / receive filter / beam determined based on a first reference signal indicated by a first common / joint TCI state. The first spatial domain receive / receive filter / beam may be the same (or substantially the same, x-degree interval, x=0, 1, 5, 10, etc.) as the spatial domain receive / receive filter / beam used to receive the first reference signal. The first spatial domain receive / receive filter / beam may be the same (or substantially the same, x-degree interval, x=0, 1, 5, 10, etc.) as the spatial domain transmit / transmit filter / beam used to transmit (e.g., transmit) the first reference signal. The downlink signals may include one or more first downlink signals. Using / applying at least two common / joint TCI states for receiving a downlink signal may include receiving one or more second downlink signals (e.g., PDSCH, PDCCH, CSI-RS, DMRS, etc.) using a second spatial domain receive / receive filter / beam determined based on a second reference signal indicated by a second common / joint TCI state. The second spatial domain receive / receive filter / beam may be the same (or substantially the same, x-degree interval, x=0, 1, 5, 10, etc.) as the spatial domain receive / receive filter / beam used to receive the second reference signal. The second spatial domain receive / receive filter / beam may be the same (or substantially the same, x-degree interval, x=0, 1, 5, 10, etc.) as the spatial domain transmit / transmit filter / beam used to transmit (e.g., transmit) the second reference signal. The downlink signal may include one or more second downlink signals.

[0230] Using / applying at least two common / joint TCI states for receiving a downlink signal may include the DMRS (or DM-RS antenna port) of one or more first downlink signals (e.g., PDSCH, PDCCH, CSI-RS, DMRS, etc.) being quasi-collocated with a first reference signal indicated by the first common / joint TCI state. The DM-RS (or DM-RS antenna port) of one or more first downlink signals may be quasi-collocated with a first reference signal with respect to a first quasi-collocation type (e.g., QCL type A, QCL type B, QCL type C, QCL type D, QCL type E, etc.) indicated by the first common / joint TCI state. Using / applying at least two common / joint TCI states for receiving a downlink signal may include the DMRS (or DM-RS antenna port) of one or more second downlink signals (e.g., PDSCH, PDCCH, CSI-RS, DMRS, etc.) being quasi-collocated with a second reference signal indicated by a second common / joint TCI state. One or more second downlink signals DM-RS (or DM-RS antenna ports) may be quasi-collocated with a second reference signal with respect to a second quasi-collocation type (e.g., QCL type A, QCL type B, QCL type C, QCL type D, QCL type E, etc.) indicated by a second common / joint TCI state.

[0231] Using / applying at least two common / joint TCI states for receiving downlink signals may include one or more first downlink signals (e.g., CSI-RS, DMRS, etc.) being quasi-collocated with a first reference signal indicated by the first common / joint TCI state. One or more first downlink signals may be quasi-collocated with a first reference signal with respect to a first quasi-collocation type indicated by the first common / joint TCI state. Using / applying at least two common / joint TCI states for receiving downlink signals may include one or more second downlink signals (e.g., CSI-RS, DMRS, etc.) being quasi-collocated with a second reference signal indicated by a second common / joint TCI state. One or more second downlink signals may be quasi-collocated with a second reference signal with respect to a second quasi-collocation type indicated by the second common / joint TCI state.

[0232] Using / applying at least two common / joint TCI states for transmitting an uplink signal may include transmitting (e.g., transmitting) one or more first uplink signals (e.g., PUSCH transmit, PUCCH transmit, UCI, transport block, SRS, etc.) using a first spatial domain transmit filter / beam determined based on a first reference signal indicated by the first common / joint TCI state. The first spatial domain transmit filter / beam may be the same as (or substantially the same as, x-degree interval, x=0, 1, 5, 10, etc.) used to receive the first reference signal. The first spatial domain transmit filter / beam may be the same as (or substantially the same as, x-degree interval, x=0, 1, 5, 10, etc.) used to transmit (e.g., transmit) the first reference signal. Using / applying at least two common / joint TCI states for transmitting uplink signals may include transmitting (e.g., transmitting) one or more first uplink signals at a first transmit power determined based on one or more first power control parameters (e.g., target received power, closed-loop index, path loss compensation coefficient, alpha, path loss reference signal, and similar) indicated by (or included in, associated with, or mapped to) a first common / joint TCI state. The uplink signals may include one or more first uplink signals.

[0233] Using / applying at least two common / joint TCI states for transmitting an uplink signal may include transmitting (e.g., transmitting) one or more second uplink signals (e.g., PUSCH transmit, PUCCH transmit, UCI, transport block, SRS, etc.) using a second spatial domain transmit filter / beam determined based on a second reference signal indicated by a second common / joint TCI state. The second spatial domain transmit filter / beam may be the same as (or substantially the same as, for example, a spatial domain receive filter / beam used to receive a second reference signal, with x-degree intervals, x=0, 1, 5, 10, etc.) The second spatial domain transmit filter / beam may be the same as (or substantially the same as, for example, a spatial domain transmit filter / beam used to transmit (e.g., transmit) a second reference signal, with x-degree intervals, x=0, 1, 5, 10, etc. Using / applying at least two common / joint TCI states for transmitting uplink signals may include transmitting (e.g., transmitting) one or more second uplink signals at a second transmit power determined based on one or more second power control parameters (e.g., target received power, closed-loop index, path loss compensation coefficient, alpha, path loss reference signal, and similar) indicated by (or included in, associated with, or mapped to) the second common / joint TCI state. The uplink signals may include one or more second uplink signals.

[0234] Figure 18 shows an example of an uplink repetition scheme. One or more wireless devices can repeatedly transmit uplink signals (e.g., PUSCH transmit, transport block, PUCCH transmit, uplink control information, HARQ-ACK, SR, CSI report, SRS) across / over / in multiple transmit / repetition opportunities. One or more wireless devices may transmit (e.g., transmit) repetitions of uplink signals across / over / in / in multiple transmit opportunities.

[0235] One or more configuration parameters may indicate a repeating scheme (e.g., FDM scheme, TDM scheme, SDM scheme, CDM scheme). One or more wireless devices may repeat an uplink signal (transmit) over / beyond / in multiple transmit / repeat opportunities, for example, based on one or more configuration parameters indicating a repeating scheme. A wireless device may transmit / transmit a transport block over / in / in multiple uplink signal / channel transmission opportunities (e.g., over, through, and in) using / in / in multiple transmission powers, for example, based on one or more configuration parameters indicating a repeating scheme.

[0236] One or more wireless devices may receive a DCI scheduling / triggered transmission of an uplink signal. The DCI may indicate a repeating scheme (e.g., FDM-Scheme, TDM-Scheme, SFN-Scheme, SDM-Scheme, CDM-Scheme). The DCI may include one or more fields indicating the repeating scheme (e.g., SRI field, TCI field, antenna port field, PUCCH resource indicator field, SRS resource set indicator field, etc.). One or more fields may be set to / equal to one or more values ​​indicating the repeating scheme. Each field of the one or more fields may be set to the respective value of one or more values. One or more wireless devices may, for example, repeat (transmit) an uplink signal over / beyond / across multiple transmission / repetition opportunities based on the DCI indicating a repeating scheme. A wireless device may, for example, transmit (e.g., transmit) a repetition of an uplink signal over / beyond / across multiple transmission opportunities based on the DCI indicating a repeating scheme.

[0237] The amount of repetition may be for repetition of the uplink signal via uplink resources (e.g., PUCCH resource, SRS resource, PUSCH resource). The repetition scheme does not have to be, for example, time-domain repetition (e.g., TDM in Figure 18). The repetition scheme does not have to be, for example, frequency-domain repetition (e.g., FDM in Figure 18). The repetition scheme does not have to be, for example, code / space-domain repetition (e.g., SDM / SFN in Figure 18).

[0238] The repetition of the uplink signal can be, for example, a time-domain repetition (e.g., TDM, TDMSchemeA, TDMSchemeB in Figure 18). In a time-domain repetition, multiple transmission opportunities cannot overlap in time. Each of the multiple transmission opportunities may have a time-domain resource allocation that does not overlap with respect to other transmission opportunities. The first uplink signal / channel transmission opportunity of multiple uplink signal / channel transmission opportunities may not overlap in time with the second signal / channel transmission opportunity of multiple uplink signal / channel transmission opportunities. The first and second uplink signal / channel transmission opportunities may be different. In the time domain, the frequencies of multiple transmission opportunities may or may not overlap. Multiple transmission opportunities in a time-domain repetition may include the first TX opportunity, the second TX opportunity, the third TX opportunity, and the fourth TX opportunity (e.g., Figure 18). In a time-domain repetition, the repetition of the uplink signal can be / occur, for example, in time units (e.g., TDM-ed). A wireless device may, for example, repeat the transmission of an uplink signal over / over / within a time unit. One or more wireless devices may, for example, transmit (e.g., transmit) repetitions of an uplink signal over / over / in a time unit. A time unit may, for example, be continuous. A time unit may, for example, not be continuous (e.g., it may have time / symbol / slot gaps). The number / quantity of time units may be equal to the number / quantity of repetitions of the uplink signal. A time unit may, for example, be a time slot. A time unit may, for example, be a minislot. A time unit may, for example, be a time symbol (e.g., an OFDM symbol). A time unit may, for example, be a subframe. A time unit may, for example, be an actual / nominal repetition. Multiple transmission opportunities may / occur as time units. For example, the first transmission opportunity of multiple transmission opportunities may / occur as the first time unit of a time unit. The second transmission opportunity of multiple transmission opportunities may / occur as the second time unit of a time unit, and / or similar.The first time unit may be different from the second time unit. The first time unit does not need to overlap temporally with the second time unit.

[0239] The repetition of the uplink signal may be, for example, a frequency domain repetition (e.g., FDM, FDMSchemeA, FDMSchemeB, etc. in Figure 18). In a frequency domain repetition, multiple transmission opportunities may or may not overlap in time. In a frequency domain repetition, multiple transmission opportunities may not overlap in frequency. Each of the multiple transmission opportunities may have a frequency domain resource allocation that does not overlap with respect to other transmission opportunities. The first uplink signal / channel transmission opportunity of multiple uplink signal / channel transmission opportunities may not overlap in frequency with that of the second signal / channel transmission opportunity of multiple uplink signal / channel transmission opportunities. The first and second transmission opportunities may overlap in time. The first and second uplink signal / channel transmission opportunities may be different. Multiple transmission opportunities may include the first TX opportunity and the second TX opportunity in a frequency domain repetition (e.g., Figure 18). In frequency domain repetitions, repetitions of an uplink signal can occur in, for example, frequency units (e.g., frequency, resource block (RB), physical resource block (PRB), frequency band, subband, bandwidth portion, cell). One or more wireless devices can repeatedly transmit an uplink signal across / over / in frequency units. One or more wireless devices can transmit (e.g., transmit) repetitions of an uplink signal across / over / in frequency units. Frequency units can be, for example, continuous. Frequency units can be, for example, non-continuous (e.g., they can have frequency / PRB / RB gaps). The number / quantity of frequency units can be equal to the number / quantity of uplink signal repetitions. Frequency units can be, for example, frequency bands. Frequency units can be, for example, PRBs (or RBs). Frequency units can be, for example, BWPs. Frequency units can be, for example, cells. Multiple transmission opportunities can be / occur in frequency units. For example, the first transmission opportunity of multiple transmission opportunities can be / occur in the first frequency unit of frequency units.The second transmission opportunity among multiple transmission opportunities may be / occur as a second frequency unit of frequency units. The first and second frequency units may be different. The first and second frequency units do not have to overlap in frequency.

[0240] Uplink signal repetition can be, for example, code / spatial domain repetition (e.g., SDM / SFN, SDM scheme, CDM scheme, SDM scheme, CDMScheme, etc. in Figure 18). In code / spatial domain repetition, multiple transmission opportunities do not have to overlap in time. In code / spatial domain repetition, multiple transmission opportunities do not have to overlap in frequency. In code / spatial domain repetition, multiple transmission opportunities can be transmission opportunities (e.g., or a single transmission opportunity). Each transmission opportunity among multiple transmission opportunities can be the same (or the same as a transmission opportunity or a single transmission opportunity). Each transmission opportunity among multiple transmission opportunities may have a frequency domain resource allocation that overlaps with respect to other transmission opportunities among multiple transmission opportunities. Each transmission opportunity among multiple transmission opportunities may have a time domain resource allocation that overlaps with respect to other transmission opportunities among multiple transmission opportunities. The first uplink signal / channel transmission opportunity among multiple uplink signal / channel transmission opportunities may overlap in time / frequency with the second signal / channel transmission opportunity among multiple uplink signal / channel transmission opportunities. The first transmission opportunity (e.g., the first TX opportunity) and the second transmission opportunity (e.g., the second TX opportunity) may be the same. Multiple transmission opportunities are the first and second TX opportunities in a code / spatial domain repetition (e.g., Figure 18). The first and second TX opportunities may be the same in a code / spatial domain repetition (e.g., they may overlap in time and frequency). In a code / spatial domain repetition, multiple transmission opportunities may occur in the same frequency unit (e.g., frequency, RB, PRB, frequency band, bandwidth portion, cell). The first frequency unit of the first signal / channel transmission opportunity and the second frequency unit of the second signal / channel transmission opportunity may have overlapping frequencies. The first frequency unit of the first transmission opportunity and the second frequency unit of the second transmission opportunity may be the same. Multiple transmission opportunities may occur in the same time unit (e.g., symbol, actual / nominal repetition, minislot, slot, subframe, etc.). The first time unit of the first signal / channel transmission opportunity and the second time unit of the second signal / channel transmission opportunity may overlap in time.The first time unit of the first transmission opportunity and the second time unit of the second transmission opportunity may be the same.

[0241] A wireless device may, for example, receive a DCI from a base station. A DCI may trigger / indicate / activate / schedule the transmission of information such as CSI reports (e.g., aperiodic CSI reports, semi-persistent CSI reports) and / or any other information. A DCI may schedule repetitions of push transmissions. A wireless device may transmit (e.g., transmit) repetitions of push transmissions to at least one TRP. For example, a wireless device may transmit (e.g., transmit) a first repetition of a push transmission to a first TRP or a first computing device. A wireless device may transmit (e.g., transmit) a second repetition of a push transmission to a second TRP or a second computing device. Repetitions of uplink transmissions (e.g., push transmissions) may be in the time domain, for example. Repetitions of push transmissions may be in the time domain.

[0242] A wireless device may receive one or more messages containing one or more configuration parameters. These configuration parameters may include CSI multiplexing mode parameters. CSI multiplexing mode parameters may be enabled (set).

[0243] In at least some wireless communications, a wireless device may transmit (e.g., the CSI report (or other information)) the PUSCH transmit (e.g., a first repetition (or first transmission opportunity) of the PUSCH transmit and a second repetition (or second transmission opportunity) of the PUSCH transmit and receive the CSI multiplexing mode parameters based on the CSI multiplexing mode parameter set, based on one or more configuration parameters, which enable the CSI multiplexing mode parameter set. The wireless device may transmit (e.g., transmit) the first repetition of the PUSCH transmit during the first transmission opportunity. The wireless device may transmit (e.g., transmit) the second repetition of the PUSCH transmit during the second transmission opportunity. The first repetition may include the first repetition. The first repetition may be the earliest / starting / first / initial repetition of the first repetition. The second repetition may include the second repetition. The second repetition may be the earliest / starting / first / initial repetition of the second repetition.

[0244] One or more configuration parameters may not include (or may not include) CSI multiplex mode parameters that are enabled. One or more configuration parameters may include disabled (or not enabled) sets of CSI multiplex mode parameters. In at least some radio communications, a radio device may transmit (e.g., transmit) a CSI report (or other information) on a first iteration (or first transmission opportunity) of a PUSCH transmission based on one or more configuration parameters that do not include a set of CSI multiplex mode parameters that are enabled. The radio device may transmit (e.g., transmit) a first iteration of a PUSCH transmission on a first transmission opportunity. The radio device may not transmit (e.g., transmit) / multiplex a CSI report on a second iteration (or second transmission opportunity) of a PUSCH transmission based on one or more configuration parameters that do not include a set of CSI multiplex mode parameters that are enabled. The radio device may not transmit (e.g., transmit) a second iteration of a PUSCH transmission on a second transmission opportunity. The iteration of a PUSCH transmission may include the first iteration. The first repetition may be the earliest / starting / first / initial repetition of the PUSCH transmission repetitions.

[0245] A repetition of an uplink transmission (e.g., a push transmission) may be in the frequency domain. A repetition of a push transmission may be in the frequency domain. A repetition of an uplink transmission (e.g., a push transmission) may begin simultaneously / symbolically (or at the same time), for example, based on the fact that the repetition is in the frequency domain. The first repetition of a push transmission may begin with the first symbol. The second repetition of a push transmission may begin with the second symbol. The first and second symbols may be identical (or substantially similar), for example, based on the fact that the repetition is in the frequency domain. In at least some radio communications, transmitting (e.g., transmitting) a CSI report (or other information) in the earliest / starting / first A base station does not need to receive / decode a PUSCH transmission repetition if, for example, the base station and radio device are not aligned to the repetition of the PUSCH transmission in which the base station and radio device transmit / multiplex a CSI report (or other information). For example, a radio device may transmit / multiplex a CSI report (or other information) in the first repetition of a PUSCH transmission repetition. The radio device may not transmit / multiplex a CSI report (or other information) in the second repetition of the PUSCH transmission repetition. The base station does not need to have information about the repetition in which the radio device transmits / multiplexes a CSI report (or other information). The base station may decode one / each repetition of a PUSCH transmission repetition under two different assumptions (e.g., 1) the repetition is multiplexed with a CSI report (or other information), and 2) the CSI report is not multiplexed in the repetition). This operation of the base station may increase power consumption at the base station.

[0246] As described herein, the transmission / multiplexing of CSI reports (or other information) for / in frequency domain repetitions can be enhanced, for example, by aligning the operation of base stations and radio devices. A radio device may repeatedly transmit / multiplex CSI reports (or other information) in a series of push transmissions based on rules such as transmitting / transmitting at the lowest / highest start / end frequency / resource block (RB). A radio device may repeatedly transmit / multiplex CSI reports (or other information) in a series of push transmissions transmitted on the antenna panel having the lowest / highest antenna panel index / identifier. A radio device may repeatedly transmit / multiplex CSI reports (or other information) in a series of push transmissions transmitted on the TCI state having the lowest TCI state index (e.g., transmit beam). A wireless device may repeatedly transmit / multiplex a CSI report (or other information) in a series of push transmissions, which are transmitted based on a first TCI state (or first SRS resource set).

[0247] A wireless device may transmit (e.g., transmit) / multiplex a CSI report (or other information) in multiple iterations of a push transmission in the frequency domain. A wireless device may transmit (e.g., transmit) / multiplex a CSI report (or other information) in each iteration of a push transmission in the frequency domain. Transmitting (e.g., transmit) / multiplexing a CSI report (or other information) in each iteration of a push transmission can increase robustness and versatility. In frequency domain iterations, a wireless device cannot determine / check whether one or more configuration parameters include a CSI multiplex mode parameter (or other parameter) that is set to enable or disable. In frequency domain iterations, a wireless device may transmit (e.g., transmit) / multiplex a CSI report (or other information) in each iteration of a push transmission, regardless of whether the CSI multiplex mode parameter (or other parameter) is enabled or disabled. In time domain iterations, a wireless device can determine / check whether one or more configuration parameters include a CSI multiplex mode parameter (or other parameter) or whether this is enabled or disabled. In time-domain iterations, the wireless device may transmit (e.g., transmit) / multiplex a CSI report (or other information) in each iteration of a push transmission, based on whether one or more configuration parameters, including CSI multiplex mode parameters (or other parameters), are enabled.

[0248] The embodiments described herein may offer advantages such as helping to align a base station and a radio device on one or more repetitions on which a radio device transmits (e.g., transmits) / multiplexes a CSI report (or other information). This alignment may achieve advantages such as reduced power consumption at the base station, increased success rate of decoding push transmissions, and / or other advantages evident from the description herein.

[0249] Figure 19 shows an example of report multiplexing. One or more configuration parameters may indicate at least two SRS resource sets. At least two SRS resource sets may include a first SRS resource set and a second SRS resource set. One or more configuration parameters may include activation parameters to be enabled. One or more configuration parameters may include, for example, usage parameters for each SRS resource set (e.g., each SRS resource set in at least two SRS resource sets). Usage parameters may be set in the codebook. Usage parameters for an SRS resource set (e.g., each SRS resource set in at least two SRS resource sets) may be set in the codebook. One or more configuration parameters may indicate a codebook for an SRS resource set (e.g., each SRS resource set in at least two SRS resource sets). One or more configuration parameters may indicate a codebook (or usage parameters set in the codebook) for the first SRS resource set. One or more configuration parameters may indicate a codebook (or usage parameters set in the codebook) for the second SRS resource set.

[0250] Usage parameters may be set in a non-codebook. Usage parameters for an SRS resource set (e.g., each SRS resource set in at least two SRS resource sets) may be set in a non-codebook. One or more configuration parameters may indicate a non-codebook for an SRS resource set (e.g., each SRS resource set in at least two SRS resource sets). One or more configuration parameters may indicate a non-codebook (or usage parameters set in a non-codebook) for a first SRS resource set. One or more configuration parameters may indicate a non-codebook (or usage parameters set in a non-codebook) for a second SRS resource set.

[0251] One or more configuration parameters may indicate at least two SRS resource set indices for at least two SRS resource sets. One or more configuration parameters may indicate respective SRS resource set indices (e.g., at least two SRS resource set indices) for an SRS resource set (e.g., each SRS resource set of at least two SRS resource sets). An SRS resource set (e.g., each SRS resource set of at least two SRS resource sets) may be identified / indicated by respective SRS resource set indices (e.g., at least two SRS resource set indices). The first SRS resource set among one or more SRS resource sets may be indicated / identified by the first SRS resource set indicator / index among SRS resource set indicators / indexes. The second SRS resource set among one or more SRS resource sets may be indicated / identified by the second SRS resource set indicator / index among SRS resource set indicators / indexes. The first SRS resource set index of the first SRS resource set may be lower than the second SRS resource set index of the second SRS resource set.

[0252] One or more wireless devices may receive DCI (e.g., at T0 in FIG. 19). The DCI may be, for example, DCI format 0_1. The DCI may be, for example, DCI format 0_2. The DCI may be, for example, DCI format 0_x, where x = 0, 1, 2, 3,.... The DCI (e.g., at time T0 in FIG. 19) may be the same as, for example, the DCI indicating the activation of at least two TCI states (e.g., at time T2 in FIG. 17). The DCI (e.g., at time T0 in FIG. 19) may be different from, for example, the DCI indicating the activation of at least two TCI states (e.g., at time T2 in FIG. 17).

[0253] DCI can schedule / trigger / activate the transmission of CSI reports. The CSI report can be, for example, an aperiodic CSI report. DCI can include scheduling / triggering the transmission of the CSI request field of an aperiodic CSI report. The CSI report can be, for example, a semi-persistent CSI report. DCI can include a CSI request field that activates the transmission of a semi-persistent CSI report. The CSI report can be, for example, a single CSI report. The CSI report can be, for example, multiple CSI reports. The CSI report can be, for example, one or more CSI reports.

[0254] DCI can include at least one field (e.g., SRS resource set indicator, TCI field, unified TCI state field, TRP indicator field, and / or the like). The field can indicate, for example, multi-TRP uplink repetition (e.g., multi-TRP PUSCH repetition, multi-TRP PUCCH repetition). The value of the field can indicate the repetition of multi-TRP uplink. The value of the field can indicate the repetition of multi-TRP PUSCH. The value of the field can indicate the repetition of multi-TRP PUCCH. The size / length of the field can be, for example, 2 bits (or any other bit amount). For example, the value of the field (e.g., SRS resource set indicator) can be equal to '10' or any other value. For example, the value of the field (e.g., SRS resource set indicator) can be equal to '11'. The size / length of the field can be, for example, 1 bit. For example, the value of the field (e.g., SRS resource set indicator) can be equal to '1'.

[0255] DCI can schedule repetitions of uplink transmissions. For example, DCI can schedule repetitions of push transmissions. A wireless device can transmit (e.g., transmit) repetitions of uplink transmissions (e.g., push transmissions) in multiple transmission opportunities. A wireless device can transmit (e.g., transmit) at least one repetition of an uplink transmission (e.g., each repetition of a push transmission) in each of the multiple transmission opportunities. A wireless device can transmit (e.g., transmit) the first repetition of a push transmission in the first of the multiple transmission opportunities. A wireless device can transmit (e.g., transmit) the second repetition of a push transmission in the second of the multiple transmission opportunities.

[0256] A repeating PUSCH transmission can be associated with at least two SRS resource sets. One or more first repeats of a repeating PUSCH transmission can be associated with the first SRS resource set of at least two SRS resource sets. One or more second repeats of a repeating PUSCH transmission can be associated with the second SRS resource set of at least two SRS resource sets. A repeating PUSCH transmission can be associated with at least two SRS resource sets, for example, based on the value of a field (e.g., SRS resource set indicator) being equal to '10' (or any other value). A repeating PUSCH transmission can be associated with at least two SRS resource sets, for example, based on the value of a field (e.g., SRS resource set indicator) being equal to '11' (or any other value). A repeating PUSCH transmission may be associated with at least two SRS resource sets, for example, based on the value of a field indicating a multi-TRP uplink repeat (e.g., SRS resource set indicator).

[0257] A PUSCH transmission may, for example, include / carry (or have a transport block). A PUSCH transmission may, for example, not include / carry (or have no transport block). A wireless device may determine / assume the number of repetitions of a PUSCH transmission to be 2 (or equal to) based on, for example, that the PUSCH transmission does not include / carry a transport block. A wireless device may determine / assume the number of repetitions of a PUSCH transmission to be 2 (or equal to) based on, for example, that the PUSCH transmission does not have a transport block. A wireless device may determine / assume the number of repetitions of a PUSCH transmission to be 2 regardless of the value of the upper-layer (e.g., RRC) parameter numberOfRepetitions or the upper-layer parameter push-AggregationFactor. One or more configuration parameters may, for example, include the upper-layer parameter numberOfRepetitions. One or more configuration parameters may, for example, include the upper-layer parameter push-AggregationFactor.

[0258] One or more configuration parameters may include CSI multiplex mode parameters. CSI multiplex mode parameters may be enabled (set). CSI multiplex mode parameters may indicate whether transmission (e.g., transmission) of CSI reports is enabled for at least two repetitions of a PUSCH transmission. The at least two repetitions of the PUSCH transmission may be, for example, in the time domain (e.g., TDM in Figure 18). CSI multiplex mode parameters may be used / applied to time domain repetitions (e.g., TDM in Figure 18). The at least two repetitions of the PUSCH transmission may be, for example, in the frequency domain (e.g., FDM in Figure 18). CSI multiplex mode parameters may be used / applied to frequency domain repetitions (e.g., FDM in Figure 18). The at least two repetitions of the PUSCH transmission may not be, for example, in the frequency domain (e.g., FDM in Figure 18). CSI multiplex mode parameters may not be used / applied to frequency domain repetitions (e.g., FDM in Figure 18). At least two iterations of a PUSCH transmission can be associated with at least two SRS resource sets. The first of at least two iterations of a PUSCH transmission can be associated with the first SRS resource set of at least two SRS resource sets. The second of at least two iterations of a PUSCH transmission can be associated with the second SRS resource set of at least two SRS resource sets.

[0259] The CSI multiplexing mode parameter may be, for example, the aperiodic CSI multiplexing mode (or AP-CSI multiplexing mode) parameter. The CSI-AperiodicTriggerStateList parameter / IE may include the aperiodic-CSI-MultiplexingMode parameter. One or more configuration parameters may include / indicate the CSI-AperiodicTriggerStateList parameter / IE.

[0260] The CSI multiplexing mode parameter may be, for example, the semi-persistent CSI multiplexing mode (or SP-CSI multiplexing mode) parameter. The CSI-SemiPersistentOnPUSCH-TriggerStateList parameter / IE may include the semi-persistent-CSI-MultiplexingMode parameter. One or more configuration parameters may include / indicate the CSI-SemiPersistentOnPUSCH-TriggerStateList parameter / IE.

[0261] One or more wireless devices may transmit (e.g., transmit) messages such as capability messages (e.g., UE capability messages). A message (e.g., UE capability message) may indicate support for transmitting (e.g., transmit) a CSI report (or other information) on / over at least two repetitions of an uplink transmit (e.g., a push transmit). A capability message may indicate support for transmitting (e.g., transmit) a CSI report (or other information) on / over at least two transmission opportunities of at least two repetitions of a push transmit. A capability message may indicate support for multiplexing a CSI report on / over at least two repetitions of a push transmit. One or more configuration parameters may include, for example, CSI multiplex mode parameters (or enabled CSI multiplex mode parameters) based on a capability message indicating support for transmitting (e.g., transmit) / multiplexing a CSI report on / over at least two repetitions (or at least two transmission opportunities) of a push transmit.

[0262] One or more configuration parameters may include CSI multiplex FDM mode parameters (or CSI-FDM multiplex mode parameters or CSI-frequency multiplex mode parameters, etc.). CSI multiplex FDM mode parameters may be enabled (set). CSI multiplex FDM mode parameters may differ from, for example, CSI multiplex mode parameters.

[0263] The CSI multiplexed FDM mode parameter may indicate whether it is enabled to transmit (e.g., transmit) a CSI report (or other information) for at least two repetitions of a PUSCH transmission. The at least two repetitions of the PUSCH transmission are in the frequency domain (e.g., Figure 18). The CSI multiplexed FDM mode parameter is in the frequency domain (e.g., Figure 18). The at least two repetitions of the PUSCH transmission may be associated with at least two SRS resource sets. The first repetition of the at least two repetitions of the PUSCH transmission may be associated with the first SRS resource set of at least two SRS resource sets. The second repetition of the at least two repetitions of the PUSCH transmission may be associated with the second SRS resource set of at least two SRS resource sets.

[0264] The CSI-Multiplexing-FDM mode parameter may be, for example, the aperiodic-CSI-Multiplexing-FDM mode (or AP-CSI-Multiplexing-FDM mode) parameter. The CSI-AperiodicTriggerStateList parameter / IE may include the aperiodic-CSI-Multiplexing-FDM-Mode parameter. One or more configuration parameters may include / indicate the CSI-AperiodicTriggerStateList parameter / IE.

[0265] The CSI-Multiplexing-FDM mode parameter may be, for example, the semi-persistent CSI-multiplexing-FDM mode (or SP-CSI-multiplexing-FDM mode) parameter. The CSI-SemiPersistentOnPUSCH-TriggerStateList parameter / IE may include the semi-persistent CSI-Multiplexing-FDM-Mode parameter. One or more configuration parameters may include / indicate the CSI-SemiPersistentOnPUSCH-TriggerStateList parameter / IE.

[0266] One or more wireless devices may transmit (e.g., transmit) messages, such as UE capability messages. A message (e.g., UE capability message) may indicate support for transmitting (e.g., transmit) a CSI report on / over at least two repetitions of an uplink transmit (e.g., a push transmit). At least two repetitions of a push transmit are in the frequency domain (e.g., Figure 18). A capability message may indicate support for transmitting (e.g., transmit) a CSI report on / over at least two transmit opportunities of at least two repetitions of a push transmit. A capability message may indicate support for multiplexing a CSI report on / over at least two repetitions of a push transmit. One or more configuration parameters may include, for example, CSI multiplexing-FDM mode parameters (or CSI multiplexing-FDM mode parameters configured to be enabled) based on a capability message indicating support for transmitting (e.g., transmit) / multiplexing a CSI report on / over at least two repetitions (or at least two transmit opportunities) of a push transmit.

[0267] One or more configuration parameters do not have to include CSI multiplex mode parameters (e.g., AP-CSI multiplex mode, SP-CSI multiplex mode). One or more configuration parameters do not have to include the set of CSI multiplex mode parameters to be enabled.

[0268] One or more wireless devices may transmit (e.g., transmit) messages, such as UE capability messages. A message (e.g., a UE capability message) may not indicate support for transmitting (e.g., transmitting) a CSI report on / over at least two repetitions of an uplink transmit (e.g., a push transmit). A capability message may not indicate support for transmitting (e.g., transmitting) a CSI report on / over at least two transmission opportunities of at least two repetitions of a push transmit. A capability message may not indicate support for multiplexing a CSI report on / over at least two repetitions of a push transmit. One or more configuration parameters may not include a CSI multiplex mode parameter (or a CSI multiplex mode parameter that is enabled) based on a capability message that does not indicate support for transmitting / multiplexing a CSI report on / over at least two repetitions (or at least two transmission opportunities) of a push transmit.

[0269] One or more configuration parameters do not have to include a CSI multiplex-FDM mode (e.g., AP-CSI-multiplex-FDM mode, SP-CSI-multiplex-FDM mode). One or more configuration parameters do not have to include an enabled CSI multiplex FDM mode parameter set.

[0270] One or more wireless devices may transmit (e.g., transmit) messages, such as UE capability messages. A message (e.g., a UE capability message) may not indicate support for transmitting (e.g., transmitting) a CSI report on / over at least two repetitions of an uplink transmit (e.g., a push transmit). At least two repetitions of a push transmit are in the frequency domain (e.g., Figure 18). The UE capability message may not indicate support for transmitting (e.g., transmitting) a CSI report on / over at least two transmission opportunities of at least two repetitions of a push transmit. The capability message may not indicate support for multiplexing a CSI report on / over at least two repetitions of a push transmit. One or more configuration parameters may not include CSI multiplex FDM mode parameters (or a set of CSI multiplex FDM mode parameters that are enabled) based on a capability message that does not indicate support for transmitting (e.g., transmitting) / multiplexing a CSI report on / over at least two repetitions (or at least two transmission opportunities) of a push transmit.

[0271] One or more configuration parameters may indicate the amount of iteration. The repetition scheme may be (or be set to) frequency-domain repetitions (e.g., frequency-domain multiplexing (FDM) repetitions). Uplink transmission (e.g., push transmission) repetitions may be in the frequency domain. Uplink transmission (e.g., push transmission) repetitions may be in the frequency domain based on one or more configuration parameters indicating a repetition scheme that is (or is set to) a frequency-domain repetition. A push transmission repetition may include a first repetition (e.g., repetition 1 in Figure 19) and a second repetition (repetition 2 in Figure 19). The first and second repetitions may overlap in time (e.g., fully in time, partially in time, in at least one symbol). The start symbol of the first repetition and the start symbol of the second repetition may be, for example, the same. The end symbol of the first repetition and the end symbol of the second repetition may be, for example, the same. The first and second repetitions do not have to overlap in frequency. The first and second repetitions may be at different frequencies (or different RBs or different PRBs). The first and second repetitions may not overlap in at least one RB (or PRB).

[0272] One or more first repetitions of a PUSCH transmission may include a first repetition (e.g., repetition 1 in Figure 19). A first repetition may be associated with a first SRS resource set of at least two SRS resource sets. A wireless device may transmit (e.g., transmit) a first repetition of a PUSCH transmission based, for example, a first SRS resource set. A wireless device may transmit (e.g., transmit) a first repetition of a PUSCH transmission based, for example, a first SRS resource in a first SRS resource set. One or more configuration parameters may indicate a first number of SRS ports (e.g., nrofSRS-PORTs) for a first SRS resource. A wireless device may transmit (e.g., transmit) a first repetition of a PUSCH transmission based, for example, a first number of SRS ports of a first SRS resource in a first SRS resource set. For example, a wireless device may transmit (e.g., transmit) a first repetition using a first transmit precoder determined based on a first number of SRS ports.

[0273] One or more second repetitions of a PUSCH transmission may include a second repetition (e.g., repetition 2 in Figure 19). A second repetition may be associated with a second set of SRS resources of at least two SRS resource sets. A wireless device may transmit (e.g., transmit) a second repetition of a PUSCH transmission based, for example, a second set of SRS resources. A wireless device may transmit (e.g., transmit) a second repetition of a PUSCH transmission based, for example, a second SRS resource in a second set of SRS resources. One or more configuration parameters may indicate a second number of SRS ports (e.g., nrofSRS-PORTs) for a second SRS resource. A wireless device may transmit (e.g., transmit) a second repetition of a PUSCH transmission based, for example, a second number of SRS ports of a second SRS resource in a second set of SRS resources. For example, a wireless device may transmit (e.g., transmit) a second repetition using a second transmit precoder determined based on a second number of SRS ports.

[0274] One or more wireless devices may transmit (e.g., send) a first repetition of a PUSCH transmission (e.g., repetition 1 in FIG. 19) at a first transmission opportunity (e.g., the first TX opportunity in FIG. 19) of a plurality of transmission opportunities (e.g., at time T1 in FIG. 19). The wireless device may transmit (e.g., send) a second repetition of a PUSCH transmission (e.g., repetition 2 in FIG. 19) at a second transmission opportunity (e.g., the second TX opportunity in FIG. 19) (e.g., at time T1 in FIG. 19) of the plurality of transmission opportunities.

[0275] One or more wireless devices may transmit (e.g., send) a first repetition of a PUSCH transmission based on a first TCI state of at least two TCI states (e.g., TCI state 26 in FIG. 17). One or more wireless devices may transmit (e.g., send) a first repetition of a PUSCH transmission using a first spatial domain transmission filter / beam determined based on a first reference signal indicated by the first TCI state. The first spatial domain transmission / transmission filter / beam may be the same (or substantially the same at an x-degree interval, x = 0, 1, 5, 10, etc.) as, for example, the spatial domain reception / reception filter / beam used to receive the first reference signal. The first spatial domain transmission / transmission filter / beam may be the same (or substantially the same at an x-degree interval, x = 0, 1, 5, 10, etc.) as, for example, the spatial domain transmission / transmission filter / beam used to transmit (e.g., send) the first reference signal.

[0276] One or more wireless devices may transmit (e.g., send) a first repetition of a PUSCH transmission at a first transmission power determined based on one or more first power control parameters (e.g., target received power, closed-loop index, path loss compensation factor, alpha, path loss reference signal, and / or the like) indicated by (or included in, or associated with, or mapped to) the first TCI state. One or more configuration parameters may indicate one or more first power control parameters for the first TCI state.

[0277] One or more wireless devices may transmit a second repetition of a push transmit based on a second TCI state (e.g., TCI state 61 in Figure 17) of at least two TCI states. One or more wireless devices may transmit a second repetition of a push transmit using a second spatial domain transmit filter / beam determined based on a second reference signal indicated by the second TCI state. The second spatial domain transmit filter / beam may be the same as (or substantially the same as) the spatial domain receive filter / beam used to receive the second reference signal (or substantially the same as x-degree intervals, x=0, 1, 5, 10, etc.). The second spatial domain transmit filter / beam may be the same as (or substantially the same as) the spatial domain transmit filter / beam used to transmit the second reference signal (e.g.,)

[0278] One or more wireless devices may transmit (e.g., transmit) a second iteration of a push transmit at a second transmission power determined based on one or more second power control parameters (e.g., target received power, closed-loop index, path loss compensation coefficient, alpha, path loss reference signal, and / or similar) indicated by (or included in, associated with, or mapped to) a second TCI state. One or more configuration parameters may indicate a second TCI state for a second core set.

[0279] One or more wireless devices may be equipped with multiple antenna panels. These multiple antenna panels may include a first antenna panel and a second antenna panel. The first antenna panel may be identified / indicated by a first antenna panel index / identifier. One or more configuration parameters may indicate a first antenna panel indicator / index for the first antenna panel. For example, one or more wireless devices may transmit (e.g., beam reports, CSI reports, UE capability messages, PUCCH transmissions) uplink signals indicating a first antenna panel index for the first antenna panel. A second antenna panel may be identified / indicated by a second antenna panel index / identifier. One or more configuration parameters may indicate a second antenna panel indicator / index for the second antenna panel. For example, one or more wireless devices may transmit (e.g., beam reports, CSI reports, UE capability messages, PUCCH transmissions) uplink signals indicating a second antenna panel index for the second antenna panel.

[0280] One or more wireless devices may transmit (e.g., transmit) a first repetition of a PUSCH transmission on a first antenna panel. The first repetition of a PUSCH transmission may be associated with the first antenna panel, for example, on the basis of transmitting (e.g., transmitting) the first repetition of a PUSCH transmission using the first antenna panel. One or more wireless devices may transmit (e.g., transmit) a second repetition of a PUSCH transmission on a second antenna panel. The second repetition of a PUSCH transmission may be associated with the second antenna panel, for example, on the basis of transmitting (e.g., transmitting) the second repetition of a PUSCH transmission using the second antenna panel.

[0281] A message transmitted by (e.g., transmitted by) one or more wireless devices (e.g., a UE capability message) may include / represent a list of capability value sets (e.g., a list of UE capability value sets, a list of wireless device capability value sets, etc.). Each capability value set (e.g., each capability value set in the list of capability value sets) may include / represent the maximum number of SRS ports for each. For example, the first capability value set in the list of capability value sets may include / represent the first maximum number of SRS ports. The second capability value set in the list of capability value sets may include / represent the second maximum number of SRS ports.

[0282] Each ability score set (for example, each ability score set in a list of ability score sets) can be identified / represented by its respective ability score set index. For example, the first ability score set can be identified / represented by the first ability score set index. The second ability score set can be identified / represented by the second ability score set index.

[0283] One or more wireless devices may transmit (e.g., transmit) at least one report (e.g., beam report, CSI report, L1-RSRP report, SINR report, and / or any other report). One or more wireless devices may transmit (e.g., transmit) a report via PUCCH. The report may show an association / mapping / correspondence between a first reference signal indicated by a first TCI state and a first capability value set. The report may include a first reference signal index for the first reference signal (e.g., CSI-RS and / or SSB resource index) and a first capability value set index for the first capability value set. One or more wireless devices may determine the association / mapping / correspondence between the first reference signal and the first capability value set. One or more configuration parameters may indicate a reference signal indicator / index / identifier for a reference signal. The first TCI state may be associated with a first capability value set based, for example, the association / mapping / correspondence between the first reference signal indicated by the first TCI state and the first capability value set. The first iteration of a PUSCH transmission may be associated with a first capability value set, for example, based on a first TCI state associated with a first capability value set, and based on transmitting (e.g., transmitting) the first iteration (e.g., in response to it).

[0284] The report may show the association / mapping / correspondence between a second reference signal and a second capability value set, indicated by a second TCI state. The report may include the second reference signal index of the second reference signal (e.g., CSI-RS and / or SSB resource index) and the second capability value set index of the second capability value set. One or more radio devices may determine the association / mapping / correspondence between the second reference signal and the second capability value set. One or more configuration parameters may indicate a reference signal indicator / index / identifier for a reference signal. A second TCI state may be associated with a second capability value set, for example, based on the association / mapping / correspondence between the second reference signal and the second capability value set indicated by the second TCI state. A second repetition of a PUSCH transmission may be associated with a second capability value set, for example, based on the second TCI state associated with the second capability value set, based on transmitting (e.g., transmitting) the second repetition (e.g., in response to it).

[0285] One or more wireless devices may receive confirmation of a report from, for example, a base station. This confirmation could be, for example, a DCI (Digital Control Indication).

[0286] One or more wireless devices may transmit (e.g., transmit) a CSI report in a first iteration of the PUSCH transmission (e.g., iteration 1 in Figure 19) and a second iteration of the PUSCH transmission (e.g., iteration 2 in Figure 19). The wireless device may transmit (e.g., transmit) a CSI report in a first transmission opportunity (e.g., the first TX opportunity in Figure 19) and a second transmission opportunity (e.g., the second TX opportunity in Figure 19).

[0287] One or more wireless devices may multiplex a CSI report (or other information) in / on / with a first iteration of a PUSCH transmission and a second iteration of a PUSCH transmission. One or more wireless devices may transmit (e.g., transmit) a CSI report in a first iteration of a PUSCH transmission and a second iteration of a PUSCH transmission, for example, based on multiplexing a CSI report in a first iteration of a PUSCH transmission and a second iteration of a PUSCH transmission. One or more wireless devices may transmit (e.g., transmit) a CSI report in a first transmission opportunity (when the first iteration of a PUSCH transmission is transmitted (e.g., transmitted)) and a second transmission opportunity (when the second iteration of a PUSCH transmission is transmitted (e.g., transmitted)), for example, based on multiplexing a CSI report in a first iteration of a PUSCH transmission and a second iteration of a PUSCH transmission.

[0288] One or more wireless devices may transmit (e.g., transmit) a CSI report in a first transmission opportunity (or first repetition of a push transmission) and a second transmission opportunity (or second repetition of a push transmission), based on, for example, one or more configuration parameters indicating at least two SRS resource sets. One or more wireless devices may multiplex the CSI report in a first repetition of a push transmission and a second repetition of a push transmission, based on, for example, one or more configuration parameters indicating at least two SRS resource sets.

[0289] One or more wireless devices may transmit (e.g., transmit) a CSI report on a first transmission opportunity (or first repetition of a push transmission) and a second transmission opportunity (or second repetition of a push transmission) based, for example, on a field (or the value of the field) indicating a multi-TRP uplink repetition. One or more wireless devices may transmit (e.g., transmit) a CSI report on a first transmission opportunity (or first repetition of a push transmission) and a second transmission opportunity (or second repetition of a push transmission) based, for example, on the value of a field being equal to '10', '11', or '1' (or any other value). One or more wireless devices may transmit (e.g., transmit) a CSI report on a first transmission opportunity (or first repetition of a push transmission) and a second transmission opportunity (or second repetition of a push transmission) based, for example, on the repetition of a push transmission being associated with at least two SRS resource sets.

[0290] One or more wireless devices may multiplex a CSI report (or other information) in the first and second iterations of a PUSCH transmission based, for example, on a field (or the value of the field) indicating a multi-TRP uplink repetition. One or more wireless devices may multiplex a CSI report in the first and second iterations of a PUSCH transmission based, for example, on the value of a field being equal to '10', '11', or '1' (or any other value). One or more wireless devices may multiplex a CSI report in the first and second iterations of a PUSCH transmission based, for example, on the repetition of a PUSCH transmission being associated with at least two SRS resource sets.

[0291] One or more wireless devices may transmit (e.g., transmit) a CSI report (or other information) in a first transmission opportunity (or first repetition of a push transmission) and a second transmission opportunity (or second repetition of a push transmission) based on one or more configuration parameters, for example, including CSI multiplex mode parameters. One or more wireless devices may transmit (e.g., transmit) a CSI report in a first transmission opportunity (or first repetition of a push transmission) and a second transmission opportunity (or second repetition of a push transmission) based on one or more configuration parameters, for example, including a set of CSI multiplex mode parameters to be enabled.

[0292] One or more wireless devices may multiplex a CSI report (or other information) in a first iteration and a second iteration of a PUSCH transmission based on one or more configuration parameters, for example, including a CSI multiplex mode parameter.

[0293] One or more wireless devices may transmit (e.g., transmit) a CSI report (or other information) on a first transmission opportunity (or first repetition of a push transmission) and a second transmission opportunity (or second repetition of a push transmission) based on one or more configuration parameters, for example, including CSI-multiplexing-FDM mode parameters. One or more wireless devices may transmit (e.g., transmit) a CSI report on a first transmission opportunity (or first repetition of a push transmission) and a second transmission opportunity (or second repetition of a push transmission) based on one or more configuration parameters, for example, including a set of CSI multiplexing-FDM mode parameters that are enabled.

[0294] One or more wireless devices may multiplex a CSI report (or other information) in a first iteration and a second iteration of a PUSCH transmission based on one or more configuration parameters, for example, including a CSI multiplex FDM mode parameter.

[0295] One or more wireless devices may transmit (e.g., transmit) a CSI report (or other information) on a first transmission opportunity (or first repetition of a PUSCH transmission) and a second transmission opportunity (or second repetition of a PUSCH transmission), for example, on the basis that a PUSCH transmission does not contain / carry uplink control information (UCI) different from the CSI report. One or more wireless devices may transmit (e.g., transmit) a CSI report on a first transmission opportunity (or first repetition of a PUSCH transmission) and a second transmission opportunity (or second repetition of a PUSCH transmission), for example, on the basis that a PUSCH transmission does not multiplex a UCI different from the CSI report. The UCI may include, for example, a HARQ-ACK. The UCI may include, for example, an SR.

[0296] One or more wireless devices may multiplex the CSI report (or other information) in a first iteration and a second iteration of a PUSCH transmission, for example, based on the fact that the PUSCH transmission does not contain / carries uplink control information (UCI) different from the CSI report. One or more wireless devices may multiplex the CSI report in a first iteration and a second iteration of a PUSCH transmission, for example, based on the fact that the PUSCH transmission does not multiplex a UCI different from the CSI report. The UCI may include, for example, a HARQ-ACK. The UCI may include, for example, an SR.

[0297] One or more wireless devices may include transmitting (e.g., transmitting), transmitting / multiplexing the CSI report (or other information in the first transmission opportunity (or the first repetition of the PUSCH transmission) and the second transmission opportunity (or the second repetition of the PUSCH transmission), for example, a UE capability message indicating support for transmission (e.g., transmitting / multiplexing the CSI report in / on at least two repetitions of the PUSCH transmission (or at least two transmission opportunities)).

[0298] One or more wireless devices may, for example, transmit a CSI report (e.g., transmission) or a capability message (e.g., UE capability message) indicating support for multiplexing in at least two iterations (or at least two transmission opportunities) of a PUSCH transmission, and multiplex a CSI report (or other information) in a first iteration of a PUSCH transmission and a second iteration of a PUSCH transmission.

[0299] One or more wireless devices may transmit (e.g., transmit) a CSI report (or other information) in a first transmission opportunity (or first repetition of a push transmission) and a second transmission opportunity (or second repetition of a push transmission) based on one or more configuration parameters indicating a repetition scheme that is (configured to be) a frequency domain repetition. One or more wireless devices may multiplex the CSI report (or other information) in a first repetition of a push transmission and a second repetition of a push transmission based on one or more configuration parameters indicating a repetition scheme that is (configured to be) a frequency domain repetition.

[0300] One or more wireless devices may transmit (e.g., transmit) a CSI report (or other information) in a series of PUSCH transmissions between a first series of PUSCH transmissions (e.g., series 1 in Figure 19) and a second series of PUSCH transmissions (e.g., series 2 in Figure 19). One or more wireless devices may transmit (e.g., transmit) a CSI report in a transmission opportunity between a first transmission opportunity (e.g., the first TX opportunity in Figure 19) and a second transmission opportunity (e.g., the second TX opportunity in Figure 19). Wireless devices may transmit (e.g., transmit) a series of PUSCH transmissions in a transmission opportunity. One or more wireless devices may not transmit (e.g., transmit) a CSI report in any series of PUSCH transmissions that are different from the series of PUSCH transmissions among the first series of PUSCH transmissions and the second series of PUSCH transmissions. One or more wireless devices may not transmit (e.g., transmit) a CSI report in any transmission opportunity among the first series of transmissions and the second series of transmissions that are different from the series of PUSCH transmissions.

[0301] One or more wireless devices may determine / select the number of push transmission repetitions between a first and second push transmission repetition for transmitting a CSI report (or other information). One or more wireless devices may determine / select the number of transmission opportunities between a first and second transmission opportunity for transmitting a CSI report.

[0302] A repeating PUSCH transmission could be, for example, the default repeat of a PUSCH transmission. Another repeating PUSCH transmission could be, for example, the base repeat of a PUSCH transmission.

[0303] For example, in Figure 19, a repetition of the PUSCH transmission may be the first repetition of the PUSCH transmission (e.g., repetition 1 in Figure 19). One or more wireless devices may transmit (e.g., transmit) a CSI report in the first repetition of the PUSCH transmission. One or more wireless devices may transmit (e.g., transmit) a CSI report in the first transmission opportunity (e.g., the first TX opportunity in Figure 19). One or more wireless devices may not transmit (e.g., transmit) a CSI report in the second repetition of the PUSCH transmission (e.g., repetition 2 in Figure 19). One or more wireless devices may not transmit (e.g., transmit) a CSI report in the second transmission opportunity (e.g., the second TX opportunity in Figure 19).

[0304] For example, in Figure 19, a repetition of the PUSCH transmission may be a second repetition of the PUSCH transmission (e.g., repetition 2 in Figure 19). One or more wireless devices may transmit (e.g., transmit) a CSI report in the second repetition of the PUSCH transmission. One or more wireless devices may transmit (e.g., transmit) a CSI report in the second transmission opportunity (e.g., the second TX opportunity in Figure 19). One or more wireless devices do not have to transmit (e.g., transmit) a CSI report in the first repetition of the PUSCH transmission (e.g., repetition 1 in Figure 19). One or more wireless devices may not transmit (e.g., transmit) a CSI report in the first transmission opportunity (e.g., the first TX opportunity in Figure 19).

[0305] One or more wireless devices may multiplex a CSI report (or other information) in / on / with a series of PUSCH transmissions. One or more wireless devices may transmit (e.g., transmit) a CSI report in a series of PUSCH transmissions, for example, based on the multiplexing of a CSI report in a series of PUSCH transmissions. One or more wireless devices may transmit (e.g., transmit) a CSI report in a transmission opportunity (when a series of PUSCH transmissions are transmitted (e.g., transmitted)), for example, based on the multiplexing of a CSI report in a series of PUSCH transmissions.

[0306] One or more wireless devices may transmit (e.g., transmit) a CSI report (or other information) during a transmission opportunity (or repeated push transmission) based on one or more configuration parameters indicating, for example, at least two SRS resource sets. One or more wireless devices may multiplex a CSI report (or other information) during repeated push transmissions based on one or more configuration parameters indicating, for example, at least two SRS resource sets.

[0307] One or more wireless devices may transmit (e.g., transmit) a CSI report (or other information) on a transmission opportunity (or repeated push transmission) based, for example, on the fact that one or more configuration parameters do not indicate at least two SRS resource sets in the codebook (or usage parameters set in the codebook). One or more wireless devices may transmit (e.g., transmit) a CSI report on a transmission opportunity (or repeated push transmission) based, for example, on the fact that one or more configuration parameters do not indicate at least two SRS resource sets in the non-codebook (or usage parameters set in the non-codebook). One or more wireless devices may transmit (e.g., transmit) a CSI report on a transmission opportunity (or repeated push transmission) based, for example, on one or more configuration parameters indicating an SRS resource set (or a single SRS resource set) having a codebook (or usage parameters set in the codebook). One or more wireless devices may transmit (e.g., transmit) a CSI report during a transmission opportunity (or repeated push transmission) based on one or more configuration parameters that indicate an SRS resource set (or a single SRS resource set) having a non-codebook (or usage parameters set in a non-codebook).

[0308] One or more wireless devices may multiplex CSI reports (or other information) in repeated push transmissions based, for example, on the fact that one or more configuration parameters do not indicate at least two SRS resource sets having codebooks (or having usage parameters set in codebooks). One or more wireless devices may multiplex CSI reports in repeated push transmissions based, for example, on the fact that one or more configuration parameters do not indicate at least two SRS resource sets that are not codebooks (or usage parameters set in non-codebooks). One or more wireless devices may multiplex CSI reports in repeated push transmissions based, for example, on one or more configuration parameters indicating an SRS resource set (or a single SRS resource set) having a codebook (or usage parameters set in a codebook). One or more wireless devices may multiplex CSI reports in repeated push transmissions based, for example, on one or more configuration parameters indicating an SRS resource set (or a single SRS resource set) having a non-codebook (or usage parameters set in non-codebooks).

[0309] One or more wireless devices may transmit (e.g., transmit) a CSI report on a transmit opportunity (or a repeat of a push transmit) based, for example, on a field (or the value of the field) indicating a repeat of a multi-TRP uplink. One or more wireless devices may transmit (e.g., transmit) a CSI report on a transmit opportunity (or a repeat of a push transmit) based, for example, on the value of a field being equal to '10', '11', or '1' (or any other value). One or more wireless devices may transmit (e.g., transmit) a CSI report on a transmit opportunity (or a repeat of a push transmit) based, for example, on the repeat of a push transmit being associated with at least two SRS resource sets.

[0310] One or more wireless devices may transmit (e.g., transmit) a CSI report (or other information) on a transmission opportunity (or repeated PUSCH transmission) based, for example, a field (or the value of the field) indicating a repetition / transmission of a single TRP uplink. One or more wireless devices may transmit (e.g., transmit) a CSI report on a transmission opportunity (or repeated PUSCH transmission) based, for example, a field value equal to '00', '01', or '0' (or any other value). One or more wireless devices may transmit (e.g., transmit) a CSI report on a transmission opportunity (or repeated PUSCH transmission) based, for example, a repeated PUSCH transmission is associated with an SRS resource set (or a single SRS resource set) having a codebook (or usage parameters set in a codebook). One or more wireless devices may transmit (e.g., transmit) a CSI report on a transmission opportunity (or repeated PUSCH transmission) based, for example, a repeated PUSCH transmission is associated with an SRS resource set (or a single SRS resource set) having a non-codebook (or usage parameters set in a non-codebook).

[0311] One or more wireless devices may multiplex CSI reports (or other information) in a PUSCH transmission repetition based, for example, on a field (or the value of the field) indicating a repetition / transmission of a single TRP uplink. One or more wireless devices may multiplex CSI reports in a PUSCH transmission repetition based, for example, on the value of a field being equal to '00', '01', or '0' (or any other value). One or more wireless devices may multiplex CSI reports in a PUSCH transmission repetition based, for example, on the repetition of a PUSCH transmission being associated with an SRS resource set (or a single SRS resource set) having a codebook (or usage parameters set in a codebook). One or more wireless devices may multiplex CSI reports in a PUSCH transmission repetition based, for example, on the repetition of a PUSCH transmission being associated with an SRS resource set (or a single SRS resource set) having a non-codebook (or usage parameters set in a non-codebook).

[0312] One or more wireless devices may transmit (e.g., transmit) a CSI report (or other information) on a transmission opportunity (or repeated PUSCH transmission) based, for example, on the fact that one or more configuration parameters do not include CSI multiplex mode parameters. One or more wireless devices may transmit (e.g., transmit) a CSI report on a transmission opportunity (or repeated PUSCH transmission) based, for example, on the fact that one or more configuration parameters do not include enabled CSI multiplex mode parameters.

[0313] One or more wireless devices may multiplex CSI reports (or other information) in repeated push transmissions based, for example, on the fact that one or more configuration parameters do not include CSI multiplex mode parameters. One or more wireless devices may multiplex CSI reports in repeated push transmissions based, for example, on the fact that one or more configuration parameters do not include CSI multiplex mode parameters that are enabled.

[0314] One or more wireless devices may transmit (e.g., transmit) a CSI report (or other information) on a transmission opportunity (or repeated push transmission) based, for example, on the fact that one or more configuration parameters do not include CSI multiplexed FDM mode parameters. One or more wireless devices may transmit (e.g., transmit) a CSI report on a transmission opportunity (or repeated push transmission) based, for example, on the fact that one or more configuration parameters do not include enabled CSI-multiplexed-FDM mode parameters.

[0315] One or more wireless devices may multiplex CSI reports in repeated push transmissions, for example, based on the fact that one or more configuration parameters do not include CSI multiplex FDM mode parameters.

[0316] One or more wireless devices may transmit (e.g., transmit) a CSI report (or other information) on a transmission opportunity (or a repetition of a PUSCH transmission) based on a PUSCH transmission that includes / carries uplink control information (UCI) different from the CSI report. One or more wireless devices may transmit (e.g., transmit) a CSI report on a transmission opportunity (or a repetition of a PUSCH transmission) based on multiplexing a UCI different from the CSI report in a PUSCH transmission. The UCI may include, for example, a HARQ-ACK. The UCI may include, for example, an SR.

[0317] One or more wireless devices may multiplex a CSI report (or other information) in a series of push transmissions based on a push transmission that includes / carries uplink control information (UCI) different from the CSI report. One or more wireless devices may multiplex a CSI report in a series of push transmissions based on multiplexing a UCI different from the CSI report in the push transmission. The UCI may include, for example, a HARQ-ACK. The UCI may include, for example, an SR.

[0318] One or more wireless devices may transmit (e.g., transmit) a CSI report (or other information) on a transmission opportunity (or a series of PUSCH transmissions) based, for example, on the basis that the UE capability message does not indicate support for transmitting (e.g., transmitting) / multiplexing a CSI report on / over at least two repetitions (or at least two transmission opportunities) of a PUSCH transmission. One or more wireless devices may transmit (e.g., transmit) a CSI report on a transmission opportunity (or a series of PUSCH transmissions) based, for example, on the basis that the UE capability message indicates support for transmitting (e.g., transmitting) / multiplexing a CSI report on / over at least one repetition (or a single transmission opportunity) of a PUSCH transmission.

[0319] One or more wireless devices may multiplex a CSI report (or other information) in a series of push transmissions, for example, based on the fact that the UE capability message does not indicate support for transmitting (e.g., transmitting) / multiplexing a CSI report in / on at least two series of push transmissions (or at least two transmission opportunities). One or more wireless devices may multiplex a CSI report in a series of push transmissions, for example, based on the fact that the UE capability message indicates support for transmitting (e.g., transmitting) / multiplexing a CSI report in / on a single series of push transmissions (or a single transmission opportunity).

[0320] One or more wireless devices may transmit (e.g., transmit) a CSI report (or other information) in a transmission opportunity (or a repetition of a push transmission) based on one or more configuration parameters that indicate a repetition scheme that is (or is set to be) a frequency domain repetition. One or more wireless devices may multiplex the CSI report in a repetition of a push transmission based on one or more configuration parameters that indicate a repetition scheme that is (or is set to be) a frequency domain repetition.

[0321] The first repetition (or first transmission opportunity) of a PUSCH transmission may begin with / in the first RB (or first PRB). The second repetition (or second transmission opportunity) of a PUSCH transmission may begin with / in the second RB (or second PRB).

[0322] A repeat of a PUSCH transmission (or transmission opportunity) may be a repeat (of the first and second repeats) having the lowest / highest starting frequency / RB among the first frequency / RB and the second frequency / RB. The starting frequency / RB of a repeat of a PUSCH transmission (or transmission opportunity) may be the lowest / highest among the first RB of the first repeat and the second RB of the second repeat. One or more wireless devices may transmit (e.g., transmit) a CSI report (or other information) in a transmission opportunity (or repeat of a PUSCH transmission) based, for example, that the starting frequency / RB of the repeat of a PUSCH transmission (or transmission opportunity) is the lowest / highest among the first RB of the first repeat and the second RB of the second repeat. One or more wireless devices may multiplex a CSI report in a repeat of a PUSCH transmission (or transmission opportunity) bas...

Claims

1. It is a method, By wireless devices, Transmission of uplink control information (UCI) via the physical uplink control channel (PUCCH), Receiving a frequency domain repeating scheme for physical uplink shared channel (PUSCH) transmission, Receiving downlink control information (DCI) that schedules the repetition of a frequency domain of a PUSCH transmission, wherein the repetition of the frequency domain includes a first repetition and a second repetition. A method comprising transmitting the UCI in a first repetition based on the frequency domain repetition of the PUCCH transmission which overlaps in time with the PUCCH transmission of the UCI, and based on the first repetition being associated with a value that satisfies a criterion.

2. Transmitting UCI in the first repetition described above is The one or more of the aforementioned configuration parameters indicate UCI multiplexing mode parameters that are not enabled, or The method according to claim 1, further relating to at least one of the following: one or more of the configuration parameters do not include UCI multiplexing mode parameters.

3. The method according to any one of claims 1 to 2, further comprising transmitting the second repetition with the same time period as the first repetition, wherein the UCI is multiplexed in the first repetition and the UCI is not multiplexed in the second repetition.

4. The method according to any one of claims 1 to 3, further comprising transmitting each of the repetitions of the frequency domain of the PUSCH transmission at multiple transmission opportunities in different frequency ranges, wherein each repetition of the frequency domain of the PUSCH transmission is transmitted by the wireless device at each of the multiple transmission opportunities.

5. Receiving a second DCI, The second UCI transmission, and The second DCI is received, and the frequency domain repetition of the second PUSCH transmission is scheduled. The method according to any one of claims 1 to 4, further comprising transmitting the second UCI in each of the frequency domain repetitions of the second PUSCH transmission, based on the validity of the UCI multiplexing mode parameter.

6. It is a method, Depending on the base station, Transmission of uplink control information (UCI) via the physical uplink control channel (PUCCH), and Receiving a frequency domain repeating scheme for physical uplink shared channel (PUSCH) transmission, Transmitting downlink control information (DCI) that schedules the repetition of a frequency domain of a PUSCH transmission, wherein the repetition of the frequency domain includes a first repetition and a second repetition. A method comprising receiving the UCI in the first repetition based on the frequency domain repetition of the PUCCH transmission which overlaps in time with the PUCCH transmission of the UCI, and based on the first repetition being associated with a value that satisfies a criterion.

7. Transmitting UCI in the first repetition described above is The one or more of the aforementioned configuration parameters indicate UCI multiplexing mode parameters that are not enabled, or The method according to claim 6, further relating to at least one of the following: one or more of the configuration parameters do not include UCI multiplexing mode parameters.

8. The method according to any one of claims 6 to 7, further comprising receiving the second repetition with the same time period as the first repetition, wherein the UCI is multiplexed in the first repetition and the UCI is not multiplexed in the second repetition.

9. The method according to any one of claims 6 to 8, further comprising receiving each of the repetitions of the frequency domain of the PUSCH transmission at multiple transmission opportunities in different frequency ranges, wherein each repetition of the frequency domain of the PUSCH transmission is received by the base station at each of the multiple transmission opportunities.

10. This involves transmitting a second DCI, The second UCI transmission, and The second DCI is transmitted to schedule the repetition of the second PUSCH transmission in the frequency domain, The method according to any one of claims 6 to 9, further comprising receiving the second UCI in each of the frequency domain repetitions of the second PUSCH transmission, based on the validity of the UCI multiplexing mode parameter.

11. Each repetition of the frequency domain is associated with each of the multiple values, The criterion includes determining the minimum or maximum value among the plurality of values, and the plurality of values ​​includes the value that satisfies the criterion. The value associated with the first repetition is frequency, Resource block value, Transmit Configuration Indicator (TCI) status, TCI status index, Sounding Reference Signal (SRS) Resource Set Control resource set (CORESET) pool index, Transmit and Receive Point (TRP) index, Antenna panel, or The method according to any one of claims 1 to 10, wherein at least one of the antenna panel indices is shown.

12. The aforementioned UCI, Hybrid Automated Repetitive Request Acknowledgment (HARQ-ACK), Channel Status Information (CSI) report, and The method according to any one of claims 1 to 11, comprising at least one of a scheduling request (SR).

13. A computing device, One or more processors, A computing device comprising: a memory that, when executed by one or more processors, stores instructions causing the computing device to perform the method according to any one of claims 1 to 12.

14. It is a system, A wireless device configured to carry out the method according to any one of claims 1 to 5, or, in the case of being dependent on the method according to claim 1, the method according to any one of claims 11 to 12, A system comprising a base station configured to implement the method according to any one of claims 6 to 10, or, if dependent on claim 6, the method according to any one of claims 11 to 12.

15. A computer-readable medium storing instructions that, when executed, produce the performance of the method according to any one of claims 1 to 12.

16. It is a method, The wireless device receives one or more configuration parameters, including uplink control information (UCI) multiplexing mode parameters, and a frequency domain repeating scheme for physical uplink shared channel (PUSCH) transmission, Receiving downlink control information (DCI) that schedules the repetition of a frequency domain of a PUSCH transmission, wherein the repetition of the frequency domain includes a first repetition and a second repetition. A method comprising transmitting the UCI in one of the first or second iterations based on one or more configuration parameters indicating that UCI multiplexing is not enabled, wherein the selection of the first or second iteration for transmitting the UCI is based on an index associated with one of the first or second iterations and satisfies the criteria.

17. The method according to claim 16, wherein transmitting the UCI involves transmitting the UCI in the first iteration based on the first iteration including the lowest index of a plurality of indices including a first index associated with the first iteration and a second index associated with the second iteration.

18. Each repetition of the frequency domain is associated with each index of a plurality of indices, and the plurality of indices includes the index that satisfies the criterion, The transmission of the UCI is within the first iteration based on the index associated with the first iteration being the lowest or highest index among the plurality of indices. The aforementioned criteria include determining the lowest index or the highest index among the plurality of indices, The index that satisfies the above criteria is TCI status index, or The method according to claim 17, wherein at least one of the antenna panel indices is shown.

19. The method according to any one of claims 17 to 18, further comprising transmitting the second repetition with the same time period as the first repetition, wherein the UCI is multiplexed in the first repetition and the UCI is not multiplexed in the second repetition.

20. The aforementioned UCI, Hybrid Automated Repetitive Request Acknowledgment (HARQ-ACK), Channel Status Information (CSI) report, and The method according to any one of claims 17 to 19, comprising at least one of a scheduling request (SR).

21. The method according to any one of claims 17 to 20, further comprising transmitting each of the repetitions of the frequency domain of the PUSCH transmission in multiple transmission opportunities in different frequency ranges and overlapping in time, wherein each repetition of the frequency domain of the PUSCH transmission is transmitted by the wireless device in each of the multiple transmission opportunities.

22. Receiving notification of a change in the UCI multiplexing mode parameter from an inactive state to an enabled state, Receiving the indication of the change in the UCI multiplexing mode parameters, and then receiving a second DCI, The second UCI transmission, and The second DCI is received, and the frequency domain repetition of the second PUSCH transmission is scheduled. The method according to any one of claims 17 to 21, comprising transmitting the second UCI in each of the frequency domain repetitions of the second PUSCH transmission, based on the UCI multiplexing mode parameter being enabled.

23. A computing device, One or more processors, A computing device comprising: a memory that, when executed by one or more processors, stores instructions causing the computing device to perform the method according to any one of claims 17 to 22.

24. It is a system, A wireless device configured to perform the method described in any one of claims 17 to 22, A system comprising a base station configured to transmit one or more of the aforementioned configuration parameters.

25. A computer-readable medium that stores instructions that, when executed, produce the performance of the method according to any one of claims 17 to 22.

26. It is a method, Depending on the base station, Uplink control information (UCI) multiplexing mode parameters, Transmission of uplink control information (UCI) via the physical uplink control channel (PUCCH), A frequency domain repeating scheme for physical uplink shared channel (PUSCH) transmission, Transmitting downlink control information (DCI) that schedules the repetition of a frequency domain of a PUSCH transmission, wherein the repetition of the frequency domain includes a first repetition and a second repetition. A method comprising receiving the UCI in one of the first or second iterations based on one or more configuration parameters indicating that UCI multiplexing is not enabled, wherein the reception of the UCI in the first or second iteration is based on an index associated with one of the first or second iterations and satisfies a criterion.

27. Each repetition of the frequency domain is associated with each index of a plurality of indices, and the plurality of indices includes the index that satisfies the criterion, Receiving the UCI is within the first iteration based on the index associated with the first iteration being the lowest or highest index among the plurality of indices, The aforementioned criteria include determining the lowest index or the highest index among the plurality of indices, The index that satisfies the above criteria is TCI status index, or The method according to claim 26, wherein at least one of the antenna panel indices is shown.

28. The method according to any one of claims 26 to 27, further comprising transmitting the second repetition with the same time period as the first repetition, wherein the UCI is multiplexed in the first repetition and the UCI is not multiplexed in the second repetition.

29. The aforementioned UCI, Hybrid Automated Repetitive Request Acknowledgment (HARQ-ACK), Channel Status Information (CSI) report, and The method according to any one of claims 26 to 28, comprising at least one of a scheduling request (SR).

30. The method according to any one of claims 26 to 29, further comprising receiving each of the repetitions of the frequency domain of the PUSCH transmission at multiple reception opportunities in different frequency ranges and overlapping in time, wherein each repetition of the frequency domain of the PUSCH transmission is received by the base station at each of the multiple reception opportunities.

31. Sending a notification indicating the change of the UCI multiplexing mode parameter from an inactive state to an enabled state, After transmitting the indication of the change in the UCI multiplexing mode parameters, transmit a second DCI, The second UCI transmission, and The second DCI is transmitted to schedule the repetition of the second PUSCH transmission in the frequency domain, The method according to any one of claims 26 to 30, comprising receiving the second UCI within each of the frequency domain repetitions of the second PUSCH transmission, based on the activation of the UCI multiplexing mode parameter.

32. A computing device, One or more processors, A computing device comprising: a memory that, when executed by one or more processors, stores instructions causing the computing device to perform the method according to any one of claims 26 to 31.

33. It is a system, A wireless device configured to perform the method described in any one of claims 26 to 31, A system comprising a base station configured to transmit one or more of the aforementioned configuration parameters.

34. A computer-readable medium that stores instructions that, when executed, produce the performance of the method according to any one of claims 26 to 31.

35. It is a method, The wireless device receives one or more configuration parameters associated with the frequency domain repetition of a physical uplink shared channel (PUSCH) transmission, Receiving downlink control information (DCI), wherein the DCI is Includes a Channel Status Information (CSI) request field indicating the submission of a CSI report, Scheduling the repetition of the frequency domain of a push transmission, wherein the repetition of the frequency domain includes a first repetition of a first frequency range that temporally overlaps with a second repetition of a second frequency range. A method comprising: transferring the CSI report in the first iteration based on the fact that the first iteration is associated with a value that satisfies a criterion.

36. In the first iteration, the transmission of the CSI report is The one or more of the aforementioned configuration parameters include CSI multiplexing mode parameters that are not enabled, or The method according to claim 35, further relating to at least one of the following: one or more of the configuration parameters do not include CSI multiplexing mode parameters.

37. Each repetition of the frequency domain is associated with a value of a plurality of values, and the plurality of values ​​include the value that satisfies the criterion. The aforementioned criteria include determining the lowest or highest value among the plurality of values, The value associated with the first repetition is frequency, Resource block value, Transmit Configuration Indicator (TCI) status, TCI status index, Sounding Reference Signal (SRS) Resource Set Control resource set (CORESET) pool index, Transmit and Receive Point (TRP) index, Antenna panel, or The method according to any one of claims 35 to 36, wherein at least one of the antenna panel indices is shown.

38. The method according to any one of claims 35 to 37, further comprising transmitting the second iteration with the same time period as the first iteration, wherein the CSI report is multiplexed in the first iteration and the CSI report is not multiplexed in the second iteration.

39. The aforementioned CSI report, Non-periodic CSI report, or The method according to any one of claims 35 to 38, comprising at least one of a semi-permanent CSI report.

40. The method according to any one of claims 35 to 39, wherein the CSI request field includes information for scheduling the transmission of the CSI report.

41. The method according to any one of claims 35 to 40, further comprising transmitting each of the repetitions of the frequency domain of the PUSCH transmission in multiple transmission opportunities in different frequency ranges and overlapping in time, wherein each repetition of the frequency domain of the PUSCH transmission is transmitted by the wireless device in each of the multiple transmission opportunities.

42. Receiving a second DCI configured to be scheduled, Sending the second CSI report, The second DCI is received, and the frequency domain repetition of the second PUSCH transmission is scheduled. The method according to any one of claims 35 to 41, comprising transmitting the second CSI report within each of the frequency domain repetitions of the second PUSCH transmission, based on the validity of the CSI multiplexing mode parameter.

43. A computing device, One or more processors, A computing device comprising: a memory that, when executed by one or more processors, stores instructions causing the computing device to perform the method according to any one of claims 35 to 42.

44. It is a system, A wireless device configured to perform the method described in any one of claims 35 to 42, A system comprising a base station configured to transmit one or more of the aforementioned configuration parameters.

45. A computer-readable medium that stores instructions that, when executed, produce the performance of the method according to any one of claims 35 to 42.

46. It is a method, Receiving one or more configuration parameters associated with frequency domain repetitions of a physical uplink shared channel (PUSCH) transmission by a wireless device, wherein the one or more configuration parameters include channel state information (CSI) multiplexing mode parameters. Receiving downlink control information (DCI) for scheduling repetitions of a frequency domain of a PUSCH transmission, wherein the repetition of the frequency domain includes a first repetition of a first frequency range that temporally overlaps with a second repetition of a second frequency range. A method comprising transmitting a CSI report in one of the first or second iterations based on one or more configuration parameters indicating that CSI multiplexing is not enabled, wherein the selection of the first or second iteration for transmitting the CSI report is based on an index associated with one of the first or second iterations and satisfies the criteria.

47. The method according to claim 46, wherein the DCI further includes a CSI request field for scheduling the transmission of the CSI report.

48. Each repetition of the frequency domain is associated with each index of a plurality of indices, and the plurality of indices includes the index that satisfies the criterion, The transmission of the CSI report is within the first iteration based on the fact that the index associated with the first iteration is the lowest or highest index among the plurality of indexes, The aforementioned criteria include determining the lowest index or the highest index among the plurality of indices, The index that satisfies the above criteria is TCI status index, or The method according to any one of claims 46 to 47, wherein at least one of the antenna panel indices is shown.

49. The method according to any one of claims 46 to 48, further comprising transmitting the second iteration at the same time period as the first iteration, wherein the CSI report is multiplexed in the first iteration and the CSI report is not multiplexed in the second iteration.

50. The aforementioned CSI report, Non-periodic CSI report, or The method according to any one of claims 46 to 49, comprising at least one of the semi-permanent CSI reports.

51. The method according to any one of claims 46 to 50, further comprising transmitting each of the repetitions of the frequency domain of the PUSCH transmission in multiple transmission opportunities in different frequency ranges and overlapping in time, wherein each repetition of the frequency domain of the PUSCH transmission is transmitted by the wireless device in each of the multiple transmission opportunities.

52. Receiving notification of a change in the CSI multiplexing mode parameter from an inactive state to an enabled state, Receiving the indication of the change in the CSI multiplexing mode parameters, and then receiving a second DCI, Sending the second CSI report, The second DCI is received, and the frequency domain repetition of the second PUSCH transmission is scheduled. The method according to any one of claims 46 to 51, comprising transmitting the second CSI report within each of the frequency domain repetitions of the second PUSCH transmission, based on the CSI multiplexing mode parameter being enabled.

53. A computing device, One or more processors, A computing device comprising: a memory that, when executed by one or more processors, stores instructions causing the computing device to perform the method according to any one of claims 46 to 52.

54. It is a system, A wireless device configured to perform the method described in any one of claims 46 to 52, A system comprising a base station configured to transmit one or more of the aforementioned configuration parameters.

55. A computer-readable medium that stores instructions that, when executed, produce the performance of the method according to any one of claims 46 to 52.

56. It is a method, The base station transmits one or more configuration parameters associated with frequency domain repetitions of a physical uplink shared channel (PUSCH) transmission, wherein the one or more configuration parameters include channel state information (CSI) multiplexing mode parameters. Transmitting downlink control information (DCI) for scheduling repetitions of frequency domains of PUSCH transmission, wherein the repetitions of the frequency domain include a first repetition of a first frequency range that temporally overlaps with a second repetition of a second frequency range. A method comprising receiving a CSI report in one of the first or second iterations based on one or more configuration parameters indicating that CSI multiplexing is not enabled, wherein the reception of the CSI report in the first or second iteration is based on an index associated with one of the first or second iterations and satisfies the criteria.

57. Each iteration of the frequency domain is associated with each index of a plurality of indices, The receipt of the CSI report is within the first iteration based on the fact that the index associated with the first iteration is the lowest or highest index among the plurality of indexes, The aforementioned criteria include determining the lowest index or the highest index among the plurality of indices, The index associated with the first repetition is TCI status index, or The method according to claim 56, wherein at least one of the antenna panel indices is shown.

58. The method according to any one of claims 56 to 57, further comprising receiving the second iteration at the same time period as the first iteration, wherein the CSI report is multiplexed in the first iteration and the CSI report is not multiplexed in the second iteration.

59. The method according to any one of claims 56 to 58, further comprising receiving each of the repetitions of the frequency domain of the PUSCH transmission at multiple reception opportunities in different frequency ranges and overlapping in time, wherein each repetition of the frequency domain of the PUSCH transmission is received by the base station at each of the multiple reception opportunities.

60. Sending a notification indicating the change in the CSI multiplexing mode parameter from an inactive state to an enabled state, After transmitting the indication of the change in the CSI multiplexing mode parameters, transmit a second DCI, Sending the second CSI report, Transmitting a second DCI, configured to schedule frequency domain repetitions of a second PUSCH transmission, The method according to any one of claims 56 to 59, comprising receiving the second CSI report within each of the frequency domain repetitions of the second PUSCH transmission, based on the CSI multiplexing mode parameter being enabled.

61. A computing device, One or more processors, A computing device comprising: a memory that, when executed by one or more processors, stores instructions causing the computing device to perform the method according to any one of claims 56 to 60.

62. It is a system, A wireless device configured to perform the method described in any one of claims 56 to 60, A system comprising a base station configured to transmit one or more of the aforementioned configuration parameters.

63. A computer-readable medium that stores instructions that, when executed, produce the performance described in any one of the clauses 56 to 60.

64. It is a method, The wireless device receives downlink control information (DCI) that schedules repeated transmissions of a first physical uplink shared channel (PUSCH), The repetition of the first PUSCH transmission is within the frequency domain. Each of the aforementioned repetitions is associated with a Transmit Configuration Indicator (TCI) state among a plurality of TCI states, The repetition of the first push transmission is based on temporal overlap with a second push transmission, which includes a power headroom report that determines the power headroom report using a path loss reference signal associated with a TCI state, among a plurality of TCI states, indicated by the lowest TCI state index among the TCI state indices of each TCI state associated with the repetition of the first push transmission. A method including transmitting the aforementioned power headroom report.

65. The method according to claim 64, wherein each repetition of the first PUSCH transmission is associated with each of the multiple path loss reference signals, and each of the multiple path loss reference signals is associated with each of the multiple TCI states.

66. Based on the first TCI state, transmit the first repetition of the first PUSCH transmission, The method according to any one of claims 64 to 65, further comprising transmitting a second repetition of the repetition of the first PUSCH transmission based on a second TCI state.

67. Determining the power headroom report using the aforementioned path loss reference signal, Receiving a power headroom mode parameter indicating that a single power headroom mode is enabled, The method according to any one of claims 64 to 66, based on at least one of the determinations that two power headroom report mode parameters have not been received.

68. Receiving an indication that activates at least two TCI states, including the aforementioned TCI state, Transmitting the first repetition of the first PUSCH transmission, Using a spatial domain transmit filter determined based on the first TCI state among the at least two TCI states, The method according to any one of claims 64 to 67, further comprising using a transmit power determined based on a path loss reference signal indicated by the first TCI state.

69. The method according to any one of claims 64 to 68, further comprising determining the path loss reference signal associated with a first repetition of the first PUSCH transmission, wherein the determination of the path loss reference signal is based on the power headroom report, and the first repetition is associated with the same value of the TCI state index.

70. The method according to any one of claims 64 to 69, wherein the power headroom report includes a power headroom value determined using the path loss reference signal associated with the TCI state indicated by the lowest TCI state index.

71. A computing device, One or more processors, A computing device comprising: a memory that, when executed by one or more processors, stores instructions causing the computing device to perform the method according to any one of claims 64 to 70.

72. It is a system, A wireless device configured to perform the method described in any one of claims 64 to 70, A system comprising a base station configured to transmit the aforementioned DCI.

73. A computer-readable medium that stores instructions that, when executed, produce the performance of the method according to any one of claims 64 to 70.

74. It is a method, The wireless device receives downlink control information (DCI) that schedules frequency domain repetitions of a first physical uplink shared channel (PUCH) that temporally overlap with a second PUSCH transmission including a power headroom report, wherein each repetition is associated with a path loss reference signal of a plurality of path loss reference signals and a respective index of a plurality of indices. In the repetitions of the first PUSCH transmission, the power headroom report is determined using a path loss reference signal corresponding to the repetition, which is associated with the lowest index of each index of the repetitions. A method including transmitting the aforementioned power headroom report.

75. The aforementioned lowest index is, Transmit Configuration Indicator (TCI) Index, Antenna panel index, or The method according to claim 74, comprising at least one of the resource block locations.

76. The method according to any one of claims 74 to 75, wherein each of the plurality of path loss reference signals is associated with a transmit configuration indicator (TCI) state from among a plurality of TCI states, and each of the plurality of TCI states is associated with a TCI state index from among a plurality of TCI state indices.

77. Based on the first Transmit Configuration Indicator (TCI) state, transmit the first repetition of the first PUSCH transmission, The method according to any one of claims 74 to 76, further comprising transmitting a second repetition of the repetition of the first PUSCH transmission based on a second TCI state.

78. The method according to any one of claims 74 to 77, wherein the transmission of the power headroom report is based on receiving power headroom mode parameters indicating that a single power headroom mode is enabled.

79. Receiving an indication to activate at least two Transmit Configuration Indicator (TCI) states, Transmitting the first repetition of the first PUSCH transmission, Using a spatial domain transmit filter determined based on the first TCI state among the at least two TCI states, The method according to any one of claims 74 to 78, further comprising using a transmit power determined based on a path loss reference signal associated with the first TCI state.

80. The method according to any one of claims 74 to 79, further comprising determining the path loss reference signal corresponding to the repetition associated with the minimum index, wherein determining the path loss reference signal is based on the power headroom report and the repetition associated with the minimum index being associated with the same value of a transmit configuration indicator (TCI) state.

81. The method according to any one of claims 74 to 80, wherein the power headroom report includes a power headroom value determined using the path loss reference signal associated with a transmit configuration indicator (TCI) state indicated by the lowest TCI state index.

82. A computing device, One or more processors, A computing device comprising: a memory that, when executed by one or more processors, stores instructions causing the computing device to perform the method according to any one of claims 74 to 81.

83. It is a system, A wireless device configured to perform the method described in any one of claims 74 to 81, A system comprising a base station configured to transmit the aforementioned DCI.

84. A computer-readable medium that stores instructions that, when executed, produce the performance of the method according to any one of claims 74 to 81.

85. It is a method, The wireless device receives downlink control information (DCI) that schedules frequency domain repetitions of a first physical uplink shared channel (PUCH) that temporally overlap with a second PUSCH transmission including a power headroom report, wherein each repetition is associated with a path loss reference signal of a plurality of path loss reference signals and a respective index of a plurality of indices. A method comprising transmitting a power headroom value in the power headroom report, wherein the power headroom value is determined using a path loss reference signal corresponding to the repetition of the first PUSCH transmission, which is associated with the lowest index of each of the repetitions of the index.

86. The aforementioned lowest index is, Minimum Transmission Configuration Indicator (TCI) Index, Minimum Sounding Reference Signal (SRS) resource set, Minimum Controlled Resource Set (CORESET) Pool Index Minimum transmit and receive point (TRP) index, Minimum antenna panel index, or The method according to claim 85, which indicates at least one of the lowest resource block locations.

87. Determining the power headroom report using the aforementioned path loss reference signal, Receiving a power headroom mode parameter indicating that a single power headroom mode is enabled, The method according to any one of claims 85 to 86, based on at least one of the determinations that two power headroom report mode parameters have not been received.

88. The method according to any one of claims 85 to 87, further comprising determining the path loss reference signal corresponding to the repetition associated with the lowest index, wherein determining the path loss reference signal is based on the power headroom report and the repetition associated with the lowest index being associated with the same value of a transmit configuration indicator (TCI) state.

89. The method according to any one of claims 85 to 88, wherein the transmission of the power headroom report is based on receiving power headroom mode parameters indicating that a single power headroom mode is enabled.

90. A computing device, One or more processors, A computing device comprising: a memory that, when executed by one or more processors, stores instructions causing the computing device to perform the method according to any one of claims 85 to 89.

91. It is a system, A wireless device configured to perform the method described in any one of claims 85 to 89, A system comprising a base station configured to transmit the aforementioned DCI.

92. A computer-readable medium storing instructions that, when executed, produce the performance of the method described in any one of claims 85 to 89.

93. It is a method, The wireless device receives first downlink control information (DCI) that schedules a first uplink transmission in a first transmission opportunity, Receiving a second DCI that schedules a second uplink transmission in a second transmission opportunity that overlaps temporally with the first transmission opportunity, Determining that the total transmission power of the wireless device, including the first uplink transmission and the second uplink transmission, exceeds the maximum transmission power, One of the first uplink transmission and the second uplink transmission is, The determination that the total transmission power of the wireless device exceeds the maximum transmission power, and A method comprising: making a preference based on a comparison between a first value associated with the first uplink transmission and a second value associated with the second uplink transmission.

94. The method according to claim 93, wherein receiving the first DCI includes receiving the first DCI via a first control resource set (CORESET) associated with a first CORESET pool index, and receiving the second DCI includes receiving the second DCI via a second CORESET associated with a second CORESET pool index different from the first CORESET pool index, wherein the first value is the first CORESET pool index and the second value is the second CORESET pool index.

95. Prioritizing one of the first uplink transmission and the second uplink transmission is To reduce the transmit power associated with at least one of the first uplink transmit or the second uplink transmit, or The method according to any one of claims 93 to 94, comprising dropping at least one of the first uplink transmission or the second uplink transmission.

96. Prioritizing one of the first uplink transmission and the second uplink transmission is To reduce the transmit power associated with at least one layer of the first uplink transmit, or The method according to any one of claims 93 to 95, comprising dropping the transmission of at least one layer of the first uplink transmission.

97. The comparison between the first value associated with the first uplink transmission and the second value associated with the second uplink transmission is, frequency, Resource block value, Transmit Configuration Indicator (TCI) status, TCI status index, Sounding Reference Signal (SRS) Resource Set Control resource set (CORESET) pool index, Transmit and Receive Point (TRP) index, Antenna panel, or The method according to any one of claims 93 to 96, comprising determining the minimum or maximum of the antenna panel index.

98. The method according to any one of claims 93 to 97, further comprising transmitting the first uplink transmission based on the comparison that shows the first value is smaller than the second value.

99. Based on the comparison showing that the first value is smaller than the second value, the second uplink transmission is dropped, or The method according to any one of claims 93 to 98, comprising: transmitting the second uplink transmission using adjusted transmit power based on the comparison that the first value is smaller than the second value.

100. A computing device, One or more processors, A computing device comprising: a memory that, when executed by one or more processors, stores instructions causing the computing device to perform the method according to any one of claims 93 to 99.

101. It is a system, A wireless device configured to perform the method described in any one of claims 93 to 99, A system comprising a base station configured to transmit the first DCI.

102. A computer-readable medium that stores instructions that, when executed, produce the performance of the method according to any one of claims 93 to 99.

103. It is a method, The wireless device receives first downlink control information (DCI) that schedules a first uplink transmission in a first transmission opportunity, Receiving a second DCI that schedules a second uplink transmission in a second transmission opportunity that overlaps temporally with the first transmission opportunity, Determining that the total transmission power of the wireless device, including the first uplink transmission and the second uplink transmission, exceeds the maximum transmission power, Transmitting the aforementioned first uplink transmission, Transmitting the second uplink transmission using the adjusted transmit power, wherein the adjusted transmit power is The determination that the total transmission power of the wireless device exceeds the maximum transmission power, and A method comprising transmitting, based on the determination that a first value associated with the first uplink transmission is smaller than a second value associated with the second uplink transmission.

104. The method according to claim 103, wherein receiving the first DCI includes receiving the first DCI via a first control resource set (CORESET) associated with a first CORESET pool index, and receiving the second DCI includes receiving the second DCI via a second CORESET associated with a second CORESET pool index different from the first CORESET pool index, wherein the first value is the first CORESET pool index and the second value is the second CORESET pool index.

105. The method according to any one of claims 103 to 104, wherein the first value includes a first transmit configuration indicator (TCI) status index associated with the first uplink transmit, and the second value includes a second TCI status index associated with the second uplink transmit.

106. Using the adjusted transmission power, the second uplink transmission is transmitted. To reduce the transmit power associated with at least one layer of the second uplink transmit, or The method according to any one of claims 103 to 105, comprising dropping transmissions of at least one layer of the second uplink transmission.

107. The first value and the second value are different, frequency, Resource block value, Transmit Configuration Indicator (TCI) status, TCI status index, Antenna panel, or The method according to any one of claims 103 to 106, including an antenna panel index.

108. The method according to any one of claims 103 to 107, further comprising transmitting the first uplink transmission using a first uplink transmission power greater than the second uplink transmission power used to transmit the second uplink transmission.

109. A computing device, One or more processors, A computing device comprising: a memory that, when executed by one or more processors, stores instructions causing the computing device to perform the method according to any one of claims 103 to 108.

110. It is a system, A wireless device configured to perform the method described in any one of claims 103 to 108, A system comprising a base station configured to transmit the first DCI.

111. A computer-readable medium that stores instructions that, when executed, produce the performance of the method according to any one of claims 103 to 108.

112. It is a method, The wireless device receives first downlink control information (DCI) that schedules a first uplink transmission in a first transmission opportunity, Receiving a second DCI that schedules a second uplink transmission in a second transmission opportunity that overlaps temporally with the first transmission opportunity, Determining that the total transmission power of the wireless device, including the first uplink transmission and the second uplink transmission, exceeds the maximum transmission power, Based on the determination that the first value associated with the first uplink transmission is smaller than the second value associated with the second uplink transmission, Transmitting the aforementioned first uplink transmission, A method comprising transmitting the second uplink transmission using adjusted transmit power, or dropping the second uplink transmission.

113. The method according to claim 112, wherein receiving the first DCI includes receiving the first DCI via a first control resource set (CORESET) associated with a first CORESET pool index, and receiving the second DCI includes receiving the second DCI via a second CORESET associated with a second CORESET pool index different from the first CORESET pool index, wherein the first value is the first CORESET pool index and the second value is the second CORESET pool index.

114. The method according to any one of claims 112 to 113, wherein the first value includes a first transmit configuration indicator (TCI) status index associated with the first uplink transmit, and the second value includes a second TCI status index associated with the second uplink transmit.

115. Using the adjusted transmission power, the second uplink transmission is transmitted. To reduce the transmit power associated with at least one layer of the second uplink transmit, or The method according to any one of claims 112 to 114, comprising dropping the transmission of at least one layer of the second uplink transmission.

116. The first value and the second value are different, frequency, Resource block value, Transmit Configuration Indicator (TCI) status, TCI status index, Sounding Reference Signal (SRS) Resource Set Control resource set (CORESET) pool index, Transmit and Receive Point (TRP) index, Antenna panel, or The method according to any one of claims 112 to 115, comprising an antenna panel index.

117. The method according to any one of claims 112 to 116, further comprising transmitting the first uplink transmission using a first uplink transmission power greater than the second uplink transmission power used to transmit the second uplink transmission.

118. The method according to any one of claims 112 to 117, further comprising dropping the second uplink transmission based on the determination that the first value associated with the first uplink transmission is smaller than the second value associated with the second uplink transmission.

119. A computing device, One or more processors, A computing device comprising: a memory that, when executed by one or more processors, stores instructions causing the computing device to perform the method according to any one of claims 112 to 118.

120. It is a system, A wireless device configured to perform the method described in any one of claims 112 to 118, A system comprising a base station configured to transmit the first DCI.

121. A computer-readable medium that stores instructions that, when executed, produce the performance of the method according to any one of claims 112 to 118.

Images