104 may be implemented as an access point, as a baseband processing unit coupled to several remote radio heads (RRHs), and/or as a repeater or relay node used to extend the coverage area of a donor node. A baseband processing unit coupled to RRHs may be part of a centralized or cloud RAN architecture, where the baseband processing unit may be either centralized in a pool of baseband processing units or virtualized. A repeater node may amplify and rebroadcast a radio signal received from a donor node. A relay node may perform the same/similar functions as a repeater node but may decode the radio signal received from the donor node to remove noise before amplifying and rebroadcasting the radio signal.

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

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

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

The 5G-CN 152 provides the UEs 156 with an interface to one or more DNs, such as public DNs (e.g., the Internet), private DNs, and/or intra-operator DNs. As part of the interface functionality, the 5G-CN 152 may set up end-to-end connections between the UEs 156 and the one or more DNs, authenticate the UEs 156, and provide charging functionality. Compared to the CN of a 3GPP 4G network, the basis of the 5G-CN 152 may be a service-based architecture. This means that the architecture of the nodes making up the 5G-CN 152 may be defined as network functions that offer services via interfaces to other network functions. The network functions of the 5G-CN 152 may be implemented in several ways, including as network elements on dedicated or shared hardware, as software instances running on dedicated or shared hardware, or as virtualized functions instantiated on a platform (e.g., a cloud-based platform).

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

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

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

The NG-RAN 154 may connect the 5G-CN 152 to the UEs 156 through radio communications over the air interface. The NG-RAN 154 may include one or more gNBs, illustrated as gNB 160A and gNB 160B (collectively gNBs 160) and/or one or more ng-eNBs, illustrated as ng-eNB 162A and ng-eNB 162B (collectively ng-eNBs 162). The gNBs 160 and ng-eNBs 162 may be more generically referred to as base stations. The gNBs 160 and ng-eNBs 162 may include one or more sets of antennas for communicating with the UEs 156 over an air interface. For example, one or more of the gNBs 160 and/or one or more of the ng-eNBs 162 may include three sets of antennas to respectively control three cells (or sectors). Together, the cells of the gNBs 160 and the ng-eNBs 162 may provide radio coverage to the UEs 156 over a wide geographic area to support UE mobility.

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

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

The gNBs 160 may provide NR user plane and control plane protocol terminations towards the UEs 156 over the Uu interface. For example, the gNB 160A may provide NR user plane and control plane protocol terminations toward the UE 156A over a Uu interface associated with a first protocol stack. The ng-eNBs 162 may provide Evolved UMTS Terrestrial Radio Access (E-UTRA) user plane and control plane protocol terminations towards the UEs 156 over a Uu interface, where E-UTRA refers to the 3GPP 4G radio-access technology. For example, the ng-eNB 162B may provide E-UTRA user plane and control plane protocol terminations towards the UE 156B over a Uu interface associated with a second protocol stack.

The 5G-CN 152 was described as being configured to handle NR and 4G radio accesses. It will be appreciated by one of ordinary skill in the art that it may be possible for NR to connect to a 4G core network in a mode known as “non-standalone operation.” In non-standalone operation, a 4G core network is used to provide (or at least support) control-plane functionality (e.g., initial access, mobility, and paging). Although only one AMF/UPF 158 is shown in FIG. 1B, one gNB or ng-eNB may be connected to multiple AMF/UPF nodes to provide redundancy and/or to load share across the multiple AMF/UPF nodes.

As discussed, an interface (e.g., Uu, Xn, and NG interfaces) between the network elements in FIG. 1B may be associated with a protocol stack that the network elements use to exchange data and signaling messages. A protocol stack may include two planes: a user plane and a control plane. The user plane may handle data of interest to a user, and the control plane may handle signaling messages of interest to the network elements.

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

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

FIG. 3 illustrates an example of services provided between protocol layers of the NR user plane protocol stack. Starting from the top of FIG. 2A and FIG. 3, the SDAPs 215 and 225 may perform QoS flow handling. The UE 210 may receive services through a PDU session, which may be a logical connection between the UE 210 and a DN. The PDU session may have one or more QoS flows. A UPF of a CN (e.g., the UPF 158B) may map IP packets to the one or more QoS flows of the PDU session based on QoS requirements (e.g., in terms of delay, data rate, and/or error rate). The SDAPs 215 and 225 may perform mapping/de-mapping between the one or more QoS flows and one or more data radio bearers. The mapping/de-mapping between the QoS flows and the data radio bearers may be determined by the SDAP 225 at the gNB 220. The SDAP 215 at the UE 210 may be informed of the mapping between the QoS flows and the data radio bearers through reflective mapping or control signaling received from the gNB 220. For reflective mapping, the SDAP 225 at the gNB 220 may mark the downlink packets with a QoS flow indicator (QFI), which may be observed by the SDAP 215 at the UE 210 to determine the mapping/de-mapping between the QoS flows and the data radio bearers.

The PDCPs 214 and 224 may perform header compression/decompression to reduce the amount of data that needs to be transmitted over the air interface, ciphering/deciphering to prevent unauthorized decoding of data transmitted over the air interface, and integrity protection (to ensure control messages originate from intended sources. The PDCPs 214 and 224 may perform retransmissions of undelivered packets, in-sequence delivery and reordering of packets, and removal of packets received in duplicate due to, for example, an intra-gNB handover. The PDCPs 214 and 224 may perform packet duplication to improve the likelihood of the packet being received and, at the receiver, remove any duplicate packets. Packet duplication may be useful for services that require high reliability.

Although not shown in FIG. 3, PDCPs 214 and 224 may perform mapping/de-mapping between a split radio bearer and RLC channels in a dual connectivity scenario. Dual connectivity is a technique that allows a UE to connect to two cells or, more generally, two cell groups: a master cell group (MCG) and a secondary cell group (SCG). A split bearer is when a single radio bearer, such as one of the radio bearers provided by the PDCPs 214 and 224 as a service to the SDAPs 215 and 225, is handled by cell groups in dual connectivity. The PDCPs 214 and 224 may map/de-map the split radio bearer between RLC channels belonging to cell groups.

The RLCs 213 and 223 may perform segmentation, retransmission through Automatic Repeat Request (ARQ), and removal of duplicate data units received from MACs 212 and 222, respectively. The RLCs 213 and 223 may support three transmission modes: transparent mode (TM); unacknowledged mode (UM); and acknowledged mode (AM). Based on the transmission mode an RLC is operating, the RLC may perform one or more of the noted functions. The RLC configuration may be per logical channel with no dependency on numerologies and/or Transmission Time Interval (TTI) durations. As shown in FIG. 3, the RLCs 213 and 223 may provide RLC channels as a service to PDCPs 214 and 224, respectively.

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

The PHYs 211 and 221 may perform mapping of transport channels to physical channels and digital and analog signal processing functions for sending and receiving information over the air interface. These digital and analog signal processing functions may include, for example, coding/decoding and modulation/demodulation. The PHYs 211 and 221 may perform multi-antenna mapping. As shown in FIG. 3, the PHYs 211 and 221 may provide one or more transport channels as a service to the MACs 212 and 222.

FIG. 4A illustrates an example downlink data flow through the NR user plane protocol stack. FIG. 4A illustrates a downlink data flow of three IP packets (n, n+1, and m) through the NR user plane protocol stack to generate two TBs at the gNB 220. An uplink data flow through the NR user plane protocol stack may be similar to the downlink data flow depicted in FIG. 4A.

The downlink data flow of FIG. 4A begins when SDAP 225 receives the three IP packets from one or more QoS flows and maps the three packets to radio bearers. In FIG. 4A, the SDAP 225 maps IP packets n and n+1 to a first radio bearer 402 and maps IP packet m to a second radio bearer 404. An SDAP header (labeled with an “H” in FIG. 4A) is added to an IP packet. The data unit from/to a higher protocol layer is referred to as a service data unit (SDU) of the lower protocol layer and the data unit to/from a lower protocol layer is referred to as a protocol data unit (PDU) of the higher protocol layer. As shown in FIG. 4A, the data unit from the SDAP 225 is an SDU of lower protocol layer PDCP 224 and is a PDU of the SDAP 225.

The remaining protocol layers in FIG. 4A may perform their associated functionality (e.g., with respect to FIG. 3), add corresponding headers, and forward their respective outputs to the next lower layer. For example, the PDCP 224 may perform IP-header compression and ciphering and forward its output to the RLC 223. The RLC 223 may optionally perform segmentation (e.g., as shown for IP packet m in FIG. 4A) and forward its output to the MAC 222. The MAC 222 may multiplex a number of RLC PDUs and may attach a MAC subheader to an RLC PDU to form a transport block. In NR, the MAC subheaders may be distributed across the MAC PDU, as illustrated in FIG. 4A. In LTE, the MAC subheaders may be entirely located at the beginning of the MAC PDU. The NR MAC PDU structure may reduce processing time and associated latency because the MAC PDU subheaders may be computed before the full MAC PDU is assembled.

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

FIG. 4B further illustrates MAC control elements (CEs) inserted into the MAC PDU by a MAC, such as MAC 223 or MAC 222. For example, FIG. 4B illustrates two MAC CEs inserted into the MAC PDU. MAC CEs may be inserted at the beginning of a MAC PDU for downlink transmissions (as shown in FIG. 4B) and at the end of a MAC PDU for uplink transmissions. MAC CEs may be used for in-band control signaling. Example MAC CEs include: scheduling-related MAC CEs, such as buffer status reports and power headroom reports; activation/deactivation MAC CEs, such as those for activation/deactivation of PDCP duplication detection, channel state information (CSI) reporting, sounding reference signal (SRS) transmission, and prior configured components; discontinuous reception (DRX) related MAC CEs; timing advance MAC CEs; and random access related MAC CEs. A MAC CE may be preceded by a MAC subheader with a similar format as described for MAC SDUs and may be identified with a reserved value in the LCID field that indicates the type of control information included in the MAC CE.

Before describing the NR control plane protocol stack, logical channels, transport channels, and physical channels are first described as well as a mapping between the channel types. One or more of the channels may be used to carry out functions associated with the NR control plane protocol stack described later below.

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

- a paging control channel (PCCH) for carrying paging messages used to page a UE whose location is not known to the network on a cell level;
- a broadcast control channel (BCCH) for carrying system information messages in the form of a master information block (MIB) and several system information blocks (SIBs), wherein the system information messages may be used by the UEs to obtain information about how a cell is configured and how to operate within the cell;
- a common control channel (CCCH) for carrying control messages together with random access;
- a dedicated control channel (DCCH) for carrying control messages to/from a specific the UE to configure the UE; and
- a dedicated traffic channel (DTCH) for carrying user data to/from a specific the UE.

Transport channels are used between the MAC and PHY layers and may be defined by how the information they carry is transmitted over the air interface. The set of transport channels defined by NR include, for example:

- a paging channel (PCH) for carrying paging messages that originated from the PCCH;
- a broadcast channel (BCH) for carrying the MIB from the BCCH;
- a downlink shared channel (DL-SCH) for carrying downlink data and signaling messages, including the SIBs from the BCCH;
- an uplink shared channel (UL-SCH) for carrying uplink data and signaling messages; and
- a random access channel (RACH) for allowing a UE to contact the network without any prior scheduling.

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

- a physical broadcast channel (PBCH) for carrying the MIB from the BCH;
- a physical downlink shared channel (PDSCH) for carrying downlink data and signaling messages from the DL-SCH, as well as paging messages from the PCH;
- a physical downlink control channel (PDCCH) for carrying downlink control information (DCI), which may include downlink scheduling commands, uplink scheduling grants, and uplink power control commands;
- a physical uplink shared channel (PUSCH) for carrying uplink data and signaling messages from the UL-SCH and in some instances uplink control information (UCI) as described below;
- a physical uplink control channel (PUCCH) for carrying UCI, which may include HARQ acknowledgments, channel quality indicators (CQI), pre-coding matrix indicators (PMI), rank indicators (RI), and scheduling requests (SR); and
- a physical random access channel (PRACH) for random access.

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

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

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

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

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

In RRC connected 602, the UE has an established RRC context and may have at least one RRC connection with a base station. The base station may be similar to one of the one or more base stations included in the RAN 104 depicted in FIG. 1A, one of the gNBs 160 or ng-eNBs 162 depicted in FIG. 1B, the gNB 220 depicted in FIG. 2A and FIG. 2B, or any other base station described in the present disclosure. The base station with which the UE is connected may have the RRC context for the UE. The RRC context, referred to as the UE context, may comprise parameters for communication between the UE and the base station. These parameters may include, for example: one or more AS contexts; one or more radio link configuration parameters; bearer configuration information (e.g., relating to a data radio bearer, signaling radio bearer, logical channel, QoS flow, and/or PDU session); security information; and/or PHY, MAC, RLC, PDCP, and/or SDAP layer configuration information. While in RRC connected 602, mobility of the UE may be managed by the RAN (e.g., the RAN 104 or the NG-RAN 154). The UE may measure the signal levels (e.g., reference signal levels) from a serving cell and neighboring cells and report these measurements to the base station currently serving the UE. The UE's serving base station may request a handover to a cell of one of the neighboring base stations based on the reported measurements. The RRC state may transition from RRC connected 602 to RRC idle 604 through a connection release procedure 608 or to RRC inactive 606 through a connection inactivation procedure 610.

In RRC idle 604, an RRC context may not be established for the UE. In RRC idle 604, the UE may not have an RRC connection with the base station. While in RRC idle 604, the UE may be in a sleep state for the majority of the time (e.g., to conserve battery power). The UE may wake up periodically (e.g., once in every discontinuous reception cycle) to monitor for paging messages from the RAN. Mobility of the UE may be managed by the UE through a procedure known as cell reselection. The RRC state may transition from RRC idle 604 to RRC connected 602 through a connection establishment procedure 612, which may involve a random access procedure as discussed in greater detail below.

In RRC inactive 606, the RRC context previously established is maintained in the UE and the base station. This allows for a fast transition to RRC connected 602 with reduced signaling overhead as compared to the transition from RRC idle 604 to RRC connected 602. While in RRC inactive 606, the UE may be in a sleep state and mobility of the UE may be managed by the UE through cell reselection. The RRC state may transition from RRC inactive 606 to RRC connected 602 through a connection resume procedure 614 or to RRC idle 604 though a connection release procedure 616 that may be the same as or similar to connection release procedure 608.

An RRC state may be associated with a mobility management mechanism. In RRC idle 604 and RRC inactive 606, mobility is managed by the UE through cell reselection. The purpose of mobility management in RRC idle 604 and RRC inactive 606 is to allow the network to be able to notify the UE of an event via a paging message without having to broadcast the paging message over the entire mobile communications network. The mobility management mechanism used in RRC idle 604 and RRC inactive 606 may allow the network to track the UE on a cell-group level so that the paging message may be broadcast over the cells of the cell group that the UE currently resides within instead of the entire mobile communication network. The mobility management mechanisms for RRC idle 604 and RRC inactive 606 track the UE on a cell-group level. They may do so using different granularities of grouping. For example, there may be three levels of cell-grouping granularity: individual cells; cells within a RAN area identified by a RAN area identifier (RAI); and cells within a group of RAN areas, referred to as a tracking area and identified by a tracking area identifier (TAI).

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

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

A base station storing an RRC context for a UE or a last serving base station of the UE may be referred to as an anchor base station. An anchor base station may maintain an RRC context for the UE at least during a period of time that the UE stays in a RAN notification area of the anchor base station and/or during a period of time that the UE stays in RRC inactive 606.

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

In NR, the physical signals and physical channels (discussed with respect to FIG. 5A and FIG. 5B) may be mapped onto orthogonal frequency divisional multiplexing (OFDM) symbols. OFDM is a multicarrier communication scheme that transmits data over F orthogonal subcarriers (or tones). Before transmission, the data may be mapped to a series of complex symbols (e.g., M-quadrature amplitude modulation (M-QAM) or M-phase shift keying (M-PSK) symbols), referred to as source symbols, and divided into F parallel symbol streams. The F parallel symbol streams may be treated as though they are in the frequency domain and used as inputs to an Inverse Fast Fourier Transform (IFFT) block that transforms them into the time domain. The IFFT block may take in F source symbols at a time, one from each of the F parallel symbol streams, and use each source symbol to modulate the amplitude and phase of one of F sinusoidal basis functions that correspond to the F orthogonal subcarriers. The output of the IFFT block may be F time-domain samples that represent the summation of the F orthogonal subcarriers. The F time-domain samples may form a single OFDM symbol. After some processing (e.g., addition of a cyclic prefix) and up-conversion, an OFDM symbol provided by the IFFT block may be transmitted over the air interface on a carrier frequency. The F parallel symbol streams may be mixed using an FFT block before being processed by the IFFT block. This operation produces Discrete Fourier Transform (DFT)-precoded OFDM symbols and may be used by UEs in the uplink to reduce the peak to average power ratio (PAPR). Inverse processing may be performed on the OFDM symbol at a receiver using an FFT block to recover the data mapped to the source symbols.

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

The duration of a slot may depend on the numerology used for the OFDM symbols of the slot. In NR, a flexible numerology is supported to accommodate different cell deployments (e.g., cells with carrier frequencies below 1 GHz up to cells with carrier frequencies in the mm-wave range). A numerology may be defined in terms of subcarrier spacing and cyclic prefix duration. For a numerology in NR, subcarrier spacings may be scaled up by powers of two from a baseline subcarrier spacing of 15 kHz, and cyclic prefix durations may be scaled down by powers of two from a baseline cyclic prefix duration of 4.7 μs. For example, NR defines numerologies with the following subcarrier spacing/cyclic prefix duration combinations: 15 kHz/4.7 μs; 30 kHz/2.3 μs; 60 kHz/1.2 μs; 120 kHz/0.59 μs; and 240 kHz/0.29 μs.

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

FIG. 8 illustrates an example configuration of a slot in the time and frequency domain for an NR carrier. The slot includes resource elements (REs) and resource blocks (RBs). An RE is the smallest physical resource in NR. An RE spans one OFDM symbol in the time domain by one subcarrier in the frequency domain as shown in FIG. 8. An RB spans twelve consecutive REs in the frequency domain as shown in FIG. 8. An NR carrier may be limited to a width of 275 RBs or 275×12=3300 subcarriers. Such a limitation, if used, may limit the NR carrier to 50, 100, 200, and 400 MHz for subcarrier spacings of 15, 30, 60, and 120 kHz, respectively, where the 400 MHz bandwidth may be set based on a 400 MHz per carrier bandwidth limit.

FIG. 8 illustrates a single numerology being used across the entire bandwidth of the NR carrier. In other example configurations, multiple numerologies may be supported on the same carrier.

NR may support wide carrier bandwidths (e.g., up to 400 MHz for a subcarrier spacing of 120 kHz). Not all UEs may be able to receive the full carrier bandwidth (e.g., due to hardware limitations). Also, receiving the full carrier bandwidth may be prohibitive in terms of UE power consumption. In an example, to reduce power consumption and/or for other purposes, a UE may adapt the size of the UE's receive bandwidth based on the amount of traffic the UE is scheduled to receive. This is referred to as bandwidth adaptation.

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

For unpaired spectra, a downlink BWP from a set of configured downlink BWPs may be linked with an uplink BWP from a set of configured uplink BWPs if a downlink BWP index of the downlink BWP and an uplink BWP index of the uplink BWP are the same. For unpaired spectra, a UE may expect that a center frequency for a downlink BWP is the same as a center frequency for an uplink BWP.

For a downlink BWP in a set of configured downlink BWPs on a primary cell (PCell), a base station may configure a UE with one or more control resource sets (CORESETs) for at least one search space. A search space is a set of locations in the time and frequency domains where the UE may find control information. The search space may be a UE-specific search space or a common search space (potentially usable by a plurality of UEs). For example, a base station may configure a UE with a common search space, on a PCell or on a primary secondary cell (PSCell), in an active downlink BWP.

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

One or more BWP indicator fields may be provided in Downlink Control Information (DCI). A value of a BWP indicator field may indicate which BWP in a set of configured BWPs is an active downlink BWP for one or more downlink receptions. The value of the one or more BWP indicator fields may indicate an active uplink BWP for one or more uplink transmissions.

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

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

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

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

FIG. 9 illustrates an example of bandwidth adaptation using three configured BWPs for an NR carrier. A UE configured with the three BWPs may switch from one BWP to another BWP at a switching point. In the example illustrated in FIG. 9, the BWPs include: a BWP 902 with a bandwidth of 40 MHz and a subcarrier spacing of 15 kHz; a BWP 904 with a bandwidth of 10 MHz and a subcarrier spacing of 15 kHz; and a BWP 906 with a bandwidth of 20 MHz and a subcarrier spacing of 60 kHz. The BWP 902 may be an initial active BWP, and the BWP 904 may be a default BWP. The UE may switch between BWPs at switching points. In the example of FIG. 9, the UE may switch from the BWP 902 to the BWP 904 at a switching point 908. The switching at the switching point 908 may occur for any suitable reason, for example, in response to an expiry of a BWP inactivity timer (indicating switching to the default BWP) and/or in response to receiving a DCI indicating BWP 904 as the active BWP. The UE may switch at a switching point 910 from active BWP 904 to BWP 906 in response receiving a DCI indicating BWP 906 as the active BWP. The UE may switch at a switching point 912 from active BWP 906 to BWP 904 in response to an expiry of a BWP inactivity timer and/or in response receiving a DCI indicating BWP 904 as the active BWP. The UE may switch at a switching point 914 from active BWP 904 to BWP 902 in response receiving a DCI indicating BWP 902 as the active BWP.

If a UE is configured for a secondary cell with a default downlink BWP in a set of configured downlink BWPs and a timer value, UE procedures for switching BWPs on a secondary cell may be the same/similar as those on a primary cell. For example, the UE may use the timer value and the default downlink BWP for the secondary cell in the same/similar manner as the UE

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

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

In an example, up to 32 CCs may be aggregated. The aggregated CCs may have the same or different bandwidths, subcarrier spacing, and/or duplexing schemes (TDD or FDD). A serving cell for a UE using CA may have a downlink CC. For FDD, one or more uplink CCs may be optionally configured for a serving cell. The ability to aggregate more downlink carriers than uplink carriers may be useful, for example, when the UE has more data traffic in the downlink than in the uplink.

When CA is used, one of the aggregated cells for a UE may be referred to as a primary cell (PCell). The PCell may be the serving cell that the UE initially connects to at RRC connection establishment, reestablishment, and/or handover. The PCell may provide the UE with NAS mobility information and the security input. UEs may have different PCells. In the downlink, the carrier corresponding to the PCell may be referred to as the downlink primary CC (DL PCC). In the uplink, the carrier corresponding to the PCell may be referred to as the uplink primary CC (UL PCC). The other aggregated cells for the UE may be referred to as secondary cells (SCells). In an example, the SCells may be configured after the PCell is configured for the UE. For example, an SCell may be configured through an RRC Connection Reconfiguration procedure. In the downlink, the carrier corresponding to an SCell may be referred to as a downlink secondary CC (DL SCC). In the uplink, the carrier corresponding to the SCell may be referred to as the uplink secondary CC (UL SCC).

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

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

FIG. 10B illustrates an example of how aggregated cells may be configured into one or more PUCCH groups. A PUCCH group 1010 and a PUCCH group 1050 may include one or more downlink CCs, respectively. In the example of FIG. 10B, the PUCCH group 1010 includes three downlink CCs: a PCell 1011, an SCell 1012, and an SCell 1013. The PUCCH group 1050 includes three downlink CCs in the present example: a PCell 1051, an SCell 1052, and an SCell 1053. One or more uplink CCs may be configured as a PCell 1021, an SCell 1022, and an SCell 1023. One or more other uplink CCs may be configured as a primary Scell (PSCell) 1061, an SCell 1062, and an SCell 1063. Uplink control information (UCI) related to the downlink CCs of the PUCCH group 1010, shown as UCI 1031, UCI 1032, and UCI 1033, may be transmitted in the uplink of the PCell 1021. Uplink control information (UCI) related to the downlink CCs of the PUCCH group 1050, shown as UCI 1071, UCI 1072, and UCI 1073, may be transmitted in the uplink of the PSCell 1061. In an example, if the aggregated cells depicted in FIG. 10B were not divided into the PUCCH group 1010 and the PUCCH group 1050, a single uplink PCell to transmit UCI relating to the downlink CCs, and the PCell may become overloaded. By dividing transmissions of UCI between the PCell 1021 and the PSCell 1061, overloading may be prevented.

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

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

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

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

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

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

The SS/PBCH block may be used by the UE to determine one or more parameters of the cell. For example, the UE may determine a physical cell identifier (PCI) of the cell based on the sequences of the PSS and the SSS, respectively. The UE may determine a location of a frame boundary of the cell based on the location of the SS/PBCH block. For example, the SS/PBCH block may indicate that it has been transmitted in accordance with a transmission pattern, wherein a SS/PBCH block in the transmission pattern is a known distance from the frame boundary.

The PBCH may use a QPSK modulation and may use forward error correction (FEC). The FEC may use polar coding. One or more symbols spanned by the PBCH may carry one or more DMRSs for demodulation of the PBCH. The PBCH may include an indication of a current system frame number (SFN) of the cell and/or a SS/PBCH block timing index. These parameters may facilitate time synchronization of the UE to the base station. The PBCH may include a master information block (MIB) used to provide the UE with one or more parameters. The MIB may be used by the UE to locate remaining minimum system information (RMSI) associated with the cell. The RMSI may include a System Information Block Type 1 (SIB1). The SIB1 may contain information needed by the UE to access the cell. The UE may use one or more parameters of the MIB to monitor PDCCH, which may be used to schedule PDSCH. The PDSCH may include the SIB1. The SIB1 may be decoded using parameters provided in the MIB. The PBCH may indicate an absence of SIB1. Based on the PBCH indicating the absence of SIB1, the UE may be pointed to a frequency. The UE may search for an SS/PBCH block at the frequency to which the UE is pointed.

The UE may assume that one or more SS/PBCH blocks transmitted with a same SS/PBCH block index are quasi co-located (QCLed) (e.g., having the same/similar Doppler spread, Doppler shift, average gain, average delay, and/or spatial Rx parameters). The UE may not assume QCL for SS/PBCH block transmissions having different SS/PBCH block indices. SS/PBCH blocks (e.g., those within a half-frame) may be transmitted in spatial directions (e.g., using different beams that span a coverage area of the cell). In an example, a first SS/PBCH block may be transmitted in a first spatial direction using a first beam, and a second SS/PBCH block may be transmitted in a second spatial direction using a second beam.

In an example, within a frequency span of a carrier, a base station may transmit a plurality of SS/PBCH blocks. In an example, a first PCI of a first SS/PBCH block of the plurality of SS/PBCH blocks may be different from a second PCI of a second SS/PBCH block of the plurality of SS/PBCH blocks. The PCIs of SS/PBCH blocks transmitted in different frequency locations may be different or the same.

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

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

The base station may configure the UE to report CSI measurements. The base station may configure the UE to provide CSI reports periodically, aperiodically, or semi-persistently. For periodic CSI reporting, the UE may be configured with a timing and/or periodicity of a plurality of CSI reports. For aperiodic CSI reporting, the base station may request a CSI report. For example, the base station may command the UE to measure a configured CSI-RS resource and provide a CSI report relating to the measurements. For semi-persistent CSI reporting, the base station may configure the UE to transmit periodically, and selectively activate or deactivate the periodic reporting. The base station may configure the UE with a CSI-RS resource set and CSI reports using RRC signaling.

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

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

In an example, a transmitter (e.g., a base station) may use a precoder matrices for a part of a transmission bandwidth. For example, the transmitter may use a first precoder matrix for a first bandwidth and a second precoder matrix for a second bandwidth. The first precoder matrix and the second precoder matrix may be different based on the first bandwidth being different from the second bandwidth. The UE may assume that a same precoding matrix is used across a set of PRBs. The set of PRBs may be denoted as a precoding resource block group (PRG).

A PDSCH may comprise one or more layers. The UE may assume that at least one symbol with DMRS is present on a layer of the one or more layers of the PDSCH. A higher layer may configure up to 3 DMRSs for the PDSCH.

Downlink PT-RS may be transmitted by a base station and used by a UE for phase-noise compensation. Whether a downlink PT-RS is present or not may depend on an RRC configuration. The presence and/or pattern of the downlink PT-RS may be configured on a UE-specific basis using a combination of RRC signaling and/or an association with one or more parameters employed for other purposes (e.g., modulation and coding scheme (MCS)), which may be indicated by DCI. When configured, a dynamic presence of a downlink PT-RS may be associated with one or more DCI parameters comprising at least MCS. An NR network may support a plurality of PT-RS densities defined in the time and/or frequency domains. When present, a frequency domain density may be associated with at least one configuration of a scheduled bandwidth. The UE may assume a same precoding for a DMRS port and a PT-RS port. A number of PT-RS ports may be fewer than a number of DMRS ports in a scheduled resource. Downlink PT-RS may be confined in the scheduled time/frequency duration for the UE. Downlink PT-RS may be transmitted on symbols to facilitate phase tracking at the receiver.

The UE may transmit an uplink DMRS to a base station for channel estimation. For example, the base station may use the uplink DMRS for coherent demodulation of one or more uplink physical channels. For example, the UE may transmit an uplink DMRS with a PUSCH and/or a PUCCH. The uplink DM-RS may span a range of frequencies that is similar to a range of frequencies associated with the corresponding physical channel. The base station may configure the UE with one or more uplink DMRS configurations. At least one DMRS configuration may support a front-loaded DMRS pattern. The front-loaded DMRS may be mapped over one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). One or more uplink DMRSs may be configured to transmit at one or more symbols of a PUSCH and/or a PUCCH. The base station may semi-statically configure the UE with a number (e.g. maximum number) of front-loaded DMRS symbols for the PUSCH and/or the PUCCH, which the UE may use to schedule a single-symbol DMRS and/or a double-symbol DMRS. An NR network may support (e.g., for cyclic prefix orthogonal frequency division multiplexing (CP-OFDM)) a common DMRS structure for downlink and uplink, wherein a DMRS location, a DMRS pattern, and/or a scrambling sequence for the DMRS may be the same or different.

A PUSCH may comprise one or more layers, and the UE may transmit at least one symbol with DMRS present on a layer of the one or more layers of the PUSCH. In an example, a higher layer may configure up to three DMRSs for the PUSCH.

Uplink PT-RS (which may be used by a base station for phase tracking and/or phase-noise compensation) may or may not be present depending on an RRC configuration of the UE. The presence and/or pattern of uplink PT-RS may be configured on a UE-specific basis by a combination of RRC signaling and/or one or more parameters employed for other purposes (e.g., Modulation and Coding Scheme (MCS)), which may be indicated by DCI. When configured, a dynamic presence of uplink PT-RS may be associated with one or more DCI parameters comprising at least MCS. A radio network may support a plurality of uplink PT-RS densities defined in time/frequency domain. When present, a frequency domain density may be associated with at least one configuration of a scheduled bandwidth. The UE may assume a same precoding for a DMRS port and a PT-RS port. A number of PT-RS ports may be fewer than a number of DMRS ports in a scheduled resource. For example, uplink PT-RS may be confined in the scheduled time/frequency duration for the UE.

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

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

An antenna port is defined such that the channel over which a symbol on the antenna port is conveyed can be inferred from the channel over which another symbol on the same antenna port is conveyed. If a first symbol and a second symbol are transmitted on the same antenna port, the receiver may infer the channel (e.g., fading gain, multipath delay, and/or the like) for conveying the second symbol on the antenna port, from the channel for conveying the first symbol on the antenna port. A first antenna port and a second antenna port may be referred to as quasi co-located (QCLed) if one or more large-scale properties of the channel over which a first symbol on the first antenna port is conveyed may be inferred from the channel over which a second symbol on a second antenna port is conveyed. The one or more large-scale properties may comprise at least one of: a delay spread; a Doppler spread; a Doppler shift; an average gain; an average delay; and/or spatial Receiving (Rx) parameters.

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

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

The three beams illustrated in FIG. 11B may be configured for a UE in a UE-specific configuration. Three beams are illustrated in FIG. 11B (beam #1, beam #2, and beam #3), more or fewer beams may be configured. Beam #1 may be allocated with CSI-RS 1101 that may be transmitted in one or more subcarriers in an RB of a first symbol. Beam #2 may be allocated with CSI-RS 1102 that may be transmitted in one or more subcarriers in an RB of a second symbol. Beam #3 may be allocated with CSI-RS 1103 that may be transmitted in one or more subcarriers in an RB of a third symbol. By using frequency division multiplexing (FDM), a base station may use other subcarriers in a same RB (for example, those that are not used to transmit CSI-RS 1101) to transmit another CSI-RS associated with a beam for another UE. By using time domain multiplexing (TDM), beams used for the UE may be configured such that beams for the UE use symbols from beams of other UEs.

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

In a beam management procedure, a UE may assess (e.g., measure) a channel quality of one or more beam pair links, a beam pair link comprising a transmitting beam transmitted by a base station and a receiving beam received by the UE. Based on the assessment, the UE may transmit a beam measurement report indicating one or more beam pair quality parameters comprising, e.g., one or more beam identifications (e.g., a beam index, a reference signal index, or the like), RSRP, a precoding matrix indicator (PMI), a channel quality indicator (CQI), and/or a rank indicator (RI).

FIG. 12A illustrates examples of three downlink beam management procedures: P1, P2, and P3. Procedure P1 may enable a UE measurement on transmit (Tx) beams of a transmission reception point (TRP) (or multiple TRPs), e.g., to support a selection of one or more base station Tx beams and/or UE Rx beams (shown as ovals in the top row and bottom row, respectively, of P1). Beamforming at a TRP may comprise a Tx beam sweep for a set of beams (shown, in the top rows of P1 and P2, as ovals rotated in a counter-clockwise direction indicated by the dashed arrow). Beamforming at a UE may comprise an Rx beam sweep for a set of beams (shown, in the bottom rows of P1 and P3, as ovals rotated in a clockwise direction indicated by the dashed arrow). Procedure P2 may be used to enable a UE measurement on Tx beams of a TRP (shown, in the top row of P2, as ovals rotated in a counter-clockwise direction indicated by the dashed arrow). The UE and/or the base station may perform procedure P2 using a smaller set of beams than is used in procedure P1, or using narrower beams than the beams used in procedure P1. This may be referred to as beam refinement. The UE may perform procedure P3 for Rx beam determination by using the same Tx beam at the base station and sweeping an Rx beam at the UE.

FIG. 12B illustrates examples of three uplink beam management procedures: U1, U2, and U3. Procedure U1 may be used to enable a base station to perform a measurement on Tx beams of a UE, e.g., to support a selection of one or more UE Tx beams and/or base station Rx beams (shown as ovals in the top row and bottom row, respectively, of U1). Beamforming at the UE may include, e.g., a Tx beam sweep from a set of beams (shown in the bottom rows of U1 and U3 as ovals rotated in a clockwise direction indicated by the dashed arrow). Beamforming at the base station may include, e.g., an Rx beam sweep from a set of beams (shown, in the top rows of U1 and U2, as ovals rotated in a counter-clockwise direction indicated by the dashed arrow). Procedure U2 may be used to enable the base station to adjust its Rx beam when the UE uses a fixed Tx beam. The UE and/or the base station may perform procedure U2 using a smaller set of beams than is used in procedure P1, or using narrower beams than the beams used in procedure P1. This may be referred to as beam refinement The UE may perform procedure U3 to adjust its Tx beam when the base station uses a fixed Rx beam.

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

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

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

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

The configuration message 1310 may be transmitted, for example, using one or more RRC messages. The one or more RRC messages may indicate one or more random access channel (RACH) parameters to the UE. The one or more RACH parameters may comprise at least one of following: general parameters for one or more random access procedures (e.g., RACH-configGeneral); cell-specific parameters (e.g., RACH-ConfigCommon); and/or dedicated parameters (e.g., RACH-configDedicated). The base station may broadcast or multicast the one or more RRC messages to one or more UEs. The one or more RRC messages may be UE-specific (e.g., dedicated RRC messages transmitted to a UE in an RRC_CONNECTED state and/or in an RRC_INACTIVE state). The UE may determine, based on the one or more RACH parameters, a time-frequency resource and/or an uplink transmit power for transmission of the Msg 1 1311 and/or the Msg 3 1313. Based on the one or more RACH parameters, the UE may determine a reception timing and a downlink channel for receiving the Msg 2 1312 and the Msg 4 1314.

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

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

The Msg 1 1311 may include one or more preamble transmissions (e.g., a preamble transmission and one or more preamble retransmissions). An RRC message may be used to configure one or more preamble groups (e.g., group A and/or group B). A preamble group may comprise one or more preambles. The UE may determine the preamble group based on a pathloss measurement and/or a size of the Msg 3 1313. The UE may measure an RSRP of one or more reference signals (e.g., SSBs and/or CSI-RSs) and determine at least one reference signal having an RSRP above an RSRP threshold (e.g., rsrp-ThresholdSSB and/or rsrp-ThresholdCSI-RS). The UE may select at least one preamble associated with the one or more reference signals and/or a selected preamble group, for example, if the association between the one or more preambles and the at least one reference signal is configured by an RRC message.

The UE may determine the preamble based on the one or more RACH parameters provided in the configuration message 1310. For example, the UE may determine the preamble based on a pathloss measurement, an RSRP measurement, and/or a size of the Msg 3 1313. As another example, the one or more RACH parameters may indicate: a preamble format; a maximum number of preamble transmissions; and/or one or more thresholds for determining one or more preamble groups (e.g., group A and group B). A base station may use the one or more RACH parameters to configure the UE with an association between one or more preambles and one or more reference signals (e.g., SSBs and/or CSI-RSs). If the association is configured, the UE may determine the preamble to include in Msg 1 1311 based on the association. The Msg 1 1311 may be transmitted to the base station via one or more PRACH occasions. The UE may use one or more reference signals (e.g., SSBs and/or CSI-RSs) for selection of the preamble and for determining of the PRACH occasion. One or more RACH parameters (e.g., ra-ssb-OccasionMskIndex and/or ra-OccasionList) may indicate an association between the PRACH occasions and the one or more reference signals.

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

The Msg 2 1312 received by the UE may include an RAR. In some scenarios, the Msg 2 1312 may include multiple RARs corresponding to multiple UEs. The Msg 2 1312 may be received after or in response to the transmitting of the Msg 1 1311. The Msg 2 1312 may be scheduled on the DL-SCH and indicated on a PDCCH using a random access RNTI (RA-RNTI). The Msg 2 1312 may indicate that the Msg 1 1311 was received by the base station. The Msg 2 1312 may include a time-alignment command that may be used by the UE to adjust the UE's transmission timing, a scheduling grant for transmission of the Msg 3 1313, and/or a Temporary Cell RNTI (TC-RNTI). After transmitting a preamble, the UE may start a time window (e.g., ra-ResponseWindow) to monitor a PDCCH for the Msg 2 1312. The UE may determine when to start the time window based on a PRACH occasion that the UE uses to transmit the preamble. For example, the UE may start the time window one or more symbols after a last symbol of the preamble (e.g., at a first PDCCH occasion from an end of a preamble transmission). The one or more symbols may be determined based on a numerology. The PDCCH may be in a common search space (e.g., a Type1-PDCCH common search space) configured by an RRC message. The UE may identify the RAR based on a Radio Network Temporary Identifier (RNTI). RNTIs may be used depending on one or more events initiating the random access procedure. The UE may use random access RNTI (RA-RNTI). The RA-RNTI may be associated with PRACH occasions in which the UE transmits a preamble. For example, the UE may determine the RA-RNTI based on: an OFDM symbol index; a slot index; a frequency domain index; and/or a UL carrier indicator of the PRACH occasions. An example of RA-RNTI may be as follows:

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

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

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

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

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

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

The contention-free random access procedure illustrated in FIG. 13B may be initiated for a beam failure recovery, other SI request, SCell addition, and/or handover. For example, a base station may indicate or assign to the UE the preamble to be used for the Msg 1 1321. The UE may receive, from the base station via PDCCH and/or RRC, an indication of a preamble (e.g., ra-PreambleIndex).

After transmitting a preamble, the UE may start a time window (e.g., ra-ResponseWindow) to monitor a PDCCH for the RAR. In the event of a beam failure recovery request, the base station may configure the UE with a separate time window and/or a separate PDCCH in a search space indicated by an RRC message (e.g., recoverySearchSpaceId). The UE may monitor for a PDCCH transmission addressed to a Cell RNTI (C-RNTI) on the search space. In the contention-free random access procedure illustrated in FIG. 13B, the UE may determine that a random access procedure successfully completes after or in response to transmission of Msg 1 1321 and reception of a corresponding Msg 2 1322. The UE may determine that a random access procedure successfully completes, for example, if a PDCCH transmission is addressed to a C-RNTI. The UE may determine that a random access procedure successfully completes, for example, if the UE receives an RAR comprising a preamble identifier corresponding to a preamble transmitted by the UE and/or the RAR comprises a MAC sub-PDU with the preamble identifier. The UE may determine the response as an indication of an acknowledgement for an SI request.

FIG. 13C illustrates another two-step random access procedure. Similar to the random access procedures illustrated in FIGS. 13A and 13B, a base station may, prior to initiation of the procedure, transmit a configuration message 1330 to the UE. The configuration message 1330 may be analogous in some respects to the configuration message 1310 and/or the configuration message 1320. The procedure illustrated in FIG. 13C comprises transmission of two messages: a Msg A 1331 and a Msg B 1332.

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

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

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

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

A UE and a base station may exchange control signaling. The control signaling may be referred to as L1/L2 control signaling and may originate from the PHY layer (e.g., layer 1) and/or the MAC layer (e.g., layer 2). The control signaling may comprise downlink control signaling transmitted from the base station to the UE and/or uplink control signaling transmitted from the UE to the base station.

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

A base station may attach one or more cyclic redundancy check (CRC) parity bits to a DCI in order to facilitate detection of transmission errors. When the DCI is intended for a UE (or a group of the UEs), the base station may scramble the CRC parity bits with an identifier of the UE (or an identifier of the group of the UEs). Scrambling the CRC parity bits with the identifier may comprise Modulo-2 addition (or an exclusive OR operation) of the identifier value and the CRC parity bits. The identifier may comprise a 16-bit value of a radio network temporary identifier (RNTI).

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

Depending on the purpose and/or content of a DCI, the base station may transmit the DCIs with one or more DCI formats. For example, DCI format 0_0 may be used for scheduling of PUSCH in a cell. DCI format 0_0 may be a fallback DCI format (e.g., with compact DCI payloads). DCI format 0_1 may be used for scheduling of PUSCH in a cell (e.g., with more DCI payloads than DCI format 0_0). DCI format 1_0 may be used for scheduling of PDSCH in a cell. DCI format 1_0 may be a fallback DCI format (e.g., with compact DCI payloads). DCI format 1_1 may be used for scheduling of PDSCH in a cell (e.g., with more DCI payloads than DCI format 1_0). DCI format 2_0 may be used for providing a slot format indication to a group of UEs. DCI format 2_1 may be used for notifying a group of UEs of a physical resource block and/or OFDM symbol where the UE may assume no transmission is intended to the UE. DCI format 2_2 may be used for transmission of a transmit power control (TPC) command for PUCCH or PUSCH. DCI format 2_3 may be used for transmission of a group of TPC commands for SRS transmissions by one or more UEs. DCI format(s) for new functions may be defined in future releases. DCI formats may have different DCI sizes, or may share the same DCI size.

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

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

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

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

As shown in FIG. 14B, the UE may determine a time-frequency resource for a CORESET based on RRC messages. The UE may determine a CCE-to-REG mapping (e.g., interleaved or non-interleaved, and/or mapping parameters) for the CORESET based on configuration parameters of the CORESET. The UE may determine a number (e.g., at most 10) of search space sets configured on the CORESET based on the RRC messages. The UE may monitor a set of PDCCH candidates according to configuration parameters of a search space set. The UE may monitor a set of PDCCH candidates in one or more CORESETs for detecting one or more DCIs. Monitoring may comprise decoding one or more PDCCH candidates of the set of the PDCCH candidates according to the monitored DCI formats. Monitoring may comprise decoding a DCI content of one or more PDCCH candidates with possible (or configured) PDCCH locations, possible (or configured) PDCCH formats (e.g., number of CCEs, number of PDCCH candidates in common search spaces, and/or number of PDCCH candidates in the UE-specific search spaces) and possible (or configured) DCI formats. The decoding may be referred to as blind decoding. The UE may determine a DCI as valid for the UE, in response to CRC checking (e.g., scrambled bits for CRC parity bits of the DCI matching a RNTI value). The UE may process information contained in the DCI (e.g., a scheduling assignment, an uplink grant, power control, a slot format indication, a downlink preemption, and/or the like).

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

There may be five PUCCH formats and the UE may determine a PUCCH format based on a size of the UCI (e.g., a number of uplink symbols of UCI transmission and a number of UCI bits). PUCCH format 0 may have a length of one or two OFDM symbols and may include two or fewer bits. The UE may transmit UCI in a PUCCH resource using PUCCH format 0 if the transmission is over one or two symbols and the number of HARQ-ACK information bits with positive or negative SR (HARQ-ACK/SR bits) is one or two. PUCCH format 1 may occupy a number between four and fourteen OFDM symbols and may include two or fewer bits. The UE may use PUCCH format 1 if the transmission is four or more symbols and the number of HARQ-ACK/SR bits is one or two. PUCCH format 2 may occupy one or two OFDM symbols and may include more than two bits. The UE may use PUCCH format 2 if the transmission is over one or two symbols and the number of UCI bits is two or more. PUCCH format 3 may occupy a number between four and fourteen OFDM symbols and may include more than two bits. The UE may use PUCCH format 3 if the transmission is four or more symbols, the number of UCI bits is two or more and PUCCH resource does not include an orthogonal cover code. PUCCH format 4 may occupy a number between four and fourteen OFDM symbols and may include more than two bits. The UE may use PUCCH format 4 if the transmission is four or more symbols, the number of UCI bits is two or more and the PUCCH resource includes an orthogonal cover code.

The base station may transmit configuration parameters to the UE for a plurality of PUCCH resource sets using, for example, an RRC message. The plurality of PUCCH resource sets (e.g., up to four sets) may be configured on an uplink BWP of a cell. A PUCCH resource set may be configured with a PUCCH resource set index, a plurality of PUCCH resources with a PUCCH resource being identified by a PUCCH resource identifier (e.g., pucch-Resourceid), and/or a number (e.g. a maximum number) of UCI information bits the UE may transmit using one of the plurality of PUCCH resources in the PUCCH resource set. When configured with a plurality of PUCCH resource sets, the UE may select one of the plurality of PUCCH resource sets based on a total bit length of the UCI information bits (e.g., HARQ-ACK, SR, and/or CSI). If the total bit length of UCI information bits is two or fewer, the UE may select a first PUCCH resource set having a PUCCH resource set index equal to “0”. If the total bit length of UCI information bits is greater than two and less than or equal to a first configured value, the UE may select a second PUCCH resource set having a PUCCH resource set index equal to “1”. If the total bit length of UCI information bits is greater than the first configured value and less than or equal to a second configured value, the UE may select a third PUCCH resource set having a PUCCH resource set index equal to “2”. If the total bit length of UCI information bits is greater than the second configured value and less than or equal to a third value (e.g., 1406), the UE may select a fourth PUCCH resource set having a PUCCH resource set index equal to “3”.

After determining a PUCCH resource set from a plurality of PUCCH resource sets, the UE may determine a PUCCH resource from the PUCCH resource set for UCI (HARQ-ACK, CSI, and/or SR) transmission. The UE may determine the PUCCH resource based on a PUCCH resource indicator in a DCI (e.g., with a DCI format 1_0 or DCI for 1_1) received on a PDCCH. A three-bit PUCCH resource indicator in the DCI may indicate one of eight PUCCH resources in the PUCCH resource set. Based on the PUCCH resource indicator, the UE may transmit the UCI (HARQ-ACK, CSI and/or SR) using a PUCCH resource indicated by the PUCCH resource indicator in the DCI.

FIG. 15 illustrates an example of a wireless device 1502 in communication with a base station 1504 in accordance with embodiments of the present disclosure. The wireless device 1502 and base station 1504 may be part of a mobile communication network, such as the mobile communication network 100 illustrated in FIG. 1A, the mobile communication network 150 illustrated in FIG. 1B, or any other communication network. Only one wireless device 1502 and one base station 1504 are illustrated in FIG. 15, but it will be understood that a mobile communication network may include more than one UE and/or more than one base station, with the same or similar configuration as those shown in FIG. 15.

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

In the downlink, data to be sent to the wireless device 1502 from the base station 1504 may be provided to the processing system 1508 of the base station 1504. The data may be provided to the processing system 1508 by, for example, a core network. In the uplink, data to be sent to the base station 1504 from the wireless device 1502 may be provided to the processing system 1518 of the wireless device 1502. The processing system 1508 and the processing system 1518 may implement layer 3 and layer 2 OSI functionality to process the data for transmission. Layer 2 may include an SDAP layer, a PDCP layer, an RLC layer, and a MAC layer, for example, with respect to FIG. 2A, FIG. 2B, FIG. 3, and FIG. 4A. Layer 3 may include an RRC layer as with respect to FIG. 2B.

After being processed by processing system 1508, the data to be sent to the wireless device 1502 may be provided to a transmission processing system 1510 of base station 1504. Similarly, after being processed by the processing system 1518, the data to be sent to base station 1504 may be provided to a transmission processing system 1520 of the wireless device 1502. The transmission processing system 1510 and the transmission processing system 1520 may implement layer 1 OSI functionality. Layer 1 may include a PHY layer with respect to FIG. 2A, FIG. 2B, FIG. 3, and FIG. 4A. For transmit processing, the PHY layer may perform, for example, forward error correction coding of transport channels, interleaving, rate matching, mapping of transport channels to physical channels, modulation of physical channel, multiple-input multiple-output (MIMO) or multi-antenna processing, and/or the like.

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

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

The processing system 1508 and the processing system 1518 may be associated with a memory 1514 and a memory 1524, respectively. Memory 1514 and memory 1524 (e.g., one or more non-transitory computer readable mediums) may store computer program instructions or code that may be executed by the processing system 1508 and/or the processing system 1518 to carry out one or more of the functionalities discussed in the present application. Although not shown in FIG. 15, the transmission processing system 1510, the transmission processing system 1520, the reception processing system 1512, and/or the reception processing system 1522 may be coupled to a memory (e.g., one or more non-transitory computer readable mediums) storing computer program instructions or code that may be executed to carry out one or more of their respective functionalities.

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

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

FIG. 16A illustrates an example structure for uplink transmission. A baseband signal representing a physical uplink shared channel may perform one or more functions. The one or more functions may comprise at least one of: scrambling; modulation of scrambled bits to generate complex-valued symbols; mapping of the complex-valued modulation symbols onto one or several transmission layers; transform precoding to generate complex-valued symbols; precoding of the complex-valued symbols; mapping of precoded complex-valued symbols to resource elements; generation of complex-valued time-domain Single Carrier-Frequency Division Multiple Access (SC-FDMA) or CP-OFDM signal for an antenna port; and/or the like. In an example, when transform precoding is enabled, a SC-FDMA signal for uplink transmission may be generated. In an example, when transform precoding is not enabled, an CP-OFDM signal for uplink transmission may be generated by FIG. 16A. These functions are illustrated as examples and it is anticipated that other mechanisms may be implemented in various embodiments.

FIG. 16B illustrates an example structure for modulation and up-conversion of a baseband signal to a carrier frequency. The baseband signal may be a complex-valued SC-FDMA or CP-OFDM baseband signal for an antenna port and/or a complex-valued Physical Random Access Channel (PRACH) baseband signal. Filtering may be employed prior to transmission.

FIG. 16C illustrates an example structure for downlink transmissions. A baseband signal representing a physical downlink channel may perform one or more functions. The one or more functions may comprise: scrambling of coded bits in a codeword to be transmitted on a physical channel; modulation of scrambled bits to generate complex-valued modulation symbols; mapping of the complex-valued modulation symbols onto one or several transmission layers; precoding of the complex-valued modulation symbols on a layer for transmission on the antenna ports; mapping of complex-valued modulation symbols for an antenna port to resource elements; generation of complex-valued time-domain OFDM signal for an antenna port; and/or the like. These functions are illustrated as examples and it is anticipated that other mechanisms may be implemented in various embodiments.

FIG. 16D illustrates another example structure for modulation and up-conversion of a baseband signal to a carrier frequency. The baseband signal may be a complex-valued OFDM baseband signal for an antenna port. Filtering may be employed prior to transmission.

A wireless device may receive from a base station one or more messages (e.g. RRC messages) comprising configuration parameters of a plurality of cells (e.g. primary cell, secondary cell). The wireless device may communicate with at least one base station (e.g. two or more base stations in dual-connectivity) via the plurality of cells. The one or more messages (e.g. as a part of the configuration parameters) may comprise parameters of physical, MAC, RLC, PCDP, SDAP, RRC layers for configuring the wireless device. For example, the configuration parameters may comprise parameters for configuring physical and MAC layer channels, bearers, etc. For example, the configuration parameters may comprise parameters indicating values of timers for physical, MAC, RLC, PCDP, SDAP, RRC layers, and/or communication channels.

A timer may begin running once it is started and continue running until it is stopped or until it expires. A timer may be started if it is not running or restarted if it is running. A timer may be associated with a value (e.g. the timer may be started or restarted from a value or may be started from zero and expire once it reaches the value). The duration of a timer may not be updated until the timer is stopped or expires (e.g., due to BWP switching). A timer may be used to measure a time period/window for a process. When the specification refers to an implementation and procedure related to one or more timers, it will be understood that there are multiple ways to implement the one or more timers. For example, it will be understood that one or more of the multiple ways to implement a timer may be used to measure a time period/window for the procedure. For example, a random access response window timer may be used for measuring a window of time for receiving a random access response. In an example, instead of starting and expiry of a random access response window timer, the time difference between two time stamps may be used. When a timer is restarted, a process for measurement of time window may be restarted. Other example implementations may be provided to restart a measurement of a time window.

FIG. 17 illustrates example configuration parameters for a wireless device to receive control and/or data from a base station. A wireless device may receive one or more radio resource control (RRC) messages comprising configuration parameters of a cell. The configuration parameters may comprise one or more parameters of a serving cell configuration (e.g., ServingCellConfig). The one or more parameters of the serving cell configuration may comprise one or more downlink bandwidth parts (e.g., a list of BWP-Downlinks). The one or more parameters of the serving cell configuration may comprise one or more uplink bandwidth parts (e.g., a list of BWP-Uplinks). A downlink bandwidth part (e.g., BWP-Downlink) and/or an uplink bandwidth part (e.g., BWP-Uplink) may comprise a bandwidth part index (e.g., bwp-Id), configuration parameters of a cell-common downlink bandwidth part (e.g., BWP-DownlinkCommon, BWP-UplinkCommon), and/or a UE-specific downlink bandwidth part (e.g., BWP-DownlinkDedicated, BWP-UplinkDedicated). For example, the bandwidth part index (bwp-Id) may indicate a bandwidth part configuration. For example, an index of the bandwidth part is the bandwidth part index. The bandwidth part configuration may comprise a location and bandwidth information (locationAndBandwidth). The locationAndBandwidth may indicate a starting resource block (RB) of the bandwidth part and a bandwidth of the bandwidth part, based on a reference point (e.g., a pointA of a carrier/cell for the bandwidth part). The bandwidth part configuration may comprise a subcarrier spacing (e.g., subcarrierSpacing) and a cyclic prefix (e.g., cyclicPrefix). For example, the subcarrier spacing may be one of 15 kHz, 30 kHz, 60 kHz, 120 kHz, 240 kHz, 480 kHz, and 960 kHz. For example, the cyclic prefix may be one of a normal cyclic prefix and an extended cyclic prefix.

For example, configuration parameters of the cell-specific downlink bandwidth (e.g., BWP-DownlinkCommon) may indicate/comprise genericParameters, pdcch-ConfigCommon, and/or pdsch-ConfigCommon. For example, pdcch-ConfigCommon may comprise cell-specific parameters for receiving downlink control information (DCIs) via the cell-specific downlink bandwidth part (e.g., an initial BWP). For example, pdsch-ConfigCommon may comprise cell-specific parameters for receiving PDSCHs of transport blocks (TBs) via the cell-specific downlink bandwidth part. Configuration parameters of the UE-specific downlink bandwidth part (e.g., BWP-DownlinkDedicated) may comprise pdcch-Config, pdsch-Config, sps-Config, and/or radioLinkMonitoringConfig (e.g., RLM-Config). The configuration parameters may comprise sps-ConfigList and/or beamFailureRecoverySCellConfig. For example, beamFailureRecoverySCellConfig may comprise reference signal parameters for beam failure recovery for secondary cells. For example, pdcch-Config may comprise parameters for receiving DCIs for the UE-specific downlink bandwidth part. For example, pdsch-Config may comprise parameters for receiving PDSCHs of TBs for the UE-specific downlink bandwidth part. For example, sps-Config may comprise parameters for receiving semi-persistent scheduling PDSCHs. The base station may configure a SPS for a BWP or a list of SPS for the BWP. For example, radioLinkMonitoringConfig may comprise parameters for radio link monitoring.

Configuration parameters of pdcch-Config may indicate/comprise at least one of a set of coresets, a set of search spaces, a downlink preemption (e.g., downlinkPreemption), a transmission power control (TPC) for PUSCH (e.g. tpc-PUSCH), a TPC for PUCCH and/or a TPC for SRS. The configuration parameters may comprise a list of search space switching groups (e.g., searchsSpaceSwitchingGroup), a search space switching timer (e.g., searchSpaceSwitchingTimer), an uplink cancellation, and/or a monitoring capability configuration (e.g., monitoringCapabilityConfig). The base station may configure the list of search space switching groups, where the wireless device may switch from a first search space group to a second search space group based on the search space switching timer or a rule, an indication, or an event. The base station may configure up to K (e.g., K=3) coresets for a BWP of a cell. The downlink preemption may indicate whether to monitor for a downlink preemption indication for the cell. The monitoring capability config may indicate whether a monitoring capability of the wireless device would be configured for the cell, where the capability is based on a basic capability or an advanced capability. The base station may configure up to M (e.g., M=10) search spaces for the BWP of the cell. The tpc-PUCCH, tpc-PUSCH, or tpc-SRS may enable and/or configure reception of TPC commands for PUCCH, PUSCH or SRS respectively. The uplink cancellation may indicate to monitor uplink cancellation for the cell.

Configuration parameters of pdcch-ConfigCommon may comprise a control resource set zero (e.g., controlResourceSetZero), a common control resource set (e.g., commonControlResourceSet), a search space zero (e.g., searchSpaceZero), a list of common search space (e.g., commonSearchSpaceList), a search space for SIB1 (e.g., searchSpaceSIB1), a search space for other SIBs (e.g., searchSpaceOtherSystemInformation), a search space for paging (e.g., pagingSearchSpace), a search space for random access (e.g., ra-SearchSpace), and/or a first PDCCH monitoring occasion. The control resource set zero may comprise parameters for a first coreset with an index value zero. The coreset zero may be configured for an initial bandwidth part of the cell. The wireless device may use the control resource set zero in a BWP of the cell, wherein the BWP is not the initial BWP of the cell based on one or more conditions. For example, a numerology of the BWP may be same as the numerology of the initial BWP. For example, the BWP may comprise the initial BWP. For example, the BWP may comprise the control resource set zero. The common control resource set may be an additional common coreset that may be used for a common search space (CSS) or a UE-specific search space (USS). The base station may configure a bandwidth of the common control resource set where the bandwidth is smaller than or equal to a bandwidth of the control resource set zero. The base station may configure the common control resource set such that it is contained within the control resource set zero (e.g., CORESET #0). The list of common search space may comprise one or more CSSs. The list of common search space may not comprise a search space with index zero (e.g., SS #0). The first PDCCH monitoring occasion may indicate monitoring occasion for paging occasion. The base station may configure a search space for monitoring DCIs for paging (e.g., pagingSearchSpace), for RAR monitoring (e.g., ra-SearchSpace), for SIB1 (e.g., searchSpaceSIB1) and/or for other SIBs than SIB1 (e.g., searchSpaceOtherSystemInformation). The search space with index zero (e.g., searchSpaceZero, SS #0) may be configured for the initial BWP of the cell. Similar to the coreset/CORESET #0, the SS #0 may be used in the BWP of the cell based on the one or more conditions.

FIG. 18 illustrates example configuration parameters for a wireless device to transmit control and/or data from a base station. A wireless device may receive one or more radio resource control (RRC) messages comprising configuration parameters of a cell. The configuration parameters may comprise one or more parameters of a serving cell configuration (e.g., ServingCellConfig). The one or more parameters of the serving cell configuration may comprise one or more downlink bandwidth parts (e.g., a list of BWP-Downlinks). The one or more parameters of the serving cell configuration may comprise one or more uplink bandwidth parts (e.g., a list of BWP-Uplinks). An uplink BWP may comprise a bandwidth part index (bwp-id), one or more common uplink BWPs (e.g., configured via SIB/MIB, BWP-UplinkCommon), and/or one or more dedicated uplink BWPs (e.g., configured via RRC signaling, BWP-UplinkDedcated).

For example, configuration parameters of a cell-specific uplink bandwidth (e.g., BWP-UplinkCommon) may indicate/comprise rach-ConfigCommon, pusch-ConfigCommon and pucch-ConfigCommon. For example, pucch-ConfigCommon may comprise cell-specific parameters for transmitting uplink control information (UCIs) via the cell-specific uplink bandwidth part (e.g., initial UL BWP). For example, pusch-ConfigCommon may comprise cell-specific parameters for transmitting PUSCHs of transport blocks (TBs) via the cell-specific uplink bandwidth part. Configuration parameters of the UE-specific uplink bandwidth part (e.g., BWP-UplinkDedicated) may comprise pucch-Config, pusch-Config, srs-Config. For example, pucch-Config may comprise one or more PUCCH resource sets, one or more PUCCH formats (format), one or more scheduling request (SR) resources, one or more values for an offset between a PDSCH to a PUCCH or a HARQ-ACK feedback corresponding to the PDSCH (e.g., dl-DataToUL-ACK), and/or spatial domain filter parameters (spatialRelationInfo).

In an example, a base station and a wireless device may use a plurality of downlink control information (DCI) formats to communicate control information to schedule downlink data and/or uplink data and/or to deliver control information. For example, a DCI format 0_0 may be used to schedule an uplink resource for a PUSCH over a cell. A DCI format 0_1 may be used to schedule one or more PUSCHs in one cell or may be used to indicate downlink feedback information for configured grant PUSCH (CG-DFI). A DCI format 0_2 may be used to schedule a resource for a PUSCH in one cell. Similarly, for downlink scheduling, a DCI format 1_0 may schedule a resource for a PDSCH in one cell. A DCI format 1_1 may be used to schedule a PDSCH in one cell or trigger one shot HARQ-ACK feedback. A DCI format 1_2 may be used to schedule a resource for a PDSCH in one cell. There are one or more DCI formats carrying non-scheduling information. For example, a DCI format 2_0 may be used to indicate a slot formation information for one or more slots of one or more cells. A DCI format 2_2 may be used to indicate one or more transmit power control commands for PUCCH and PUSCH. A DCI format 2_3 may be used to indicate one or more transmit power control for SRS. A DCI format 2_4 may be used to indicate an uplink cancellation information. A DCI format 2_5 may be used to indicate a preemption information. A DCI format 2_6 may be used to indicate a power saving state outside of DRX active time. A DCI format 3_0 or 3_1 may be used to schedule NR sidelink resource or LTE sidelink resource in one cell.

In an example, a DCI format 0_0 and a DCI format 1_0 may be referred as a fallback DCI format for scheduling uplink and downlink respectively. In an example, a DCI format 0_1 and a DCI format 1_1 may be referred as a non-fallback DCI format scheduling uplink and downlink respectively. In an example, a DCI format 0_2 and a DCI format 1_2 may be referred as a compact DCI format for scheduling uplink and downlink respectively. A base station may configure one or more DCI formats for scheduling downlink and/or uplink resources. For example, a DCI format 0_0, 0_1 and 0_2 may be used to schedule uplink resource(s) for one or more PUSCHs. A DCI format 1_0, 1_1 and 1_2 may be used to schedule downlink resource(s) for one or more PDSCHs. A DCI format 2_0, 2_1, 2_2, 2_3, 2_4, 2_5 and 2_6 may be used for a group-common DCI transmission. Each format of DCI format 2_x may be used for different information. For example, the DCI format 2_4 may be used to indicate uplink resources for a group of wireless devices. In response to receiving a DCI based on the DCI format 2_4, a wireless device may cancel any uplink resource, scheduled prior to the receiving, when the uplink resource may be overlapped with the indicated uplink resources.

A DCI format may comprise one or more DCI fields. A DCI field may have a DCI size. A wireless device may determine one or more bitfield sizes of one or more DCI fields of the DCI format based on one or more radio resource control (RRC) configuration parameters by a base station. For example, the one or more RRC configuration parameters may be transmitted via master information block (MIB). For example, the one or more RRC configuration parameters may be transmitted via system information blocks (SIBs). For example, the one or more RRC configuration parameters may be transmitted via one or more a wireless device specific messages. For example, the wireless device may determine one or more DCI sizes of one or more DCI fields of a DCI format 0_0 based on the one or more RRC configuration parameters transmitted via the MIB and/or the SIBs. The wireless device may be able to determine the one or more DCI sizes of the DCI format 0_0 without receiving any the wireless device specific message. Similarly, the wireless device may determine one or more DCI sizes of one or more second DCI fields of a DCI format 1_0 based on the one or more RRC configuration parameters transmitted via the MIB and/or the SIBs.

For example, the wireless device may determine one or more first DCI sizes of one or more first DCI fields of a DCI format 0_2 based on one or more RRC configuration parameters transmitted via the MIB and/or the SIBs and/or the wireless device specific RRC message(s). The wireless device may determine one or more bitfield sizes of the one or more first DCI fields based on the one or more RRC configuration parameters. For example, FIG. 19 may illustrate the one or more first DCI fields of the DCI format 0_2. In FIG. 19, there are one or more second DCI fields that may present in the DCI format 0_2 regardless of the wireless device specific RRC message(s). For example, the one or more second DCI fields may comprise at least one of DL/UL indicator, frequency domain resource allocation, MCS, NDI, and TPC fields. For example, the one or more first DCI fields may comprise the one or more second DCI fields and one or more third DCI fields. A DCI field of the one or more third DCI fields may be present or may not be present based on one or more configuration parameters transmitted by the base station. For example, the one or more third DCI fields may comprise at least one of a BWP index, RV, HARQ process #, PMI, antenna ports, and/or beta offset.

For example, the DCI format 0_2 may comprise a 1-bit DL/UL indicator where the bit is configured with zero (‘0’) to indicate an uplink grant for the DCI format 0_2. DCI field(s) shown in dotted boxes may not be present or a size of the DCI field(s) may be configured as zero. For example, a carrier indicator may be present when the DCI format 0_2 is used to schedule a cell based on cross-carrier scheduling. The carrier indicator may indicate a cell index of a scheduled cell by the cross-carrier scheduling. For example, UL/SUL indicator (shown UL/SUL in FIG. 19) may indicate whether a DCI based on the DCI format 0_2 schedules a resource for an uplink carrier or a supplemental uplink. The UL/SUL indicator field may be present when the wireless device is configured with a supplemental uplink for a scheduled cell of the DCI. Otherwise, the UL/SUL indicator field is not present.

A field of BWP index may indicate a bandwidth part indicator. The base station may transmit configuration parameters indicating one or more uplink BWPs for the scheduled cell. The wireless device may determine a bit size of the field of BWP index based on a number of the one or more uplink BWPs. For example, 1 bit may be used. The number of the one or more uplink BWPs (excluding an initial UL BWP) is two. The field of BWP index may be used to indicate an uplink BWP switching. The wireless device may switch to a first BWP in response to receiving the DCI indicating an index of the first BWP. The first BWP is different from an active uplink BWP (active before receiving the DCI).

A DCI field of frequency domain resource allocation (frequency domain RA in FIG. 19) may indicate uplink resource(s) of the scheduled cell. For example, the base station may transmit configuration parameters indicating a resource allocation type 0. With the resource allocation type 0, a bitmap over one or more resource block groups (RBGs) may schedule the uplink resource(s). With a resource allocation type 1, a starting PRB index and a length of the scheduled uplink resource(s) may be indicated. In an example, a length may be a multiple of K1 resource blocks. For example, the configuration parameters may comprise a resource allocation type1 granularity for the DCI format 0_2 (e.g., K1). A default value of the K1 may be one (‘1’). The base station may transmit configuration parameters indicating a dynamic change between the resource allocation type 0 and the resource allocation type 1 (e.g., ‘dynamicswitch’). The wireless device may determine a field size of the frequency domain RA field based on the configured resource allocation type and a bandwidth of an active UL BWP of the scheduled cell. The wireless device may further determine the field size of the frequency domain RA field based on the K1 value, when the resource allocation type 1 may be used/configured. For example, when the resource allocation type 0 is configured, the bitmap may indicate each of the one or more RBGs covering the bandwidth of the active UL BWP. A size of the bitmap may be determined based on a number of the one or more RBGs of the active UL BWP. For example, the wireless device may determine the size of the frequency domain RA field based on the resource allocation type 1 based on the bandwidth of the active uplink BWP (e.g., ceil (log 2(BW/K1(BW/K1+1)/2) and the resource allocation type1 granularity. E.g., the BW is the bandwidth of the active uplink BWP. E.g., the K1 is the resource allocation type1 granularity).

The wireless device may determine a resource allocation indicator value (RIV) table, where an entry of the table may comprise a starting PRB index and a length value. The wireless device may determine the RIV table based on the resource allocation type1 granularity. For example, when the dynamic change between the resource allocation type 0 and the resource allocation type 1 is used, a larger size between a first size based on the resource allocation type 0 (e.g., the bitmap size) and a second size based on the resource allocation type 1 (e.g., the RIV table size) with additional 1 bit indication to indicate either the resource allocation type 0 or the resource allocation type 1. For example, the frequency domain RA field may indicate a frequency hopping offset. The base station may use K (e.g., 1 bit for two offset values, 2 bits for up to four offset values) bit(s) to indicate the frequency hopping offset from one or more configured offset values, based on the resource allocation type 1. The base station may use ceil(log 2(BW/K1(BW/K1+1)/2)—K bits to indicate the uplink resource(s) based on the resource allocation type 1, when frequency hopping is enabled. Otherwise, the base station/wireless device may use ceil(log 2(BW/K1(BW/K1+1)/2) bits to indicate the uplink resource(s) based on the resource allocation type 1.

In an example, a base station may transmit one or more messages comprising configuration parameters of a BWP of a cell. The configuration parameters may indicate/comprise a resource allocation type for one or more PUSCHs scheduled by one or more DCIs, based on a first RNTI. The resource allocation type may be a resource allocation type 0 or a resource allocation type 1 or a dynamic switching between the resource allocation type 0 and the resource allocation type 1. For example, the first RNTI is a C-RNTI. The configuration parameters may indicate/comprise a configured grant configuration or a SPS configuration. The configuration parameters may indicate a resource allocation type for the configured grant configuration or the SPS configuration. The resource allocation type may be a resource allocation type 0 or a resource allocation type 1 or a dynamic switching between the resource allocation type 0 and the resource allocation type 1.

A DCI field of time domain resource allocation (time domain RA shown in FIG. 19) may indicate time domain resource of one or more slots of the scheduled cell. The base station may transmit configuration parameters indicating one or more time domain resource allocation lists of a time domain resource allocation table for an uplink BWP of the scheduled cell. The wireless device may determine a bit size of the time domain RA field based on a number of the one or more time domain resource allocation lists of the time domain resource allocation table. The base station may indicate a frequency hopping flag by a FH flag (shown as FH in FIG. 19). For example, the FH flag may present when the base station may enable a frequency hopping of the scheduled cell or the active UL BWP of the scheduled cell. A DCI field of modulation and coding scheme (MCS) (shown as MCS in FIG. 19) may indicate a coding rate and a modulation scheme for the scheduled uplink data. In an example, a bit size of the MCS field may be predetermined as a constant (e.g., 5 bits). A new data indicator (NDI) field may indicate whether the DCI schedules the uplink resource(s) for a new/initial transmission or a retransmission. A bit size of the NDI may be fixed as a constant value (e.g., 1 bit). A redundancy version (RV) field may indicate one or more RV values (e.g., a RV value may be 0, 2, 3, or 1) for one or more PUSCHs scheduled over the one or more slots of the scheduled cells. For example, the DCI may schedule a single PUSCH via one slot, a RV value is indicated. For example, the DCI may schedule two PUSCHs via two slots, two RV values may be indicated. A number of PUSCHs scheduled by a DCI may be indicated in a time domain resource allocation list of the one or more time domain resource allocation lists. The configuration parameters may indicate/comprise a bit size of the RV field. For example, the bit size may be 0, 1 or 2 bits for a single PUSCH. When the bit size is configured as zero (‘0’), the wireless device may apply a RV=0 for any uplink resource scheduled by a DCI based on the DCI format 0_2.

A DCI field of hybrid automatic repeat request (HARQ) process number (HARQ process # in FIG. 19) may indicate an index of a HARQ process used for the one or more PUSCHs. The wireless device may determine one or more HARQ processes for the one or more PUSCHs based on the index of the HARQ process. The wireless device may determine the index for a first HARQ process of a first PUSCH of the one or more PUSCHs and select a next index as a second HARQ process of a second PUSCH of the one or more PUSCHs and so on. The configuration parameters may indicate/comprise a bit size for the HARQ process # field. For example, the bit size may be 0, 1, 2, 3 or 4 bits for a single PUSCH. The wireless device may assume that a HARQ process index=0 in case the bit size is configured as zero. The wireless device may assume that a HARQ process index in a range of [0, 1] when the bit size is configured as one. The wireless device may assume that a HARQ process index in a range of [0, . . . , 3] when the bit size is configured as two. The wireless device may assume that a HARQ process index in a range of [0, . . . , 7] when the bit size is configured as three. For the 4 bits of bit size, the wireless device may use a HARQ process in a range of [0, . . . , 15].

The DCI format 0_2 may have a first downlink assignment index (1st DAI) and/or a second DAI (2nd DAI). The configuration parameters may indicate/comprise a parameter to indicate whether to use DAI for the DCI format 0_2 (e.g., Downlinkassignmentindex-ForDCIFormat0_2). The first DAI may be used to indicate a first size of bits of first HARQ-ACK codebook group. The second DAI may be present when the base station may transmit configuration parameters indicating a plurality of HARQ-ACK codebook groups. When there is no HARQ-ACK codebook group configured, the wireless device may assume the first HARQ-ACK codebook group only. The second DAI may indicate a second size of bits of second HARQ-ACK codebook group. The first DAI may be 1 bit when a semi-static HARQ-ACK codebook generation mechanism is used. The first DAI may be 2 bits or 4 bits when a dynamic HARQ-ACK codebook generation mechanism is used.

A field of transmission power control (TPC shown in FIG. 19) may indicate a power offset value to adjust transmission power of the one or more scheduled PUSCHs. A field of sounding reference signal (SRS) resource indicator (SRI) may indicate an index of one or more configured SRS resources of an SRS resource set. A field of precoding information and number of layers (shown as PMI in FIG. 19) may indicate a precoding and a MIMO layer information for the one or more scheduled PUSCHs. A field of antenna ports may indicate DMRS pattern(s) for the one or more scheduled PUSCHs. A field of SRS request may indicate to trigger a SRS transmission of a SRS resource or skip SRS transmission. A field of CSI request may indicate to trigger a CSI feedback based on a CSI-RS configuration or skip CSI feedback. A field of phase tracking reference signal (PTRS)-demodulation reference signal (DMRS) association (shown as PTRS in FIG. 19) may indicate an association between one or more ports of PTRS and one or more ports of DM-RS. The one or more ports may be indicated in the field of antenna ports. A field of beta_offset indicator (beta offset in FIG. 19) may indicate a code rate for transmission of uplink control information (UCI) via a PUSCH of the one or more scheduled PUSCHs. A field of DM-RS sequence initialization (shown as DMRS in FIG. 19) may present based on a configuration of transform precoding. A field of UL-SCH indicator (UL-SCH) may indicate whether a UCI may be transmitted via a PUSCH of the one or more scheduled PUSCHs or not. A field of open loop power control parameter set indication (open loop power in FIG. 19) may indicate a set of power control configuration parameters. The wireless device is configured with one or more sets of power control configuration parameters. A field of priority indicator (priority) may indicate a priority value of the one or more scheduled PUSCHs. A field of invalid symbol pattern indicator (invalid OS) may indicate one or more unavailable/not-available OFDM symbols to be used for the one or more scheduled PUSCHs.

Note that additional DCI field(s), although not shown in FIG. 19, may be present for the DCI format 0_2. For example, a downlink feedback information (DFI) field indicating for one or more configured grant resources may present for an unlicensed/shared spectrum cell. For example, the unlicensed/shared spectrum cell is a scheduled cell. When the DCI format 0_2 is used for indicating downlink feedback information for the one or more configured grant resources, other DCI fields may be used to indicate a HARQ-ACK bitmap for the one or more configured grant resources and TPC commands for a scheduled PUSCH. Remaining bits may be reserved and filled with zeros (‘0’s).

The DCI format 1_2 may schedule a downlink resource for a scheduled downlink cell. The DCI format 1_2 may comprise one or more DCI fields such as an identifier for DCI formats (DL/UL), a carrier indicator, bandwidth part indicator (BWP index), a frequency domain resource assignment (frequency domain RA), a time domain resource assignment (time domain RA), a virtual resource block to physical resource block mapping (VRB-PRB), Physical resource block (PRB) bundling size indicator (PRB bundle), rate matching indicator (rate matching), zero power CSI-RS (ZP-CSI), a MCS, a NDI, a RV, a HARQ process number, a downlink assignment index (DAI), a TPC command for a PUCCH, a PUCCH resource indicator (PUCCH-RI), a PDSCH-to-HARQ feedback timing indicator (PDSCH-to-HARQ), an antenna ports, a transmission configuration indication (TCI), a SRS request, DMRS sequence initialization (DMRS), and a priority indicator (priority).

The base station may transmit one or more messages indicating configuration parameters for the DCI format 1_2. Similar to the DCI format 0_2 of FIG. 19, one or more DCI fields shown in dotted lined boxes may be present or may not be present based on the configuration parameters. The configuration parameters may indicate/comprise one or more DCI bit sizes and/or related configuration parameters/values for the one or more DCI fields.

For example, the VRB-PRB field may indicate whether a mapping is based on a virtual RB or a physical RB. For example, the PRB bundle may indicate a size of PRB bundle when a dynamic PRB bundling is enabled. For example, the rate matching may indicate one or more rate matching resources where the scheduled data may be mapped around based on the rate matching. For example, the ZP-CSI field may indicate a number of aperiodic ZP CSI-RS resource sets configured by the base station. For example, the DCI format 1_2 may also include MCS, NDI and RV for a second transport block, in response to a max number of codewords scheduled by DCI may be configured as two. The DCI format 1_2 may not include MCS, NDI and RV field for the second transport block. For example, the DAI field may indicate a size of bits of HARQ-ACK codebook. The TPC field may indicate a power offset for the scheduled PUCCH. The wireless device may transmit the scheduled PUCCH comprising HARQ-ACK bit(s) of the scheduled downlink data by the DCI. The PUCCH-RI may indicate a PUCCH resource of one or more PUCCH resources configured by the base station. The PDSCH-to-HARQ field may indicate a timing offset between an end of a scheduled PDSCH by the DCI and a starting of the scheduled PUCCH. The field of antenna ports may indicate DMRS patterns for the scheduled PDSCH. The TCI field may indicate a TCI code point of one or more active TCI code points/active TCI states. The base station may transmit configuration parameters indicating one or more TCI states for the scheduled cell. The base station may active one or more second TCI states of the one or more TCI states via one or more MAC CEs/DCIs. The wireless device may map an active TCI code point of the one or more active TCI code points to an active TCI of the one or more second TCI states.

In an example, two downlink resource allocation schemes, type 0 and type 1, are supported. A wireless device may determine a frequency domain resource based on a DCI based on a fallback DCI format such as DCI format 0_1 based on a resource allocation type 1. A base station may transmit configuration parameters indicating a dynamic switch between the type 0 and the type 1 resource allocation via an indication in a DCI. The configuration parameters may comprise ‘dynamicswitch’ to enable dynamic switching between the type 0 and the type 1 via the DCI. The dynamic switching may be supported for a DCI based on a non-fallback DCI format such as DCI format 1_1 or DCI format 1_2. The configuration parameters may comprise/indicate either the type 0 or the type 1 as a resource allocation type via an RRC signaling. The wireless device may determine a frequency domain resource based on a DCI based on the resource allocation configured via the RRC signaling, in response to ‘dynamicswitch’ being not configured. The wireless device may determine a frequency domain resource based on a frequency domain resource assignment field of a DCI based on an active downlink BWP of a cell. The cell is a scheduled cell. The DCI may indicate a BWP index. The wireless device may determine the frequency domain resource based on one or more configuration parameters of an indicated BWP by the BWP index. For a PDSCH scheduled with a DCI based on a fallback DCI format (e.g., DCI format 1_0) via any common search space, a RB numbering, to determine a frequency domain resource, may start from a lowest RB of a coreset. For example, the DCI has been received via the coreset. In other cases, the RB numbering may start from a lowest RB of an active BWP of the scheduled cell.

For example, a resource allocation type 0 may use a bitmap to indicate a frequency domain resource. The bitmap may indicate one or more resource block groups (RBGs) that may allocate the frequency domain resource. One RBG may represent a set of consecutive virtual resource blocks defined by a rgb-Size. For example, the rbg-Size may be indicated as a parameter of a PDSCH-Config under a servingCellConfig. For example, the rbg-Size may be determined based on a parameter of ‘Configuration 1’ or ‘Configuration 2’ and a bandwidth of an active BWP of a scheduled cell. For example, when the bandwidth of the active BWP is between 1 to 36 RBs, ‘Configuration 1’ indicates the rbg-Size of 2 and ‘Configuration 2’ indicates the rbg-Size of 4. For example, when the bandwidth of the active BWP is between 37 to 72 RBs, ‘Configuration 1’ indicates the rbg-Size of 4 and ‘Configuration 2’ indicates the rbg-Size of 8. For example, when the bandwidth of the active BWP is between 73 to 144 RBs, ‘Configuration 1’ indicates the rbg-Size of 8 and ‘Configuration 2’ indicates the rbg-Size of 16. For example, when the bandwidth of the active BWP is between 145 to 275 (or 550) RBs, ‘Configuration 1’ indicates the rbg-Size of 16 and ‘Configuration 2’ indicates the rbg-Size of 16. A number of RBGs (N_RBG) for a downlink BWP may present. A DCI field size of a frequency domain resource allocation based on the resource allocation type 0 would be ceil (N_RBG+(N_start_BWP mode P))/P) where a size of a first RBG is P−N_start_BWP mode P, a size of a last RBG is (N_start_BWP+bandwidth) mode P wherein is (N_start_BWP+bandwidth) mode P is greater than zero, a size of other RBGs are P, and P is the rbg-Size. The bitmap of N_RBG bits with one bitmap bit per a corresponding RBG, such that the corresponding RBG may be scheduled. The one or more RBGs may be indexed in an order of increasing frequency, and indexing may start from a lowest frequency of the active BWP. The order of the bitmap may be determined such that RBG #0 to RBG #N_RBG−1 may be mapped to most significant bit to least significant bit of the bitmap. The wireless device may assume an RBG is allocated in response to a corresponding bit of the bitmap being allocated/assigned as 1. The wireless device may assume a second RBG is not allocated in response to a corresponding bit of the bitmap being allocated/assigned as 0.

When a virtual RB to a physical RB mapping is enabled, the wireless device may determine one or more physical RBGs based on the indicated bitmap for the virtual RBGs. Otherwise, the indicated bitmap may determine the one or more physical RBGs.

For example, a resource allocation type 1, a frequency domain resource allocation may indicate a set of contiguously allocated non-interleaved or interleaved virtual resource blocks within an active bandwidth part of a scheduled cell. For example, a DCI may be scheduled via a USS. The frequency domain resource allocation field based on the resource allocation type 1 may use a resource allocation value (RIV). The RIV may indicate a starting virtual RB (RB_start) and a length in terms of contiguously allocated virtual RBs (L_rbs). The RIV value may be determined as the RIV=bandwidth (L_rbs−1)+RB_start when (L_rbs−1) is smaller than or equal to floor (bandwidth/2), or the RIV=bandwidth (bandwidth−L_rbs+1)+(bandwidth−1−RB_start) otherwise. The bandwidth may represent a bandwidth of the active BWP.

A base station may enable a PRB bundling. A wireless device may assume a same precoding over a number RBs of the PRB bundle (e.g., two PRBs, four PRBs or the bandwidth). The base station may schedule the PRB bundle or not, and may not schedule partial PRB bundle to the wireless device.

Similar to downlink, for an uplink transmission, a few resource allocation types are supported. For the uplink transmission, a resource allocation type 0, resource allocation type 1 or resource allocation type 2 may be supported. The resource allocation type 0 may be used in response to a transform precoding being disabled. The resource allocation type 1 or the resource allocation type 2 may be used in response to the transform precoding being enabled or being disabled. For the uplink transmission, a ‘dynamicswitch’ may be configured. In response to the ‘dynamicswitch’, the wireless device may switch between the resource allocation type 0 and the resource allocation type 1 based on a DCI. The base station may configure a resource allocation type via an RRC signaling in response to the ‘dynamicswitch’ being not configured/enabled. The resource allocation type 2 may be used in response to an interlaced PUSCH being enabled. The wireless device may apply the resource allocation type 1 for a DCI based on a fallback DCI format such as a DCI format 0_0. The interlaced PUSCH is disabled for the fallback DCI format. When the interlaced PUSCH is enabled, the wireless device may apply the resource allocation type 2 for the DCI. The wireless device may determine a frequency domain resource based on a frequency domain resource allocation field of a DCI based on an active uplink BWP of a scheduled cell. The DCI may not comprise a BWP index. The wireless device may determine the frequency domain resource based on an indicated BWP by a BWP index when the DCI comprises the BWP index.

In an example, a resource allocation type 0 for an uplink transmission may use a bitmap indicating one or more RBGs within an active UL BWP of a scheduled cell. One RBG may represent a set of consecutive virtual resource blocks defined by a rbg-Size. The rbg-Size may be indicated as a parameter of a PYSCH-Config under a servingCellConfig. For example, the rbg-Size may be determined based on a parameter of ‘Configuration 1’ or ‘Configuration 2’ and a bandwidth of an active UL BWP of a scheduled cell. For example, when the bandwidth of the active UL BWP is between 1 to 36 RBs, ‘Configuration 1’ indicates the rbg-Size of 2 and ‘Configuration 2’ indicates the rbg-Size of 4. For example, when the bandwidth of the active UL BWP is between 37 to 72 RBs, ‘Configuration 1’ indicates the rbg-Size of 4 and ‘Configuration 2’ indicates the rbg-Size of 8. For example, when the bandwidth of the active UL BWP is between 73 to 144 RBs, ‘Configuration 1’ indicates the rbg-Size of 8 and ‘Configuration 2’ indicates the rbg-Size of 16. For example, when the bandwidth of the active UL BWP is between 145 to 275 (or 550) RBs, ‘Configuration 1’ indicates the rbg-Size of 16 and ‘Configuration 2’ indicates the rbg-Size of 16. A number of RBGs (N_RBG) for a uplink BWP may present. Determination of a bit of the bitmap of the uplink resource allocation type 1 is same as that of the downlink resource allocation type 1. In frequency range 1 (e.g., below 7 GHz), almost contiguous allocation may be supported. In frequency range 2 (e.g., above 7 GHz and below 52.6 GHz), contiguous resource allocation may be supported.

The resource allocation type 0 for an uplink transmission may follow similar procedure to the resource allocation type 0 for an downlink transmission.

The resource allocation type 2 may be used to indicate an interlaced resource allocation, wherein M is a number of interlaces. For example, a frequency domain resource allocation field may comprise a RIV. For the RIV between 0 and M (M+1)/2 (e.g., 0<=RIV<M(M+1)/2), the RIV may indicate a starting interlace index m_0 and a number of contiguous interlace indices L (L>=1). For example, when (L−1)<=floor (M/2), the RIV may define M (L−1)+m_0. Otherwise, the RIV may define M (M−L+1)+(M−1−m_0). For the RIV larger than or equal to M(M+1)/2 (e.g., RIV>=M(M+1)/2), the RIV may indicate a starting interlace index m_0 and a set of values 1 based on one or more set of values. For example, an entry may represent {RIV-M(M+1)/2, m_0, 1}. For example, the one or more set of values may comprise {0, 0, {0, 5}}, {1, 0, {0, 1, 5, 6}}, {2, 1, {0, 5}}, {3, 1, {0, 1, 3, 5, 6, 7, 8}}, {4, 2, {0, 5}}, {5, 2, {0, 1, 2, 5, 6, 7}}, {6, 3, {0, 5}}, and/or {7, 4, {0, 5}}.

Resource allocation type and mechanism based on a DCI may be also applied to a configured grant configuration or semi-persistent scheduling configuration.

In an example, a base station may transmit a DCI. The DCI may comprise a time domain resource allocation field. A value of the time domain resource allocation field (e.g., m) may indicate a row index m+1 of a time domain resource allocation lists/a time domain resource allocation table. The base station may transmit configuration parameters indicating one or more time domain resource allocation tables. For example, a first time domain resource allocation table may be used for a fallback DCI format scheduled via a CSS. For example, a second time domain resource allocation table may be used for a fallback DCI format and/or a non-fallback DCI format via a USS. The wireless device may determine a time domain resource allocation table from the one or more time domain resource allocation tables for the DCI in response to receiving the DCI. The configuration parameters may comprise one or more time domain resource allocation entries for a time domain resource allocation table. One time domain resource allocation entry may comprise a starting and a length indicator value (SLIV), a PUSCH mapping type, and K2 value. The K2 may represent a scheduling offset between a scheduling DCI of a PUSCH and a starting slot index of the PUSCH. The one time domain resource allocation (TDRA) entry may comprise a repetition number (numberOfRepetitions). The one TDRA entry may comprise a starting symbol (startSymbol) and a length addition to the SLIV. For a PUSCH, scheduled by a non-fallback DCI format such as DCI format 0_1, a base station may transmit, to a wireless device, configuration parameters indicating PUSCHRepTypeIndicaor-ForDCIFormat0_1 to ‘puschRepTypeB’ indicating a repetition type B. In response to being configured with ‘puschRepTypeB’, the wireless device may determine a resource based on a procedure for the repetition type B and a time domain resource allocation field of a DCI based on the DCI format 0_1. Similarly, the configuration parameters may comprise PUSCHRepTypeIndicator-ForDCIformat0_2 to ‘puschRepTypeB’ to apply the repetition type B for a second DCI based on a DCI format 0_2. When the base station may not configure PUSCHRepTypeIndicaor-ForDCIFormat0_1 indicating ‘puschRepTypeB’, the wireless device may determine a time domain resource based on a DCI based on a repetition type A.

For example, when the repetition type A is configured/enabled, the wireless device may determine a starting symbol S in a starting slot and a number of consecutive symbols L from the starting symbol S based on a SLIV value. For example, the SLIV value may define SLIV=14*(L−1)+S when (L−1) is smaller than or equal to 7 (half slot based on a normal CP). The SLF value may define SLIV=14*(14−L+1)+(14−1−S) when (L−1) is larger than 7. For example, L would be greater than 0, and may be smaller than or equal to 14−S. In an uplink BWP with an extended CP, 12 OFDM symbols may be assumed for a slot. A SLIV value may be determined by 12*(L−1)+S or 12*(12−L+1)+(14−1−S) respectively based on L−1 being smaller than/equal to 6 or larger than 6. For the repetition type A, the configuration parameters may comprise/indicate a TypeA or Type B for a PUSCH mapping type. For example, the base station may determine a first OFDM symbol comprising a DM-RS based on a fixed location (e.g., a first symbol of a slot) when the TypeA is configured for the PUSCH mapping type. For example, the base station may determine a first OFDM symbol comprising a DM-RS based on a starting OFDM symbol of the PUSCH in response to the typeB being configured for the PUSCH mapping type.

For example, when the repetition type B is configured/enabled, the wireless device may determine a starting OFDM symbol S in a starting slot, and a number of consecutive OFDM symbols L based on a row of a time domain resource allocation table. For example, the row of the time domain resource allocation table may comprise startSymbol for the starting OFDM symbol S and length for the number of consecutive OFDM symbols L. For the repetition type B, the wireless device may assume that the TypeB is configured for the PUSCH mapping type. For example, when a TypeA is configured for a PUSCH mapping type, a staring OFDM symbol S, a length L, and S+L may represent one or more values. For example, {S, L, S+L} may be {0, {4, . . . , 14}, {4, . . . , 14} } for a normal CP, and {0, {4, . . . , 12}, {4, . . . , 12} } for an extended CP. When a TypeB is configured for the PUSCH mapping type, {S, L, S+L} may be {{0, . . . , 13}, {1, . . . , 14}, {1, . . . , 14} for a repetition type A, {1, . . . , 27} fora repetition type B} for the normal CP, and {{0, . . . , 11}, {1, . . . , 12}, {1, . . . , 12} } for the extended CP.

For a repetition type A, a wireless device may determine a repetition number K based on a row of a time domain resource allocation table. The row may comprise a number of repetitions. The wireless device may determine based on an RRC parameter, ‘pusch-AggregationFactor’ when the row may not comprise the number of repetitions. The wireless device may determine a single transmission based on the row may not comprise the number of repetitions nor the ‘pusch-AggregationFactor’ is not configured. The wireless device may determine the single transmission for a PUSCH scheduled by a fallback DCI such as a DCI format 0_0.

For a repetition type A with a repetition number K being larger than 1, a wireless device may apply a starting OFDM symbol S and a length L in a slot across K consecutive slots based on a single transmission layer. The wireless device may repeat a TB across the K consecutive slots applying same OFDM symbols in each slot. A redundancy version (RV) applied on a i-th transmission of the K consecutive slots may be determined based on a repetition type. For example, when a RV value indicated by a DCI is 0, a second RV value for i-th transmission occasion (when a repetition type A is configured) or i-th actual repetition (when a repetition type B is configured) may be determined as 0 for i mod 4=0, 2 for i mod 4=1, 3 for i mod 4=2, 4 for i mod 4=3. When the RV value is 2, the second RV value may be determined as 2 for i mod 4=0, 3 for i mod 4=1, 1 for i mod 4=2, 0 for i mod 4=3. When the RV value is 3, the second RV value may be determined as 3 for i mod 4=0, 1 for i mod 4=1, 0 for i mod 4=2, 0 for i mod 4=2. When the RV value is 1, the second RV value may be determined as 1 for i mod 4=0, 0 for i mod 4=1, 2 for i mod 4=2, 3 for i mod 4=3.

For a repetition type A, a PUSCH transmission of a slot over a plurality of slots may be omitted when the slot may not have a sufficient number of uplink OFDM symbols for the PUSCH transmission. For a repetition type B, a wireless device may determine one or more slots for a number of nominal repetition number N. For a i-th nominal repetition, wherein i is 0, . . . , N−1, wherein N may be configured by a base station via an RRC signaling or a time domain resource allocation of a DCI. The wireless device may determine a slot. The i-th nominal repetition may start, wherein a slot index would be Ks+floor ((S+iL)/N_slot_symbol), and a starting symbol in the slot may be given by mod (S+iL, N_slot_symbol). The N_slot_symbol may be 14 with a normal CP and 12 with an extended CP. The S may represent a starting OFDM symbol indicated by a time domain resource allocation field of a DCI and L may represent a length indicated by the time domain resource allocation field of the DCI. The wireless device may determine a second slot wherein the i-th nominal repetition may end wherein a second slot index of the second slot may be determined as Ks+floor ((S+(i+1)*L−1)/N_slot_symbol), and an ending symbol in the second slot may be determined as mod (S+(i+1)*L−1, N_slot_symbol). The Ks may be determined as a starting slot indicated by the time domain resource allocation field of the DCI.

When the wireless device is configured with the repetition type B, the wireless device may determine invalid OFDM symbol for PUSCH repetitions based on a tdd-UL-DL-ConfigurationCommon/a tdd-UL-DL-ConfigurationDedicated and/or an InvalidSymbolPattern indicated by an RRC signaling. For example, the wireless device may determine a downlink symbol based on the tdd-UL-DL-ConfigurationCommon or the tdd-UL-DL-ConfigurationDedicated as an invalid OFDM symbol for the repetition type B. The base station may transmit the InvalidSymbolPattern, a bitmap of OFDM symbols over one slot or two slots. A bit of the bitmap may indicate ‘1’ to invalidate a corresponding OFDM symbol. The base station may further configure periodicityAndPattern. A bit of the periodicityAndPattern may correspond to a unit equal to a duration of the bitmap of the InvalidSymbolPattern. The wireless device may determine invalid OFDM symbol(s) based on the InvalidSymbolPattern and the periodicityAndPattern. For example, when a PUSCH is scheduled/activated by a non-fallback DCI format such as a DCI format 0_1/0_2 and InvalidSymbolPatternIndicator-ForDCIFormat0_1/0_2 is configured, a invalid symbol pattern indicator field may indicate 1, the wireless device may apply an invalid symbol pattern (e.g., InvalidSymbolPattern). Otherwise, the wireless device may not apply the invalid symbol pattern. When the InvalidSymbolPatternIndicator-ForDCIFormat0_1/0_2 is not configured, the wireless device may not apply the invalid symbol pattern. The wireless device may determine remaining OFDM symbols. The remaining OFDM symbols may not comprise invalid OFDM symbol(s), the wireless device may consider the remaining OFDM symbols as valid OFDM symbols. When there is a sufficient number of valid OFDM symbols in a slot to transmit a PUSCH based on a scheduling DCI, the wireless device may determine an actual repetition of a slot wherein the slot may have consecutive sufficient valid consecutive OFDM symbols. The wireless device may skip the actual repetition based on a slot formation indication. The wireless device may apply a redundancy version based on the actual repetition.

In an example, a row of a time domain resource allocation may comprise one or more resource assignments for one or more contiguous PUSCHs. A K2 of the row may indicate a first PSCH of the one or more contiguous PUSCHs. Each PUSCH of the one or more contiguous PUSCHs may be indicated/scheduled with a separate SLIV value and a PUSCH mapping type.

FIGS. 20A and 20B illustrate an examples of typeA repetition for an uplink transmission as per an aspect of an example embodiment of the present disclosure. FIG. 20A illustrates a TypeA PUSCH mapping type for a PUSCH repetition. FIG. 20B illustrates a TypeA PUCCH mapping type for a PUCCH repetition. TypeA repetition may be called as a slot aggregation.

For example, FIG. 20A and FIG. 20B illustrate four instances of repetition. The wireless device may determine four PUSCHs (in FIG. 20A) or four PUCCHs (in FIG. 20B), where a set of OFDM symbols in each slot of four slots is identical. For example, slot n+2 may be a downlink slot. The wireless device may drop a third PUSCH in the slot n+2.

The wireless device may not transmit the third PUSCH in response to dropping the third PUSCH. The wireless device may put zero power on resources of the third PUSCH in response to dropping the third PUSCH. The wireless device may cancel the third PUSCH in response to dropping the third PUSCH.

For example, the wireless device may determine a slot to drop a repetition of a PUSCH in response to corresponding resources of the PUSCH in the slot overlapping with downlink symbol(s). The wireless device may postpone transmission of a PUCCH in the slot n+3. The wireless device may determine a third repetition of a PUCCH in the slot n+3 in FIG. 20B based on postponing. The wireless device may determine one or more slots of a PUCCH repetition based on slot formation information in an unpaired spectrum. The wireless device may determine one or more slots of a PUCCH repetition based on consecutive slots in a faired spectrum.

A resource in each slot may be referred as a PUSCH resource of the slot or a PUCCH resource of the slot. The resource in each slot may be identical in a time domain (e.g., a same set of OFDM symbols in a slot) and may or may not be same in a frequency domain based on a hopping pattern. For example, when hopping is not used/enabled, the resource may be identical in each slot in the frequency domain. When hoping is enabled/used, the resource may be different (based on a hopping offset) in each slot. FIG. 20 illustrates that symbols [3-14] are allocated for PUSCH repetitions and/or PUCCH repetitions in each slot.

FIG. 21 illustrates an example of typeB repetition for an uplink transmission as per an aspect of an example embodiment of the present disclosure. FIG. 21A illustrates a TypeB PUSCH mapping type for a PUSCH repetition. FIG. 21B illustrates a TypeB PUCCH mapping type for a PUCCH repetition. TypeB repetition may be called as an enhanced uplink repetition.

For example, FIG. 21A and FIG. 21B illustrate four instances of nominal repetition. The wireless device may determine four nominal PUSCHs (PUSCH #1, PUSCH #2, PUSCH #3, and PUSCH #4 in FIG. 21A) or four nominal PUCCHs (PUCCH #1, PUCCH #2, PUCCH #3, and PUCCH #4 in FIG. 21B), where a number of OFDM symbols in each nominal repetition may be identical. A nominal PUSCH may refer to a reference PUSCH determined based on a resource allocation (e.g., based on a TDRA entry of a TDRA table). The nominal PUSCH may be used for determining a transport block size (TBS) and/or a DM-RS pattern. A first nominal repetition may be determined based on resource assignment(s) of a scheduling DCI (e.g., uplink grant) or a downlink scheduling DCI indicating a PUCCH resource. For example, an uplink grant may indicate a starting symbol and a duration for the first nominal repetition. For example, a downlink scheduling DCI may indicate a PUCCH resource for the first nominal repetition.

Within each nominal repetition, the wireless device may determine one or more actual repetition (if any). For example, the wireless device may not determine any actual repetition in a slot n+3 wherein the slot n+3 is a downlink slot. For an uplink signal transmission, a downlink slot or downlink resources may be considered as unavailable resources. The wireless device may be indicated with unavailable resources dynamically via a DCI and/or MAC CE. The wireless device may determine unavailable resources based on slot formation information based on RRC configuration parameters such as tdd-UL-DL-ConfigurationCommon/a tdd-UL-DL-ConfigurationDedicated.

In a first nominal PUSCH repetition or PUCCH repetition (PUSCH #1 or PUCCH #1), the wireless device may determine two actual repetitions (#1 and #2). The wireless device may determine to end an actual repetition in response to a slot boundary or an unavailable symbol. The wireless device may determine three actual repetitions for a second PUSCH.

In FIG. 21A, the wireless device may determine two actual PUSCH repetitions (e.g., #1 and #2 overlapping with PUSCH #1) based on a slot boundary between a slot n and a slot n+1. The wireless device may split PUSCH #1 to a first actual transmission (#1) and a second actual transmission (#2).

In FIG. 21A, the wireless device may determine two OFDM symbols of the slot n+1 are unknown or unavailable or downlink resources. The wireless device may determine the two OFDM symbols based on an uplink grant for the PUSCH repetition. The wireless device may determine the two OFDM symbols based on a slot formation information (e.g., SFI indicator). The wireless device may determine the two OFDM symbols based on a RRC configuration.

The wireless device may split (e.g., divide into) a first actual repetition (#1) of the second nominal repetition and a second actual repetition (#2) of the second nominal repetition around the two OFDM symbols. The wireless device may divide the second nominal repetition into two actual repetitions (#1 and #2). The wireless device may transmit a first PUSCH via the first actual repetition and a second PUSCH via the second actual repetition. The wireless device may determine a TBS of a transport block based on the second nominal repetition. The wireless device may determine a DM-RS of the first PUSCH and the second PUSCH based on the second nominal repetition. The first PUSCH and the second PUSCH may comprise repetition of the transport block.

In an example, a nominal PUSCH may refer to a reference PUSCH. An actual PUSCH may refer a PUSCH used for a transmission. The wireless device may determine a TBS of a transport block and a DM-RS pattern based on the nominal PUSCH. The wireless device may map data via resources of the actual PUSCH.

The two OFDM symbols may be indicated by a scheduling uplink grant. The first actual repletion (#1) and the second actual repetition (#2) are overlapping with a PUSCH #2. The wireless device may further determine a third actual repetition (#3) overlapping with PUSCH #2 based on a slot boundary between the slot n+1 and a slot n+2. Nominal PUSCH #2 may be divided to three actual repetitions based on unavailable symbols and/or slot boundary.

In FIG. 21A, the wireless device may determine two actual repetition of a third nominal repetition (PUSCH #3) based on unavailable/downlink OFDM symbols in the middle of slot n+2. The wireless device may determine one actual repetition of a fourth nominal repetition, which may be dropped due to the slot n+3 being a downlink slot.

In FIG. 21B, the wireless device may determine two actual repetitions for a first PUCCH nominal repetition (PUSCH #1) due to a slot boundary between slot n and slot n+1, one actual repetition for a second PUCCH nominal repetition (PUCCH #2). The wireless device may determine a third nominal repetition in a slot n+2 and may drop the third nominal repetition. The wireless device may drop the third nominal repetition in response to the slot n+2 being a downlink slot. In an example, the wireless device may postpone (or does not count the slot n+2 for a repetition) the third nominal repetition to slot n+3. For example, the wireless device may skip downlink resources and may continuously determine a same number of symbols for a next PUCCH nominal repetition. For example, when a slot n+3 is an uplink slot, the wireless device may determine a third nominal repetition for the PUCCH repetition starting first symbol of the slot n+3 and may allocate 12 symbols for the third nominal repetition. The third nominal repetition (PUCCH #3) may have one actual repetition.

A similar mechanism may be used to schedule a time domain resource for a downlink data/control (e.g., PDSCH, PDCCH).

In an example, a carrier or a cell (e.g., an uplink carrier/cell or a downlink carrier/cell) may comprise a plurality of resource blocks (RBs). A resource block may comprise a set of subcarriers (e.g., 1 RB=12 subcarriers). The carrier may be configured with one or more uplink BWPs. An uplink BWP may comprise a plurality of consecutive RBs and a numerology. A wireless device may transmit a TB via the carrier, whereas the wireless device may transmit a part of TB (e.g., a modulation symbol) via a subcarrier.

In an example, a wireless device may transmit a first PUSCH of a TB via a first uplink carrier/cell and a second PUSCH of the TB via the second uplink carrier/cell simultaneously based on the first uplink carrier may operate in a first frequency range and the second uplink (UL) carrier may operate in a second frequency range. For example, a wireless device may receive a first PDSCH of a TB via a first downlink (DL) carrier/cell and a second PDSCH of the TB via the second downlink carrier/cell simultaneously based on the first downlink carrier may operate in a first frequency range and the second downlink carrier may operate in a second frequency range. For example, the first frequency range may be different from the second frequency range. The first frequency range may belong to a frequency range 1, a frequency range 2 or a frequency range 3. The second frequency range may belong to the frequency range 1, the frequency range 2 or the frequency range 3.

For example, the first UL carrier may be a non-supplemental uplink carrier of a cell and the second UL carrier may be a supplemental uplink carrier of the cell. For example, the first uplink carrier is associated with a first uplink panel and/or a first transmission and reception point (TRP) (e.g., a first coreset pool, a first coreset group) of the cell, and the second uplink carrier is associated with a second uplink panel and/or a second TRP (e.g., a second coreset pool, a second coreset group) of the cell. The first UL carrier may be associated with a first cell. The second UL carrier may be associated with a second cell. The first cell and the second cell may be different. For example, the first DL carrier may be a non-supplemental downlink carrier of a cell and the second DL carrier may be a supplemental downlink carrier of the cell. For example, the first downlink carrier is associated with a first uplink panel and/or a first transmission and reception point (TRP) (e.g., a first coreset pool, a first coreset group) of the cell, and the second downlink carrier is associated with a second uplink panel and/or a second TRP (e.g., a second coreset pool, a second coreset group) of the cell. The first DL carrier may be associated with a first cell. The second DL carrier may be associated with a second cell. The first cell and the second cell may be different.

In the specification, a first uplink signal is associated with a TRP in response to a TCI state used for the first uplink signal is associated with/configured with the TRP. The uplink signal is associated with a TRP may correspond to the uplink signal is associated with a panel, a coreset pool or a group associated with the TRP. The first uplink may be associated with a TRP in response to a spatial domain filter parameter configured/used for the first uplink signal is associated with a reference signal of the TRP. The first uplink may be associated with a TRP in response to a spatial domain filter parameter configured/used for the first uplink signal is associated with a TCI state of the TRP. The first uplink may be associated with a TRP in response to a spatial domain filter parameter configured/used for the first uplink signal is associated with a TCI state of a panel associated/linked/mapped to the TRP. The first uplink may be associated with a TRP in response to a spatial domain filter parameter configured/used for the first uplink signal is associated with a SRS resource (or a SRS resource set) associated/linked/mapped to the TRP.

A base station may transmit one or more RRC messages comprising a list of one or more TCI-state configurations (e.g., a mother set of TCI states) for a PDSCH-Config. The base station may configure the one or more TCI-states to determine RX parameters to receive a downlink data for a BWP of a cell. One or more TCI-states configured in the mother set of TCI states may be configured to a set of TCI-states for a CORESET. When a base station configures more than one TCI-states in a CORESET, the base station may further activate (e.g., indicate via a MAC-CE signaling) a TCI-state for the CORESET. A wireless device may support up to M active TCI-states, where M may be different based on a UE capability.

A TCI-state may comprise parameters for configuring a quasi co-location (QCL) relationship between one or more downlink reference signals and the DM-RS ports used for the PDSCH (and/or a PDCCH). QCL relationships may be configured by the base station using qcl-Type1 for the first downlink reference signal, and qcl-Type2 (optionally) for the second downlink reference signal. For example, different QCL-types may be considered to support various use cases and one of QLC-types may be indicated in each qcl-Type1 or qcl-Type2. For example, QCL-TypeA means that a downlink RS (e.g., CSI-RS, TRS) and DM-RSs of a PDSCH (and/or a PDCCH) may have similar properties in Doppler shift, Doppler spread, average delay and delay spread. For example, QCL-TypeB means that a downlink RS and DM-RSs of a PDSCH (and/or a PDCCH) may have similar properties in Doppler shift and Doppler spread. For example, QCL-TypeC means that a downlink RS and DM-RSs of a PDSCH (and/or a PDCCH) may have similar properties in Doppler shift and average delay. For example, QCL-TypeD means that a downlink RS and DM-RSs of a PDSCH (and/or a PDCCH) may have similar properties in spatial RX parameters (e.g., spatial domain filter parameter, spatial domain filter). QCL-TypeD may be used between a gNB and a wireless device to determine one analog beam (e.g., a beam) from one or more analog beams (e.g., beams). A wireless device may determine its spatial RX parameters to receive a downlink analog beam (e.g., beam) based on a QCL-TypeD property configured in a TCI-state.

In an example, a TCI-state may comprise an identifier of the TCI-state (e.g., tci-StateId) and at least one QCL info (e.g., qcl-Type1 and/or qcl-Type 2). A QCL info may indicate/comprise a serving cell index (ServCellIndex), a BWP id (BWP-Id), an index of a reference signal (e.g., between CSI-RS or SSB), and a QCL type (e.g., typeA, type B, typeC, and typeD). The reference signal may be used to determine spatial domain filter parameters (e.g., spatial domain filter) related to the TCI-state used for receiving downlink signals and/or transmitting uplink signals. The wireless device may receive a downlink channel based on the TCI-state. The wireless device may use/refer the reference signal and the QCL type to determine a quasi co-location relationship between the reference signal and a DM-RS of the downlink channel (e.g., PDCCH or PDSCH).

In an example, a base station and a wireless device may support a first mode (e.g., first TCI indication mechanism, a first spatial domain filter parameter (e.g., spatial filter parameter) update mechanism, a first type, a separate beam update mechanism) to update and/or apply a TCI state for a downlink channel or an uplink channel. For example, the following shows an example of the first mode to determine a TCI state of a PDSCH. In response to receiving the one or more RRC messages of the TCI-states (e.g., a mother set of TCI states) initially (e.g., RRC configuration of TCI-states first time) until the wireless device may receive the one or more MAC CE commands to activating a subset of TCI-states from the mother set of TCI states, the wireless device may assume that DM-RS ports of a PDSCH of a serving cell are QCL-ed with an SSB used in an initial access procedure with respect to QCL-Type A and QCL-TypeD if applicable. Based on the one or more MAC CE commands to activate a subset of TCI-states, the wireless device may apply one TCI state from the activated TCI-states for DM-RS ports of a PDSCH of the serving cell. A wireless device may receive an RRC message indicating tci-PresentInDCI is enabled for a CORESET carrying a DCI comprising a resource assignment for a downlink PDSCH. In response to enabled tci-PresentInDCI, the wireless device may expect the DCI field ‘Transmission Configuration Indication’ in a first DCI comprising a resource assignment based on one or more first DCI formats (e.g., DCI format 1_1). The wireless device may not expect the DCI field ‘Transmission Configuration Indication’ in a second DCI comprising a resource assignment based on one or more second DCI formats (e.g., DCI format 1_0). A wireless device may determine QCL information of DM-RS ports of a PDSCH based on one or more following examples.

For example, in response to tci-PresentInDCI being enabled for a CORESET carrying a DCI comprising a resource assignment for the PDSCH, the wireless device may determine the QCL information based on a slot offset K0 indicated by the DCI. For example, when the slot offset K0 is larger than or equal to a Threshold-Sched-Offset, the wireless device may determine the QCL information based on an indicated TCI state by the DCI. For example, the DCI may indicate the TCI state indicating a reference signal for the QCL information.

For example, when the slot offset is smaller than the Threshold-Sched-Offset), the wireless device may determine QCL/TCI information (e.g., a default TCI state) based on one or more CORESETs within an active BWP of the serving cell where the one or more CORESETs are monitored by the wireless device in the latest slot and the index of the one or more CORESETs; selecting a lowest indexed CORESET from the one or more CORESETs and determining the QCL/TCI information based on a QCL/TCI state of the lowest indexed CORESET.

For example, in response to tci-PresentInDCI not being enabled for a second CORESET carrying a second DCI comprising a resource assignment for a first PDSCH or a third DCI is based on the one or more second DCI formats (e.g., DCI format 1_0), the wireless device may determine QCL information based on a slot offset K0 as follows. For example, when K0 is larger than or equal to a Threshold-Sched-Offset, the wireless device may determine QCL/TCI information based on the QCL/TCI state of the second CORESET;

When K0 is smaller than the Threshold-Sched-Offset), the wireless device may determine QCL/TCI information (e.g., a default TCI state) based on one or more CORESETs within an active BWP of the serving cell where the one or more CORESETs are monitored by the wireless device in the latest slot and the index of the one or more CORESETs; selecting a lowest indexed CORESET from the one or more CORESETs and determining the QCL/TCI information based on a QCL/TCI state of the lowest indexed CORESET.

A wireless device may receive one or more MAC CE commands indicating up to K (e.g., K=8) TCI sates from the RRC configured TCI states (e.g., the mother set of TCI states) to one or more codepoints of a DCI field ‘Transmission Configuration Indication’ (if present). One or more DCI formats (e.g., DCI format 1_1) may carry the DCI field ‘Transmission Configuration Indication’. In an example, the wireless device may transmit a HARQ-ACK corresponding to a PDSCH in slot n. The PDSCH may comprise/carry the activation command. In response to the transmitting the HARQ-ACK in the slot n, the wireless device may apply the mapping between the one or more TCI-states and the one or more codepoints of the DCI field “Transmission Configuration Indication” starting from slot n+3·N_slot^subframe,μ+1.

FIG. 22 illustrates an example embodiment of the first mode to update and/or apply a TCI state for a downlink channel or an uplink channel. The base station may transmit one or more RRC messages comprising/indicating configuration parameters. The configuration parameters may comprise one or more TCI states for a CORESET. The configuration parameters may comprise/indicate one or more second TCI states for data channel such as PDSCH. The configuration parameters may comprise spatial domain filter parameters for uplink data and/or uplink control channels. The wireless device may receive the one or more RRC messages at a time T0.

After the wireless device receives an initial higher layer configuration of one or more TCI-states at the time T0 and before a reception of an activation command via a MAC-CE at a time T1, the wireless device may determine a TCI-state of a PDCCH or a coreset based on a SS/PBCH block via an initial access procedure. For example, the SS/PBCH block is a SS/PBCH block selected for a random access procedure that occurs during the initial access procedure. For example, the SS/PBCH block is a SS/PBCH block with a best/good signal quality (e.g., a signal quality of the SS/PBCH block exceeds a threshold). The wireless device may determine QCL-TypeA properties based on the SS/PBCH block. The wireless device may determine QCL-TypeD properties based on the SS/PBCH block. The wireless device may determine a TCI state of a PDSCH based on a PDCCH or a coreset scheduling the PDCCH, where the TCI state of the PDSCH is same as a second TCI state of the PDCCH or the coreset.

Between T0 and T1, the wireless device may determine a spatial domain filter parameter (or a TCI state) of a PUSCH via a cell based on a spatial domain filter parameter (or a TCI state) of a PUCCH resource with a lowest index among one or more configured PUCCH resources if the one or more PUCCH resources are configured for the cell. For example, the wireless device may determine the spatial domain filter parameter for determining a beam or a beam direction to receive or transmit signals via the beam/beam direction based on a beam forming mechanism.

The wireless device may determine a spatial domain filter parameter (or a TCI state) of a PUSCH via a cell based on a TCI state) of a coreset with a lowest index among one or more coresets of the cell when default beam pathloss for PUSCH is enabled. The wireless device may determine a TCI state of a PUSCH based on an SRS resource indicator (SRI) associated with the PUSCH. The wireless device may determine a spatial domain filter parameter of a PUCCH based on a most recent random access procedure (e.g., a spatial domain filter parameter used for a preamble transmission for the most recent random access procedure). The most recent random access procedure may be performed for an initial access process or Reconfiguration with sync procedure (e.g., handover) or beam failure recovery procedure or an uplink synchronization.

The wireless device may receive an activation MAC CE at the time T1. The activation MAC CE may activate one or more TCI states for receiving PDSCHs. The activation MAC CE may activate a TCI state for a CORESET. In response to receiving the MAC CE activating the one or more TCI states for receiving PDSCHs, the wireless device may activate the one or more TCI states. The base station may transmit a DCI (e.g., based on DCI format 1_1) comprising a TCI state (or a TCI state code point) that indicating one TCI of the one or more TCI states. The wireless device may receive a PDSCH based on the DCI via the indicated TCI state. Similarly, a second DCI (e.g., based on DCI format 0_1) may indicate an SRI indicating a spatial domain filter parameter. The wireless device may transmit a PUSCH based on the second DCI via the indicated SRI.

The wireless device may receive a DCI based on a fallback DCI format (e.g., DCI format 1_0 or 0_0). The wireless device may determine a spatial domain filter parameter or a TCI state for a scheduled data reception or transmission based on a rule. For example, for a PDSCH, the wireless device may follow a coreset or a DCI scheduling the PDSCH. For example, for a PUSCH, the wireless device may follow a TCI state of a lowest coreset or a TCI state or a spatial domain filter parameter of a lowest indexed PUCCH. In FIG. 19, the wireless device receives a first DCI (e.g., DCI 0_0), based on a fallback DCI format (e.g., DCI format 1_0 or a DCI format 0_0), scheduling a PUSCH of a cell. The wireless device determines a spatial domain filter parameter of the PUSCH based on a lowest indexed coreset of the cell. In FIG. 22, the wireless device receives a second DCI (e.g., DCI 1_1 or DCI 0_1), based on a non-fallback DCI format (e.g., DCI format 1_1 or DCI format 0_1), scheduling a PDSCH or a PUSCH, the wireless device may determine a TCI state or a spatial domain filter parameter of the PDSCH or the PUSCH based on the DCI if TCI is indicated by the DCI.

In an example, a wireless device may monitor one or more CORESETs (or one or more search spaces) within/in an active BWP (e.g., active downlink BWP) of a serving cell in one or more slots. In an example, the monitoring the one or more CORESETs within/in the active BWP of the serving cell in the one or more slots may comprise monitoring at least one CORESET within/in the active BWP of the serving cell in each slot of the one or more slots. In an example, a latest slot of the one or more slots may occur latest in time. In an example, the wireless device may monitor, within/in the active BWP of the serving cell, one or more second CORESETs of the one or more CORESETs in the latest slot. In response to the monitoring the one or more second CORESETs in the latest slot and the latest slot occurring latest in time, the wireless device may determine the latest slot. In an example, each CORESET of the one or more second CORESETs may be identified by a CORESET specific index (e.g., indicated by a higher layer CORESET-ID). In an example, a CORESET specific index of a CORESET of the one or more secondary CORESETs may be the lowest among the CORESET specific indices of the one or more second CORESETs. In an example, the wireless device may monitor a search space associated with the CORESET in the latest slot. In an example, in response to the CORESET specific index of the CORESET being the lowest and the monitoring the search space associated with the CORESET in the latest slot, the wireless device may select the CORESET of the one or more secondary CORESETs.

In an example, when the offset between the reception of the DCI in the CORESET and the PDSCH scheduled by the DCI is lower than the threshold (e.g., Threshold-Sched-Offset), the wireless device may perform a default PDSCH RS selection. In an example, in the default PDSCH RS selection, the wireless device may assume that one or more DM-RS ports of the PDSCH of a serving cell are quasi co-located with one or more RSs in a TCI-state with respect to one or more QCL type parameter(s). The one or more RSs in the TCI-state may be used for PDCCH quasi co-location indication of the (selected) CORESET of the one or more second CORESETs.

In an example, a wireless device may receive a DCI via a PDCCH in a CORESET. In an example, the DCI may schedule a PDSCH. In an example, an offset between a reception of the DCI and the PDSCH may be less than a threshold (e.g., Threshold-Sched-Offset). A first QCL type (e.g., ‘QCL-TypeD’, etc.) of one or more DM-RS ports of the PDSCH may be different from a second QCL type (e.g., ‘QCL-TypeD’, etc.) of one or more second DM-RS ports of the PDCCH. In an example, the PDSCH and the PDCCH may overlap in at least one symbol. In an example, in response to the PDSCH and the PDCCH overlapping in at least one symbol and the first QCL type being different from the second QCL type, the wireless device may prioritize a reception of the PDCCH associated with the coreset. In an example, the prioritizing may apply to an intra-band CA case (when the PDSCH and the CORESET are in different component carriers). In an example, the prioritizing the reception of the PDCCH may comprise receiving the PDSCH with the second QCL type of one or more second DM-RS ports of the PDCCH. In an example, the prioritizing the reception of the PDCCH may comprise overwriting the first QCL type of the one or more DM-RS ports of the PDSCH with the second QCL type of the one or more second DM-RS ports of the PDCCH. In an example, the prioritizing the reception of the PDCCH may comprise assuming a spatial QCL of the PDCCH (e.g., the second QCL type), for the simultaneous reception of the PDCCH and PDSCH, on the PDSCH. In an example, the prioritizing the reception of the PDCCH may comprise applying a spatial QCL of the PDCCH (e.g., the second QCL type), for the simultaneous reception of the PDCCH and PDSCH, on the PDSCH. In an example, the prioritizing the reception of the PDCCH may comprise receiving the PDCCH and not receiving the PDSCH.

In an example, none of the configured TCI-states may contain a QCL type (e.g., ‘QCL-TypeD’). In response to the none of the configured TCI-states containing the QCL type, the wireless device may obtain the other QCL assumptions from the indicated TCI-states for its scheduled PDSCH irrespective of the time offset between the reception of the DCI and the corresponding PDSCH.

FIG. 23 illustrates an example of configuration parameters for a sounding reference signal (SRS) as per an aspect of an embodiment of the present disclosure. In an example, a base station may configure a wireless device with one or more sounding reference signal (SRS) resource sets by a higher layer parameter SRS-ResourceSet. A SRS-ResourceSet may comprise a SRS-ResourceSetld and one or more SRS resources (e.g, SRS-Resource). In an example, for an SRS resource set of the one or more SRS resource sets, the base station may configure the wireless device with one or more SRS resources by a higher layer parameter SRS-Resource. A SRS-Resource may comprise a SRS-ResourceId, one or more parameters of resources for the SRS resource, and/or spatial relation information (e.g., SRS-SpatialRelationInfo). In an example, the wireless device may indicate a maximum value of a number of the one or more SRS resources to the base station (e.g., by SRS_capability). In an example, the base station may configure an applicability of the SRS resource set by a higher layer parameter usage in the higher layer parameter SRS-ResourceSet.

A spatial relation information may comprise a serving cell index (ServCellIndex) and/or a reference signal. The reference signal may be one of a SSB, a non-zero power CSI-RS and a SRS of an uplink BWP. The wireless device may use the reference signal to determine spatial domain filter parameters based on the SRS resource (e.g., a SRI in a DCI indicates the SRS resource).

In an example, the SRS resource set may comprise a parameter of usage for determining a purpose of the SRS resource set. For example, the higher layer parameter usage is set to ‘BeamManagement’, the wireless device may transmit, at a given time instant, one SRS resource of the one or more SRS resources in each SRS resource set (e.g., simultaneously). In an example, the wireless device may determine that the one SRS resource of the one or more SRS resources in each SRS resource set may have the same time domain resource in a same BWP (e.g., uplink BWP). In an example, in response to the determining, the wireless device may transmit the one SRS resource of the one or more SRS resources in each SRS resource set in the same BWP simultaneously. For example, the one or more SRS resources may overlap in time domain or may have same time domain resources.

In an example, when the higher layer parameter usage is set to ‘BeamManagement’, the wireless device may transmit, at a given time instant, only one SRS resource in each of the one or more SRS resource sets (e.g., simultaneously). In an example, the wireless device may determine that the only one SRS resource in each of the one or more SRS resource sets may have the same time domain resource in a same BWP (e.g., uplink BWP). In an example, in response to the determining, the wireless device may transmit the only one SRS resource in each of the one or more SRS resource sets in the same BWP simultaneously.

In an example, when the higher layer parameter usage is set to ‘BeamManagement’, the wireless device may transmit, at a given time instant, one SRS resource in each of one or more SRS resource sets simultaneously. In an example, the wireless device may determine that the one SRS resource in each of the one or more SRS resource sets may have the same time domain resource in a same BWP (e.g., uplink BWP). In an example, in response to the determining, the wireless device may transmit the one SRS resource in each of the one or more SRS resource sets in the same BWP simultaneously.

In an example, the one or more SRS resource sets may comprise a first SRS resource set and a second SRS resource set. In an example, the first SRS resource set may comprise one or more first SRS resources. The one or more first SRS resources may comprise a first SRS resource and a second SRS resource. In an example, the second SRS resource set may comprise one or more second SRS resources. The one or more second SRS resources may comprise a third SRS resource and a fourth SRS resource.

In an example, a first time domain behavior of the first SRS resource and a third time domain behavior of the third SRS resource may be the same in a BWP. In an example, when the higher layer parameter usage is set to ‘BeamManagement’, the wireless device may transmit, in a given time instant in the BWP, the first SRS resource of the first SRS resource set and the third SRS resource of the second SRS resource set simultaneously, in response to the first time domain behavior of the first SRS resource and the third time domain behavior of the third SRS resource being the same.

In an example, a first time domain behavior of the first SRS resource and a fourth time domain behavior of the fourth SRS resource may be different in a BWP. In an example, when the higher layer parameter usage is set to ‘BeamManagement’, the wireless device may not transmit, in a given time instant in the BWP, the first SRS resource of the first SRS resource set and the fourth SRS resource of the second SRS resource set simultaneously in response to the first time domain behavior of the first SRS resource and the fourth time domain behavior of the fourth SRS resource being different.

In an example, a second time domain behavior of the second SRS resource and a fourth time domain behavior of the fourth SRS resource may be the same in a BWP. In an example, when the higher layer parameter usage is set to ‘BeamManagement’, the wireless device may transmit, in a given time instant in the BWP, the second SRS resource of the first SRS resource set and the fourth SRS resource of the second SRS resource set simultaneously in response to the second time domain behavior of the second SRS resource and the fourth time domain behavior of the fourth SRS resource being the same.

In an example, a second time domain behavior of the second SRS resource and a third time domain behavior of the third SRS resource may be different in a BWP. In an example, when the higher layer parameter usage is set to ‘BeamManagement’, the wireless device may not transmit, in a given time instant in the BWP, the second SRS resource of the first SRS resource set and the third SRS resource of the second SRS resource set simultaneously in response to the second time domain behavior of the second SRS resource and the third time domain behavior of the third SRS resource being different.

In an example, the higher layer parameter SRS-Resource may comprise at least one of: an SRS resource index (e.g., provided by a higher layer parameter srs-ResourceId) indicating a configuration of an SRS resource; a time domain behavior of the configuration of the SRS resource (e.g., indicated by a higher layer parameter resourceType); an SRS sequence ID (e.g., provided by a higher layer parameter sequenceId; and/or a configuration of a spatial relation between a reference RS and a target SRS. In an example, the base station may configure the wireless device with a higher layer parameter spatialRelationInfo. In an example, the higher layer parameter spatialRelationInfo may comprise an index (ID) of the reference RS. In an example, the time domain behavior of an SRS resource may be a periodic transmission, a semi-persistent transmission, or an aperiodic SRS transmission. In an example, a time domain behavior of an SRS resource may comprise a transmission periodicity, a transmission offset of the SRS resource, etc.

In an example, the wireless device may determine that a higher layer parameter servingCellId (or servCellIndex) indicating a serving cell may be present in the higher layer parameter spatialRelationInfo. In response to the determining, the wireless device may determine that the reference RS may be a first RS (e.g., SS/PBCH block, CSI-RS) configured on the serving cell.

In an example, the wireless device may determine that a higher layer parameter uplinkBWP indicating an uplink BWP and a higher layer parameter servingCellId indicating a serving cell may be present in the higher layer parameter spatialRelationInfo. In an example, in response to the determining, the wireless device may determine that the reference RS may be a first RS (e.g., SRS) configured on the uplink BWP of the serving cell.

In an example, the base station may configure the target SRS on a serving cell. In an example, the wireless device may determine that a higher layer parameter servingCellId may be absent in the higher layer parameter spatialRelationInfo. In response to the determining, the wireless device may determine that the reference RS may be a first RS (e.g., SS/PBCH block, CSI-RS) configured on the serving cell.

In an example, the base station may configure the target SRS on a serving cell. In an example, the wireless device may determine that a higher layer parameter servingCellId is absent and a higher layer parameter uplinkBWP indicating an uplink BWP is present in the higher layer parameter spatialRelationInfo. In response to the determining, the wireless device may determine that the reference RS may be a first RS (e.g., SRS) configured on the uplink BWP the serving cell.

In an example, a wireless device may transmit PUSCH and SRS in a same slot. In response to the transmitting the PUSCH and SRS in the same slot, the base station may configure the wireless device to transmit the SRS after the transmission of the PUSCH (and the corresponding DM-RS).

In an example, a base station may configure a wireless device with one or more SRS resource configurations. In an example, a higher layer parameter resourceType in a higher layer parameter SRS-Resource may be set to “periodic.”

In an example, the base station may configure the wireless device with a higher layer parameter spatialRelationInfo. The higher layer parameter spatialRelationInfo may comprise an ID of a reference RS (e.g., ssb-Index, csi-RS-Index, srs).

In an example, the reference RS may be a SS/PBCH block. In an example, the reference RS may be a CSI-RS (e.g., periodic CSI-RS, semi-persistent CSI-RS, aperiodic CSI-RS). In an example, the wireless device may use a spatial domain reception (Rx) filter to receive the reference RS. In an example, in response to the higher layer parameter spatialRelationInfo indicating the reference RS (e.g., by the ID of the reference RS) being the SS/PBCH block or the CSI-RS, the wireless device may transmit a target SRS resource with a spatial domain transmission (Tx) filter same as the spatial domain reception (Rx) filter. In an example, in response to the higher layer parameter spatialRelationInfo indicating the reference RS (e.g., by the ID of the reference RS), the wireless device may transmit a target SRS resource with the spatial domain Rx filter.

In an example, the reference RS may be an SRS (e.g., periodic SRS, semi-persistent SRS, aperiodic SRS). In an example, the wireless device may use a spatial domain transmission (Tx) filter to transmit the reference RS. In an example, in response to the higher layer parameter spatialRelationInfo indicating the reference RS (e.g., by the ID of the reference RS) being the SRS, the wireless device may transmit a target SRS resource with the spatial domain transmission (Tx) filter.

In an example, the base station may activate and deactivate one or more configured SRS resource sets (e.g., semi-persistent SRS resource sets) of a serving cell by sending an SP SRS Activation/Deactivation MAC CE. In an example, the one or more configured SRS resource sets may be initially deactivated upon configuration. In an example, the one or more configured SRS resource sets may be deactivated after a handover.

In an example, a base station may configure a wireless device with one or more SRS resource sets (e.g., semi-persistent SRS resource sets). In an example, a higher layer parameter resourceType in a higher layer parameter SRS-Resource may be set to “semi-persistent.” In an example, the wireless device may receive, from the base station, an activation command (e.g., SP SRS Activation/Deactivation MAC CE) for an SRS resource set of the one or more SRS resource sets. In an example, a PDSCH may carry the activation command. In an example, the wireless device may transmit an HARQ-ACK for the PDSCH in a slot n. In an example, in response to the transmitting the HARQ-ACK for the PDSCH in the slot n, the wireless device may apply one or more assumptions/actions for an SRS transmission of the SRS resource set starting from the slot n+3·N_slot^subframe,μ+1. In an example, the activation command may comprise one or more spatial relation assumptions for one or more SRS resources of the SRS resource set. In an example, a first field (e.g., Resource ID) in the activation command may comprise an identifier of a resource (e.g., SS/PBCH block, NZP CSI-RS, SRS) used for spatial relationship derivation for an SRS resource of the one or more SRS resources. In an example, the one or more spatial relation assumptions may be provided by a list of references to one or more reference signal IDs (e.g., SSB-Index, SRS-ResourceId, etc.), one per SRS resource of the (activated) SRS resource set. In an example, a spatial relation assumption of the one or more spatial relation assumption may be provided by a reference to an ID of a reference RS. In an example, the reference RS may be SS/PBCH block, NZP CSI-RS resource, or SRS.

In an example, a Resource Serving Cell ID field indicating a serving cell may be present in the activation command. In an example, the reference RS may be an SS/PBCH block resource or a NZP CSI-RS resource. In response to the Resource Serving Cell ID field being present and the reference RS being the SS/PBCH block resource or the NZP CSI-RS resource, the reference RS (e.g., SS/PBCH block, NZP CSI-RS resource) may be configured on the serving cell.

In an example, the base station may configure the (activated) SRS resource set on a serving cell. In an example, a Resource Serving Cell ID field may be absent in the activation command. In response to the Resource Serving Cell ID field being absent and the base station configuring the SRS resource set on the serving cell, the reference RS (e.g., SS/PBCH block, NZP CSI-RS resource) may be configured on the serving cell.

In an example, a Resource Serving Cell ID field indicating a serving cell and a Resource BWP ID field indicating an uplink BWP may be present in the activation command. In response to the Resource Serving Cell ID field and the Resource BWP ID field being present, the reference RS (e.g., SRS resource) may be configured on the uplink BWP of the serving cell.

In an example, the base station may configure the SRS resource set on an uplink BWP of a serving cell. In an example, a Resource Serving Cell ID field and a Resource BWP ID field may be absent in the activation command. In response to the Resource Serving Cell ID field and the Resource BWP ID field being absent and the SRS resource set being configured on the uplink BWP of the serving cell, the reference RS (e.g., SRS resource) may be configured on the uplink BWP of the serving cell.

In an example, the base station may configure an SRS resource in the (activated) SRS resource set with a higher layer parameter spatialRelationInfo. In response to the SRS resource, in the (activated) SRS resource set, being configured with the higher layer parameter spatialRelationInfo, the wireless device may assume that a reference RS (e.g., indicated by an ID of the reference RS) in the activation command overrides a second reference RS configured in the higher layer parameter spatialRelationInfo.

In an example, the wireless device may receive, from the base station, a deactivation command (e.g., SP SRS Activation/Deactivation MAC CE) for an (activated) SRS resource set of the one or more SRS resource sets. In an example, a PDSCH may carry the deactivation command. In an example, the wireless device may transmit an HARQ-ACK for the PDSCH in a slot n. In an example, in response to the transmitting the HARQ-ACK for the PDSCH in the slot n, the wireless device may apply one or more assumptions/actions for a cessation of an SRS transmission of the (deactivated) SRS resource set starting from the slot n+ [Image Omitted] 3_slot{circumflex over ( )}(subframe,μ)+1.

In an example, a wireless device may activate a semi-persistent SRS resource configuration on an uplink BWP of a serving cell in response to receiving, from a base station, an activation command for the semi-persistent SRS resource configuration. In an example, the wireless device may not receive, from the base station, a deactivation command for the semi-persistent SRS resource configuration.

In an example, the uplink BWP may be an active uplink BWP of the serving cell. In an example, in response to the uplink BWP being the active uplink BWP of the serving cell and not receiving the deactivation command for the semi-persistent SRS resource configuration, the wireless device may consider the semi-persistent SRS resource configuration active. In an example, in response to the considering, the wireless device may transmit an SRS transmission, via the uplink BWP of the serving cell, according to the semi-persistent SRS resource configuration.

In an example, the uplink BWP may not be an active uplink BWP of the serving cell. In an example, the uplink BWP not being the active uplink BWP may comprise the uplink BWP being deactivated in the serving cell. In response to not receiving the deactivation command for the semi-persistent SRS resource configuration and the uplink BWP being deactivated, the wireless device may assume that the semi-persistent SRS configuration is suspended in the UL BWP of the serving cell. In an example, the semi-persistent SRS configuration being suspended in the UL BWP may comprise that the wireless device may reactivate the semi-persistent SRS configuration when the UL BWP becomes an active UL BWP of the serving cell.

In an example, a first SRS resource of an SRS resource set may have a first time domain behavior (e.g., periodic, semi-persistent, or aperiodic, etc.). In an example, a second SRS resource of the SRS resource set may have a second time domain behavior (e.g., periodic, semi-persistent, or aperiodic, etc.). In an example, in response to the first SRS resource and the second SRS resource being in the (same) SRS resource set, the wireless device may expect that the first time domain behavior and the second time behavior are the same. In an example, in response to the first SRS resource and the second SRS resource being in the (same) SRS resource set, the wireless device may not expect that the first time domain behavior and the second time behavior are different.

In an example, an SRS resource of an SRS resource set may have a first time domain behavior (e.g., periodic, semi-persistent, or aperiodic, etc.). In an example, the SRS resource set may have a second time domain behavior (e.g., periodic, semi-persistent, or aperiodic, etc.). In an example, in response to the SRS resource being associated with the SRS resource set, the wireless device may expect that the first time domain behavior and the second time behavior are the same. In an example, in response to the SRS resource and the SRS resource set being associated, the wireless device may not expect that the first time domain behavior and the second time behavior are different. In an example, the SRS resource being associated with the SRS resource set may comprise that the SRS resource set comprises the SRS resource. In an example, the SRS resource being associated with the SRS resource set may comprise that the SRS resource is an element of the SRS resource set.

In an example, a base station may configure a wireless device with a PUCCH on at least one first symbol on a carrier (e.g., SUL, NUL). In an example, the PUCCH may carry/comprise one or more CSI reports. In an example, the PUCCH may carry/comprise one or more L1-RSRP reports. In an example, the PUCCH may carry/comprise HARQ-ACK and/or SR. In an example, the base station may configure the wireless device with an SRS configuration on the carrier. In an example, the SRS configuration may be a semi-persistent SRS configuration. In an example, the SRS configuration may be a periodic SRS configuration. In an example, the wireless device may determine that the PUCCH and an SRS transmission of the SRS configuration overlap in at least one symbol. In an example, the wireless device may determine that the at least one first symbol of the PUCCH and at least one second symbol of the SRS transmission of the SRS configuration may overlap in the at least one symbol. In an example, in response to the determining, the wireless device may not perform the SRS transmission, on the carrier, on the at least one symbol.

In an example, a base station may configure a wireless device with a PUCCH on at least one first symbol on a carrier (e.g., SUL, NUL). In an example, the PUCCH may carry/comprise HARQ-ACK and/or SR. In an example, the base station may trigger an SRS configuration on the carrier. In an example, the SRS configuration may be an aperiodic SRS configuration. In an example, the wireless device may determine that the PUCCH and an SRS transmission of the SRS configuration overlap in at least one symbol. In an example, the wireless device may determine that the at least one first symbol of the PUCCH and at least one second symbol of the SRS transmission of the SRS configuration may overlap in the at least one symbol. In an example, in response to the determining, the wireless device may not perform the SRS transmission, on the carrier, on the at least one symbol.

In an example, the not performing the SRS transmission may comprise dropping the SRS transmission on the at least one symbol. In an example, the wireless device may perform the SRS transmission on at least one third symbol of the at least one second symbol. The at least one third symbol may not overlap with the at least one symbol.

In an example, a base station may configure a wireless device with a PUCCH on at least one first symbol on a carrier (e.g., SUL, NUL). In an example, the PUCCH may carry/comprise one or more semi-persistent CSI reports. In an example, the PUCCH may carry/comprise one or more periodic CSI reports. In an example, the PUCCH may carry/comprise one or more semi-persistent L1-RSRP reports. In an example, the PUCCH may carry/comprise one or more periodic L1-RSRP reports. In an example, the base station may trigger an SRS configuration on the carrier. In an example, the SRS configuration may be an aperiodic SRS configuration. In an example, the wireless device may determine that the PUCCH and an SRS transmission of the SRS configuration overlap in at least one symbol. In an example, the wireless device may determine that the at least one first symbol of the PUCCH and at least one second symbol of the SRS transmission of the SRS configuration being the aperiodic SRS configuration may overlap in the at least one symbol. In an example, in response to the determining, the wireless device may not transmit the PUCCH, on the carrier, on the at least one symbol.

In an example, in an intra-band carrier aggregation (CA) or in an inter-band CA band-band combination, a wireless device may not transmit an SRS and a PUCCH/PUSCH simultaneously. In an example, in response to not transmitting the SRS and the PUCCH/PUSCH simultaneously, a base station may not configure the wireless device with an SRS transmission from a first carrier and a PUCCH/PUSCH (e.g., PUSCH/UL DM-RS/UL PT-RS/PUCCH formats) in a second carrier in the same symbol. In an example, the first carrier may be different from the second carrier.

In an example, in an intra-band carrier aggregation (CA) or in an inter-band CA band-band combination, a wireless device may not transmit an SRS and a PRACH simultaneously. In an example, in response to not transmitting the SRS and the PRACH simultaneously, the wireless device may not transmit an SRS from a first carrier and a PRACH from a second carrier simultaneously. In an example, the first carrier may be different from the second carrier.

In an example, a base station may configure a wireless device with a periodic SRS transmission on at least one symbol (e.g., OFDM symbol). In an example, the base station may configure an SRS resource with a higher layer parameter resourceType set as ‘aperiodic’. In an example, the base station may trigger the SRS resource on the at least one symbol. In an example, in response to the SRS resource with the higher layer parameter resourceType set as ‘aperiodic’ being triggered on the at least one symbol configured with the periodic SRS transmission, the wireless device may transmit the (aperiodic) SRS resource on the (overlapped) at least one symbol. In an example, in response to the SRS resource with the higher layer parameter resourceType set as ‘aperiodic’ being triggered on the at least one symbol configured with the periodic SRS transmission, the wireless device may not perform the periodic SRS transmission on the at least one symbol. In an example, the not performing the periodic SRS transmission may comprise that the wireless device may not transmit an SRS associated with the periodic SRS transmission on the (overlapped) at least one symbol.

In an example, a base station may configure a wireless device with a semi-persistent SRS transmission on at least one symbol (e.g., OFDM symbol). In an example, the base station may configure an SRS resource with a higher layer parameter resourceType set as ‘aperiodic’. In an example, the base station may trigger the SRS resource on the at least one symbol. In an example, in response to the SRS resource with the higher layer parameter resourceType set as ‘aperiodic’ being triggered on the at least one symbol configured with the semi-persistent SRS transmission, the wireless device may transmit the (aperiodic) SRS resource on the (overlapped) at least one symbol. In an example, in response to the SRS resource with the higher layer parameter resourceType set as ‘aperiodic’ being triggered on the at least one symbol configured with the semi-persistent SRS transmission, the wireless device may not perform the semi-persistent SRS transmission on the at least one symbol. In an example, the not performing the semi-persistent SRS transmission may comprise that the wireless device may not transmit an SRS associated with the semi-persistent SRS transmission on the (overlapped) at least one symbol.

In an example, a base station may configure a wireless device with a periodic SRS transmission on at least one symbol (e.g., OFDM symbol). In an example, the base station may configure an SRS resource with a higher layer parameter resourceType set as ‘semi-persistent’. In an example, the base station may trigger the SRS resource on the at least one symbol. In an example, in response to the SRS resource with the higher layer parameter resourceType set as ‘ semi-persistent’ being triggered on the at least one symbol configured with the periodic SRS transmission, the wireless device may transmit the (semi-persistent) SRS resource on the (overlapped) at least one symbol. In an example, in response to the SRS resource with the higher layer parameter resourceType set as ‘semi-persistent’ being triggered on the at least one symbol configured with the periodic SRS transmission, the wireless device may not perform the periodic SRS transmission on the at least one symbol. In an example, the not performing the periodic SRS transmission may comprise that the wireless device may not transmit an SRS associated with the periodic SRS transmission on the (overlapped) at least one symbol.

In an example, a wireless device may be configured, by a base station, with one or more serving cells. In an example, the base station may activate one or more second serving cells of the one or more serving cells. In an example, the base station may configure each activated serving cell of the one or more second serving cells with a respective PDCCH monitoring. In an example, the wireless device may monitor a set of PDCCH candidates in one or more CORESETs on an active DL BWP of each activated serving cell configured with the respective PDCCH monitoring. In an example, the wireless device may monitor the set of PDCCH candidates in the one or more CORESETs according to corresponding search space sets. In an example, the monitoring may comprise decoding each PDCCH candidate of the set of PDCCH candidates according to monitored DCI formats.

In an example, a set of PDCCH candidates for a wireless device to monitor may be defined in terms of PDCCH search space sets. In an example, a search space set may be a common search space (CSS) set or a UE specific search space (USS) set.

In an example, one or more PDCCH monitoring occasions may be associated with a SS/PBCH block. In an example, the SS/PBCH block may be quasi-co-located with a CSI-RS. In an example, a TCI-state of an active BWP may comprise the CSI-RS. In an example, the active BWP may comprise a CORESET identified with index being equal to zero (e.g., CORESET zero, or CORESET #0, etc.). In an example, the wireless device may determine the TCI-state by the most recent of: an indication by a MAC-CE activation command or a random-access procedure that is not initiated by a PDCCH order that triggers a non-contention based random access procedure. In an example, for a DCI format with CRC scrambled by a C-RNTI, a wireless device may monitor corresponding PDCCH candidates at the one or more PDCCH monitoring occasions in response to the one or more PDCCH monitoring occasions being associated with the SS/PBCH block.

In an example, a base station may configure a wireless device with one or more DL BWPs in a serving cell. In an example, for a DL BWP of the one or more DL BWPs, the wireless device may be provided by a higher layer signaling with one or more (e.g., 2, 3) control resource sets (CORESETs). For a CORESET of the one or more CORESETs, the base station may provide the wireless device, by a higher layer parameter ControlResourceSet, at least one of: a CORESET index (e.g., provided by higher layer parameter controlResourceSetId), a DMRS scrambling sequence initialization value (e.g., provided by a higher layer parameter pdcch-DMRS-ScramblingID); a number of consecutive symbols (e.g., provided by a higher layer parameter duration), a set of resource blocks (e.g., provided by higher layer parameter frequencyDomainResources), CCE-to-REG mapping parameters (e.g., provided by higher layer parameter cce-REG-MappingType), an antenna port quasi co-location (e.g., from a set of antenna port quasi co-locations provided by a first higher layer parameter tci-StatesPDCCH-ToAddList and a second higher layer parameter tci-StatesPDCCH-ToReleaseList), and an indication for a presence or absence of a TCI (e.g., transmission configuration indication, etc.) field for a DCI format (e.g., DCI format 1_1) transmitted by a PDCCH in the CORESET (e.g., provided by higher layer parameter TCI-PresentInDCI). In an example, the antenna port quasi co-location may indicate a quasi co-location information of one or more DM-RS antenna ports for a PDCCH reception in the CORESET. In an example, the CORESET index may be unique among the one or more DL BWPs of the serving cell. In an example, when the higher layer parameter TCI-PresentInDCI is absent, the wireless device may consider that a TCI field is absent/disabled in the DCI format.

In an example, a first higher layer parameter tci-StatesPDCCH-ToAddList and a second higher layer parameter tci-StatesPDCCH-ToReleaseList may provide a subset of TCI-states defined in pdsch-Config. In an example, the wireless device may use the subset of the TCI-states to provide one or more QCL relationships between one or more RS in a TCI-state of the subset of the TCI-states and one or more DM-RS ports of a PDCCH reception in the CORESET.

In an example, a base station may configure a CORESET for a wireless device. In an example, a CORESET index (e.g., provided by higher layer parameter controlResourceSetId) of the CORESET may be non-zero. In an example, the base station may not provide the wireless device with a configuration of one or more TCI-states, by a first higher layer parameter tci-StatesPDCCH-ToAddList and/or a second higher layer parameter tci-StatesPDCCH-ToReleaseList, for the CORESET. In an example, in response to not being provided with the configuration of the one or more TCI-states for the CORESET, the wireless device may assume that one or more DMRS antenna ports for a PDCCH reception in the CORESET is quasi co-located with an RS (e.g., SS/PBCH block). In an example, the wireless device may identify the RS during an initial access procedure.

In an example, a base station may configure a CORESET for a wireless device. In an example, a CORESET index (e.g., provided by higher layer parameter controlResourceSetId) of the CORESET may be non-zero. In an example, the base station may provide the wireless device with an initial configuration of at least two TCI-states, by a first higher layer parameter tci-StatesPDCCH-ToAddList and/or a second higher layer parameter tci-StatesPDCCH-ToReleaseList, for the CORESET. In an example, the wireless device may receive the initial configuration of the at least two TCI-states from the base station. In an example, the wireless device may not receive a MAC-CE activation command for at least one of the at least two TCI-states for the CORESET. In an example, in response to being provided with the initial configuration for the CORESET and not receiving the MAC-CE activation command for the CORESET, the wireless device may assume that one or more DMRS antenna ports for a PDCCH reception in the CORESET is quasi co-located with an RS (e.g., SS/PBCH block). In an example, the wireless device may identify the RS during an initial access procedure.

In an example, a base station may configure a CORESET for a wireless device. In an example, a CORESET index (e.g., provided by higher layer parameter controlResourceSetId) of the CORESET may be equal to zero. In an example, the wireless device may not receive a MAC-CE activation command for a TCI-state for the CORESET. In response to not receiving the MAC-CE activation command, the wireless device may assume that one or more DMRS antenna ports for a PDCCH reception in the CORESET is quasi co-located with an RS (e.g., SS/PBCH block). In an example, the wireless device may identify the RS during an initial access procedure. In an example, the wireless device may identify the RS from a most recent random-access procedure. In an example, the wireless device may not initiate the most recent random-access procedure in response to receiving a PDCCH order triggering a non-contention based random-access procedure.

In an example, a base station may provide a wireless device with a single TCI-state for a CORESET. In an example, the base station may provide the single TCI-state by a first higher layer parameter tci-StatesPDCCH-ToAddList and/or a second higher layer parameter tci-StatesPDCCH-ToReleaseList. In response to being provided with the single TCI-state for the CORESET, the wireless device may assume that one or more DM-RS antenna ports for a PDCCH reception in the CORESET is quasi co-located with one or more DL RSs configured by the single TCI-state.

In an example, a base station may configure a CORESET for a wireless device. In an example, the base station may provide the wireless device with a configuration of at least two TCI-states, by a first higher layer parameter tci-StatesPDCCH-ToAddList and/or a second higher layer parameter tci-StatesPDCCH-ToReleaseList, for the CORESET. In an example, the wireless device may receive the configuration of the at least two TCI-states from the base station. In an example, the wireless device may receive a MAC-CE activation command for at least one of the at least two TCI-states for the CORESET. In response to the receiving the MAC-CE activation command for the at least one of the at least two TCI-states, the wireless device may assume that one or more DM-RS antenna ports for a PDCCH reception in the CORESET is quasi co-located with one or more DL RSs configured by the at least one of the at least two TCI-states.

In an example, a base station may configure a CORESET for a wireless device. In an example, a CORESET index (e.g., provided by higher layer parameter controlResourceSetId) of the CORESET may be equal to zero. In an example, the base station may provide the wireless device with a configuration of at least two TCI-states for the CORESET. In an example, the wireless device may receive the configuration of the at least two TCI-states from the base station. In an example, the wireless device may receive a MAC-CE activation command for at least one of the at least two TCI-states for the CORESET. In an example, in response to the CORESET index being equal to zero, the wireless device may expect that a QCL type (e.g., QCL-TypeD) of a first RS (e.g., CSI-RS) in the at least one of the at least two TCI-states is provided by a second RS (e.g., SS/PBCH block). In an example, in response to the CORESET index being equal to zero, the wireless device may expect that a QCL type (e.g., QCL-TypeD) of a first RS (e.g., CSI-RS) in the at least one of the at least two TCI states is spatial QCL-ed with a second RS (e.g., SS/PBCH block).

In an example, a wireless device may receive a MAC-CE activation command for at least one of at least two TCI-states for a CORESET. In an example, a PDSCH may provide the MAC-CE activation command. In an example, the wireless device may transmit a HARQ-ACK information for the PDSCH in a slot. In an example, when the wireless device receives the MAC-CE activation command for the at least one of the at least two TCI-states for the CORESET, in response to the transmitting HARQ-ACK information in the slot, the wireless device may apply the MAC-CE activation command X msec (e.g., 3 msec, 5 msec) after the slot. In an example, when the wireless device applies the MAC-CE activation command in a second slot, a first BWP may be active in the second slot. In response to the first BWP being active in the second slot, the first BWP may be an active BWP.

In an example, a base station may configure a wireless device with one or more DL BWPs in a serving cell. In an example, for a DL BWP of the one or more DL BWPs, the wireless device may be provided by higher layers with one or more (e.g., 3, 5, 10) search space sets. In an example, for a search space set of the one or more search space sets, the wireless device may be provided, by a higher layer parameter SearchSpace, at least one of: a search space set index (e.g., provided by higher layer parameter searchSpaceId), an association between the search space set and a CORESET (e.g., provided by a higher layer parameter controlResourceSetId); a PDCCH monitoring periodicity of a first number of slots and a PDCCH monitoring offset of a second number of slots (e.g., provided by a higher layer parameter monitoringSlotPeriodicityAndOffset); a PDCCH monitoring pattern within a slot, indicating first symbol(s) of the CORESET within the slot for PDCCH monitoring, (e.g., provided by a higher layer parameter monitoringSymbolsWithinSlot); a duration of a third number of slots (e.g., provided by a higher layer parameter duration); a number of PDCCH candidates; an indication that the search space set is either a common search space set or a UE-specific search space set (e.g., provided by a higher layer parameter searchSpaceType). In an example, the duration may indicate a number of slots that the search space set may exist.

In an example, a wireless device may not expect two PDCCH monitoring occasions on an active DL BWP, for a same search space set or for different search space sets, in a same CORESET to be separated by a non-zero number of symbols that is smaller than the CORESET duration.

In an example, the wireless device may determine a PDCCH monitoring occasion on an active DL BWP based on the PDCCH monitoring periodicity, the PDCCH monitoring offset, and the PDCCH monitoring pattern within a slot. In an example, for the search space set, the wireless device may determine that a PDCCH monitoring occasion exists in a slot. In an example, the wireless device may monitor at least one PDCCH for the search space set for the duration of third number of slots (consecutive) starting from the slot.

In an example, a wireless device may monitor one or more PDCCH candidates in a UE-specific search space (USS) set on an active DL BWP of a serving cell. In an example, a base station may not configure the wireless device with a carrier indicator field. In response to not being configured with the carrier indicator field, the wireless device may monitor the one or more PDCCH candidates without the carrier indicator field.

In an example, a wireless device may monitor one or more PDCCH candidates in a USS set on an active DL BWP of a serving cell. In an example, a base station may configure the wireless device with a carrier indicator field. In response to being configured with the carrier indicator field, the wireless device may monitor the one or more PDCCH candidates with the carrier indicator field.

In an example, a base station may configure a wireless device to monitor one or more PDCCH candidates with a carrier indicator field in a first cell. In an example, the carrier indicator field may indicate a second cell. In an example, the carrier indicator field may correspond to a second cell. In response to monitoring the one or more PDCCH candidates, in the first cell, with the carrier indicator field indicating the second cell, the wireless device may not expect to monitor the one or more PDCCH candidates on an active DL BWP of the second cell.

In an example, a wireless device may monitor one or more PDCCH candidates on an active DL BWP of a serving cell. In response to the monitoring the one or more PDCCH candidates on the active DL BWP of the serving cell, the wireless device may monitor the one or more PDCCH candidates at least for the serving cell. In an example, the wireless device may monitor the one or more PDCCH candidates for the serving cell and at least a second serving cell.

In an example, a base station may configure a wireless device with one or more cells. In an example, when a number of the one or more cells is one, the base station may configure the wireless device for a single-cell operation. In an example, when a number of the one or more cells is more than one, the base station may configure the wireless device for an operation with a carrier aggregation in a same frequency band (e.g., intra-band).

In an example, the wireless device may monitor one or more PDCCH candidates in overlapping PDCCH monitoring occasions in a plurality of CORESETs on active DL BWP(s) of the one or more cells. In an example, the plurality of the CORESETs may have a different QCL-TypeD property.

In an example, a first PDCCH monitoring occasion in a first CORESET, of the plurality of CORESETs, of a first cell of the one or more cells may overlap with a second PDCCH monitoring occasion in a second CORESET, of the plurality of CORESETs, of the first cell. In an example, the wireless device may monitor at least one first PDCCH candidate in the first PDCCH monitoring occasion on an active DL BWP, of the active DL BWP(s), of the first cell. In an example, the wireless device may monitor at least one second PDCCH candidate in the second PDCCH monitoring occasion on the active DL BWP, of the active DL BWP(s), of the first cell.

In an example, a first PDCCH monitoring occasion in a first CORESET, of the plurality of CORESETs, of a first cell of the one or more cells may overlap with a second PDCCH monitoring occasion in a second CORESET, of the plurality of CORESETs, of a second cell of the one or more cells. In an example, the wireless device may monitor at least one first PDCCH candidate in the first PDCCH monitoring occasion on a first active DL BWP, of the active DL BWP(s), of the first cell. In an example, the wireless device may monitor at least one second PDCCH candidate in the second PDCCH monitoring occasion on a second active DL BWP, of the active DL BWP(s), of the second cell.

In an example, a first QCL type property (e.g., QCL-TypeD) of the first CORESET may be different from a second QCL type property (e.g., QCL-TypeD) of the second CORESET.

In an example, in response to the monitoring the one or more PDCCH candidates in the overlapping PDCCH monitoring occasions in the plurality of CORESETs and the plurality of the CORESETs having the different QCL-TypeD property, for a CORESET determination rule, the wireless device may determine a selected CORESET, of the plurality of the CORESETs, of a cell of the one or more cells. In an example, in response to the determining, the wireless device may monitor at least one PDCCH candidate, in the overlapping PDCCH monitoring occasions, in the selected CORESET on an active DL BWP of the cell. In an example, the selected CORESET may be associated with a search space set (e.g., association provided by a higher layer parameter controlResourceSetId).

In an example, one or more CORESETs of the plurality of CORESETs may be associated with a common search space (CSS) set. In an example, the one or more CORESETs of the plurality of CORESETs being associated with the CSS set may comprise that at least one search space set of a CORESET (e.g., association between the at least one search space set and the CORESET provided by a higher layer parameter controlResourceSetId) of the one or more CORESETs has at least one PDCCH candidate in the overlapping PDCCH monitoring occasions and/or in a CSS set.

In an example, the first CORESET may be associated with a first CSS set. In an example, the first CORESET may be associated with a first USS set. In an example, the second CORESET may be associated with a second CSS set. In an example, the second CORESET may be associated with a second USS set. In an example, a CORESET (e.g., the first CORESET, the second CORESET) being associated with a CSS set (e.g., first CSS set, second CSS set) may comprise that at least one search space of the CORESET is the CSS set. In an example, a CORESET (e.g., the first CORESET, the second CORESET) being associated with an USS set (e.g., first USS set, second USS set) may comprise that at least one search space of the CORESET is the USS set.

In an example, when the first CORESET is associated with the first CSS set and the second CORESET is associated with the second CSS set, the one or more CORESETs may comprise the first CORESET and the second CORESET.

In an example, when the one or more CORESETs comprises the first CORESET and the second CORESET, the one or more selected cells may comprise the first cell and the second cell in response to the first CORESET being configured in the first cell and the second CORESET being configured in the second cell.

In an example, when the one or more CORESETs comprises the first CORESET and the second CORESET, the one or more selected cells may comprise the first cell in response to the first CORESET being configured in the first cell and the second CORESET being configured in the first cell. In an example, the at least one CORESET may comprise the first CORESET and the second CORESET. In an example, a first search space set of the first CORESET of the at least one CORESET may be identified by a first search space set specific index (e.g., provided by a higher layer parameter searchSpaceId). In an example, the wireless device may monitor the at least one first PDCCH candidate in the first PDCCH monitoring occasion in the first CORESET associated with the first search space set (e.g., association provided by a higher layer parameter controlResourceSetId). In an example, a second search space set of the second coreset of the at least one CORESET may be identified by a second search space set specific index (e.g., provided by a higher layer parameter searchSpaceId). In an example, the wireless device may monitor the at least one second PDCCH candidate in the second PDCCH monitoring occasion in the second CORESET associated with the second search space set (e.g., association provided by a higher layer parameter controlResourceSetId). In an example, the first search space set specific index may be lower than the second search space set specific index. In response to the first search space set specific index being lower than the second search space set specific index, for a CORESET determination rule, the wireless device may select the first search space set. In an example, in response to the selecting, for the coreset determination rule, the wireless device may monitor the at least one first PDCCH candidate in the first PDCCH monitoring occasion in the first CORESET on the active DL BWP of the first cell. In an example, in response to the selecting, for the coreset determination rule, the wireless device may stop monitoring the at least one second PDCCH candidate in the second PDCCH monitoring occasion in the second CORESET on the active DL BWP of the first cell. In an example, in response to the selecting, the wireless device may drop monitoring the at least one second PDCCH candidate in the second PDCCH monitoring occasion in the second CORESET on the active DL BWP of the first cell.

In an example, the first cell may be identified by a first cell-specific index. In an example, the second cell may be identified by a second cell-specific index. In an example, the first cell-specific index may be lower than the second cell-specific index. In an example, when the one or more selected cells comprises the first cell and the second cell, the wireless device may select the first cell in response to the first cell-specific index being lower than the second cell-specific index.

In an example, when the first CORESET is associated with the first CSS set and the second CORESET is associated with the second USS set, the one or more CORESETs may comprise the first CORESET. In an example, when the one or more CORESETs comprises the first CORESET, the one or more selected cells may comprise the first cell in response to the first CORESET being configured in the first cell.

In an example, when the first CORESET is associated with the first USS set and the second CORESET is associated with the second CSS set, the one or more CORESETs may comprise the second CORESET. In an example, when the one or more CORESETs comprises the second CORESET, the one or more selected cells may comprise the first cell in response to the second CORESET being configured in the first cell. In an example, when the one or more CORESETs comprises the second CORESET, the one or more selected cells may comprise the second cell in response to the second CORESET being configured in the second cell.

In an example, the wireless device may determine that the one or more CORESETs are associated with one or more selected cells of the one or more cells. In an example, the base station may configure a first CORESET of the one or more CORESETs in a first cell of the one or more selected cells. In an example, the base station may configure a second CORESET of the one or more CORESETs in the first cell. In an example, the base station may configure a third CORESET of the one or more CORESETs in a second cell of the one or more selected cells. In an example, the first cell and the second cell may be different.

In an example, the wireless device may receive, from the base station, one or more configuration parameters. The one or more configuration parameters may indicate cell-specific indices (e.g., provided by a higher layer parameter servCellIndex) for the one or more cells. In an example, each cell of the one or more cells may be identified by a respective one cell-specific index of the cell-specific indices. In an example, a cell-specific index of a cell of the one or more selected cells may be lowest among the cell-specific indices of the one or more selected cells.

In an example, when the wireless device determines that the one or more CORESETs are associated with the one or more selected cells of the one or more cells, for the CORESET determination rule, the wireless device may select the cell in response to the cell-specific index of the cell being lowest among the cell-specific indices of the one or more selected cells.

In an example, the base station may configure at least one CORESET of the one or more CORESETs in the (selected) cell. In an example, at least one search space set of the at least one CORESET may have at least one PDCCH candidate in the overlapping PDCCH monitoring occasions and/or may be a CSS set.

In an example, the one or more configuration parameters may indicate search space set specific indices (e.g., provided by a higher layer parameter searchSpaceId) for the at least one search space set of the cell. In an example, each search space set of the at least one search space set may be identified by a respective one search space set specific index of the search space set specific indices. In an example, the wireless device may determine that a search space specific index of a search space set of the at least one search space set may be the lowest among the search space set specific indices of the at least one search space set. In response to the determining that the search space specific index of the search space set specific index being the lowest among the search space set specific indices of the at least one search space set, for the CORESET determination rule, the wireless device may select the search space set. In an example, the search space set may be associated with a selected CORESET of the at least one CORESET (e.g., association provided by a higher layer parameter controlResourceSetId).

In an example, when the wireless device monitors the one or more PDCCH candidates in the overlapping PDCCH monitoring occasions in the plurality of CORESETs and the plurality of the CORESETs have the different QCL-TypeD property, the wireless device may monitor at least one PDCCH in the selected CORESET of the plurality of the CORESETs on an active DL BWP of the cell of the one or more cells in response to the selecting the cell and/or the selecting the search space set associated with the selected CORESET. In an example, the wireless device may select the selected CORESET associated with the search space set and the cell for the CORESET determination rule.

In an example, the selected CORESET may have a first QCL-TypeD property. In an example, a second CORESET of the plurality of the CORESETs may have a second QCL-TypeD property. In an example, the selected CORESET and the second CORESET may be different.

In an example, the first QCL-TypeD property and the second QCL-TypeD property may be the same. In an example, the wireless device may monitor at least one second PDCCH candidate (in the overlapping PDCCH monitoring occasions) in the second CORESET of the plurality of the CORESETs in response to the first QCL-TypeD property of the selected CORESET and the second QCL-TypeD property of the second CORESET being the same.

In an example, the first QCL-TypeD property and the second QCL-TypeD property may be different. In an example, the wireless device may stop monitoring at least one second PDCCH candidate (in the overlapping PDCCH monitoring occasions) in the second CORESET of the plurality of the CORESETs in response to the first QCL-TypeD property of the selected CORESET and the second QCL-TypeD property of the second CORESET being different. In an example, the wireless device may drop monitoring at least one second PDCCH candidate (in the overlapping PDCCH monitoring occasions) in the second CORESET of the plurality of the CORESETs in response to the first QCL-TypeD property of the selected CORESET and the second QCL-TypeD property of the second CORESET being different.

In an example, for the CORESET determination rule, a wireless device may consider that a first QCL type (e.g., QCL TypeD) property of a first RS (e.g., SS/PBCH block) is different from a second QCL type (e.g., QCL TypeD) property of a second RS (CSI-RS).

In an example, for the CORESET determination rule, a first RS (e.g., CSI-RS) may be associated (e.g., QCL-ed) with an RS (e.g., SS/PBCH block) in a first cell. In an example, a second RS (e.g., CSI-RS) may be associated (e.g., QCL-ed) with the RS in a second cell. In response to the first RS and the second RS being associated with the RS, the wireless device may consider that a first QCL type (e.g., QCL TypeD) property of the first RS and a second QCL type (e.g., QCL TypeD) property of the second RS are the same.

In an example, the wireless device may determine a number of active TCI-states from the plurality of CORESETs.

In an example, a wireless device may monitor multiple search space sets associated with different CORESETs for one or more cells (e.g., for a single cell operation or for an operation with carrier aggregation in a same frequency band). In an example, at least two monitoring occasions of at least two search space sets of the multiple search space sets may overlap in time (e.g., at least one symbol, at least one slot, subframe, etc.). In an example, the at least two search space sets may be associated with at least two first CORESETs. The at least two first CORESETs may have different QCL-TypeD properties. In an example, for the CORESET determination rule, the wireless device may monitor at least one search space set associated with a selected CORESET in an active DL BWP of a cell. In an example, the at least one search space set may be a CSS set. In an example, a cell-specific index of the cell may be lowest among cell-specific indices of the one or more cells comprising the cell. In an example, at least two second CORESETs of the cell may comprise a CSS set. In response to the at least two second CORESETs of the cell comprising the CSS set, the wireless device may select a selected CORESET of the at least two second CORESETs in response to a search space specific index of a search space set associated with the selected CORESET being the lowest among search space specific indices of search space sets associated with the at least two second CORESETs. In an example, the wireless device may monitor the search space set in the at least two monitoring occasions.

In an example, the wireless device may determine that the at least two first CORESETs may not be associated with a CSS set. In an example, the wireless device may determine that each CORESET of the at least two first CORESETs may not be associated with a CSS set. In an example, for the CORESET determination rule, in response to the determining, the wireless device may monitor at least one search space set associated with a selected CORESET in an active DL BWP of a cell. In an example, the at least one search space set may be a USS set. In an example, a cell-specific index of the cell may be lowest among cell-specific indices of the one or more cells comprising the cell. In an example, at least two second CORESETs of the cell may comprise a USS set. In response to the at least two second CORESETs of the cell comprising the USS set, the wireless device may select a selected CORESET of the at least two second CORESETs in response to a search space specific index of a search space set associated with the selected CORESET being the lowest among search space specific indices of search space sets associated with the at least two second CORESETs. In an example, the wireless device monitors the search space set in the at least two monitoring occasions.

In an example, a base station may indicate, to a wireless device, a TCI-state for a PDCCH reception for a CORESET of a serving cell by sending a TCI-state indication for UE-specific PDCCH MAC-CE. In an example, when a MAC entity of the wireless device receives a TCI-state indication for UE-specific PDCCH MAC-CE on/for a serving cell, the MAC entity may indicate to lower layers (e.g., PHY) the information regarding the TCI-state indication for the UE-specific PDCCH MAC-CE.

In an example, a TCI-state indication for UE-specific PDCCH MAC-CE may be identified by a MAC PDU subheader with LCID. The TCI-state indication for UE-specific PDCCH MAC-CE may have a fixed size of 16 bits comprising one or more fields. In an example, the one or more fields may comprise a serving cell ID, CORESET ID, TCI-state ID and a reserved bit.

In an example, the serving cell ID may indicate the identity of the serving cell for which the TCI-state indication for the UE-specific PDCCH MAC-CE applies. The length of the serving cell ID may be n bits (e.g., n=5 bits).

In an example, the CORESET ID may indicate a control resource set. The control resource set may be identified with a control resource set ID (e.g., ControlResourceSetId). The TCI-state is being indicated to the control resource set ID for which. The length of the CORESET ID may be n3 bits (e.g., n3=4 bits).

In an example, the TCI-state ID may indicate a TCI-state identified by TCI-StateId. The TCI-state may be applicable to the control resource set identified by the CORESET ID. The length of the TCI-state ID may be n4 bits (e.g., n4=6 bits).

An information element ControlResourceSet may be used to configure a time/frequency control resource set (CORESET) in which to search for downlink control information.

An information element TCI-State may associate one or two DL reference signals with a corresponding quasi-colocation (QCL) type. The information element TCI-State may comprise one or more fields including TCI-StateId and QCL-Info. The QCL-Info may comprise one or more second fields. The one or more second fields may comprise serving cell index, BWP ID, a reference signal index (e.g., SSB-index, NZP-CSI-RS-ResourceID), and a QCL Type (e.g., QCL-typeA, QCL-typeB, QCL-typeC, QCL-typeD). In an example, the TCI-StateID may identify a configuration of a TCI-state.

In an example, the serving cell index may indicate a serving cell in which a reference signal indicated by the reference signal index is located in. When the serving cell index is absent in an information element TCI-State, the information element TCI-State may apply to a serving cell in which the information element TCI-State is configured. The reference signal may be located on a second serving cell other than the serving cell in which the information element TCI-State is configured only if the QCL-Type is configured as first type (e.g., TypeD, TypeA, TypeB). In an example, the BWP ID may indicate a downlink BWP of the serving cell in which the reference signal is located in.

An information element SearchSpace may define how/where to search for PDCCH candidates in a search space. The search space may be identified by a searchSpaceId field in the information element SearchSpace. Each search space may be associated with a control resource set (e.g., ControlResourceSet). The control resource set may be identified by a controlResourceSetId field in the information element SearchSpace. The controlResourceSetId field may indicate the control resource set (CORESET) applicable for the SearchSpace.

In an example, a base station may use an information element (IE) CSI-AperiodicTriggerStateList to configure a wireless device with one or more aperiodic trigger states (e.g., 1, 64, 128 aperiodic trigger states). A codepoint of a CSI request field in a DCI may be associated with (or indicate) an aperiodic trigger state of the one or more aperiodic trigger states. In an example, the aperiodic trigger state may comprise one or more report configurations (e.g., 1, 8, 16 report configurations, provided by a higher layer parameter associatedReportConfigInfoList). Based on receiving the DCI with the CSI request field indicating the aperiodic trigger state, the wireless device may perform measurement of CSI-RS and aperiodic reporting according to the one or more report configurations (e.g., in the associatedReportConfigInfoList) for the aperiodic trigger state.

In an example, a report configuration (e.g., provided by a higher layer parameter CSI-AssociatedReportConfigInfo) of the one or more report configurations may be identified/associated with a report configuration index (e.g., provided by a higher layer parameter CSI-ReportConfigId). In an example, the report configuration may comprise one or more CSI-RS resources (e.g., 1, 8, 16 CSI-RS resources). In an example, an aperiodic CSI-RS resource of the one or more CSI-RS resources may be associated with a TCI state (provided by a higher layer parameter qcl-info in IE CSI-AperiodicTriggerStateList) of one or more TCI-State configurations. The TCI state may provide a QCL assumption (e.g., an RS, an RS source, SS/PBCH block, CSI-RS). The TCI state may provide a QCL type (e.g., QCL-TypeA, QCL-TypeD, etc.).

In an example, the wireless device may receive a DCI with a CSI request field from a base station. The wireless device may receive the DCI in a PDCCH. The wireless device may receive the DCI when monitoring the PDCCH. In an example, the DCI with the CSI request field may initiate/indicate/trigger an aperiodic trigger state of the one or more aperiodic trigger states. In an example, a codepoint of the CSI request field in the DCI may indicate the aperiodic trigger state. In an example, the aperiodic trigger state may comprise one or more report configurations (e.g., a list of NZP-CSI-RS-ResourceSet). In an example, a report configuration (e.g., NZP-CSI-RS-ResourceSet) of the one or more report configurations may comprise one or more CSI-RS resources (e.g., aperiodic CSI-RS resources, NZP-CSI-RS-Resources).

In an example, the base station may not configure the report configuration with a higher layer parameter trs-Info. In an example, configuring the report configuration without the higher layer parameter trs-Info may comprise that a first antenna port for a first aperiodic CSI-RS resource of the one or more CSI-RS resources is different from a second antenna port for a second aperiodic CSI-RS resource of the one or more CSI resources. In an example, configuring the report configuration without the higher layer parameter trs-Info may comprise that an antenna port for each aperiodic CSI-RS resource of the one or more CSI-RS resources is different. In an example, the base station may not configure the report configuration with a higher layer parameter repetition. In an example, a scheduling offset between a last symbol of the PDCCH carrying the DCI and a first symbol of the one or more CSI-RS resources in the report configuration may be smaller than a second threshold (e.g., beamSwitchTiming). In an example, the wireless device may report the second threshold. In an example, the second threshold may be a first value (e.g., 14, 28, 48 symbols).

In an example, an aperiodic CSI-RS resource of the one or more CSI-RS resources may be associated with a first TCI state of the one or more TCI-State configurations. In an example, the first TCI state may indicate at least one first RS. In an example, the first TCI state may indicate at least one first QCL type. In an example, the aperiodic CSI-RS resource being associated with the first TCI state may comprise that the wireless device receives an aperiodic CSI-RS of the aperiodic CSI-RS resource with the at least one first RS (indicated by the first TCI state) with respect to the at least one first QCL type indicated by the first TCI state.

In an example, the base station may transmit a downlink signal with a second TCI state. In an example, the second TCI state may indicate at least one second RS. In an example, the second TCI state may indicate at least one second QCL type. The wireless device may receive the downlink signal in one or more first symbols. The wireless device may receive an aperiodic CSI-RS for the aperiodic CSI-RS resource in one or more second symbols. In an example, the one or more first symbols and the one or more second symbols may overlap (e.g., fully or partially). In an example, the downlink signal and the aperiodic CSI-RS (or the aperiodic CSI-RS resource) may overlap based on the one or more first symbols and the one or more second symbols overlapping.

In an example, the downlink signal and the aperiodic CSI-RS (or the aperiodic CSI-RS resource) may overlap in a time duration. In an example, the time duration may be at least one symbol. In an example, the time duration may be at least one slot. In an example, the time duration may be at least one subframe. In an example, the time duration may be at least one mini-slot. In an example, the time duration may be the one or more second symbols. In an example, the time duration may be the one or more first symbols.

In an example, the downlink signal may be a PDSCH scheduled with an offset larger than or equal to a first threshold (e.g., Threshold-Sched-Offset, timeDurationForQCL). In an example, the downlink signal may be a second aperiodic CSI-RS scheduled with an offset larger than or equal a second threshold (e.g., beamSwitchTiming) when the second threshold is a first value (e.g., 14, 28, 48 symbols). In an example, the downlink signal may be an RS (e.g., periodic CSI-RS, semi-persistent CSI-RS, SS/PBCH block etc.).

In an example, when the scheduling offset between the last symbol of the PDCCH and the first symbol is smaller than the second threshold, based on the downlink signal with the second TCI state and the aperiodic CSI-RS (or the aperiodic CSI-RS resource) overlapping, the wireless device may apply a QCL assumption provided/indicated by the second TCI state when receiving the aperiodic CSI-RS. In an example, the applying the QCL assumption (provided/indicated by the second TCI state) when receiving the aperiodic CSI may comprise that the wireless device receives the aperiodic CSI-RS with the at least one second RS (indicated by the second TCI state) with respect to the at least one second QCL type indicated by the second TCI state.

In an example, a scheduling offset between a last symbol of the PDCCH carrying the DCI and a first symbol of the one or more CSI-RS resources in the report configuration may be equal to or larger than a second threshold (e.g., beamSwitchTiming). In an example, the wireless device may report the second threshold. In an example, the second threshold may be a first value (e.g., 14, 28, 48 symbols). Based on the scheduling offset being equal to or larger than the second threshold, the wireless device may apply a QCL assumption (provided by the first TCI state) for the aperiodic CSI-RS resource of the one or more CSI-RS resources in the report configuration. In an example, the applying the QCL assumption (provided by the first TCI state) for the aperiodic CSI-RS resource may comprise that the wireless device receives the aperiodic CSI-RS of the aperiodic CSI-RS resource with the at least one first RS (indicated by the first TCI state) with respect to the at least one first QCL type indicated by the first TCI state.

In an example, two transmission schemes for uplink may be supported for physical uplink shared channel (PUSCH): codebook based transmission and non-codebook based transmission. A wireless device may be configured with codebook based transmission when the higher layer parameter txConfig in pusch-Config is set to ‘codebook’. The wireless device may be configured with non-codebook based transmission when the higher layer parameter txConfig is set to ‘nonCodebook’. When the higher layer parameter txConfig is not configured, the wireless device may not expect to be scheduled by DCI format 0_1 or 0_2. When PUSCH is scheduled by DCI format 0_0, the PUSCH transmission may be based on a single antenna port. Except when the higher layer parameter enableDefaultBeamPlForPUSCH0_0 is set ‘enabled’, the wireless device may not expect PUSCH scheduled by DCI format 0_0 in a BWP without configured PUCCH resource with PUCCH-SpatialRelationInfo in frequency range 2 in RRC connected mode.

For codebook based transmission, in an example, PUSCH may be scheduled by DCI format 0_0, DCI format 0_1, DCI format 0_2 or semi-statically configured. When this PUSCH is scheduled by DCI format 0_1, DCI format 0_2, or semi-statically configured, the wireless device may determine its PUSCH transmission precoder based on a SRS resource indicator (SRI), a transmit precoding matrix indicator (TPMI) and a transmission rank, where the SRI, the TPMI and the transmission rank may be given by DCI fields of ‘SRS resource indicator’ and Trecoding information and number of layers' for DCI format 0_1 and 0_2 or given by srs-ResourceIndicator and precodingAndNumberOfLayers. In an example, the SRS-ResourceSet(s) applicable for PUSCH scheduled by DCI format 0_1 and DCI format 0_2 may be defined by the entries of the higher layer parameter srs-ResourceSetToAddModList and srs-ResourceSetToAddModList-ForDCIFormat0_2 in SRS-Config, respectively. The TPMI may be used to indicate the precoder to be applied over the layers {0 . . . v−1} and that corresponds to an SRS resource selected by the SRI when multiple SRS resources are configured, or when a single SRS resource is configured TPMI is used to indicate the precoder to be applied over the layers {0 . . . v−1} and that corresponds to the SRS resource. The transmission precoder may be selected from the uplink codebook that has a number of antenna ports equal to higher layer parameter nrofSRS-Ports in SRS-Config. When the wireless device is configured with the higher layer parameter txConfig set to ‘codebook’, the wireless device may be configured with at least one SRS resource. In an example, the indicated SRI in slot n may be associated with the most recent transmission of an SRS resource identified by the SRI, where the SRS resource is prior to the PDCCH carrying the SRI.

For non-codebook based transmission, in an example, PUSCH may be scheduled by DCI format 0_0, DCI format 0_1, DCI format 0_2 or semi-statically configured. When this PUSCH is scheduled by DCI format 0_1, DCI format 0_2, or semi-statically configured, the wireless device may determine its PUSCH precoder and transmission rank based on an SRI when multiple SRS resources are configured, where the SRI is given by a DCI field of ‘SRS resource indicator’ in DCI for DCI format 0_1 and DCI format 0_2, or the SRI is given by srs-ResourceIndicator. In an example, the SRS-ResourceSet(s) applicable for PUSCH scheduled by DCI format 0_1 and DCI format 0_2 may be defined by the entries of the higher layer parameter srs-ResourceSetToAddModList and srs-ResourceSetToAddModList-ForDCIFormat0_2 in SRS-Config, respectively. The wireless device may use one or multiple SRS resources for SRS transmission, where, in a SRS resource set, the maximum number of SRS resources which may be configured to the wireless device for simultaneous transmission in the same symbol and the maximum number of SRS resources may the wireless device's capabilities. In an example, the SRS resources transmitted simultaneously may occupy the same RBs. In an example, at least one SRS port for an SRS resource may be configured. In an example, one SRS resource set may be configured with higher layer parameter usage in SRS-ResourceSet set to ‘nonCodebook’. The indicated SRI in slot n may be associated with the most recent transmission of SRS resource(s) identified by the SRI, where the SRS transmission is prior to the PDCCH carrying the SRI. The wireless device may perform one-to-one mapping from the indicated SRI(s) to the indicated demodulation RS (DMRS) ports(s) and their corresponding PUSCH layers {0 . . . v−1} given by DCI format 0_1 or by configuredGrantConfig in increasing order.

FIG. 24 shows an example of transmission and reception with multiple transmission reception points (TRPs) and/or multiple panels. In an example, a base station may be equipped with more than one TRP (e.g., TRP 1 and TRP 2). A wireless device may be equipped with more than one panel (e.g., Panel 1 and Panel 2).

In an example, a wireless device may comprise antenna/RF component. The antenna may comprise one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. The antenna may be coupled to the radio front end circuitry and nay be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In some embodiments, the antenna may comprise one or more omni-directional, sector, or panel antennas operable to transmit/receive radio signals between, for example, 2 gigahertz (GHz) and 66 GHz. An omni-directional antenna may be used to transmit/receive radio signals in any direction, a sector antenna may be used to transmit/receive radio signals from devices within a particular area, and a panel antenna may be a line of sight antenna used to transmit/receive radio signals in a relatively straight line. In some instances, the use of more than one antenna may be referred to as Multiple input Multiple Output (MIMO). In certain embodiments, the antenna may be separate from a network node (e.g., a base station) and may be connectable to the network node through an interface or port.

A common UE antenna panel may be a physical or logical antenna array comprising a set of antenna elements or antenna ports that share a common or a significant portion of an RF chain (e.g., in-phase/quadrature (I/Q) modulator, analog to digital (A/D) converter, local oscillator, phase shift network). Communicating (receiving or transmitting) on at least a subset of antenna elements or antenna ports active for radiating energy (also referred to herein as active elements) of an antenna panel requires biasing or powering on of the RF chain which results in current drain or power consumption in the UE associated with the antenna panel (including power amplifier/low noise amplifier (LNA) power consumption associated with the antenna elements or antenna ports). The phrase “active for radiating energy,” as used herein, is not meant to be limited to a transmit function but also encompasses a receive function. Accordingly, an antenna element that is active for radiating energy may be coupled to a transmitter to transmit radio frequency energy or to a receiver to receive radio frequency energy, either simultaneously or sequentially, or may be coupled to a transceiver in general, for performing its intended functionality. Communicating on the active elements of an antenna panel enables generation of radiation patterns or beams.

A panel may be a panel antenna or an antenna panel. A panel may comprise one or more radio frequency antenna. A panel may be a hardware (e.g., a logical) component/entity comprising a set of radio frequency antenna. A panel may be a group of antenna. A panel may be a set of antenna. A panel may be a set of reference signals. A panel may be a set of properties (e.g., QCL properties) based on one or more reference signals. A panel may be a group/set of beams (e.g., TCI states, spatial relation information). A panel may be a set of antenna ports. A panel may be a set of antenna/MIMO layers. A panel may be a set of reference signals. A panel may be a set of resources related to spatial domain filter parameters. A panel may be a set of spatial domain filter parameters. A panel may be a set of resources comprising reference signal(s). A panel may be an uplink panel for transmitting uplink signals. A panel may be a downlink panel for receiving downlink signals. For example, a panel may be both uplink and downlink panel for receiving downlink signals and transmitting uplink signals.

A wireless device with multiple panels may determine a panel index for a panel of the multiple panels. Each panel may be a logical entity comprising/associated with a set of reference signals, where the logical entity may comprise one or more physical hardware components/antenna arrays.

In an example, a wireless device may have an active panel, where the wireless device is able to use a TCI state/spatial relation information/spatial domain filter parameter/reference signal/antenna/layer of a set of TCI states/spatial relation information/spatial domain filter parameters/reference signals/antenna/layers associated with the panel without activating the panel (e.g., without additional delay, with zero delay, immediately). The panel may be active when the wireless device may use a TCI state/spatial relation information/spatial domain filter parameter/reference signal/antenna/layer of a set of TCI states/spatial relation information/spatial domain filter parameters/reference signals/antenna/layers associated with the panel with zero delay.

The panel may be inactive when the wireless device may be able to use a TCI state/spatial relation information/spatial domain filter parameter/reference signal/antenna/layer of a set of TCI states/spatial relation information/spatial domain filter parameters/reference signals/antenna/layers associated with the panel after activating the panel (or activating the set of TCI states/spatial relation information/spatial domain filter parameters/reference signals/antenna/layers). The wireless device may need a processing time to activate the inactive panel. The TCI state/spatial relation information/spatial domain filter parameter/reference signal/antenna/layer may be available after the processing time.

A wireless device may activate a panel. The wireless device may be able to use a corresponding set of antenna of the activated panel. The wireless device may transmit an uplink signal via an active panel at a given time. The wireless device may switch from a first active panel to a second active panel. The wireless device may switch a first set of antenna to a second set of antenna in response to switching to the second active panel. The wireless device may require a panel activation latency in switching to the second panel or switching an active panel for a transmission.

The wireless device may have one or more active panels. The wireless device may use an active panel for a transmission at a given time. The wireless device may require an inter-panel transmission latency between two consecutive transmissions comprising a first transmission via a first active panel and a second transmission via a second active panel. The inter-panel transmission latency may be smaller than the panel activation latency.

In the specification, a spatial relation information may comprise a reference signal. A spatial relation information may be referred as a TCI state, a QCL reference signal, a spatial domain filter parameter.

Transmission and reception with multiple TRPs and/or multiple panels may improve system throughput and/or transmission robustness for a wireless communication in a high frequency (e.g., above 6 GHz). For example, a TRP of a plurality of TRPs (or a coreset pool of a plurality of coreset pools) and a panel of a plurality of panels may be associated. For example, the wireless device may receive via the TRP and transmit via the panel that is associated with the TRP when the wireless device communicates with a base station via a TRP. For example, a first TRP of the plurality of TRPs may be associated with a first panel of the plurality of panels based on RRC/MAC-CE/DCI signaling. For example, a TRP with an index may be associated with a panel with the index. For example, a TRP with a coreset pool index may be associated with a panel configured with the coreset pool index. For example, a TRP with a coreset pool index may be associated with a panel with one or more PUCCH resources configured with the coreset pool index.

In an example, a TRP of multiple TRPs of the base station may be identified by at least one of: a TRP identifier (ID), a cell index, or a reference signal index. In an example, a TRP ID of a TRP may comprise a control resource set group (or pool) index (e.g., CORESETPoolIndex) of a control resource set group from which a DCI is transmitted from the base station on a control resource set. In an example, a TRP ID of a TRP may comprise a TRP index indicated in the DCI. In an example, a TRP ID of a TRP may comprise a TCI state group index of a TCI state group. A TCI state group may comprise at least one TCI state with which the wireless device receives the downlink transport blocks (TBs), or with which the base station transmits the downlink TBs.

In an example, a base station may be equipped with multiple TRPs. The base station may transmit to a wireless device one or more RRC messages comprising configuration parameters of a plurality of CORESETs on a cell (or a BWP of the cell). A CORESET of the plurality of CORESETs may be identified with a CORESET index and may be associated with (or configured with) a CORESET pool (or group) index. One or more CORESETs, of the plurality of CORESETs, having a same CORESET pool index may indicate that DCIs received on the one or more CORESETs are transmitted from a same TRP of a plurality of TRPs of the base station. The wireless device may determine receiving beams (or spatial domain filters) for PDCCHs/PDSCHs based on a TCI indication (e.g., DCI) and a CORESET pool index associated with a CORESET for the DCI.

In an example, a wireless device may receive multiple PDCCHs scheduling fully/partially/non-overlapped PDSCHs in time and frequency domain, when the wireless device receives one or more RRC messages (e.g., PDCCH-Config IE) comprising a first CORESET pool index (e.g., CORESETPoolIndex) value and a second COESET pool index in ControlResourceSet IE. The wireless device may determine the reception of full/partially overlapped PDSCHs in time domain when PDCCHs that schedule two PDSCHs are associated to different ControlResourceSets having different values of CORESETPoolIndex.

In an example, a wireless device may assume (or determine) that the ControlResourceSet is assigned with CORESETPoolIndex as 0 for a ControlResourceSet without CORESETPoolIndex. When the wireless device is scheduled with full/partially/non-overlapped PDSCHs in time and frequency domain, scheduling information for receiving a PDSCH is indicated and carried by the corresponding PDCCH. The wireless device is expected to be scheduled with the same active BWP and the same SCS. In an example, a wireless device can be scheduled with at most two codewords simultaneously when the wireless device is scheduled with full/partially overlapped PDSCHs in time and frequency domain.

In an example, when PDCCHs that schedule two PDSCHs are associated to different ControlResourceSets having different values of CORESETPoolIndex, the wireless device is allowed to the following operations: for any two HARQ process IDs in a given scheduled cell, if the wireless device is scheduled to start receiving a first PDSCH starting in symbol j by a PDCCH associated with a value of CORESETpoolIndex ending in symbol i, the wireless device can be scheduled to receive a PDSCH starting earlier than the end of the first PDSCH with a PDCCH associated with a different value of CORESETpoolIndex that ends later than symbol i; in a given scheduled cell, the wireless device can receive a first PDSCH in slot i, with the corresponding HARQ-ACK assigned to be transmitted in slot j, and a second PDSCH associated with a value of CORESETpoolIndex different from that of the first PDSCH starting later than the first PDSCH with its corresponding HARQ-ACK assigned to be transmitted in a slot before slot j.

In an example, if a wireless device configured by higher layer parameter PDCCH-Config that contains two different values of CORESETPoolIndex in ControlResourceSet, for both cases, when tci-PresentInDCI is set to ‘enabled’ and tci-PresentInDCI is not configured in RRC connected mode, if the offset between the reception of the DL DCI and the corresponding PDSCH is less than the threshold timeDurationForQCL, the wireless device may assume that the DM-RS ports of PDSCH associated with a value of CORESETPoolIndex of a serving cell are quasi co-located with the RS(s) with respect to the QCL parameter(s) used for PDCCH quasi co-location indication of the CORESET associated with a monitored search space with the lowest CORESET-ID among CORESETs, which are configured with the same value of CORESETPoolIndex as the PDCCH scheduling that PDSCH, in the latest slot in which one or more CORESETs associated with the same value of CORESETPoolIndex as the PDCCH scheduling that PDSCH within the active BWP of the serving cell are monitored by the wireless device. If the offset between the reception of the DL DCI and the corresponding PDSCH is less than the threshold timeDurationForQCL and at least one configured TCI states for the serving cell of scheduled PDSCH contains the ‘QCL-TypeD’, and at least one TCI codepoint indicates two TCI states, the wireless device may assume that the DM-RS ports of PDSCH of a serving cell are quasi co-located with the RS(s) with respect to the QCL parameter(s) associated with the TCI states corresponding to the lowest codepoint among the TCI codepoints containing two different TCI states.

In an example, a wireless device, when configured with multiple panels, may determine to activate (or select) one of the multiple panels to receive downlink signals/channels transmitted from one of multiple TRPs of the base station. The activation/selection of one of the multiple panels may be based on receiving downlink signaling indicating the activation/selection or be automatically performed based on measuring downlink channel qualities of one or more reference signals transmitted from the base station.

In an example, the wireless device may apply a spatial domain filter to transmit from a panel of the multiple panels to one of the multiple TRPs of the base station, the panel and the spatial domain filter being determined based on at least one of: an UL TCI indication of a DCI, a panel ID in the DCI, a SRI indication of a DCI, a CORESET pool index of a CORESET for receiving the DCI, and the like.

In an example, when receiving a DCI indicating an uplink grant, the wireless device may determine a panel and a transmission beam (or spatial domain transmission filter) on the panel. The panel may be explicitly indicated by a panel ID comprised in the DCI. The panel may be implicitly indicated by an SRS ID (or an SRS group/pool index), a UL TCI pool index of a UL TCI for uplink transmission, and/or a CORESET pool index of a CORESET for receiving the DCI.

In an example, a wireless device may complete a beam failure recovery (BFR) procedure for a primary cell of a first cell group or a primary cell of a second cell group (e.g., PSCell, SPCell) or a secondary cell. The beam failure recovery procedure may be for a cell or a coreset pool of the cell. For example, the wireless device may complete the beam failure recovery procedure by receiving an explicit or implement acknowledgement from a base station. For example, when the wireless may trigger a contention-free random access procedure for the BFR procedure. The wireless device may consider receiving a DCI, based on a first RNTI such as C-RNTI, comprising resource assignment in response to a preamble transmission of the contention-free random access, as an implicit acknowledgement of the BFR (e.g., transmission of one or more candidate beams). For example, when the wireless device may trigger a contention based random access procedure for the BFR procedure, the wireless device may consider receiving a DCI, based on the first RNTI and via a recovery coreset (e.g., identified by recoveryCoresetId) or a recovery search space (e.g., identified by recoverySearchSpaceId), as an implicit acknowledgement of the BFR procedure. In an example, the wireless device may transmit a scheduling request (e.g., a dedicated SR) to initiate the BFR procedure. The wireless device may receive an UL grant, comprising a HARQ process ID, scheduling a PUSCH. The wireless device may transmit a candidate beam via the PUSCH. When the wireless device receives another UL grant, comprising the HARQ process ID with NID bit toggled, the wireless device may consider the BFR procedure is completed.

After the BFR is successfully completed, the wireless device may perform the followings for various coresets and PUCCH resources. For example, after K symbols after completing the BFR (e.g., K=28), the wireless device may transmit a PUCCH based on a PUCCH resource, wherein a spatial domain filter parameter of the PUCCH may be determined based on a last PRACH transmission if the BFR procedure is performed based on a random access procedure. For example, after K symbols after completing the BFR (e.g., K=28), the wireless device may determine a TCI state of a coreset #0 (a coreset with index=0) as a first TCI state used for the recovery coreset if the BFR procedure is performed based on a random access procedure. For example, when the wireless device may have transmitted a candidate beam via a PUSCH (e.g., the BFR is triggered by transmitting a SR), after K symbols after completing the BFR (e.g., K=28), the wireless device may determine a second TCI state of a coreset (e.g., an active BWP of a cell of the BFR), based on the candidate beam. For example, when the wireless device may have transmitted a candidate beam via a PUSCH (e.g., the BFR is triggered by transmitting a SR), after K symbols after completing the BFR (e.g., K=28), the wireless device may determine a second TCI state of a PUCCH resource based on the candidate beam.

Note that coresets and/or PUCCH resources mentioned in above may refer to one or more coresets and/or one or more PUCCH resources configured for active DL/UL BWP of a cell where the BFR occurs for the cell or a candidate beam for the cell has been reported.

In an example, a TCI state of a coreset may be determined, after K symbols after completing the BFR, based on a TCI state used for monitoring a RAR or used for a recovery coreset if the BFR has been performed based on a random access procedure, or a second TCI based on a candidate beam. In an example, a TCI state of a PUCCH resource may be determined, after K symbols after completing the BFR, based on a TCI state used for a preamble transmission if the BFR has been performed based on a random access procedure, or a second TCI based on a candidate beam.

In an example, a base station and a wireless device may support a second mode (e.g., second TCI indication mechanism, a second spatial domain filter update mechanism, a second type, a common beam update, beamUpadate-Type2) to update and/or apply a TCI state for a downlink channel or an uplink channel. In a second mode, a TCI state (e.g., a DL TCI, a common DL TCI state, a common DL TCI) may be applied to one or more downlink channels such as PDCCH and PDSCH. A second TCI state (e.g., an UL TCI, a common UL TCI state, a common UL TCI) may be applied to one or more uplink channels such as PUSCH and PUCCH. The TCI state may be same as the second TCI state. Each TCI state may be different per serving cell. A TCI state may be shared over one or more serving cells. For example, a base station may indicate a DL TCI state (e.g., DL common beam, a separate DL TCI state, a joint DL TCI state) for downlink channels/signals such as PDCCH, PDSCH and CSI-RS transmission. The base station may indicate the DL TCI state via a DCI or a MAC CE. The base station may update the DL TCI state via another DCI or another MAC-CE. The base station may indicate a UL TCI state (e.g., UL common beam, a separate UL TCI state, a joint UL TCI state) for uplink channels/signals such as PUCCH, PUSCH and SRS. The base station may indicate the UL TCI via a DCI or a MAC CE. The base station may update the UL TCI state via another DCI or another MAC-CE. For example, the base station may indicate a first DL TCI state for downlink for a first coreset pool and a second DL TCI state for downlink for a second coreset pool, when the wireless device is configured with a plurality of coreset pools. When the wireless device is configured with a single coreset pool or not configured with a coreset pool, the wireless device may apply the DL TCI state for a cell. In an example, the base station may indicate a plurality of DL TCI states for downlink. The base station may indicate a plurality of UL TCI states for uplink. A DL TCI state may be same as a UL TCI state where a common beam may be used for both downlink and uplink.

The base station may transmit one or more RRC messages comprising configuration parameters. The configuration parameters may indicate a set of TCI states for downlink and uplink or a first set of TCI states for downlink and a second set of TCI states for uplink. The base station may configure a joint set of TCI states for downlink and uplink of a cell. The base station may configure separate set of TCI states for downlink of the cell and the uplink of the cell, respectively. For example, the second mode may not be applied to a supplemental uplink of the cell, if the supplemental uplink is configured/associated with the cell.

FIG. 25 shows an example of a second mode to update and/or apply a TCI state for downlink of a cell or uplink of the cell. The base station may transmit one or more RRC messages or MAC CE messages to indicate/comprise configuration parameters. The configuration parameters may comprise/indicate at least one set of TCI states. For example, when a single or joint TCI state is applied for downlink of a cell and uplink of the cell jointly/unified manner, the configuration parameters indicate/comprise a set of TCI states for the cell. The set of TCI states may be applied to downlink and uplink of the cell. When a first TCI state of downlink of the cell may be independently indicated or separately indicated or separately configured or separately enabled from a second TCI state of uplink of the cell, the configuration parameters may indicate a first set of TCI states for the downlink and a second set of TCI states for the uplink of the cell respectively. For a notation, a DL TCI state may refer a TCI state used for receiving downlink signals/channels of a cell when the base station independently indicates TCI states for DL and UL of the cell. Similarly, a UL TCI may refer a TCI state used for transmitting uplink signals/channels of the cell when independent indication is used. When a joint indication between DL and UL of the cell is used (e.g., a common TCI is applied to downlink and uplink), a joint TCI state may refer a TCI state used for both downlink signals/channels of the cell and uplink signals/channels of the cell.

In an example, a TCI state (e.g., a DL TCI state, a UL TCI state or a joint TCI state) may comprise at least one source RS, where the at least one source RS may provide a reference (e.g., a spatial-domain reference, a reference for a QCL type and/or a spatial relation, or a QCL assumption for the wireless device, etc.) for determining a QCL (relationship) and/or a spatial (domain) filter. In an example, the at least one TCI state (e.g., a DL TCI state, a UL TCI state or a joint TCI state) may indicate (e.g., be associated with, or comprise, etc.) at least one TRP ID (e.g., a cell index, a reference signal index, a CORESET group (or pool) index (e.g., CORESETPoolIndex), or a CORESET group (or pool) index of a CORESET group from which the at least one TCI state is indicated/signaled, etc.), where the at least one source RS (e.g., transmitted from a TRP identified by the at least one TRP ID) may provide a reference (e.g., a spatial-domain reference, a reference for a QCL type and/or a spatial relation, or a QCL assumption for the wireless device, etc.) for determining a QCL (relationship) and/or a spatial (domain) filter. For example, a TCI state may be indicated for downlink and/or uplink for a TRP or a panel of a cell. For example, for a cell, a first TCI state may be used for a first TRP/panel and a second TCI state may be used for a second TRP/panel. For example, a TCI may be indicated for a cell regardless of a plurality of coreset pools or a single coreset pool (or multi-TRPs or a single TRP). A single TCI state may be used for a plurality of serving cells with a same coreset pool index. A single TCI state may be used for a plurality of serving ells regardless of coreset pool index. A single TCI state may be use for both downlink and uplink channels/signals. A single TCI may be used only for downlink or uplink operation.

In an example, one or more TCI states (e.g., M TCI states) may be used for downlink signals/channels of a cell. One or more reference signals of the one or more TCI states may provide common QCL information at least for reception (e.g., device-dedicated reception, UE-dedicated reception, etc.) on a PDSCH and one or more CORESETs in a serving cell (e.g., an activated serving-cell (configured with a PDCCH monitoring), or a component carrier (CC), etc.). The common QCL information may refer that a QCL property is shared or commonly used for a plurality of downlink/uplink channels/signals such as PDCCH/PDSCH for downlink and PUSCH/PUCCH for uplink. Similarly, one or more TCI states (e.g., N TCI states) may be used for uplink signals/channels of a cell. One or more TCI states (e.g., M TCI states) may be used for downlink signals/channels of a TRP of a cell.

One or more reference signals of the one or more TCI states may provide common QCL information at least for reception (e.g., device-dedicated reception, UE-dedicated reception, etc.) on a PDSCH and one or more CORESETs in a TRP of a serving cell (e.g., an activated serving-cell (configured with a PDCCH monitoring), or a component carrier (CC), etc.). One or more reference signals of the one or more TCI states may provide common QCL information at least for reception (e.g., device-dedicated reception, UE-dedicated reception, etc.) on a PDSCH and one or more CORESETs in a TRP/panel of a plurality of serving cells (e.g., a plurality of activated serving-cell (configured with a PDCCH monitoring), or a plurality of component carriers (CCs), etc.).

Similarly, one or more TCI states (e.g., N TCI states) may be used for uplink signals/channels of a TRP/panel of a cell. One or more TCI states (e.g., N TCI states) may be used for uplink signals/channels of a TRP of a plurality of cells. One or more reference signals of the one or more TCI states may provide common QCL information at least for transmission (e.g., device-dedicated transmission, UE-dedicated transmission, etc.) on a PUSCH and one or more PUCCH resources in a TRP/panel of a plurality of serving cells (e.g., a plurality of activated serving-cell (configured with a PDCCH monitoring), or a plurality of component carriers (CCs), etc.).

In an example, the common QCL information may be applied to at least one CSI-RS resource, e.g., for CSI feedback/reporting, for beam management (configured with a parameter, e.g., repetition), for tracking (configured with a parameter, e.g., trs-Info). In an example, the common QCL information may be applied to determining a PDSCH default beam, e.g., in response to a mode (e.g., the second mode, etc.) for TCI indication (being configured/indicated, etc.) based on the at least one joint TCI. In an example, the wireless device may determine a PDSCH default beam as identical to an indicated (e.g., configured, activated, updated, or selected, etc.) (joint) TCI states, e.g., of the M (joint) TCIs, e.g., in response to a mode (e.g., the second mode, etc.) for TCI indication (being configured/indicated, etc.) based on the at least one TCI state.

In an example, the PDSCH default beam may be used for a PDSCH reception based on certain condition(s), e.g., when a time offset between a reception of a DCI scheduling a PDSCH and a reception of the PDSCH is equal to or lower than a threshold (e.g., Threshold-Sched-Offset), when a CORESET delivering a DCI scheduling a PDSCH is not configured with a higher layer parameter (e.g., TCI-PresentInDCI), when a higher layer parameter (e.g., TCI-PresentInDCI) associated with a CORESET delivering a DCI scheduling a PDSCH is not enabled (e.g. not set as “enabled”, not turned on, or disabled), when an explicit signaling from the base station for enabling the PDSCH default beam is given, or based on a pre-defined/pre-configured rule, etc.

The PDSCH default beam (e.g., for the second mode for TCI indication), as identical to an indicated (e.g., configured, activated, updated, or selected, etc.) (joint) TCI state, e.g., of the M (joint) TCI states, may be different (e.g., independent, or separately, etc.) from a first PDSCH default beam for the first mode which may be as identical to a second TCI-state or a second QCL assumption applied for a CORESET with a lowest ID (e.g., CORESET-specific index being the lowest) or as identical to a third TCI-state with a lowest ID (e.g., among activated TCI-states in a BWP), e.g., TCI-state ID being the lowest among active TCI-states in a BWP.

In an example, a wireless device (e.g., the first wireless device, or the second wireless device, etc.) may receive an indication, e.g., from the base station, etc., of applying a method for determining a PDSCH default beam, where the method may comprise at least one of: a first method for determining a PDSCH default beam, based on the performing the default PDSCH RS selection, etc., e.g., as identical to a second TCI-state or a second QCL assumption applied for a CORESET with a lowest ID (e.g., CORESET-specific index being the lowest) or as identical to a third TCI-state with a lowest ID (e.g., among activated TCI-states in a BWP), e.g., TCI-state ID being the lowest among active TCI-states in a BWP, e.g., as applied based on the first mode for TCI state indication, and a second method for determining a PDSCH default beam as being identical to an indicated (e.g., configured, activated, updated, or selected, etc.) (joint) TCI state, e.g., of the M (joint) TCI states, e.g., as applied based on the second mode for TCI state indication, etc.

In an example, the indication of applying a method for determining a PDSCH default beam, e.g., where the indication may select one method among at least the first method, and the second method, etc., may be received via an RRC message. In an example, the indication of applying a method for determining a PDSCH default beam, e.g., where the indication may select one method among at least the first method, and the second method, etc., may be received via a MAC-CE message (e.g., and/or a dynamic indication via a DCI, etc.).

Example embodiments may improve a flexibility and efficiency in a communication network (e.g., comprising at least a base station and a wireless device, etc.) by selectively applying a mode for TCI indication over at least one channel (e.g., a control channel, a data channel, and a shared channel, etc.) for a wireless device, and/or by selectively applying a method for determining a PDSCH default beam, e.g., based on the base station's efficient operational strategy. Example embodiments may reduce an overhead and a latency in control signaling for TCI indication, based on applying a single TCI-state over multiple channels (e.g., a downlink control channel and a downlink shared channel, etc.), e.g., based on the second mode for TCI indication.

In an example, reference signals of N TCI states (e.g., UL-TCIs, or UL-TCI states, etc.), where N is one or an integer greater than zero, may provide a reference for determining common uplink Tx spatial (domain) filter(s) at least for dynamic-grant-based (or configured-grant based) PUSCH and one or more (device-dedicated, e.g., UL-dedicated) PUCCH resources in a CC (e.g., a serving-cell, etc.). In an example, one or more PUCCH resources of a cell may be protected (e.g., restricted, or kept, etc.) from being affected by the reference for determining common uplink Tx spatial (domain) filter(s). In an example, the common uplink Tx spatial (domain) filter(s) may not be applied (e.g., used, etc.) for the one or more PUCCH resources.

In an example, the one or more PUCCH resources in the CC may be a pre-defined PUCCH resource (e.g., from the lowest indexed PUCCH resource) in the CC, which may be used for a special purpose, e.g., as a secured fallback (or default) PUCCH resource, e.g., when an ambiguity situation (e.g., due to a re-configuration of a control signaling, etc.) arises between a wireless device (e.g., the first wireless device, or the second wireless device, etc.) and the base station.

In an example, the common uplink Tx spatial (domain) filter(s) may be applied to one or more SRS resources in SRS resource set(s), where an SRS resource set of the SRS resource set(s) may be configured for antenna switching, codebook-based uplink, or non-codebook-based uplink, etc. In an example, the common uplink Tx spatial (domain) filter(s) may be applied to at least one SRS resource in an SRS resource set configured for beam management (via a parameter, e.g., usage, set to ‘beamManagement’, etc.), in response to receiving an explicit signaling from the base station for enabling the applying the common uplink Tx spatial (domain) filter(s) to the at least one SRS resource for beam management, or based on a pre-defined/pre-configured rule, etc.

In FIG. 25, the base station transmits one or more RRC messages indicating a set of TCI states at T0. The base station transmits a first control command (e.g., a DCI) indicating one or more first TCI states of the set of TCI states. For example, the DCI may indicate a first TCI state for downlink channels/signals of a cell, and a second TCI state for uplink channels/signals of the cell. For example, the first command or the DCI may indicate one or more TCI states for downlink/uplink channels/signals of the cell. The one or more TCI states may be jointly/commonly used for downlink/uplink channels/signals of the cell. For example, the first command or the DCI may indicate a TCI state for downlink/uplink channels/signals of the cell.

The wireless device receives the first control command at a time T1. At a time T2, the wireless device may update one or more DL TCI states, one or more UL TCI states or one or more joint TCI states for the cell in response to receiving the first control command. For example, T1 and T2 may be same. For example, T2 may occur after processing delay or an offset after T1. The wireless device receives downlink channels/signals (e.g., PDCCH, PDSCH and/or CSI-RS) based on the one or more DL TCI states or the one or more joint TCI states after updating the one or more DL states or the one or more joint TCI states.

The wireless device transmits uplink channels/signals (e.g., PUCCH, PUSCH, and/or SRS) based on the one or more DL TCI states or the one or more joint TCI states after updating the one or more UL states or the one or more joint TCI states. The wireless device receives a second control command (e.g., a second DCI) at a time T3. The wireless device updates the one or more DL TCI states, the one or more UL TCI states or the one or more joint TCI states based on the second control command in response to the receiving.

In the specification, a common beam update mechanism may refer a second mode to update TCI state(s) for downlink and/or uplink channels/signals of a cell. The downlink and/or uplink channels/signals may comprise one or more PDCCHs scheduled via one or more coresets, one or more PDSCHs of the cell, or CSI-RS or one or more PUCCH resources, one or more PUSCHs of the cell, or SRS. For example, the one or more coresets may not comprise a coreset #0 or may not comprise one or more second coresets (e.g., coreset #0, a coreset associated with a search space for SIB/RAR/paging, such as Type0/0A/2-PDCCH CSS). For example, the one or more PUCCH resources may not comprise PUCCH resources (e.g., default PUCCH resources) configured/indicated by SIB message(s). For example, CSI-RS may comprise non-zeropower CSI-RSs used for CSI feedback but may not comprise CSI-RSs for a beam failure measurement.

The common beam update mechanism determines at least one DL TCI state (e.g., at least one DL common beam, at least one common beam) of a TRP (e.g., a coreset pool) of a serving cell, where the wireless device may receive downlink signals/channels (e.g., PDCCH, PDSCH and/or CSI-RS) based on the at least one DCI TCI state from the TRP of the serving cell. The at least one DL TCI state may apply to a plurality of channels based on the common beam update mechanism. Similarly, the common beam update mechanism determines at least one UL TCI state (e.g., at least one UL common beam, at least one common beam) of a TRP (e.g., a coreset pool, a panel associated with the TRP, a panel associated with the coreset pool) of a serving cell.

An example of the common beam update is shown in FIG. 25. The at least one DL TCI of the TRP of the serving cell may be called as a DL TCI state (a common DL beam, a DL common beam, a common DL TCI state) of the TRP (or a coreset pool) of the serving cell. The at least one UL TCI of the TRP (or the panel) of the serving cell may be called as an UL TCI state (a UL common beam, a UL common beam, a common UL TCI state) of the TRP (or a coreset pool) of the serving cell.

In an example, a DL TCI state (a DL common beam, a selected DL TCI state, a DL common TCI state) may comprise a reference signal providing a qcl-TypeD properties for receiving downlink control/data channels/signals. The wireless device may apply/use the qcl-TypeD properties of the reference signal that has QCL-ed with a DM-RS or a CSI-RS of a downlink control/data channel/signal. In an example, a DL TCI state may comprise a plurality of reference signals. For example, the plurality of reference signals may comprise a first reference signal for a first TRP, a second reference signal for a second TRP.

The plurality of reference signals may be used for a repetition of a control channel or for a repetition of a data channel. For example, a data, based on the DL TCI state, may be transmitted via a TRP switching where a first transmission/repetition of the data may be transmitted via the first TRP based on the first reference signal, and a second transmission/repetition of the data may be transmitted via the second TRP based on the second reference signal. In the specifications, the DL TCI state may refer the one or more TCI states, or the one or more reference signals used for receiving a single DCI via a PDCCH or a plurality of PDCCHs.

In the specifications, the DL TCI state may refer the one or more TCI states, or the one or more reference signals used for receiving a transport block via a PDSCH or a plurality of PDSCHs or a PDSCH with a multiple layers, In the specifications, the DL TCI state may refer the one or more TCI states, or the one or more reference signals used for receiving a CSI-RS or a plurality of CSI-RSs,

In an example, a UL TCI state (e.g., an UL common beam, an selected UL TCI state, an UL common TCI state) may comprise a plurality of reference signals. For example, the plurality of reference signals may comprise a first reference signal for a first panel (or a first TRP), a second reference signal for a second panel (or a second TRP). The plurality of reference signals may be used for a repetition of a control channel or for a repetition of a data channel. For example, a data, based on the UL TCI state, may be transmitted via a panel/TRP switching where a first transmission/repetition of the data may be transmitted via the first panel/TRP based on the first reference signal, and a second transmission/repetition of the data may be transmitted via the second panel/TRP based on the second reference signal.

In the specifications, the UL TCI state may refer the one or more TCI states, or the one or more reference signals used for transmitting a single UCI via a PUCCH or a plurality of PUCCHs or a single PUSCH or a plurality of PUSCHs. In the specifications, the UL TCI state may refer the one or more TCI states, or the one or more reference signals used for transmitting a transport block via a PUSCH or a plurality of PUSCHs or a PUSCH with a multiple layers, In the specifications, the UL TCI state may refer the one or more TCI states, or the one or more reference signals used for receiving a SRS or a plurality of SRSs,

A common beam update mechanism is further categorized as separate common beam update mechanism (or independent common beam update mechanism, separate/independent common beam update mechanism, independent/separate common beam update mechanism beamUpdate-Type2-separate, separate-Type2 beam update, separate Type-2 beam update mechanism) and joint (or unified common beam update mechanism, joint/unified common beam update mechanism, unified/joint common beam update mechanism beamUpdate-Type2-joint, joint-Type2 beam update, joint Type-2 beam update mechanism)) common beam update mechanism.

For example, in the separate common beam update mechanism (e.g., separate Type 2 beam update mechanism), the base station may indicate/configure, via RRC signaling, one or more first (or separate) TCI states for DL (e.g., one or more DL common beams, one or more separate DL TCI states, one or more separate DL common beams, a first TCI state pool, a first set of TCI states) and one or more second TCI states for UL (e.g., one or more UL common beams, one or more separate UL TCI states, one or more separate UL common beams, a second TCI state pool, a second set of TCI states) independently/separately in the separate common beam update mechanism.

For example, the first TCI state pool may be configured for DL and the second TCP state pool may be independently configured for the UL. For example, a first MAC CE may indicate an activation of one or more first TCI states for DL. A second MAC CE may indicate an activation of one or more second TCI states for UL. The first MAC CE and the second MAC CE may be a single MC CE or separate MAC CEs. For example, a first DCI may indicate a DL TCI state of the one or more first TCI states, wherein the DL TCI is a common beam for DL. For example, a second DCI may indicate a UL TCI state of the one or more second TCI states, wherein the UL TCI is a common beam for UL.

In the joint common beam update, the base station and the wireless device may determine one or more joint TCI states (e.g., one or more joint DL/UL common beams, one or more joint DL/UL TCI states, one or more DL/UL beams, one or more DL/UL TCI states) for DL and UL.

For example, in the joint common beam update mechanism (e.g., joint Type 2 beam update mechanism), the base station may indicate/configure, via RRC signaling, one or more TCI states (e.g., one or more common beams, one or more common beams, a TCI state pool, a set of TCI states) for DL and UL jointly/commonly. For example, a TCI state pool may be shared between DL and UL. For example, a MAC CE may indicate an activation of one or more joint TCI states for DL and UL.

For example, a DCI may indicate a joint DL/UL TCI state of the one or more joint TCI states, wherein the joint DL/UL TCI state is applied/indicated for the DL and UL. In the joint common beam update, the base station and the wireless device may determine one or more joint TCI states (e.g., one or more joint DL/UL common beams, one or more joint DL/UL TCI states, one or more DL/UL beams, one or more DL/UL TCI states) for DL and UL.

A first mode (e.g., separate, separate/independent, independent/separate) beam update mechanism may refer to an independent mode to update TCI state for a downlink channel or an uplink channel. Separately indication for each downlink channel and/or uplink channel may be used.

In an example, a base station may transmit one or more RRC messages indicating whether the first mode is applied or the second mode is applied for a beam update (e.g., indication of a separate beam update mechanism or a common beam update mechanism). When the second mode is indicated, the one or more RRC messages may further indicate whether to use a joint common beam update between downlink and uplink or a separate common beam update mechanism for DL and UL separately.

In an example, the one or more RRC messages may comprise a parameter to indicate between the joint common beam update mechanism or the separate common beam update mechanism. In an example, a wireless device may determine the joint common beam update mechanism in response to a first set of TCI states (or one or more first TCI states, a first TCI state pool) configured/indicated for downlink (e.g., associated with one or more downlink configuration parameters) being same to a second set of TCI states (or one or more second TCI states, a second TCI state pool) or in response to a single set of TCI states (or a TCI state pool) being configured for DL/UL.

In the example, the wireless device may determine the separate common beam update mechanism in response to the first set of TCI states (or one or more first TCI states, the first TCI state pool) configured/indicated for downlink (e.g., associated with one or more downlink configuration parameters) being same to the second set of TCI states (or one or more second TCI states, the second TCI state pool) or in response to independent TCI state pools being configured for DL and UL respectively.

The common beam mechanism, in the specification, may be applied for a coreset pool of a serving cell, or a serving cell, or a coreset pool of a plurality of serving cells (if configured with simultaneous beam update list(s)), and/or a plurality of serving cells (if configured with simultaneous beam update list(s)).

In an example, a base station may transmit one or more RRC messages indicating configuration parameters. The configuration parameters may indicate repetition of uplink data via multiple beams. For example, the multiple beams may be associated with a plurality of TRPs. For example, the multiple beams may be associated with a plurality of panels. For example, the multiple beams may be associated with a plurality of coreset pools. For example, the multiple beams may be associated with a plurality of SRS resource sets. For example, a beam of the multiple beams may be associated/configured with a TCI state or a spatial relation information. The wireless device may determine a spatial domain filter parameter for the beam based on a reference signal of the TCI state or a reference signal of the spatial relation information.

FIG. 26 illustrates an example embodiment of a multi-beam repetition of an uplink signal as per an aspect of an embodiment of the present disclosure.

The base station may be equipped with a plurality of TRPs (e.g., a first TRP and a second TRP). The wireless device may be equipped with a plurality of panels (e.g., a first panel and a second panel). The wireless device may receive a DCI scheduling an uplink signal, via a repetition of one or more uplink channel transmissions, based on a plurality of beams (e.g., a first beam and a second beam).

For example, a first DCI (DCI #1) may indicate repetition of uplink channels based on a first beam (Beam 1) and a second beam (Beam 2). The first DCI may indicate a cyclic repetition pattern for the repetition of uplink channels. The uplink channels may be PUSCHs. The uplink channels may be PUCCHs. For example, the first DCI may be an uplink grant. For example, the first DCI may be a downlink scheduling DCI indicating one or more PUCCH resources for the repetition of uplink channels. The repetition of uplink channels may comprise a transport block (for the PUSCHs) or a UCI (for the PUCCHs). For example, the cyclic repetition pattern for the repetition of uplink channels may be configured via a RRC signaling or dynamically indicated by a MAC CE for a PUCCH resource used for the repetition of uplink channels.

The first DCI may indicate two repetitions of an uplink signal. The first DCI may indicate a mapping pattern of the two repetitions via the plurality of beams (e.g., cyclic mapping pattern). Based on the cyclic mapping pattern, the wireless device may map a first repetition via a first beam of the plurality of beams and a second repetition via a second beam of the plurality of beams. When a number of repetitions is greater than two, the wireless device may map the first beam and the second beam via each repetition in a round-robin manner (e.g., alternate the first beam and the second beam in respective repetition). The first DCI may indicate an inter-beam gap. For example, the wireless device may apply the inter-beam gap between consecutive repetitions mapping to the plurality of beams. For example, the inter-beam gap may be applied in each repetition based on the cyclic mapping pattern as a beam is changed in each repetition.

The inter-beam gap may be one of category 1 (or small) gap, category 2 (or large) gap, category 3 (activation latency) and zero. For example, the category 1 gap may be one symbol. The wireless device may determine no transmission of 1 symbol, based on the category 1 gap, between two consecutive repetitions via the plurality of beams. For example, the category 2 gap may be M symbols (e.g., M=2 or 3). The wireless device may determine no transmission of M symbols, based on the category 2 gap, between two consecutive repetitions via the plurality of beams. For example, when no gap is assumed, the wireless device may determine continuous transmissions between two consecutive repetitions. The category 3 (activation latency) may refer a panel activation latency to activate a panel. The category 3 may be larger than category 2 and may be a slot duration.

The wireless device may receive a second DCI (DCI #2) indicating a third beam (Beam 3) and a fourth beam (Beam 4). The second DCI may indicate four repetitions of uplink channels (e.g., #3, #4, #5 and #6). The uplink channels may comprise an uplink signal (e.g., transport block, UCI). A second inter-beam gap may be indicated for the four repetitions of the uplink channels. The second DCI may indicate a sequential mapping pattern for the repetition. For example, the wireless device may transmit first half number of repetitions via the third beam (e.g., first indicated beam by the second DCI) and may transmit second half number of repetitions via the fourth beam.

The wireless device may determine first half number of repetitions as ceil (# of repetitions/2). For example, when a number of repetitions (e.g., # of repetitions) is four, the first half number of repetitions may correspond to first two repetitions of the four repetitions. The wireless device may determine second half number of repetitions as the remainder (e.g., repetitions excluding the first half number of repetitions).

The wireless device may transmit one or more first/earliest repetitions via first beam indicated by the second DCI. The wireless device may transmit remaining one or more repetitions via second beam indicated by the second DCI.

When a DCI indicates more than two beams, the wireless device may apply each repetition, from first to last, in each beam in a round robin manner based on the cyclic mapping pattern. When a DCI indicates more than two beams, the wireless device may apply first ceil (N/M) repetitions via first beam, second ceil (N/M) repetitions via second beam, and so on. Last beam may have less than ceil (N/M) repetitions. For example, N is a number of repetitions. M is a number of beams indicated by the DCI.

In an example, the first DCI may be an uplink grant scheduling repetition of a transport block via a plurality of PUSCHs. The first DCI may comprise a first SRI field and a second SRI field. The first SRI field may indicate an index for the first beam (e.g., a reference RS of the first beam may be a spatial relation information of a first SRS resource indicated by the index). The second SRI field may indicate a second index for the second beam. The second index may indicate a second SRS resource.

The configuration parameters may comprise/indicate a first SRS resource set. The first SRS resource may comprise one or more first SRS resources comprising the first SRS resource. The configuration parameters may comprise/indicate a second SRS resource set. The second SRS resource set may comprise one or more second SRSs comprising the second SRS resource set. For example, a first usage of the first SRS resource set is ‘non-codebook’ and a second usage of the second SRS resource set is ‘non-codebook’. For example, a first usage of the first SRS resource set is ‘codebook’ and a second usage of the second SRS resource set is ‘codebook’. The first SRI field may indicate an SRS resource of the one or more first SRS resources. The second SRI field may indicate an SRS resource of the one or more second SRS resources.

The first SRI field may indicate a reserved state indicating no transmission via the first SRS resource set. For example, the reserved state may be set to ‘00’ or ‘11’. The second SRI may indicate the reserved state indicating no transmission via the second SRS resource set. When the first SRI being set to the reserved state or the second SRI field being set to the reserved state, the wireless device may transmit repetition via a single beam.

The wireless device may determine the first beam based on the first SRS resource indicated by the first SRI field. The wireless device may determine the first beam based on a spatial relation information of the first SRS. The wireless device may determine the first beam based on an associated CSI-RS of the first SRS resource (or the first SRS resource set). The wireless device may determine the first beam based on a UL TCI state associated with the first SRS resource set. The wireless device may determine the first beam based on a common UL beam of the first SRS resource or the first SRS resource set. The first beam may be quasi-collocated (or have QCL property) to a reference signal of the spatial relation information or the associated CSI-RS or a reference signal of the UL TCI state or a reference signal of the common UL beam.

The wireless device may determine the second beam in a same manner to the first beam based on the second SRI field and the second SRS resource and/or the second SRS resource set.

In an example, the second DCI may schedule a downlink data and indicate a PUCCH resource (e.g., via a PUCCH-resource-indicator PRI field). The configuration parameters may indicate two spatial relation information (e.g., PUCCH-SpatialRelationInfo) for the PUCCH resource.

A spatial relation information for a PUCCH resource (PUCCH-SpatialRelationInfo) may comprise a pucch-SpatialRelationInfold (e.g., an index of the spatial relation information) and a reference signal (e.g., one of SSB, CSI-RS, and SRS). The spatial relation information may additionally comprise a serving cell index (ServCellIndex) for the corresponding reference signal.

The configuration parameters may indicate a list of PUCCH-SpatialRelationInfo for the PUCCH resource. The base station may transmit a MAC CE indicating/activating one or more PUCCH-SpatialRelationInfo of the list of PUCCH-SpatialRelationInfo. The wireless device may determine a first activated PUCCH-SpatialRelationInfo for the third beam by the second DCI. The wireless device may determine a second activated PUCCH-SpatialRelationInfo for the fourth beam by the second DCI.

The wireless device may determine the third beam as a reference signal of the first activated PUCCH-SpatialRelationInfo. The wireless device may determine the fourth beam as a reference signal of the second activated PUCCH-SpatialRelationInfo.

The configuration parameters may indicate a first list of PUCCH-SpatialRelationInfo for the third beam. The configuration parameters may indicate a second list of PUCCH-SpatialRelationInfo for the fourth beam. The base station may transmit a MAC CE activating a first PUCCH-SpatialRelationInfo of the first list of PUCCH-SpatialRelationInfo and a second SpatialRelationInfo of the second list of PUCCH-SpatialRelationInfo. The wireless device may determine the third beam based on the first PUCCH-SpatialRelationInfo. The wireless device may determine the fourth beam based on the second PUCCH-SpatialRelationInfo.

The wireless device may determine the third beam as a reference signal of the first PUCCH-SpatialRelationInfo. The wireless device may determine the fourth beam as a reference signal of the second PUCCH-SpatialRelationInfo.

In an example, a wireless device may be equipped with a plurality of panels, where a panel of the plurality of panels is a hardware component/entry. The wireless device may activate a panel or deactivate the panel. Each panel may comprise a set of radio frequency antennas. Each panel may support a set of spatial domain filter parameters or support a set of uplink beams.

For a downlink beam, the wireless device may support a corresponding uplink beam, to the downlink beam, based on a first panel or based on a second panel. For example, the wireless device may be able to support the corresponding uplink beam based on the first panel at a first time. When the wireless device moves or changes hardware parameters/antenna configuration parameters, the wireless device may support the corresponding uplink beam based on the second panel at a second time. A set of first beams supported via the first panel may change over time. A set of second beams supported via the second panel may change over time.

When a base station schedules a repetition of an uplink signal via a plurality of beams, the base station may not know how each beam of the plurality of beams is associated with one or more panels of a wireless device. For example, a DCI may indicate the repetition via a first beam and a second beam. The first beam may be associated with a first panel and the second beam may be associated with a second panel. The first beam and the second beam may be associated with the first panel.

During repetition, based on a TDM multiplexing among repetitions via the plurality of beams, the wireless device may switch from the first beam to the second beam (or vice versa). A required processing latency to switch from the first beam to the second beam may be different depending on association of the beams and the panels. For example, when the first beam and the second beam are associated with a single panel, the required processing latency may be small (e.g., 5 us). For example, when the first beam is associated with the first panel and the second beam is associated with the second panel and the second panel is active state, the required processing latency may be larger (e.g., 30 us). For example, when the second panel is inactive state, the required processing latency may also include a panel activation switching latency and thus the latency may be increased (e.g., a slot or a few slots).

Depending on the association, a required inter-beam latency may be different. Assuming a worst case latency for each repetition of uplink signals via a plurality of beams may be inefficient as it increases a latency. To allow dynamic indication of a minimum gap for the inter-beam repetition, the wireless device and the base station may need to align on the association between beams and the panels. The base station may need to be aware of the association and/or status of the panels.

In existing technologies, a wireless device may indicate an associated panel for a reference signal (e.g., SSB or NZP-CSI-RS) via a CSI feedback. The associated panel may indicate an active panel, of the wireless device, that is used for retransmitting uplink signals based on the reference signal (e.g., via a spatial relation information comprising the reference signal). A base station may assume that the associated panel may be active at least for a time duration T after receiving the CSI feedback. The base station may acquire information of an active panel for the reference signal based on the CSI feedback. Implementation of existing technologies may not indicate a panel information of a second reference signal where a CSI feedback for the second reference signal has not been triggered/transmitted for more than the time duration T. The base station may need to send a CSI feedback request for the second reference signal to acquire information of the corresponding panel.

When a base station transmits a DCI indicating a first beam and a second beam, the base station may not know the status of one or more panels associated with the first beam and the second beam. For example, when the base station may have received a first CSI feedback for the first beam within the time duration T and a second CSI feedback for the second beam within the time duration T, the base station may be able to determine that the one or more panels are active. Based on the determining, the base station may indicate a small gap between repetitions of an uplink signal via the first beam and the second beam. Implementation of existing technologies may not provide panel status information for one or more SRS resources where a reference signal of the one or more SRS resources is an SRS. The base station may not be able to determine a proper inter-beam latency when a beam of the one or more SRS resources is indicated. Implementation of existing technologies may increase overhead of CSI feedback, particularly for repetition of uplink signals as the base station may need to keep track of multiple beams and request CSI feedbacks for the multiple beams.

In an example, a wireless device may be required to activate one or more panels, where each of the one or more panels supports/is associated with/is used for a spatial relation information of an SRS resource or a PUCCH resource. The spatial relation information may be configured by RRC signaling. The wireless device may need to activate a panel regardless of whether a beam/spatial relation information supported by the panel may be used or not.

When the base station configures multiple uplink beams associated with multiple panels, the wireless device may need to activate the multiple panels regardless of actual usage of the multiple beams.

For example, a PUCCH resource may be configured with a plurality of spatial relation information where a spatial relation information may be associated with an inactive panel. The base station may activate a second spatial relation information of the plurality of spatial relation information for the PUCCH resource, where the second spatial relation information is associated with an active second panel. Based on implementation of the example, the wireless device may need to activate the panel associated with the spatial relation information even though the spatial relation information is not activated.

This may increase a power consumption of the wireless device significantly. Some enhancements to determine which panel(s) to activate are needed.

In existing technologies, a wireless device may periodically report a state of a panel via a DCI and/or a MAC CE. This may increase signaling overhead and may lead to ambiguity between the wireless device and a base station. For example, the base station may not receive the report. The base station may determine inaccurate inter-beam latency. For example, the wireless device and the base station may determine one or more spatial relation information of a resource during a time period between a first time when the wireless device may trigger to transmit an updated information and a second time when the base station successfully receives the updated information.

In an example, a wireless device and a base station may determine that the wireless device activates or has activated a panel based on a dynamic signaling of a beam/spatial relation information/TCI state associated with the panel. The beam/spatial relation information/TCI state may be associated with the panel in response to the panel comprising the beam/spatial relation information/TCI state or in response to the panel supporting the beam/spatial relation information/TCI state or in response to the panel supporting spatial domain filter parameter(s) for the beam/spatial relation information/TCI state. The base station and the wireless device may determine the activated panel may be active at least a time duration after the dynamic signaling.

The dynamic signaling may comprise an uplink feedback by the base station where the uplink feedback comprising feedback on the beam/spatial relation information/TCI state. For example, the uplink feedback may comprise a CSI feedback of the beam/spatial relation information/TCI state. For example, the uplink feedback may comprise a PUCCH transmission via the beam/spatial relation information/TCI state. For example, the dynamic signaling may comprise one or more MAC CE activating the beam/spatial relation information/TCI state. For example, the dynamic signaling may comprise one or more uplink grants scheduling uplink data via the beam/spatial relation information/TCI state. Based on dynamic signaling, the wireless device and the base station may determine a state of the panel.

For example, the wireless device and the base station may determine that the wireless device activates a panel in response to sending a CSI feedback or an SRS transmission for a reference signal (e.g., a beam). The wireless device and the base station may determine that the wireless device may maintain active state of the panel at least a time duration T (e.g., an active time duration, an active panel maintenance gap). The wireless device may determine to deactivate the panel after the time duration. A wireless device may determine to activate or deactivate one or more panels for a power saving or based on mobility/radio parameters. Without a rule, the base station may not be able to assume a status of a panel associated with a reference signal.

The wireless device may restart the time duration in response to transmitting an uplink transmission based on the reference signal/beam.

In an example, a wireless device and a base station may determine that the wireless device activates a panel associated with a spatial relation information/reference signal/beam/TCI state in response to receiving a MAC CE activating the spatial relation information/reference signal/beam/TCI state of an uplink resource (e.g., a PUCCH resource or a SRS resource) for uplink signal transmissions (e.g., PUSCH, PUCCH)

For example, the MAC CE may activate a spatial relation information of the SRS resource that may be used for a PUSCH transmission. The MAC CE may activate PUCCH-SpatialRelationInfo of the PUCCH resource. The MAC CE may activate the TCI state as one or more activated TCI state for an UL TCI state (e.g., an uplink common beam).

The base station may determine whether a second panel of a second reference signal is active or not based on one or more CSI feedbacks of the second reference signal/the reference signal and the MAC CE. For example, the base station may determine the second panel of the second reference signal is active in response to the second panel having a same index to the panel and a validity of a mapping information between the second panel and the second reference signal and the panel being activated. For example, the wireless device may determine the validity of the mapping based on a time window/duration since a CSI feedback of the second reference signal (e.g., less than a time duration T being considered valid). The base station may determine the second reference signal is associated with the active second panel. The base station may determine a small (e.g., category 1 or category 2 or zero) latency for a repetition of an uplink signal via the reference signal (e.g., a first beam) and the second reference signal (e.g., a second beam).

Example embodiments may enable maintaining active states of a panel based on a dynamic feedback and/or signaling. Example embodiments may reduce power consumption by reducing unnecessary activated panels. Example embodiments may reduce an inter-beam latency by activating one or more panels which are indicated dynamically via MAC-CE or requested via DCIs (e.g., CSI feedback, SRS transmission).

In existing technologies, a CSI feedback may indicate a mapping of a reference signal/beam and a panel. The CSI feedback may not indicate whether the panel is active or inactive state. The CSI feedback may indicate a status of the panel. The status of the panel may change over time. The base station may not have accurate information of the status of the panel at a time of scheduling a repetition of uplink signals via the reference signal/beam. The status of the panel may determine a latency required for an inter-beam repetition of an uplink signal. The base station may not effectively determine the latency without accurate information of the panel state.

In an example, a wireless device may report a latency (e.g., an inter-beam/repetition latency) for a PUCCH resource via MAC CE in response to receiving a MAC CE updating one or more spatial relation information for the PUCCH resource. The wireless device may report a latency for a pair of two SRIs (two SRI values indicated by a DCI) via MAC CE in response to receiving a MAC CE updating one or more spatial relation information for one or more SRS resources for PUSCHs.

Example embodiments may allow to align required latency between a wireless device and a base station with a low overhead. Example embodiments allow to update latency information based on a dynamic update of one or more beam pairs schedulable by a DCI for data and/or UCI repetition.

In an example, a base station may transmit one or more RRC messages indicating configuration parameters. The configuration parameters may indicate/comprise one or more CSI-RSs (channel state information reference signals) for CSI measurement. The configuration parameters may indicate one or more SSBs for CSI measurement.

The configuration parameters may configure one or more periodic CSI feedback reports, where a CSI feedback report of the one more periodic CSI feedback reports may indicate/comprise a periodic CSI-RS or an SSB. The wireless device may perform measurement on the periodic CSI-RS or the SSB and may report measurement results via a PUCCH resource. The configuration parameters may configure one or more semi-persistent CSI feedback reports, where a CSI feedback report of the one or more semi-persistent CSI feedback reports may indicate/comprise a CSI-RS or an SSB. The configuration parameters may configure one or more aperiodic CSI feedback reports, where a CSI feedback report of the one or more aperiodic CSI feedback reports may indicate/comprise a CSI-RS or an SSB.

The wireless device may measure a reference signal indicated by/associated with a CSI report. The wireless device may report measurement results via a resource configured/scheduled for the CSI report. For example, the wireless device may transmit a periodic CSI feedback report via a PUCCH resource. For example, the wireless device may transmit a semi-persistent CSI feedback report via a configured grant PUSCH resource. For example, the wireless device may transmit an aperiodic CSI feedback report via a PUSCH scheduled by a DCI.

The configuration parameters may comprise/indicate one or more spatial relation information for a PUCCH resource. The configuration parameters may comprise one or more spatial relation information for an SRS resource.

One or more CSI-RSs and/or SSBs may be associated with a plurality of TRPs of the base station. One or more spatial relation information configured for SRS resource(s) and/or PUCCH resources may be associated with a plurality of panels of the wireless device.

A spatial relation information, of a SRS resource or a PUCCH resource, may comprise a reference signal of a CSI-RS or an SSB. For example, when the reference signal is associated with a first TRP of the plurality of TRPs, the wireless device and the base station may determine the reference signal is associated with a first panel of the plurality of TRPs. For example, a first index of the first TRP may be equal to a second index of the first panel. For example, when a spatial relation information comprises an SRS as a reference signal, the wireless device and the base station may assume that the spatial relation information is associated with a panel with an index=0 (e.g., the first panel). In an example, a first RS is associated with a first TRP. A second RS may be associated with the first TRP. The first RS and the second RS may be associated with a first panel with a same index to the first TRP.

In an example, a first RS, of a first TRP, may be associated with a first panel. A second RS, of the first TRP, may be associated with a second panel. Association of a RS with a panel may be determined by the wireless device. The base station may not determine an association between a reference signal and a panel of the wireless device.

In an example, a wireless device may indicate an index of a panel associated with a reference signal. The wireless device may determine the panel based on one or more transmission parameters (e.g., spatial relation information comprising the reference signal). The wireless device may use the panel when the wireless device transmits uplink signal based on the reference signal (or the spatial domain filter parameter based on the reference signal or the spatial domain filter parameter comprising the reference signal). The wireless device may report the panel via a CSI feedback report configured for a downlink CSI-RS (e.g., a SSB or a NZP-CSI-RS) comprising the reference signal.

FIG. 27A illustrates an example association between a reference signal and a panel as per an aspect of an embodiment of the present disclosure. The base station may be equipped with a first TRP (TRP 1) and a second TRP (TRP 2). For example, a first CSI-RS with index 1 (first beam of the first TRP within index 1 in FIG. 27A) may be supported by the first TRP. A second CSI-RS with index 2 (third beam of the first TRP with index 2) may be supported by the first TRP. A third CSI-RS with index 3 (first beam of the second TRP with index 3) may be supported by the second TRP.

For example, CSI-RS may be one of SSB or an NZP-CSI-RS.

The wireless device may be equipped with a first panel (panel 1) and a second panel (panel 2). The wireless device may be configured with a first spatial relation information (e.g., first beam of the first panel with index 1) comprising a first RS. The first RS is associated/mapped with the first CSI-RS. Based on the association/mapping, the first RS may be the first CSI-RS. Based on the association/mapping, the first RS may be based on the first CSI-RS. Based on the association/mapping, the first RS may be a corresponding RS of the first CSI-RS.

The wireless device may be configured with a second spatial relation information (e.g., third beam of the first panel with index 2) comprising a second RS. The second RS may be associated with the third CSI-RS. A first index of a TRP of the third CSI-RS (e.g., the first index=2) may be different from a second index of a panel of the second RS (e.g., the second index=1). The wireless device may determine association between a TRP for a RS and a panel for a spatial relation information associating with the RS.

The wireless device may be configured with a third spatial relation information (e.g., first beam of the second panel with index 3) comprising a third RS. The third RS may be associated with the second CSI-RS of the first TRP.

The wireless device may be configured with a fourth spatial relation information (e.g., third beam of the second panel with index 4) comprising a fourth RS. The fourth RS may be an SRS (e.g., a first SRS, SRS 1). The fourth RS may not be associated with any CSI-RS. The fourth RS may be a source RS of a CSI-RS. For example, the fourth RS is the source RS of the CSI-RS in response to an NZP-CSI-RS of the CSI-RS comprises the fourth RS as a QCL-RS (e.g., the fourth RS is indicated by qcl-InfoPeriodicCSI-RS of the NZP-CSI-RS). An example embodiment of indicating a panel associated with a spatial relation information referenced with a. SRS is illustrated in FIG. 28.

FIG. 27B illustrates one or more CSI reports as per an aspect of an embodiment of the present disclosure. FIG. 27B is based on FIG. 27A.

For example, the wireless device may report a first CSI report (CSI 1) comprising one or more CSI feedback information (e.g., CQI) and a panel associated with a CSI-RS of the first CSI report. For example, the first CSI report may be configured for the first CSI-RS. The wireless device may indicate the first panel as the associated panel with the first CSI-RS. The wireless device may indicate the first panel for the first CSI report.

The wireless device may report a second CSI report (CSI 2) comprising one or more CSI feedback information based on the second CSI-RS (e.g., CQI) and a panel associated with the second CSI-RS. The second CSI report may be configured for the second CSI-RS. The wireless device may indicate the second panel associated with the second CSI-RS. Similarly, the wireless device may indicate the first panel for a third CSI report for the second CSI-RS.

The wireless device may inform a panel information of a CSI-RS via a CSI feedback/report.

FIG. 28 illustrates an example CSI configuration and feedback for a panel indication for an SRS resource as per an aspect of an embodiment of the present disclosure. For example, the base station may transmit one or more RRC messages comprising/indicating configuration parameters. The configuration parameters may indicate a CSI report (e.g., CSI-ReportConfig). The CSI report may be configured for a CSI feedback report. The CSI report may comprise a report index (e.g., reportConfigId), an index of a serving cell where a measurement may be occurring or a reference signal of the report is transmitted (e.g., ServCellIndex), and one or more reference signal needed for the measurement. For example, a reference signal for a channel measurement (e.g., resourceForChannelMeasurement) may comprise a SSB or a CSI-RS. An interference measurement reference signal (e.g., csi-IM-REesourceForinterference or nzp-CSI-RS-ReosurceForInterference) may be configured.

The CSI-ReportConfig may comprise one or more indexes of SRS resources. The CSI-ReportConfig may comprise one or more indexes of SRS resource sets. For example, the CSI-ReportConfig may indicate an index of an SRS resource. The SRS resource may not be indicated/configured with a spatial relation information (e.g., no reference signal is present for the SRS resource). The SRS resource may be configured with a reference signal referring the SRS resource (e.g., spatial domain filter parameter/spatial relation information of the SRS resource is determined based on the SRS resource. For example, the one or more SRS resources may comprise the SRS resource (that is used for a reference for a spatial relation information for a second SRS resource).

For example, the one or more SRS resource sets may comprise an SRS resource set that comprises the SRS resource (e.g., a reference of the spatial relation information of the second SRS resource). When a SRS resource set is configured in a CSI-ReportConfig, the wireless device and the base station may assume that a single panel is used for the SRS resource set.

For example, the wireless device may indicate one or more indexes of one or more panels of the one or more SRS resources (or the one or more SRS resource sets). For example, each of the one or more panels may be associated/configured/supporting each of the one or more SRS resource.

In the example, the wireless device may report a first CSI report (CSI 1) for the first CSI-RS. The CSI-ReportConfig for the first CSI report may comprise a first SRS resource (e.g., the SRS (SRS1) associated with a spatial relation information with index 4 in FIG. 27A). The wireless device may indicate a panel information of the SRS1. For example, the wireless device may indicate the second panel for the first SRS resource.

Based on the CSI feedback report, the base station may acquire a panel information of an SRS resource that is not associated/configured with a downlink reference signal or a CSI-RS.

In an example, a base station and a wireless device may determine a panel reported via a CSI feedback is active. For example, the base station and the wireless device may determine the second panel is active in response to communicating the second CSI report in FIG. 27B. The wireless device may report the CSI feedback after activating the corresponding panel. The wireless device may maintain active state of the corresponding panel after the CSI feedback. For example, the wireless device may maintain an active state of the corresponding panel at least a time duration T (e.g., T_csi). For example, the wireless device may start an active timer, if the active timer is not running, for the corresponding panel in response to transmitting the CSI feedback. The wireless device may restart the active timer for the corresponding panel in each time the wireless device may report a second CSI feedback associated with the corresponding panel. The wireless device may restart the active timer for the corresponding panel in each time the wireless device may receive downlink signal via the panel. The wireless device may restart the active timer for the corresponding panel in each time the wireless device may transmit uplink signal via the panel.

For example, the wireless device may receive downlink signal via a panel in response to a TCI state of the downlink signal being associated with the panel. For example, the wireless device may transmit uplink signal via a panel in response to a TCI state or a spatial relation information or a spatial domain filter parameter of the uplink signal being associated with the panel. A TCI state or a spatial relation information or a spatial domain filter parameter is associated with a panel in response to a reference signal, of the TCI state or the spatial relation information or the spatial domain filter parameter, is supported by/associated with/mapped with the panel. Example embodiment of managing timer is shown in FIG. 33.

In an example, a wireless device may receive a DCI indicating a CSI feedback based on a CSI-RS. The wireless device may determine that a panel associated with the CSI-RS is inactive. The wireless device may determine to activate the panel. The wireless device may start measurement after activating the panel. For example, the DCI may indicate a latency to receive the CSI-RS. The latency may represent a gap between the DCI and one or more transmission of the CSI-RS. The base station may determine the latency sufficiently large to accommodate a potential panel activation delay when the base station may not know a state of the panel associated with the CSI-RS. When the latency is not sufficient to activate the panel, the wireless device may determine not to measure the CSI-RS. The wireless device may indicate ‘out-of-range’ of a CQI (e.g., channel quality indicator) or a reserved CSI feedback value (e.g., CQI=0) indicating the wireless device may not have measured the CSI-RS via the CSI feedback. The wireless device may indicate a previous CSI feedback of the CSI-RS in response to determining not to measure the CSI-RS.

The base station may determine a CSI measurement was unsuccessful in response to receiving the ‘out-of-range’ or the reserved CSI feedback or a same report from the previous CSI feedback. The base station may request a second CSI feedback for the CSI-RS with a sufficient latency to activate the panel.

In an example, a wireless device and a base station may determine a panel is active in response to a SRS transmission associated with the panel.

For example, the base station may acquire association between one or more beams/reference signals and one or more panels of the wireless device. The base station may not be able to determine state(s) of the one or more panels. The base station may trigger an SRS transmission activating a panel associated with the SRS transmission.

FIG. 29 illustrates an example embodiment of a panel activation as per an aspect of an embodiment of the present disclosure.

The base station may acquire mapping/association information between a plurality of RSs and a plurality of panels. For example, the plurality of RSs may comprise a first RS (RS1), a second RS (RS2), a third RS (RS3) and a fourth RS (RS4). The plurality of panels may comprise a first panel (pane #1) and a second panel (panel #2). For example, the first RS and the second RS are associated with the first panel. The third RS and the fourth RS are associated with the second panel.

The base station may configure a periodic or semi-persistent SRS transmission of a first SRS resource associated with the first RS (e.g., the first SRS resource has a spatial relation information comprising the first RS).

The wireless device may transmit a first SRS at a first time (T0). The wireless device and the base station may determine the first panel associated with the first RS becomes active in response to communicating the first SRS. The wireless device may maintain active state of the first panel at least a time duration T (e.g., T_srs) after transmitting the SRS.

To enhance alignment in terms of active time duration, the wireless device may determine the time duration at the time of the first SRS transmission (e.g., update the time duration at transmission of an uplink signal).

The base station may send an SRS trigger for a second SRS resource associated with the third RS (e.g., via a DCI, a MAC-CE) at a second time (T1). The wireless device may receive the SRS trigger. The wireless device may activate the second panel in response o the SRS trigger. The base station may indicate a latency to transmit a second SRS in consideration of a panel activation delay. For example, the SRS trigger may indicate a gap that is equal to or larger than the panel activation delay. For example, the SRS trigger may indicate the transmission of the second SRS at a third time (T2) where T2−T1>=panel activation delay.

The wireless device may activate the second panel and transmit the second SRS via a spatial domain filter parameter of the third RS.

The wireless device may maintain active state of the second panel at least a time duration after transmitting the second SRS (e.g., at T2).

The wireless device may maintain active state of a panel. For example, an index of the panel may be a lowest index (e.g., 0 or 1). For example, an index of the panel may be indicated by a base station. For example, the panel may be determined via an initial access procedure. A panel used in an initial access procedure may be maintained active state regardless of SRS transmission and/or CSI feedback and/or signal communication with the base station.

In an example, a base station may transmit one or more MAC CEs and/or DCIs activating/updating one or more spatial relation information (or reference signal(s) or beam(s) or spatial domain filter parameter(s)) of a PUCCH resource or an SRS resource or an SRS resource set. FIG. 30 and FIG. 31 illustrate example MAC CE format indicating one or more spatial relation information for a PUCCH resource and an SRS resource set.

FIG. 30 illustrates an example MAC CE format activating spatial relation information for a PUCCH resource as per an aspect of an embodiment of the present disclosure.

For example, a MAC CE may be referred as a PUCCH spatial relation activation/deactivation MAC CE. The MAC CE may be identified by a MAC subheader with a LCID for a PUCCH spatial relation activation/deactivation. For example, the MAC CE may comprise a serving cell ID indicating an identify of a serving cell for which the MAC CE applies. For example, the serving cell may comprise a PUCCH resource indicated by a PUCCH resource ID. The MAC CE may comprise a BWP ID indicating an UL BWP for which the MAC CE applies. For example, the UL BWP may comprise the PUCCH resource. The MAC CE may comprise the PUCCH resource ID indicating an index of the PUCCH resource (e.g., PUCCH-ResourceId).

The MAC CE may comprise a G field (e.g., a gap) indicating whether an inter-beam gap is applied or not between consecutive repetition via a plurality of beams. When the G field indicates 1 (e.g., the inter-beam gap is enabled), the wireless device may apply an inter-beam gap value between two consecutive repetitions via a plurality of beams (e.g., when a beam switching occurs between repetitions). The inter-beam gap may be configured via RRC/MAC-CE/DCI signaling.

The MAC CE may comprise a M field (e.g., a hopping pattern, repetition pattern, beam mapping pattern) indicating whether cyclic mapping pattern across beams or sequential mapping pattern across beams is used for the repetitions. For example, M field may indicate 1 for a cyclic mapping pattern. M field may indicate 0 for a sequential mapping pattern. A number of repetitions may be configured via RRC or indicated by DCI for the PUCCH resource.

The MAC CE may comprise a first bitmap (e.g., S0, . . . , S7 in Octet 3) for a first spatial relation information for a first beam. For example, the base station may configure a first set of spatial relation information for the PUCCH resource. The PUCCH resource may be associated with the first set of spatial relation information for the first beam. Each bit of the first bitmap may correspond to each of the first set of spatial relation information. The base station may activate one of the first set of spatial relation information for the first beam. The wireless device may not expect more than one spatial relation information of the first set of spatial relation information is activated.

The MAC CE may comprise a second bitmap (e.g., S0, . . . , S7 in Octet 4) for a second spatial relation information for a second beam. For example, the base station may configure a second set of spatial relation information for the PUCCH resource. For example, the second set of spatial relation information may be same to the first set of spatial relation information. For example, the PUCCH resource may be associated with the second set of spatial relation information for the first beam. Each bit of the second bitmap may correspond to each of the second set of spatial relation information. The base station may activate one of the second set of spatial relation information for the second beam. The wireless device may not expect more than one spatial relation information of the second set of spatial relation information is activated.

For example, when the first set of spatial relation information is same as the second set of spatial relation information, the wireless device may be activated with a same spatial relation information for the first beam and the second beam. The wireless device may determine that a single beam is used for the PUCCH resource in response to the same spatial relation information is activated for the first beam and the second beam.

For example, when the second set of spatial relation information is configured independently from the first spatial relation information, the MAC CE may comprise a T field (e.g., 1 or 2 bits T field). The T field (e.g., a single beam or multi-beam) may indicate whether the PUCCH resource is activated with a single beam only or multiple beams. In case of a single beam, whether a beam is from the first set of spatial relation information or is from the second set of spatial relation information may be indicated. For example, ‘00’ of the T field may indicate a single beam of the first set of spatial relation information. ‘01’ of the T field may indicate a single beam of the second set of spatial relation information. ‘10’ of T field may indicate multi-beams from each of the first set of spatial relation information and the second set of spatial relation information. ‘11’ of the T field may be reserved.

For example, first bit (e.g., G) of the Octet 1 and first bit (e.g., M) of the Octet 2 may be used to indicate a single beam or multi-beam (e.g., T field). For example, one or more bits of Si bit(s) may be used for T field.

For example, a single bitmap of spatial relation information (e.g., S0, . . . , S7) may be used to activate one or more spatial relation information. The wireless device may determine first beam that is activated with a lower index among the one or more spatial relation information. The wireless device may determine second beam that is activated with a higher index among the one or more spatial relation information.

Each Si bit may indicate a PUCCH-SpatialRelationInfo (e.g., a spatial relation information for a PUCCH resource) with an index (PUCCH-SpatialRelationInfold)=i+1. When Si=1, the wireless device may activate a PUCCH-SpatialRelationInfo with index i+1 for the PUCCH resource. When Si=0, the wireless device may deactivate the PUCCH-SpatialRelationInfo with the index i+1.

In an example, when all Si of the first bitmap are zeros, the wireless device may determine that the first beam is not activated. The wireless device may determine that a single beam is used for the PUCCH resource, where the single beam may be activated from the second set of spatial relation information. In an example, when all Si of the second bitmap are zeros, the wireless device may determine that the second beam is not activated. The wireless device may determine that a single beam is used for the PUCCH resource, where the single beam may be activated from the first set of spatial relation information.

In an example, the wireless device may not expect both the first bitmap and the second bitmap are all zeros.

For each bitmap, the wireless device may determine a single bit being set to 1 (e.g., a single beam is activated for each set of spatial relation information).

In an example, a MAC CE may comprise one or more PUCCH resources. The MAC CE may comprise one or more index(es) of spatial relation information, where each index may correspond to each PUCCH resource. For example, the MAC CE may comprise two spatial relation information indexes for a PUCCH resource. First spatial relation information may correspond to a first beam of the PUCCH resource. Second spatial relation information may correspond to a second beam of the PUCCH resource.

FIG. 31 illustrates an example MAC CE format indicating spatial relation information for SRS resource as per an aspect of an embodiment of the present disclosure.

The MAC CE format may refer an enhanced SP/AP SRS spatial relation information MAC CE that is identified by a MAC subheader with a LCID for the semi-persistent/aperiodic SRS spatial relation information. For example, a semi-persistent (SP) or aperiodic (AP) SRS may refer a SRS resource set configured with a resource type being either semi-persistent or aperiodic.

The MAC CE format may comprise A/D field indicating whether to activate or deactivate a SP SRS resource set. The field may be set to 1 to indicate activation of the SP SRS resource set. The field may be set to 0 to indicate deactivation of the SP SRS resource set. When the MAC CE format is for an aperiodic SRS resource set, the A/D field may be ignored (e.g., not used or reserved or filled with zero where the wireless device may not interpret the field).

The MAC CE format may comprise an SRS resource set's cell ID field. The field may indicate an identity of a serving cell. The serving cell may comprise an SRS resource set indicated by the MAC CE format.

The MAC CE format may comprise ‘R’ field that is a reserved bit. The MAC CE format may comprise a ‘C’ field. The C field may indicate whether resource serving cell ID and a resource BWP ID for each resource ID are present or not. When C field is set to 0, the resource serving cell ID and the resource BWP ID for the resource ID may not be present. When C field is set to 1, the resource serving cell ID and the resource BWP ID may be present. When the C field is set to 0, SRS resource set's cell ID may be used for an identifier of a serving cell of one or more resources (e.g., indicated by resource IDi).

The MAC CE format may comprise a SUL field indicating whether a MAC CE based on the MAC CE format applies to a supplemental uplink carrier (SUL) or non-SUL (e.g., normal UL) carrier. The field is set to 1 to indicate the MAC CE applies to the SUL carrier. The field is set to 0 to indicate the MAC CE applies to the normal UL carrier. The SUL or the UL carrier may be associated with a cell with the SRS resource set's cell ID.

The MAC CE format may comprise an SRS resource set ID. The field may indicate an index (e.g., SRS-ResourceSetld) of the SRS resource set the MAC CE is applied. The SRS resource set may be configured with a resource type of semi-persistent or aperiodic.

The MAC CE format may comprise one or more set of {Fi, resource serving cell IDi, resource BWP IDi, resource IDi}. The resource serving cell IDi and resource BWP IDi may be present when the C field indicates 1.

Each set of {Fi, resource serving cell IDi, resource BWP IDi, resource IDi} may correspond to i-th SRS resource of the SRS resource set. For example, F0 may correspond to first SRS resource of the SRS resource set (e.g., a lowest indexed SRS resource). F1 may correspond to second SRS resource of the SRS resource set (e.g., a next lowest indexed SRS resource). For each SRS resource of the SRS resource set, a set may be applied.

Fi may indicate 1 to indicate that a resource ID of the Fi (Resource IDi) is based on an NZP-CSI-RS. When Fi is set to 0, the resource ID of the Fi may indicate an index of a SSB or an index of an SRS resource. The one or more sets may be present only when A/D indicating activation for a SP SRS resource set or for aperiodic SRS resource set.

The resource serving cell IDi may indicate an identity of a serving cell comprising a resource (or a reference signal) indicated by the resource IDi.

The resource BWP IDi may indicate an index of a BWP comprising the resource.

The resource IDi may indicate an index of the resource. When Fi is set to 1, first bit of the resource IDi may be set to 0. When Fi set to 0, first bit of the resource IDi may be set to 1 to indicate a SSB-index based on remained bits. When Fi set to 0, first bit of the resource IDi may be set to 0 to indicate an SRS resource index (e.g., SRS-ResourceId).

For example, the wireless device may be configured with a first SRS resource set for a first beam for uplink signal repetition. The wireless device may be configured with a second SRS resource set for a second beam for the uplink signal repetition. The wireless device may receive a first MAC CE activating spatial relation information for the first SRS resource set. The wireless device may receive a second MAC CE activating spatial relation information for the second SRS resource set.

In an example, a wireless device may receive one or more RRC messages indicating configuration parameters. The configuration parameters may comprise/indicate a first SRS resource set comprising a set of first SRS resources. The configuration parameters may comprise/indicate a second SRS resource set comprising a set of second SRS resources. The first SRS resource set may be used for a first beam of an uplink signal repetition (e.g., data via PUSCH). The second SRS resource set may be used for a second beam of the uplink signal repetition.

For example, the wireless device may receive a MAC CE indicating spatial relation information for the first SRS resource set. For example, based on example in FIG. 27A, the configuration parameters may indicate the first SRS resource set comprise a first SRS resource and a second SRS resource. The configuration parameters may indicate the second SRS resource set comprise a third SRS resource and a fourth SRS resource. The MAC CE may indicate the first SRS resource is associated with the spatial relation information with index 1 (e.g., associated with the CSI RS with index 1). The MAC CE may indicate the second SRS resource is associated with the spatial relation information within index 2 (e.g., associated with CSI RS with index 3).

The spatial relation information with index 1 and index 2 may be associated with the first panel.

The wireless device may maintain active state for the first panel.

The wireless device may maintain active/inactive state for the second panel where the wireless device may not have any spatial relation information (or reference signal), associated with the second panel, being activated.

The wireless device may receive a second MAC CE indicating spatial relation information for the second SRS resource set. For example, the second MAC CE may indicate that the third SRS is associated with a spatial relation information with index 3 (e.g., associated with CS RS with index 2). The second MAC CE may indicate that the fourth SRS is associated with a spatial relation information of an SRS resource (e.g., SRS 1).

The third SRS and the fourth SRS may be associated with the second panel. In response to receiving the second MAC CE, the wireless device may activate the second panel.

For example, the wireless device may transmit a HARQ-ACK feedback for the second MAC CE after activation of the second panel. For example, the base station may indicate or schedule an offset between the second MAC CE (e.g., a PDSCH comprising the second MAC CE) and a PUCCH resource comprising the HARQ-ACK feedback where the offset may be larger than or equal to a panel activation latency.

FIG. 32 illustrates an example diagram of a panel active time as per an aspect of an embodiment of the present disclosure.

The base station may transmit one or more RRC messages. For example, the RRC messages may comprise configuration parameters. The configuration parameters may comprise/indicate a CSI report configuration of a first CSI reference signal (e.g., RS1). The first CSI reference signal (RS1) may be associated with a first panel of the wireless device. For example, the wireless device may determine that the first CSI RS (RS1) and a second RS (RS2) are associated with the first panel. The wireless device may determine that a third RS (RS3) and a fourth RS (RS4) are associated with a second panel.

The wireless device may transmit a CSI report of the first CSI RS at a first time (T0). In response to transmitting the CSI report, the wireless device may start an active time of the first panel. The wireless device may maintain active state of the first panel at least for a time duration (T_csi).

The wireless device may receive a MAC CE activating or indicating a spatial relation information comprising the third RS for an SRS resource set configured for uplink signal transmission. For example, the SRS resource set may be at least one of a first SRS resource set and a second SRS resource set configured for data repetition via multiple beams. For example, the MAC CE may activate or indicate one or more PUCCH spatial relation information for a PUCCH resource. For example, the MAC CE may activate or indicate PUCCH spatial relation information for a plurality of PUCCH resources. The MAC CE may activate/indicate a PUCCH spatial relation information comprising the third RS for a PUCCH resource. The wireless device receives the MAC CE at a second time (T1). The wireless device may determine to activate the second panel in response to the MAC CE activating the third RS associated with the second panel and the second panel is not being active.

For example, the wireless device may activate the second panel within a panel activation delay. The wireless device may transmit a HARQ-ACK feedback (e.g., HARQ feedback) for the MAC CE after activating the second panel. For example, when the wireless device may fail to activate the second panel (e.g., due to some hardware issue, power issue or based on determination not to activate the second panel), the wireless device may transmit negative ACK (NACK) for the MAC CE. The NACK may be used to indicate that the MAC CE was not successful.

In an example, the wireless device may have received data via a PDSCH comprising the MAC CE successfully. The wireless device may generate ACK for the PDSCH. The wireless device may generate NACK for the MAC CE. The wireless device may generate two HARQ-ACK bits for the PDSCH in response to the PDSCH comprising the MAC CE.

In an example, the wireless device may transmit a MAC CE confirmation for the MAC CE activating spatial relation information. The wireless device may not transmit the MAC CE confirmation when the wireless device may not successfully activate the second panel or the wireless device may not successfully apply one or more spatial relation information indicated by the MAC CE.

For example, the MAC CE confirmation may indicate a MAC subheader indicating a PUCCH spatial relation information activation/deactivation or indicating a SP/AP SRS spatial relation information indication. The MAC CE confirmation may indicate a MAC CE subheader of the corresponding MAC CE.

In response to transmitting the HARQ-ACK feedback or the MAC CE confirmation informing a successful activation of the second panel, the wireless device may start active time of the second panel. The wireless device may maintain active state of the second panel at least for a time duration (T_mac_ce). In an example, T_csi may be same as T_mac_ce. T_csi may be same as T_srs. For example, the configuration parameters may comprise/indicate a time duration T that is applied for T_csi, T_mac_ce, and/or T_srs. For example, T_mac_ce (or T_csi, or T_srs) may be configured as X msec, Y slots or Z symbols. A timer may run (or increment) in every milli-second if X msec is configured for T_mac_ce. A timer may run (or increment) in every slot if Y slots is configured for T_mac_ce. A timer may run (or increment) in every symbol if Y symbols is configured for T_mac_ce.

For example, the configuration parameters may comprise/indicate T_csi, T_mac_ce and/or T_srs.

The wireless device may start the time duration in response to transmitting the feedback. This is to align a timing between the base station and the wireless device. The wireless device may start the time duration at an event that the base station is also aware of.

In response to receiving the HARQ-ACK feedback or the MAC CE confirmation, the base station may be able to determine an inter-beam latency (e.g., zero, category 1 or category 2) based on the active state of the second panel.

For example, the base station may assume that the wireless device maintains the active state of the second panel in response to receiving the HARQ-ACK feedback or the MAC CE confirmation.

The base station may determine an inter-beam switching latency between the first RS (RS1) and the third RS (RS3) based on active states of the first panel and the second panel. For example, the base station may determine the inter-beam latency is zero based on both panels being active. For example, the s may determine the inter-beam latency is category 2 based on the first RS being associated with the first panel and the third RS being associated with the second panel.

The base station may transmit an uplink grant scheduling an uplink signal (e.g., a transport block, data) via a plurality of PUSCHs based on the inter-beam latency. For example, the plurality of PUSCHs may be mapped based on a cyclic mapping pattern. The base station may indicate a latency between consecutive PUSCH of the plurality of PUSCHs based on the inter-beam latency.

In an example, when the base station may not be aware of state of a panel associated with a reference signal or when the base station may not be aware of which panel that the reference signal is associated with, the base station may assume a worst latency for the inter-beam latency. For example, the worst latency may comprise a panel activation latency. For example, the base station may indicate an uplink signal repetition based on the worst latency assumption.

In an example, the configuration parameters may comprise/indicate one or more PUCCH resources. For example, the wireless device may determine to maintain active state of a panel when one or more followings may be satisfied. For example, the wireless device may have a PUCCH resource configured with a single spatial relation information. The single spatial relation information may be associated with the panel. The wireless device may maintain the active state of the panel until the PUCCH resource is deconfigured (e.g., maintain active time based on the RRC configuration).

For example, the configuration parameters may indicate two spatial relation information for a PUCCH resource. First spatial relation information of the two spatial relation information may be associated with a first panel. Second spatial relation information of the two spatial relation information may be associated with a second panel. In response to being configured with a single spatial relation information for each beam, the wireless device may determine that the single spatial relation information is activated for the each beam. The wireless device may determine to maintain active state of the first panel and the active state of the second panel in response to the PUCCH resource being configured with single spatial relation information for each beam.

The wireless device may not determine to activate a panel based on a PUCCH resource, for a beam, being configured with a plurality of spatial relation information. The wireless device may expect to receive a MAC CE activating a spatial relation information, of the plurality of spatial relation information, for the PUCCH resource. The wireless device may determine a panel based on the activated spatial relation information. The wireless device may activate the panel in response to the determining.

In an example, a wireless device may receive a MAC CE activating one or more spatial relation information for a PUCCH resource. For example, the MAC CE may activate a first spatial relation information for a first beam of the PUCCH resource. The MAC CE may activate a second spatial relation information for a second beam of the PUCCH resource. The first spatial relation information may be associated with the first panel that is active state. The second spatial relation information may be associated with the second panel that is inactive state.

In response to receiving the MAC CE, the wireless device may activate the second panel. The base station may determine an inter-beam latency of the PUCCH resource as zero or category 2. The base station may indicate whether to assume zero latency or the category 2 latency via the MAC CE activating spatial relation information of the PUCCH resource. When the inter-beam latency is not indicated, the wireless device may determine zero latency if the wireless device is capable of supporting zero latency between beams across multiple panels. Otherwise, the wireless device may assume the category 2 latency.

The wireless device may maintain the active state of the first panel and the second panel until the wireless device may receive a second MAC CE activating spatial relation information of the PUCCH resource. For example, the second MAC CE may activate a second spatial relation information and a fourth spatial relation information for the PUCCH resource. The second spatial relation information and the fourth spatial relation information may be associated with the first panel. In response to the PUCCH resource not being associated with the second panel, and there is no PUCCH resource associated with the second panel, the wireless device may deactivate the second panel.

In an example, the configuration parameters may indicate/comprise a time duration T_mac_ce as infinite (e.g., a large value that may not expire) or a largest time duration. The wireless device may not deactivate the second panel until the T_mac_ce time duration expires. The wireless device may deactivate the second panel when T_mac_ce time duration expires (or an activation timer associated with the second panel is expired).

In FIG. 32, the wireless device may maintain active time for the first panel at least after transmitting the CSI feedback of the first RS associated with the first panel. The wireless device may maintain active time for the second panel at least after transmitting the HARQ-ACK feedback for the MAC CE activating the third RS of the second panel. While both panels active, the base station may determine an inter-beam latency between two beams of two panels as zero or category 2. In an example, the category 2 latency may be same as category 1 (e.g., inter-beam latency may be same for beams of a single beam or beams of multiple panels).

In an example, a wireless device may maintain an activation timer for a panel. For example, the wireless device may determine whether to deactivate the panel based on the activation timer.

The wireless device may be equipped with a plurality of panels comprising a first panel and a second panel. The wireless device may perform initial access procedure based on the first panel. The wireless device may maintain an active state of the first panel in response to the first panel has been activated based on the initial access procedure. The wireless device may not maintain an activation timer for the first panel.

For one or more panels other than the first panel, the wireless device may maintain an activation timer for each panel. For example, the wireless device may determine a first activation timer for the second panel. The wireless device may determine a second activation time for a third panel when the plurality of panels comprises the third panel.

The wireless device may receive configuration parameters. The configuration parameters may indicate a time duration T for an active timer for a panel. For example, the time duration T may be applied for each panel. For example, the configuration parameters may indicate a first time duration for a first panel. The configuration parameters may indicate a second time duration for a second panel.

The wireless device may determine an active time duration T based on a power saving capability/consumption and/or a capability of the wireless device. The wireless device may indicate the active time duration of each panel to the base station. For example, the wireless device may transmit a recommended value of a time duration T. For example, the wireless device may indicate a time duration T via one or more RRC/MAC-CE/UCI signaling.

In an example, the configuration parameters may indicate an active timer for a serving cell. In an example, the wireless device may maintain an active time duration (e.g., activation timer) for a panel of a serving cell. The wireless device may determine to maintain active state of the panel in response to at least one of activation timer, of the panel, of serving cell(s) are running (e.g., active). The wireless device may determine to deactivate the panel in response to all activation timer, of the panel, of the serving cell(s) are stopped or expired.

In an example, the wireless device may maintain an active time duration (e.g., activation timer) for a panel for a cell group. For example, for a panel, the wireless device may determine a first activation timer for a first cell group. The wireless device may determine a second activation timer for a second cell group. The wireless device may deactivate the panel in response to the first activation timer is expired/stopped and the second activation timer is expired/stopped. The wireless device may activate the panel in response to at least one of the first activation timer and the second activation timer is running.

A base station, of the first cell group, may assume that the panel is inactive in response to the first activation timer expires. A second base station, of the second cell group, may assume that the panel is inactive in response to the second activation timer expires. The base station may be same to the second base station. The base station may operate the first cell group and the second cell group.

In an example, a wireless device may receive a MAC CE indicating activating one or more spatial relation information (e.g., one or more reference signals associated with the one or more spatial relation information) for a PUCCH resource. For example, the one or more spatial relation information may comprise a first RS for a first beam and a second RS for a second beam. The wireless device may determine an activation time to activate and use the indicated one or more spatial relation information. For example, the wireless device may need to activate a panel associated with the first RS or the second RS.

The wireless device may determine the activation time (e.g., panel activation time, panel switching time) T_act (e.g., 1 slot, X symbols, M slots and/or the like) based on an indication whether the wireless device is equipped with multiple panels. The wireless device may report/indicate to a base station that the wireless device is equipped with a plurality of panels. In response to the indication, the wireless device and the base station may determine T_act as an activation switching latency. The base station and the wireless device may assume that the one or more spatial relation information may become active after T_act from a reference time. The reference time is a slot when the wireless device receives a DCI scheduling resources for a PDSCH comprising the MAC CE. The reference time is a slot when the wireless device transmits a HARQ-ACK feedback corresponding to the PDSCH comprising the MAC CE. The reference time is a slot when the wireless device physical layer receives the information from mac layer that may occur in a slot after X (e.g., 3) milliseconds after transmitting the HARQ-ACK feedback corresponding to the PDSCH comprising the MAC CE.

The base station and the wireless device may assume that the one or more spatial relation information may become active after T_act from receiving a HARQ-ACK feedback corresponding to a PDSCH comprising the AMC CE. The base station and the wireless device may assume that the one or more spatial relation information may become active after T_act from a slot n+MAC CE delay. For example, the base station and/or the wireless device may determine the slot n where the wireless device transmits the HARQ-ACK feedback or the base station receives the HARQ-ACK feedback. For example, the MAC CE delay may be a predetermined value (e.g., 3 msec).

For example, in FIG. 32, a second RS (RS2) may be associated with a PUCCH resource before a second time (T1). The PUCCH resource may be used for a repetition based on a single beam of the second RS.

The wireless device may receive a MAC CE updating spatial relation information of a PUCCH resource at the second time (T1). The spatial relation information may indicate to use a first RS (RS1) for a first beam and a third RS (RS3) for a second beam. The MAC CE may indicate to switch the PUCCH resource from a single beam to multi-beam repetition. For example, the base station and the wireless device may assume that the first RS for the PUCCH and the third RS for the PUCCH may become effective after T1+T_act (a panel activation delay) or after T2+T_act or T′1+T_act (where T′1 is when the wireless device receives a scheduling DCI for the MAC CE).

In terms of a delay, the wireless device may determine the delay as T_act (a panel activation delay) (e.g., the delay=T_act). For example, the wireless device may determine the delay as max {MAC CE activation delay, T_act} or sum of MAC CE activation delay and T_act. For example, MAC CE activation delay is a latency of applying a MAC CE command (e.g., 3 msec, M slots, X milli-seconds).

The wireless device may continue using the second RS for the PUCCH resource until the T1+the delay or T2+the delay or T2+M+the delay (e.g., between T1 and T3 in FIG. 32 or until the spatial relation information indicated by the MAC CE becomes effective). At the T1+X+the delay or T2+M+the delay, the wireless device may start to use the first RS and the third RS for the PUCCH resource.

For example, when the wireless device transmits the HARQ-ACK feedback at a third time (T2) via the PUCCH resource, the wireless device may use the first RS and the third RS for the HARQ-ACK feedback transmission.

For example, when the wireless device may transmit a HARQ-ACK feedback, via the PUCCH resource, of the MAC CE before T2 and before T1+the delay, the wireless device may use the second RS for the HARQ-ACK feedback transmission.

The wireless device may determine the delay as zero in response to indicated spatial relation information for the PUCCH resource are associated with active state panel(s). For example, the wireless device may determine the delay as T_act in response to a reference signal, of the indicated spatial relation information of the PUCCH resource, being associated with an inactive panel. Otherwise, the wireless device may determine the delay as zero. The wireless device may apply the indicated spatial relation information in response to receiving the MAC CE.

In an example, a wireless device may receive a MAC CE activating one or more spatial relation information for an SRS resource set. The one or more spatial relation information may comprise one or more reference signals. The one or more reference signals may be associated with one or more panels. A panel of the one or more panels may be inactive. The wireless device may determine a delay to apply the one or more spatial relation information for the SRS resource set based on a panel activation latency (T_act). Similar to a PUCCH resource, the wireless device may determine a delay based on T_act (e.g., the delay=T_act, the delay=max (T_act, MAC CE activation delay) in response to a spatial relation information (e.g., a reference signal) of the one or more spatial relation information for the SRS resource being associated with inactive panel. Otherwise, the wireless device may determine the delay is zero. The wireless device may continue using previous spatial relation information(s) of one or more SRS resources of the SRS resource set until the one or more spatial relation information for the SRS resource set becomes effective.

For example, the MAC CE may indicate to update a first SRS resource of an SRS resource from a second RS to a third RS in FIG. 32. The wireless device may need to activate a second panel associated with the third RS. For example, the first SRS may be mapped to an SRI=0 (e.g., index=0). The wireless device may receive a DCI indicating SRI=0 (e.g., the first SRS resource) after T2. The wireless device may determine the third RS for determining spatial domain filter parameter based on the first SRS resource based on the DCI. The wireless device may receive a second DCI indicating SRI=0 before T2 and before T1+the delay (or effective time). The wireless device may determine the second RS for determining spatial domain filter parameter based on the first resource based on the second DCI.

The wireless device may determine an active/effective time when spatial relation information(s) and/or reference signal(s) indicated by a MAC CE becomes active based on state of one or more panels associated with the spatial relation information(s). The wireless device may determine the active/effective time as T+delay where T is a time when the wireless device may receive a DCI indicating resources for the MAC CE and delay is a processing time to process/activate the indicated spatial relation information(s).

In an example, a wireless device may receive a MAC CE activating one or more uplink TCI states for a common UL beam (e.g., UL TCI state). The wireless device may determine to activate the one or more uplink TCI states at a time slot that is after T2+MAC CE delay+panel activation delay. For example, T2 is when the wireless device transmits a HARQ-ACK feedback corresponding to the MAC CE and MAC CE delay is a predetermined value (e.g., 3 msec) and the panel activation delay may be determined based on a capability of the wireless device.

In an example, a base station may not be aware of a state of a panel associated with a spatial relation information and/or an index of the panel at a time when the base station transmits a MAC CE activating the spatial relation information for a PUCCH resource or an SRS resource. The base station and a wireless device may determine an effective time of the MAC CE application in consideration of a panel activation latency. For example, the wireless device and the base station may determine that the spatial relation information indicated by the MAC CE may be activated after the panel activation delay (e.g., max {MAC CE activation delay, T_act} or a sum of MAC CE activation delay+T_act) after the MAC CE (e.g., at a time receiving a PDSCH comprising the MAC CE) or after transmitting the HARQ-ACK feedback. The wireless device and the base station may determine that the spatial relation information may be activated at a time when the wireless device transmits a HARQ-ACK feedback corresponding to the MAC CE (e.g., corresponding to the PDSCH comprising the MAC CE). For example, in FIG. 32, the wireless device may determine a spatial relation information of a resource until the third time T2 based on the second RS (RS2) and then update to the third RS (RS3) at the third time (T2).

In an example, the base station may indicate a latency that is applied for activating a spatial relation information. The wireless device may apply the latency where the latency may be applied after a slot n, where the slot n is when the wireless device receives a PDSCH comprising the MAC CE. For example, the wireless device may determine slot n+latency as a starting slot to activate the indicated spatial relation information. The latency may also consider/reflect a processing time for the MAC CE and/or an inter-layer latency. For example, the latency may be a sum of MAC CE activation delay (e.g., 3 msec)+a panel switching latency. The base station may determine the latency based on an indication of a panel activation latency by the wireless device.

In an example, a wireless device may receive a DCI scheduling resources for a PDSCH comprising a MAC CE at a first time. The DCI may indicate a PUCCH resource. The PUCCH resource may be associated with a first spatial relation information for a first repetition and a second spatial relation information for a second repetition. The wireless device may receive the MAC CE. The MAC CE may activate two spatial relation information, for the PUCCH resource, comprising a third spatial relation information for a fourth beam and a second spatial relation information for a second beam. The wireless device may determine one or more panels associated with the third spatial relation information and the fourth spatial relation information. The wireless device may transmit a HARQ-ACK feedback corresponding to the PDSCH via the PUCCH resource based on the first spatial relation information and the second spatial relation information. The wireless device may transmit an uplink signal via the PUCCH resource based on the third spatial relation information and the fourth spatial relation information after a time slot. For example, the wireless device may determine the time slot based on the HARQ-ACK feedback and a panel activation delay/processing time.

The wireless device may apply the third spatial relation information and the fourth spatial relation information after/immediately after/at/starting from/in the time slot.

FIG. 33 illustrates an example of an activation timer as per an aspect of an embodiment of the present disclosure. An activation timer may be called/referred as a deactivation timer (e.g., a deactivation panel timer, deactivation panel time duration, deactivation panel counter, activation time counter, activation time timer).

The base station may transmit a command indicating an activation of a second panel (e.g., panel #2) at a first time (T0). The command may be a CSI request (e.g., an aperiodic CSI request of a reference signal associated with the second panel). The command may be a MAC CE activating a spatial relation information associated with the second panel. The command may be an SRS request (e.g., an aperiodic SRS request where SRS is associated with the second panel). The command may be an activation of a semi-persistent CSI feedback of a reference signal associated with the second panel. The command may be an activation of a semi-persistent SRS comprising a reference signal of the second panel.

The wireless device may activate the second panel in response to the command. For example, the wireless device may activate or the activation becomes effective based on a procedure illustrated in FIG. 32. The wireless device may transmit an uplink signal based on the activation of the second panel. For example, the uplink signal may be a feedback (e.g., CSI report, a HARQ-ACK feedback for a MAC CE, a MAC CE confirmation). The uplink signal may be an SRS transmission. The uplink signal may be data transmission such as via PUSCH(s).

In an example, the wireless device may activate the second panel in a processing time of a panel activation time (e.g., P). The wireless device may transmit a HARQ-ACK feedback corresponding to the command before finishing the activation. The base station may receive the processing time by the wireless device. The base station may assume that the second panel is active at least after T0+P (e.g., the processing time after receiving the MAC CE) in response to receiving the HARQ-ACK feedback of ACK (e.g., the command has been successfully received). During [T0, T0+P], the wireless device may drop one or more uplink signals when an inter-beam latency is not sufficient or the wireless device may not be able to process the one or more uplink signals based on one or more examples in FIG. 36A-D. The wireless device may transmit the one or more uplink signals based on previous spatial relation information associated with/configured for/scheduled for the one or more uplink signals. For example, the wireless device may maintain the previous spatial relation information (e.g., spatial relation information of a SRS resource) until the indicated spatial relation information becomes effective.

In response to the command, a physical layer (PHY) of the wireless device may activate the second panel. The PHY of the wireless device may indicate a state of the second panel to a medium access layer (MAC) of the wireless device. The MAC of the wireless device may maintain an activation timer for the second panel.

The wireless device may complete the activation of the second panel at a second time (T1). The wireless device may start to perform the activation after transmitting the feedback and a MAC CE delay (e.g., a predetermined delay). For example, T1 may occur after T2+the MAC CE delay+a panel switching/activation latency. The PHY of the wireless device may indicate an active state of the second panel to the MAC of the wireless device. In response to the indication, the MAC of the wireless device may start the activation timer of the second panel when the activation timer of the second panel is not running. For example, the wireless device may start the activation timer (e.g., a panel deactivation timer) in response to transmitting the feedback (e.g., at T2) even though the wireless device may not activate the panel yet.

When the activation timer of the second panel is running, the MAC of the wireless device may restart the activation timer of the second panel. When the activation timer of the second panel is running, the MAC of the wireless device may ignore the indication.

The PHY of the wireless device may indicate the active state of the second panel after completing activation of the second panel or after transmission of a feedback/transmission corresponding to the command. For example, the PHY of the wireless device may transmit a HARQ-ACK feedback for the MAC CE activating a spatial relation information associated with the second panel at a third time (T2). The PHY of the wireless device may indicate to the MAC of the wireless device at the third time. The MAC of the wireless device may start the activation timer at the third time.

Regardless of when the indication from the PHY of the wireless device occurs, the MAC of the wireless device may start the activation timer at the third time in response to transmitting a corresponding uplink signal of the command. This may reduce ambiguity between the base station and the wireless device.

The base station may transmit a DCI scheduling a second uplink signal (uplink signal #2) after the third time. The base station may determine an inter-beam latency as zero or category 2 based on the active state of the second panel. For example, the DCI may schedule resources via the first panel and the second panel. For example, the DCI may schedule uplink signal repetition via a first beam of the first panel and a second beam of the second panel. The base station may determine that the second panel is active based on the activation timer at the wireless device.

The wireless device may transmit the second uplink signal at a fourth time (T3). In response to transmitting the second uplink signal, where the second uplink signal may be transmitted via the second panel, the wireless device may restart the activation timer of the second panel. The wireless device may restart the activation timer of the second panel in response to transmitting uplink signal/reference signal (e.g., data, UCI, SRS, PRACH) based on the second panel.

The wireless device may restart a first activation timer of the first panel (if the first activation timer is running or available) in response to the second uplink signal.

In an example, when a wireless device may switch from a first BWP to a second BWP, the wireless device may determine whether to keep active state for one or more panels.

For example, the wireless device may switch a BWP of a primary cell or a PUCCH cell, where one or more PUCCH resources are configured for the primary cell or the PUCCH cell. For example, the wireless device may determine a PUCCH resource with a lowest index (e.g., a PUCCH resource with an index=0) among one or more PUCCH resources of the second BWP. The wireless device may determine a panel associated with the PUCCH resource. For example, the PUCCH resource may be associated with the second panel. The wireless device may determine to maintain a state of the second panel being active without employing an activation timer (e.g., maintain active state of the second panel for the second BWP or while the second BWP is active).

The wireless device may determine or disable an activation timer of the second panel if any. The wireless device may determine to maintain active state of the second panel based on the PUCCH resource.

The wireless device may determine one or more panels to be active based on the one or more PUCCH resources. For example, when the wireless device determines a first panel is associated with a second PUCCH resource configured with a spatial relation information associated with the first panel, the wireless device may determine to activate the first panel and maintain an active state of the first panel.

The wireless device may determine one or more panels associated with an uplink grant indicating a BWP switching. The wireless device may determine one or more spatial relation information (or beams) indicated by the uplink grant. The wireless device may restart one or more activation timers of the one or more panels.

The wireless device may deactivate a panel when an activation timer of the panel is not running and the wireless device may not maintain an active state of the panel based on one or more PUCCH resources.

The wireless device may determine a primary panel that is maintained active for a BWP being active for a primary cell and/or a PUCCH cell. The wireless device may not operate an activation timer for the primary panel. The wireless device may maintain active state for the primary panel at least until the BWP is active. For an initial BWP, the primary panel may be determined based on a panel used in an initial access procedure. For a non-initial BPW, the primary panel may be determined based on a panel associated with a PUCCH resource with a lowest index. When the wireless device is configured with a primary cell and a PUCCH cell, where a lowest indexed PUCCH resource of the primary cell is associated with a first panel and a lowest indexed PUCCH resource of the PUCCH cell is associated with a second panel, the wireless device may determine both the first panel and the second panel as primary panels. The wireless device may maintain active states of the primary cell and the secondary cell.

In an example, the lowest indexed PUCCH of the primary cell or the PUCCH cell may be configured with a plurality of spatial relation information. The base station may transmit a MAC CE activating a spatial relation information of the plurality of spatial relation information.

The wireless device may determine a lowest indexed PUCCH resource (e.g., a PUCCH resource with index=0) of one or more PUCCH resources as a PUCCH resource configured with a single spatial relation information. When there are more than one PUCCH resources configured with a single spatial relation information respectively (each PUCCH resource is configured with a spatial relation information), the wireless device may determine a lowest indexed PUCCH resource among the more than one PUCCH resources.

The wireless device may determine a primary panel based on the lowest indexed PUCCH resource among the more than one PUCCH resources configured with a single spatial relation information.

The wireless device may determine a panel index=0 for the primary panel. When the wireless device may have a plurality of primary panels (e.g., for primary cell and PUCCH cell), the wireless device may assign a panel index=0 for a primary panel of the primary cell and panel index=1 for a primary panel of the PUCCH cell.

In an example, a wireless device may receive a MAC CE indicating a spatial relation information comprising a reference signal. The reference signal may be associated with a panel that is inactive state. The MAC CE may indicate the spatial relation information for an SRS resource set. The spatial relation information may be indicated for an SRS resource of the SRS resource set. The wireless device may inform a state of the panel to the base station. The wireless device may inform an index of a panel associated with an SRS resource. The wireless device may inform an index of a panel associated with an SRS resource set. The wireless device may inform an inter-beam latency for a pair of SRS resources. The wireless device may inform an inter-beam latency for a pair of spatial relation information. The wireless device may inform an inter-beam latency for a PUCCH resource. The wireless device may inform a state of a panel associated with an SRS resource in a SRS resource set.

FIG. 34A illustrate an example diagram of an indication as per an aspect of an embodiment of the present disclosure.

For example, the wireless device may initiate a scheduling request (SR) to request for an uplink grant. The base station may transmit the uplink grant based on the SR. The base station may schedule an uplink grant for a MAC CE. The base station may request a CSI feedback via the uplink grant. The wireless device may send the MAC CE comprising indication of one or more latency information/panel information of one or more beams/spatial relation information/resources based on the uplink grant. The wireless device may transmit a CSI feedback based on the uplink grant.

FIG. 34B illustrates an example MAC CE format of the indication as per an aspect of an embodiment of the present disclosure. For example, the example MAC CE format may indicate an index of a panel associated with an SRS resource of an SRS resource set. The example MAC format may comprise an SRS resource set's cell ID where a cell with the SRS resource set's cell ID comprises the SRS resource set. The example MAC CE format may comprise an SRS resource set's BWP ID where a BWP with the SRS resource set's BWP ID comprises the SRS resource set.

The example MAC CE format may indicate a SUL or UL via a ‘SUL’ field.

The example MAC CE format may be based on one or more fields of a MAC CE format in FIG. 31. The example MAC CE format may comprise a bitmap (e.g., S0, . . . , S7). Each bit of the bitmap may correspond to an SRS resource of the SRS resource set. For example, first bit of the bitmap may correspond to first SRS resource (e.g., a lowest indexed SRS resource among one or more SRS resources of the SRS resource set). For example, second bit of the bitmap may correspond to second SRS resource with a second lowest index among the one or more SRS resources. The wireless device may map the one or more SRS resources in ascending order, based on index(es) of the one or more SRS resources, to the bitmap. The wireless device may the one or more SRS resources in an order in the SRS resource set (e.g., based on a list of the SRS resource set) to the bitmap.

Each bit (Si) may indicate 0 to indicate a first panel with an index=0. The Si may indicate 1 to indicate a second panel with index=1.

Each bit (Si) may indicate 0 to indicate a panel associated with an SRS resource mapping to Si is active. Each bit (Si) may indicate 1 to indicate the panel is inactive.

Each bit (Si) may indicate 1 to indicate a panel associated with an SRS resource mapping to Si is active. Each bit (Si) may indicate 0 to indicate the panel is inactive.

In an example, a wireless device may change an association between one or more beams/reference signals/spatial relation information and one or more panels. For example, the wireless device may change the association based on a mobility. The wireless device may change the association to reduce a power consumption. The wireless device may change the association due to an interference and/or maximum exposure issue.

The wireless device may indicate a new association or panel information via a MAC CE (e.g., based on FIG. 34). Before a base station receives the MAC CE, the base station may determine an inter-beam latency based on previous association information that may be obsolete. The wireless device may receive a DCI scheduling uplink signal repetition via a plurality of beams based on a first inter-beam latency. The wireless device may require larger gap between consecutive repetitions based on the new association. The wireless device may need to drop one or more repetitions/symbols to accommodate a second inter-beam latency based on the new association.

FIG. 35 illustrates an example diagram of a new association between beams and panels as per an aspect of an embodiment of the present disclosure.

The base station may transmit one or more RRC messages comprising/indicating configuration parameters. The configuration parameters may comprise/indicate one or more CSI report configurations. For example, the one or more CSI report configurations may comprise a first CSI report configuration of a first RS (RS1), a second CSI report configuration of a second RS (RS2), a third CSI report configuration of a third RS (RS3), and a fourth CSI report configuration of a fourth RS (RS4). The wireless device may transmit one or more CSI feedbacks based on the one or more CSI report configurations at a first time (T0). The wireless device may indicate panel information for one or more CSI RSs. For example, the wireless device may indicate the first RS is associated with a first panel (panel #1) and the second RS is associated with the first panel. The wireless device may indicate the third RS is associated with a second panel (panel #2) and the fourth RS is associated with the fourth RS.

The base station may acquire association mapping between RSs and the panels (e.g., beams/TCI states based on the RSs and the panels) based on the one or more CSI feedbacks.

The wireless device may determine to change the association between RSs and the panel at a second time (T1). For example, the wireless device may determine to change an association between the third RS and a panel. The third RS becomes being associated with the first panel from the second panel. The wireless device may also determine to deactivate the second panel. For example, the wireless device may deactivate the second panel based on an activation timer expires.

The base station may not be aware of the second panel being deactivated. The base station may transmit an uplink grant scheduling an uplink signal repetition via the third RS (e.g., a first beam) and the fourth RS (e.g., a second beam) at a third time (T3). The base station may indicate a small latency for an inter-beam latency between a first repetition (#1) via the first beam and a second repetition (#2) via the second beam.

The wireless device may need to activate the second panel before transmitting the second repetition. The wireless device may not have a sufficient time to activate the second panel. The inter-beam latency indicated by the uplink grant may not be sufficient to activate the second panel. The wireless device may drop the second panel.

The wireless device may inform or indicate the new association or a state of the second panel to the base station. For example, the wireless device may inform that the fourth RS is associated with the second panel and the second panel is inactive.

In an example, the wireless device may receive a DCI indicating resources for an uplink signal repetition via a plurality of beams. The DCI may indicate an inter-beam latency where the inter-beam latency may be applied between two consecutive repetitions via different beams. Due to dynamic changes in a panel layout and/or association between beams and panels and/or mobility of the wireless device, the base station and the wireless device may have different information on a required inter-beam latency. For example, the wireless device may need to activate a panel to transmit a repetition that may require a panel activation latency between the two consecutive repetitions.

In an example, the wireless device may drop one or more repetitions in response to the indicated inter-beam latency not being sufficient. In an example, the wireless device may drop one or more symbols of a repetition in response to the indicated inter-beam latency not being sufficient.

FIG. 36A-D illustrates examples of handling insufficient gap as per an aspect of an embodiment of the present disclosure.

For example, a dotted box may illustrate a required latency (e.g., M).

A wireless device may receive a DCI indicating two repetitions comprising a first transmission (#1) and a second transmission (#2). The DCI may indicate an inter-beam latency L. For example, L may be 1 symbol. For example, L may be zero. The wireless device may need a latency M that is larger than L. The wireless device may determine to drop one or more transmissions or puncture one or more symbols of a transmission based on the latency M.

The wireless device may puncture one or more symbols by putting zero power of resources via the one or more symbols. The wireless device may skip transmission of resources via the one or more symbols by puncturing the one or more symbols of the transmission. The wireless device may put zero power for the one or more transmissions in response to dropping the one or more transmissions. The wireless device may cancel the one or more transmissions in response to dropping the one or more transmissions.

For example, the wireless device may puncture (e.g., drop transmission in resources punctured) one or more symbols of a first transmission. FIG. 36A illustrates that the wireless device may drop one or more symbols (e.g., last few symbols) of the first transmission to accommodate the latency M.

For example, the wireless device may drop one or more transmissions to accommodate the latency M. For example, the wireless device may drop the first transmission as shown in FIG. 36B. For example, the wireless device may determine to drop the first transmission or the second transmission based on a first RV of the first transmission and a second RV of the second transmission. For example, the wireless device may not drop a transmission with a RV=0 (e.g., including systematic bits). The wireless device may prioritize a RV in order of 10, 2, 3, 11 (e.g., 0 is prioritized over 2, 2 is prioritized over 3, 3 is prioritized over 1). The wireless device may determine to drop a transmission with lower priority based on a RV of the transmission.

The wireless device may puncture one or more first symbols of the second transmission as shown in FIG. 36C. This may drop a DM-RS symbol. This option may be used only when the second transmission is configured with more than one DM-RS symbols or punctured resources may not comprise a DM-RS symbol. When the wireless device may need to drop a DM-RS, the wireless device may drop the second transmission. For example, when the wireless device punctures a few first symbols for accommodating the latency where the few first symbols comprise a DM-RS symbol, the wireless device may drop an entire transmission.

The wireless device may drop the second transmission as shown in FIG. 36D.

The base station may configure which option to use to accommodate insufficient gap. For example, the base station may indicate to use option 1 (e.g., FIG. 36A), option 2 (e.g., FIG. 36B), option 3 (e.g., FIG. 36C) or option 4 (e.g., FIG. 36D).

In an example, when the uplink repetition is indicated with insufficient gap, the wireless device may drop the entire repetition. The wireless device may not transmit the uplink signal repetition.

In an example, a base station may assume a worst case latency (e.g., L_w) for an inter-beam latency when the base station may not be aware of state of one or more panels associated with beams/RSs used for an uplink signal repetition. For example, the worst case latency may include a panel activation latency. For example, the base station may schedule an uplink grant with k2 value (e.g., a scheduling offset between a DCI (e.g., the uplink grant) and a first PUSCH, comprising a transport block, scheduled by the DCI) such that k2 value is larger than or equal to L_w. The base station may also indicate the inter-beam latency being larger than L_w as well.

For example, the base station may transmit one or more RRC messages indicating configuration parameters. The configuration parameters may indicate a value of L_w (e.g., a maximum inter-beam latency, an inter-beam latency). The base station may dynamically indicate whether to apply the L_w or not via the uplink grant. For example, a field in the uplink grant may indicate 0 to not apply L_w or to indicate zero inter-beam latency. The field may indicate 1 to apply L_w. One or more values of inter-beam latency may be configured via the configuration parameters. A DCI may indicate one of the one or more values dynamically.

The base station may determine zero or a category 1 or a category 2 latency based on information/feedback from the wireless device. The information/feedback may comprise one or more of {a state of a panel, an association between beams/RSs and one or more panels, an association between SRSs and one or more panels}.

In an example, a wireless device may transmit one or more CSI feedback. A base station may acquire an association between beams/RSs/TCI states/spatial relation information/SRS resources and panel(s). The base station may acquire state(s) of the panel(s) via the CSI feedback. The base station may transmit a DCI indicating a BWP switching.

For example, one or more PUCCH resources may be configured for each BWP of one or more BWPs of a cell. For example, one or more SRS resources and/or one or more SRS resource sets may be configured for each BWP of the one or more BWPs. In response to switching to a BWP, the wireless device may determine one or more primary panels based on BWP (e.g., a panel associated with a PUCCH resource with index=0, a panel associated with a PUCCH resource with a single spatial relation information). The wireless device may activate the one or more primary panels in response to switching to the BWP. The wireless device may determine to stop one or more activation timers of a previous BWP.

The wireless device may determine to deactivate one or more second panels where an activation timer for a panel of the one or more second panels may not run and the panel may not belong to the one or more primary panels. The base station may determine an inter-beam latency and/or state(s) of one or more panels of the wireless device based on the one or more primary panels and/or the one or more second panels.

FIG. 37 illustrates a flow diagram of an example embodiment as per an aspect of an embodiment of the present disclosure.

In an example, a wireless device may receive a plurality of spatial relation information for a PUCCH resource (e.g., at 3710). For example, the wireless device may determine a lowest indexed spatial relation information, of the plurality of spatial relation information, is activated for the PUCCH resource. For example, the wireless device may determine any spatial relation information is active for the PUCCH resource until the wireless device may receive a MAC CE activating a spatial relation information. For example, the wireless device may determine a second spatial relation information configured for a lowest indexed PUCCH resource (e.g., a second PUCCH resource with an index=0) for the PUCCH resource until the wireless device may receives the MAC CE activating the spatial relation information for the PUCCH resource.

The wireless device may receive a MAC CE activating a spatial relation information for the PUCCH resource (e.g., at 3720). The spatial relation information is one of the plurality of spatial relation information configured for the PUCCH resource. The spatial relation information may comprise a reference signal that is one of SSB, CSI-RS or an SRS.

The wireless device may activate a panel associated with the spatial relation information for the PUCCH resource in response to the panel being inactive state and based on the MAC CE activating the spatial relation information associated with the pane 1 (e.g., at 3730). For example, the panel may be a second panel or may have an index being greater than zero (e.g., the index=1). For example, the panel may not be a primary panel, where the wireless device may maintain the primary panel active regardless of a MAC CE or based on RRC signaling. For example, the primary panel may be a panel with index=0. For example, the primary panel may be a panel used for an initial access procedure. For example, the primary panel may be a panel used in a most recent random access procedure. For example, the primary panel may be a panel associated with a PUCCH resource with a lowest index (e.g., a PUCCH resource with an index=0). For example, an index of a resource or a panel may be counted for resources or panels respectively.

The base station may determine that the panel associated with the spatial relation information is active at least for a time duration. The wireless device may start a timer, based on an active time duration, for the panel (e.g., at 3740). The base station may transmit RRC message(s) comprising/indicating configuration parameters. The configuration parameters may comprise/indicate a value for the active time duration or a value for the timer for the active time duration. The wireless device may run the timer based on the active time duration. The wireless device may restart the timer in response to the timer is running. The wireless device may start the timer in response to the timer is not running. The wireless device may determine the timer is expired in response to elapsing the active time duration since the timer has been lastly started or restarted. The timer may expire after the active time duration without being restarted. When the timer is restarted, the wireless device may determine to restart to measure an elapsed time.

The wireless device may transmit an uplink signal via the spatial relation information based on an active state of the panel at least until the timer is expired (e.g., at least during the active time duration) (e.g., at 3750). The wireless device may determine a spatial domain filter parameter for the uplink signal based on the spatial relation information. The wireless device may determine the spatial domain filter parameter based on a reference signal of the spatial relation information. The wireless device may be able to transmit the uplink signal without requiring additional latency to activate the panel. For example, the wireless device may be able to transmit the uplink signal based on a processing time of uplink signal without accounting a panel activation latency. For example, the wireless device may require a zero inter-beam latency between a first uplink transmission based on a first RS that is associated with a primary panel and a second uplink transmission based on the spatial relation information that is associated with the panel, while the timer is running (e.g., during the active time duration).

In an example, a wireless device may receive a medium access control control element (MAC CE) for a physical uplink control channel (PUCCH) resource. The MAC CE may indicate to activate, for the PUCH resource, a first spatial relation information comprising a first reference signal (RS) and a second spatial relation information comprising a second RS. For example, the first RS may be associated with a first wireless device panel that may be active. For example, the second RS may be associated with a second wireless device panel that may be inactive at a time of receiving the MAC CE. The wireless device may activate, in response to the MAC CE, the second wireless device panel in response to the second wireless panel being inactive and the second RS being associated with the second wireless device panel. The wireless device may start an active time duration for the second wireless device panel. The wireless device may receive an uplink grant, for repetition of a transport block. The uplink grant may indicate first time domain resource of a first repetition and second time domain resource of a second repetition. For example, a gap between the first time domain resource and the second time domain resource may be smaller than or equal to a predetermined value. The wireless device may transmit the repetition of the transport block via the first time domain resource based on the first RS; and the second time domain resource based on the second RS.

In an example embodiment, the first RS may be a synchronization signal and physical broadcast channel block (SSB) or a channel state information RS (CSI-RS) or a sounding reference signal. The second RS may be a second SSB, a second CSI-RS or a second SRS.

In an example embodiment, the wireless device may start the active time duration in response to the active time duration has not started. The wireless device may restart the activation time duration in response to the active time duration has started.

In an example embodiment, the wireless device may restart the active time duration in response to the transmitting the repetition of the transmit block via the second time domain resource based on the second RS.

In an example embodiment, the first time domain resource may be a first slot. The second time domain resource may be a second slot.

In an example embodiment, the first time domain resource may be a first sub-slot. The second time domain resource may be a second sub-slot. A slot may comprise 14 symbols. A sub-slot may comprise 2 symbols or 7 symbols.

In an example embodiment, the wireless device may transmit a first physical uplink shared channel (PUSCH) comprising the transport block via the first time domain resource based on the first RS. The wireless device may transmit a second PUSCH the transport block via the second time domain resource based on the second RS.

In an example embodiment, the wireless device may determine the gap is between an end of the first time domain resource and a start of the second time domain resource.

In an example embodiment, the first RS may be associated with a first transmission and reception point (TRP) of a base station. The second RS may be associated with a second TRP of the base station.

In an example embodiment, the wireless device may receive one or more radio resource control (RRC) messages indicating configuration parameters. For example, the configuration parameters may indicate a second PUCCH resource comprising a single spatial relation information.

In an example embodiment, an index of the second PUCCH resource may be zero.

In an example embodiment, the wireless device may determine a panel associated with the single spatial relation information.

In an example embodiment, the wireless device may activate the panel in response to the determining.

In an example embodiment, the wireless device may maintain an active state of the panel based on the RRC messages.

In an example embodiment, the wireless device may deactivate the second wireless device panel in response to elapsing the active time duration since restarting the active time duration.