Resource configuration for overlapping transmissions

Abstract

A wireless device may communicate with a base station by using overlapping transmissions. A transmission, such as a physical uplink control channel (PUCCH) transmission (e.g., including uplink control information (UCI)), may be multiplexed in a repetition of a transmission, such as a physical uplink shared channel (PUSCH) transmission. Information, such as a channel state information (CSI) report, may be multiplexed in a repetition of a transmission, such as a physical uplink shared channel (PUSCH) transmission. Rules may be applied to indicate / determine which of the plurality of repetitions includes multiplexing information (e.g., which PUSCH repetition includes UCI). The rules may include including the multiplexing information in a transmission associated with at least one of: a lowest (or highest) frequency or range of frequencies, a lowest (or highest) start (or end) resource block, a lowest (or highest) transmission configuration indicator (TCI) state, a lowest (or highest) TCI state index, a lowest (or highest) panel or panel index, and a transmission associated with the lowest (or highest) TCI state index. And / or any other parameter / indicator that may distinguish transmissions (including the multiplexing information) from other transmissions. Transmission such as power headroom reporting may be multiplexed in transmissions such as physical uplink shared channel (PUSCH) transmissions. Rules may be applied to indicate / determine values / parameters associated with the transmission. For example, the rule may be used to indicate / determine a value of a power headroom report, which may indicate a pathloss reference signal used to determine the power headroom report. The rules may include indicating / determining a value / parameter associated with the transmission using at least one of: a lowest (or highest) frequency or range of frequencies, a lowest (or highest) start (or end) resource block, a lowest (or highest) transmission configuration indicator (TCI) state, a lowest (or highest) TCI state index, a lowest (or highest) panel or panel index, and a lowest (or highest) transmission configuration indicator (TCI) state index. And / or any other parameter / indicator transmitted may be distinguished. The overlapping transmissions may include multiple transmissions of the same type / channel, such as physical uplink shared channel (PUSCH) transmissions, physical uplink control channel (PUCCH) transmissions, and the like. Rules may be applied to indicate / determine a power prioritization for the overlapping transmissions. For example, a rule may be used to indicate which of the overlapping transmissions of the same type / channel (e.g., PUSCH, PUCCH, etc.) may be discarded or transmitted using reduced power if the overlapping transmissions would otherwise exceed a power threshold. The rules may include indicating / determining a power prioritization of overlapping transmissions based on at least one of: a lowest (or highest) frequency or range of frequencies, a lowest (or highest) start (or end) resource block, a lowest (or highest) transmission configuration indicator (TCI) state, a lowest (or highest) TCI state index, a lowest (or highest) panel or panel index, and a power prioritization of the overlapping transmissions based on at least one of the following: a lowest (or highest) frequency or range of frequencies, a lowest (or highest) start (or end) resource block, a lowest (or highest) transmission configuration indicator (TCI) state; and / or any other parameter / indicator of overlapping transmissions may be distinguished.

Description

[0001] Cross-reference to related applications

[0002] This application claims the benefit of U.S. Provisional Application No. 63 / 307,299, filed February 7, 2022, U.S. Provisional Application No. 63 / 307,301, filed February 7, 2022, U.S. Provisional Application No. 63 / 308,699, filed February 10, 2022, and U.S. Provisional Application No. 63 / 307,703, filed February 8, 2022. Each of the above-referenced applications is hereby incorporated by reference in its entirety. Background Art

[0003] Wireless communication involves repetition of transmissions to increase the likelihood of successful message reception. Transmission repetitions are performed using time division multiplexing. Summary of the Invention

[0004] The following summary presents a simplified summary of certain features. This summary is not an extensive overview and is not intended to identify key or critical elements.

[0005] A wireless device may communicate with a base station using overlapping transmissions. For example, overlapping transmissions may include using time division multiplexing (TDM), frequency division multiplexing (FDM), and / or spatial division multiplexing (SDM) for transmissions that overlap in time (e.g., using FDM and / or SDM), frequency (e.g., using TDM and / or SDM), and / or spatial domain (e.g., using TDM and / or FDM). The wireless device may use multiplexing to send repetitions of a message / transmission, which may increase the likelihood of successful reception. In at least some repetitions, the wireless device may multiplex information within the repeated message / transmission. The multiplexed information may include, for example, channel state information (CSI) reports multiplexed on repetitions of a physical uplink shared channel (PUSCH) transmission, physical uplink control channel (PUCCH) transmissions (e.g., including uplink control information (UCI)) multiplexed on repetitions of a PUSCH transmission, and / or any other information included in the transmission. The wireless device and the base station may apply rules to indicate / determine which repetition(s) of a plurality of repetitions include the multiplexed information so that the multiplexed information can be successfully transmitted. For example, the rule may include including the multiplexing information in a transmission associated with at least one of the following: a lowest (or highest) frequency or frequency range, a lowest (or highest) starting (or ending) resource block, a lowest (or highest) transmission configuration indicator (TCI) state, a lowest (or highest) TCI state index, a lowest (or highest) panel or panel index, and / or any other parameter / indicator that can distinguish a transmission (including the multiplexing information) from other transmissions. Additionally or alternatively, the wireless device and the base station may apply the rule to indicate / determine (e.g., using the lowest or highest frequency, the lowest / starting or highest / ending resource block, the lowest or highest TCI state or TCI state index, the lowest or highest panel or panel index, etc.) a value / parameter associated with a transmission, such as a value of a power headroom report, which may indicate a path loss reference signal used to determine the power headroom report (e.g., which in turn may indicate to which of a plurality of transmission and reception points the power headroom report corresponds). Additionally or alternatively, the rules may include power prioritization rules that may be applied by the wireless device and base station to indicate / determine power prioritization of transmissions that overlap in time (e.g., using the lowest or highest frequency, lowest / starting or highest / ending resource block, lowest or highest TCI state / TCI state index, lowest or highest panel / panel index, etc.), wherein the power prioritization rules may indicate which of multiple transmissions of the same type / channel (e.g., PUSCH, PUCCH, etc.) may be dropped or transmitted with reduced power if the multiple transmissions would otherwise exceed a power threshold (e.g., the maximum transmit power of the wireless device). By establishing one or more rules for overlapping transmissions as described herein, advantages may result, such as increased synchronization between the wireless device and the base station, reduced retransmissions, reduced latency, and / or reduced power consumption.

[0006] These and other features and advantages are described in more detail below. BRIEF DESCRIPTION OF THE DRAWINGS

[0007] In the accompanying drawings, some features are illustrated by way of example and not limitation. Like reference numerals refer to similar elements throughout the figures.

[0008] Figure 1A and Figure 1B An exemplary communication network is shown.

[0009] Figure 2A An exemplary user plane is shown.

[0010] Figure 2B An exemplary control plane configuration is shown.

[0011] Figure 3 An example of protocol layers is shown.

[0012] Figure 4A An exemplary downlink data flow for user plane configuration is shown.

[0013] Figure 4B An exemplary format of a Medium Access Control (MAC) subheader in a MAC protocol data unit (PDU) is shown.

[0014] Figure 5A An exemplary mapping of downlink channels is shown.

[0015] Figure 5B An exemplary mapping of uplink channels is shown.

[0016] Figure 6 Exemplary radio resource control (RRC) states and RRC state transitions are shown.

[0017] Figure 7 An exemplary configuration of a frame is shown.

[0018] Figure 8 An exemplary resource configuration for one or more carriers is shown.

[0019] Figure 9 An exemplary configuration of a bandwidth part (BWP) is shown.

[0020] Figure 10A An exemplary component carrier based carrier aggregation configuration is shown.

[0021] Figure 10B An exemplary group of cells is shown.

[0022] Figure 11AAn exemplary mapping of one or more synchronization signal / physical broadcast channel (SS / PBCH) blocks is shown.

[0023] Figure 11B An exemplary mapping of one or more channel state information reference signals (CSI-RS) is shown.

[0024] Figure 12A An example of a downlink beam management procedure is shown.

[0025] Figure 12B An example of an uplink beam management procedure is shown.

[0026] Figure 13A An exemplary four-step random access procedure is shown.

[0027] Figure 13B An exemplary two-step random access procedure is shown.

[0028] Figure 13C An exemplary two-step random access procedure is shown.

[0029] Figure 14A An example of a control resource set (CORESET) configuration is shown.

[0030] Figure 14B An example of control channel element to resource element group (CCE to REG) mapping is shown.

[0031] Figure 15A An example of communication between a wireless device and a base station is shown.

[0032] Figure 15B Exemplary elements of a computing device are shown that may be used to implement any of the various devices described herein.

[0033] Figure 16A 、 Figure 16B 、 Figure 16C and Figure 16D Examples of uplink and downlink signal transmission are shown.

[0034] Figure 17 An exemplary TCI status update is shown.

[0035] Figure 18 An example of an uplink repetition scheme is shown.

[0036] Figure 19 An example of report multiplexing is shown.

[0037] Figure 20 An example of report multiplexing is shown.

[0038] Figure 21A and Figure 21B An example of report multiplexing is shown.

[0039] Figure 22 An example of uplink control information multiplexing is shown.

[0040] Figure 23 An example of uplink control information multiplexing is shown.

[0041] Figure 24A and Figure 24B An example of uplink control information multiplexing is shown.

[0042] Figure 25 An example of unified beam updating is shown.

[0043] Figure 26 An example of a power headroom report (PHR) is shown.

[0044] Figure 27A and Figure 27B An example of a PHR is shown.

[0045] Figure 28A and Figure 28B An example of a PHR is shown.

[0046] Figure 29A and Figure 29B An example of a PHR is shown.

[0047] Figure 30 An example of power prioritization is shown.

[0048] Figure 31 An example of power prioritization is shown.

[0049] Figure 32 An example of power prioritization is shown.

[0050] Figure 33 An example of power prioritization is shown. DETAILED DESCRIPTION

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

[0052] Figure 1AAn exemplary communication network 100 is shown. Communication network 100 may comprise a mobile communication network. Communication network 100 may comprise, for example, a public land mobile network (PLMN) operated / managed / run by a network operator. Communication network 100 may comprise one or more of a core network (CN) 102, a radio access network (RAN) 104, and / or wireless devices 106. Communication network 100 may comprise one or more data networks (DNs) 108, and / or devices within communication network 100 may communicate with the one or more data networks (e.g., via 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 RAN 104 and / or via CN 102. CN 102 may provide / configure one or more interfaces for wireless devices 106 to interface with one or more DNs 108. As part of the interface functionality, the CN 102 may set up an end-to-end connection between the wireless device 106 and one or more DNs 108, authenticate the wireless device 106, provide / configure charging functionality, and the like.

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

[0054] As used throughout, the term "wireless device" may include one or more of the following: a mobile device, a fixed (e.g., non-mobile) device configured or capable of using wireless communication, a computing device, a node, a device capable of wireless communication, or any other device capable of sending and / or receiving signals. As non-limiting examples, a wireless device may include, for example: a phone, a cellular phone, a Wi-Fi phone, a smartphone, a tablet, a computer, a laptop, a sensor, a meter, a wearable device, an Internet of Things (IoT) device, a hotspot, a cellular repeater, a vehicle roadside unit (RSU), a relay node, an automobile, a wireless user device (e.g., user equipment (UE), user terminal (UT), etc.), an access terminal (AT), a mobile station, a handset, a wireless transmit and receive unit (WTRU), a wireless communication device, and / or any combination thereof.

[0055] The RAN 104 may include one or more base stations (not shown). As used throughout, the term "base station" may include one or more of the following: a base station, a node, a Node B (NB), an evolved Node B (eNB), a gNB, an ng-eNB, a relay node (e.g., an integrated access and backhaul (IAB) node), a donor node (e.g., a donor eNB, a donor gNB, etc.), an access point (e.g., a Wi-Fi access point), a transmission and reception point (TRP), a computing device, a device capable of wireless communication, or any other device capable of sending and / or receiving signals. A base station may include one or more of each of the elements listed above. For example, a base station may include one or more TRPs. As other non-limiting examples, a base station may include, for example, one or more of: a Node B (e.g., associated with Universal Mobile Telecommunications System (UMTS) and / or third generation (3G) standards), an evolved Node B (eNB) (e.g., associated with Evolved Universal Terrestrial Radio Access (E-UTRA) and / or fourth generation (4G) standards), a remote radio head (RRH), a baseband processing unit coupled to one or more remote radio heads (RRHs), a relay node or relay node for extending the coverage area of ​​a donor node, a next generation evolved Node B (ng-eNB), a second generation Node B (gNB) (e.g., associated with NR and / or fifth generation (5G) standards), an access point (AP) (e.g., associated with, for example, Wi-Fi or any other suitable wireless communication standard), any other generation base station, and / or any combination thereof. A base station may include one or more devices, such as at least one base station central device (e.g., a gNB central unit (gNB-CU)) and at least one base station distributed device (e.g., a gNB distributed unit (gNB-DU)).

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

[0057] One or more base stations (e.g., in the RAN 104) may be implemented as sectored sites with more or less than three sectors. One or more base stations of the RAN 104 may be implemented as access points, baseband processing devices / units coupled to several RRHs, and / or repeaters or relay nodes for extending the coverage area of ​​a node (e.g., a donor node). The baseband processing devices / units coupled to the RRHs may be part of a centralized or cloud RAN architecture, for example, where the baseband processing devices / units may be centralized in a pool of baseband processing devices / units or virtualized. The relay node may amplify and transmit (e.g., transmit, retransmit, rebroadcast, etc.) a radio signal received from the donor node. The relay node may perform substantially the same / similar functions as a relay node. The relay node may decode the radio signal received from the donor node, for example, to remove noise before amplifying and transmitting the radio signal.

[0058] The RAN 104 may be deployed as a homogeneous network of base stations (e.g., macrocell base stations) with similar antenna patterns and / or similar high levels of transmit power. The RAN 104 may 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 may be used to provide / configure small coverage areas, e.g., coverage areas that overlap with relatively larger coverage areas provided / configured by other base stations (e.g., macrocell base stations). Small coverage areas may be provided / configured in areas with high data traffic (or so-called "hotspots") or in areas with weak macrocell coverage. Examples of small cell base stations may include (in descending order of coverage area) microcell base stations, picocell base stations, and femtocell base stations or home base stations.

[0059] The examples described herein can be used for various types of communications. For example, communications can be based on the Third Generation Partnership Project (3GPP) (e.g., one or more network elements similar to the network elements of the communication network 100), communications according to the Institute of Electrical and Electronics Engineers (IEEE), communications according to the International Telecommunication Union (ITU), communications according to the International Organization for Standardization (ISO), etc. 3GPP has established specifications for multiple generations of mobile networks: a 3G network known as UMTS, a 4G network known as Long Term Evolution (LTE) and Advanced LTE (LTE-A), and a 5G network known as a 5G system (5GS) and a NR system. 3GPP can develop specifications for additional generations of communication networks (e.g., 6G and / or any other generation of communication networks). Examples can be described with reference to one or more elements (e.g., RAN) of a 3GPP 5G network (referred to as the Next Generation RAN (NG-RAN)) or any other communication network (such as a 3GPP network and / or a non-3GPP network). The examples described herein may be applicable to other communication networks, such as 3G and / or 4G networks, as well as communication networks that may not yet be finalized / specified (e.g., 3GPP 6G networks), satellite communication networks, and / or any other communication networks. NG-RAN implements and updates the 5G radio access technology known as NR and may be configured to implement 4G radio access and / or other radio access technologies, such as other 3GPP and / or non-3GPP radio access technologies.

[0060] Figure 1B An exemplary communication network 150 is shown. The communication network may include a mobile communication network. The communication network 150 may include, for example, a PLMN operated / managed / run by a network operator. The communication network 150 may include one or more of the following: a CN 152 (e.g., a 5G core network (5G-CN)), a RAN 154 (e.g., an NG-RAN), and / or radios 156A and 156B (collectively, radios 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 (e.g., via the CN 152) the one or more data networks. These components may be configured to communicate with respect to Figure 1A The corresponding components are implemented and operate in substantially the same or similar manner.

[0061] The CN 152 (e.g., 5G-CN) may provide / configure one or more interfaces for wireless devices 156 to interface with one or more DNs 170 (such as public DNs (e.g., the Internet), private DNs, and / or intra-carrier DNs). As part of the interface functionality, the CN 152 (e.g., 5G-CN) may set up an end-to-end connection between the wireless device 156 and the one or more DNs, authenticate the wireless device 156, and / or provide / configure charging functionality. The CN 152 (e.g., 5G-CN) may be a service-based architecture that may differ from other CNs (e.g., such as 3GPP 4G CNs). The architecture of a node of the CN 152 (e.g., 5G-CN) may be defined as a network function that provides services to other network functions via interfaces. The network functions of the CN 152 (e.g., 5G CN) may be implemented in a number of 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).

[0062] The 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 of the AMF / UPF device 158. The UPF device 158B may serve as a gateway between the RAN 154 (e.g., NG-RAN) and one or more DNs 170. The UPF device 158B may perform functions such as packet routing and forwarding, packet inspection and user plane policy rule enforcement, traffic usage reporting, uplink classification to support routing of traffic flows to one or more DNs 170, user plane quality of service (QoS) processing (e.g., packet filtering, gating, uplink / downlink rate enforcement, and uplink traffic verification), downlink packet buffering, and / or downlink data notification triggering. The UPF device 158B may serve as an anchor point for intra- and inter-radio access technology (RAT) mobility, an external protocol (or packet) data unit (PDU) session point interconnecting one or more DNs, and / or a branch point to support multi-homed PDU sessions. The wireless device 156 may be configured to receive services via a PDU session, which may be a logical connection between the wireless device and the DN.

[0063] The AMF device 158A may perform functions such as: non-access stratum (NAS) signaling termination, NAS signaling security, access stratum (AS) security control, CN inter-node signaling for mobility between access networks (e.g., 3GPP access networks and / or non-3GPP networks), idle mode wireless device reachability (e.g., idle mode UE reachability for controlling and performing paging retransmissions), registration area management, intra-system and inter-system mobility support, access authentication, access authorization including roaming rights check, mobility management control (e.g., subscription and policy), network slicing support, and / or session management function (SMF) selection. NAS may refer to functions running between the CN and the wireless device, and AS may refer to functions running between the wireless device and the RAN.

[0064] CN 152 (e.g., 5G-CN) may be included in Figure 1B One or more additional network functions that may not be shown in the figure. CN 152 (e.g., 5G-CN) may include one or more devices that implement at least one of the following: 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.

[0065] The RAN 154 (e.g., NG-RAN) can communicate with the wireless device 156 via radio communication (e.g., over an air interface). The wireless device 156 can communicate with the CN 152 via the RAN 154. The RAN 154 (e.g., NG-RAN) can include one or more first-type base stations (e.g., gNBs including gNB 160A and gNB 160B (collectively, gNB 160)) and / or one or more second-type base stations (e.g., ng-eNBs including ng-eNB 162A and ng-eNB 162B (collectively, ng-eNB 162)). The RAN 154 can include one or more of any number of types of base stations. The gNB 160 and ng-eNB 162 can be referred to as base stations. The base stations (e.g., gNB 160 and ng-gNB 162) can include one or more antennas for wirelessly communicating with the wireless device 156 (e.g., over an air interface). One or more base stations (e.g., gNB 160 and / or ng-eNB 162) may include multiple antenna groups to control multiple cells (or sectors), respectively. The cells of the base stations (e.g., gNB 160 and ng-eNB 162) may provide radio coverage to wireless devices 156 over a wide geographic area to support wireless device mobility.

[0066] A base station (e.g., gNB 160 and / or ng-eNB 162) may be connected to CN 152 (e.g., 5G CN) via a first interface (e.g., NG interface) and to other base stations via a second interface (e.g., Xn interface). The NG and Xn interfaces may be established using direct physical connections and / or indirect connections through an underlying transport network (such as an Internet Protocol (IP) transport network). A base station (e.g., gNB 160 and / or ng-eNB 162) may communicate with wireless device 156 via a third interface (e.g., Uu interface). A base station (e.g., gNB 160A) may communicate with wireless device 156A via a Uu interface. The NG, Xn, and Uu interfaces may be associated with protocol stacks. The protocol stacks associated with the interfaces may be configured by Figure 1B The network elements shown in FIG are used 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 (e.g., in a protocol stack) may be used. The user plane may process data of interest to the user. The control plane may process signaling messages of interest to the network elements.

[0067] 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 and / or connect with UPF 158B of AMF / UPF 158 via an NG user plane (NG-U) interface. The NG-U interface may provide / perform delivery (e.g., non-guaranteed 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 communicate and / or connect with an AMF device (e.g., AMF 158A) via an 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), transmission of NAS messages, paging, PDU session management, configuration transfer, and / or warning message transmission.

[0068] The wireless device may access the base station via an interface (e.g., a Uu interface) for user plane configuration and control plane configuration. The base station (e.g., gNB 160) may provide user plane and control plane protocol terminals to the wireless device 156 via the Uu interface. The base station (e.g., gNB 160A) may provide user plane and control plane protocol terminals to the wireless device 156A via the Uu interface associated with the first protocol stack. The base station (e.g., ng-eNB 162) may provide Evolved UMTS Terrestrial Radio Access (E UTRA) user plane and control plane protocol terminals (e.g., where E UTRA may refer to 3GPP 4G radio access technology) to the wireless device 156 via the Uu interface. The base station (e.g., ng-eNB 162B) may provide Evolved UMTS Terrestrial Radio Access (E UTRA) user plane and control plane protocol terminals to the wireless device 156B via the Uu interface associated with the second protocol stack. The user plane and control plane protocol terminals may include, for example, NR user plane and control plane protocol terminals, 4G user plane and control plane protocol terminals, etc.

[0069] The CN 152 (e.g., 5G-CN) can be configured to handle one or more radio accesses (e.g., NR, 4G, and / or any other radio access). The NR network / device (or any first network / device) can also be connected to the 4G core network / device (or any second network / device) in a non-standalone mode (e.g., non-standalone operation). In the non-standalone mode / operation, the 4G core network can be used to provide (or at least support) control plane functions (e.g., initial access, mobility, and / or paging). Although Figure 1B Only one AMF / UPF 158 is shown, but 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.

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

[0071] Figure 1A The communication network 100 and / or Figure 1BThe communication network 150 in the present disclosure may include any quantity / number and / or type 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., UE). Although reference may be made herein to one or more of the aforementioned types of devices (e.g., UE, wireless device, computing device, etc.), it should be understood that any device herein may include any one or more of the aforementioned types of devices or similar devices. The communication network and any other networks mentioned herein may include an LTE network, a 5G network, a satellite network, and / or any other network 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 on one or more devices (e.g., wireless devices, base stations, eNBs, gNBs, computing devices, etc.) in one or more networks, but it should be understood that one or more features and steps may be implemented in any device and / or any network.

[0072] Figure 2A An exemplary user plane configuration is shown. The user plane configuration may include, for example, an NR user plane protocol stack. Figure 2B An exemplary control plane configuration is shown. The control plane configuration may include, for example, an NR control plane protocol stack. One or more of the user plane configuration and / or the control plane configuration may utilize a Uu interface that may be located between the wireless device 210 and the base station 220. Figure 2A and Figure 2B The protocol stack shown in can be used with e.g. Figure 1B The protocol stack of the Uu interface between the wireless device 156A and the base station 160A shown in FIG. 1 is substantially the same or similar.

[0073] The user plane configuration (e.g., NR user plane protocol stack) may be included in the wireless device 210 and the base station 220 (e.g., Figure 2AThe protocol stack may include multiple layers (e.g., five layers or any other number of layers) implemented in the protocol stack (as shown). At the bottom of the protocol stack, physical layers (PHY) 211 and 221 may provide transport services to higher layers of the protocol stack and may correspond to layer 1 of the open systems interconnection (OSI) model. Protocol layers above PHY 211 may include a media 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. Protocol layers above PHY 221 may include a media 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 above PHY 211 may correspond to layer 2, or the data link layer, of the OSI model. One or more of the four protocol layers above PHY 221 may correspond to layer 2, or the data link layer, of the OSI model.

[0074] Figure 3 An example of a protocol layer is shown. The protocol layer may include, for example, a protocol layer of the NR user plane protocol stack. One or more services may be provided between the protocol layers. SDAP (e.g., Figure 2A and Figure 3SDAPs 215 and 225 shown in FIG. 215 and 225 may perform quality of service (QoS) flow processing. A wireless device (e.g., wireless devices 106, 156A, 156B, and 210) may receive services through a PDU session, which may be a logical connection between the wireless device and a DN. The PDU session may have one or more QoS flows 310. The UPF of the CN (e.g., UPF 158B) may map IP packets to the one or more QoS flows of the PDU session, for example, based on one or more QoS requirements (e.g., based on latency, data rate, bit error rate, and / or any other quality / service requirements). SDAPs 215 and 225 may perform mapping / demapping between the one or more QoS flows 310 and one or more radio bearers 320 (e.g., data radio bearers). The mapping / demapping between the one or more QoS flows 310 and the radio bearers 320 may be determined by the SDAP 225 of the base station 220. The SDAP 215 of the wireless device 210 may be informed of the mapping between the QoS flows 310 and the radio bearers 320 via the reflective mapping and / or control signaling received from the base station 220. For the reflective mapping, the SDAP 225 of the base station 220 may mark downlink packets with a QoS flow indicator (QFI), which the SDAP 215 of the wireless device 210 may monitor / detect / identify / indicate / observe to determine the mapping / demapping between one or more QoS flows 310 and the radio bearers 320.

[0075] PDCP (e.g. Figure 2A and Figure 3 The PDCPs 214 and 224 (shown in FIG) may perform header compression / decompression, e.g., to reduce the amount of data that may need to be transmitted (e.g., sent) over the air interface, perform encryption / decryption to prevent unauthorized decoding of data transmitted (e.g., sent) over the air interface, and / or perform integrity protection (e.g., to ensure that control messages originate from the intended source). The PDCPs 214 and 224 may perform retransmission of undelivered packets, in-sequence delivery and reordering of packets, and / or removal of duplicated packets received due to, for example, handovers (e.g., intra-gNB handovers). The PDCPs 214 and 224 may perform packet duplication, e.g., to increase the likelihood that a packet will be received. A receiver may receive packets repeatedly and may remove any duplicate packets. Packet duplication may be used for certain services, such as those requiring high reliability.

[0076] The PDCP layer (e.g., PDCP 214 and 224) may perform mapping / demapping between separate radio bearers and RLC channels (e.g., RLC channel 330) (e.g., in a dual connectivity scenario / configuration). Dual connectivity may refer to a technology that allows a wireless device to communicate with multiple cells (e.g., two cells) or, more generally, multiple cell groups including a master cell group (MCG) and a secondary cell group (SCG). For example, if a single radio bearer (e.g., one of the radio bearers provided / configured by PDCP 214 and 224 as a service for SDAP 215 and 225) is handled by a cell group in dual connectivity, a separate bearer may be configured and / or used. PDCP 214 and 224 may map / demap between the separate radio bearer and the RLC channel 330 belonging to the cell group.

[0077] The RLC layer (e.g., RLC 213 and 223) can perform segmentation, retransmission via automatic repeat request (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) can support multiple transmission modes (e.g., three transmission modes: transparent mode (TM); unacknowledged mode (UM); and acknowledged mode (AM)). The RLC layer can perform one or more of the functions described, for example, based on the transmission mode in which the RLC layer is operating. The RLC configuration can be for each logical channel. The RLC configuration may not depend on a parameter set and / or a transmission time interval (TTI) duration (or other duration). The RLC layer (e.g., RLC 213 and 223) can provide / configure an RLC channel as a service to the PDCP layer (e.g., PDCP 214 and 224, respectively), such as Figure 3 shown.

[0078] The MAC layer (e.g., MAC 212 and 222) may perform multiplexing / demultiplexing of logical channels and / or mapping between logical channels and transport channels. Multiplexing may include multiplexing data units / data portions belonging to the one or more logical channels into transport blocks (TBs) delivered to the PHY layer (e.g., PHY 211 and 221, respectively), and demultiplexing may include demultiplexing data units / data portions from the TBs delivered from the PHY layer. The MAC layer (e.g., MAC 222) of the base station may be configured to perform scheduling, scheduling information reporting, and / or priority handling between wireless devices via dynamic scheduling. Scheduling may be performed by the base station (e.g., base station 220 at MAC 222) for downlink and / or uplink. The MAC layer (e.g., MAC 212 and 222) may be configured to perform error correction via hybrid automatic repeat request (HARQ) (e.g., one HARQ entity per carrier in the case of carrier aggregation (CA)) and to perform priority handling between logical channels of the wireless device 210 via logical channel prioritization and / or padding. The MAC layer (e.g., MAC 212 and 222) may support one or more parameter sets and / or transmission timings. Mapping restrictions in logical channel prioritization may control the parameter sets and / or transmission timings that may be used by the logical channels. The MAC layer (e.g., MAC 212 and 222) may provide / configure the logical channel 340 as a service to the RLC layer (e.g., RLC 213 and 223).

[0079] The PHY layer (e.g., PHY 211 and 221) can perform mapping of transport channels to physical channels and / or digital and analog signal processing functions, for example, for transmitting and / or receiving information (e.g., via an air interface). The digital and / or analog signal processing functions may include, for example, encoding / decoding and / or modulation / demodulation. The PHY layer (e.g., PHY 211 and 221) can perform multi-antenna mapping. The PHY layer (e.g., PHY 211 and 221) can 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).

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

[0081] For example, if SDAP 225 receives three IP packets (or other number of IP packets) from one or more QoS flows and maps the three packets (or other number of packets) to radio bearers (e.g., radio bearers 402 and 404), then downlink data flow may begin. 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. SDAP header (in Figure 4A Each SDAP SDU shown in FIG is marked with an "H" before it) can be added to an IP packet to generate an SDAP PDU, which can be called a PDCP SDU. A data unit transmitted from / to a higher protocol layer can be called a service data unit (SDU) of a lower protocol layer, and a data unit transmitted to / from a lower protocol layer can be called a PDU of a higher protocol layer. Figure 4A As shown, the data units from SDAP 225 may be SDUs of the lower protocol layer PDCP 224 (eg, PDCP SDUs), and may be PDUs of SDAP 225 (eg, SDAP PDUs).

[0082] Each protocol layer (e.g. Figure 4A ) or at least some of the protocol layers may: perform their own functions (e.g., Figure 3 ), adds a corresponding header, and / or forwards the corresponding output to the next lower layer (e.g., its corresponding lower layer). PDCP 224 may perform IP header compression and / or encryption. PDCP 224 may forward its output (e.g., PDCP PDU, which is an RLC SDU) to RLC 223. RLC 223 may optionally perform segmentation (e.g., as Figure 4A 223 may forward its output (e.g., two RLC PDUs, which are two MAC SDUs generated by adding corresponding subheaders to two SDU segments (SDU segments)) to MAC 222. MAC 222 may multiplex multiple RLC PDUs (MAC SDUs). MAC 222 may attach MAC subheaders to RLC PDUs (MAC SDUs) to form TBs. MAC subheaders may be distributed over MAC PDUs (e.g., as shown in FIG. Figure 4AThe NR configuration shown in FIG. 1 shows a MAC subheader located entirely at the beginning of the MAC PDU (e.g., in an LTE configuration). For example, if the MAC PDU subheader is calculated before assembling the full MAC PDU, the NR MAC PDU structure can reduce processing time and / or associated delays.

[0083] Figure 4B An exemplary format of a MAC subheader in a MAC PDU is shown. 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 for indicating the length (e.g., in bytes) of the MAC SDU to which the MAC subheader corresponds; a logical channel identifier (LCID) field for identifying / indicating the logical channel from which the MAC SDU originates to assist in demultiplexing processing; a flag (F) for indicating the size of the SDU length field; and a reserved bit (R) field for future use.

[0084] One or more MAC Control Elements (CEs) may be added or inserted into a MAC PDU by a MAC layer (such as MAC 223 or MAC 222). Figure 4B As shown, two MAC CEs can be inserted / added before two MAC PDUs. MAC CEs can be inserted / added at the beginning of a MAC PDU for downlink transmission (e.g. Figure 4B As shown). One or more MAC CEs may be inserted / added at the end of a MAC PDU for uplink transmission. MAC CEs may be used for in-band control signaling. Exemplary MAC CEs may include scheduling-related MAC CEs, such as buffer status reports and power headroom reports; activation / deactivation MAC CEs (e.g., activation / deactivation for PDCP duplicate detection, channel state information (CSI) reporting, sounding reference signal (SRS) transmission, and MAC CEs of previously configured components); discontinuous reception (DRX)-related MAC CEs; timing advance MAC CEs; and random access-related MAC CEs. The MAC CE may be preceded by a MAC subheader having a format similar to that described for the MAC subheader of a MAC SDU, and may be identified with a reserved value in the LCID field indicating the type of control information included in the corresponding MAC CE.

[0085] Figure 5A An exemplary mapping of downlink channels is shown. The mapping of uplink channels may include mapping between downlink channels (eg, logical channels, transport channels, and physical channels). Figure 5BAn exemplary mapping of uplink channels is shown. The mapping of uplink channels may include mappings between uplink channels (e.g., logical channels, transport channels, and physical channels). Information may be passed through / via channels between the RLC, MAC, and PHY layers of a protocol stack (e.g., an NR protocol stack). Logical channels may be used between the RLC and MAC layers. Logical channels may be classified / indicated as control channels that may carry control and / or configuration information (e.g., in the NR control plane), or traffic channels that may carry data (e.g., in the NR user plane). Logical channels may be classified / indicated as dedicated logical channels that may be dedicated to a specific wireless device, and / or common logical channels that may be used by more than one wireless device (e.g., a group of wireless devices).

[0086] A logical channel may be defined by the type of information it carries. The set of logical channels (e.g., in an NR configuration) may include one or more channels described below. A Paging Control Channel (PCCH) may include / carry one or more paging messages for paging a wireless device 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 a Master Information Block (MIB) and several System Information Blocks (SIBs). A wireless device may use the system information messages to obtain information about how a cell is configured and how to operate 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 to configure the wireless device with configuration information. A Dedicated Traffic Channel (DTCH) may include / carry user data to / from a specific wireless device.

[0087] Transport channels can be used between the MAC and PHY layers. Transport channels can be defined by how the information they carry is sent / transmitted (e.g., via an air interface). The set of transport channels (e.g., defined by an NR configuration or any other configuration) can include one or more of the following channels. Paging channel (PCH) can include / carry paging messages from PCCH. Broadcast channel (BCH) can include / carry MIB from BCCH. Downlink shared channel (DL-SCH) can include / carry downlink data and signaling messages, including SIB from BCCH. Uplink shared channel (UL-SCH) can include / carry uplink data and signaling messages. Random access channel (RACH) can provide wireless devices with access to the network without any previous scheduling.

[0088] The PHY layer can use physical channels to transfer / transmit information between processing layers of the PHY layer. A physical channel may have an associated set of time-frequency resources for carrying information of one or more transport channels. The PHY layer may generate control information to support the low-level operations of the PHY layer. The PHY layer may provide / transmit control information to the lower layers of the PHY layer via a physical control channel (e.g., referred to as an L1 / L2 control channel). The set of physical channels and physical control channels (e.g., defined by an NR configuration or any other configuration) may include one or more of the following channels. The physical broadcast channel (PBCH) may include / carry the MIB from the BCH. The physical downlink shared channel (PDSCH) may include / carry downlink data and signaling messages from the DL-SCH and paging messages from the PCH. The physical downlink control channel (PDCCH) may include / 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, and in some cases include 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), precoding matrix indicators (PMI), rank indicators (RI), and scheduling requests (SR). The physical random access channel (PRACH) may be used for random access.

[0089] The physical layer can generate physical signals to support the lower layer operations of the physical layer, which can be similar to physical control channels. Figure 5A and Figure 5B As shown, the physical layer signals (e.g., as defined by the NR configuration or any other configuration) 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 any other signals.

[0090] One or more of these 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 An exemplary control plane configuration (e.g., NR control plane protocol stack) is shown. Figure 2BAs shown, the control plane configuration (e.g., NR control plane protocol stack) may use one or more protocol layers (e.g., PHY 211 and 221, MAC 212 and 222, RLC 213 and 223, and PDCP 214 and 224) that are substantially the same as or similar to the exemplary user plane configuration (e.g., NR user plane protocol stack). The similar four 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 radio resource control (RRC) 216 and 226 and NAS protocols 217 and 237 at the upper layer of the control plane configuration (e.g., NR control plane protocol stack), for example, instead of SDAP 215 and 225. The control plane configuration may include an AMF 230 that includes a NAS protocol 237.

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

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

[0093] Figure 6 Example RRC states and RRC state transitions are shown. The RRC state of a wireless device may change to another RRC state (e.g., an RRC state transition of the wireless device). The wireless device may be substantially the same as or similar to wireless device 106, 210, or any other wireless device. The wireless device may be in at least one of a plurality of states, such as three RRC states, including RRC connected 602 (e.g., RRC_CONNECTED), RRC idle 606 (e.g., RRC_IDLE), and RRC inactive state 604 (e.g., RRC_INACTIVE). The RRC inactive state 604 may be when the RRC is connected but inactive.

[0094] An RRC connection may be established for the wireless device. For example, this may occur during an RRC connected state. During the RRC connected state (e.g., during RRC connected 602), the wireless 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 of the one or more base stations (e.g., Figure 1A One or more base stations of the RAN 104 are shown, Figure 1BOne of the gNB 160 or ng eNB 162 shown, Figure 2A and Figure 2B 20 or any other base station). A base station connected to a wireless device (e.g., having established an RRC connection) may have an RRC context for the wireless device. The RRC context may be referred to as a wireless device context (e.g., a UE context) and may include parameters for communication between the wireless device and the base station. These parameters may include, for example, one or more of: an AS context; radio link configuration parameters; bearer configuration information (e.g., related to data radio bearers, signaling radio bearers, logical channels, QoS flows, and / or PDU sessions); security information; and / or layer configuration information (e.g., PHY, MAC, RLC, PDCP, and / or SDAP layer configuration information). During an RRC connected state (e.g., RRC connected 602), the mobility of the wireless device may be managed / controlled by a RAN (e.g., RAN 104 or NG RAN 154). The wireless device may measure a received signal level (e.g., a reference signal level, a reference signal received power, a reference signal received quality, a received signal strength indicator, etc.) based on one or more signals sent from a serving cell and a neighboring cell. The wireless device may report these measurement results to a serving base station (e.g., a base station currently serving the wireless device). The serving base station of the wireless device may, for example, request a handover to a cell of one of the neighboring base stations based on the reported measurement results. 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 a connection release procedure 608. The RRC state may transition from an RRC connected state (e.g., RRC connected 602) to an RRC inactive state (e.g., RRC inactive state 604) via a connection detachment procedure 610.

[0095] An RRC context may not be established for the wireless device. For example, this may occur during an RRC idle state. During an RRC idle state (e.g., RRC idle 606), an RRC context may not be established for the wireless device. During an RRC idle state (e.g., RRC idle 606), the wireless device may not have an RRC connection with a base station. During an RRC idle state (e.g., RRC idle 606), the wireless device may be in a sleep state (e.g., to conserve battery power) for most of the time. The wireless device may periodically wake up (e.g., once per discontinuous reception (DRX) cycle) to monitor for paging messages (e.g., paging messages set up by the RAN). The mobility of the wireless device may be managed by the wireless device via 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.

[0096] A previously established RRC context may be maintained for the wireless device. For example, this may occur during an RRC inactive state. During the RRC inactive state (e.g., RRC inactive state 604), the previously established RRC context may be maintained in the wireless device and the base station. Maintaining the RRC context may enable / allow a quick transition to the RRC connected state (e.g., RRC connected 602) with reduced signaling overhead compared to a transition from an RRC idle state (e.g., RRC idle 606) to an RRC connected state (e.g., RRC connected 602). During the RRC inactive state (e.g., RRC inactive state 604), the wireless device may be in a sleep state, and the mobility of the wireless device may be managed / controlled by the wireless device via cell reselection. The RRC state may transition from the RRC inactive state (e.g., RRC inactive state 604) to the RRC connected state (e.g., RRC connected 602) via a connection recovery procedure 614. The RRC state may transition from an RRC inactive state (eg, RRC inactive state 604 ) to an RRC idle state (eg, RRC idle 606 ) via a connection release procedure 616 , which may be the same as or similar to the connection release procedure 608 .

[0097] The RRC state may be associated with a mobility management mechanism. During an RRC idle state (e.g., RRC idle 606) and an RRC inactive state (e.g., RRC inactive state 604), mobility may be managed / controlled by the wireless device via cell reselection. The purpose of mobility management during an RRC idle state (e.g., RRC idle 606) or during an RRC inactive state (e.g., RRC inactive state 604) may be to enable / allow the network to notify the wireless device of an event via a paging message without broadcasting the paging message across the entire mobile communication network. The mobility management mechanism used during an RRC idle state (e.g., RRC idle 606) or during an RRC inactive state (e.g., RRC inactive state 604) may enable / allow the network to track the wireless device, for example, at a cell group level, such that a paging message may be broadcast on cells of the cell group in which the wireless device is currently camped (e.g., rather than sending the paging message across the entire mobile communication network). The mobility management mechanism for the RRC idle state (e.g., RRC idle 606) and the RRC inactive state (e.g., RRC inactive state 604) can track the wireless device at the cell group level. The mobility management mechanism can, for example, use different grouping granularities for tracking. There can be multiple levels of cell grouping granularity (e.g., three levels of cell grouping granularity: a single cell; cells within a RAN area identified by a RAN area identifier (RAI); and cells within a group of RAN areas referred to as a tracking area and identified by a tracking area identifier (TAI)).

[0098] Tracking areas may be used to track wireless devices (e.g., to track the location of wireless devices at the CN level). A CN (e.g., CN 102, 5G CN 152, or any other CN) may send a TAI list associated with a wireless device registration area (e.g., a UE registration area) to the wireless device. The wireless device may perform a registration update with the CN to allow the CN to update the location of the wireless device and provide the wireless device with a new UE registration area, for example, if the wireless device moves (e.g., via cell reselection) to a cell associated with a TAI that may not be included in the TAI list associated with the UE registration area.

[0099] RAN areas may be used to track wireless devices (e.g., the location of wireless devices at the RAN level). For wireless devices in an RRC inactive state (e.g., RRC inactive state 604), a RAN notification area may be assigned / provisioned / configured to the wireless device. A RAN notification area may include one or more cell identities (e.g., an RAI list and / or a TAI list). A base station may belong to one or more RAN notification areas. A cell may belong to one or more RAN notification areas. The wireless device may perform a notification area update with the RAN to update the RAN notification area of ​​the wireless device, for example, if the wireless device moves (e.g., via cell reselection) to a cell that is not included in the RAN notification area assigned / provisioned / configured to the wireless device.

[0100] A base station that stores the RRC context of a wireless device or the last serving base station of the wireless device may be referred to as an anchor base station. The anchor base station may maintain the RRC context of the wireless device at least during a period when the wireless device remains in the RAN notification area of ​​the anchor base station and / or during a period when the wireless device remains in an RRC inactive state (e.g., RRC inactive state 604).

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

[0102] Physical signals and physical channels (e.g., Figure 5A and Figure 5BThe data may be mapped to a series of complex symbols (e.g., M quadrature amplitude modulation (M-QAM) symbols or M phase shift keying (M-PSK) symbols or any other modulated symbols) referred to as source symbols and divided into F parallel symbol streams, for example, before data transmission. The F parallel symbol streams may be viewed as if they were in the frequency domain. The F parallel symbols may be used as input to an inverse fast Fourier transform (IFFT) block that transforms them into the time domain. The IFFT block may receive F source symbols at a time, one source symbol from each of the F parallel symbol streams. The IFFT block may use each source symbol to modulate the amplitude and phase of one of the F sinusoidal basis functions corresponding to the F orthogonal subcarriers. The output of the IFFT block may be F time domain samples representing 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 sent / transmitted over the air interface on the carrier frequency, for example, after one or more processes (e.g., adding a cyclic prefix) and up-conversion. For example, a Fast Fourier Transform (FFT) block can be used to mix the F parallel symbol streams before being processed by the IFFT block. This operation can produce a discrete Fourier transform (DFT) precoded OFDM symbol and can be used by one or more wireless devices in the uplink to reduce the peak-to-average power ratio (PAPR). The FFT block can be used at the receiver to perform inverse processing on the OFDM symbol to recover the data mapped to the source symbol.

[0103] Figure 7 An exemplary configuration of a frame is shown. The frame may include, for example, an NR radio frame into which OFDM symbols may be grouped. A frame (e.g., an NR radio frame) may be identified / indicated by a system frame number (SFN) or any other value. The SFN may be repeated in a period of 1024 frames. The duration of an NR frame may be 10 milliseconds (ms) and may include 10 subframes of 1 ms duration. The subframe may be divided into one or more time slots (e.g., depending on a parameter set and / or different subcarrier spacings). Each of the one or more time slots may include, for example, 14 OFDM symbols per time slot. Any number of symbols, time slots, or durations may be used for any time interval.

[0104] The duration of a time slot may depend on a parameter set for the OFDM symbol used for the time slot. For example, flexible parameter sets may be supported to accommodate different deployments (e.g., cells with carrier frequencies below 1 GHz to cells with carrier frequencies in the millimeter wave range). For example, in an NR configuration or any other radio configuration, flexible parameter sets may be supported. The parameter set may be defined based on subcarrier spacing and / or cyclic prefix duration. The subcarrier spacing may be increased proportionally by powers of two from a baseline subcarrier spacing of 15 kHz. For example, for a parameter set in an NR configuration or any other radio configuration, the cyclic prefix duration may be scaled down by powers of two from a baseline cyclic prefix duration of 4.7 μs. The parameter set may be defined with the following subcarrier spacing / cyclic prefix duration combinations: 15 kHz / 4.7 μs; 30 kHz / 2.3 μs; 60 kHz / 1.2 μs; 120 kHz / 0.59 μs; 240 kHz / 0.29 μs, and / or any other subcarrier spacing / cyclic prefix duration combination.

[0105] A slot may have a fixed number / quantity of OFDM symbols (eg, 14 OFDM symbols). Parameter sets with higher subcarrier spacing may have shorter slot durations and more slots per subframe. Figure 7 An example of parameter set related slot duration and per-subframe slot transmission structure is shown in ( Figure 7 Parameter sets with 240kHz subcarrier spacing are not shown in [4]. A subframe (e.g., in an NR configuration) can be used as a parameter set-independent time reference. A slot can be used as the unit for scheduling uplink and downlink transmissions. Scheduling (e.g., in an NR configuration) can be decoupled from the slot duration. Scheduling can start at any OFDM symbol. Scheduling can last for as many symbols as required for the transmission, e.g., to support low latency. These partial slot transmissions can be referred to as mini-slots or sub-slot transmissions.

[0106] Figure 8 An exemplary resource configuration for one or more carriers is shown. The resource configuration may include a slot in the time and frequency domains for an NR carrier or any other carrier. The slot may include a resource element (RE) and a resource block (RB). A resource element (RE) may be the smallest physical resource (e.g., in an NR configuration). An RE may span one OFDM symbol in the time domain, such as one subcarrier in the frequency domain. Figure 8 As shown in . RB can span twelve consecutive REs in the frequency domain, as Figure 8As shown. A carrier (e.g., an NR carrier) can be restricted to a certain number of RBs and / or subcarrier widths (e.g., 275 RBs or 275×12=3300 subcarriers). If such a restriction is used, the carrier (e.g., NR carrier) frequency can be restricted based on the subcarrier spacing (e.g., 50 MHz, 100 MHz, 200 MHz, and 400 MHz for subcarrier spacings of 15 kHz, 30 kHz, 60 kHz, and 120 kHz, respectively). A 400 MHz bandwidth can be set based on a 400 MHz bandwidth restriction per carrier. Any other bandwidth can be set based on a per-carrier bandwidth restriction.

[0107] The entire bandwidth of the carrier (e.g., such as Figure 8 ) using a single parameter set on the NR shown. In other exemplary configurations, multiple parameter sets may be supported on the same carrier. NR and / or other access technologies may support wide carrier bandwidths (e.g., up to 400 MHz for a subcarrier spacing of 120 kHz). Not all wireless devices may be able to receive the full carrier bandwidth (e.g., due to hardware limitations and / or different wireless device capabilities). For example, receiving and / or utilizing the full carrier bandwidth may be prohibited depending on the wireless device power consumption. The wireless device may, for example, adjust the size of the receive bandwidth of the wireless device based on the amount of traffic the wireless device is scheduled to receive (e.g., to reduce power consumption and / or other purposes). Such adaptation may be referred to as bandwidth adaptation.

[0108] The configuration of one or more bandwidth parts (BWPs) can support one or more wireless devices that are unable to receive the full carrier bandwidth. The BWP can support bandwidth adaptation, for example, for such wireless devices that cannot receive the full carrier bandwidth. A BWP (e.g., a BWP for an NR configuration) can be defined by a subset of contiguous RBs on a carrier. A wireless device can be configured (e.g., via the RRC layer) with one or more downlink BWPs per serving cell and one or more uplink BWPs per serving cell (e.g., up to four downlink BWPs per serving cell and up to four uplink BWPs per serving cell). One or more of the configured BWPs for a serving cell can be active, for example, at a given time. The one or more BWPs can be referred to as the active BWPs of the serving cell. For example, if a serving cell is configured with a secondary uplink carrier, the serving cell can have one or more first active BWPs in the uplink carrier and one or more second active BWPs in the secondary uplink carrier.

[0109] A downlink BWP from a set of configured downlink BWPs can be linked with an uplink BWP from a set of configured uplink BWPs (e.g., for unpaired spectrum). For example, if the downlink BWP index of the downlink BWP and the uplink BWP index of the uplink BWP are the same, then the downlink BWP can be linked with the uplink BWP. The wireless device can expect the center frequency of the downlink BWP to be the same as the center frequency of the uplink BWP (e.g., for unpaired spectrum).

[0110] A base station may configure one or more control resource sets (CORESETs) for at least one search space for a wireless device. The base station may configure one or more CORESETs for a wireless device, such as a downlink BWP from a set of configured downlink BWPs on a primary cell (PCell) or a secondary cell (SCell). A search space may include a set of locations in the time and frequency domains where a wireless device may monitor / search / detect / identify control information. The search space may be a wireless device-specific search space (e.g., a UE-specific search space) or a common search space (e.g., potentially used by multiple wireless devices or a group of wireless user devices). The base station may configure a common search space for a group of wireless devices in an active downlink BWP on a PCell or a primary / secondary cell (PSCell).

[0111] The base station may configure one or more resource sets for the wireless device for one or more PUCCH transmissions, e.g., for an uplink BWP in a set of configured uplink BWPs. The wireless device may receive downlink transmissions (e.g., PDCCH or PDSCH) in the downlink BWP, e.g., according to a configured parameter set for the downlink BWP (e.g., configured subcarrier spacing and / or configured cyclic prefix duration). The wireless device may send / transmit uplink transmissions (e.g., PUCCH or PUSCH) in the uplink BWP, e.g., according to a configured parameter set (e.g., configured subcarrier spacing and / or configured cyclic prefix length for the uplink BWP).

[0112] One or more BWP indicator fields may be provided / included in the DCI. The value of the BWP indicator field may indicate which BWP, from a set of configured BWPs, is the active downlink BWP for one or more downlink receptions. The value of the one or more BWP indicator fields may indicate the active uplink BWP for one or more uplink transmissions.

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

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

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

[0116] Downlink BWP switching may refer to switching the active downlink BWP from a first downlink BWP to a second downlink BWP (e.g., activating the second downlink BWP and deactivating the first downlink BWP). Uplink BWP switching may refer to switching the active uplink BWP from a first uplink BWP to a second uplink BWP (e.g., activating the second uplink BWP and deactivating the first uplink BWP). Downlink and uplink BWP switching may be performed independently (e.g., in one or more paired spectrums). Downlink and uplink BWP switching may be performed simultaneously (e.g., in one or more unpaired spectrums). Switching between configured BWPs may occur, for example, based on RRC signaling, DCI signaling, expiration of a BWP inactivity timer, and / or the initiation of a random access.

[0117] Figure 9An example of a configured BWP is shown. Bandwidth adaptation using multiple BWPs (e.g., three configured BWPs for NR carriers) is available. A wireless device configured with multiple BWPs (e.g., three BWPs) can switch from one BWP to another at a switch point. The BWPs may include: BWP 902, which has a bandwidth of 40 MHz and a subcarrier spacing of 15 kHz; BWP 904, which has a bandwidth of 10 MHz and a subcarrier spacing of 15 kHz; and BWP 906, which has 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 can switch between BWPs at a switch point. The wireless device can switch from BWP 902 to BWP 904 at a switch point 908. The switch at switch point 908 may occur for any suitable reason. The switch at switch 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 a default BWP). The switch at switch point 908 may occur, for example, based on (e.g., after or in response to) receiving a DCI indicating BWP 904 as the active BWP. The wireless device may switch from active BWP 904 to BWP 906 at switch point 910, for example, after or in response to receiving a DCI indicating BWP 906 as the new active BWP. The wireless device may switch from active BWP 906 to BWP 904 at switch point 912, for example, based on (e.g., after or in response to) the expiration of a BWP inactivity timer. The wireless device may switch from active BWP 906 to BWP 904 at switch point 912, for example, after or in response to receiving a DCI indicating BWP 904 as the new active BWP. The wireless device may switch from the active BWP 904 to the BWP 902 at a switching point 914, for example, after or in response to receiving a DCI indicating the BWP 902 as the new active BWP.

[0118] The wireless device procedures for switching BWPs on a secondary cell can be the same / similar to those on a primary cell, for example, if the wireless device is configured for a secondary cell with a default downlink BWP and timer value from a set of configured downlink BWPs. The wireless device can use the timer values ​​and default downlink BWP for the secondary cell in the same / similar manner as the wireless device uses the timer values ​​and / or default BWP for the primary cell. The timer value (e.g., BWP inactivity timer) can be configured for each cell (e.g., for one or more BWPs), for example, via RRC signaling or any other signaling. One or more active BWPs can be switched to another BWP, for example, based on the expiration of the BWP inactivity timer.

[0119] Two or more carriers can be aggregated, and carrier aggregation (CA) can be used to simultaneously transmit / transmit data to / from the same wireless device (e.g., to increase data rates). The aggregated carriers in CA may be referred to as component carriers (CCs). For example, if CA is configured / used, there may be a certain number of serving cells for the wireless device (e.g., one serving cell for a CC). A CC may have multiple configurations in the frequency domain.

[0120] Figure 10A An exemplary CC-based CA configuration is shown. Figure 10A As shown, three types of CA configurations may include intra-band (contiguous) configuration 1002, intra-band (non-contiguous) configuration 1004, and / or inter-band configuration 1006. In the intra-band (contiguous) configuration 1002, two CCs may be aggregated in the same frequency band (Band A) and may be directly adjacent to each other within the frequency band. In the intra-band (non-contiguous) configuration 1004, two CCs may be aggregated in the same frequency band (Band A) but may be separated by a gap within the frequency band. In the inter-band configuration 1006, two CCs may be located in different frequency bands (e.g., Band A and Band B, respectively).

[0121] The network may set a maximum number of CCs that can be aggregated (e.g., up to 32 CCs in NR, or any other number in other systems). Aggregated CCs may have the same or different bandwidths, subcarrier spacing, and / or duplexing schemes (TDD, FDD, or any other duplexing scheme). A serving cell for a wireless device using CA may have downlink CCs. One or more uplink CCs may optionally be configured for the serving cell (e.g., for FDD). The ability to aggregate more downlink carriers than uplink carriers may be useful, for example, if the wireless device has more data traffic in the downlink than in the uplink.

[0122] One of the aggregated cells for a wireless device may be referred to as a primary cell (PCell), for example, if carrier aggregation (CA) is configured. A PCell may be the serving cell for a wireless device's initial connection or access, for example, during or at the time of RRC connection establishment, RRC connection reestablishment, and / or handover. The PCell may provide / configure NAS mobility information and security inputs to the wireless device. A wireless device may have different PCells. For the downlink, the carrier corresponding to the PCell may be referred to as a downlink primary CC (DL PCC). For the uplink, the carrier corresponding to the PCell may be referred to as an uplink primary CC (UL PCC). Other aggregated cells for a wireless device (e.g., associated with CCs other than the DL PCC and UL PCC) may be referred to as secondary cells (SCells). For example, an SCell may be configured after the PCell is configured for the wireless device. The SCell may be configured via an RRC connection reconfiguration procedure. For the downlink, the carrier corresponding to the SCell may be referred to as a downlink secondary CC (DL SCC). For the uplink, the carrier corresponding to the SCell may be referred to as an uplink secondary CC (UL SCC).

[0123] For example, the SCell configured for the wireless device may be activated or deactivated based on traffic and channel conditions. Deactivation of the SCell may cause the wireless device to stop receiving PDCCH and PDSCH on the SCell and transmitting PUSCH, SRS, and CQI on the SCell. For example, a MAC CE (e.g., regarding Figure 4B The MAC CE may activate or deactivate the configured SCells. The MAC CE may use a bitmap (e.g., one bit per SCell) to indicate which SCells (e.g., within a subset of the configured SCells) for the wireless device are activated or deactivated. For example, the configured SCells may be deactivated based on (e.g., after or in response to) the expiration of an SCell deactivation timer (e.g., one SCell deactivation timer per SCell may be configured).

[0124] DCI may include control information for a cell, such as scheduling assignments and scheduling grants. DCI may be sent / transmitted via a cell corresponding to a scheduling assignment and / or scheduling grant, which may be referred to as self-scheduling. DCI including control information for a cell may be sent / transmitted via another cell, which may be referred to as cross-carrier scheduling. Uplink control information (UCI) may include control information, such as HARQ confirmation and channel state feedback (e.g., CQI, PMI, and / or RI) of an aggregated cell. UCI may be sent / transmitted via an uplink control channel (e.g., PUCCH) of a PCell or a SCell (e.g., an SCell configured with PUCCH). For a large number of aggregated downlink CCs, the PUCCH of the PCell may become overloaded. The cell may be divided into multiple PUCCH groups.

[0125] Figure 10B An exemplary cell group is shown. Aggregated cells may be configured into one or more PUCCH groups (e.g., Figure 10BAs shown). One or more cell groups or one or more uplink control channel groups (e.g., PUCCH group 1010 and PUCCH group 1050) may respectively include one or more downlink CCs. PUCCH group 1010 may include one or more downlink CCs, for example, three downlink CCs: 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: 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 the 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). UCI associated with the downlink CCs of the PUCCH group 1010 may be transmitted / transmitted via the uplink of the PCell 1021 (e.g., via the PUCCH of the PCell 1021), as shown as UCI 1031, UCI 1032, and UCI 1033. UCI associated with the downlink CCs of the PUCCH group 1050 may be transmitted / transmitted via the uplink of the PUCCH SCell (or PSCell) 1061 (e.g., via the PUCCH of the PUCCH SCell 1061), as shown as UCI 1071, UCI 1072, and UCI 1073. For example, if Figure 10B If the aggregated cells shown in FIG are not divided into PUCCH group 1010 and PUCCH group 1050, a single uplink PCell can be configured to send / transmit UCI associated with six downlink CCs. For example, if UCI 1031, 1032, 1033, 1071, 1072, and 1073 are sent / transmitted via PCell 1021, PCell 1021 may become overloaded. By dividing the transmission of UCI between PCell 1021 and PUCCH SCell (or PSCell) 1061, overload can be prevented and / or reduced.

[0126] 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 physical cell ID and a cell index may be assigned to a cell including a downlink carrier and optionally an uplink carrier. The physical cell ID or cell index may indicate / identify the downlink carrier and / or uplink carrier of the cell, for example, depending on the context in which the physical cell ID is used. For example, the physical cell ID may be determined using a synchronization signal (e.g., PSS and / or SSS) sent / transmitted via a downlink component carrier. The cell index may be determined, for example, using one or more RRC messages. The physical cell ID may be referred to as a carrier ID, and the cell index may be referred to as a carrier index. The first physical cell ID for a first downlink carrier may refer to the first physical cell ID of a cell including the first downlink carrier. Substantially the same / similar concepts may apply, for example, to carrier activation. Activation of a first carrier may refer to activation of a cell including the first carrier.

[0127] The multi-carrier nature of the PHY layer can be exposed / indicated to the MAC layer (e.g., in a CA configuration). The HARQ entity can operate on the serving cell. A transport block can be generated for each assignment / grant per serving cell. The transport block and potential HARQ retransmissions of the transport block can be mapped to the serving cell.

[0128] For the downlink, the base station may send / transmit (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 wireless devices. For the uplink, the one or more wireless devices may send / transmit one or more RS (e.g., DM-RS, PT-RS, and / or SRS) to the base station. The PSS and SSS may be sent / transmitted by the base station and used by the one or more wireless devices to synchronize the one or more wireless devices with the base station. A synchronization signal (SS) / physical broadcast channel (PBCH) block may include the PSS, SSS, and PBCH. The base station may periodically send / transmit a burst of SS / PBCH blocks, which may be referred to as an SSB.

[0129] Figure 11A An exemplary mapping of one or more SS / PBCH blocks is shown. A burst of SS / PBCH blocks may include one or more SS / PBCH blocks (e.g., 4 SS / PBCH blocks, such as Figure 11A). The bursts may be sent / transmitted periodically (e.g., every 2 frames, 20 milliseconds, or any other duration). The bursts may be limited to half a frame (e.g., the first half frame having a duration of 5 ms). Such parameters (e.g., the number of SS / PBCH blocks per burst, the periodicity of the bursts, the position of the bursts within the frame) may be configured, for example, based on at least one of: the carrier frequency of the cell in which the SS / PBCH blocks are sent / transmitted; the parameter set or subcarrier spacing of the cell; configuration by the network (e.g., using RRC signaling); and / or any other suitable factors. For example, unless the wireless network configures the wireless device to assume a different subcarrier spacing, the wireless device may assume the subcarrier spacing of the SS / PBCH blocks based on the monitored carrier frequency.

[0130] The SS / PBCH block may span one or more OFDM symbols in the time domain (e.g., 4 OFDM symbols, such as Figure 11A The PSS may be sent / transmitted first and may span, for example, 1 OFDM symbol and 127 subcarriers. The SSS may be sent / transmitted after the PSS (for example, two symbols later) and may span 1 OFDM symbol and 127 subcarriers. The PBCH may be sent / transmitted after the PSS (for example, across the next 3 OFDM symbols) and may span 240 subcarriers (for example, after 1 OFDM symbol) in the frequency domain. Figure 11A ) and / or may span fewer than 240 subcarriers (e.g., in the second OFDM symbol and the fourth OFDM symbol shown). Figure 11A 3 OFDM symbol shown).

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

[0132] A wireless device may use the SS / PBCH blocks to determine one or more parameters of a cell. The wireless device may determine the physical cell identifier (PCI) of the cell, for example, based on the sequences of the PSS and SSS, respectively. The wireless device may determine the location of the cell's frame boundary, for example, based on the location of the SS / PBCH blocks. The SS / PBCH blocks may indicate that they have been sent / transmitted according to a transmission mode. The SS / PBCH blocks in the transmission mode may be at a known distance from the frame boundary (e.g., a predefined distance configured by the RAN between one or more networks, one or more base stations, and one or more wireless devices).

[0133] The PBCH may use QPSK modulation and / or forward error correction (FEC). The FEC may use polarity coding. One or more symbols spanned by the PBCH may include / carry one or more DM-RSs used for PBCH demodulation. The PBCH may include an indication of the current system frame number (SFN) of the cell and / or an SS / PBCH block timing index. These parameters may facilitate time synchronization between the wireless device and the base station. The PBCH may include a MIB for sending / transmitting one or more parameters to the wireless device. The wireless device may use the MIB to locate the remaining minimum system information (RMSI) associated with the cell. The RMSI may include system information block type 1 (SIB1). SIB1 may include information for the wireless device to access the cell. The wireless 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 SIB1. SIB1 may be decoded using parameters provided / included in the MIB. The PBCH may indicate the absence of SIB1. The wireless device may be directed to a frequency, for example, based on the PBCH indicating the absence of SIB1. The wireless device may search for SS / PBCH blocks at the frequency to which the wireless device is pointed.

[0134] A wireless device may assume that one or more SS / PBCH blocks transmitted / transmitted using the same SS / PBCH block index are quasi-co-located (QCLed) (e.g., have substantially the same / similar Doppler spread, Doppler shift, average gain, average delay, and / or spatial Rx parameters). A wireless device may not assume QCL for SS / PBCH block transmissions with different SS / PBCH block indices. SS / PBCH blocks (e.g., those within a half-frame) may be transmitted / transmitted in spatial directions (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, a fourth SS / PBCH block may be transmitted / transmitted in a fourth spatial direction using a fourth beam, and so on.

[0135] For example, a base station may send / transmit multiple SS / PBCH blocks within a frequency span of a carrier. A first PCI of a first SS / PBCH block in the multiple SS / PBCH blocks may be different from a second PCI of a second SS / PBCH block in the multiple SS / PBCH blocks. The PCIs of SS / PBCH blocks sent / transmitted at different frequency locations may be different or substantially the same.

[0136] The CSI-RS may be sent / transmitted by a base station and used by a wireless device to collect / acquire / determine channel state information (CSI). The base station may configure one or more CSI-RSs for the wireless device for channel estimation or any other suitable purpose. The base station may configure one or more of the same / similar CSI-RSs for the wireless device. The wireless device may measure the one or more CSI-RSs. The wireless device may estimate the downlink channel state and / or generate a CSI report based on the measurement results of the one or more downlink CSI-RSs, for example. The wireless device may send / transmit a CSI report to the base station (e.g., based on periodic CSI reporting, semi-persistent CSI reporting, and / or aperiodic CSI reporting). The base station may use the feedback provided by the wireless device (e.g., estimated downlink channel state) to perform link adaptation.

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

[0138] The base station may configure the wireless device to report CSI measurement results. The base station may configure the wireless device to provide CSI reports periodically, aperiodically, or semi-persistently. For periodic CSI reporting, the wireless device may be configured with the timing and / or periodicity of multiple CSI reports. For aperiodic CSI reporting, the base station may request a CSI report. The base station may command the wireless device to measure the configured CSI-RS resources and provide a CSI report related to the measurement results. For semi-persistent CSI reporting, the base station may configure the wireless device to send / transmit periodically and selectively activate or deactivate periodic reporting (e.g., via one or more activation / deactivation MAC CEs and / or one or more DCIs). The base station may configure the CSI-RS resource set and CSI report for the wireless device, for example, using RRC signaling.

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

[0140] Downlink DM-RS may be sent / transmitted by a base station and received / used by a wireless device for channel estimation. Downlink DM-RS may be used for coherent demodulation of one or more downlink physical channels (e.g., PDSCH). 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 front-loaded DM-RS pattern. The front-loaded DM-RS may be mapped to one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). A base station may semi-statically configure a wireless device with a certain number / quantity (e.g., a maximum number / quantity) of front-loaded DM-RS symbols for 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 wireless device (e.g., for single-user MIMO). A DM-RS configuration may support up to four orthogonal downlink DM-RS ports per wireless device (e.g., for multi-user MIMO). The radio network may support (e.g., at least for CP-OFDM) a common DM-RS structure for downlink and uplink. The DM-RS positions, DM-RS patterns, and / or scrambling sequences may be the same or different. The base station may, for example, use the same precoding matrix to send / transmit the downlink DM-RS and the corresponding PDSCH. The wireless device may use the one or more downlink DM-RSs for coherent demodulation / channel estimation of the PDSCH.

[0141] A transmitter (e.g., a transmitter of a base station) may use a precoder matrix for a portion of a transmission bandwidth. The transmitter may use a first precoder matrix for a first bandwidth and a second precoder matrix for a second bandwidth. For example, the first precoder matrix and the second precoder matrix may be different based on the first bandwidth being different from the second bandwidth. The wireless device may assume that the same precoding matrix is ​​used across a group of PRBs. The group of PRBs may be determined / indicated / identified / represented as a precoding resource block group (PRG).

[0142] The PDSCH may include one or more layers. The wireless device may assume that at least one symbol with a DM-RS is present on one of the one or more layers of the PDSCH. Higher layers may configure one or more DM-RSs for the PDSCH (e.g., configuring up to three DMRSs for the PDSCH). Downlink PT-RSs may be sent / transmitted by the base station and used by the wireless device, for example, for phase noise compensation. The presence or absence of downlink PT-RSs may depend on the RRC configuration. The presence and / or pattern of downlink PT-RSs may be configured on a wireless device-specific basis, for example, using a combination of RRC signaling and / or association with one or more parameters used for other purposes (e.g., modulation and coding scheme (MCS)), which may be indicated by DCI. The dynamic presence of downlink PT-RSs (if configured) may be associated with one or more DCI parameters including at least the MCS. The network (e.g., an NR network) may support multiple PT-RS densities defined in the time and / or frequency domains. The frequency domain density (if configured / present) may be associated with at least one configuration of the scheduling bandwidth. The wireless device may assume the same precoding for both 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 scheduled resources. The downlink PT-RS may be configured / allocated / restricted to the scheduled time / frequency duration of the wireless device. The downlink PT-RS may be sent / transmitted via symbols, for example, to facilitate phase tracking at the receiver.

[0143] For example, a wireless device may send / transmit uplink DM-RS to a base station for channel estimation. The base station may use the uplink DM-RS to perform coherent demodulation of one or more uplink physical channels. The wireless device may use the PUSCH and / or PUCCH to send / transmit uplink DM-RS. The uplink DM-RS may span a frequency range similar to the frequency range associated with the corresponding physical channel. The base station may configure one or more uplink DM-RS configurations for the wireless device. At least one DM-RS configuration may support a front-loaded DM-RS pattern. The front-loaded DM-RS may be mapped to one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). One or more uplink DM-RS may be configured to be sent / transmitted at one or more symbols of the PUSCH and / or PUCCH. The base station may semi-statically configure a certain number / quantity (e.g., a maximum number / quantity) of front-loaded DM-RS symbols for the PUSCH and / or PUCCH for the wireless device, which the wireless device may use to schedule single-symbol DM-RS and / or dual-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 positions, DM-RS patterns, and / or scrambling sequences of the DM-RSs may be substantially the same or different.

[0144] The PUSCH may include one or more layers. The wireless device may send / transmit at least one symbol in which a DM-RS is present on one of the one or more layers of the PUSCH. Higher layers may configure one or more DM-RSs (e.g., up to three DMRSs) for the PUSCH. For example, depending on the RRC configuration of the wireless device, uplink PT-RSs (which may be used by the base station for phase tracking and / or phase noise compensation) may or may not be present. The presence and / or pattern of uplink PT-RSs may be configured on a wireless device-specific basis (e.g., a UE-specific basis), for example, via RRC signaling and / or a combination of one or more parameters configured / used for other purposes (e.g., MCS), which may be indicated by DCI. If configured, the dynamic presence of uplink PT-RSs may be associated with one or more DCI parameters including at least MCS. The radio 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 scheduling bandwidth. The wireless device may assume the same precoding for both DM-RS ports and PT-RS ports. The number / quantity of PT-RS ports may be less than the number / quantity of DM-RS ports in the scheduled resources.The uplink PT-RS may be configured / allocated / restricted to the scheduled time / frequency duration of the wireless device.

[0145] One or more SRSs may be sent / transmitted by a wireless device to a base station, for example, for channel state estimation to support uplink channel-dependent scheduling and / or link adaptation. The SRSs sent / transmitted by the wireless device may enable / allow the base station to estimate uplink channel states at one or more frequencies. A scheduler at the base station may use / adopt the estimated uplink channel states to assign one or more resource blocks for uplink PUSCH transmissions by the wireless device. The base station may semi-statically configure one or more SRS resource sets for the wireless device. For an SRS resource set, the base station may configure one or more SRS resources for the wireless device. The applicability of an SRS resource set may be configured, for example, by higher-layer (e.g., RRC) parameters. SRS resources (e.g., having the same / similar time-domain behavior, periodicity, aperiodicity, etc.) in the one or more SRS resource sets may be sent / transmitted at a certain time (e.g., simultaneously), for example, if higher-layer parameters indicate beam management. The wireless device may send / transmit one or more SRS resources in an SRS resource set. The network (e.g., an NR network) may support aperiodic, periodic, and / or semi-persistent SRS transmission. The wireless device may, for example, send / transmit SRS resources based on one or more trigger types. The one or more trigger types may include higher layer signaling (e.g., RRC) and / or one or more DCI formats. The wireless device may use / adopt at least one DCI format to select at least one of one or more configured SRS resource sets. SRS trigger type 0 may refer to SRS triggered based on higher layer signaling. SRS trigger type 1 may refer to SRS triggered based on one or more DCI formats. If PUSCH and SRS are sent / transmitted in the same time slot, the wireless device may be configured to send / transmit SRS, for example, after the transmission of PUSCH and the corresponding uplink DM-RS. The base station can semi-statically configure one or more SRS configuration parameters for the wireless device, wherein the configuration parameters indicate at least one of the following: an SRS resource configuration identifier; the number of SRS ports; the time domain behavior of the SRS resource configuration (e.g., an indication of periodic semi-persistent or aperiodic SRS); slot, mini-slot and / or subframe level periodicity; the offset of periodic and / or aperiodic SRS resources; the number of OFDM symbols in the SRS resource; the starting OFDM symbol of the SRS resource; the SRS bandwidth; the frequency hopping bandwidth; the cyclic shift; and / or the SRS sequence ID.

[0146] Antenna ports can be determined / defined so that the channel over which a symbol on the same antenna port is transmitted can be inferred from the channel over which another symbol on the same antenna port is transmitted. For example, if a first symbol and a second symbol are sent / transmitted on the same antenna port, the receiver can infer / determine the channel (e.g., attenuation gain, multipath delay, etc.) used to transmit the second symbol on the antenna port from the channel used to transmit the first symbol on the antenna port. For example, if one or more large-scale properties of the channel over which the first symbol on the first antenna port is transmitted can be inferred from the channel over which the second symbol on the second antenna port is transmitted, the first antenna port and the second antenna port can be referred to as quasi-co-located (QCLed). The one or more large-scale properties may include at least one of the following: delay spread; Doppler spread; Doppler shift; average gain; average delay; and / or spatial receive (Rx) parameters.

[0147] Channels using beamforming may require beam management. Beam management may include beam measurement, beam selection, and / or beam indication. A beam may be associated with one or more reference signals. A beam may be identified by one or more beamforming reference signals. The wireless device may, for example, perform downlink beam measurement based on one or more downlink reference signals (e.g., CSI-RS) and generate a beam measurement report. For example, after establishing an RRC connection with a base station, the wireless device may perform a downlink beam measurement procedure.

[0148] Figure 11B An exemplary mapping of one or more CSI-RSs is shown. The CSI-RSs may be mapped in both the time domain and the frequency domain. Figure 11BEach rectangular block shown in may correspond to a resource block (RB) within the bandwidth of the cell. The base station may send / transmit one or more RRC messages including CSI-RS resource configuration parameters indicating one or more CSI-RSs. One or more of the parameters may be configured by high-layer signaling (e.g., RRC and / or MAC signaling) for CSI-RS resource configuration. One or more of these parameters may include at least one of the following: CSI-RS resource configuration identity, number of CSI-RS ports, CSI-LS configuration (e.g., symbol and resource element (RE) positions in a subframe), CSI-RS subframe configuration (e.g., subframe position, offset, and periodicity in a radio frame), CSI-RS power parameter, CSI-SS sequence parameter, code division multiple access (CDM) type parameter, frequency density, transmission comb, quasi co-location (QCL) parameters (e.g., QCL-scramblingidentity, crs-portscount, mbsfn-subframeconfiglist, csi-rs-configZPid, qcl-csi-rs-configNZPid), and / or other radio resource parameters.

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

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

[0151] The wireless device may determine / evaluate (e.g., measure) the channel quality of one or more beam pair links, for example, in a beam management procedure. The beam pair link may include a Tx beam of a base station and an Rx beam of a wireless device. The Tx beam of the base station may send / transmit a downlink signal, and the Rx beam of the wireless device may receive a downlink signal. For example, the wireless device may send / transmit a beam measurement report based on the evaluation / determination. The beam measurement report may indicate one or more beam pair quality parameters including at least one of the following: one or more beam identifiers (e.g., beam index, reference signal index, etc.), RSRP, precoding matrix indicator (PMI), channel quality indicator (CQI), and / or rank indicator (RI).

[0152] Figure 12AAn example of a downlink beam management procedure is shown. One or more downlink beam management procedures (e.g., downlink beam management procedures P1, P2, and P3) may be executed. Procedure P1 may enable measurements (e.g., wireless device measurements) of the Tx beams of a TRP (or multiple TRPs) (e.g., to support selection of one or more base station Tx beams and / or wireless device Rx beams). The Tx beams of the base station and the Rx beams of the wireless device are shown as ovals in the top row of P1 and the bottom row of P1, respectively. Beamforming (e.g., at the TRP) may include Tx beam scanning for a set of beams (e.g., shown as elliptical beam scanning rotating counterclockwise as indicated by dashed arrows in the top row of P1 and P2). Beamforming (e.g., at the wireless device) may include Rx beam scanning for a set of beams (e.g., shown as elliptical beam scanning rotating clockwise as indicated by dashed arrows in the bottom row of P1 and P3). Procedure P2 may be used to enable measurements (e.g., wireless device measurements) of the Tx beams of the TRP (shown in the top row of P2 as an ellipse rotating counterclockwise indicated by a dashed arrow). The wireless device and / or the base station may perform procedure P2, for example, using a smaller set of beams than the set of beams used in procedure P1, or using a narrower beam than the beam used in procedure P1. Procedure P2 may be referred to as beam refinement. The wireless device may perform procedure P3 for Rx beam determination, for example, by using the same Tx beam of the base station and scanning the Rx beam of the wireless device.

[0153] Figure 12BAn example of an uplink beam management program is shown. One or more uplink beam management programs (e.g., uplink beam management programs U1, U2, and U3) may be executed. Program U1 may be used to enable a base station to perform measurements on a wireless device's Tx beam (e.g., to support selection of one or more Tx beams of the wireless device and / or Rx beams of the base station). The Tx beams of the wireless device and the Rx beams of the base station are shown as ovals in the top row of U1 and the bottom row of U3, respectively. Beamforming (e.g., at the wireless device) may include one or more beam scans, e.g., Tx beam scans from a set of beams (shown as ovals rotating clockwise as indicated by dashed arrows in the bottom row of U1 and U3). Beamforming (e.g., at the base station) may include one or more beam scans, e.g., Rx beam scans from a set of beams (shown as ovals rotating counterclockwise as indicated by dashed arrows in the top row of U1 and U2). For example, if a wireless device (e.g., a UE) uses a fixed Tx beam, procedure U2 can be used to enable the base station to adjust its Rx beam. The wireless device and / or base station can perform procedure U2, for example, to use a smaller set of beams than the set of beams used in procedure P1, or to use a narrower beam than the beam used in procedure P1. Procedure U2 can be referred to as beam refinement. For example, if the base station uses a fixed Rx beam, the wireless device can perform procedure U3 to adjust its Tx beam.

[0154] The wireless device may, for example, initiate / start / perform a beam failure recovery (BFR) procedure based on detecting a beam failure. The wireless device may, for example, send / transmit a BFR request (e.g., a preamble, UCI, SR, MAC CE, etc.) based on initiating the BFR procedure. The wireless device may detect a beam failure based on, for example, determining that the quality of the beam-pair link of the associated control channel is unsatisfactory (e.g., having a bit error rate above a bit error rate threshold, a received signal power below a received signal power threshold, expiration of a timer, etc.).

[0155] The wireless device may measure the quality of the beam-to-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-RSs. The quality of the beam-to-link may be based on one or more of a block error rate (BLER), an RSRP value, a signal-to-interference-plus-noise ratio (SINR) value, an RSRQ value, and / or a CSI value measured for the RS resources. The base station may indicate the QCL of one or more DM-RSs of the RS resources and a channel (e.g., a control channel, a shared data channel, etc.). For example, if the channel characteristics (e.g., Doppler shift, Doppler spread, average delay, delay spread, spatial Rx parameters, fading, etc.) of the transmission from the RS resources to the wireless device are similar or identical to the channel characteristics of the transmission from the channel to the wireless device, the RS resources and the one or more DM-RSs of the channel may be QCL.

[0156] A network (e.g., an NR network including a gNB and / or ng-eNB) and / or a wireless device may initiate / start / perform a random access procedure. A wireless device in an RRC idle (e.g., RRC_IDLE) state and / or an RRC inactive (e.g., RRC_INACTIVE) state may initiate / start / perform a random access procedure to request connection setup to the network. The wireless device may initiate / start / perform a random access procedure from an RRC connected (e.g., RRC_CONNECTED) state. The wireless device may initiate / start / perform a random access procedure to request uplink resources (e.g., for uplink transmission of an SR if no PUCCH resources exist) and / or acquire / determine uplink timing (e.g., if the uplink synchronization state is asynchronous). The wireless device may initiate / start / perform a random access procedure to request one or more system information blocks (SIBs) (e.g., other system information blocks such as SIB2, SIB3, etc.). The wireless device may initiate / start / perform a random access procedure for a beam failure recovery request. The network may initiate / start / perform a random access procedure, for example, for handover and / or for establishing time alignment for SCell addition.

[0157] Figure 13AAn exemplary four-step random access procedure is shown. The four-step random access procedure may include a four-step contention-based random access procedure. The base station may, for example, send / transmit a configuration message 1310 to the wireless device 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 referred to as a preamble. The second message (e.g., Msg 2 1312) may include a random access response (RAR). The second message (e.g., Msg 2 1312) may be referred to as a RAR.

[0158] The configuration message 1310 may be sent / transmitted, for example, using one or more RRC messages. The one or more RRC messages may indicate one or more random access channel (RACH) parameters to the wireless device. The one or more RACH parameters may include at least one of: common parameters (e.g., RACH-configGeneral) for one or more random access procedures; cell-specific parameters (e.g., RACH-ConfigCommon); and / or dedicated parameters (e.g., RACH-configDedicated). The base station may send / transmit (e.g., broadcast or multicast) the one or more RRC messages to the one or more wireless devices. The one or more RRC messages may be wireless device-specific. The one or more wireless device-specific RRC messages may be, for example, dedicated RRC messages sent / transmitted to a wireless device in an RRC connected (e.g., RRC_CONNECTED) state and / or in an RRC inactive (e.g., RRC_INACTIVE) state. The wireless device may determine time-frequency resources and / or uplink transmission power for transmitting the first message (e.g., Msg 1 1311) and / or the third message (e.g., Msg 3 1313) based on the one or more RACH parameters. The wireless device may determine, for example, reception timing and a downlink channel for receiving the second message (e.g., Msg 2 1312) and the fourth message (e.g., Msg 4 1314) based on the one or more RACH parameters.

[0159] The one or more RACH parameters provided / configured / included in the configuration message 1310 may indicate one or more physical RACH (PRACH) opportunities that may be used to transmit the first message (e.g., Msg 1 1311). The one or more PRACH opportunities may be predefined (e.g., by a network including one or more base stations). The one or more RACH parameters may indicate one or more available sets of one or more PRACH opportunities (e.g., prach-ConfigIndex). The one or more RACH parameters may indicate an association between (a) one or more PRACH opportunities and (b) one or more reference signals. The one or more RACH parameters may indicate an association between (a) one or more preambles and (b) one or more reference signals. The one or more reference signals may be SS / PBCH blocks and / or CSI-RS. The one or more RACH parameters may indicate the number / number of SS / PBCH blocks mapped to the PRACH opportunities and / or the number / number of preambles mapped to the SS / PBCH blocks.

[0160] The one or more RACH parameters provided / configured / included in the configuration message 1310 may be used to determine the uplink transmission power of the first message (e.g., Msg 1 1311) and / or the third message (e.g., Msg 3 1313). The one or more RACH parameters may indicate a reference power for preamble transmission (e.g., a received target power and / or initial power for the preamble transmission). There may be one or more power offsets indicated by the one or more RACH parameters. The one or more RACH parameters may indicate: a power ramp step; a power offset between the SSB and the CSI-RS; a 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 a power offset value between preamble groups. The one or more RACH parameters may indicate one or more thresholds, for example, based on which the wireless device may determine at least one reference signal (e.g., SSB and / or CSI-RS) and / or uplink carrier (e.g., normal uplink (NUL) carrier and / or supplemental uplink (SUL) carrier).

[0161] 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 configure one or more preamble groups (e.g., Group A and / or Group B). The preamble group may include one or more preambles. The wireless device may determine the preamble group based on, for example, a path loss measurement result and / or the size of the 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 greater than an RSRP threshold (e.g., rsrp-ThresholdSSB and / or rsrp-ThresholdCSI-RS). For example, if the association between the one or more preambles and the at least one reference signal is configured by the RRC message, the wireless device may select at least one preamble associated with the one or more reference signals and / or the selected preamble group.

[0162] For example, the wireless device may determine a preamble based on the one or more RACH parameters provided / configured / included in the configuration message 1310. The wireless device may determine the preamble based on, for example, a path loss measurement result, an RSRP measurement result, and / or the size of a third message (e.g., Msg 3 1313). The one or more RACH parameters may indicate: a preamble format; a maximum number / number of preamble transmissions; and / or one or more thresholds for determining one or more preamble groups (e.g., Group A and Group B). The base station may use the one or more RACH parameters to configure the wireless device with an association between one or more preambles and one or more reference signals (e.g., SSB and / or CSI-RS). For example, if an association is configured, the wireless device may determine that the preamble is to be included in the first message (e.g., Msg 1 1311) based on the association. The first message (e.g., Msg 1 1311) may be sent / transmitted to the base station via one or more PRACH opportunities. The wireless device may use one or more reference signals (e.g., SSB and / or CSI-RS) to select a preamble and determine a PRACH opportunity. One or more RACH parameters (e.g., ra-ssb-OccasionMskIndex and / or ra-OccasionList) may indicate an association between a PRACH opportunity and the one or more reference signals.

[0163] For example, if no response is received based on (e.g., after or in response to) a preamble transmission (e.g., within a period of time, such as a monitoring window for monitoring RAR), the wireless device may perform a preamble retransmission. The wireless device may increase the uplink transmission power for the preamble retransmission. The wireless device may select an initial preamble transmission power based on, for example, a path loss measurement result and / or a target received preamble power configured by the network. The wireless device may determine to resend / retransmit the preamble and may ramp up the uplink transmission power. The wireless device may receive one or more RACH parameters (e.g., PREAMBLE_POWER_RAMPING_STEP) indicating a ramp-up step for the preamble retransmission. The ramp-up step may be an incremental increase in the uplink transmission power for the retransmission. For example, if the wireless device determines the same reference signal (e.g., SSB and / or CSI-RS) as the previous preamble transmission, the wireless device may ramp up the uplink transmission power. The wireless device may count the number of preamble transmissions and / or retransmissions, for example, using a counter parameter (e.g., PREAMBLE_TRANSMISSION_COUNTER). For example, if the number of preamble transmissions exceeds a threshold configured by one or more RACH parameters (e.g., preambleTransMax) without receiving a successful response (e.g., RAR), the wireless device may determine that the random access procedure was unsuccessful.

[0164] A second message (e.g., Msg 2 1312) (e.g., received by a wireless device) may include a RAR. The second message (e.g., Msg 2 1312) may include multiple RARs corresponding to multiple wireless devices. The second message (e.g., Msg 2 1312) may be received, for example, based on (e.g., after or in response to) the transmission / 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, for example, using a random access radio network temporary identifier (RA RNTI). The second message (e.g., Msg 2 1312) may indicate that the base station received the first message (e.g., Msg 1 1311). The second message (e.g., Msg 2 1312) may include a time alignment command (which may be used by the wireless device to adjust the transmission timing of the wireless device), a scheduling grant for transmitting a third message (e.g., Msg 3 1313), and / or a temporary cell-RNTI (TC-RNTI). For example, after sending / transmitting the first message (e.g., Msg 1 1311) (e.g., a preamble), the wireless device may determine / start a time window (e.g., a PRA-ResponseWindow) to monitor the PDCCH for the second message (e.g., Msg 2 1312). The wireless device may determine the start time of the time window, for example, based on the PRACH opportunity used by the wireless device to send / transmit the first message (e.g., Msg 1 1311) (e.g., a preamble). The wireless device may start the time window one or more symbols after the last symbol of the first message (e.g., Msg 1 1311) including the preamble (e.g., the symbol in which the transmission of the first message (Msg 1 1311) including the preamble is completed or the first PDCCH opportunity after the preamble transmission ends). The one or more symbols may be determined based on a parameter set. The PDCCH may be mapped in a common search space (e.g., Type 1-PDCCH common search space) configured by an RRC message. The wireless device may identify / determine the RAR based on, for example, an RNTI. A radio network temporary identifier (RNTI) may be used based on one or more events in which a random access procedure is initiated / started. The wireless device may use an RA-RNTI, for example, for one or more communications associated with random access or any other purpose. The RA-RNTI may be associated with a PRACH opportunity in which the wireless device sends / transmits the preamble. The wireless device may determine the RA-RNTI based on, for example, at least one of: an OFDM symbol index; a slot index; a frequency domain index; and / or a UL carrier indicator of the PRACH opportunity. An exemplary RA-RNTI may be determined as follows:

[0165] RA-RNTI=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id

[0166] where s_id may be the index of the first OFDM symbol of the PRACH opportunity (e.g., 0≤s_id<14), t_id may be the index of the first time slot of the PRACH opportunity in the system frame (e.g., 0≤t_id<80), f_id may be the index of the PRACH opportunity in the frequency domain (e.g., 0≤f_id<8), and ul_carrier_id may be the UL carrier used for preamble transmission (e.g., 0 for NUL carrier and 1 for SUL carrier).

[0167] The wireless device may, for example, send / transmit a third message (e.g., Msg 3 1313) (e.g., using the resources identified in Msg 2 1312), based on (e.g., after or in response to) the successful reception of the second message (e.g., Msg 2 1312). The third message (e.g., Msg 3 1313) may be used, for example, for contention resolution in a contention-based random access procedure. Multiple wireless devices may send / transmit the same preamble to a base station, and the base station may send / transmit a Random Address Recognition (RAR) corresponding to the wireless device. For example, if the multiple wireless devices interpret the RAR as corresponding to themselves, a collision may occur. Contention resolution (e.g., using the third message (e.g., Msg 3 1313) and the 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. For example, the wireless device may include a device identification (e.g., the TC RNTI included in the second message (e.g., Msg 2 1312) if a C-RNTI is assigned, and / or any other suitable identifier) ​​in the third message (e.g., Msg 3 1313), e.g., to perform contention resolution.

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

[0169] A wireless device may be configured with a SUL carrier and / or a NUL carrier. Initial access (e.g., random access) may be supported via an uplink carrier. A base station may configure multiple RACH configurations for the wireless device (e.g., two separate RACH configurations, one for the SUL carrier and the other for the NUL carrier). For random access in a cell configured with a SUL carrier, the network may indicate which carrier (NUL or SUL) to use. 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 below a broadcast threshold, the wireless device may determine to use the SUL carrier. The uplink transmission of the 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 performed via the selected carrier. The wireless device may switch uplink carriers during the random access procedure (e.g., between Msg 1 1311 and Msg 3 1313). The wireless device may determine and / or switch uplink carriers for the first message (eg, Msg 1 1311) and / or the third message (eg, Msg 3 1313), for example, based on channel idleness assessment (eg, listen before talk).

[0170] Figure 13BA two-step random access procedure is shown. The two-step random access procedure may include a two-step contention-free random access procedure. Similar to the four-step contention-based random access procedure, the base station may send / transmit a configuration message 1320 to the wireless device before initiating the procedure. Configuration message 1320 may be similar in some aspects to configuration message 1310. Figure 13B The procedure shown in FIG3 may include the transmission of two messages: a first message (e.g., Msg 1 1321) and a second message (e.g., Msg 2 1322). The first message (e.g., Msg 1 1321) and the second message (e.g., Msg 2 1322) may be similar in some aspects to the first message (e.g., Msg 1 1311) and the second message (e.g., Msg 2 1312), respectively. The two-step contention-free random access procedure may not include messages similar to the third message (e.g., Msg 3 1313) and / or the fourth message (e.g., Msg 4 1314).

[0171] A two-step (e.g., contention-free) random access procedure may be configured / initiated for beam failure recovery, other SI requests, SCell addition, and / or handover. The base station may indicate or assign a preamble to the wireless device for the first message (e.g., Msg 1 1321). The wireless device may receive an indication of the preamble (e.g., ra-PreambleIndex) from the base station via PDCCH and / or RRC.

[0172] The wireless device may, for example, begin a time window (e.g., ra-ResponseWindow) to monitor the PDCCH for the RAR based on (e.g., after or in response to) sending / transmitting a preamble. The base station may configure one or more beam failure recovery parameters for the wireless device, such as a separate time window and / or a separate PDCCH in a search space indicated by an RRC message (e.g., recoverySearchSpaceId). The base station may configure one or more beam failure recovery parameters, for example, in association with a beam failure recovery request. The separate time window for monitoring the PDCCH and / or RAR may be configured to begin after sending / transmitting the beam failure recovery request (e.g., the window may begin any number of symbols and / or slots after sending / transmitting the beam failure recovery request). The wireless device may monitor PDCCH transmissions addressed to a cell RNTI (C-RNTI) on the search space. During a two-step (e.g., contention-free) random access procedure, the wireless device may determine that the random access procedure was successful, for example, based on sending / transmitting a first message (e.g., Msg 1 1321) and receiving (e.g., after or in response to) a corresponding second message (e.g., Msg 2 1322). For example, if the PDCCH transmission is addressed to the corresponding C-RNTI, the wireless device may determine that the random access procedure has been successfully completed. For example, if the wireless device receives a RAR including a preamble identifier corresponding to a preamble sent / transmitted by the wireless device and / or the RAR includes a MAC sub-PDU with the preamble identifier, the wireless device may determine that the random access procedure has been successfully completed. The wireless device may determine that the response is an indication of an acknowledgement of the SI request.

[0173] Figure 13C An exemplary two-step random access procedure is shown. Figure 13A and 13B , the base station may send / transmit a configuration message 1330 to the wireless device before initiating the random access procedure shown in FIG. 13. Configuration message 1330 may be similar in some aspects to configuration message 1310 and / or configuration message 1320. Figure 13C The procedure shown in may include transmission of a plurality of messages (eg, two messages including: a first message (eg, Msg A 1331) and a second message (eg, Msg B 1332)).

[0174] Msg A 1320 may be sent / transmitted by the wireless device in an uplink transmission. Msg A 1320 may include one or more transmissions of a preamble 1341 and / or one or more transmissions of a transmission block 1342. The transmission block 1342 may include content similar and / or equivalent to the content of the third message (e.g., Msg 3 1313) (e.g., Figure 13A). Transport block 1342 may include UCI (e.g., SR, HARQ ACK / NACK, etc.). The wireless device may receive a second message (e.g., Msg B 1332), for example, based on (e.g., after or in response to) sending / transmitting the first message (e.g., Msg A 1331). The second message (e.g., Msg B 1332) may include content (e.g., Figure 13A RAR shown in ), the content of the second message (eg, Msg 2 1322) (eg, Figure 13B ) and / or the fourth message (eg, Msg 4 1314) (eg, Figure 13A ) similar and / or equivalent content.

[0175] The wireless device may start / initiate a two-step random access procedure for licensed spectrum and / or unlicensed spectrum (e.g., Figure 13C The wireless device may determine whether to start / initiate the two-step random access procedure based on one or more factors. The one or more factors may include at least one of the following: the radio access technology being used (e.g., LTE, NR, etc.); whether the wireless device has a valid TA; the cell size; the RRC state of the wireless device; the spectrum type (e.g., licensed vs. unlicensed); and / or any other suitable factors.

[0176] The wireless device may determine radio resources and / or uplink transmission power for the preamble 1341 and / or transport block 1342 (e.g., 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 for the preamble 1341 and / or transport block 1342. The time-frequency resources used to transmit the preamble 1341 (e.g., PRACH) and the time-frequency resources used to transmit 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 reception timing and downlink channel for monitoring and / or receiving the second message (e.g., Msg B 1332).

[0177] Transport block 1342 may include data (e.g., delay-sensitive data), wireless device identification, security information, and / or device information (e.g., International Mobile Subscriber Identity (IMSI)). The base station may send / transmit a second message (e.g., Msg B 1332) in response to the 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., a radio resource assignment and / or an MCS); a wireless device identification (e.g., a UE identifier for contention resolution); and / or an RNTI (e.g., a C-RNTI or a TC-RNTI). For example, if the preamble identifier in the second message (e.g., Msg B 1332) corresponds to or matches the preamble sent / transmitted by the wireless device and / or the identifier of the wireless device in the second message (e.g., Msg B 1332) corresponds to or matches the identifier of the wireless device (e.g., transport block 1342) in the first message (e.g., Msg A 1331), the wireless device may determine that the two-step random access procedure is successfully completed.

[0178] The wireless device and the base station may exchange control signaling (e.g., control information). The control signaling may be referred to as L1 / L2 control signaling and may originate from the PHY layer (e.g., Layer 1) and / or the MAC layer (e.g., Layer 2) of the wireless device or the base station. The control signaling may include downlink control signaling sent / transmitted from the base station to the wireless device and / or uplink control signals sent / transmitted from the wireless device to the base station.

[0179] Downlink control signaling may include at least one of the following: a downlink scheduling assignment; an uplink scheduling grant indicating uplink radio resources and / or transmission format; time slot format information; a preemption indicator; a power control command; and / or any other suitable signaling. A wireless device may receive downlink control signaling in a payload sent / transmitted by a base station via a PDCCH. The payload sent / transmitted via the PDCCH may be referred to as DCI. The PDCCH may be a group common PDCCH (GC-PDCCH) shared by a group of wireless devices. The GC-PDCCH may be scrambled by a group common RNTI.

[0180] For example, the base station may attach one or more cyclic redundancy check (CRC) parity bits to the DCI to facilitate detection of transmission errors. For example, if the DCI is intended for a wireless device (or group of wireless devices), the base station may scramble the CRC parity bits with an identifier of the wireless device (or group of wireless devices). Scrambling the CRC parity bits with the identifier may include 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.

[0181] DCI can be used for different purposes. The purpose can be indicated by the type of RNTI used to scramble the CRC parity bits. DCI with CRC parity bits scrambled with a paging RNTI (P-RNTI) can indicate paging information and / or system information change notification. P-RNTI can be predefined as "FFFE" in hexadecimal. DCI with CRC parity bits scrambled with a system information RNTI (SI-RNTI) can indicate a broadcast transmission of system information. SI-RNTI can be predefined as "FFFF" in hexadecimal. DCI with CRC parity bits scrambled with a random access RNTI (RA-RNTI) can indicate a random access response (RAR). DCI with CRC parity bits scrambled with a cell RNTI (C-RNTI) can indicate a dynamically scheduled unicast transmission and / or the triggering of a PDCCH ordered random access. DCI with CRC parity bits scrambled with a temporary cell RNTI (TC-RNTI) can indicate contention resolution (e.g., similar to Figure 13A Other RNTIs configured by the base station for the wireless device may include a configured scheduling RNTI (CS RNTI), a transmit power control PUCCH RNTI (TPC PUCCH-RNTI), a transmit power control PUSCH RNTI (TPC-PUSCH-RNTI), a transmit power control SRS RNTI (TPC-SRS-RNTI), an interruption RNTI (INT-RNTI), a slot format indication RNTI (SFI-RNTI), a semi-persistent CSI RNTI (SP-CSI-RNTI), a modulation and coding scheme cell RNTI (MCS-C RNTI), and the like.

[0182] A base station may send / transmit DCI using one or more DCI formats, for example, depending on the purpose and / or content of the DCI. DCI format 0_0 may be used to schedule a PUSCH in a cell. DCI format 0_0 may be a fallback DCI format (e.g., having a compact DCI payload). DCI format 0_1 ​​may be used to schedule a PUSCH in a cell (e.g., having a larger DCI payload than DCI format 0_0). DCI format 1_0 may be used to schedule a PDSCH in a cell. DCI format 1_0 may be a fallback DCI format (e.g., having a compact DCI payload). DCI format 1_1 may be used to schedule a PDSCH in a cell (e.g., having a larger DCI payload than DCI format 1_0). DCI format 2_0 may be used to provide a slot format indication to a group of wireless devices. DCI format 2_1 may be used to notify / inform a group of wireless devices of physical resource blocks and / or OFDM symbols, wherein the group of wireless devices may assume that no transmission is intended for the group of wireless devices. DCI format 2_2 can be used to transmit transmit power control (TPC) commands for PUCCH or PUSCH. DCI format 2_3 can be used to transmit a set of TPC commands for SRS transmission of one or more wireless devices. DCI formats for new functions may be defined in future releases. DCI formats can have different DCI sizes or can share the same DCI size.

[0183] For example, after scrambling the DCI with RNTI, the base station can process the DCI with channel coding (e.g., polarity coding), rate matching, scrambling and / or QPSK modulation. The base station can map the coded and modulated DCI to resource elements used for and / or configured for PDCCH. The base station can, for example, send / transmit DCI via a PDCCH occupying multiple consecutive control channel elements (CCEs) based on the effective load size of the DCI and / or the coverage of the base station. The number of consecutive CCEs (referred to as the aggregation level) can be 1, 2, 4, 8, 16 and / or any other suitable number. CCE may include a certain number (e.g., 6) of resource element groups (REGs). REG may include a resource block in an OFDM symbol. The mapping of the coded and modulated DCI on the resource element can be based on the mapping of CCE and REG (e.g., CCE to REG mapping).

[0184] Figure 14AAn example of a core set configuration is shown. The core set configuration can be used for a portion of the bandwidth or any other frequency band. The base station can send / transmit DCI via the PDCCH on one or more control resource sets (core sets). A core set may include time-frequency resources that a wireless device attempts to use one or more search spaces to decode the DCI. The base station can configure the size and location of the core sets in the time-frequency domain. The first core set 1401 and the second core set 1402 may appear at the first symbol in a time slot, or may be configured at the first symbol in a time slot. The first core set 1401 may overlap with the second core set 1402 in the frequency domain. The third core set 1403 may appear at the third symbol in a time slot, or may be configured at the third symbol in a time slot. The fourth core set 1404 may appear at the seventh symbol in a time slot, or may be configured at the seventh symbol in a time slot. The core sets may have different numbers of resource blocks in the frequency domain.

[0185] Figure 14B An example of CCE to REG mapping is shown. CCE to REG mapping for DCI transmission can be performed via CORESET and PDCCH processing. CCE to REG mapping can be interleaved mapping (e.g., for the purpose of providing frequency diversity) or non-interleaved mapping (e.g., for the purpose of facilitating interference coordination and / or frequency selective transmission of control channels). The base station can perform different or the same CCE to REG mapping on different CORESETs. A CORESET can be associated with a CCE to REG mapping (e.g., via RRC configuration). The CORESET can be configured with an antenna port QCL parameter. The antenna port QCL parameter can indicate QCL information for DM-RS received via the PDCCH of the CORESET.

[0186] The base station may send / transmit one or more RRC messages including configuration parameters for one or more CORESETs and one or more search space sets to the wireless device. These configuration parameters may indicate the association 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). These configuration parameters may indicate at least one of the following: the number of PDCCH candidates to be monitored per aggregation level; PDCCH monitoring periodicity and PDCCH monitoring mode; one or more DCI formats to be monitored by the wireless device; and / or whether the search space set is a common search space set or a wireless device-specific search space set (e.g., a UE-specific search space set). The set of CCEs in the common search space set may be predefined and known to the wireless device. The set of CCEs in the wireless device-specific search space set (e.g., a UE-specific search space set) may be configured, for example, based on the identity of the wireless device (e.g., C-RNTI).

[0187] like Figure 14B As shown, the wireless device may determine the time-frequency resources for the CORESET based on one or more RRC messages. For example, the wireless device may determine the CCE to REG mapping for the CORESET (e.g., interleaved or non-interleaved and / or mapping parameters) based on the configuration parameters of the CORESET. For example, the wireless device may determine the number of search space sets configured on / for the CORESET based on the one or more RRC messages (e.g., up to 10). The wireless device may monitor the PDCCH candidate set based on the configuration parameters of the search space set. The wireless device may monitor the PDCCH candidate set in one or more CORESETs to detect one or more DCIs. Monitoring may include decoding one or more PDCCH candidates of the PDCCH candidate set based on the monitored DCI format. Monitoring may include decoding the DCI content of one or more PDCCH candidates using a possible (or configured) PDCCH position, a possible (or configured) PDCCH format (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 wireless device-specific search space), and a possible (or configured) DCI format. Decoding may be referred to as blind decoding. The wireless device may determine that the DCI is valid for the wireless device, for example, based on a CRC check (e.g., a match between the scrambled bits of the CRC parity bits of the DCI and the RNTI value) (e.g., thereafter or in response thereto). The wireless device may process information included in the DCI (e.g., scheduling assignments, uplink grants, power control, slot format indications, downlink preemption, etc.).

[0188] Uplink control signaling (e.g., UCI) may be sent / transmitted to a base station. The uplink control signaling may include a HARQ acknowledgment for a received DL-SCH transport block. The wireless device may, for example, send / transmit the HARQ acknowledgment based on (e.g., after or in response to) receiving the DL-SCH transport block. The uplink control signaling may include CSI indicating the channel quality of the physical downlink channel. The wireless device may send / transmit the CSI to the base station. Based on the received CSI, the base station may determine the transport format parameters for downlink transmission (e.g., including multiple antennas and beamforming schemes). The uplink control signaling may include a scheduling request (SR). The wireless device may send / transmit the SR indicating that uplink data is available for transmission to the base station. The wireless device may send / transmit UCI (e.g., HARQ acknowledgment (HARQ-ACK), CSI report, SR, etc.) via the PUCCH or PUSCH. The wireless device may send / transmit the uplink control signaling via the PUCCH using one of several PUCCH formats.

[0189] There may be multiple PUCCH formats (e.g., five PUCCH formats). The wireless device may determine the PUCCH format, for example, based on the size of the UCI (e.g., the number / number of uplink symbols for UCI transmission and the number of UCI bits). PUCCH format 0 may have a length of one or two OFDM symbols and may include two bits or less. If transmission is performed over / via one or two symbols and the number / number of HARQ-ACK information bits (HARQ-ACK / SR bits) with positive or negative SR is one or two bits, the wireless device may send / transmit UCI via PUCCH resources, for example, using PUCCH format 0. PUCCH format 1 may occupy multiple OFDM symbols (e.g., between four and fourteen OFDM symbols) and may include two bits or less. For example, if transmission is performed over / via four or more symbols and the number of HARQ-ACK / SR bits is one or two bits, the wireless device may use PUCCH format 1. PUCCH format 2 may occupy one or two OFDM symbols and may include more than two bits. For example, if the transmission is over / via one or two symbols and the number of UCI bits is two or more bits, the wireless device may use PUCCH format 2. PUCCH format 3 may occupy multiple OFDM symbols (e.g., between four and fourteen OFDM symbols) and may include more than two bits. For example, if the transmission is four or more symbols, the number of UCI bits is two or more bits, and the PUCCH resource does not include an orthogonal cover code (OCC), the wireless device may use PUCCH format 3. PUCCH format 4 may occupy multiple OFDM symbols (e.g., between four and fourteen OFDM symbols) and may include more than two bits. For example, if the transmission is four or more symbols, the number of UCI bits is two or more bits, and the PUCCH resource includes an OCC, the wireless device may use PUCCH format 4.

[0190] The base station may send / transmit configuration parameters for multiple PUCCH resource sets to the wireless device, for example, using an RRC message. Multiple PUCCH resource sets may be configured on the uplink BWP of the cell (e.g., up to four sets in NR, or up to any other number of sets in other systems). A PUCCH resource set may be configured with a PUCCH resource set index, a plurality of PUCCH resources, and / or a number (e.g., a maximum number) of UCI information bits, where the PUCCH resource is identified by a PUCCH resource identifier (e.g., pucch-resourceid), and the wireless device may use one of the multiple PUCCH resources in the PUCCH resource set to send / transmit the UCI information bits. If multiple PUCCH resource sets are configured, the wireless device may select one of the multiple PUCCH resource sets based on, for example, the total bit length of the UCI information bits (e.g., HARQ-ACK, SR, and / or CSI). For example, if the total bit length of the UCI information bits is two bits or less, the wireless device may select the first PUCCH resource set with a PUCCH resource set index equal to "0". For example, if the total bit length of the UCI information bits is greater than two bits and less than or equal to the first configured value, the wireless device may select a second PUCCH resource set having a PUCCH resource set index equal to "1." For example, if the total bit length of the UCI information bits is greater than the first configured value and less than or equal to the second configured value, the wireless device may select a third PUCCH resource set having a PUCCH resource set index equal to "2." For example, if the total bit length of the UCI information bits is greater than the second configured value and less than or equal to a third value (e.g., 1406, 1706, or any other number of bits), the wireless device may select a fourth PUCCH resource set having a PUCCH resource set index equal to "3."

[0191] For example, after determining a PUCCH resource set from a plurality of PUCCH resource sets, the wireless device may determine a PUCCH resource from a PUCCH resource set for UCI (HARQ-ACK, CSI, and / or SR) transmission. The wireless device may determine the PUCCH resource based on, for example, a PUCCH resource indicator in DCI (e.g., DCI format 1_0 or DCI for 1_1) received on / via the PDCCH. The n-bit (e.g., three-bit) PUCCH resource indicator in the DCI may indicate one of a plurality (e.g., eight) PUCCH resources in the PUCCH resource set. The wireless device may transmit / transmit UCI (HARQ-ACK, CSI, and / or SR) using the PUCCH resource indicated by the PUCCH resource indicator in the DCI, for example, based on the PUCCH resource indicator.

[0192] Figure 15A1502 and base station 1504 may be part of a communication network, such as a Figure 1A The communication network 100 shown in Figure 1B The communication network 150 shown in FIG. 1 or any other communication network. A communication network may include more than one wireless device and / or more than one base station, having Figure 15A The base stations are configured substantially the same or similarly to those shown in FIG.

[0193] The base station 1504 can connect the wireless device 1502 to a core network (not shown) via radio communication over an air interface (or radio interface) 1506. The direction of communication from the base station 1504 to the wireless device 1502 over the air interface 1506 can be referred to as downlink. The direction of communication from the wireless device 1502 to the base station 1504 over the air interface can be referred to as uplink. For example, various duplexing schemes (e.g., FDD, TDD, and / or some combination of duplexing techniques) can be used to separate downlink transmissions from uplink transmissions.

[0194] For the downlink, data to be transmitted from the base station 1504 to the wireless device 1502 may be provided / transmitted / sent to the processing system 1508 of the base station 1504. The data may be provided / transmitted / sent to the processing system 1508 via, for example, the core network. For the uplink, data to be transmitted from the wireless device 1502 to the base station 1504 may be provided / transmitted / sent to the processing system 1518 of the wireless device 1502. The processing system 1508 and the processing system 1518 may implement layer 3 and layer 2 OSI functions to process the data for transmission. Layer 2 may include, for example, information about Figure 2A 、 Figure 2B 、 Figure 3 and Figure 4A The SDAP layer, PDCP layer, RLC layer and MAC layer described in the previous section may include, for example, Figure 2B Describes the RRC layer.

[0195] Data to be transmitted to wireless device 1502 may be provided / transmitted / sent to transmission processing system 1510 of base station 1504, for example, after being processed by processing system 1508. Data to be transmitted to base station 1504 may be provided / transmitted / sent to transmission processing system 1520 of wireless device 1502, for example, after being processed by processing system 1518. Transmission processing system 1510 and transmission processing system 1520 may implement layer 1 OSI functions. Layer 1 may include, for example, information regarding Figure 2A 、 Figure 2B 、 Figure 3 and Figure 4AFor transport processing, the PHY layer may perform, for example, forward error correction coding of transport channels, interleaving, rate matching, mapping of transport channels to physical channels, modulation of physical channels, and multiple-input multiple-output (MIMO) or multi-antenna processing.

[0196] The receive processing system 1512 of the base station 1504 may receive uplink transmissions from the wireless device 1502. The receive processing system 1512 of the base station 1504 may include one or more TRPs. The receive processing system 1522 of the wireless device 1502 may receive downlink transmissions from the base station 1504. The receive processing system 1522 of the wireless device 1502 may include one or more antenna panels. The receive processing system 1512 and the receive processing system 1522 may implement layer 1 OSI functions. Layer 1 may include, for example, information about Figure 2A 、 Figure 2B 、 Figure 3 and Figure 4A For receive processing, the PHY layer may perform, for example, error detection, forward error correction decoding, deinterleaving, demapping of transport channels to physical channels, demodulation of physical channels, MIMO or multi-antenna processing, and the like.

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

[0198] Processing system 1508 and processing system 1518 may be associated with memory 1514 and memory 1524, respectively. Memory 1514 and memory 1524 (e.g., one or more non-transitory computer-readable media) may store computer program instructions or code that can be executed by processing system 1508 and / or processing system 1518, respectively, to perform one or more of the functions (e.g., one or more functions described herein and other functions of a general-purpose computer, processor, memory, and / or other peripheral devices). 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-transitory computer-readable media) that stores computer program instructions or code that can be executed to perform one or more of their respective functions. Transmitting processing system 1520 and / or receiving processing system 1522 may be coupled to memory 1524 and / or another memory (e.g., one or more non-transitory computer-readable media) that stores computer program instructions or code that can be executed to perform one or more of their respective functions.

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

[0200] The processing system 1508 can be connected to one or more peripheral devices 1516. The processing system 1518 can be connected to one or more peripheral devices 1526. The one or more peripheral devices 1516 and the one or more peripheral devices 1526 can include software and / or hardware that provides features and / or functionality, such as a speaker, a microphone, a keypad, a display, a touchpad, a power source, a satellite transceiver, a universal serial bus (USB) port, a hands-free headset, a frequency modulation (FM) radio unit, a media player, an Internet browser, an electronic control unit (e.g., for a motor vehicle), and / or one or more sensors (e.g., an accelerometer, a gyroscope, a temperature sensor, a radar sensor, a laser sensor, an ultrasonic sensor, a light sensor, a camera, etc.). The processing system 1508 and / or the processing system 1518 can receive input data (e.g., user output data) and / or provide output data (e.g., user output data) from and / or to the one or more peripheral devices 1516 and / or the one or more peripheral devices 1526. The processing system 1518 in the wireless device 1502 can receive power from a power source and / or can be configured to distribute power to other components in the wireless device 1502. The power source can include one or more power sources, such as a battery, a solar cell, a fuel cell, or any combination thereof. The processing system 1508 can be connected to a global positioning system (GPS) chipset 1517. The processing system 1518 can be connected to a global positioning system (GPS) chipset 1527. The GPS chipset 1517 and the GPS chipset 1527 can be configured to determine and provide geographic location information for the wireless device 1502 and the base station 1504, respectively.

[0201] Figure 15B16. Example elements of a computing device that can be used to implement any of the various devices described herein are shown, including, for example, base stations 160A, 160B, 162A, 162B, 220, and / or 1504, wireless devices 106, 156A, 156B, 210, and / or 1502, or any other base station, wireless device, AMF, UPF, network device, or computing device described herein. Computing device 1530 may include one or more processors 1531 that can execute instructions stored in random access memory (RAM) 1533, removable media 1534 (such as a universal serial bus (USB) drive, compact disk (CD) or digital versatile disk (DVD), or floppy disk drive), or any other desired storage medium. Instructions may also be stored in an attached (or internal) hard drive 1535. Computing device 1530 may also include a security processor (not shown) that can execute instructions of one or more computer programs to monitor processes executing on processor 1531 and any processes requesting access to any hardware and / or software components of 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.). Computing device 1530 may include one or more output devices, such as a display 1536 (e.g., a screen, display device, monitor, television, etc.), and may include one or more output device controllers 1537, such as a video processor. One or more user input devices 1538 may also be present, such as a remote control, keyboard, mouse, touch screen, microphone, etc. Computing device 1530 may also include one or more network interfaces (such as network interface 1539), which may be wired interfaces, wireless interfaces, or a combination of both. The network interface 1539 can provide an interface for the computing device 1530 to communicate with the network 1540 (e.g., a RAN or any other network). The network interface 1539 can include a modem (e.g., a cable modem), and the external network 1540 can include a communication link, an external network, a home network, a provider's wireless, coaxial cable, fiber optic or hybrid fiber optic / coaxial cable distribution system (e.g., a DOCSIS network), or any other desired network. In addition, the computing device 1530 can include a location detection device, such as a global positioning system (GPS) microprocessor 1541, which can be configured to receive and process global positioning signals and determine the geographic location of the computing device 1530 with the possible help of an external server and antenna.

[0202] Figure 15BThe examples in the example may be hardware configurations, but the components shown may also be implemented as software. Modifications may be made to add, remove, combine, divide, etc., components of the computing device 1530 as needed. In addition, the components may be implemented using basic computing devices and components, and any other computing devices and components described herein may be implemented using the same components (e.g., processor 1531, ROM storage device 1532, display 1536, etc.). For example, the various components described herein may be implemented using a computing device having a component (such as a processor) that executes computer-executable instructions stored on a computer-readable medium, such as a processor. Figure 15B Some or all of the entities described herein may be software-based and may coexist on a common physical platform (e.g., the requesting entity may be a separate software process and program from the related entities, both of which may be executed as software on a common computing device).

[0203] Figure 16A An exemplary structure for uplink transmission is shown. Processing of a baseband signal representing a physical uplink shared channel may include / perform one or more functions. The one or more functions may include at least one of: scrambling; modulating scrambled bits to generate complex-valued symbols; mapping the complex-valued modulation symbols onto one or several transmission layers; transform precoding to generate complex-valued symbols; precoding the complex-valued symbols; mapping the precoded complex-valued symbols to resource elements; generating a complex-valued time-domain single carrier frequency division multiple access (SC-FDMA), a CP-OFDM signal for an antenna port, or any other signal; and the like. For example, if transform precoding is enabled, an SC-FDMA signal may be generated for uplink transmission. For example, if transform precoding is not enabled (e.g., as Figure 16A As shown in FIG, a CP-OFDM signal may be generated for uplink transmission. These functions are examples, and other mechanisms for uplink transmission may be implemented.

[0204] Figure 16B An exemplary structure for modulating and up-converting a baseband signal to a carrier frequency is shown. The baseband signal may be a complex-valued SC-FDMA, CP-OFDM baseband signal (or any other baseband signal) for an antenna port and / or a complex-valued physical random access channel (PRACH) baseband signal. For example, filtering may be performed / applied prior to transmission.

[0205] Figure 16CAn exemplary structure for downlink transmission is shown. Processing of a baseband signal representing a physical downlink channel may include / perform one or more functions. The one or more functions may include: scrambling coded bits in a codeword to be sent / transmitted on / via a physical channel; modulating the scrambled bits to generate complex-valued modulation symbols; mapping the complex-valued modulation symbols onto one or more transmission layers; precoding the complex-valued modulation symbols on a layer for transmission on an antenna port; mapping the complex-valued modulation symbols for an antenna port to resource elements; generating a complex-valued time-domain OFDM signal for the antenna port; and the like. These functions are examples, and other mechanisms for downlink transmission may be implemented.

[0206] Figure 16D An exemplary structure for modulating and up-converting a baseband signal to a carrier frequency is shown. The baseband signal may be a complex-valued OFDM baseband signal for an antenna port or any other signal. For example, filtering may be performed / applied prior to transmission.

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

[0208] A timer may, for example, begin running once started and continue running until it is stopped or expires. For example, if the timer is not running, the timer may be started, or if it is running, the timer may be restarted. A timer may be associated with a value (e.g., a timer may be started or restarted at a certain value, or may be started from zero and expire upon reaching the value). For example, the timer duration may not be updated until the timer is stopped or expires (e.g., due to a BWP switch). A timer may be used to measure a time period / window for a procedure. With respect to embodiments and / or procedures related to one or more timers or other parameters, it should be understood that there may be a variety of ways to implement the one or more timers or other parameters. One or more of the various ways of implementing a timer may be used to measure a time period / window for a procedure. A random access response window timer may be used to measure a time window for receiving a random access response. For example, rather than starting a random access response window timer and determining its expiration, the time difference between two timestamps may be used. For example, if the timer is restarted, the process for measuring the time window may be restarted. Other exemplary embodiments may be configured / provided to restart the measurement of the time window.

[0209] Figure 17 An exemplary TCI status update is shown. The TCI status update may include a unified beam update. The wireless device 1701 may receive one or more messages (e.g., at time T0). The wireless 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 wireless device, etc.). For example, the wireless device 1701 may receive one or more messages from a base station. The wireless device 1701 may receive one or more messages from a relay node. The wireless device 1701 may receive one or more messages from another wireless device (e.g., a TRP, a vehicle, a remote radio head, etc.). The one or more messages may include one or more configuration parameters (e.g., Figure 17 The one or more configuration parameters may include RRC configuration parameters. The one or more configuration parameters may include RRC reconfiguration parameters.

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

[0211] The wireless device may perform / perform uplink transmission (e.g., PUSCH, PUCCH, SRS) of the cell via the cell at a first time and a first frequency. The wireless device may perform / perform downlink reception (e.g., PDCCH, PDSCH) of the cell via the cell at a second time and a second frequency. The cell may operate in time division duplex (TDD) mode. For example, in TDD mode, the first frequency and the second frequency may be the same. For example, in TDD mode, the first time and the second time may be different. The cell may operate in frequency division duplex (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, wherein the first frequency and the second frequency may be the same or different, and / or wherein 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, wherein the first frequency and the second frequency may be the same or different, and / or wherein the first time and the second time may be the same or different. The cell may operate in one or more of TDD mode, FDD mode, CDM mode and / or SDM mode.

[0212] The wireless device may be in one of a plurality of RRC modes. For example, the wireless device may be in an RRC connected mode. The wireless device may be in an RRC idle mode. The wireless device may be in an RRC inactive mode.

[0213] A cell may include multiple BWPs. The multiple BWPs may include one or more uplink BWPs, including the uplink BWP of the cell. The multiple BWPs may include one or more downlink BWPs, including the downlink BWP of the cell.

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

[0215] In an active state of an uplink BWP among the one or more uplink BWPs, the wireless device may send (e.g., transmit) an uplink signal / channel (e.g., PUCCH, preamble, PUSCH, PRACH, SRS, etc.) on / via the uplink BWP. In an inactive state of an uplink BWP among the one or more uplink BWPs, the wireless device may not send (e.g., transmit) an uplink signal / channel (e.g., PUCCH, preamble, PUSCH, PRACH, SRS, etc.) on / via the uplink BWP.

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

[0217] The wireless device may activate an uplink BWP from one or more uplink BWPs of a cell. Activating the uplink BWP may include the wireless device setting (or switching) the uplink BWP to an active uplink BWP for the cell. Activating the uplink BWP may include setting the uplink BWP to an active state. Activating the uplink BWP may include switching the uplink BWP from an inactive state to an active state.

[0218] The one or more configuration parameters may be for an (active) downlink BWP of a cell.At least one configuration parameter of the one or more configuration parameters may be for a downlink BWP of a cell.

[0219] One or more configuration parameters may be used for an (active) uplink BWP for a cell. At least one of the one or more configuration parameters may be used for an uplink BWP for a cell. The one or more configuration parameters may indicate a subcarrier spacing (or parameter set) for a downlink BWP. The one or more configuration parameters may indicate a subcarrier spacing (or parameter set) for an uplink BWP.

[0220] The value of the subcarrier spacing (of the downlink BWP and / or uplink BWP) may be / indicate, for example, 15 kHz (μ=0) or any other frequency or frequency range. The value of the subcarrier spacing may be / indicate, for example, 30 kHz (μ=1). The value of the subcarrier spacing may be / indicate, for example, 60 kHz (μ=2). The value of the subcarrier spacing may be / indicate, for example, 120 kHz (μ=3). The value of the subcarrier spacing may be / indicate, for example, 240 kHz (μ=4). The value of the subcarrier spacing may be / indicate, for example, 480 kHz (μ=5). The value of the subcarrier spacing may be / indicate, 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 frequency range may be valid / applicable in any FR(n) (for example, μ may be equal to any value).

[0221] One or more configuration parameters may indicate a plurality of control resource sets (CORESETs). The one or more configuration parameters may indicate the plurality of CORESETs for an (active) downlink BWP of a cell. The (active) downlink BWP may include the plurality of CORESETs.

[0222] One or more configuration parameters may indicate a plurality of CORESET indices / identifiers / indicators for the plurality of CORESETs (e.g., provided by a higher layer parameter ControlResourceSetId). Each CORESET in the plurality of CORESETs may be identified / indicated by a corresponding CORESET index in the plurality of CORESET indices. A first CORESET in the plurality of CORESETs may be identified by a first CORESET index in the plurality of CORESET indices. A second CORESET in the plurality of CORESETs may be identified by a second CORESET index in the plurality of CORESET indices.

[0223] One or more configuration parameters may indicate multiple TCI states (e.g., provided by a higher layer parameter tci-StatesToAddModList in PDSCH_Config, PUSCH_Config, PDCCH_Config, or PUCCH_Config, etc.). The one or more configuration parameters may be sent / received in one or more messages 1710, such as Figure 17 The one or more configuration parameters may indicate, for example, the multiple TCI states of the downlink BWP of the cell. Figure 17 In the embodiment, the plurality of TCI states may include TCI state 1, TCI state 2, ..., TCI state M.

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

[0225] One or more configuration parameters may indicate a plurality of TCI state indices / identifiers / indicators for the plurality of TCI states (e.g., provided by a higher layer parameter TCI-StateId). Each TCI state in the plurality of TCI states may be identified / indicated by a corresponding TCI state index in the plurality of TCI state indices. A first TCI state in the plurality of TCI states may be identified by a first TCI state index in the plurality of TCI state indices. A second TCI state in the plurality of TCI states may be identified by a second TCI state index in the plurality of TCI state indices.

[0226] Multiple TCI states (or at least one of the multiple TCI states) may be used for (decoding) PDSCH transmission / reception of a cell. One or more configuration parameters may indicate the multiple TCI states (or at least one of the multiple TCI states) used for decoding PDSCH transmission / reception of a downlink BWP of a cell. The TCI states in the multiple TCI states may indicate a quasi-co-located reference signal (e.g., via SourceRs-Info) for a DM-RS (or DM-RS antenna port) used for PDSCH transmission / reception.

[0227] Multiple TCI states (or at least one of the multiple TCI states) may be used for PDCCH transmission / reception of a cell. One or more configuration parameters may indicate the multiple TCI states (or at least one of the multiple TCI states) used for PDCCH transmission / reception of a downlink BWP of the cell. A TCI state in the multiple TCI states may indicate a quasi-co-located reference signal for a DM-RS (or DM-RS antenna port) used for PDCCH transmission / reception.

[0228] Multiple TCI states (or at least one of the multiple TCI states) may be used for CSI-RS transmission / reception of a cell. One or more configuration parameters may indicate the multiple TCI states (or at least one of the multiple TCI states) used for CSI-RS transmission / reception of a downlink BWP of the cell. A TCI state in the multiple TCI states may indicate a quasi-co-located reference signal used for CSI-RS transmission / reception.

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

[0230] Multiple TCI state pools / groups may include multiple TCI states. For example, two TCI state pools / groups may include multiple TCI states. A first TCI state pool in the two TCI state pools may include multiple downlink TCI states from the multiple TCI states. A second TCI state pool in the two TCI state pools may include multiple uplink TCI states from the multiple TCI states.

[0231] A (single) TCI state pool / group may include multiple TCI states. The multiple TCI states may include / may be multiple downlink TCI states. The multiple TCI states may include / may be multiple uplink TCI states.

[0232] A wireless device may apply / use multiple downlink TCI states to receive / decode transport blocks (or PDSCH transmissions / receptions). The wireless device may use multiple downlink TCI states, for example, to receive / decode transport blocks (or PDSCH transmissions / receptions) scheduled for a cell's downlink BWP. The wireless device may use multiple downlink TCI states, for example, to receive downlink signals (e.g., PDSCH transmissions / receptions, PDCCH transmissions / receptions, DCI, transport blocks, CSI-RS, etc.) via the cell's downlink BWP. For example, the wireless device may not use multiple downlink TCI states (or each of the multiple downlink TCI states) to transmit uplink signals (e.g., PUSCH transmissions, PUCCH transmissions, UCI, transport blocks, SRS, etc.). A TCI state in the multiple downlink TCI states may indicate / have / include a reference signal that is quasi-co-located with a DM-RS used for a downlink signal (e.g., PDSCH / PDCCH transmissions / receptions). The reference signal may be quasi-co-located with the DM-RS of the downlink signal. The reference signal may be quasi-co-located with the DM-RS of the downlink signal relative to a quasi-co-location type (e.g., QCL type A, QCL type B, QCL type C, QCL type D, QCL type E, etc.). The TCI state may indicate / include / have a quasi-co-location type for the reference signal. A TCI state in a plurality of downlink TCI states may indicate a quasi-co-located reference signal for reception of a downlink signal (e.g., CSI-RS). Each of the plurality of downlink TCI states may indicate a corresponding reference signal for quasi-co-location of the DM-RS of the downlink signal (e.g., PDSCH / PDCCH transmission / reception). Each of the plurality of downlink TCI states may indicate a corresponding reference signal for quasi-co-location of the DM-RS of the downlink signal (e.g., CSI-RS).

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

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

[0235] The 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 "Separate" or "Separate UL / DL TCI State" to indicate a separate UL / DL TCI state mode.

[0236] The multiple TCI states may include / may include multiple common / joint TCI states (or multiple common / joint uplink and downlink TCI states). A wireless device may use the multiple common / joint TCI states, for example, to receive downlink signals (e.g., PDSCH, PDCCH, CSI-RS, DCI, transport blocks, etc.) via a cell's downlink BWP. The wireless device may use the multiple common / joint TCI states, for example, to transmit uplink signals (e.g., PUSCH, PUCCH, UCI, transport blocks, SRS, etc.) via a cell's uplink BWP. The wireless device may use each of the multiple common / joint TCI states, for example, for receiving downlink signals and transmitting uplink signals. A TCI state in the multiple TCI states (or multiple common / joint TCI states) may indicate a quasi-co-located reference signal for a DM-RS used for downlink signals (e.g., PDSCH / PDCCH transmission / reception). A TCI state in a plurality of TCI states (or a plurality of common / joint TCI states) may indicate a quasi-co-located reference signal for reception of a downlink signal (e.g., a CSI-RS). Each TCI state in the plurality of TCI states (or a plurality of common / joint TCI states) may indicate a corresponding quasi-co-located reference signal for reception of a DM-RS for a downlink signal (e.g., PDSCH / PDCCH transmission / reception). Each TCI state in the plurality of TCI states (or a plurality of common / joint TCI states) may indicate a corresponding quasi-co-located reference signal for reception of a downlink signal (e.g., CSI-RS). The wireless device may determine a spatial domain transmission filter / beam based on the reference signal indicated by (or in) the TCI state in the plurality of TCI states (or a plurality of common / joint TCI states) for transmission of an uplink signal. The wireless device may determine a corresponding spatial domain transmission filter / beam for transmission of an uplink signal based on the reference signal indicated by (or in) each TCI state in the plurality of TCI states (or a plurality of common / joint TCI states).

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

[0238] The wireless device may receive an activation command 1720, such as Figure 17 The activation command may be in one or more messages (e.g., DCI, MAC-CE, UE-specific MAC CE TCI state activation / deactivation, Figure 17 The activation command may activate / select / instruct / update a subset of the plurality of TCI states. The subset of the plurality of TCI states may include / may be, for example, one or more TCI states from the plurality of TCI states. The subset of the plurality of TCI states may include / may be, for example, a first plurality of TCI states from the plurality of TCI states. For example, Figure 17 , a subset of the multiple TCI states are TCI State 4, TCI State 5, TCI State 8, TCI State 26, TCI State 61 and TCI State 42.

[0239] The activation command may include one or more fields indicating / including a subset of multiple TCI states / indicating / identifying at least one TCI state index of the subset. The multiple TCI state indexes may include the at least one TCI state index. Each TCI state of the subset of multiple TCI states may be identified / indicated by a corresponding TCI state index in the at least one TCI state index. The one or more fields may be set to a value (e.g., one) indicating activation of the subset of multiple TCI states. Based on the one or more fields indicating that the subset of multiple TCI states is set to the value, the wireless device may activate the subset of multiple TCI states. The wireless device may activate the subset of multiple TCI states, for example, based on receiving the activation command to activate / select / indicate / update the subset of multiple TCI states.

[0240] The wireless device may map a subset of the multiple TCI states to one or more TCI code points (e.g., Figure 17 000, 001, ..., 110, and 011 in the TCI code points in the . ... Figure 17 In the embodiment of the present invention, TCI state 4 can be mapped to TCI code point 000; TCI state 5 and TCI state 8 can be mapped to TCI code point 001; TCI state 26 and TCI state 61 can be mapped to TCI code point 110; and TCI state 42 can be mapped to TCI code point 111. Each TCI code point in the one or more TCI code points can be equal to the value of the TCI field in the DCI. The DCI can schedule or not schedule a transport block (e.g., PDSCH, PUSCH). The TCI field in the DCI can indicate (or be equal to) a TCI code point in the one or more TCI code points. A TCI code point can include / indicate at least one TCI state of a subset of the multiple TCI states.

[0241] A TCI state for a subset of multiple TCI states may indicate a reference signal with / for a quasi co-location type (e.g., QCL Type A, QCL Type D). The TCI state may not include / indicate the BWP index / ID and / or cell index / ID of the reference signal. The wireless device may assume that the reference signal is configured in the downlink BWP of the cell to which the TCI state applies.

[0242] A subset of the multiple TCI states may be used for (decoding) PDSCH transmission / reception of a cell. The activation command may indicate activation of a subset of the multiple TCI states for decoding PDSCH transmission / reception of a downlink BWP of a cell.

[0243] A subset of multiple TCI states may be used for uplink resources (e.g., PUSCH resources, PUCCH resources, SRS resources) of a cell, for transmission of uplink signals (e.g., UCI, PUSCH, SRS, PUCCH, transport blocks, SR, CSI, CSI reports, HARQ-ACK) on / for / on / via uplink resources of the cell's uplink BWP. The activation command may indicate activation of a subset of multiple TCI states for transmission of uplink signals on / for / on / via uplink resources of the cell's uplink BWP.

[0244] A subset of the multiple TCI states may include one or more downlink TCI states. The wireless device may use the one or more downlink TCI states to receive or decode a transport block (or PDSCH transmission or reception). The wireless device may use the one or more downlink TCI states, for example, to receive or decode a transport block (or PDSCH transmission or reception) scheduled or configured for a cell's downlink BWP. The wireless device may use the one or more downlink TCI states, for example, to receive or decode a downlink signal (e.g., PDSCH, PDCCH, DCI, CSI-RS, transport block, etc.) via the cell's downlink BWP.

[0245] A subset of the plurality of TCI states may include one or more uplink TCI states. The wireless device may use one or more uplink TCI states to transmit a transport block (or PUSCH transmission). The wireless device may use one or more uplink TCI states, for example, to transmit a transport block (or PUSCH transmission) scheduled / configured for the uplink BWP of a cell. The wireless device may use one or more uplink TCI states, for example, to transmit an uplink signal (e.g., PUSCH, PUCCH, UCI, transport block, SRS, etc.) via the uplink BWP of a cell.

[0246] A subset of the multiple TCI states may include one or more common / joint TCI states. A wireless device may use one or more common / joint TCI states, for example, to receive downlink signals (e.g., PDSCH, PDCCH, DCI, CSI-RS, transport blocks, etc.) via a cell's downlink BWP. A wireless device may use one or more common / joint TCI states, for example, to transmit uplink signals (e.g., PUSCH, PUCCH, UCI, transport blocks, 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.

[0247] The wireless device may receive a downlink signal 1730 such as Figure 17As shown in . A downlink signal may be sent / 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, for example, based on the TCI state of a subset of multiple TCI states. The wireless device may, for example, receive DCI that schedules / triggers the reception / transmission of a downlink signal. For example, the DCI may indicate a dynamic uplink / downlink grant. The DCI may, for example, indicate the activation of an SPS PDSCH transmission. The wireless device may receive a downlink signal (e.g., a transport block) transmitted by an SPS PDSCH. The DCI may include a TCI field indicating a TCI state (or a TCI code point including / indicating a TCI state). One or more configuration parameters may indicate / configure / schedule / trigger the transmission / reception of a downlink signal (e.g., periodic CSI-RS, PDCCH / PDSCH transmission, etc.). The one or more configuration parameters may include / indicate a TCI field indicating a TCI state (or a TCI code point including / indicating a TCI state) for transmission / reception of a downlink signal.

[0248] Receiving a downlink signal based on the TCI state may include quasi-co-location of at least one DMRS antenna port of the downlink signal (e.g., PDSCH / PDCCH transmission, transport block) with a reference signal (e.g., CSI-RS, SS / PBCH block, SRS, PUCCH, etc.) indicated by the TCI state. The at least one DMRS antenna port of the downlink signal may be quasi-co-located with the reference signal with respect to a quasi-co-location 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-co-location 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 for the TCI state.

[0249] Receiving a downlink signal based on the TCI state may include quasi-co-location 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-co-located with the reference signal relative to a quasi-co-location 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-co-location 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 for the TCI state.

[0250] Receiving a downlink signal based on the TCI state may include receiving the downlink signal using a spatial domain reception / reception filter / beam for receiving a reference signal indicated by the TCI state. The spatial domain reception / reception filter / beam for receiving the downlink signal may be the same as (or substantially the same as, separated by x degrees, where x = 0, 1, 5, 10, etc.) the spatial domain reception / reception filter / beam for receiving the reference signal.

[0251] A wireless device may send (e.g., transmit) an uplink signal (e.g., a transport block, PUCCH / PUSCH transmission, SRS, aperiodic SRS, PUCCH, aperiodic PUCCH, UCI, etc.) based on the TCI state of a subset of a plurality of TCI states. The wireless device may, for example, receive DCI that schedules / trigger transmission of the uplink signal. For example, the DCI may indicate a dynamic uplink / downlink grant. The DCI may, for example, indicate activation of a configured uplink grant (e.g., a type 2 configured uplink grant). The wireless device may send (e.g., transmit) an uplink signal (e.g., a transport block) with the configured uplink grant. The DCI may include a TCI field that indicates the TCI state (or a TCI codepoint that includes / indicates the TCI state). One or more configuration parameters may indicate / configure / schedule / trigger transmission of the uplink signal (e.g., periodic SRS, PUCCH / PUSCH transmission, periodic PUCCH, configured uplink grant, etc.). The one or more configuration parameters may include or indicate a TCI field indicating a TCI state (or a TCI codepoint including or indicating a TCI state) for transmission of an uplink signal. The one or more configuration parameters may indicate a TCI state for a configured uplink grant (e.g., a type 1 configured uplink grant). The wireless device may send (e.g., transmit) an uplink signal (e.g., a transport block) for the configured uplink grant (e.g., a type 1 configured uplink grant).

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

[0253] The wireless device may monitor PDCCH transmissions in / via a CORESET for DCI based on the TCI state. The multiple CORESETs may include the CORESET. The downlink BWP of a cell (or one or more CORESETs in a downlink BWP) may include the CORESET. A subset of the multiple TCI states may include the TCI state. The subset of TCI states may include or may not include the TCI state. The wireless device may receive a second activation command indicating activation of the TCI state of the CORESET. The second activation command may be the same as or different from the activation command (in Figure 17 Monitoring PDCCH transmission in the CORESET based on the TCI state may include quasi-co-location of at least one DMRS antenna port of the PDCCH transmission in the CORESET with a reference signal (e.g., CSI-RS, SS / PBCH block, SRS, etc.) indicated by the TCI state. The at least one DMRS antenna port may be quasi-co-located with the reference signal with respect to a quasi-co-location 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-co-location type.

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

[0255] The number of one or more TCI code points may be greater than one. Figure 17 DCI 1 at time T2 in . 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, ....

[0256] The DCI may include a TCI field. The TCI field may indicate a TCI code point among one or more TCI code points. The TCI field (e.g., Figure 17 The value of 110 at step 1730 in the DCI field may be, for example, equal to the TCI code point. The value of the TCI field may, for example, indicate the TCI code point. The TCI code point (e.g., 110) may indicate / include at least two TCI states. The DCI may indicate activation of at least two TCI states (or may activate 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 In the example, 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). The DCI may indicate the activation of one TCI state (e.g., TCI state 42). The DCI may indicate the activation of at least two TCI states (or any other number of TCI states).

[0257] A first TCI state among the at least two TCI states may be identified / indicated by a first TCI state index. A second TCI state among the at least two TCI states may be identified / indicated by a second TCI state index. The plurality of TCI state indexes may include the first TCI state index. The plurality of TCI state indexes may include the second TCI state index. At least one TCI state index among the plurality of TCI state indexes may include the first TCI state index. At least one TCI state index among the plurality of TCI state indexes may include the second TCI state index.

[0258] The at least two TCI states may be / include at least two unified TCI states. The first TCI state may be / include a first unified TCI state. The second TCI state may be / include a second unified TCI state.

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

[0260] A 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 among at least two TCI states in a TCI code point (or indicated by it). The position / location of the second TCI state may be the second earliest / second highest / second lowest in the vector of at least two TCI states. In the vector of at least two TCI states, the position / location of the first TCI state may be earlier than (or before) the position / location of the second TCI state. In the vector of at least two TCI states, the position / location of the second TCI state may be later than (e.g., after) the position / location of the first TCI state. The second TCI state may occur second in the vector / set / list of at least two TCI states. For example, if the vector of at least two TCI states is equal to [TCI state 26, TCI state 61], the second / second starting / second earliest TCI state (or second TCI state) is TCI state 61. For example, if the vector of at least two TCI states is equal to [TCI state 2, TCI state 1], the second / second starting / second earliest TCI state (or second TCI state) is TCI state 1.

[0261] The DCI may schedule the transmission of a transport block (e.g., PDSCH, PUSCH). The DCI may include, for example, a downlink assignment indicating the resources used for the transport block. The DCI may include, for example, an uplink grant / assignment indicating the resources used for the transport block. The wireless device may send (e.g., transmit) the transport block via the resources.

[0262] The DCI may not schedule the transmission of a transport block (e.g., PDSCH / PUSCH transmission). The DCI may not include, for example, a downlink assignment. The DCI may not include, for example, an uplink grant / assignment. The CRC of the DCI may be scrambled with an RNTI (e.g., a CS-RNTI). The RV field of the DCI may be set to (or may indicate or may be equal to) one (e.g., all “1s”) by the base station, for example. The MCS field of the DCI may be set to (or may indicate or may be equal to) one (e.g., all “1s”) by the base station, for example. The New Data Indicator (NDI) field of the DCI may be set to (or may indicate or may be equal to) zero (e.g., all “0s”) by the base station, for example. The FDRA field of the DCI may be set to (or may indicate or may be equal to) zero (e.g., all “0s”), for example, for FDRA Type 0. The FDRA field of the DCI may be set to (or may indicate or may be equal to) one (e.g., all “1s”), for example, for FDRA Type 1. The FDRA field of the DCI may be set to (or may indicate or may be equal to) zero (e.g., all “0s”), for example, for dynamic switching.

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

[0264] The wireless device may apply (or start using) at least two TCI states starting from a start / initial / earliest / first time slot, for example, a certain 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). ). The wireless device may apply (or begin using) at least two TCI states starting from a starting / initial / earliest / first time slot, where the starting / initial / earliest / first time slot is at least the number of symbols from / after the last / end / latest symbol of the uplink signal (e.g., beam application time, MAC-CE activation time). The starting / initial / earliest / first time slot may occur at least the number of symbols from / after the last / end / latest symbol of the uplink signal. The number of symbols (e.g., beam application time) may be based on the capabilities of the wireless device. For example, the wireless device may send (e.g., transmit) a capability message (e.g., a UE capability message) indicating the number of symbols. For example, the wireless device may send (e.g., transmit) a capability message (e.g., a UE capability message) indicating the minimum and / or maximum number of symbols. One or more configuration parameters (e.g., via an RRC parameter beamAppTime) may indicate the number of symbols. One or more configuration parameters (e.g., via an RRC parameter beamAppTime) may indicate the number of symbols, for example, based on the minimum / maximum number of symbols. The number of symbols may be, for example, equal to or greater than the minimum and / or maximum number of symbols. The number of symbols may be, for example, equal to or less than the minimum and / or maximum number of symbols. The number of symbols may be, for example, based on the subcarrier spacing (e.g., μ) of the downlink BWP. The number of symbols may be, for example, based on the subcarrier spacing (e.g., μ) of the uplink BWP.

[0265] The wireless device may apply (or start using) the time slot specified by the activation command (e.g., in the first slot) starting from the start / initial / earliest / first slot, for example, based on the number of one or more TCI code points being equal to one. Figure 17 The at least two TCI states indicated / activated by DCI 1) at time T1 in.

[0266] The wireless device may apply (or start using) the code points specified by the DCI (e.g., in the first slot) starting from the start / initial / earliest / first slot, for example, based on the number of one or more TCI code points being greater than one. Figure 17 The at least two TCI states indicated / activated at time T2 in .

[0267] The at least two TCI states may be / include at least two uplink TCI states. The multiple uplink TCI states may include the at least two uplink TCI states. The first TCI state may be / include a first uplink TCI state among the at least two uplink TCI states. The second TCI state may be / include a second uplink TCI state among the at least two uplink TCI states. The wireless device may apply / use the at least two uplink TCI states, for example, for transmitting uplink signals (e.g., PUSCH transmission, PUCCH transmission, UCI, transport block, SRS, etc.) via an uplink BWP of a cell.

[0268] Using / applying at least two uplink TCI states to transmit uplink signals may include sending (e.g., transmitting) one or more first uplink signals (e.g., PUSCH transmission, PUCCH transmission, UCI, transport block, SRS, etc.) using a first spatial domain transmission filter / beam determined based on a first reference signal indicated by a first uplink TCI state. The first spatial domain transmission / transmission filter / beam may, for example, be the same as (or substantially the same as, separated by x degrees, x = 0, 1, 5, 10, etc.) a spatial domain reception / reception filter / beam used to receive the first reference signal. The first spatial domain transmission / transmission filter / beam may, for example, be the same as (or substantially the same as, separated by x degrees, x = 0, 1, 5, 10, etc.) a spatial domain transmission / transmission filter / beam used to send (e.g., transmit) the first reference signal. Transmitting uplink signals using / applying at least two uplink TCI states may include sending (e.g., transmitting) one or more first uplink signals at a first transmission power, the first transmission power being determined based on one or more first power control parameters (e.g., target received power, closed-loop index, path loss compensation factor, α, path loss reference signal, etc.) indicated by the first uplink TCI state (or contained in, associated with, or mapped to the first uplink TCI state). The uplink signals may include one or more first uplink signals. Transmitting uplink signals using / applying at least two uplink TCI states may include sending (e.g., transmitting) one or more second uplink signals (e.g., PUSCH transmission, PUCCH transmission, UCI, transport block, SRS, etc.) using a second spatial domain transmission filter / beam determined based on a second reference signal indicated by a second uplink TCI state. The second spatial domain transmission / transmission filter / beam can, for example, be the same as (or substantially the same as, separated by x degrees, x = 0, 1, 5, 10, etc.) the spatial domain reception / reception filter / beam used to receive the second reference signal. The second spatial domain transmission / transmission filter / beam can, for example, be the same as (or substantially the same as, separated by x degrees, x = 0, 1, 5, 10, etc.) the spatial domain transmission / transmission filter / beam used to send (e.g., transmit) the second reference signal. Using / applying at least two uplink TCI states to transmit uplink signals can include sending (e.g., transmitting) one or more second uplink signals at a second transmission power, the second transmission power being determined based on one or more second power control parameters (e.g., target receive power, closed loop index, path loss compensation factor, α, path loss reference signal, etc.) indicated by (or contained in or associated with or mapped to) the second uplink TCI state.The uplink signal may include one or more second uplink signals.

[0269] The at least two TCI states may include or may include at least two downlink TCI states. The multiple downlink TCI states may include at least two downlink TCI states. The first TCI state may include or may include a first downlink TCI state among the at least two downlink TCI states. The second TCI state may include or may include a second downlink TCI state among the at least two downlink TCI states. The wireless device may apply or use the at least two downlink TCI states, for example, to receive downlink signals (e.g., PDSCH transmission / reception, PDCCH transmission / reception, CSI-RS, DMRS, etc.) via a downlink BWP of a cell.

[0270] Using / applying at least two downlink TCI states to receive 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 downlink TCI state. The first spatial domain receive / receive filter / beam may, for example, be the same as (or substantially the same, x degrees apart, 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, for example, be the same as (or substantially the same, x degrees apart, x = 0, 1, 5, 10, etc.) as the spatial domain transmit / transmit filter / beam used to send (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 to receive downlink signals 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 downlink TCI state. The second spatial domain receive / receive filter / beam may, for example, be the same as (or substantially the same, x degrees apart, 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, for example, be the same as (or substantially the same, x degrees apart, x = 0, 1, 5, 10, etc.) as the spatial domain transmit / transmit filter / beam used to send (e.g., transmit) the second reference signal. The downlink signal may include one or more second downlink signals.

[0271] Receiving downlink signals using / applying at least two downlink TCI states may include quasi-co-locating DM-RSs (or DM-RS antenna ports) of one or more first downlink signals (e.g., PDSCH, PDCCH, CSI-RS, DMRS, etc.) with a first reference signal indicated by the first downlink TCI state. The DM-RSs (or DM-RS antenna ports) of the one or more first downlink signals may be quasi-co-located with the first reference signal relative to a first quasi-co-location 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. Receiving downlink signals using / applying at least two downlink TCI states may include quasi-co-locating DM-RSs (or DM-RS antenna ports) of one or more second downlink signals (e.g., PDSCH, PDCCH, CSI-RS, DMRS, etc.) with a second reference signal indicated by a second downlink TCI state. The DM-RS (or DM-RS antenna ports) of one or more second downlink signals can be quasi-co-located with the second reference signal relative to a second quasi-co-location 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.

[0272] Receiving downlink signals using / applying at least two downlink TCI states may include quasi-co-location of one or more first downlink signals (e.g., CSI-RS, DMRS, etc.) with a first reference signal indicated by the first downlink TCI state. The one or more first downlink signals may be quasi-co-located with the first reference signal relative to a first quasi-co-location type indicated by the first downlink TCI state. Receiving downlink signals using / applying at least two downlink TCI states may include quasi-co-location of one or more second downlink signals (e.g., CSI-RS, DMRS, etc.) with a second reference signal indicated by a second downlink TCI state. The one or more second downlink signals may be quasi-co-located with the second reference signal relative to a second quasi-co-location type indicated by the second downlink TCI state.

[0273] The 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). The multiple common / joint TCI states may include at least two common / joint TCI states. The first TCI state may be / include a first common / joint TCI state among the at least two common / joint TCI states. The second TCI state may be / include a second common / joint TCI state among the at least two common / joint TCI states. The wireless device may apply / use the at least two common / joint TCI states, for example, to receive downlink signals (e.g., PDSCH, PDCCH, CSI-RS, DMRS, etc.) via the downlink BWP of the cell. The wireless device may apply / use the at least two common / joint TCI states, for example, to transmit uplink signals (e.g., PUSCH, PUCCH, UCI, transport block, SRS, etc.) via the uplink BWP of the cell. The wireless device may apply / use the at least two common / joint TCI states to receive downlink signals and transmit uplink signals.

[0274] Using / applying at least two common / joint TCI states to receive 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, for example, be the same as (or substantially the same, x degrees apart, 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, for example, be the same as (or substantially the same, x degrees apart, x=0, 1, 5, 10, etc.) as the spatial domain transmit / transmit filter / beam used to send (e.g., transmit) the first reference signal. The downlink signal may include one or more first downlink signals. Using / applying at least two common / joint TCI states to receive downlink signals 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, for example, be the same as (or substantially the same, x degrees apart, 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, for example, be the same as (or substantially the same, x degrees apart, x=0, 1, 5, 10, etc.) as the spatial domain transmit / transmit filter / beam used to send (e.g., transmit) the second reference signal. The downlink signal may include one or more second downlink signals.

[0275] Receiving downlink signals using / applying at least two common / joint TCI states may include quasi-co-locating DMRSs (or DM-RS antenna ports) of one or more first downlink signals (e.g., PDSCH, PDCCH, CSI-RS, DMRS, etc.) with a first reference signal indicated by the first common / joint TCI state. The DM-RSs (or DM-RS antenna ports) of the one or more first downlink signals may be quasi-co-located with the first reference signal relative to a first quasi-co-location 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. Receiving downlink signals using / applying at least two common / joint TCI states may include quasi-co-locating DMRSs (or DM-RS antenna ports) of one or more second downlink signals (e.g., PDSCH, PDCCH, CSI-RS, DMRS, etc.) with a second reference signal indicated by a second common / joint TCI state. The DM-RS (or DM-RS antenna ports) of one or more second downlink signals can be quasi-co-located with the second reference signal relative to a second quasi-co-location 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.

[0276] Receiving downlink signals using / applying at least two common / joint TCI states may include quasi-co-location of one or more first downlink signals (e.g., CSI-RS, DMRS, etc.) with a first reference signal indicated by the first common / joint TCI state. The one or more first downlink signals may be quasi-co-located with the first reference signal with respect to a first quasi-co-location type indicated by the first common / joint TCI state. Receiving downlink signals using / applying at least two common / joint TCI states may include quasi-co-location of one or more second downlink signals (e.g., CSI-RS, DMRS, etc.) with a second reference signal indicated by a second common / joint TCI state. The one or more second downlink signals may be quasi-co-located with the second reference signal with respect to a second quasi-co-location type indicated by the second common / joint TCI state.

[0277] Using / applying at least two common / joint TCI states to transmit uplink signals may include sending (e.g., transmitting) one or more first uplink signals (e.g., PUSCH transmission, PUCCH transmission, UCI, transport block, SRS, etc.) using a first spatial domain transmission filter / beam determined based on a first reference signal indicated by a first common / joint TCI state. The first spatial domain transmission / transmission filter / beam may, for example, be the same as (or substantially the same, separated by x degrees, x = 0, 1, 5, 10, etc.) a spatial domain reception / reception filter / beam used to receive the first reference signal. The first spatial domain transmission / transmission filter / beam may, for example, be the same as (or substantially the same, separated by x degrees, x = 0, 1, 5, 10, etc.) a spatial domain transmission / transmission filter / beam used to send (e.g., transmit) the first reference signal. Transmitting uplink signals using / applying at least two common / joint TCI states may include sending (e.g., transmitting) one or more first uplink signals at a first transmission power, wherein the first transmission power is determined based on one or more first power control parameters (e.g., target received power, closed-loop index, path loss compensation factor, α, path loss reference signal, etc.) indicated by the first common / joint TCI state (or included in the first common / joint TCI state, associated with the first common / joint TCI state, or mapped to the first common / joint TCI state). The uplink signal may include one or more first uplink signals.

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

[0279] Figure 18 An example of an uplink repetition scheme is shown. One or more wireless devices may repeat (transmit) an uplink signal (e.g., PUSCH transmission, transport block, PUCCH transmission, uplink control information, HARQ-ACK, SR, CSI report, SRS) across multiple transmission / repetition opportunities, within multiple transmission / repetition opportunities, or in multiple transmission / repetition opportunities. One or more wireless devices may send (e.g., transmit) repetitions of an uplink signal across multiple transmission opportunities, within multiple transmission opportunities, or in multiple transmission opportunities.

[0280] One or more configuration parameters may indicate a repetition scheme (e.g., an FDM scheme, a TDM scheme, an SFN scheme, an SDM scheme, a CDM scheme). One or more wireless devices may repeat (or transmit) an uplink signal across multiple transmission / repetition opportunities / within multiple transmission / repetition opportunities / in multiple transmission / repetition opportunities, for example, based on the one or more configuration parameters indicating the repetition scheme. One or more wireless devices may send (or transmit) repetitions of an uplink signal across multiple transmission opportunities / within multiple transmission opportunities / in multiple transmission opportunities, for example, based on the one or more configuration parameters indicating the repetition scheme.

[0281] One or more wireless devices may receive a DCI that schedules / triggering the transmission of an uplink signal. The DCI may indicate a repetition scheme (e.g., an FDM scheme, a TDM scheme, an SFN scheme, an SDM scheme, a CDM scheme). The DCI may include one or more fields indicating the repetition scheme (e.g., an SRI field, a TCI field, an antenna port field, a PUCCH resource indicator field, an SRS resource set indicator field, etc.). The one or more fields may be set to / equal to one or more values ​​indicating the repetition scheme. Each of the one or more fields may be set to a corresponding value from the one or more values. The one or more wireless devices may, for example, repeat (transmit) the uplink signal across multiple transmissions / repetition opportunities / within multiple transmissions / repetition opportunities / in multiple transmissions / repetition opportunities based on the DCI indicating the repetition scheme. The wireless device may, for example, send (e.g., transmit) repetitions of the uplink signal across multiple transmission opportunities / within multiple transmission opportunities / in multiple transmission opportunities based on the DCI indicating the repetition scheme.

[0282] A repetition scheme may be used for repetition of transport blocks via uplink resources (eg, PUCCH resources, SRS resources, PUSCH resources). The repetition scheme may be (set to) for example, time domain repetition (eg, Figure 18 The repetition scheme may be (set to) for example frequency domain repetition (e.g., Figure 18 The repetition scheme may be (set to) for example code / space domain repetition (e.g., Figure 18 SDM / SFN in ).

[0283] The repetition of the uplink signal may be, for example, a time domain repetition (eg, Figure 18 In the time domain repetition, multiple transmission opportunities may not overlap in time. Each transmission opportunity in the multiple transmission opportunities may have a non-overlapping time domain resource allocation relative to other transmission opportunities in the multiple transmission opportunities. For example, a first transmission opportunity in the multiple transmission opportunities may not overlap in time with a second transmission opportunity in the multiple transmission opportunities. The first transmission opportunity and the second transmission opportunity may be different. In the time domain repetition, multiple transmission opportunities may or may not overlap in frequency. The multiple transmission opportunities may include a first TX opportunity, a second TX opportunity, a third TX opportunity, and a fourth TX opportunity in the time domain repetition (for example, Figure 18In time domain repetition, the repetition of the uplink signal may occur, for example, within / within a time unit (e.g., TDM-ed). For example, a wireless device may repeat the transmission of an uplink signal across / on / within a time unit. For example, one or more wireless devices may send (e.g., transmit) a repetition of an uplink signal across / on / within a time unit. For example, the time unit may be continuous. For example, the time unit may not be continuous (e.g., may have time / symbol / time slot gaps). The number / quantity of time units may be equal to the number / quantity of repetitions of the uplink signal. For example, the time unit may be a time slot. For example, the time unit may be a micro-time slot. For example, the time unit may be a time symbol (e.g., an OFDM symbol). For example, the time unit may be a subframe. For example, the time unit may be an actual / nominal repetition. Multiple transmission opportunities may occur within / within a time unit. For example, a first transmission opportunity of a plurality of transmission opportunities may occur within / within a first time unit of a time unit. A second transmission opportunity in the plurality of transmission opportunities may occur within a second one of the time units, etc. The first time unit may be different from the second time unit. The first time unit may not overlap with the second time unit in time.

[0284] For example, the repetition of the uplink signal may be a frequency domain repetition (eg, Figure 18 In frequency domain repetition, multiple transmission opportunities may or may not overlap in time. In frequency domain repetition, multiple transmission opportunities may not overlap in frequency. Each transmission opportunity in the multiple transmission opportunities may have a non-overlapping frequency domain resource allocation relative to other transmission opportunities in the multiple transmission opportunities. For example, a first transmission opportunity in the multiple transmission opportunities may not overlap in frequency with a second transmission opportunity in the multiple transmission opportunities. The first transmission opportunity and the second transmission opportunity may overlap in time. The first transmission opportunity and the second transmission opportunity may be different. The multiple transmission opportunities may include a first TX opportunity and a second TX opportunity in frequency domain repetition (for example, Figure 18In frequency domain repetition, repetition of the uplink signal may occur, for example, within a frequency unit (e.g., frequency, resource block (RB), physical resource block (PRB), frequency band, subband, bandwidth part, cell). For example, one or more wireless devices may repeat transmission of the uplink signal across / on / within the frequency unit. For example, one or more wireless devices may send (e.g., transmit) repetitions of the uplink signal across / on / within the frequency unit. For example, the frequency unit may be contiguous. For example, the frequency unit may not be contiguous (e.g., may have frequency / PRB / RB gaps). The number / quantity of frequency units may be equal to the number / quantity of repetitions of the uplink signal. For example, the frequency unit may be a frequency band. For example, the frequency unit may be a PRB (or RB). For example, the frequency unit may be a BWP. For example, the frequency unit may be a cell. Multiple transmission opportunities may occur within / within the frequency unit. For example, a first transmission opportunity among the multiple transmission opportunities may occur within / within a first frequency unit among the frequency units. A second transmission opportunity in the plurality of transmission opportunities may occur within a second frequency unit in the frequency units, etc. The first frequency unit may be different from the second frequency unit. The first frequency unit and the second frequency unit may not overlap in frequency.

[0285] For example, the repetition of the uplink signal may be code / space domain repetition (eg, Figure 18 SDM / SFN, SDM scheme, CDM scheme, SDMScheme, CDMScheme, etc. in code / space domain repetition). In code / space domain repetition, multiple transmission opportunities may overlap in time. In code / space domain repetition, multiple transmission opportunities may overlap in frequency. In code / space domain repetition, multiple transmission opportunities may be transmission opportunities (e.g., or a single transmission opportunity). Each transmission opportunity in the multiple transmission opportunities may be the same (or the same as the transmission opportunity or the single transmission opportunity). Each transmission opportunity in the multiple transmission opportunities may have overlapping frequency domain resource allocation relative to other transmission opportunities in the multiple transmission opportunities. Each transmission opportunity in the multiple transmission opportunities may have overlapping time domain resource allocation relative to other transmission opportunities in the multiple transmission opportunities. For example, a first transmission opportunity in the multiple transmission opportunities may overlap with a second transmission opportunity in the multiple transmission opportunities in time and frequency. 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. The multiple transmission opportunities are the first TX opportunity and the second TX opportunity in the code / space domain repetition (e.g., Figure 18In code / space domain repetition, the first TX opportunity and the second TX opportunity may be the same (e.g., may overlap in time and frequency). In code / space domain repetition, multiple transmission opportunities may occur within the same frequency unit (e.g., frequency, RB, PRB, frequency band, bandwidth portion, cell). For example, the first frequency unit of the first transmission opportunity and the second frequency unit of the second transmission opportunity may overlap in frequency. 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 within the same time unit (e.g., symbol, actual / nominal repetition, mini-slot, time slot, subframe, etc.). For example, the first time unit of the first transmission opportunity and the second frequency unit of the second 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.

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

[0287] The wireless device may receive one or more messages, wherein the one or more messages include one or more configuration parameters. The one or more configuration parameters may include a CSI multiplexing mode parameter. The CSI multiplexing mode parameter may be (set to) enabled.

[0288] In at least some wireless communications, for example, based on one or more configuration parameters including a CSI multiplexing mode parameter being set to enabled, a wireless device may send (e.g., transmit) / multiplex a CSI report (or other information) in more than one repetition (transmission opportunity) of a PUSCH transmission (e.g., a first repetition (or first transmission opportunity) of the PUSCH transmission and a second repetition (or second transmission opportunity) of the PUSCH transmission. The wireless device may send (e.g., transmit) the first repetition of the PUSCH transmission in the first transmission opportunity. The wireless device may send (e.g., transmit) the second repetition of the PUSCH transmission in 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.

[0289] The one or more configuration parameters may not include a CSI multiplexing mode parameter (or may not include a CSI multiplexing mode parameter set to enabled). The one or more configuration parameters may include a CSI multiplexing mode parameter set to disabled (or not set to enabled). In at least some wireless communications, for example, based on the one or more configuration parameters not including the CSI multiplexing mode parameter being set to enabled, the wireless device may send (e.g., transmit) a CSI report (or other information) in a first repetition (or first transmission opportunity) of a PUSCH transmission. The wireless device may send (e.g., transmit) the first repetition of the PUSCH transmission in the first transmission opportunity. For example, based on the one or more configuration parameters not including the CSI multiplexing mode parameter being set to enabled, the wireless device may not send (e.g., transmit) / multiplex a CSI report in a second repetition (or second transmission opportunity) of the PUSCH transmission. The wireless device may not send (e.g., transmit) the second repetition of the PUSCH transmission in the second transmission opportunity. The repetition of the PUSCH transmission may include a first repetition. The first repetition may be the earliest / starting / first / initial repetition of the repetition of the PUSCH transmission.

[0290] The repetition of an uplink transmission (e.g., a PUSCH transmission) may be, for example, in the frequency domain. The repetition of the PUSCH transmission may be a frequency domain repetition. The repetition of the uplink transmission (e.g., a PUSCH transmission) may start at the same time / symbol (or simultaneously), for example, based on the repetition being in the frequency domain. A first repetition of the PUSCH transmission may start in a first symbol. A second repetition of the PUSCH transmission may start in a second symbol. For example, based on the repetition being in the frequency domain, the first symbol and the second symbol may be the same (or substantially similar). In at least some wireless communications, for example, based on the repetition of the PUSCH transmission starting at the same time / symbol in the frequency domain repetition, sending (e.g., transmitting) a CSI report (or other information) in the earliest / starting / first / initial repetition of the PUSCH transmission may not be effective for frequency domain repetition. Each of the repetitions of the PUSCH transmission may be the earliest / starting / first / initial repetition of the PUSCH transmission. For example, if the base station and the wireless device are not aligned with the repetitions of the PUSCH transmission in which the CSI report (or other information) is sent (e.g., transmitted) / multiplexed to the wireless device, the base station may not receive / decode the repetitions of the PUSCH transmission. For example, the wireless device may send (e.g., transmit) / multiplex the CSI report (or other information) in a first repetition of the PUSCH transmission. The wireless device may not send (e.g., transmit) / multiplex the CSI report (or other information) in a second repetition of the PUSCH transmission. The base station may not have information about the repetitions that the wireless device sent (e.g., transmitted) / multiplexed the CSI report (or other information). The base station may decode one / each repetition of the PUSCH transmission under two different assumptions (e.g., 1) the repetition is multiplexed with the CSI report (or other information), and 2) no CSI report is multiplexed in the repetition). This operation of the base station may increase power consumption at the base station.

[0291] As described herein, transmission / multiplexing of CSI reports (or other information) for frequency domain repetition / frequency domain repetition can be enhanced by, for example, aligning the operation of the base station and the wireless device. The wireless device may send (e.g., transmit) / multiplex CSI reports (or other information) in repetitions among repetitions of PUSCH transmissions based on a rule, such as sending / transmitting with the lowest / highest starting / ending frequency / resource block (RB). The wireless device may send (e.g., transmit) / multiplex CSI reports (or other information) in repetitions among repetitions of PUSCH transmissions that are sent (e.g., transmitted) with the antenna panel having the lowest / highest antenna panel index / identifier. The wireless device may send (e.g., transmit) / multiplex CSI reports (or other information) in repetitions among repetitions of PUSCH transmissions that are sent (e.g., transmitted) based on the TCI state (e.g., transmit beam) having the lowest TCI state index. The wireless device may send (eg, transmit) / multiplex a CSI report (or other information) in a repetition among repetitions of the PUSCH transmission, which is sent (eg, transmitted) based on the first TCI state (or the first SRS resource set).

[0292] The wireless device may send (e.g., transmit) / multiplex a CSI report (or other information) in multiple repetitions of a PUSCH transmission in the frequency domain. The wireless device may send (e.g., transmit) / multiplex a CSI report (or other information) in each of the repetitions of the PUSCH transmission in the frequency domain. Sending (e.g., transmitting) / multiplexing a CSI report (or other information) in each of the repetitions of the PUSCH transmission may increase robustness and diversity. In the frequency domain repetitions, the wireless device may not determine / check whether one or more configuration parameters include a CSI multiplexing mode parameter (or other parameter) set to enabled or disabled. In the frequency domain repetitions, the wireless device may send (e.g., transmit) / multiplex a CSI report (or other information) in each of the repetitions of the PUSCH transmission regardless of whether the CSI multiplexing mode parameter (or other parameter) is set to enabled. In the time domain repetitions, the wireless device may determine / check whether one or more configuration parameters include a CSI multiplexing mode parameter (or other parameter) set to enabled or disabled. In time domain repetition, the wireless device may send (e.g., transmit) / multiplex a CSI report (or other information) in each of the repetitions of the PUSCH transmission based on whether one or more configuration parameters including a CSI multiplexing mode parameter (or other parameters) are set to enabled.

[0293] The examples described herein may provide advantages, such as by helping to align a base station and a wireless device when the wireless device sends (e.g., transmits) / multiplexes one or more repetitions of a CSI report (or other information). Such alignment may achieve advantages such as reducing power consumption at the base station, increasing the probability of successful decoding of a PUSCH transmission, and / or other advantages apparent from the description herein.

[0294] Figure 19 An example of report multiplexing is shown. One or more configuration parameters may indicate at least two SRS resource sets. The at least two SRS resource sets may include a first SRS resource set and a second SRS resource set. The one or more configuration parameters may include a usage parameter. The one or more configuration parameters may include, for example, corresponding usage parameters for an SRS resource set (e.g., each SRS resource set in at least two SRS resource sets). The usage parameter may be set to a codebook. The usage parameter of an SRS resource set (e.g., each SRS resource set in at least two SRS resource sets) may be set to a codebook. One or more configuration parameters may indicate, for example, 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 for the first SRS resource set (or a usage parameter set to the codebook). One or more configuration parameters may indicate a codebook for the second SRS resource set (or a usage parameter set to the codebook).

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

[0296] One or more configuration parameters may indicate at least two SRS resource set indexes for at least two SRS resource sets. One or more configuration parameters may indicate corresponding SRS resource set indexes (e.g., in at least two SRS resource set indexes) for an SRS resource set (e.g., each SRS resource set in at least two SRS resource sets). An SRS resource set (e.g., each SRS resource set in at least two SRS resource sets) may be identified / indicated by a corresponding SRS resource set index (e.g., in at least two SRS resource set indexes). A first SRS resource set in at least two SRS resource sets may be identified / indicated by a first SRS resource set index in at least two SRS resource set indexes. A second SRS resource set in at least two SRS resource sets may be identified / indicated by a second SRS resource set index in at least two SRS resource set 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.

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

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

[0299] The DCI may include at least one field (e.g., an SRS resource set indicator, a TCI field, a unified TCI status field, a TRP indicator field, etc.). The field may indicate, for example, multiple TRP uplink repetitions (e.g., multiple TRP PUSCH repetitions, multiple TRPPUCCH repetitions). The value of the field may indicate multiple TRP uplink repetitions. The value of the field may indicate multiple TRP PUSCH repetitions. The value of the field may indicate multiple TRP PUCCH repetitions. The size / length of the field may be, for example, two bits (or any other number of bits). For example, the value of the field (e.g., the SRS resource set indicator) may be equal to '10' or any other value. For example, the value of the field (e.g., the SRS resource set indicator) may be equal to '11'. The size / length of the field may be, for example, one bit. For example, the value of the field (e.g., the SRS resource set indicator) may be equal to '1'.

[0300] The DCI may schedule repetitions of an uplink transmission. For example, the DCI may schedule repetitions of a PUSCH transmission. The wireless device may send (e.g., transmit) repetitions of an uplink transmission (e.g., a PUSCH transmission) in a plurality of transmission opportunities. The wireless device may send (e.g., transmit) at least one repetition of the uplink transmission (e.g., each repetition of the PUSCH transmission) in a corresponding transmission opportunity in the plurality of transmission opportunities. The wireless device may send (e.g., transmit) a first repetition of the PUSCH transmission in a first transmission opportunity in the plurality of transmission opportunities. The wireless device may send (e.g., transmit) a second repetition of the PUSCH transmission in a second transmission opportunity in the plurality of transmission opportunities.

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

[0302] The PUSCH transmission may, for example, include / carry (or may have) a transport block. For example, the PUSCH transmission may not include / carry (or may not have) a transport block. The wireless device may determine / assume that the number of repetitions of the PUSCH transmission is (or is equal to) two, for example, based on the PUSCH transmission not including / carrying a transport block. The wireless device may determine / assume that the number of repetitions of the PUSCH transmission is (or is equal to) two, for example, based on the PUSCH transmission not including / carrying a transport block. The wireless device may determine / assume that the number of repetitions of the PUSCH transmission is (or is equal to) two, for example, based on the PUSCH transmission not having a transport block. The wireless device may determine / assume that the number of repetitions of the PUSCH transmission is two, regardless of the value of the higher layer (e.g., RRC) parameter numberOfRepetitions or the value of the higher layer parameter pusch-AggregationFactor. The one or more configuration parameters may include, for example, the higher layer parameter numberOfRepetitions. The one or more configuration parameters may include, for example, the higher layer parameter pusch-AggregationFactor.

[0303] The one or more configuration parameters may include a CSI multiplexing mode parameter. The CSI multiplexing mode parameter may be (set to) enabled. The CSI multiplexing mode parameter may indicate whether to enable sending (e.g., transmitting) CSI reports on at least two repetitions of a PUSCH transmission. The at least two repetitions of a PUSCH transmission may be, for example, in the time domain (e.g., Figure 18 CSI multiplexing mode parameters may be used / applicable to time domain repetition (e.g., Figure 18 The at least two repetitions of the PUSCH transmission may be, for example, in the frequency domain (e.g., Figure 18 The CSI multiplexing mode parameters may be used / applicable to frequency domain repetition (e.g., Figure 18 The at least two repetitions of the PUSCH transmission may, for example, not be in the frequency domain (e.g., Figure 18 The CSI multiplexing mode parameter may not be used for / applicable to frequency domain repetition (e.g., Figure 18

[0045] At least two repetitions of the PUSCH transmission may be associated with at least two SRS resource sets. A first repetition of the at least two repetitions of the PUSCH transmission may be associated with a first SRS resource set in the at least two SRS resource sets. A second repetition of the at least two repetitions of the PUSCH transmission may be associated with a second SRS resource set in the at least two SRS resource sets.

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

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

[0306] One or more wireless devices may send (e.g., transmit) a message, such as a capability message (e.g., a UE capability message). The message (e.g., a UE capability message) may indicate, for example, support for sending (e.g., transmitting) a CSI report (or other information) in / on at least two repetitions of an uplink transmission (e.g., a PUSCH transmission). The capability message may indicate, for example, support for sending (e.g., transmitting) a CSI report (or other information) in / on at least two transmission opportunities of at least two repetitions of a PUSCH transmission. The capability message may indicate, for example, support for multiplexing a CSI report in / on at least two repetitions of a PUSCH transmission. For example, based on the capability message indicating support for sending (e.g., transmitting) / multiplexing a CSI report in / on at least two repetitions of a PUSCH transmission (or at least two transmission opportunities), the one or more configuration parameters may include a CSI multiplexing mode parameter (or the CSI multiplexing mode parameter is set to enabled).

[0307] The one or more configuration parameters may include a CSI multiplexing FDM mode parameter (or a CSI-FDM multiplexing mode parameter or a CSI-frequency multiplexing mode parameter, etc.). The CSI multiplexing FDM mode parameter may be (set to) enabled. The CSI multiplexing FDM mode parameter may be, for example, different from the CSI multiplexing mode parameter.

[0308] The CSI multiplexing FDM mode parameter may indicate whether sending (eg, transmitting) CSI reports (or other information) on at least two repetitions of a PUSCH transmission is enabled. The at least two repetitions of a PUSCH transmission may be in the frequency domain (eg, Figure 18 CSI multiplexing FDM mode parameters can be used / applicable to frequency domain repetition (e.g., Figure 18

[0045] At least two repetitions of the PUSCH transmission may be associated with at least two SRS resource sets. A first repetition of the at least two repetitions of the PUSCH transmission may be associated with a first SRS resource set in the at least two SRS resource sets. A second repetition of the at least two repetitions of the PUSCH transmission may be associated with a second SRS resource set in the at least two SRS resource sets.

[0309] The CSI multiplexing FDM mode parameter may be, for example, an 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.

[0310] The CSI multiplexing FDM mode parameter may be, for example, a 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.

[0311] One or more wireless devices may send (e.g., transmit) a message, such as a UE capability message. The message (e.g., UE capability message) may indicate, for example, support for sending (e.g., transmitting) CSI reports in / on at least two repetitions of an uplink transmission (e.g., a PUSCH transmission). The at least two repetitions of the PUSCH transmission may be in the frequency domain (e.g., Figure 18 The capability message may indicate, for example, support for sending (e.g., transmitting) a CSI report in / on at least two transmission opportunities of at least two repetitions of PUSCH transmission. The capability message may indicate, for example, support for multiplexing a CSI report in / on at least two repetitions of PUSCH transmission. For example, based on the capability message indicating support for sending (e.g., transmitting) / multiplexing a CSI report in / on at least two repetitions of PUSCH transmission (or at least two transmission opportunities), the one or more configuration parameters may include a CSI multiplexing FDM mode parameter (or the CSI multiplexing FDM mode parameter is set to enabled).

[0312] The one or more configuration parameters may not include a CSI multiplexing mode parameter (eg, AP-CSI multiplexing mode, SP-CSI multiplexing mode). The one or more configuration parameters may not include a CSI multiplexing mode parameter being set to enabled.

[0313] One or more wireless devices may send (e.g., transmit) a message, such as a UE capability message. The message (e.g., UE capability message) may not indicate, for example, support for sending (e.g., transmitting) a CSI report in / on at least two repetitions of an uplink transmission (e.g., a PUSCH transmission). The capability message may not indicate, for example, support for sending (e.g., transmitting) a CSI report in / on at least two transmission opportunities of at least two repetitions of a PUSCH transmission. The capability message may not indicate, for example, support for multiplexing a CSI report in / on at least two repetitions of a PUSCH transmission. For example, based on the capability message not indicating support for sending (e.g., transmitting) / multiplexing a CSI report in / on at least two repetitions (or at least two transmission opportunities) of a PUSCH transmission, the one or more configuration parameters may not include a CSI multiplexing mode parameter (or the CSI multiplexing mode parameter may be set to enabled).

[0314] The one or more configuration parameters may not include a CSI multiplexing FDM mode (eg, AP-CSI multiplexing FDM mode, SP-CSI multiplexing FDM mode). The one or more configuration parameters may not include a CSI multiplexing FDM mode parameter being set to enabled.

[0315] One or more wireless devices may send (e.g., transmit) a message, such as a UE capability message. The message (e.g., UE capability message) may not indicate, for example, support for sending (e.g., transmitting) CSI reports in / on at least two repetitions of an uplink transmission (e.g., a PUSCH transmission). The at least two repetitions of the PUSCH transmission may be in the frequency domain (e.g., Figure 18 The UE capability message may not indicate, for example, support for sending (e.g., transmitting) a CSI report in / on at least two transmission opportunities of at least two repetitions of PUSCH transmission. The capability message may not indicate, for example, support for multiplexing a CSI report in / on at least two repetitions of PUSCH transmission. For example, based on the capability message not indicating support for sending (e.g., transmitting) / multiplexing a CSI report in / on at least two repetitions (or at least two transmission opportunities) of PUSCH transmission, the one or more configuration parameters may not include a CSI multiplexing FDM mode parameter (or the CSI multiplexing FDM mode parameter may be set to enabled).

[0316] One or more configuration parameters may indicate a repetition scheme. The repetition scheme may be (or be set to) frequency domain repetition (e.g., frequency domain multiplexing (FDM) repetition). The repetition of the uplink transmission (e.g., PUSCH transmission) may be in the frequency domain. The repetition of the uplink transmission (e.g., PUSCH transmission) may be in the frequency domain, for example, based on one or more configuration parameters indicating (set to) a repetition scheme of frequency domain repetition. The repetition of the PUSCH transmission may include a first repetition (e.g., Figure 19 in repetition 1) and in repetition 2 ( Figure 19 The first repetition and the second repetition may overlap in time (e.g., completely in time, partially in time, in at least one symbol). The starting symbol of the first repetition and the starting symbol of the second repetition may be, for example, the same. The ending symbol of the first repetition and the ending symbol of the second repetition may be, for example, the same. The first repetition and the second repetition may not overlap in frequency. The first repetition and the second repetition may be in different frequencies (or different RBs or different PRBs). The first repetition and the second repetition may not overlap in at least one RB (or PRB).

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

[0318] The one or more second repetitions of the PUSCH transmission may include a second repetition (e.g., Figure 19 2). The second repetition may be associated with a second SRS resource set in the at least two SRS resource sets. The wireless device may, for example, send (e.g., transmit) a second repetition of the PUSCH transmission based on the second SRS resource set. The wireless device may, for example, send (e.g., transmit) a second repetition of the PUSCH transmission based on the second SRS resource in the second SRS resource set. The one or more configuration parameters may indicate a second number of SRS ports (e.g., nr0fSRS ports) for the second SRS resource. The wireless device may, for example, send (e.g., transmit) a second repetition of the PUSCH transmission based on the second number of SRS ports of the second SRS resource in the second SRS resource set. For example, the wireless device may send (e.g., transmit) the second repetition with a second transmission precoder determined based on the second number of SRS ports.

[0319] One or more wireless devices may transmit at multiple transmission opportunities (e.g., Figure 19The first transmission opportunity (eg, Figure 19 The first repetition (eg, the first TX opportunity in the TX period) of the PUSCH transmission is sent (eg, transmitted) in the TX period. Figure 19 The wireless device may transmit at multiple transmission opportunities (e.g., Figure 19 The second transmission opportunity (eg, Figure 19 The second repetition (eg, Figure 19 Repetition 2).

[0320] One or more wireless devices may be configured to receive a signal based on a first TCI state (e.g., Figure 17 The first repetition of the PUSCH transmission may be sent (e.g., transmitted) using a first spatial domain transmit filter / beam determined based on a first reference signal indicated by the first TCI state. The one or more wireless devices may send (e.g., transmit) a first repetition of the PUSCH transmission using a first spatial domain transmit filter / beam determined based on a first reference signal indicated by the first TCI state. The first spatial domain transmit / transmit filter / beam may be, for example, the same as (or substantially the same as, separated by x degrees, x = 0, 1, 5, 10, etc.) a spatial domain receive / receive filter / beam used to receive the first reference signal. The first spatial domain transmit / transmit filter / beam may be, for example, the same as (or substantially the same as, separated by x degrees, x = 0, 1, 5, 10, etc.) a spatial domain transmit / transmit filter / beam used to send (e.g., transmit) the first reference signal.

[0321] One or more wireless devices may send (e.g., transmit) a first repetition of a PUSCH transmission using 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, α, path loss reference signal, etc.) indicated by (or included in, associated with, or mapped to) a first TCI state. The one or more configuration parameters may indicate the one or more first power control parameters for the first TCI state.

[0322] One or more wireless devices may be configured to receive a signal based on a second TCI state (e.g., Figure 17The one or more wireless devices may send (e.g., transmit) a second repetition of the PUSCH transmission with a second spatial domain transmission filter / beam determined based on a second reference signal indicated by the second TCI state. The second spatial domain transmission / transmission filter / beam may, for example, be the same as (or substantially the same as, separated by x degrees, x = 0, 1, 5, 10, etc.) a spatial domain reception / reception filter / beam used to receive the second reference signal. The second spatial domain transmission / transmission filter / beam may, for example, be the same as (or substantially the same as, separated by x degrees, x = 0, 1, 5, 10, etc.) a spatial domain transmission / transmission filter / beam used to send (e.g., transmit) the second reference signal.

[0323] The one or more wireless devices may send (e.g., transmit) a second repetition of the PUSCH transmission using 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 factor, α, path loss reference signal, etc.) indicated by (or included in, associated with, or mapped to) a second TCI state. The one or more configuration parameters may indicate the one or more second power control parameters for the second TCI state.

[0324] One or more wireless devices may be equipped with multiple antenna panels. The 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, for example, indicate a first antenna panel index for the first antenna panel. For example, one or more wireless devices may send (e.g., transmit) an uplink signal (e.g., a beam report, a CSI report, a UE capability message, a PUCCH transmission) indicating the first antenna panel index for the first antenna panel. The second antenna panel may be identified / indicated by a second antenna panel index / identifier. One or more configuration parameters may, for example, indicate a second antenna panel index for the second antenna panel. For example, one or more wireless devices may send (e.g., transmit) an uplink signal (e.g., a beam report, a CSI report, a UE capability message, a PUCCH transmission) indicating the second antenna panel index for the second antenna panel.

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

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

[0327] A capability value set (e.g., each capability value set in the capability value set list) may be identified / indicated by a corresponding capability value set index. For example, a first capability value set may be identified / indicated by a first capability value set index. A second capability value set may be identified / indicated by a second capability value set index.

[0328] One or more wireless devices may send (e.g., transmit) at least one report (e.g., a beam report, a CSI report, an L1-RSRP report, an SINR report, and / or any other report). One or more wireless devices may send (e.g., transmit) the report via a PUCCH. The report may indicate 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 (e.g., a CSI-RS and / or SSB resource index) for the first reference signal and a first capability value set index for the first capability value set. The one or more wireless devices may determine an association / mapping / correspondence between the first reference signal and the first capability value set. One or more configuration parameters may indicate a first reference signal index for the first reference signal. The first TCI state may be associated with the first capability value set, for example, based on an association / mapping / correspondence between the first reference signal indicated by the first TCI state and the first capability value set. A first repetition of the PUSCH transmission may be associated with the first capability value set, for example, based on (e.g., in response to) sending (e.g., transmitting) the first repetition based on the first TCI state associated with the first capability value set.

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

[0330] One or more wireless devices may receive an acknowledgment of the report, for example from the base station. The acknowledgment may be, for example, a DCI.

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

[0332] One or more wireless devices may multiplex a CSI report (or other information) in / on / with a first repetition of a PUSCH transmission and a second repetition of a PUSCH transmission. For example, based on multiplexing the CSI report in the first repetition of a PUSCH transmission and the second repetition of a PUSCH transmission, the one or more wireless devices may send (e.g., transmit) a CSI report in the first repetition of a PUSCH transmission and the second repetition of a PUSCH transmission. For example, based on multiplexing the CSI report in the first repetition of a PUSCH transmission and the second repetition of a PUSCH transmission, the one or more wireless devices may send (e.g., transmit) a CSI report in a first transmission opportunity (where the first repetition of a PUSCH transmission is sent (e.g., transmitted)) and in a second transmission opportunity (where the second repetition of a PUSCH transmission is sent (e.g., transmitted)).

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

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

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

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

[0337] The one or more wireless devices may multiplex the CSI report (or other information) in the first repetition of the PUSCH transmission and the second repetition of the PUSCH transmission, for example, based on one or more configuration parameters including a CSI multiplexing mode parameter. The one or more wireless devices may multiplex the CSI report in the first repetition of the PUSCH transmission and the second repetition of the PUSCH transmission, for example, based on one or more configuration parameters including a CSI multiplexing mode parameter set to enabled.

[0338] One or more wireless devices may send (e.g., transmit) a CSI report (or other information) at a first transmission opportunity (or in a first repetition of a PUSCH transmission) and a second transmission opportunity (or in a second repetition of a PUSCH transmission), for example, based on one or more configuration parameters including a CSI multiplexing FDM mode parameter. One or more wireless devices may send (e.g., transmit) a CSI report at a first transmission opportunity (or in a first repetition of a PUSCH transmission) and a second transmission opportunity (or in a second repetition of a PUSCH transmission), for example, based on one or more configuration parameters including a CSI multiplexing FDM mode parameter set to enabled.

[0339] The one or more wireless devices may multiplex the CSI report (or other information) in the first repetition of the PUSCH transmission and the second repetition of the PUSCH transmission, for example, based on one or more configuration parameters including a CSI multiplexing FDM mode parameter. The one or more wireless devices may multiplex the CSI report in the first repetition of the PUSCH transmission and the second repetition of the PUSCH transmission, for example, based on one or more configuration parameters including a CSI multiplexing FDM mode parameter set to enabled.

[0340] One or more wireless devices may send (e.g., transmit) a CSI report (or other information) at a first transmission opportunity (or in a first repetition of a PUSCH transmission) and a second transmission opportunity (or in a second repetition of a PUSCH transmission), for example, based on the PUSCH transmission not including / carrying uplink control information (UCI) other than the CSI report. For example, based on not multiplexing UCI other than the CSI report in the PUSCH transmission, the one or more wireless devices may send (e.g., transmit) a CSI report at a first transmission opportunity (or in a first repetition of a PUSCH transmission) and a second transmission opportunity (or in a second repetition of a PUSCH transmission). The UCI may include, for example, HARQ-ACK. The UCI may include, for example, SR.

[0341] For example, based on the PUSCH transmission not including / carrying uplink control information (UCI) other than the CSI report, one or more wireless devices may multiplex the CSI report (or other information) in the first repetition of the PUSCH transmission and the second repetition of the PUSCH transmission. For example, based on not multiplexing UCI other than the CSI report in the PUSCH transmission, the one or more wireless devices may multiplex the CSI report in the first repetition of the PUSCH transmission and the second repetition of the PUSCH transmission. The UCI may include, for example, HARQ-ACK. The UCI may include, for example, SR.

[0342] For example, based on the UE capability message indicating support for sending (e.g., transmitting) / multiplexing CSI reports in / on at least two repetitions (or at least two transmission opportunities) of PUSCH transmission, one or more wireless devices may send (e.g., transmit) CSI reports (or other information) in a first transmission opportunity (or in a first repetition of PUSCH transmission) and a second transmission opportunity (or in a second repetition of PUSCH transmission).

[0343] For example, based on a capability message (e.g., a UE capability message) indicating support for sending (e.g., transmitting) / multiplexing CSI reports in / on at least two repetitions (or at least two transmission opportunities) of a PUSCH transmission, one or more wireless devices may multiplex the CSI report (or other information) in a first repetition of the PUSCH transmission and a second repetition of the PUSCH transmission.

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

[0345] One or more wireless devices may transmit a PUSCH in the first repetition (e.g., Figure 19 repetition 1 in the PUSCH transmission) and the second repetition of the PUSCH transmission (e.g., Figure 19 One or more wireless devices may send (e.g., transmit) a CSI report (or other information) in a repetition of a PUSCH transmission in a repetition 2). Figure 19 ) and a second transmission opportunity (e.g., Figure 19The wireless device may send (e.g., transmit) a CSI report in a transmission opportunity among the first repetition of the PUSCH transmission and the second repetition of the PUSCH transmission. The wireless device may send (e.g., transmit) a repetition of the PUSCH transmission in the transmission opportunity. The one or more wireless devices may not send (e.g., transmit) a CSI report in any repetition of the PUSCH transmission that is different from the repetition of the PUSCH transmission among the first repetition of the PUSCH transmission and the second repetition of the PUSCH transmission. The one or more wireless devices may not send (e.g., transmit) a CSI report in any transmission opportunity that is different from the transmission opportunity among the first transmission opportunity and the second transmission opportunity.

[0346] One or more wireless devices may determine / select a repetition of PUSCH transmission for transmission of a CSI report (or other information) between a first repetition of PUSCH transmission and a second repetition of PUSCH transmission. One or more wireless devices may determine / select a transmission timing for transmission of a CSI report between a first transmission timing and a second transmission timing.

[0347] The repetition of the PUSCH transmission may be, for example, a default repetition of the PUSCH transmission. The repetition of the PUSCH transmission may be, for example, a reference repetition of the PUSCH transmission.

[0348] For example, in Figure 19 In the embodiment, the repetition of the PUSCH transmission may be the first repetition of the PUSCH transmission (eg, Figure 19 One or more wireless devices may send (e.g., transmit) a CSI report in the first repetition of a PUSCH transmission. One or more wireless devices may send (e.g., transmit) a CSI report in the first repetition of a PUSCH transmission. Figure 19 One or more wireless devices may not send (e.g., transmit) a CSI report in the second repetition of the PUSCH transmission (e.g., the first TX opportunity in the PUSCH). Figure 19 One or more wireless devices may not send (e.g., transmit) a CSI report in the second transmission opportunity (e.g., Figure 19 Send (e.g., transmit) the CSI report in the second TX opportunity in .

[0349] For example, in Figure 19 In the embodiment, the repetition of the PUSCH transmission may be a second repetition of the PUSCH transmission (eg, Figure 19 The one or more wireless devices may send (e.g., transmit) a CSI report in the second repetition of the PUSCH transmission. The one or more wireless devices may send (e.g., transmit) a CSI report in the second repetition of the PUSCH transmission. Figure 19 One or more wireless devices may not send (e.g., transmit) a CSI report in the first repetition of a PUSCH transmission (e.g., the second TX opportunity in the PUSCH). Figure 19One or more wireless devices may not send (eg, transmit) a CSI report in the first transmission opportunity (eg, Figure 19 The CSI report may be sent (e.g., transmitted) in the first TX opportunity in the TX period.

[0350] One or more wireless devices may multiplex a CSI report (or other information) in / on / with a repetition of a PUSCH transmission. One or more wireless devices may send (e.g., transmit) a CSI report in a repetition of a PUSCH transmission, for example, based on multiplexing the CSI report in the repetition of the PUSCH transmission. One or more wireless devices may send (e.g., transmit) a CSI report in a transmission opportunity (e.g., send (e.g., transmit) a repetition of a PUSCH transmission), for example, based on multiplexing the CSI report in the repetition of the PUSCH transmission.

[0351] One or more wireless devices may send (e.g., transmit) a CSI report (or other information) in a transmission opportunity (or in a repetition of a PUSCH transmission), for example, based on one or more configuration parameters indicating at least two SRS resource sets. One or more wireless devices may multiplex the CSI report (or other information) in a repetition of a PUSCH transmission, for example, based on one or more configuration parameters indicating at least two SRS resource sets.

[0352] For example, based on one or more configuration parameters that do not indicate at least two SRS resource sets with a codebook (or with a usage parameter set to a codebook), one or more wireless devices may send (e.g., transmit) a CSI report (or other information) in a transmission opportunity (or in a repetition of a PUSCH transmission). For example, based on one or more configuration parameters that do not indicate at least two SRS resource sets with a non-codebook (or with a usage parameter set to a non-codebook), one or more wireless devices may send (e.g., transmit) a CSI report in a transmission opportunity (or in a repetition of a PUSCH transmission). For example, based on one or more configuration parameters that indicate an SRS resource set (or a single SRS resource set) with a codebook (or with a usage parameter set to a codebook), one or more wireless devices may send (e.g., transmit) a CSI report in a transmission opportunity (or in a repetition of a PUSCH transmission). For example, based on one or more configuration parameters that indicate an SRS resource set (or a single SRS resource set) with a non-codebook (or with a usage parameter set to a non-codebook), one or more wireless devices may send (e.g., transmit) a CSI report in a transmission opportunity (or in a repetition of a PUSCH transmission).

[0353] One or more wireless devices may, for example, multiplex CSI reports (or other information) across repetitions of a PUSCH transmission based on one or more configuration parameters that do not indicate at least two SRS resource sets with a codebook (or with a usage parameter set to a codebook). One or more wireless devices may, for example, multiplex CSI reports across repetitions of a PUSCH transmission based on one or more configuration parameters that do not indicate at least two SRS resource sets with a non-codebook (or with a usage parameter set to a non-codebook). One or more wireless devices may, for example, multiplex CSI reports across repetitions of a PUSCH transmission based on one or more configuration parameters that indicate an SRS resource set (or a single SRS resource set) with a codebook (or with a usage parameter set to a codebook). One or more wireless devices may, for example, multiplex CSI reports across repetitions of a PUSCH transmission based on one or more configuration parameters that indicate an SR...

Claims

1. A method comprising: One or more configuration parameters are received by a wireless device, the one or more configuration parameters indicating: Physical Uplink Control Channel (PUCCH) transmission of Uplink Control Information (UCI); and A frequency domain repetition scheme for Physical Uplink Shared Channel (PUSCH) transmissions; receiving downlink control information (DCI) scheduling frequency domain repetition of PUSCH transmission, wherein the frequency domain repetition includes a first repetition and a second repetition; and The UCI is transmitted in the first repetition based on that the frequency domain repetition of the PUSCH transmission overlaps in time with the PUCCH transmission of the UCI, and based on that the first repetition is associated with a value that satisfies a criterion.

2. The method of claim 1 , wherein the transmitting the UCI in the first repetition is further based on at least one of: The one or more configuration parameters indicate a UCI multiplexing mode parameter that is not enabled; or The one or more configuration parameters do not include a UCI multiplexing mode parameter. 3 . The method according to claim 1 , further comprising transmitting the second repetition in the same time period as the first repetition, wherein the UCI is multiplexed in the first repetition, and wherein the UCI is not multiplexed in the second repetition.

4. The method according to any one of claims 1 to 3 further includes transmitting each of the frequency domain repetitions of the PUSCH transmission in multiple transmission opportunities within different frequency ranges, wherein each of the frequency domain repetitions of the PUSCH transmission is transmitted by the wireless device in a corresponding transmission opportunity among the multiple transmission opportunities.

5. The method according to any one of claims 1 to 4, further comprising: Receive the second DCI scheduling the following: Transmission of the second UCI; as well as Frequency domain repetition of the second PUSCH transmission; as well as Based on an enabled UCI multiplexing mode parameter, the second UCI is transmitted in each frequency-domain repetition of the frequency-domain repetitions of the second PUSCH transmission.

6. A method comprising: One or more configuration parameters are transmitted by a base station, the one or more configuration parameters indicating: Physical Uplink Control Channel (PUCCH) transmission of Uplink Control Information (UCI); and A frequency domain repetition scheme for Physical Uplink Shared Channel (PUSCH) transmissions; transmitting downlink control information (DCI) of frequency domain repetitions for scheduling PUSCH transmission, wherein the frequency domain repetitions include a first repetition and a second repetition; and The UCI is received in the first repetition based on the frequency-domain repetition of the PUSCH transmission overlapping 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. The method of claim 6, wherein the receiving the UCI in the first repetition is further based on at least one of: The one or more configuration parameters indicate a UCI multiplexing mode parameter that is not enabled; or The one or more configuration parameters do not include a UCI multiplexing mode parameter. 8 . The method according to claim 6 , further comprising receiving the second repetition in a same time period as the first repetition, wherein the UCI is multiplexed in the first repetition, and wherein the UCI is not multiplexed in the second repetition.

9. The method according to any one of claims 6 to 8 further includes receiving each of the frequency domain repetitions of the PUSCH transmission in multiple transmission opportunities within different frequency ranges, wherein each of the frequency domain repetitions of the PUSCH transmission is received by the base station in a corresponding transmission opportunity among the multiple transmission opportunities.

10. The method according to any one of claims 6 to 9, further comprising: The transmission schedule is the following second DCI: Transmission of the second UCI; as well as Frequency domain repetition of the second PUSCH transmission; as well as Based on an enabled UCI multiplexing mode parameter, the second UCI is received in each frequency-domain repetition of the frequency-domain repetitions of the second PUSCH transmission.

11. The method according to any one of claims 1 to 10, wherein: Each of the frequency domain repetitions is associated with a corresponding value of a plurality of values; The criterion includes determining a lowest value or a highest value among the plurality of values, wherein the plurality of values ​​includes the value that satisfies the criterion; and The value associated with the first repetition indicates at least one of: frequency; Resource block value; Transmission Configuration Indicator (TCI) status; TCI status index; Sounding Reference Signal (SRS) resource set; Control resource set (CORESET) pool index; Transmission and reception point (TRP) index; Antenna panels; or Antenna Panel Index.

12. The method according to any one of claims 1 to 11, wherein the UCI comprises at least one of: Hybrid Automatic Repeat Request Acknowledgement (HARQ-ACK); Channel State Information (CSI) reporting; and Scheduling Request (SR).

13. A computing device comprising: one or more processors; as well as A memory storing instructions which, when executed by the one or more processors, cause the computing device to perform a method according to any one of claims 1 to 12.

14. A system comprising: A wireless device configured to perform a method according to any one of claims 1 to 5 when dependent on claim 1, or a method according to any one of claims 11 to 12; and A base station configured to perform a method according to any one of claims 6 to 10 when dependent on claim 6, or a method according to any one of claims 11 to 12.

15. A computer readable medium storing instructions which, when executed, cause the method according to any one of claims 1 to 12 to be performed.

16. A method comprising: receiving, by a wireless device, one or more configuration parameters, the one or more configuration parameters comprising an uplink control information (UCI) multiplexing pattern parameter; as well as A frequency domain repetition scheme for Physical Uplink Shared Channel (PUSCH) transmissions; receiving downlink control information (DCI) scheduling frequency domain repetition of PUSCH transmission, wherein the frequency domain repetition includes a first repetition and a second repetition; and Based on the one or more configuration parameters indicating that UCI multiplexing is not enabled, transmitting the UCI in one of the first repetition or the second repetition, wherein selecting the first repetition or the second repetition for transmitting the UCI is based on an index associated with one of the first repetition or the second repetition that meets a criterion. 17 . The method of claim 16 , wherein the transmitting the UCI comprises transmitting the UCI in the first repetition based on the first repetition comprising a lowest index of a plurality of indices, the plurality of indices comprising a first index associated with the first repetition and a second index associated with the second repetition.

18. The method of claim 17, wherein: Each of the frequency-domain repetitions is associated with a corresponding index of a plurality of indices, wherein the plurality of indices includes the index that satisfies the criterion; Based on the index associated with the first repetition being a lowest index or a highest index among the plurality of indices, the transmitting the UCI is in the first repetition; The criteria include determining the lowest index or the highest index among the plurality of indexes; and The index that meets the criteria includes at least one of the following: TCI Status Index; or Antenna Panel Index.

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

20. The method of any one of claims 17 to 19, wherein the UCI comprises at least one of: Hybrid Automatic Repeat Request Acknowledgement (HARQ-ACK); Channel State Information (CSI) reporting; and Scheduling Request (SR).

21. The method according to any one of claims 17 to 20 further comprises transmitting each of the frequency domain repetitions of the PUSCH transmission in a plurality of transmission opportunities within different frequency ranges and overlapping in time, wherein each of the frequency domain repetitions of the PUSCH transmission is transmitted by the wireless device in a corresponding transmission opportunity among the plurality of transmission opportunities.

22. The method according to any one of claims 17 to 21, further comprising: Receiving an indication that the UCI multiplexing mode parameter is changed from not enabled to enabled; After receiving the indication of the change of the UCI multiplexing pattern parameter, receiving a second DCI scheduling: Transmission of the second UCI; as well as Frequency domain repetition of the second PUSCH transmission; as well as Based on enabling the UCI multiplexing mode parameter, the second UCI is transmitted in each frequency-domain repetition of the frequency-domain repetition of the second PUSCH transmission.

23. A computing device comprising: one or more processors; as well as A memory storing instructions which, when executed by the one or more processors, cause the computing device to perform a method according to any one of claims 17 to 22.

24. A system comprising: A wireless device configured to perform the method according to any one of claims 17 to 22; as well as A base station is configured to transmit the one or more configuration parameters.

25. A computer readable medium storing instructions which, when executed, cause performance of the method of any one of claims 17 to 22.

26. A method comprising: One or more configuration parameters are transmitted by a base station, the one or more configuration parameters indicating: Uplink control information (UCI) multiplexing mode parameters; Physical Uplink Control Channel (PUCCH) transmission of Uplink Control Information (UCI); and A frequency domain repetition scheme for Physical Uplink Shared Channel (PUSCH) transmissions; transmitting downlink control information (DCI) of frequency domain repetitions for scheduling PUSCH transmission, wherein the frequency domain repetitions include a first repetition and a second repetition; and Based on the one or more configuration parameters indicating that UCI multiplexing is not enabled, receiving the UCI in one of the first repetition or the second repetition, wherein receiving the UCI in the first repetition or the second repetition is based on an index associated with one of the first repetition or the second repetition satisfying a criterion.

27. The method of claim 26, wherein: Each of the frequency-domain repetitions is associated with a corresponding index of a plurality of indices, wherein the plurality of indices includes the index that satisfies the criterion; The receiving the UCI is in the first repetition based on the index associated with the first repetition being a lowest index or a highest index among the plurality of indices; The criteria include determining the lowest index or the highest index among the plurality of indexes; and The index that meets the criteria includes at least one of the following: TCI Status Index; or Antenna Panel Index.

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

29. The method of any one of claims 26 to 28, wherein the UCI comprises at least one of: Hybrid Automatic Repeat Request Acknowledgement (HARQ-ACK); Channel State Information (CSI) reporting; and Scheduling Request (SR).

30. The method according to any one of claims 26 to 29 further comprises receiving each of the frequency domain repetitions of the PUSCH transmission in a plurality of reception opportunities within different frequency ranges and overlapping in time, wherein each of the frequency domain repetitions of the PUSCH transmission is received by the base station in a corresponding reception opportunity among the plurality of reception opportunities.

31. The method according to any one of claims 26 to 30, further comprising: Transmitting an indication that the UCI multiplexing mode parameter is changed from not enabled to enabled; After transmitting the indication of the change of the UCI multiplexing mode parameter, transmitting a second DCI scheduling: Transmission of the second UCI; as well as Frequency domain repetition of the second PUSCH transmission; as well as Based on enabling the UCI multiplexing mode parameter, the second UCI is received in each frequency-domain repetition of the frequency-domain repetitions of the second PUSCH transmission.

32. A computing device comprising: one or more processors; as well as A memory storing instructions which, when executed by the one or more processors, cause the computing device to perform a method according to any one of claims 26 to 31.

33. A system comprising: A wireless device configured to perform the method according to any one of claims 26 to 31; as well as A base station is configured to transmit the one or more configuration parameters.

34. A computer readable medium storing instructions which, when executed, cause performance of the method of any one of claims 26 to 31.

35. A method comprising: receiving, by a wireless device, one or more configuration parameters associated with frequency domain repetition of a physical uplink shared channel (PUSCH) transmission; receiving downlink control information (DCI), wherein the DCI: including a channel state information (CSI) request field indicating transmission of a CSI report; and scheduling frequency domain repetitions of PUSCH transmissions, wherein the frequency domain repetitions include a first repetition within a first frequency range overlapping in time with a second repetition within a second frequency range; and Based on the first repetition being associated with a value that satisfies a criterion, the CSI report is transmitted in the first repetition.

36. The method of claim 35, wherein the transmitting the CSI report in the first repetition is further based on at least one of: The one or more configuration parameters include a non-enabled CSI multiplexing mode parameter; or The one or more configuration parameters do not include a CSI multiplexing mode parameter.

37. A method according to any one of claims 35 to 36, wherein: Each of the frequency-domain repetitions is associated with a respective value of a plurality of values, wherein the plurality of values ​​includes the value satisfying the criterion; The criteria include determining a lowest value or a highest value among the plurality of values; and The value associated with the first repetition indicates at least one of: frequency; Resource block value; Transmission Configuration Indicator (TCI) status; TCI status index; Sounding Reference Signal (SRS) resource set; Control resource set (CORESET) pool index; Transmission and reception point (TRP) index; Antenna panels; or Antenna Panel Index.

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

39. The method according to any one of claims 35 to 38, wherein the CSI report comprises at least one of: Non-periodic CSI reporting; or Semi-persistent CSI reporting.

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

41. The method according to any one of claims 35 to 40 further comprises transmitting each of the frequency domain repetitions of the PUSCH transmission in a plurality of transmission opportunities within different frequency ranges and overlapping in time, wherein each of the frequency domain repetitions of the PUSCH transmission is transmitted by the wireless device in a corresponding transmission opportunity among the plurality of transmission opportunities.

42. The method according to any one of claims 35 to 41, further comprising: Receiving a second DCI, where the second DCI is configured to schedule: Transmission of a second CSI report; as well as Frequency domain repetition of the second PUSCH transmission; as well as Based on an enabled CSI multiplexing mode parameter, the second CSI report is transmitted in each frequency-domain repetition of the frequency-domain repetitions of the second PUSCH transmission.

43. A computing device comprising: one or more processors; as well as A memory storing instructions which, when executed by the one or more processors, cause the computing device to perform a method according to any one of claims 35 to 42.

44. A system comprising: A wireless device configured to perform the method according to any one of claims 35 to 42; as well as A base station is configured to transmit the one or more configuration parameters.

45. A computer readable medium storing instructions which, when executed, cause performance of the method of any one of claims 35 to 42.

46. ​​A method comprising: receiving, by a wireless device, one or more configuration parameters associated with frequency domain repetition of a physical uplink shared channel (PUSCH) transmission, wherein the one or more configuration parameters include a channel state information (CSI) multiplexing mode parameter; receiving downlink control information (DCI) scheduling frequency domain repetitions of a PUSCH transmission, wherein the frequency domain repetitions include a first repetition within a first frequency range overlapping in time with a second repetition within a second frequency range; as well as Based on the one or more configuration parameters indicating that CSI multiplexing is not enabled, a CSI report is transmitted in one of the first repetition or the second repetition, wherein selecting the first repetition or the second repetition for transmitting the CSI report is based on an index associated with one of the first repetition or the second repetition that meets a criterion.

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

48. A method according to any one of claims 46 to 47, wherein: Each of the frequency-domain repetitions is associated with a corresponding index of a plurality of indices, wherein the plurality of indices includes the index that satisfies the criterion; Based on the index associated with the first repetition being a lowest index or a highest index among the plurality of indices, the transmitting the CSI report is in the first repetition; The criteria include determining the lowest index or the highest index among the plurality of indexes; and The index that meets the criteria includes at least one of the following: TCI Status Index; or Antenna Panel Index.

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

50. The method of any one of claims 46 to 49, wherein the CSI report comprises at least one of: Non-periodic CSI reporting; or Semi-persistent CSI reporting.

51. The method according to any one of claims 46 to 50 further comprises transmitting each of the frequency domain repetitions of the PUSCH transmission in a plurality of transmission opportunities within different frequency ranges and overlapping in time, wherein each of the frequency domain repetitions of the PUSCH transmission is transmitted by the wireless device in a corresponding transmission opportunity among the plurality of transmission opportunities.

52. The method according to any one of claims 46 to 51, further comprising: Receiving an indication that the CSI multiplexing mode parameter is changed from not enabled to enabled; After receiving the indication of the change of the CSI multiplexing pattern parameter, receiving a second DCI scheduling: Transmission of a second CSI report; as well as Frequency domain repetition of the second PUSCH transmission; as well as Based on enabling the CSI multiplexing mode parameter, the second CSI report is transmitted in each frequency-domain repetition of the frequency-domain repetitions of the second PUSCH transmission.

53. A computing device comprising: one or more processors; as well as A memory storing instructions which, when executed by the one or more processors, cause the computing device to perform a method according to any one of claims 46 to 52.

54. A system comprising: A wireless device configured to perform the method according to any one of claims 46 to 52; as well as A base station is configured to transmit the one or more configuration parameters.

55. A computer readable medium storing instructions which, when executed, cause performance of the method of any one of claims 46 to 52.

56. A method comprising: transmitting, by a base station, one or more configuration parameters associated with frequency domain repetition of a physical uplink shared channel (PUSCH) transmission, wherein the one or more configuration parameters include a channel state information (CSI) multiplexing mode parameter; transmitting frequency domain repetitions of downlink control information (DCI) scheduling PUSCH transmissions, wherein the frequency domain repetitions include a first repetition within a first frequency range that temporally overlaps with a second repetition within a second frequency range; as well as Based on the one or more configuration parameters indicating that CSI multiplexing is not enabled, a CSI report is received in one of the first repetition or the second repetition, wherein receiving the CSI report in the first repetition or the second repetition is based on an index associated with one of the first repetition or the second repetition that meets a criterion.

57. The method of claim 56, wherein: Each repetition in the frequency domain repetition is associated with a corresponding index in a plurality of indices; The receiving the CSI report is in the first repetition based on the index associated with the first repetition being a lowest index or a highest index among the plurality of indices; The criteria include determining the lowest index or the highest index among the plurality of indexes; and The index associated with the first repetition includes at least one of: TCI Status Index; or Antenna Panel Index.

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

59. The method according to any one of claims 56 to 58 further comprises receiving each of the frequency domain repetitions of the PUSCH transmission in a plurality of reception opportunities within different frequency ranges and overlapping in time, wherein each of the frequency domain repetitions of the PUSCH transmission is received by the base station in a corresponding reception opportunity among the plurality of reception opportunities.

60. The method according to any one of claims 56 to 59, further comprising: Transmitting an indication that the CSI multiplexing mode parameter is changed from not enabled to enabled; Subsequent to transmitting the indication of the change of the CSI multiplexing pattern parameter, transmitting a second DCI configured to schedule: Transmission of a second CSI report; as well as Frequency domain repetition of the second PUSCH transmission; as well as Based on enabling the CSI multiplexing mode parameter, the second CSI report is received in each of the frequency-domain repetitions of the second PUSCH transmission.

61. A computing device comprising: one or more processors; as well as A memory storing instructions which, when executed by the one or more processors, cause the computing device to perform a method according to any one of claims 56 to 60.

62. A system comprising: A wireless device configured to perform the method according to any one of claims 56 to 60; as well as A base station is configured to transmit the one or more configuration parameters.

63. A computer readable medium storing instructions which, when executed, cause performance of the method of any one of claims 56 to 60.

64. A method comprising: Repetitive downlink control information (DCI) scheduling a first physical uplink shared channel (PUSCH) transmission is received by a wireless device, wherein: The repetition of the first PUSCH transmission is in the frequency domain; and Each of the repetitions is associated with a corresponding transmission configuration indicator (TCI) state of a plurality of TCI states; determining the power headroom report using a path loss reference signal associated with a TCI state of the plurality of TCI states indicated by a lowest TCI state index among TCI state indexes of corresponding TCI states associated with the repetition of the first PUSCH transmission based on the repetition of the first PUSCH transmission overlapping in time with a second PUSCH transmission including a power headroom report; and The power headroom report is transmitted.

65. A method according to claim 64, wherein each of the repetitions of the first PUSCH transmission is associated with a corresponding path loss reference signal in a plurality of path loss reference signals, and wherein each of the plurality of path loss reference signals is associated with a corresponding TCI state in the plurality of TCI states.

66. The method of any one of claims 64 to 65, further comprising transmitting: transmitting a first repetition of the repetitions of the first PUSCH transmission based on a first TCI state; and A second repetition of the repetitions of the first PUSCH transmission is transmitted based on a second TCI state.

67. The method of any one of claims 64 to 66, wherein the using the path loss reference signal to determine the power headroom report is based on at least one of: receiving a power headroom mode parameter indicating enabling of a single power headroom mode; or It is determined that two power headroom reporting mode parameters have not been received.

68. The method according to any one of claims 64 to 67, further comprising: receiving an indication to activate at least two TCI states including the TCI state; and Transmitting a first repetition of the repetitions of the first PUSCH transmission by: using a spatial domain transfer filter determined based on a first TCI state of the at least two TCI states; as well as Using a transmission 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 comprises determining the path loss reference signal associated with the 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 being associated with the same value of a TCI state index.

70. The method of any one of claims 64 to 69, wherein the power headroom report comprises 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 comprising: one or more processors; as well as A memory storing instructions which, when executed by the one or more processors, cause the computing device to perform a method according to any one of claims 64 to 70.

72. A system comprising: A wireless device configured to perform the method according to any one of claims 64 to 70; as well as A base station is configured to transmit the DCI.

73. A computer readable medium storing instructions which, when executed, cause performance of the method of any one of claims 64 to 70.

74. A method comprising: receiving, by a wireless device, downlink control information (DCI) scheduling frequency domain repetitions of a first physical uplink shared channel (PUSCH) overlapping in time with a second PUSCH transmission including a power headroom report, wherein each of the repetitions is associated with a corresponding path loss reference signal of a plurality of path loss reference signals and a corresponding index of a plurality of indices; determining the power headroom report using a path loss reference signal corresponding to a repetition associated with a lowest index among the respective indices of the repetitions among the repetitions of the first PUSCH transmission; and The power headroom report is transmitted.

75. The method of claim 74, wherein the lowest index indicates at least one of: Transmission Configuration Indicator (TCI) index; Antenna Panel Index; or Resource block location.

76. A method according to any one of claims 74 to 75, wherein each of the multiple path loss reference signals is associated with a corresponding transmission configuration indicator (TCI) state in a plurality of TCI states, and wherein each of the multiple TCI states is associated with a corresponding TCI state index in a plurality of TCI state indexes.

77. The method of any one of claims 74 to 76, further comprising transmitting: transmitting a first repetition of the repetitions of the first PUSCH transmission based on a first transmission configuration indicator (TCI) state; and A second repetition of the repetitions of the first PUSCH transmission is transmitted based on a second TCI state.

78. The method according to any one of claims 74 to 77, wherein the transmitting the power headroom report is based on receiving a power headroom mode parameter indicating enabling of a single power headroom mode.

79. The method of any one of claims 74 to 78, further comprising: receiving an indication to activate at least two transmission configuration indicator (TCI) states; as well as Transmitting a first repetition of the repetitions of the first PUSCH transmission by: using a spatial domain transfer filter determined based on a first TCI state of the at least two TCI states; and Using a transmission 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 comprises determining the path loss reference signal corresponding to the repetition associated with the lowest index, wherein the determination of 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 transmission configuration indicator (TCI) state.

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

82. A computing device comprising: one or more processors; as well as A memory storing instructions which, when executed by the one or more processors, cause the computing device to perform a method according to any one of claims 74 to 81.

83. A system comprising: A wireless device configured to perform the method according to any one of claims 74 to 81; as well as A base station is configured to transmit the DCI.

84. A computer readable medium storing instructions which, when executed, cause performance of the method of any one of claims 74 to 81.

85. A method comprising: receiving, by a wireless device, downlink control information (DCI) scheduling frequency domain repetitions of a first physical uplink shared channel (PUSCH) overlapping in time with a second PUSCH transmission including a power headroom report, wherein each of the repetitions is associated with a corresponding path loss reference signal of a plurality of path loss reference signals and a corresponding index of a plurality of indices; and A power headroom value is transmitted in the power headroom report, wherein the power headroom value is determined using a path loss reference signal corresponding to a repetition associated with a lowest index among the respective indices of the repetitions among the repetitions of the first PUSCH transmission.

86. The method of claim 85, wherein the lowest index indicates at least one of: Minimum transmission configuration indicator (TCI) index; Minimum Sounding Reference Signal (SRS) resource set; Minimum Control Resource Set (CORESET) pool index; Minimum transmission and reception point (TRP) index; Lowest Antenna Panel Index; or Lowest resource block position.

87. The method of any one of claims 85 to 86, wherein the using the path loss reference signal to determine the power headroom report is based on at least one of: receiving a power headroom mode parameter indicating enabling of a single power headroom mode; or It is determined that two power headroom reporting mode parameters have not been received.

88. The method according to any one of claims 85 to 87 further comprises determining the path loss reference signal corresponding to the repetition associated with the lowest index, wherein the determination of 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 transmission configuration indicator (TCI) state.

89. The method according to any one of claims 85 to 88, wherein the transmitting the power headroom report is based on receiving a power headroom mode parameter indicating enabling of a single power headroom mode.

90. A computing device comprising: one or more processors; as well as A memory storing instructions which, when executed by the one or more processors, cause the computing device to perform a method according to any one of claims 85 to 89.

91. A system comprising: A wireless device configured to perform the method according to any one of claims 85 to 89; as well as A base station is configured to transmit the DCI.

92. A computer readable medium storing instructions which, when executed, cause performance of the method of any one of claims 85 to 89.

93. A method comprising: receiving, by a wireless device, first downlink control information (DCI) scheduling a first uplink transmission in a first transmission opportunity; receiving a second DCI scheduling a second uplink transmission in a second transmission opportunity overlapping in time with the first transmission opportunity; determining that a total transmission power of transmissions by the wireless device including the first uplink transmission and the second uplink transmission exceeds a maximum transmission power; as well as Prioritizing one of the first uplink transmission and the second uplink transmission based on: the determining that the total transmission power of transmissions by the wireless device exceeds the maximum transmission power; as well as Based on a comparison of a first value associated with the first uplink transmission and a second value associated with the second uplink transmission.

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

95. The method of any one of claims 93 to 94, wherein the prioritizing the one of the first uplink transmission and the second uplink transmission comprises at least one of: reducing a transmission power associated with at least one of the first uplink transmission or the second uplink transmission; or A transmission of at least one of the first uplink transmission or the second uplink transmission is dropped.

96. The method of any one of claims 93 to 95, wherein the prioritizing the one of the first uplink transmission and the second uplink transmission comprises at least one of: reducing a transmission power associated with at least one layer of the first uplink transmission; or Transmission of at least one layer of the first uplink transmission is discarded.

97. The method of any one of claims 93 to 96, wherein the comparison of the first value associated with the first uplink transmission and the second value associated with the second uplink transmission comprises determining the lowest or highest of: frequency; Resource block value; Transmission Configuration Indicator (TCI) status; TCI status index; Sounding Reference Signal (SRS) resource set; Control resource set (CORESET) pool index; Transmission and reception point (TRP) index; Antenna panels; or Antenna Panel Index.

98. The method of any one of claims 93 to 97, further comprising: Based on the comparison indicating that the first value is less than the second value, transmitting the first uplink transmission.

99. The method of any one of claims 93 to 98, further comprising performing at least one of the following: based on the comparison indicating that the first value is less than the second value, discarding the second uplink transmission; or Based on the comparison indicating that the first value is less than the second value, transmitting the second uplink transmission using an adjusted transmission power.

100. A computing device comprising: one or more processors; as well as A memory storing instructions which, when executed by the one or more processors, cause the computing device to perform a method according to any one of claims 93 to 99.

101. A system comprising: A wireless device configured to perform the method according to any one of claims 93 to 99; as well as A base station is configured to transmit the first DCI.

102. A computer readable medium storing instructions which, when executed, cause performance of the method of any one of claims 93 to 99.

103. A method comprising: receiving, by a wireless device, first downlink control information (DCI) scheduling a first uplink transmission in a first transmission opportunity; receiving a second DCI scheduling a second uplink transmission in a second transmission opportunity overlapping in time with the first transmission opportunity; determining that a total transmission power of transmissions by the wireless device including the first uplink transmission and the second uplink transmission exceeds a maximum transmission power; transmitting the first uplink transmission; as well as Transmitting the second uplink transmission using the adjusted transmit power based on: the determining that the total transmission power of transmissions by the wireless device exceeds the maximum transmission power; as well as A determination is made that a first value associated with the first uplink transmission is less than a second value associated with the second uplink transmission.

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

105. A method according to any one of claims 103 to 104, wherein the first value comprises a first transmission configuration indicator (TCI) state index associated with the first uplink transmission, and the second value comprises a second TCI state index associated with the second uplink transmission.

106. The method of any one of claims 103 to 105, wherein the transmitting the second uplink transmission using the adjusted transmit power comprises at least one of: reducing a transmission power associated with at least one layer of the second uplink transmission; or Transmission of at least one layer of the second uplink transmission is discarded.

107. The method of any one of claims 103 to 106, wherein the first value and the second value comprise different ones of: frequency; Resource block value; Transmission Configuration Indicator (TCI) status; TCI status index; Antenna panels; or Antenna Panel Index.

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

109. A computing device comprising: one or more processors; as well as A memory storing instructions which, when executed by the one or more processors, cause the computing device to perform a method according to any one of claims 103 to 108.

110. A system comprising: A wireless device configured to perform the method according to any one of claims 103 to 108; as well as A base station is configured to transmit the first DCI.

111. A computer readable medium storing instructions which, when executed, cause the method of any one of claims 103 to 108 to be performed.

112. A method comprising: receiving, by a wireless device, first downlink control information (DCI) scheduling a first uplink transmission in a first transmission opportunity; receiving a second DCI scheduling a second uplink transmission in a second transmission opportunity overlapping in time with the first transmission opportunity; determining that a total transmission power of transmissions by the wireless device including the first uplink transmission and the second uplink transmission exceeds a maximum transmission power; as well as Based on a determination that a first value associated with the first uplink transmission is less than a second value associated with the second uplink transmission: transmitting the first uplink transmission; and The second uplink transmission is transmitted using the adjusted transmission power or is dropped.

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

114. A method according to any one of claims 112 to 113, wherein the first value comprises a first transmission configuration indicator (TCI) state index associated with the first uplink transmission, and the second value comprises a second TCI state index associated with the second uplink transmission.

115. The method of any one of claims 112 to 114, wherein the transmitting the second uplink transmission using the adjusted transmit power comprises at least one of: reducing a transmission power associated with at least one layer of the second uplink transmission; or Transmission of at least one layer of the second uplink transmission is discarded.

116. The method of any one of claims 112 to 115, wherein the first value and the second value comprise different ones of: frequency; Resource block value; Transmission Configuration Indicator (TCI) status; TCI status index; Sounding Reference Signal (SRS) resource set; Control resource set (CORESET) pool index; Transmission and reception point (TRP) index; Antenna panels; or Antenna Panel Index.

117. The method according to any one of claims 112 to 116, further comprising: The first uplink transmission is transmitted using a first uplink transmission power that is greater than a 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: Based on the determination that the first value associated with the first uplink transmission is less than the second value associated with the second uplink transmission, the second uplink transmission is discarded.

119. A computing device comprising: one or more processors; as well as A memory storing instructions which, when executed by the one or more processors, cause the computing device to perform a method according to any one of claims 112 to 118.

120. A system comprising: A wireless device configured to perform the method according to any one of claims 112 to 118; as well as A base station is configured to transmit the first DCI.

121. A computer readable medium storing instructions which, when executed, cause performance of the method of any one of claims 112 to 118.

Images