CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No. 17/853,404, filed Jun. 29, 2022, which is a continuation of U.S. patent application Ser. No. 16/857,383, filed Apr. 24, 2020, which claims the benefit of U.S. Provisional Application No. 62/842,319, filed May 2, 2019, all of which are hereby incorporated by reference in their entireties.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram of an example RAN architecture as per an aspect of an embodiment of the present disclosure.

FIG. 2A is a diagram of an example user plane protocol stack as per an aspect of an embodiment of the present disclosure.

FIG. 2B is a diagram of an example control plane protocol stack as per an aspect of an embodiment of the present disclosure.

FIG. 3 is a diagram of an example wireless device and two base stations as per an aspect of an embodiment of the present disclosure.

FIG. 4A, FIG. 4B, FIG. 4C and FIG. 4D are example diagrams for uplink and downlink signal transmission as per an aspect of an embodiment of the present disclosure.

FIG. 5A is a diagram of an example uplink channel mapping and example uplink physical signals as per an aspect of an embodiment of the present disclosure.

FIG. 5B is a diagram of an example downlink channel mapping and example downlink physical signals as per an aspect of an embodiment of the present disclosure.

FIG. 6 is a diagram depicting an example frame structure as per an aspect of an embodiment of the present disclosure.

FIG. 7A and FIG. 7B are diagrams depicting example sets of OFDM subcarriers as per an aspect of an embodiment of the present disclosure.

FIG. 8 is a diagram depicting example OFDM radio resources as per an aspect of an embodiment of the present disclosure.

FIG. 9A is a diagram depicting an example CSI-RS and/or SS block transmission in a multi-beam system.

FIG. 9B is a diagram depicting an example downlink beam management procedure as per an aspect of an embodiment of the present disclosure.

FIG. 10 is an example diagram of configured BWPs as per an aspect of an embodiment of the present disclosure.

FIG. 11A, and FIG. 11B are diagrams of an example multi connectivity as per an aspect of an embodiment of the present disclosure.

FIG. 12 is a diagram of an example random access procedure as per an aspect of an embodiment of the present disclosure.

FIG. 13 is a structure of example MAC entities as per an aspect of an embodiment of the present disclosure.

FIG. 14 is a diagram of an example RAN architecture as per an aspect of an embodiment of the present disclosure.

FIG. 15 is a diagram of example RRC states as per an aspect of an embodiment of the present disclosure.

FIG. 16 is an example diagram to show beam operation procedures as per an aspect of an embodiment of the present disclosure.

FIG. 17 is an example diagram to show applications of TCI state as per an aspect of an embodiment of the present disclosure.

FIG. 18 is an example diagram to show an indication in MAC CE as per an aspect of an embodiment of the present disclosure.

FIG. 19 is an example diagram to show beam operation procedures as per an aspect of an embodiment of the present disclosure.

FIG. 20 is an example diagram to show applications of TCI state as per an aspect of an embodiment of the present disclosure.

FIG. 21 is an example diagram to show applications of TCI state as per an aspect of an embodiment of the present disclosure.

FIG. 22 is an example diagram to show an indication in MAC CE as per an aspect of an embodiment of the present disclosure.

FIG. 23 is an example diagram to show applications of transmission group as per an aspect of an embodiment of the present disclosure.

FIG. 24 is an example diagram to show operations of transmission group as per an aspect of an embodiment of the present disclosure.

FIG. 25 is an example diagram to show operations of transmission group as per an aspect of an embodiment of the present disclosure.

FIG. 26 is an example diagram to show operations of transmission group as per an aspect of an embodiment of the present disclosure.

FIG. 27 is an example diagram to show operations of an uplink transmission as per an aspect of an embodiment of the present disclosure.

FIG. 28 is an example diagram to show operations of an uplink transmission as per an aspect of an embodiment of the present disclosure.

FIG. 29 is an example diagram to show operations of an uplink transmission as per an aspect of an embodiment of the present disclosure.

FIG. 30 is an example diagram to show operations of a downlink control information reception as per an aspect of an embodiment of the present disclosure.

FIG. 31 is an example diagram to show operations of a downlink control information reception as per an aspect of an embodiment of the present disclosure.

DETAILED DESCRIPTION

Example embodiments of the present disclosure enable operation of activation and/or deactivation of one or more transmission configuration groups. Embodiments of the technology disclosed herein may be employed in the technical field of multicarrier communication systems. More particularly, the embodiments of the technology disclosed herein may relate to multicarrier communication systems.

The following Acronyms are used throughout the present disclosure:

- 3GPP 3rd Generation Partnership Project
- 5GC 5G Core Network
- ACK Acknowledgement
- AMF Access and Mobility Management Function
- ARQ Automatic Repeat Request
- AS Access Stratum
- ASIC Application-Specific Integrated Circuit
- BA Bandwidth Adaptation
- BCCH Broadcast Control Channel
- BCH Broadcast Channel
- BPSK Binary Phase Shift Keying
- BWP Bandwidth Part
- CA Carrier Aggregation
- CBG Code Block Group
- CC Component Carrier
- CCCH Common Control CHannel
- CDMA Code Division Multiple Access
- CN Core Network
- CP Cyclic Prefix
- CP-OFDM Cyclic Prefix-Orthogonal Frequency Division Multiplex
- C-RNTI Cell-Radio Network Temporary Identifier
- CS Configured Scheduling
- CS-RNTI Configured Scheduling-Radio Network Temporary Identifier
- CSI Channel State Information
- CSI-RS Channel State Information-Reference Signal
- CORESET Control REsource SET
- CQI Channel Quality Indicator
- CSS Common Search Space
- CU Central Unit
- DC Dual Connectivity
- DCCH Dedicated Control CHannel
- DCI Downlink Control Information
- DL Downlink
- DL-SCH Downlink Shared CHannel
- DMRS DeModulation Reference Signal
- DRB Data Radio Bearer
- DRX Discontinuous Reception
- DTCH Dedicated Traffic CHannel
- DU Distributed Unit
- EPC Evolved Packet Core
- E-UTRA Evolved UMTS Terrestrial Radio Access
- E-UTRAN Evolved-Universal Terrestrial Radio Access Network
- FDD Frequency Division Duplex
- FPGA Field Programmable Gate Arrays
- F1-C F1-Control plane
- F1-U F1-User plane
- gNB next generation Node B
- HARQ Hybrid Automatic Repeat reQuest
- HDL Hardware Description Languages
- IE Information Element
- IP Internet Protocol
- LCID Logical Channel IDentifier
- LTE Long Term Evolution
- MAC Media Access Control
- MCG Master Cell Group
- MCS Modulation and Coding Scheme
- MCS-C-RNTI Modulation and Coding Scheme-Cell-Radio Network Temporary Identity
- MeNB Master evolved Node B
- MIB Master Information Block
- MME Mobility Management Entity
- MN Master Node
- NACK Negative Acknowledgement
- NAS Non-Access Stratum
- NDI New Data Indicator
- NG CP Next Generation Control Plane
- NGC Next Generation Core
- NG-C NG-Control plane
- ng-eNB next generation evolved Node B
- NG-U NG-User plane
- NR New Radio
- NR MAC New Radio MAC
- NR PDCP New Radio PDCP
- NR PHY New Radio PHYsical
- NR RLC New Radio RLC
- NR RRC New Radio RRC
- NSSAI Network Slice Selection Assistance Information
- O&M Operation and Maintenance
- OFDM Orthogonal Frequency Division Multiplexing
- PBCH Physical Broadcast CHannel
- PCC Primary Component Carrier
- PCCH Paging Control CHannel
- PCell Primary Cell
- PCH Paging CHannel
- PDCCH Physical Downlink Control CHannel
- PDCP Packet Data Convergence Protocol
- PDSCH Physical Downlink Shared CHannel
- PDU Protocol Data Unit
- PHICH Physical HARQ Indicator CHannel
- PHY PHYsical
- PLMN Public Land Mobile Network
- PMI Precoding Matrix Indicator
- PRACH Physical Random Access CHannel
- PRB Physical Resource Block
- P-RNTI Paging-Temporary Radio Network Temporary Identifier
- PSCell Primary Secondary Cell
- PSS Primary Synchronization Signal
- pTAG primary Timing Advance Group
- PT-RS Phase Tracking Reference Signal
- PUCCH Physical Uplink Control CHannel
- PUSCH Physical Uplink Shared CHannel
- QAM Quadrature Amplitude Modulation
- QFI Quality of Service Indicator
- QoS Quality of Service
- QPSK Quadrature Phase Shift Keying
- RA Random Access
- RACH Random Access CHannel
- RAN Radio Access Network
- RAT Radio Access Technology
- RA-RNTI Random Access-Radio Network Temporary Identifier
- RB Resource Blocks
- RBG Resource Block Groups
- RI Rank Indicator
- RLC Radio Link Control
- RNTI Radio Network Temporary Identity
- RRC Radio Resource Control
- RS Reference Signal
- RSRP Reference Signal Received Power
- RV Redundancy Version
- SCC Secondary Component Carrier
- SCell Secondary Cell
- SCG Secondary Cell Group
- SC-FDMA Single Carrier-Frequency Division Multiple Access
- SDAP Service Data Adaptation Protocol
- SDU Service Data Unit
- SeNB Secondary evolved Node B
- SFN System Frame Number
- S-GW Serving GateWay
- SI System Information
- SIB System Information Block
- SLIV Start and Length Indicator Value
- SMF Session Management Function
- SN Secondary Node
- SpCell Special Cell
- SRB Signaling Radio Bearer
- SRS Sounding Reference Signal
- SS Synchronization Signal
- SSS Secondary Synchronization Signal
- SUL Supplementary Uplink
- sTAG secondary Timing Advance Group
- TA Timing Advance
- TAG Timing Advance Group
- TAI Tracking Area Identifier
- TAT Time Alignment Timer
- TB Transport Block
- TCI Transmission Configuration Indication
- TC-RNTI Temporary Cell-Radio Network Temporary Identifier
- TDD Time Division Duplex
- TDMA Time Division Multiple Access
- TPC Transmit Power Control
- TRP Transmission and Reception Point
- TTI Transmission Time Interval
- UCI Uplink Control Information
- UE User Equipment
- UL Uplink
- UL-SCH Uplink Shared CHannel
- UPF User Plane Function
- UPGW User Plane Gateway
- URLLC Ultra Reliable Low Latency Communication
- VHDL VHSIC Hardware Description Language
- Xn-C Xn-Control plane
- Xn-U Xn-User plane
- ZP CSI-RS Zero power CSI-RS

Example embodiments of the disclosure may be implemented using various physical layer modulation and transmission mechanisms. Example transmission mechanisms may include, but are not limited to: Code Division Multiple Access (CDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Time Division Multiple Access (TDMA), Wavelet technologies, and/or the like. Hybrid transmission mechanisms such as TDMA/CDMA, and OFDM/CDMA may also be employed. Various modulation schemes may be applied for signal transmission in the physical layer. Examples of modulation schemes include, but are not limited to: phase, amplitude, code, a combination of these, and/or the like. An example radio transmission method may implement Quadrature Amplitude Modulation (QAM) using Binary Phase Shift Keying (BPSK), Quadrature Phase Shift Keying (QPSK), 16-QAM, 64-QAM, 256-QAM, and/or the like. Physical radio transmission may be enhanced by dynamically or semi-dynamically changing the modulation and coding scheme depending on transmission requirements and radio conditions.

FIG. 1 is an example Radio Access Network (RAN) architecture as per an aspect of an embodiment of the present disclosure. As illustrated in this example, a RAN node may be a next generation Node B (gNB) (e.g., 120A, 120B) providing New Radio (NR) user plane and control plane protocol terminations towards a first wireless device (e.g., 110A). In an example, a RAN node may be a next generation evolved Node B (ng-eNB) (e.g., 124A, 124B), providing Evolved UMTS Terrestrial Radio Access (E-UTRA) user plane and control plane protocol terminations towards a second wireless device (e.g., 110B). The first wireless device may communicate with a gNB over a Uu interface. The second wireless device may communicate with a ng-eNB over a Uu interface. In this disclosure, wireless device 110A and 110B are structurally similar to wireless device 110. Base stations 120A and/or 120B may be structurally similarly to base station 120. Base station 120 may comprise at least one of a gNB (e.g., 122A and/or 122B), ng-eNB (e.g., 124A and/or 124B), and or the like.

A gNB or an ng-eNB may host functions such as: radio resource management and scheduling, IP header compression, encryption and integrity protection of data, selection of Access and Mobility Management Function (AMF) at User Equipment (UE) attachment, routing of user plane and control plane data, connection setup and release, scheduling and transmission of paging messages (originated from the AMF), scheduling and transmission of system broadcast information (originated from the AMF or Operation and Maintenance (O&M)), measurement and measurement reporting configuration, transport level packet marking in the uplink, session management, support of network slicing, Quality of Service (QoS) flow management and mapping to data radio bearers, support of UEs in RRC_INACTIVE state, distribution function for Non-Access Stratum (NAS) messages, RAN sharing, and dual connectivity or tight interworking between NR and E-UTRA.

In an example, one or more gNBs and/or one or more ng-eNBs may be interconnected with each other by means of Xn interface. A gNB or an ng-eNB may be connected by means of NG interfaces to 5G Core Network (5GC). In an example, 5GC may comprise one or more AMF/User Plan Function (UPF) functions (e.g., 130A or 130B). A gNB or an ng-eNB may be connected to a UPF 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 Protocol Data Units (PDUs) between a RAN node and the UPF. A gNB or an ng-eNB may be connected to an AMF 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, configuration transfer and/or warning message transmission, combinations thereof, and/or the like.

In an example, a UPF may host functions such as anchor point for intra-/inter-Radio Access Technology (RAT) mobility (when applicable), external PDU session point of interconnect to data network, packet routing and forwarding, packet inspection and user plane part of policy rule enforcement, traffic usage reporting, uplink classifier to support routing traffic flows to a data network, branching point to support multi-homed PDU session, QoS handling for user plane, e.g., packet filtering, gating, Uplink (UL)/Downlink (DL) rate enforcement, uplink traffic verification (e.g., Service Data Flow (SDF) to QoS flow mapping), downlink packet buffering and/or downlink data notification triggering.

In an example, an AMF may host functions such as NAS signaling termination, NAS signaling security, Access Stratum (AS) security control, inter Core Network (CN) node signaling for mobility between 3rd Generation Partnership Project (3GPP) access networks, idle mode UE reachability (e.g., control and execution of paging retransmission), registration area management, support of intra-system and inter-system mobility, access authentication, access authorization including check of roaming rights, mobility management control (subscription and policies), support of network slicing and/or Session Management Function (SMF) selection.

FIG. 2A is an example user plane protocol stack, where Service Data Adaptation Protocol (SDAP) (e.g., 211 and 221), Packet Data Convergence Protocol (PDCP) (e.g., 212 and 222), Radio Link Control (RLC) (e.g., 213 and 223) and Media Access Control (MAC) (e.g., 214 and 224) sublayers and Physical (PHY) (e.g., 215 and 225) layer may be terminated in wireless device (e.g., 110) and gNB (e.g., 120) on the network side. In an example, a PHY layer provides transport services to higher layers (e.g., MAC, RRC, etc.). In an example, services and functions of a MAC sublayer may comprise mapping between logical channels and transport channels, multiplexing/demultiplexing of MAC Service Data Units (SDUs) belonging to one or different logical channels into/from Transport Blocks (TBs) delivered to/from the PHY layer, scheduling information reporting, error correction through Hybrid Automatic Repeat request (HARQ) (e.g., one HARQ entity per carrier in case of Carrier Aggregation (CA)), priority handling between UEs by means of dynamic scheduling, priority handling between logical channels of one UE by means of logical channel prioritization, and/or padding. A MAC entity may support one or multiple 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. In an example, an RLC sublayer may supports transparent mode (TM), unacknowledged mode (UM) and acknowledged mode (AM) transmission modes. The RLC configuration may be per logical channel with no dependency on numerologies and/or Transmission Time Interval (TTI) durations. In an example, Automatic Repeat Request (ARQ) may operate on any of the numerologies and/or TTI durations the logical channel is configured with. In an example, services and functions of the PDCP layer for the user plane may comprise sequence numbering, header compression and decompression, transfer of user data, reordering and duplicate detection, PDCP PDU routing (e.g., in case of split bearers), retransmission of PDCP SDUs, ciphering, deciphering and integrity protection, PDCP SDU discard, PDCP re-establishment and data recovery for RLC AM, and/or duplication of PDCP PDUs. In an example, services and functions of SDAP may comprise mapping between a QoS flow and a data radio bearer. In an example, services and functions of SDAP may comprise mapping Quality of Service Indicator (QFI) in DL and UL packets. In an example, a protocol entity of SDAP may be configured for an individual PDU session.

FIG. 2B is an example control plane protocol stack where PDCP (e.g., 233 and 242), RLC (e.g., 234 and 243) and MAC (e.g., 235 and 244) sublayers and PHY (e.g., 236 and 245) layer may be terminated in wireless device (e.g., 110) and gNB (e.g., 120) on a network side and perform service and functions described above. In an example, RRC (e.g., 232 and 241) may be terminated in a wireless device and a gNB on a network side. In an example, services and functions of RRC may comprise broadcast of system information related to AS and NAS, paging initiated by 5GC or RAN, establishment, maintenance and release of an RRC connection between the UE and RAN, security functions including key management, establishment, configuration, maintenance and release of Signaling Radio Bearers (SRBs) and Data Radio Bearers (DRBs), mobility functions, QoS management functions, UE measurement reporting and control of the reporting, detection of and recovery from radio link failure, and/or NAS message transfer to/from NAS from/to a UE. In an example, NAS control protocol (e.g., 231 and 251) may be terminated in the wireless device and AMF (e.g., 130) on a network side and may perform functions such as authentication, mobility management between a UE and a AMF for 3GPP access and non-3GPP access, and session management between a UE and a SMF for 3GPP access and non-3GPP access.

In an example, a base station may configure a plurality of logical channels for a wireless device. A logical channel in the plurality of logical channels may correspond to a radio bearer and the radio bearer may be associated with a QoS requirement. In an example, a base station may configure a logical channel to be mapped to one or more TTIs/numerologies in a plurality of TTIs/numerologies. The wireless device may receive a Downlink Control Information (DCI) via Physical Downlink Control CHannel (PDCCH) indicating an uplink grant. In an example, the uplink grant may be for a first TTI/numerology and may indicate uplink resources for transmission of a transport block. The base station may configure each logical channel in the plurality of logical channels with one or more parameters to be used by a logical channel prioritization procedure at the MAC layer of the wireless device. The one or more parameters may comprise priority, prioritized bit rate, etc. A logical channel in the plurality of logical channels may correspond to one or more buffers comprising data associated with the logical channel. The logical channel prioritization procedure may allocate the uplink resources to one or more first logical channels in the plurality of logical channels and/or one or more MAC Control Elements (CEs). The one or more first logical channels may be mapped to the first TTI/numerology. The MAC layer at the wireless device may multiplex one or more MAC CEs and/or one or more MAC SDUs (e.g., logical channel) in a MAC PDU (e.g., transport block). In an example, the MAC PDU may comprise a MAC header comprising a plurality of MAC sub-headers. A MAC sub-header in the plurality of MAC sub-headers may correspond to a MAC CE or a MAC SUD (logical channel) in the one or more MAC CEs and/or one or more MAC SDUs. In an example, a MAC CE or a logical channel may be configured with a Logical Channel IDentifier (LCID). In an example, LCID for a logical channel or a MAC CE may be fixed/pre-configured. In an example, LCID for a logical channel or MAC CE may be configured for the wireless device by the base station. The MAC sub-header corresponding to a MAC CE or a MAC SDU may comprise LCID associated with the MAC CE or the MAC SDU.

In an example, a base station may activate and/or deactivate and/or impact one or more processes (e.g., set values of one or more parameters of the one or more processes or start and/or stop one or more timers of the one or more processes) at the wireless device by employing one or more MAC commands. The one or more MAC commands may comprise one or more MAC control elements. In an example, the one or more processes may comprise activation and/or deactivation of PDCP packet duplication for one or more radio bearers. The base station may transmit a MAC CE comprising one or more fields, the values of the fields indicating activation and/or deactivation of PDCP duplication for the one or more radio bearers. In an example, the one or more processes may comprise Channel State Information (CSI) transmission of on one or more cells. The base station may transmit one or more MAC CEs indicating activation and/or deactivation of the CSI transmission on the one or more cells. In an example, the one or more processes may comprise activation or deactivation of one or more secondary cells. In an example, the base station may transmit a MA CE indicating activation or deactivation of one or more secondary cells. In an example, the base station may transmit one or more MAC CEs indicating starting and/or stopping one or more Discontinuous Reception (DRX) timers at the wireless device. In an example, the base station may transmit one or more MAC CEs indicating one or more timing advance values for one or more Timing Advance Groups (TAGs).

FIG. 3 is a block diagram of base stations (base station 1, 120A, and base station 2, 120B) and a wireless device 110. A wireless device may be called a UE. A base station may be called a NB, eNB, gNB, and/or ng-eNB. In an example, a wireless device and/or a base station may act as a relay node. The base station 1, 120A, may comprise at least one communication interface 320A (e.g., a wireless modem, an antenna, a wired modem, and/or the like), at least one processor 321A, and at least one set of program code instructions 323A stored in non-transitory memory 322A and executable by the at least one processor 321A. The base station 2, 120B, may comprise at least one communication interface 320B, at least one processor 321B, and at least one set of program code instructions 323B stored in non-transitory memory 322B and executable by the at least one processor 321B.

A base station may comprise many sectors for example: 1, 2, 3, 4, or 6 sectors. A base station may comprise many cells, for example, ranging from 1 to 50 cells or more. A cell may be categorized, for example, as a primary cell or secondary cell. At Radio Resource Control (RRC) connection establishment/re-establishment/handover, one serving cell may provide the NAS (non-access stratum) mobility information (e.g., Tracking Area Identifier (TAI)). At RRC connection re-establishment/handover, one serving cell may provide the security input. This cell may be referred to as the Primary Cell (PCell). In the downlink, a carrier corresponding to the PCell may be a DL Primary Component Carrier (PCC), while in the uplink, a carrier may be an UL PCC. Depending on wireless device capabilities, Secondary Cells (SCells) may be configured to form together with a PCell a set of serving cells. In a downlink, a carrier corresponding to an SCell may be a downlink secondary component carrier (DL SCC), while in an uplink, a carrier may be an uplink secondary component carrier (UL SCC). An SCell may or may not have an uplink carrier.

A cell, comprising a downlink carrier and optionally an uplink carrier, may be assigned a physical cell ID and a cell index. A carrier (downlink or uplink) may belong to one cell. The cell ID or cell index may also identify the downlink carrier or uplink carrier of the cell (depending on the context it is used). In the disclosure, a cell ID may be equally referred to a carrier ID, and a cell index may be referred to a carrier index. In an implementation, a physical cell ID or a cell index may be assigned to a cell. A cell ID may be determined using a synchronization signal transmitted on a downlink carrier. A cell index may be determined using RRC messages. 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 concept may apply to, for example, carrier activation. When the disclosure indicates that a first carrier is activated, the specification may equally mean that a cell comprising the first carrier is activated.

A base station may transmit to a wireless device one or more messages (e.g., RRC messages) comprising a plurality of configuration parameters for one or more cells. One or more cells may comprise at least one primary cell and at least one secondary cell. In an example, an RRC message may be broadcasted or unicasted to the wireless device. In an example, configuration parameters may comprise common parameters and dedicated parameters.

Services and/or functions of an RRC sublayer may comprise at least one of: broadcast of system information related to AS and NAS; paging initiated by 5GC and/or NG-RAN; establishment, maintenance, and/or release of an RRC connection between a wireless device and NG-RAN, which may comprise at least one of addition, modification and release of carrier aggregation; or addition, modification, and/or release of dual connectivity in NR or between E-UTRA and NR. Services and/or functions of an RRC sublayer may further comprise at least one of security functions comprising key management; establishment, configuration, maintenance, and/or release of Signaling Radio Bearers (SRBs) and/or Data Radio Bearers (DRBs); mobility functions which may comprise at least one of a handover (e.g., intra NR mobility or inter-RAT mobility) and a context transfer; or a wireless device cell selection and reselection and control of cell selection and reselection. Services and/or functions of an RRC sublayer may further comprise at least one of QoS management functions; a wireless device measurement configuration/reporting; detection of and/or recovery from radio link failure; or NAS message transfer to/from a core network entity (e.g., AMF, Mobility Management Entity (MME)) from/to the wireless device.

An RRC sublayer may support an RRC_Idle state, an RRC_Inactive state and/or an RRC_Connected state for a wireless device. In an RRC_Idle state, a wireless device may perform at least one of: Public Land Mobile Network (PLMN) selection; receiving broadcasted system information; cell selection/re-selection; monitoring/receiving a paging for mobile terminated data initiated by 5GC; paging for mobile terminated data area managed by 5GC; or DRX for CN paging configured via NAS. In an RRC_Inactive state, a wireless device may perform at least one of: receiving broadcasted system information; cell selection/re-selection; monitoring/receiving a RAN/CN paging initiated by NG-RAN/5GC; RAN-based notification area (RNA) managed by NG-RAN; or DRX for RAN/CN paging configured by NG-RAN/NAS. In an RRC_Idle state of a wireless device, a base station (e.g., NG-RAN) may keep a 5GC-NG-RAN connection (both C/U-planes) for the wireless device; and/or store a UE AS context for the wireless device. In an RRC_Connected state of a wireless device, a base station (e.g., NG-RAN) may perform at least one of: establishment of 5GC-NG-RAN connection (both C/U-planes) for the wireless device; storing a UE AS context for the wireless device; transmit/receive of unicast data to/from the wireless device; or network-controlled mobility based on measurement results received from the wireless device. In an RRC_Connected state of a wireless device, an NG-RAN may know a cell that the wireless device belongs to.

System information (SI) may be divided into minimum SI and other SI. The minimum SI may be periodically broadcast. The minimum SI may comprise basic information required for initial access and information for acquiring any other SI broadcast periodically or provisioned on-demand, i.e. scheduling information. The other SI may either be broadcast, or be provisioned in a dedicated manner, either triggered by a network or upon request from a wireless device. A minimum SI may be transmitted via two different downlink channels using different messages (e.g., MasterInformationBlock and SystemInformationBlockType1). Another SI may be transmitted via SystemInformationBlockType2. For a wireless device in an RRC_Connected state, dedicated RRC signaling may be employed for the request and delivery of the other SI. For the wireless device in the RRC_Idle state and/or the RRC_Inactive state, the request may trigger a random-access procedure.

A wireless device may report its radio access capability information which may be static. A base station may request what capabilities for a wireless device to report based on band information. When allowed by a network, a temporary capability restriction request may be sent by the wireless device to signal the limited availability of some capabilities (e.g., due to hardware sharing, interference, or overheating) to the base station. The base station may confirm or reject the request. The temporary capability restriction may be transparent to 5GC (e.g., static capabilities may be stored in 5GC).

When CA is configured, a wireless device may have an RRC connection with a network. At RRC connection establishment/re-establishment/handover procedure, one serving cell may provide NAS mobility information, and at RRC connection re-establishment/handover, one serving cell may provide a security input. This cell may be referred to as the PCell. Depending on the capabilities of the wireless device, SCells may be configured to form together with the PCell a set of serving cells. The configured set of serving cells for the wireless device may comprise one PCell and one or more SCells.

The reconfiguration, addition, and removal of SCells may be performed by RRC. At intra-NR handover, RRC may also add, remove, or reconfigure SCells for usage with the target PCell. When adding a new SCell, dedicated RRC signaling may be employed to send all required system information of the SCell i.e. while in connected mode, wireless devices may not need to acquire broadcasted system information directly from the SCells.

The purpose of an RRC connection reconfiguration procedure may be to modify an RRC connection, (e.g., to establish, modify and/or release RBs, to perform handover, to setup, modify, and/or release measurements, to add, modify, and/or release SCells and cell groups). As part of the RRC connection reconfiguration procedure, NAS dedicated information may be transferred from the network to the wireless device. The RRCConnectionReconfiguration message may be a command to modify an RRC connection. It may convey information for measurement configuration, mobility control, radio resource configuration (e.g., RBs, MAC main configuration and physical channel configuration) comprising any associated dedicated NAS information and security configuration. If the received RRC Connection Reconfiguration message includes the sCellToReleaseList, the wireless device may perform an SCell release. If the received RRC Connection Reconfiguration message includes the sCellToAddModList, the wireless device may perform SCell additions or modification.

An RRC connection establishment (or reestablishment, resume) procedure may be to establish (or reestablish, resume) an RRC connection. an RRC connection establishment procedure may comprise SRB1 establishment. The RRC connection establishment procedure may be used to transfer the initial NAS dedicated information/message from a wireless device to E-UTRAN. The RRCConnectionReestablishment message may be used to re-establish SRB1.

A measurement report procedure may be to transfer measurement results from a wireless device to NG-RAN. The wireless device may initiate a measurement report procedure after successful security activation. A measurement report message may be employed to transmit measurement results.

The wireless device 110 may comprise at least one communication interface 310 (e.g., a wireless modem, an antenna, and/or the like), at least one processor 314, and at least one set of program code instructions 316 stored in non-transitory memory 315 and executable by the at least one processor 314. The wireless device 110 may further comprise at least one of at least one speaker/microphone 311, at least one keypad 312, at least one display/touchpad 313, at least one power source 317, at least one global positioning system (GPS) chipset 318, and other peripherals 319.

The processor 314 of the wireless device 110, the processor 321A of the base station 1 120A, and/or the processor 321B of the base station 2 120B may comprise at least one of a general-purpose processor, a digital signal processor (DSP), a controller, 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, and the like. The processor 314 of the wireless device 110, the processor 321A in base station 1 120A, and/or the processor 321B in base station 2120B 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 110, the base station 1 120A and/or the base station 2 120B to operate in a wireless environment.

The processor 314 of the wireless device 110 may be connected to the speaker/microphone 311, the keypad 312, and/or the display/touchpad 313. The processor 314 may receive user input data from and/or provide user output data to the speaker/microphone 311, the keypad 312, and/or the display/touchpad 313. The processor 314 in the wireless device 110 may receive power from the power source 317 and/or may be configured to distribute the power to the other components in the wireless device 110. The power source 317 may comprise at least one of one or more dry cell batteries, solar cells, fuel cells, and the like. The processor 314 may be connected to the GPS chipset 318. The GPS chipset 318 may be configured to provide geographic location information of the wireless device 110.

The processor 314 of the wireless device 110 may further be connected to other peripherals 319, which may comprise one or more software and/or hardware modules that provide additional features and/or functionalities. For example, the peripherals 319 may comprise at least one of an accelerometer, a satellite transceiver, a digital camera, a universal serial bus (USB) port, a hands-free headset, a frequency modulated (FM) radio unit, a media player, an Internet browser, and the like.

The communication interface 320A of the base station 1, 120A, and/or the communication interface 320B of the base station 2, 120B, may be configured to communicate with the communication interface 310 of the wireless device 110 via a wireless link 330A and/or a wireless link 330B respectively. In an example, the communication interface 320A of the base station 1, 120A, may communicate with the communication interface 320B of the base station 2 and other RAN and core network nodes.

The wireless link 330A and/or the wireless link 330B may comprise at least one of a bi-directional link and/or a directional link. The communication interface 310 of the wireless device 110 may be configured to communicate with the communication interface 320A of the base station 1 120A and/or with the communication interface 320B of the base station 2 120B. The base station 1 120A and the wireless device 110 and/or the base station 2 120B and the wireless device 110 may be configured to send and receive transport blocks via the wireless link 330A and/or via the wireless link 330B, respectively. The wireless link 330A and/or the wireless link 330B may employ at least one frequency carrier. According to some of various aspects of embodiments, transceiver(s) may be employed. A transceiver may be a device that comprises both a transmitter and a receiver. Transceivers may be employed in devices such as wireless devices, base stations, relay nodes, and/or the like. Example embodiments for radio technology implemented in the communication interface 310, 320A, 320B and the wireless link 330A, 330B are illustrated in FIG. 4A, FIG. 4B, FIG. 4C, FIG. 4D, FIG. 6, FIG. 7A, FIG. 7B, FIG. 8, and associated text.

In an example, other nodes in a wireless network (e.g., AMF, UPF, SMF, etc.) may comprise one or more communication interfaces, one or more processors, and memory storing instructions.

A node (e.g., wireless device, base station, AMF, SMF, UPF, servers, switches, antennas, and/or the like) may comprise one or more processors, and memory storing instructions that when executed by the one or more processors causes the node to perform certain processes and/or functions. Example embodiments may enable operation of single-carrier and/or multi-carrier communications. Other example embodiments may comprise a non-transitory tangible computer readable media comprising instructions executable by one or more processors to cause operation of single-carrier and/or multi-carrier communications. Yet other example embodiments may comprise an article of manufacture that comprises a non-transitory tangible computer readable machine-accessible medium having instructions encoded thereon for enabling programmable hardware to cause a node to enable operation of single-carrier and/or multi-carrier communications. The node may include processors, memory, interfaces, and/or the like.

An interface may comprise at least one of a hardware interface, a firmware interface, a software interface, and/or a combination thereof. The hardware interface may comprise connectors, wires, electronic devices such as drivers, amplifiers, and/or the like. The software interface may comprise code stored in a memory device to implement protocol(s), protocol layers, communication drivers, device drivers, combinations thereof, and/or the like. The firmware interface may comprise a combination of embedded hardware and code stored in and/or in communication with a memory device to implement connections, electronic device operations, protocol(s), protocol layers, communication drivers, device drivers, hardware operations, combinations thereof, and/or the like.

FIG. 4A, FIG. 4B, FIG. 4C and FIG. 4D are example diagrams for uplink and downlink signal transmission as per an aspect of an embodiment of the present disclosure. FIG. 4A shows an example uplink transmitter for at least one physical channel. 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. 4A. These functions are illustrated as examples and it is anticipated that other mechanisms may be implemented in various embodiments.

An example structure for modulation and up-conversion to the carrier frequency of the complex-valued SC-FDMA or CP-OFDM baseband signal for an antenna port and/or the complex-valued Physical Random Access CHannel (PRACH) baseband signal is shown in FIG. 4B. Filtering may be employed prior to transmission.

An example structure for downlink transmissions is shown in FIG. 4C. The baseband signal representing a downlink physical 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.

In an example, a gNB may transmit a first symbol and a second symbol on an antenna port, to a wireless device. The wireless device may infer the channel (e.g., fading gain, multipath delay, etc.) for conveying the second symbol on the antenna port, from the channel for conveying the first symbol on the antenna port. In an example, a first antenna port and a second antenna port may be quasi co-located 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: delay spread; Doppler spread; Doppler shift; average gain; average delay; and/or spatial Receiving (Rx) parameters.

An example modulation and up-conversion to the carrier frequency of the complex-valued OFDM baseband signal for an antenna port is shown in FIG. 4D. Filtering may be employed prior to transmission.

FIG. 5A is a diagram of an example uplink channel mapping and example uplink physical signals. FIG. 5B is a diagram of an example downlink channel mapping and a downlink physical signals. In an example, a physical layer may provide one or more information transfer services to a MAC and/or one or more higher layers. For example, the physical layer may provide the one or more information transfer services to the MAC via one or more transport channels. An information transfer service may indicate how and with what characteristics data are transferred over the radio interface.

In an example embodiment, a radio network may comprise one or more downlink and/or uplink transport channels. For example, a diagram in FIG. 5A shows example uplink transport channels comprising Uplink-Shared CHannel (UL-SCH) 501 and Random Access CHannel (RACH) 502. A diagram in FIG. 5B shows example downlink transport channels comprising Downlink-Shared CHannel (DL-SCH) 511, Paging CHannel (PCH) 512, and Broadcast CHannel (BCH) 513. A transport channel may be mapped to one or more corresponding physical channels. For example, UL-SCH 501 may be mapped to Physical Uplink Shared CHannel (PUSCH) 503. RACH 502 may be mapped to PRACH 505. DL-SCH 511 and PCH 512 may be mapped to Physical Downlink Shared CHannel (PDSCH) 514. BCH 513 may be mapped to Physical Broadcast CHannel (PBCH) 516.

There may be one or more physical channels without a corresponding transport channel. The one or more physical channels may be employed for Uplink Control Information (UCI) 509 and/or Downlink Control Information (DCI) 517. For example, Physical Uplink Control CHannel (PUCCH) 504 may carry UCI 509 from a UE to a base station. For example, Physical Downlink Control CHannel (PDCCH) 515 may carry DCI 517 from a base station to a UE. NR may support UCI 509 multiplexing in PUSCH 503 when UCI 509 and PUSCH 503 transmissions may coincide in a slot at least in part. The UCI 509 may comprise at least one of CSI, Acknowledgement (ACK)/Negative Acknowledgement (NACK), and/or scheduling request. The DCI 517 on PDCCH 515 may indicate at least one of following: one or more downlink assignments and/or one or more uplink scheduling grants

In uplink, a UE may transmit one or more Reference Signals (RSs) to a base station. For example, the one or more RSs may be at least one of Demodulation RS (DMRS) 506, Phase Tracking-RS (PT-RS) 507, and/or Sounding RS (SRS) 508. In downlink, a base station may transmit (e.g., unicast, multicast, and/or broadcast) one or more RSs to a UE. For example, the one or more RSs may be at least one of Primary Synchronization Signal (PSS)/Secondary Synchronization Signal (SSS) 521, CSI-RS 522, DMRS 523, and/or PT-RS 524.

In an example, a UE may transmit one or more uplink DMRSs 506 to a base station for channel estimation, for example, for coherent demodulation of one or more uplink physical channels (e.g., PUSCH 503 and/or PUCCH 504). For example, a UE may transmit a base station at least one uplink DMRS 506 with PUSCH 503 and/or PUCCH 504, wherein the at least one uplink DMRS 506 may be spanning a same frequency range as a corresponding physical channel. In an example, a base station may configure a UE with one or more uplink DMRS configurations. At least one DMRS configuration may support a front-loaded DMRS pattern. A front-loaded DMRS may be mapped over one or more OFDM symbols (e.g., 1 or 2 adjacent OFDM symbols). One or more additional uplink DMRS may be configured to transmit at one or more symbols of a PUSCH and/or PUCCH. A base station may semi-statistically configure a UE with a maximum number of front-loaded DMRS symbols for PUSCH and/or PUCCH. For example, a UE may schedule a single-symbol DMRS and/or double symbol DMRS based on a maximum number of front-loaded DMRS symbols, wherein a base station may configure the UE with one or more additional uplink DMRS for PUSCH and/or PUCCH. A new radio network may support, e.g., at least for CP-OFDM, a common DMRS structure for DL and UL, wherein a DMRS location, DMRS pattern, and/or scrambling sequence may be same or different.

In an example, whether uplink PT-RS 507 is present or not may depend on a RRC configuration. For example, a presence of uplink PT-RS may be UE-specifically configured. For example, a presence and/or a pattern of uplink PT-RS 507 in a scheduled resource may be UE-specifically configured by a combination of RRC signaling and/or 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 uplink PT-RS 507 may be associated with one or more DCI parameters comprising at least MCS. A radio network may support 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. A 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 507 may be confined in the scheduled time/frequency duration for a UE.

In an example, a UE may transmit SRS 508 to a base station for channel state estimation to support uplink channel dependent scheduling and/or link adaptation. For example, SRS 508 transmitted by a UE may allow for a base station to estimate an uplink channel state at one or more different frequencies. A base station scheduler may employ an uplink channel state to assign one or more resource blocks of good quality for an uplink PUSCH transmission from a UE. A base station may semi-statistically configure a UE with one or more SRS resource sets. For an SRS resource set, a base station may configure a 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, a SRS resource in each of one or more SRS resource sets may be transmitted at a time instant. A UE may transmit one or more SRS resources in different SRS resource sets simultaneously. A new radio network may support aperiodic, periodic and/or semi-persistent SRS transmissions. A 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 (e.g., at least one DCI format may be employed for a 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 503 and SRS 508 are transmitted in a same slot, a UE may be configured to transmit SRS 508 after a transmission of PUSCH 503 and corresponding uplink DMRS 506.

In an example, a base station may semi-statistically configure a 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 SRS resource configuration (e.g., an indication of periodic, semi-persistent, or aperiodic SRS), slot (mini-slot, and/or subframe) level periodicity and/or offset for a periodic and/or aperiodic SRS resource, a number of OFDM symbols in a SRS resource, starting OFDM symbol of a SRS resource, a SRS bandwidth, a frequency hopping bandwidth, a cyclic shift, and/or a SRS sequence ID.

In an example, in a time domain, an SS/PBCH block may comprise one or more OFDM symbols (e.g., 4 OFDM symbols numbered in increasing order from 0 to 3) within the SS/PBCH block. An SS/PBCH block may comprise PSS/SSS 521 and PBCH 516. In an example, in the frequency domain, an SS/PBCH block may comprise one or more contiguous subcarriers (e.g., 240 contiguous subcarriers with the subcarriers numbered in increasing order from 0 to 239) within the SS/PBCH block. For example, a PSS/SSS 521 may occupy 1 OFDM symbol and 127 subcarriers. For example, PBCH 516 may span across 3 OFDM symbols and 240 subcarriers. A UE may assume that one or more SS/PBCH blocks transmitted with a same block index may be quasi co-located, e.g., with respect to Doppler spread, Doppler shift, average gain, average delay, and spatial Rx parameters. A UE may not assume quasi co-location for other SS/PBCH block transmissions. A periodicity of an SS/PBCH block may be configured by a radio network (e.g., by an RRC signaling) and one or more time locations where the SS/PBCH block may be sent may be determined by sub-carrier spacing. In an example, a UE may assume a band-specific sub-carrier spacing for an SS/PBCH block unless a radio network has configured a UE to assume a different sub-carrier spacing.

In an example, downlink CSI-RS 522 may be employed for a UE to acquire channel state information. A radio network may support periodic, aperiodic, and/or semi-persistent transmission of downlink CSI-RS 522. For example, a base station may semi-statistically configure and/or reconfigure a UE with periodic transmission of downlink CSI-RS 522. A configured CSI-RS resources may be activated ad/or deactivated. For semi-persistent transmission, an activation and/or deactivation of CSI-RS resource may be triggered dynamically. In an example, CSI-RS configuration may comprise one or more parameters indicating at least a number of antenna ports. For example, a base station may configure a UE with 32 ports. A base station may semi-statistically configure a UE with one or more CSI-RS resource sets. One or more CSI-RS resources may be allocated from one or more CSI-RS resource sets to one or more UEs. For example, a base station may semi-statistically configure one or more parameters indicating CSI RS resource mapping, for example, time-domain location of one or more CSI-RS resources, a bandwidth of a CSI-RS resource, and/or a periodicity. In an example, a UE may be configured to employ a same OFDM symbols for downlink CSI-RS 522 and COntrol REsource SET (CORESET) when the downlink CSI-RS 522 and CORESET are spatially quasi co-located and resource elements associated with the downlink CSI-RS 522 are the outside of Physical Resource Block (PRB)s configured for CORESET. In an example, a UE may be configured to employ a same OFDM symbols for downlink CSI-RS 522 and SSB/PBCH when the downlink CSI-RS 522 and SSB/PBCH are spatially quasi co-located and resource elements associated with the downlink CSI-RS 522 are the outside of PRBs configured for SSB/PBCH.

In an example, a UE may transmit one or more downlink DMRSs 523 to a base station for channel estimation, for example, for coherent demodulation of one or more downlink physical channels (e.g., PDSCH 514). For example, a radio 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., 1 or 2 adjacent OFDM symbols). A base station may semi-statistically configure a UE with a maximum number of front-loaded DMRS symbols for PDSCH 514. For example, a DMRS configuration may support one or more DMRS ports. For example, for single user-MIMO, a DMRS configuration may support at least 8 orthogonal downlink DMRS ports. For example, for multiuser-MIMO, a DMRS configuration may support 12 orthogonal downlink DMRS ports. A radio network may support, e.g., at least for CP-OFDM, a common DMRS structure for DL and UL, wherein a DMRS location, DMRS pattern, and/or scrambling sequence may be same or different.

In an example, whether downlink PT-RS 524 is present or not may depend on a RRC configuration. For example, a presence of downlink PT-RS 524 may be UE-specifically configured. For example, a presence and/or a pattern of downlink PT-RS 524 in a scheduled resource may be UE-specifically configured by a combination of RRC signaling and/or association with one or more parameters employed for other purposes (e.g., MCS) which may be indicated by DCI. When configured, a dynamic presence of downlink PT-RS 524 may be associated with one or more DCI parameters comprising at least MCS. A radio network may support plurality of 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. A 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, downlink PT-RS 524 may be confined in the scheduled time/frequency duration for a UE.

FIG. 6 is a diagram depicting an example frame structure for a carrier as per an aspect of an embodiment of the present disclosure. A multicarrier OFDM communication system may include one or more carriers, for example, ranging from 1 to 32 carriers, in case of carrier aggregation, or ranging from 1 to 64 carriers, in case of dual connectivity. Different radio frame structures may be supported (e.g., for FDD and for TDD duplex mechanisms). FIG. 6 shows an example frame structure. Downlink and uplink transmissions may be organized into radio frames 601. In this example, radio frame duration is 10 ms. In this example, a 10 ms radio frame 601 may be divided into ten equally sized subframes 602 with 1 ms duration. Subframe(s) may comprise one or more slots (e.g., slots 603 and 605) depending on subcarrier spacing and/or CP length. For example, a subframe with 15 kHz, 30 kHz, 60 kHz, 120 kHz, 240 kHz and 480 kHz subcarrier spacing may comprise one, two, four, eight, sixteen and thirty-two slots, respectively. In FIG. 6, a subframe may be divided into two equally sized slots 603 with 0.5 ms duration. For example, 10 subframes may be available for downlink transmission and 10 subframes may be available for uplink transmissions in a 10 ms interval. Uplink and downlink transmissions may be separated in the frequency domain. Slot(s) may include a plurality of OFDM symbols 604. The number of OFDM symbols 604 in a slot 605 may depend on the cyclic prefix length. For example, a slot may be 14 OFDM symbols for the same subcarrier spacing of up to 480 kHz with normal CP. A slot may be 12 OFDM symbols for the same subcarrier spacing of 60 kHz with extended CP. A slot may contain downlink, uplink, or a downlink part and an uplink part and/or alike.

FIG. 7A is a diagram depicting example sets of OFDM subcarriers as per an aspect of an embodiment of the present disclosure. In the example, a gNB may communicate with a wireless device with a carrier with an example channel bandwidth 700. Arrow(s) in the diagram may depict a subcarrier in a multicarrier OFDM system. The OFDM system may use technology such as OFDM technology, SC-FDMA technology, and/or the like. In an example, an arrow 701 shows a subcarrier transmitting information symbols. In an example, a subcarrier spacing 702, between two contiguous subcarriers in a carrier, may be any one of 15 KHz, 30 KHz, 60 KHz, 120 KHz, 240 KHz etc. In an example, different subcarrier spacing may correspond to different transmission numerologies. In an example, a transmission numerology may comprise at least: a numerology index; a value of subcarrier spacing; a type of cyclic prefix (CP). In an example, a gNB may transmit to/receive from a UE on a number of subcarriers 703 in a carrier. In an example, a bandwidth occupied by a number of subcarriers 703 (transmission bandwidth) may be smaller than the channel bandwidth 700 of a carrier, due to guard band 704 and 705. In an example, a guard band 704 and 705 may be used to reduce interference to and from one or more neighbor carriers. A number of subcarriers (transmission bandwidth) in a carrier may depend on the channel bandwidth of the carrier and the subcarrier spacing. For example, a transmission bandwidth, for a carrier with 20 MHz channel bandwidth and 15 KHz subcarrier spacing, may be in number of 1024 subcarriers.

In an example, a gNB and a wireless device may communicate with multiple CCs when configured with CA. In an example, different component carriers may have different bandwidth and/or subcarrier spacing, if CA is supported. In an example, a gNB may transmit a first type of service to a UE on a first component carrier. The gNB may transmit a second type of service to the UE on a second component carrier. Different type of services may have different service requirement (e.g., data rate, latency, reliability), which may be suitable for transmission via different component carrier having different subcarrier spacing and/or bandwidth. FIG. 7B shows an example embodiment. A first component carrier may comprise a first number of subcarriers 706 with a first subcarrier spacing 709. A second component carrier may comprise a second number of subcarriers 707 with a second subcarrier spacing 710. A third component carrier may comprise a third number of subcarriers 708 with a third subcarrier spacing 711. Carriers in a multicarrier OFDM communication system may be contiguous carriers, non-contiguous carriers, or a combination of both contiguous and non-contiguous carriers.

FIG. 8 is a diagram depicting OFDM radio resources as per an aspect of an embodiment of the present disclosure. In an example, a carrier may have a transmission bandwidth 801. In an example, a resource grid may be in a structure of frequency domain 802 and time domain 803. In an example, a resource grid may comprise a first number of OFDM symbols in a subframe and a second number of resource blocks, starting from a common resource block indicated by higher-layer signaling (e.g., RRC signaling), for a transmission numerology and a carrier. In an example, in a resource grid, a resource unit identified by a subcarrier index and a symbol index may be a resource element 805. In an example, a subframe may comprise a first number of OFDM symbols 807 depending on a numerology associated with a carrier. For example, when a subcarrier spacing of a numerology of a carrier is 15 KHz, a subframe may have 14 OFDM symbols for a carrier. When a subcarrier spacing of a numerology is 30 KHz, a subframe may have 28 OFDM symbols. When a subcarrier spacing of a numerology is 60 Khz, a subframe may have 56 OFDM symbols, etc. In an example, a second number of resource blocks comprised in a resource grid of a carrier may depend on a bandwidth and a numerology of the carrier.

As shown in FIG. 8, a resource block 806 may comprise 12 subcarriers. In an example, multiple resource blocks may be grouped into a Resource Block Group (RBG) 804. In an example, a size of a RBG may depend on at least one of: a RRC message indicating a RBG size configuration; a size of a carrier bandwidth; or a size of a bandwidth part of a carrier. In an example, a carrier may comprise multiple bandwidth parts. A first bandwidth part of a carrier may have different frequency location and/or bandwidth from a second bandwidth part of the carrier.

In an example, a gNB may transmit a downlink control information comprising a downlink or uplink resource block assignment to a wireless device. A base station may transmit to or receive from, a wireless device, data packets (e.g., transport blocks) scheduled and transmitted via one or more resource blocks and one or more slots according to parameters in a downlink control information and/or RRC message(s). In an example, a starting symbol relative to a first slot of the one or more slots may be indicated to the wireless device. In an example, a gNB may transmit to or receive from, a wireless device, data packets scheduled on one or more RBGs and one or more slots.

In an example, a gNB may transmit a downlink control information comprising a downlink assignment to a wireless device via one or more PDCCHs. The downlink assignment may comprise parameters indicating at least modulation and coding format; resource allocation; and/or HARQ information related to DL-SCH. In an example, a resource allocation may comprise parameters of resource block allocation; and/or slot allocation. In an example, a gNB may dynamically allocate resources to a wireless device via a Cell-Radio Network Temporary Identifier (C-RNTI) on one or more PDCCHs. The wireless device may monitor the one or more PDCCHs in order to find possible allocation when its downlink reception is enabled. The wireless device may receive one or more downlink data package on one or more PDSCH scheduled by the one or more PDCCHs, when successfully detecting the one or more PDCCHs.

In an example, a gNB may allocate Configured Scheduling (CS) resources for down link transmission to a wireless device. The gNB may transmit one or more RRC messages indicating a periodicity of the CS grant. The gNB may transmit a DCI via a PDCCH addressed to a Configured Scheduling-RNTI (CS-RNTI) activating the CS resources. The DCI may comprise parameters indicating that the downlink grant is a CS grant. The CS grant may be implicitly reused according to the periodicity defined by the one or more RRC messages, until deactivated.

In an example, a gNB may transmit a downlink control information comprising an uplink grant to a wireless device via one or more PDCCHs. The uplink grant may comprise parameters indicating at least modulation and coding format; resource allocation; and/or HARQ information related to UL-SCH. In an example, a resource allocation may comprise parameters of resource block allocation; and/or slot allocation. In an example, a gNB may dynamically allocate resources to a wireless device via a C-RNTI on one or more PDCCHs. The wireless device may monitor the one or more PDCCHs in order to find possible resource allocation. The wireless device may transmit one or more uplink data package via one or more PUSCH scheduled by the one or more PDCCHs, when successfully detecting the one or more PDCCHs.

In an example, a gNB may allocate CS resources for uplink data transmission to a wireless device. The gNB may transmit one or more RRC messages indicating a periodicity of the CS grant. The gNB may transmit a DCI via a PDCCH addressed to a CS-RNTI activating the CS resources. The DCI may comprise parameters indicating that the uplink grant is a CS grant. The CS grant may be implicitly reused according to the periodicity defined by the one or more RRC message, until deactivated.

In an example, a base station may transmit DCI/control signaling via PDCCH. The DCI may take a format in a plurality of formats. A DCI may comprise downlink and/or uplink scheduling information (e.g., resource allocation information, HARQ related parameters, MCS), request for CSI (e.g., aperiodic CQI reports), request for SRS, uplink power control commands for one or more cells, one or more timing information (e.g., TB transmission/reception timing, HARQ feedback timing, etc.), etc. In an example, a DCI may indicate an uplink grant comprising transmission parameters for one or more transport blocks. In an example, a DCI may indicate downlink assignment indicating parameters for receiving one or more transport blocks. In an example, a DCI may be used by base station to initiate a contention-free random access at the wireless device. In an example, the base station may transmit a DCI comprising slot format indicator (SFI) notifying a slot format. In an example, the base station may transmit a DCI comprising preemption indication notifying the PRB(s) and/or OFDM symbol(s) where a UE may assume no transmission is intended for the UE. In an example, the base station may transmit a DCI for group power control of PUCCH or PUSCH or SRS. In an example, a DCI may correspond to an RNTI. In an example, the wireless device may obtain an RNTI in response to completing the initial access (e.g., C-RNTI). In an example, the base station may configure an RNTI for the wireless (e.g., CS-RNTI, TPC-CS-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI, TPC-SRS-RNTI). In an example, the wireless device may compute an RNTI (e.g., the wireless device may compute RA-RNTI based on resources used for transmission of a preamble). In an example, an RNTI may have a pre-configured value (e.g., P-RNTI or SI-RNTI). In an example, a wireless device may monitor a group common search space which may be used by base station for transmitting DCIs that are intended for a group of UEs. In an example, a group common DCI may correspond to an RNTI which is commonly configured for a group of UEs. In an example, a wireless device may monitor a UE-specific search space. In an example, a UE specific DCI may correspond to an RNTI configured for the wireless device.

A NR system may support a single beam operation and/or a multi-beam operation. In a multi-beam operation, a base station may perform a downlink beam sweeping to provide coverage for common control channels and/or downlink SS blocks, which may comprise at least a PSS, a SSS, and/or PBCH. A wireless device may measure quality of a beam pair link using one or more RSs. One or more SS blocks, or one or more CSI-RS resources, associated with a CSI-RS resource index (CRI), or one or more DMRSs of PBCH, may be used as RS for measuring quality of a beam pair link. Quality of a beam pair link may be defined as a reference signal received power (RSRP) value, or a reference signal received quality (RSRQ) value, and/or a CSI value measured on RS resources. The base station may indicate whether an RS resource, used for measuring a beam pair link quality, is quasi-co-located (QCLed) with DMRSs of a control channel. A RS resource and DMRSs of a control channel may be called QCLed when a channel characteristics from a transmission on an RS to a wireless device, and that from a transmission on a control channel to a wireless device, are similar or same under a configured criterion. In a multi-beam operation, a wireless device may perform an uplink beam sweeping to access a cell.

In an example, a wireless device may be configured to monitor PDCCH on one or more beam pair links simultaneously depending on a capability of a wireless device. This may increase robustness against beam pair link blocking. A base station may transmit one or more messages to configure a wireless device to monitor PDCCH on one or more beam pair links in different PDCCH OFDM symbols. For example, a base station may transmit higher layer signaling (e.g., RRC signaling) or MAC CE comprising parameters related to the Rx beam setting of a wireless device for monitoring PDCCH on one or more beam pair links. A base station may transmit indication of spatial QCL assumption between an DL RS antenna port(s) (for example, cell-specific CSI-RS, or wireless device-specific CSI-RS, or SS block, or PBCH with or without DMRSs of PBCH), and DL RS antenna port(s) for demodulation of DL control channel. Signaling for beam indication for a PDCCH may be MAC CE signaling, or RRC signaling, or DCI signaling, or specification-transparent and/or implicit method, and combination of these signaling methods.

For reception of unicast DL data channel, a base station may indicate spatial QCL parameters between DL RS antenna port(s) and DMRS antenna port(s) of DL data channel. The base station may transmit DCI (e.g., downlink grants) comprising information indicating the RS antenna port(s). The information may indicate RS antenna port(s) which may be QCL-ed with the DMRS antenna port(s). Different set of DMRS antenna port(s) for a DL data channel may be indicated as QCL with different set of the RS antenna port(s).

FIG. 9A is an example of beam sweeping in a DL channel. In an RRC_INACTIVE state or RRC_IDLE state, a wireless device may assume that SS blocks form an SS burst 940, and an SS burst set 950. The SS burst set 950 may have a given periodicity. For example, in a multi-beam operation, a base station 120 may transmit SS blocks in multiple beams, together forming a SS burst 940. One or more SS blocks may be transmitted on one beam. If multiple SS bursts 940 are transmitted with multiple beams, SS bursts together may form SS burst set 950.

A wireless device may further use CSI-RS in the multi-beam operation for estimating a beam quality of a links between a wireless device and a base station. A beam may be associated with a CSI-RS. For example, a wireless device may, based on a RSRP measurement on CSI-RS, report a beam index, as indicated in a CRI for downlink beam selection, and associated with a RSRP value of a beam. A CSI-RS may be transmitted on a CSI-RS resource including at least one of one or more antenna ports, one or more time or frequency radio resources. A CSI-RS resource may be configured in a cell-specific way by common RRC signaling, or in a wireless device-specific way by dedicated RRC signaling, and/or L1/L2 signaling. Multiple wireless devices covered by a cell may measure a cell-specific CSI-RS resource. A dedicated subset of wireless devices covered by a cell may measure a wireless device-specific CSI-RS resource.

A CSI-RS resource may be transmitted periodically, or using aperiodic transmission, or using a multi-shot or semi-persistent transmission. For example, in a periodic transmission in FIG. 9A, a base station 120 may transmit configured CSI-RS resources 940 periodically using a configured periodicity in a time domain. In an aperiodic transmission, a configured CSI-RS resource may be transmitted in a dedicated time slot. In a multi-shot or semi-persistent transmission, a configured CSI-RS resource may be transmitted within a configured period. Beams used for CSI-RS transmission may have different beam width than beams used for SS-blocks transmission.

FIG. 9B is an example of a beam management procedure in an example new radio network. A base station 120 and/or a wireless device 110 may perform a downlink L1/L2 beam management procedure. One or more of the following downlink L1/L2 beam management procedures may be performed within one or more wireless devices 110 and one or more base stations 120. In an example, a P-1 procedure 910 may be used to enable the wireless device 110 to measure one or more Transmission (Tx) beams associated with the base station 120 to support a selection of a first set of Tx beams associated with the base station 120 and a first set of Rx beam(s) associated with a wireless device 110. For beamforming at a base station 120, a base station 120 may sweep a set of different TX beams. For beamforming at a wireless device 110, a wireless device 110 may sweep a set of different Rx beams. In an example, a P-2 procedure 920 may be used to enable a wireless device 110 to measure one or more Tx beams associated with a base station 120 to possibly change a first set of Tx beams associated with a base station 120. A P-2 procedure 920 may be performed on a possibly smaller set of beams for beam refinement than in the P-1 procedure 910. A P-2 procedure 920 may be a special case of a P-1 procedure 910. In an example, a P-3 procedure 930 may be used to enable a wireless device 110 to measure at least one Tx beam associated with a base station 120 to change a first set of Rx beams associated with a wireless device 110.

A wireless device 110 may transmit one or more beam management reports to a base station 120. In one or more beam management reports, a wireless device 110 may indicate some beam pair quality parameters, comprising at least, one or more beam identifications; RSRP; Precoding Matrix Indicator (PMI)/Channel Quality Indicator (CQI)/Rank Indicator (RI) of a subset of configured beams. Based on one or more beam management reports, a base station 120 may transmit to a wireless device 110 a signal indicating that one or more beam pair links are one or more serving beams. A base station 120 may transmit PDCCH and PDSCH for a wireless device 110 using one or more serving beams.

In an example embodiment, new radio network may support a Bandwidth Adaptation (BA). In an example, receive and/or transmit bandwidths configured by an UE employing a BA may not be large. For example, a receive and/or transmit bandwidths may not be as large as a bandwidth of a cell. Receive and/or transmit bandwidths may be adjustable. For example, a UE may change receive and/or transmit bandwidths, e.g., to shrink during period of low activity to save power. For example, a UE may change a location of receive and/or transmit bandwidths in a frequency domain, e.g., to increase scheduling flexibility. For example, a UE may change a subcarrier spacing, e.g., to allow different services.

In an example embodiment, a subset of a total cell bandwidth of a cell may be referred to as a Bandwidth Part (BWP). A base station may configure a UE with one or more BWPs to achieve a BA. For example, a base station may indicate, to a UE, which of the one or more (configured) BWPs is an active BWP.

FIG. 10 is an example diagram of 3 BWPs configured: BWP1 (1010 and 1050) with a width of 40 MHz and subcarrier spacing of 15 kHz; BWP2 (1020 and 1040) with a width of 10 MHz and subcarrier spacing of 15 kHz; BWP3 1030 with a width of 20 MHz and subcarrier spacing of 60 kHz.

In an example, a UE, configured for operation in one or more BWPs of a cell, may be configured by one or more higher layers (e.g., RRC layer) for a cell a set of one or more BWPs (e.g., at most four BWPs) for receptions by the UE (DL BWP set) in a DL bandwidth by at least one parameter DL-BWP and a set of one or more BWPs (e.g., at most four BWPs) for transmissions by a UE (UL BWP set) in an UL bandwidth by at least one parameter UL-BWP for a cell.

To enable BA on the PCell, a base station may configure a UE with one or more UL and DL BWP pairs. To enable BA on SCells (e.g., in case of CA), a base station may configure a UE at least with one or more DL BWPs (e.g., there may be none in an UL).

In an example, an initial active DL BWP may be defined by at least one of a location and number of contiguous PRBs, a subcarrier spacing, or a cyclic prefix, for a control resource set for at least one common search space. For operation on the PCell, one or more higher layer parameters may indicate at least one initial UL BWP for a random access procedure. If a UE is configured with a secondary carrier on a primary cell, the UE may be configured with an initial BWP for random access procedure on a secondary carrier.

In an example, for unpaired spectrum operation, a UE may expect that a center frequency for a DL BWP may be same as a center frequency for a UL BWP.

For example, for a DL BWP or an UL BWP in a set of one or more DL BWPs or one or more UL BWPs, respectively, a base statin may semi-statistically configure a UE for a cell with one or more parameters indicating at least one of following: a subcarrier spacing; a cyclic prefix; a number of contiguous PRBs; an index in the set of one or more DL BWPs and/or one or more UL BWPs; a link between a DL BWP and an UL BWP from a set of configured DL BWPs and UL BWPs; a DCI detection to a PDSCH reception timing; a PDSCH reception to a HARQ-ACK transmission timing value; a DCI detection to a PUSCH transmission timing value; an offset of a first PRB of a DL bandwidth or an UL bandwidth, respectively, relative to a first PRB of a bandwidth.

In an example, for a DL BWP in a set of one or more DL BWPs on a PCell, a base station may configure a UE with one or more control resource sets for at least one type of common search space and/or one UE-specific search space. For example, a base station may not configure a UE without a common search space on a PCell, or on a PSCell, in an active DL BWP.

For an UL BWP in a set of one or more UL BWPs, a base station may configure a UE with one or more resource sets for one or more PUCCH transmissions.

In an example, if a DCI comprises a BWP indicator field, a BWP indicator field value may indicate an active DL BWP, from a configured DL BWP set, for one or more DL receptions. If a DCI comprises a BWP indicator field, a BWP indicator field value may indicate an active UL BWP, from a configured UL BWP set, for one or more UL transmissions.

In an example, for a PCell, a base station may semi-statistically configure a UE with a default DL BWP among configured DL BWPs. If a UE is not provided a default DL BWP, a default BWP may be an initial active DL BWP.

In an example, a base station may configure a UE with a timer value for a PCell. For example, a UE may start a timer, referred to as BWP inactivity timer, when a UE detects a DCI indicating an active DL BWP, other than a default DL BWP, for a paired spectrum operation or when a UE detects a DCI indicating an active DL BWP or UL BWP, other than a default DL BWP or UL BWP, for an unpaired spectrum operation. The UE may increment the timer by an interval of a first value (e.g., the first value may be 1 millisecond or 0.5 milliseconds) if the UE does not detect a DCI during the interval for a paired spectrum operation or for an unpaired spectrum operation. In an example, the timer may expire when the timer is equal to the timer value. A UE may switch to the default DL BWP from an active DL BWP when the timer expires.

In an example, a base station may semi-statistically 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 BWP inactivity timer (for example, the second BWP may be a default BWP). For example, FIG. 10 is an example diagram of 3 BWPs configured, BWP1 (1010 and 1050), BWP2 (1020 and 1040), and BWP3 (1030). BWP2 (1020 and 1040) may be a default BWP. BWP1 (1010) may be an initial active BWP. In an example, a UE may switch an active BWP from BWP1 1010 to BWP2 1020 in response to an expiry of BWP inactivity timer. For example, a UE may switch an active BWP from BWP2 1020 to BWP3 1030 in response to receiving a DCI indicating BWP3 1030 as an active BWP. Switching an active BWP from BWP3 1030 to BWP2 1040 and/or from BWP2 1040 to BWP1 1050 may be in response to receiving a DCI indicating an active BWP and/or in response to an expiry of BWP inactivity timer.

In an example, if a UE is configured for a secondary cell with a default DL BWP among configured DL BWPs and a timer value, UE procedures on a secondary cell may be same as on a primary cell using the timer value for the secondary cell and the default DL BWP for the secondary cell.

In an example, if a base station configures a UE with a first active DL BWP and a first active UL BWP on a secondary cell or carrier, a UE may employ an indicated DL BWP and an indicated UL BWP on a secondary cell as a respective first active DL BWP and first active UL BWP on a secondary cell or carrier.

FIG. 11A and FIG. 11B show packet flows employing a multi connectivity (e.g., dual connectivity, multi connectivity, tight interworking, and/or the like). FIG. 11A is an example diagram of a protocol structure of a wireless device 110 (e.g., UE) with CA and/or multi connectivity as per an aspect of an embodiment. FIG. 11B is an example diagram of a protocol structure of multiple base stations with CA and/or multi connectivity as per an aspect of an embodiment. The multiple base stations may comprise a master node, MN 1130 (e.g., a master node, a master base station, a master gNB, a master eNB, and/or the like) and a secondary node, SN 1150 (e.g., a secondary node, a secondary base station, a secondary gNB, a secondary eNB, and/or the like). A master node 1130 and a secondary node 1150 may co-work to communicate with a wireless device 110.

When multi connectivity is configured for a wireless device 110, the wireless device 110, which may support multiple reception/transmission functions in an RRC connected state, may be configured to utilize radio resources provided by multiple schedulers of a multiple base stations. Multiple base stations may be inter-connected via a non-ideal or ideal backhaul (e.g., Xn interface, X2 interface, and/or the like). A base station involved in multi connectivity for a certain wireless device may perform at least one of two different roles: a base station may either act as a master base station or as a secondary base station. In multi connectivity, a wireless device may be connected to one master base station and one or more secondary base stations. In an example, a master base station (e.g., the MN 1130) may provide a master cell group (MCG) comprising a primary cell and/or one or more secondary cells for a wireless device (e.g., the wireless device 110). A secondary base station (e.g., the SN 1150) may provide a secondary cell group (SCG) comprising a primary secondary cell (PSCell) and/or one or more secondary cells for a wireless device (e.g., the wireless device 110).

In multi connectivity, a radio protocol architecture that a bearer employs may depend on how a bearer is setup. In an example, three different type of bearer setup options may be supported: an MCG bearer, an SCG bearer, and/or a split bearer. A wireless device may receive/transmit packets of an MCG bearer via one or more cells of the MCG, and/or may receive/transmits packets of an SCG bearer via one or more cells of an SCG. Multi-connectivity may also be described as having at least one bearer configured to use radio resources provided by the secondary base station. Multi-connectivity may or may not be configured/implemented in some of the example embodiments.

In an example, a wireless device (e.g., Wireless Device 110) may transmit and/or receive: packets of an MCG bearer via an SDAP layer (e.g., SDAP 1110), a PDCP layer (e.g., NR PDCP 1111), an RLC layer (e.g., MN RLC 1114), and a MAC layer (e.g., MN MAC 1118); packets of a split bearer via an SDAP layer (e.g., SDAP 1110), a PDCP layer (e.g., NR PDCP 1112), one of a master or secondary RLC layer (e.g., MN RLC 1115, SN RLC 1116), and one of a master or secondary MAC layer (e.g., MN MAC 1118, SN MAC 1119); and/or packets of an SCG bearer via an SDAP layer (e.g., SDAP 1110), a PDCP layer (e.g., NR PDCP 1113), an RLC layer (e.g., SN RLC 1117), and a MAC layer (e.g., MN MAC 1119).

In an example, a master base station (e.g., MN 1130) and/or a secondary base station (e.g., SN 1150) may transmit/receive: packets of an MCG bearer via a master or secondary node SDAP layer (e.g., SDAP 1120, SDAP 1140), a master or secondary node PDCP layer (e.g., NR PDCP 1121, NR PDCP 1142), a master node RLC layer (e.g., MN RLC 1124, MN RLC 1125), and a master node MAC layer (e.g., MN MAC 1128); packets of an SCG bearer via a master or secondary node SDAP layer (e.g., SDAP 1120, SDAP 1140), a master or secondary node PDCP layer (e.g., NR PDCP 1122, NR PDCP 1143), a secondary node RLC layer (e.g., SN RLC 1146, SN RLC 1147), and a secondary node MAC layer (e.g., SN MAC 1148); packets of a split bearer via a master or secondary node SDAP layer (e.g., SDAP 1120, SDAP 1140), a master or secondary node PDCP layer (e.g., NR PDCP 1123, NR PDCP 1141), a master or secondary node RLC layer (e.g., MN RLC 1126, SN RLC 1144, SN RLC 1145, MN RLC 1127), and a master or secondary node MAC layer (e.g., MN MAC 1128, SN MAC 1148).

In multi connectivity, a wireless device may configure multiple MAC entities: one MAC entity (e.g., MN MAC 1118) for a master base station, and other MAC entities (e.g., SN MAC 1119) for a secondary base station. In multi-connectivity, a configured set of serving cells for a wireless device may comprise two subsets: an MCG comprising serving cells of a master base station, and SCGs comprising serving cells of a secondary base station. For an SCG, one or more of following configurations may be applied: at least one cell of an SCG has a configured UL CC and at least one cell of a SCG, named as primary secondary cell (PSCell, PCell of SCG, or sometimes called PCell), is configured with PUCCH resources; when an SCG is configured, there may be at least one SCG bearer or one Split bearer; upon detection of a physical layer problem or a random access problem on a PSCell, or a number of NR RLC retransmissions has been reached associated with the SCG, or upon detection of an access problem on a PSCell during a SCG addition or a SCG change: an RRC connection re-establishment procedure may not be triggered, UL transmissions towards cells of an SCG may be stopped, a master base station may be informed by a wireless device of a SCG failure type, for split bearer, a DL data transfer over a master base station may be maintained; an NR RLC acknowledged mode (AM) bearer may be configured for a split bearer; PCell and/or PSCell may not be de-activated; PSCell may be changed with a SCG change procedure (e.g., with security key change and a RACH procedure); and/or a bearer type change between a split bearer and a SCG bearer or simultaneous configuration of a SCG and a split bearer may or may not supported.

With respect to interaction between a master base station and a secondary base stations for multi-connectivity, one or more of the following may be applied: a master base station and/or a secondary base station may maintain RRM measurement configurations of a wireless device; a master base station may (e.g., based on received measurement reports, traffic conditions, and/or bearer types) may decide to request a secondary base station to provide additional resources (e.g., serving cells) for a wireless device; upon receiving a request from a master base station, a secondary base station may create/modify a container that may result in configuration of additional serving cells for a wireless device (or decide that the secondary base station has no resource available to do so); for a UE capability coordination, a master base station may provide (a part of) an AS configuration and UE capabilities to a secondary base station; a master base station and a secondary base station may exchange information about a UE configuration by employing of RRC containers (inter-node messages) carried via Xn messages; a secondary base station may initiate a reconfiguration of the secondary base station existing serving cells (e.g., PUCCH towards the secondary base station); a secondary base station may decide which cell is a PSCell within a SCG; a master base station may or may not change content of RRC configurations provided by a secondary base station; in case of a SCG addition and/or a SCG SCell addition, a master base station may provide recent (or the latest) measurement results for SCG cell(s); a master base station and secondary base stations may receive information of SFN and/or subframe offset of each other from OAM and/or via an Xn interface, (e.g., for a purpose of DRX alignment and/or identification of a measurement gap). In an example, when adding a new SCG SCell, dedicated RRC signaling may be used for sending required system information of a cell as for CA, except for a SFN acquired from a MIB of a PSCell of a SCG.

FIG. 12 is an example diagram of a random access procedure. One or more events may trigger a random access procedure. For example, one or more events may be at least one of following: initial access from RRC_IDLE, RRC connection re-establishment procedure, handover, DL or UL data arrival during RRC_CONNECTED when UL synchronization status is non-synchronized, transition from RRC_Inactive, and/or request for other system information. For example, a PDCCH order, a MAC entity, and/or a beam failure indication may initiate a random access procedure.

In an example embodiment, a random access procedure may be at least one of a contention based random access procedure and a contention free random access procedure. For example, a contention based random access procedure may comprise, one or more Msg 1 1220 transmissions, one or more Msg2 1230 transmissions, one or more Msg3 1240 transmissions, and contention resolution 1250. For example, a contention free random access procedure may comprise one or more Msg 1 1220 transmissions and one or more Msg2 1230 transmissions.

In an example, a base station may transmit (e.g., unicast, multicast, or broadcast), to a UE, a RACH configuration 1210 via one or more beams. The RACH configuration 1210 may comprise one or more parameters indicating at least one of following: available set of PRACH resources for a transmission of a random access preamble, initial preamble power (e.g., random access preamble initial received target power), an RSRP threshold for a selection of a SS block and corresponding PRACH resource, a power-ramping factor (e.g., random access preamble power ramping step), random access preamble index, a maximum number of preamble transmission, preamble group A and group B, a threshold (e.g., message size) to determine the groups of random access preambles, a set of one or more random access preambles for system information request and corresponding PRACH resource(s), if any, a set of one or more random access preambles for beam failure recovery request and corresponding PRACH resource(s), if any, a time window to monitor RA response(s), a time window to monitor response(s) on beam failure recovery request, and/or a contention resolution timer.

In an example, the Msg1 1220 may be one or more transmissions of a random access preamble. For a contention based random access procedure, a UE may select a SS block with a RSRP above the RSRP threshold. If random access preambles group B exists, a UE may select one or more random access preambles from a group A or a group B depending on a potential Msg3 1240 size. If a random access preambles group B does not exist, a UE may select the one or more random access preambles from a group A. A UE may select a random access preamble index randomly (e.g., with equal probability or a normal distribution) from one or more random access preambles associated with a selected group. If a base station semi-statistically configures a UE with an association between random access preambles and SS blocks, the UE may select a random access preamble index randomly with equal probability from one or more random access preambles associated with a selected SS block and a selected group.

For example, a UE may initiate a contention free random access procedure based on a beam failure indication from a lower layer. For example, a base station may semi-statistically configure a UE with one or more contention free PRACH resources for beam failure recovery request associated with at least one of SS blocks and/or CSI-RSs. If at least one of SS blocks with a RSRP above a first RSRP threshold amongst associated SS blocks or at least one of CSI-RSs with a RSRP above a second RSRP threshold amongst associated CSI-RSs is available, a UE may select a random access preamble index corresponding to a selected SS block or CSI-RS from a set of one or more random access preambles for beam failure recovery request.

For example, a UE may receive, from a base station, a random access preamble index via PDCCH or RRC for a contention free random access procedure. If a base station does not configure a UE with at least one contention free PRACH resource associated with SS blocks or CSI-RS, the UE may select a random access preamble index. If a base station configures a UE with one or more contention free PRACH resources associated with SS blocks and at least one SS block with a RSRP above a first RSRP threshold amongst associated SS blocks is available, the UE may select the at least one SS block and select a random access preamble corresponding to the at least one SS block. If a base station configures a UE with one or more contention free PRACH resources associated with CSI-RSs and at least one CSI-RS with a RSRP above a second RSPR threshold amongst the associated CSI-RSs is available, the UE may select the at least one CSI-RS and select a random access preamble corresponding to the at least one CSI-RS.

A UE may perform one or more Msg1 1220 transmissions by transmitting the selected random access preamble. For example, if a UE selects an SS block and is configured with an association between one or more PRACH occasions and one or more SS blocks, the UE may determine an PRACH occasion from one or more PRACH occasions corresponding to a selected SS block. For example, if a UE selects a CSI-RS and is configured with an association between one or more PRACH occasions and one or more CSI-RSs, the UE may determine a PRACH occasion from one or more PRACH occasions corresponding to a selected CSI-RS. A UE may transmit, to a base station, a selected random access preamble via a selected PRACH occasions. A UE may determine a transmit power for a transmission of a selected random access preamble at least based on an initial preamble power and a power-ramping factor. A UE may determine a RA-RNTI associated with a selected PRACH occasions in which a selected random access preamble is transmitted. For example, a UE may not determine a RA-RNTI for a beam failure recovery request. A UE may determine an RA-RNTI at least based on an index of a first OFDM symbol and an index of a first slot of a selected PRACH occasions, and/or an uplink carrier index for a transmission of Msg1 1220.

In an example, a UE may receive, from a base station, a random access response, Msg 2 1230. A UE may start a time window (e.g., ra-ResponseWindow) to monitor a random access response. For beam failure recovery request, a base station may configure a UE with a different time window (e.g., bfr-ResponseWindow) to monitor response on beam failure recovery request. For example, a UE may start a time window (e.g., ra-ResponseWindow or bfr-ResponseWindow) at a start of a first PDCCH occasion after a fixed duration of one or more symbols from an end of a preamble transmission. If a UE transmits multiple preambles, the UE may start a time window at a start of a first PDCCH occasion after a fixed duration of one or more symbols from an end of a first preamble transmission. A UE may monitor a PDCCH of a cell for at least one random access response identified by a RA-RNTI or for at least one response to beam failure recovery request identified by a C-RNTI while a timer for a time window is running.

In an example, a UE may consider a reception of random access response successful if at least one random access response comprises a random access preamble identifier corresponding to a random access preamble transmitted by the UE. A UE may consider the contention free random access procedure successfully completed if a reception of random access response is successful. If a contention free random access procedure is triggered for a beam failure recovery request, a UE may consider a contention free random access procedure successfully complete if a PDCCH transmission is addressed to a C-RNTI. In an example, if at least one random access response comprises a random access preamble identifier, a UE may consider the random access procedure successfully completed and may indicate a reception of an acknowledgement for a system information request to upper layers. If a UE has signaled multiple preamble transmissions, the UE may stop transmitting remaining preambles (if any) in response to a successful reception of a corresponding random access response.

In an example, a UE may perform one or more Msg 3 1240 transmissions in response to a successful reception of random access response (e.g., for a contention based random access procedure). A UE may adjust an uplink transmission timing based on a timing advanced command indicated by a random access response and may transmit one or more transport blocks based on an uplink grant indicated by a random access response. Subcarrier spacing for PUSCH transmission for Msg3 1240 may be provided by at least one higher layer (e.g., RRC) parameter. A UE may transmit a random access preamble via PRACH and Msg3 1240 via PUSCH on a same cell. A base station may indicate an UL BWP for a PUSCH transmission of Msg3 1240 via system information block. A UE may employ HARQ for a retransmission of Msg 31240.

In an example, multiple UEs may perform Msg 1 1220 by transmitting a same preamble to a base station and receive, from the base station, a same random access response comprising an identity (e.g., TC-RNTI). Contention resolution 1250 may ensure that a UE does not incorrectly use an identity of another UE. For example, contention resolution 1250 may be based on C-RNTI on PDCCH or a UE contention resolution identity on DL-SCH. For example, if a base station assigns a C-RNTI to a UE, the UE may perform contention resolution 1250 based on a reception of a PDCCH transmission that is addressed to the C-RNTI. In response to detection of a C-RNTI on a PDCCH, a UE may consider contention resolution 1250 successful and may consider a random access procedure successfully completed. If a UE has no valid C-RNTI, a contention resolution may be addressed by employing a TC-RNTI. For example, if a MAC PDU is successfully decoded and a MAC PDU comprises a UE contention resolution identity MAC CE that matches the CCCH SDU transmitted in Msg3 1250, a UE may consider the contention resolution 1250 successful and may consider the random access procedure successfully completed.

FIG. 13 is an example structure for MAC entities as per an aspect of an embodiment. In an example, a wireless device may be configured to operate in a multi-connectivity mode. A wireless device in RRC_CONNECTED with multiple RX/TX may be configured to utilize radio resources provided by multiple schedulers located in a plurality of base stations. The plurality of base stations may be connected via a non-ideal or ideal backhaul over the Xn interface. In an example, a base station in a plurality of base stations may act as a master base station or as a secondary base station. A wireless device may be connected to one master base station and one or more secondary base stations. A wireless device may be configured with multiple MAC entities, e.g., one MAC entity for master base station, and one or more other MAC entities for secondary base station(s). In an example, a configured set of serving cells for a wireless device may comprise two subsets: an MCG comprising serving cells of a master base station, and one or more SCGs comprising serving cells of a secondary base station(s). FIG. 13 illustrates an example structure for MAC entities when MCG and SCG are configured for a wireless device.

In an example, at least one cell in a SCG may have a configured UL CC, wherein a cell of at least one cell may be called PSCell or PCell of SCG, or sometimes may be simply called PCell. A PSCell may be configured with PUCCH resources. In an example, when a SCG is configured, there may be at least one SCG bearer or one split bearer. In an example, upon detection of a physical layer problem or a random access problem on a PSCell, or upon reaching a number of RLC retransmissions associated with the SCG, or upon detection of an access problem on a PSCell during a SCG addition or a SCG change: an RRC connection re-establishment procedure may not be triggered, UL transmissions towards cells of an SCG may be stopped, a master base station may be informed by a UE of a SCG failure type and DL data transfer over a master base station may be maintained.

In an example, a MAC sublayer may provide services such as data transfer and radio resource allocation to upper layers (e.g., 1310 or 1320). A MAC sublayer may comprise a plurality of MAC entities (e.g., 1350 and 1360). A MAC sublayer may provide data transfer services on logical channels. To accommodate different kinds of data transfer services, multiple types of logical channels may be defined. A logical channel may support transfer of a particular type of information. A logical channel type may be defined by what type of information (e.g., control or data) is transferred. For example, BCCH, PCCH, CCCH and DCCH may be control channels and DTCH may be a traffic channel. In an example, a first MAC entity (e.g., 1310) may provide services on PCCH, BCCH, CCCH, DCCH, DTCH and MAC control elements. In an example, a second MAC entity (e.g., 1320) may provide services on BCCH, DCCH, DTCH and MAC control elements.

A MAC sublayer may expect from a physical layer (e.g., 1330 or 1340) services such as data transfer services, signaling of HARQ feedback, signaling of scheduling request or measurements (e.g., CQI). In an example, in dual connectivity, two MAC entities may be configured for a wireless device: one for MCG and one for SCG. A MAC entity of wireless device may handle a plurality of transport channels. In an example, a first MAC entity may handle first transport channels comprising a PCCH of MCG, a first BCH of MCG, one or more first DL-SCHs of MCG, one or more first UL-SCHs of MCG and one or more first RACHs of MCG. In an example, a second MAC entity may handle second transport channels comprising a second BCH of SCG, one or more second DL-SCHs of SCG, one or more second UL-SCHs of SCG and one or more second RACHs of SCG.

In an example, if a MAC entity is configured with one or more SCells, there may be multiple DL-SCHs and there may be multiple UL-SCHs as well as multiple RACHs per MAC entity. In an example, there may be one DL-SCH and UL-SCH on a SpCell. In an example, there may be one DL-SCH, zero or one UL-SCH and zero or one RACH for an SCell. A DL-SCH may support receptions using different numerologies and/or TTI duration within a MAC entity. A UL-SCH may also support transmissions using different numerologies and/or TTI duration within the MAC entity.

In an example, a MAC sublayer may support different functions and may control these functions with a control (e.g., 1355 or 1365) element. Functions performed by a MAC entity may comprise mapping between logical channels and transport channels (e.g., in uplink or downlink), multiplexing (e.g., 1352 or 1362) of MAC SDUs from one or different logical channels onto transport blocks (TB) to be delivered to the physical layer on transport channels (e.g., in uplink), demultiplexing (e.g., 1352 or 1362) of MAC SDUs to one or different logical channels from transport blocks (TB) delivered from the physical layer on transport channels (e.g., in downlink), scheduling information reporting (e.g., in uplink), error correction through HARQ in uplink or downlink (e.g., 1353 or 1363), and logical channel prioritization in uplink (e.g., 1351 or 1361). A MAC entity may handle a random access process (e.g., 1354 or 1364).

FIG. 14 is an example diagram of a RAN architecture comprising one or more base stations. In an example, a protocol stack (e.g., RRC, SDAP, PDCP, RLC, MAC, and PHY) may be supported at a node. A base station (e.g., 120A or 120B) may comprise a base station central unit (CU) (e.g., gNB-CU 1420A or 1420B) and at least one base station distributed unit (DU) (e.g., gNB-DU 1430A, 1430B, 1430C, or 1430D) if a functional split is configured. Upper protocol layers of a base station may be located in a base station CU, and lower layers of the base station may be located in the base station DUs. An F1 interface (e.g., CU-DU interface) connecting a base station CU and base station DUs may be an ideal or non-ideal backhaul. F1-C may provide a control plane connection over an F1 interface, and F1-U may provide a user plane connection over the F1 interface. In an example, an Xn interface may be configured between base station CUs.

In an example, a base station CU may comprise an RRC function, an SDAP layer, and a PDCP layer, and base station DUs may comprise an RLC layer, a MAC layer, and a PHY layer. In an example, various functional split options between a base station CU and base station DUs may be possible by locating different combinations of upper protocol layers (RAN functions) in a base station CU and different combinations of lower protocol layers (RAN functions) in base station DUs. A functional split may support flexibility to move protocol layers between a base station CU and base station DUs depending on service requirements and/or network environments.

In an example, functional split options may be configured per base station, per base station CU, per base station DU, per UE, per bearer, per slice, or with other granularities. In per base station CU split, a base station CU may have a fixed split option, and base station DUs may be configured to match a split option of a base station CU. In per base station DU split, a base station DU may be configured with a different split option, and a base station CU may provide different split options for different base station DUs. In per UE split, a base station (base station CU and at least one base station DUs) may provide different split options for different wireless devices. In per bearer split, different split options may be utilized for different bearers. In per slice splice, different split options may be applied for different slices.

FIG. 15 is an example diagram showing RRC state transitions of a wireless device. In an example, a wireless device may be in at least one RRC state among an RRC connected state (e.g., RRC Connected 1530, RRC_Connected), an RRC idle state (e.g., RRC Idle 1510, RRC_Idle), and/or an RRC inactive state (e.g., RRC Inactive 1520, RRC_Inactive). In an example, in an RRC connected state, a wireless device may have at least one RRC connection with at least one base station (e.g., gNB and/or eNB), which may have a UE context of the wireless device. A UE context (e.g., a wireless device context) may comprise at least one of an access stratum context, one or more radio link configuration parameters, bearer (e.g., data radio bearer (DRB), signaling radio bearer (SRB), logical channel, QoS flow, PDU session, and/or the like) configuration information, security information, PHY/MAC/RLC/PDCP/SDAP layer configuration information, and/or the like configuration information for a wireless device. In an example, in an RRC idle state, a wireless device may not have an RRC connection with a base station, and a UE context of a wireless device may not be stored in a base station. In an example, in an RRC inactive state, a wireless device may not have an RRC connection with a base station. A UE context of a wireless device may be stored in a base station, which may be called as an anchor base station (e.g., last serving base station).

In an example, a wireless device may transition a UE RRC state between an RRC idle state and an RRC connected state in both ways (e.g., connection release 1540 or connection establishment 1550; or connection reestablishment) and/or between an RRC inactive state and an RRC connected state in both ways (e.g., connection inactivation 1570 or connection resume 1580). In an example, a wireless device may transition its RRC state from an RRC inactive state to an RRC idle state (e.g., connection release 1560).

In an example, an anchor base station may be a base station that may keep a UE context (a wireless device context) of a wireless device at least during a time period that a wireless device stays in a RAN notification area (RNA) of an anchor base station, and/or that a wireless device stays in an RRC inactive state. In an example, an anchor base station may be a base station that a wireless device in an RRC inactive state was lastly connected to in a latest RRC connected state or that a wireless device lastly performed an RNA update procedure in. In an example, an RNA may comprise one or more cells operated by one or more base stations. In an example, a base station may belong to one or more RNAs. In an example, a cell may belong to one or more RNAs.

In an example, a wireless device may transition a UE RRC state from an RRC connected state to an RRC inactive state in a base station. A wireless device may receive RNA information from the base station. RNA information may comprise at least one of an RNA identifier, one or more cell identifiers of one or more cells of an RNA, a base station identifier, an IP address of the base station, an AS context identifier of the wireless device, a resume identifier, and/or the like.

In an example, an anchor base station may broadcast a message (e.g., RAN paging message) to base stations of an RNA to reach to a wireless device in an RRC inactive state, and/or the base stations receiving the message from the anchor base station may broadcast and/or multicast another message (e.g., paging message) to wireless devices in their coverage area, cell coverage area, and/or beam coverage area associated with the RNA through an air interface.

In an example, when a wireless device in an RRC inactive state moves into a new RNA, the wireless device may perform an RNA update (RNAU) procedure, which may comprise a random access procedure by the wireless device and/or a UE context retrieve procedure. A UE context retrieve may comprise: receiving, by a base station from a wireless device, a random access preamble; and fetching, by a base station, a UE context of the wireless device from an old anchor base station. Fetching may comprise: sending a retrieve UE context request message comprising a resume identifier to the old anchor base station and receiving a retrieve UE context response message comprising the UE context of the wireless device from the old anchor base station.

In an example embodiment, a wireless device in an RRC inactive state may select a cell to camp on based on at least a on measurement results for one or more cells, a cell where a wireless device may monitor an RNA paging message and/or a core network paging message from a base station. In an example, a wireless device in an RRC inactive state may select a cell to perform a random access procedure to resume an RRC connection and/or to transmit one or more packets to a base station (e.g., to a network). In an example, if a cell selected belongs to a different RNA from an RNA for a wireless device in an RRC inactive state, the wireless device may initiate a random access procedure to perform an RNA update procedure. In an example, if a wireless device in an RRC inactive state has one or more packets, in a buffer, to transmit to a network, the wireless device may initiate a random access procedure to transmit one or more packets to a base station of a cell that the wireless device selects. A random access procedure may be performed with two messages (e.g., 2 stage random access) and/or four messages (e.g., 4 stage random access) between the wireless device and the base station.

In an example embodiment, a base station receiving one or more uplink packets from a wireless device in an RRC inactive state may fetch a UE context of a wireless device by transmitting a retrieve UE context request message for the wireless device to an anchor base station of the wireless device based on at least one of an AS context identifier, an RNA identifier, a base station identifier, a resume identifier, and/or a cell identifier received from the wireless device. In response to fetching a UE context, a base station may transmit a path switch request for a wireless device to a core network entity (e.g., AMF, MME, and/or the like). A core network entity may update a downlink tunnel endpoint identifier for one or more bearers established for the wireless device between a user plane core network entity (e.g., UPF, S-GW, and/or the like) and a RAN node (e.g., the base station), e.g., changing a downlink tunnel endpoint identifier from an address of the anchor base station to an address of the base station.

In an example, multiple DCI formats may be used for different purposes. In an example, DCI format 0_0 may be used for scheduling of PUSCH in one cell. In an example, DCI format 0_1 may be used for scheduling of PUSCH in one cell.

In an example, DCI format 1_0 may be used for scheduling of PDSCH in one cell. In an example, DCI format 1_0 scrambled by C-RNTI or CS-RNTI or MCS-C-RNTI. may comprise identifier for DCI formats, frequency domain resource assignment, random access preamble index, UL/SUL indicator, SS/PBCH index, PRACH mask index and/or reserved bits. In an example, DCI format 1_0 scrambled by P-RNTI may comprise short messages indicator, short messages, frequency domain resource assignment, time domain resource assignment, VRB-to-PRB mapping, modulation and coding scheme, TB scaling, and/or reserved bits.

In an example, DCI format 1_1 may be used for scheduling of PDSCH in one cell. In an example, DCI format 1_1 scrambled by C-RNTI or CS-RNTI or MCS-C-RNTI may comprise identifier for DCI formats, carrier indicator, bandwidth part indicator, frequency domain resource assignment, time domain resource assignment, VRB-to-PRB mapping, PRB bundling size indicator, rate matching indicator, Zero Power (ZP) CSI-RS trigger, MCS/New Data Indicator (NDI)/Redundancy Version (RV) for each transport block, HARQ process number, downlink assignment index, Transmit Power Control (TPC) command for scheduled PUCCH, PUCCH resource indicator, PDSCH-to-HARQ_feedback timing indicator, Antenna ports of DMRS, transmission configuration indication, SRS request, Code Block Group (CBG) transmission information, CBG flushing out information, and/or DMRS sequence initialization.

In an example, DCI formats 1_1 may be monitored in multiple search spaces associated with multiple CORESETs in a BWP. In this case, zeros may be appended until the payload size of the DCI formats 1_1 monitored in the multiple search spaces equal to the maximum payload size of the DCI format 1_1 monitored in the multiple search spaces.

In an example, the antenna ports of DMRS in DCI format 1_1 may indicate information comprising number of DMRS Code Division Multiplexing (CDM) groups without data, DMRS ports and/or Number of front-load symbols. For example, the number of CDM groups without data values 1, 2, and 3 may refer to CDM groups {0}, {0,1}, and {0,1,2}, respectively. The antenna ports of DMRS may be determined according to the predefined ordering of DMRS port(s).

In an example, transmission configuration indication may be 0 if higher layer parameter tci-PresentInDCI is not enabled. In an example, tci-PresentInDCI may indicate one of RRC configured TCI states for the scheduled PDSCH.

In an example, the time domain resource assignment value m in DCI format 1_0 or DCI format 1_1 may provide a row index m+1 to an allocation table. The determination of the used resource allocation table according to parameters (e.g., RNTI, PDCCH search space, Synchronization Signal (SS)/Physical Broadcasting CHannel (PBCH) block and CORESET multiplexing pattern, pdsch-ConfigCommon includes pdsch-TimeDomainAllocationList, pdsch-Config includes pdsch-TimeDomainAllocationList, PDSCH time domain resource allocation to apply and/or cyclic prefix type) may be defined in predefined tables. In an example, the indexed row may define the slot offset KO, the start and length indicator Value (SLIV), the start symbol S, the allocation length L and/or PDSCH mapping type to be assumed in the PDSCH reception.

In an example, the slot allocated for the PDSCH may be determined as

⌊

n
·

2

μ
PDSCH

2

μ
PDCCH

⌋

+

K
0

,

where n is the slot with the scheduling DCI, and KO is based on the numerology of PDSCH, and μ_PDSCHand μ_PDCCHare the subcarrier spacing configurations for PDSCH and PDCCH, respectively.

In an example, the starting symbol S relative to the start of the slot, and the number of consecutive symbols S counting from the symbol S allocated for the PDSCH may be determined from the start and length indicator SLIV. For example, if (L−1)≤7 then SLIV=14·(L−1)+S. Otherwise SLIV=14·(14−L+1)+(14−1−S) where 0<L≤14−S.

In an example, the wireless device may consider the predefined combinations of S and L as valid allocations considering PDSCH mapping type, cyclic prefix type and/or dmrs-TypeA-Position.

In an example, DCI format 2_0 may be used for notifying a group of wireless devices of the slot format. In an example, DCI format 2_1 may be used for notifying a group of wireless devices of the PRBs and OFDM symbols where a wireless device may assume no transmission is intended for the wireless device. In an example, DCI format 2_2 may be used for transmitting TPC commands for PUCCH and PUSCH. In an example, DCI format 2_3 may be used for transmitting a group of TPC commands for SRS transmissions by one or more wireless devices.

In an example, a wireless device may assume the PDSCH DMRS being mapped to physical resources according to configuration type 1 or configuration type 2 as given by the higher-layer parameter dmrs-Type.

In an example, the wireless device may assume the sequence r(m) may be scaled by a factor μ_PDSCH^DMRSto conform with the transmission power and mapped to resource elements (k, l)_p,μ according to

a

k
,
l

(

p
,
μ

)

=

β
PDSCH
DMRS

⁢

w
f

(

k
′

)

⁢

w
t

(

l
′

)

⁢

r
⁡
(

2
⁢
n

+

k
′

)

⁢

k
=

{

4
⁢
n

+

2
⁢

k
′

+
Δ

Configuration
⁢

type
⁢

1

6
⁢
n

+

k
′

+
Δ

Configuration
⁢

type
⁢

2

⁢

k
′

=
0

,

1
⁢

l

=

l
_

+

l
′

⁢

n

=
0

,
1
,
…

- where w_f(k′), w_t(l′), and a may be given by predefined tables.

In an example, the resource elements may be within the common resource blocks allocated for PDSCH transmission.

In an example, the reference point k may be subcarrier 0 of the lowest-numbered resource block in CORESET 0 (e.g., if the corresponding PDCCH may be associated with CORESET 0 and Type0-PDCCH common search space and may be addressed to SI-RNTI). In another example, subcarrier 0 in common resource block 0 may be subcarrier 0 (e.g., other cases).

In an example, the reference point for l and position I0 of the first DM-RS symbol may depend on the indicated mapping type in DCI. For example, for PDSCH mapping type A, l may be defined relative to the start of the slot. For example, 10 may be 3 (e.g., the higher-layer parameter dmrs-TypeA-Position is equal to ‘pos3). For example, I0 may be 2 (e.g., otherwise). For example, for PDSCH mapping type B, l may be defined relative to the start of the scheduled PDSCH resources. For example, I0 may be 0.

In an example, the one or more positions of DMRS symbols may be given by l and duration Id. For example, for PDSCH mapping type A, Id may be the duration between the first OFDM symbol of the slot and the last OFDM symbol of the scheduled PDSCH resources in the slot. For example, for PDSCH mapping type B, Id may be the number of OFDM symbols of the scheduled PDSCH resources.

In an example, dmrs-AdditionalPosition equals to ‘pos3’ may be only supported when dmrs-TypeA-Position is equal to ‘pos2’. In an example, for PDSCH mapping type A, Id=3 and/or Id=4 symbols may be only applicable when dmrs-TypeA-Position is equal to ‘pos2’.

In an example, for PDSCH mapping type A single-symbol DM-RS, I1=11 except if the predefined conditions (e.g., Ite-CRS-ToMatchAround is configured, any PDSCH DMRS symbol coincides with any symbol containing LTE cell-specific reference signals as indicated by the higher-layer parameter Ite-CRS-ToMatchAround, the higher-layer parameters dmrs-AdditionalPosition equal to ‘pos1’ and I0=3 and/or the indicated capability signaling of supporting I1=12.

In an example, in absence of CSI-RS configuration, and unless otherwise configured, the wireless device may assume PDSCH DMRS and SS/PBCH block may be quasi co-located (e.g., with respect to Doppler shift, Doppler spread, average delay, delay spread, and when applicable, spatial Rx parameters).

In an example, the wireless device may assume that PDSCH DMRS within the same CDM group may be quasi co-located (e.g., with respect to Doppler shift, Doppler spread, average delay, delay spread, and spatial Rx parameters). The wireless device may assume that DMRS ports associated with a PDSCH are quasi co-located (e.g., with QCL Type A, Type D (when applicable) and average gain).

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). 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 transmission configuration indication (TCI) 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 DMRS 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 DMRS 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 DMRS 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 DMRS 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, 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 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 for the serving 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 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 is 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 or quasi co-located (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, and 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 monitors 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).

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

In an example, an information element TCI-State may associate one or two DL reference signals with a corresponding quasi co-location (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.

In an example, 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 gNB may communicate with a wireless device via a wireless network employing one or more new radio technologies. The one or more radio technologies may comprise at least one of: multiple technologies related to physical layer; multiple technologies related to medium access control layer; and/or multiple technologies related to radio resource control layer. Example embodiments of enhancing the one or more radio technologies may improve performance of a wireless network. Example embodiments may increase the system throughput, or data rate of transmission. Example embodiments may reduce battery consumption of a wireless device. Example embodiments may improve latency of data transmission between a gNB and a wireless device. Example embodiments may improve network coverage of a wireless network. Example embodiments may improve transmission efficiency of a wireless network.

In an example, a base station may configure a wireless device with a list of one or more TCI-State configurations by a higher layer parameter PDSCH-Config for a serving cell. A number of the one or more TCI states may depend on a capability of the wireless device. The wireless device may use the one or more TCI-States to decode a PDSCH according to a detected PDCCH with a DCI. The DCI may be intended for the wireless device and a serving cell of the wireless device.

In an example, a TCI state of the one or more TCI-State configurations may contain one or more parameters. The wireless device may use the one or more parameters to configure a quasi co-location relationship between one or two downlink reference signals (e.g., first DL RS and second DL RS) and DMRS ports of a PDSCH. The quasi co-location relationship may be configured by a higher layer parameter qcl-Type1 for the first DL RS. The quasi co-location relationship may be configured by a higher layer parameter qcl-Type2 for the second DL RS (if configured).

In an example, when the wireless device configures a quasi co-location relationship between the two downlink reference signals (e.g., first DL RS and second DL RS), a first QCL type of the first DL RS and a second QCL type of the second DL RS may not be the same. In an example, the first DL RS and the second DL RS may be the same. In an example, the first DL RS and the second DL RS may be different.

In an example, a quasi co-location type (e.g., the first QCL type, the second QCL type) of a DL RS (e.g., the first DL RS, the second DL RS) may be provided to the wireless device by a higher layer parameter qcl-Type in QCL-Info. The higher layer parameter QCL-Type may take at least one of: QCL-TypeA: {Doppler shift, Doppler spread, average delay, delay spread}; QCL-TypeB: {Doppler shift, Doppler spread}; QCL-TypeC: {average delay, Doppler shift} and QCL-TypeD: {Spatial Rx parameter}.

In an example, a wireless device may receive an activation command. The activation command may be used to map one or more TCI states (e.g., up to 8) to one or more codepoints of a DCI field “Transmission Configuration Indication (TCI)”. 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+3N_slot^subframe,μ+1.

In an example, after the wireless device receives an initial higher layer configuration of one or more TCI states and before the reception of the activation command, the wireless device may assume that one or more DMRS ports of a PDSCH of a serving cell are quasi co-located with an SSB/PBCH block. In an example, the wireless device may determine the SSB/PBCH block in an initial access procedure with respect ‘QCL-TypeA’. In an example, the wireless device may determine the SSB/PBCH block in the initial access procedure with respect to ‘QCL-TypeD’ (when applicable).

In an example, a wireless device may be configured, by a base station, with a higher layer parameter TCI-PresentInDCI. When the higher layer parameter TCI-PresentInDCI is set as ‘enabled’ for a control resource set (CORESET) scheduling a PDSCH, the wireless device may assume that a TCI field is present in a DCI format (e.g., DCI format 1_1) of a PDCCH transmitted on the CORESET.

In an example, a base station may not configure a CORESET with a higher layer parameter TCI-PresentInDCI. In an example, the CORESET may schedule a PDSCH. In an example, a time offset between a reception of a DCI (e.g., DCI format 1_1, DCI format 1_0) received in the CORESET and the (corresponding) PDSCH may be equal to or greater than a threshold (e.g., Threshold-Sched-Offset). In an example, the threshold may be based on a reported UE capability. In an example, the wireless device may apply a second TCI state for the CORESET used for a PDCCH transmission of the DCI. In an example, the wireless device may apply a second QCL assumption for the CORESET used for a PDCCH transmission of the DCI. In an example, in response to the base station not configuring the CORESET with the higher layer parameter TCI-PresentInDCI and the time offset between the reception of the DCI and the PDSCH being equal or greater than the threshold, the wireless device may perform a default PDSCH RS selection. In an example, in the default PDSCH RS selection, the wireless device may assume, in order to determine antenna port quasi co-location of the PDSCH, that a first TCI state or a first QCL assumption for the PDSCH is identical to the second TCI state or the second QCL assumption applied for the CORESET.

In an example, a base station may configure a CORESET with a higher layer parameter TCI-PresentInDCI. In an example, the higher layer parameter TCI-PresentInDCI may be set as “enabled”. In an example, the CORESET may schedule a PDSCH with a DCI (e.g., DCI format 1_0). In an example, the DCI may not comprise a TCI field. In an example, a time offset between a reception of the DCI received in the CORESET and the (corresponding) PDSCH may be equal to or greater than a threshold (e.g., Threshold-Sched-Offset). In an example, the threshold may be based on a reported UE capability. In an example, the wireless device may apply a second TCI state for the CORESET used for a PDCCH transmission of the DCI. In an example, the wireless device may apply a second QCL assumption for the CORESET used for a PDCCH transmission of the DCI. In an example, in response to the base station scheduling the PDSCH with the DCI not comprising the TCI field and the time offset between the reception of the DCI and the PDSCH being equal or greater than the threshold, the wireless device may perform a default PDSCH RS selection. In an example, in the default PDSCH RS selection, the wireless device may assume, in order to determine antenna port quasi co-location of the PDSCH, that a first TCI state or a first QCL assumption for the PDSCH is identical to the second TCI state or the second QCL assumption applied for the CORESET.

In an example, a base station may configure a CORESET with a higher layer parameter TCI-PresentInDCI. In an example, the higher layer parameter TCI-PresentInDCI may be set as “enabled”. The wireless device may receive a DCI in the CORESET of a scheduling component carrier. The DCI may comprise a TCI field. In response to the higher layer parameter TCI-PresentinDCI being set as ‘enabled’, the TCI field in the DCI in the scheduling component carrier may point to one or more activated TCI states (e.g., after receiving the activation command) in a scheduled component carrier or in a DL BWP.

In an example, a base station may configure a CORESET with a higher layer parameter TCI-PresentInDCI. In an example, the higher layer parameter TCI-PresentInDCI may be set as “enabled”. The wireless device may receive a DCI (e.g., DCI format 1_1) in the CORESET. In an example, the DCI may schedule a PDSCH of a wireless device. In an example, a TCI field may be present in the DCI. In an example, a time offset between a reception of the DCI and the (corresponding scheduled) PDSCH may be equal to or greater than a threshold (e.g., Threshold-Sched-Offset). In an example, the threshold may be based on a reported UE capability. In an example, in response to the TCI field being present in the DCI scheduling the PDSCH and the higher layer parameter TCI-PresentinDCI being set as ‘enabled’ for the CORESET, the wireless device may, in order to determine antenna port quasi co-location for the PDSCH, use a TCI State according to a value of the TCI field in a detected PDCCH with the DCI. In an example, the using the TCI State according to the value of the TCI field may comprise that the wireless device may assume that one or more DMRS ports of the PDSCH of a serving cell are quasi co-located with one or more RS(s) in the TCI State with respect to one or more QCL type parameter(s) given by the TCI state when the time offset between the reception of the DCI and the PDSCH is equal or greater than the threshold. In an example, the value of the TCI field may indicate the TCI state.

In an example, a base station may configure a wireless device with a single slot PDSCH. In an example, the single slot PDSCH may be scheduled in a slot. In an example, the base station may activate one or more TCI states in the slot. In response to being configured with the single slot PDSCH, a TCI state (e.g., indicated by a TCI field in a DCI scheduling the single slot PDSCH) may be based on the one or more activated TCI states in the slot with the scheduled single slot PDSCH. In an example, the TCI state may be one of the one or more activated TCI states in the slot. In an example, the TCI field in the DCI may indicate a TCI state of the one or more activated TCI states in the slot.

In an example, a wireless device may be configured with a CORESET. In an example, the CORESET may be associated with a search space set for cross-carrier scheduling. In an example, in response to the CORESET being associated with the search space set for cross-carrier scheduling, the wireless device may expect the higher layer parameter TCI-PresentInDCI set as ‘enabled’ for the CORESET. In an example, a base station may configure a serving cell with one or more TCI states. In an example, the wireless device may detect, in the search space set, a PDCCH, with a DCI, scheduling a PDSCH. In an example, a TCI field in the DCI may indicate at least one of the one or more TCI states. In an example, the at least one of the one more TCI states (scheduled by the search space set) may comprise/contain a QCL type (e.g., QCL-TypeD). In an example, in response to the at least one of the one or more TCI states scheduled by the search space set containing the QCL type, the wireless device may expect a time offset between a reception of the PDCCH detected in the search space set and the (corresponding) PDSCH is larger than or equal to the threshold (e.g., Threshold-Sched-Offset).

In an example, a base station may configure a CORESET with a higher layer parameter TCI-PresentInDCI. In an example, the higher layer parameter TCI-PresentInDCI may be set as “enabled”. In an example, when the higher layer parameter TCI-PresentInDCI is set to ‘enabled’ for the CORESET, an offset between a reception of a DCI in the CORESET and a PDSCH scheduled by the DCI may be less than the threshold (e.g., Threshold-Sched-Offset).

In an example, a base station may not configure a CORESET with a higher layer parameter TCI-PresentInDCI. In an example, the wireless device may be in an RRC connected mode. In an example, the wireless device may be in an RRC idle mode. In an example, the wireless device may be in an RRC inactive mode. In an example, when the higher layer parameter TCI-PresentInDCI is not configured for the CORESET, an offset between a reception of a DCI in the CORESET and a PDSCH scheduled by the DCI may be lower than the threshold (e.g., Threshold-Sched-Offset).

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 DMRS 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’) of one or more DMRS ports of the PDSCH may be different from a second QCL type (e.g., ‘QCL-TypeD’) of one or more second DMRS 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 DMRS 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 DMRS ports of the PDSCH with the second QCL type of the one or more second DMRS 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, 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.

In an example, a wireless device may use CSI-RS for at least one of: time/frequency tracking, CSI computation, L1-RSRP computation and mobility.

In an example, a base station may configure a wireless device to monitor a CORESET on one or more symbols. In an example, a CSI-RS resource may be associated with a NZP-CSI-RS-ResourceSet. A higher layer parameter repetition of the NZP-CSI-RS-ResourceSet may be set to ‘on’. In an example, in response to the CSI-RS resource being associated with the NZP-CSI-RS-ResourceSet with the higher layer parameter repetition set to ‘on’, the wireless device may not expect to be configured with a CSI-RS of the CSI-RS resource over the one or more symbols.

In an example, a higher layer parameter repetition of the NZP-CSI-RS-ResourceSet may not be set to ‘on’. In an example, a base station may configure a CSI-RS resource and one or more search space sets associated with a CORESET in the same one or more symbols (e.g., OFDM symbols). In an example, in response to the higher layer parameter repetition of the NZP-CSI-RS-ResourceSet not being set to ‘on’, and the CSI-RS resource and the one or more search space sets associated with the CORESET being configured in the same one or more symbols, the wireless device may assume that a CSI-RS of the CSI-RS resource and one or more DMRS ports of a PDCCH are quasi co-located with ‘QCL-TypeD’. In an example, the base station may transmit the PDCCH in the one or more search space sets associated with the CORESET.

In an example, a higher layer parameter repetition of the NZP-CSI-RS-ResourceSet may not be set to ‘on’. In an example, a base station may configure a CSI-RS resource of a first cell and one or more search space sets associated with a CORESET of a second cell in the same one or more symbols (e.g., OFDM symbols). In an example, in response to the higher layer parameter repetition of the NZP-CSI-RS-ResourceSet not being set to ‘on’, and the CSI-RS resource and the one or more search space sets associated with the CORESET being configured in the same one or more symbols, the wireless device may assume that a CSI-RS of the CSI-RS resource and one or more DMRS ports of a PDCCH are quasi co-located with ‘QCL-TypeD’. In an example, the base station may transmit the PDCCH in the one or more search space sets associated with the CORESET. In an example, the first cell and the second cell may be in different intra-band component carriers.

In an example, a base station may configure a wireless device with a CSI-RS in a first set of PRBs. In an example, the base station may configure the wireless device with one or more search space sets associated with a CORESET in one or more symbols (e.g., OFDM symbols) and in a second set of PRBs. In an example, the wireless device may not expect the first set of PRBs sand the second set of PRBs overlapping in the one or more symbols.

In an example, a base station may configure a wireless device with a CSI-RS resource and an SS/PBCH block in the same one or more (OFDM) symbols. In an example, in response to the CSI-RS resource and the SS/PBCH block being configured in the same one or more (OFDM) symbols, the wireless device may assume that the CSI-RS resource and the SS/PBCH block are quasi co-located with a QCL type (e.g., ‘QCL-TypeD’).

In an example, the base station may configure the CSI-RS resource in a first set of PRBs for the wireless device. In an example, the base station may configure the SS/PBCH block in a second set of PRBs for the wireless device. In an example, the wireless device may not expect the first set of PRBs overlapping with the second set of PRBs.

In an example, the base station may configure the CSI-RS resource with a first subcarrier spacing for the wireless device. In an example, the base station may configure the SS/PBCH block with a second subcarrier spacing for the wireless device. In an example, the wireless device may expect the first subcarrier spacing and the second subcarrier spacing being the same.

In an example, a base station may configure a wireless device with a NZP-CSI-RS-ResourceSet. In an example, the NZP-CSI-RS-ResourceSet may be configured with a higher layer parameter repetition set to ‘on’. In an example, in response to the NZP-CSI-RS-ResourceSet being configured with the higher layer parameter repetition set to ‘on’, the wireless device may assume that the base station transmits one or more CSI-RS resources within the NZP-CSI-RS-ResourceSet with the same downlink spatial domain transmission filter. In an example, the base station may transmit each CSI-RS resource of the one or more CSI-RS resources in different symbols (e.g., OFDM symbols).

In an example, the NZP-CSI-RS-ResourceSet may be configured with a higher layer parameter repetition set to ‘off’. In an example, in response to the NZP-CSI-RS-ResourceSet being configured with the higher layer parameter repetition set to ‘off’, the wireless device may not assume that the base station transmits one or more CSI-RS resources within the NZP-CSI-RS-ResourceSet with the same downlink spatial domain transmission filter.

In an example, a base station may configure a wireless device with a higher layer parameter groupBasedBeamReporting. In an example, the base station may set the higher layer parameter groupBasedBeamReporting to “enabled”. In response to the higher layer parameter groupBasedBeamReporting set to “enabled”, the wireless device may report at least two different resource indicators (e.g., CRI, SSBRI) in a single reporting instance for a reporting setting of one or more report settings. In an example, the wireless device may receive at least two RSs (e.g., CSI-RS, SSB) indicated by the at least two different resource indicators simultaneously. In an example, the wireless device may receive the at least two RSs simultaneously with a single spatial domain receive filter. In an example, the wireless device may receive the at least two RSs simultaneously with a plurality of simultaneous spatial domain receive filters.

In an example, a base station may need (additional) one or more UE radio access capability information of a wireless device. In response to the needing the one or more UE radio access capability information, the base station may initiate a procedure to request the one or more UE radio access capability information (e.g., by an information element UECapabilityEnquiry) from the wireless device. In an example, the wireless device may use an information element (e.g., UECapabilityInformation message) to transfer one or more UE radio access capability information requested by the base station. In an example, the wireless device may provide a threshold (e.g., timeDurationForQCL, Threshold-Sched-Offset) in FeatureSetDownlink indicating a set of features that the wireless device supports.

In an example, the threshold may comprise a minimum number of OFDM symbols required by the wireless device to perform a PDCCH reception with a DCI and to apply a spatial QCL information (e.g., TCI-State) received in (or indicated by) the DCI for a processing of a PDSCH scheduled by the DCI.

In an example, the wireless device may require the minimum number of OFDM symbols between the PDCCH reception and the processing of the PDSCH to apply the spatial QCL information, indicated by the DCI, to the PDSCH.

In an example, a base station may configure a wireless device with one or more first reference signals (e.g., SS/PBCH block, CSI-RS, etc.) for beam failure detection. In an example, the wireless device may declare/detect a beam failure based on the one or more first reference signals (RSs) when a number of beam failure instance indications from a physical layer of the wireless device to a higher layer (e.g., MAC layer) of the wireless device reaches a configured threshold (e.g., beamFailureInstanceMaxCount) before an expiry of a configured timer (e.g., beamFailureDetectionTimer).

In an example, an SSB (e.g., cell-defining SSB) may be associated with an initial downlink BWP of a cell. The wireless device may detect a beam failure based on the SSB in response to the SSB being associated with the initial downlink BWP. In an example, the base station may configure the SSB, for detecting the beam failure, for the initial downlink BWP. In an example, a downlink BWP of the cell may comprise the SSB. The base station may configure the SSB, for detecting the beam failure, for the downlink BWP based on the downlink BWP comprising the SSB. The one or more first RSs may comprise the SSB.

In an example, a downlink BWP of the cell may not comprise the SSB. In response to the downlink BWP not comprising the SSB, the wireless device may detect a beam failure for the downlink BWP based on one or more CSI-RSs. The one or more first RSs may comprise the one or more CSI-RSs.

In an example, if a wireless device is configured with a SCG, the wireless device may apply the procedures described in this subclause for both MCG and SCG. When the procedures are applied for MCG, the terms ‘secondary cell’, ‘secondary cells’, ‘serving cell’, ‘serving cells’ may refer to secondary cell, secondary cells, serving cell, serving cells belonging to the MCG respectively. When the procedures are applied for SCG, the terms ‘secondary cell’, ‘secondary cells’, ‘serving cell’, ‘serving cells’ may refer to secondary cell, secondary cells (not including PSCell), serving cell, serving cells belonging to the SCG respectively. The term ‘primary cell’ may refer to the PSCell of the SCG.

In an example, if the wireless device is configured with a PUCCH-SCell, the wireless device may apply the procedures described for both primary PUCCH group and secondary PUCCH group. When the procedures are applied for the primary PUCCH group, the terms ‘secondary cell’, ‘secondary cells’, ‘serving cell’, ‘serving cells’ may refer to secondary cell, secondary cells, serving cell, serving cells belonging to the primary PUCCH group respectively. When the procedures are applied for secondary PUCCH group, the terms ‘secondary cell’, ‘secondary cells’, ‘serving cell’, ‘serving cells’ may refer to secondary cell, secondary cells (not including the PUCCH-SCell), serving cell, serving cells belonging to the secondary PUCCH group respectively. The term ‘primary cell’ may refer to the PUCCH-SCell of the secondary PUCCH group.

In an example, if a wireless device would transmit on a serving cell a PUSCH without UL-SCH that overlaps with a PUCCH transmission on the serving cell that includes positive SR information, the wireless device may not transmit the PUSCH.

In an example, if a wireless device would transmit CSI reports on overlapping physical channels, the wireless device may apply the priority rules for the multiplexing of CSI reports.

In an example, if a wireless device has overlapping resources for PUCCH transmissions in a slot and at least one of the PUCCH transmissions is with repetitions over multiple slots, the wireless device first may follow the procedures for resolving the overlapping among the resources for the PUCCH transmissions.

In an example, if a wireless device would multiplex UCI in a PUCCH transmission that overlaps with a PUSCH transmission, and the PUSCH and PUCCH transmissions fulfill the conditions for UCI multiplexing, the wireless device may multiplex only HARQ-ACK information, if any, from the UCI in the PUSCH transmission and does not transmit the PUCCH if the wireless device multiplexes aperiodic or semi-persistent CSI reports in the PUSCH and may multiplex only HARQ-ACK information and CSI reports, if any, from the UCI in the PUSCH transmission and does not transmit the PUCCH if the UE does not multiplex aperiodic or semi-persistent CSI reports in the PUSCH.

In an example, a wireless device does not expect to multiplex in a PUSCH transmission in one slot with SCS configuration UCI of same type that the wireless device would transmit in PUCCHs in different slots with SCS configuration μ₂if μ₁<μ₂.

In an example, a wireless device may not expect to detect a DCI format scheduling a PDSCH reception or a SPS PDSCH release and indicating a resource for a PUCCH transmission with corresponding HARQ-ACK information in a slot if the wireless device previously detects a DCI format scheduling a PUSCH transmission in the slot and if the wireless device multiplexes HARQ-ACK information in the PUSCH transmission.

In an example, if a wireless device multiplexes aperiodic CSI in a PUSCH and the wireless device would multiplex UCI that includes HARQ-ACK information in a PUCCH that overlaps with the PUSCH and the timing conditions for overlapping PUCCHs and PUSCHs are fulfilled, the wireless device may multiplex only the HARQ-ACK information in the PUSCH and may not transmit the PUCCH.

In an example, if a wireless device transmits multiple PUSCHs in a slot on respective serving cells that include first PUSCHs that are scheduled by DCI format(s) 0_0 or DCI format(s) 0_1 and second PUSCHs configured by respective ConfiguredGrantConfig or semiPersistentOnPUSCH, and the wireless device would multiplex UCI in one of the multiple PUSCHs, and the multiple PUSCHs fulfil the conditions in Subclause 9.2.5 for UCI multiplexing, the wireless device may multiplex the UCI in a PUSCH from the first PUSCHs.

In an example, if a wireless device transmits multiple PUSCHs in a slot on respective serving cells and the wireless device would multiplex UCI in one of the multiple PUSCHs and the wireless device does not multiplex aperiodic CSI in any of the multiple PUSCHs, the wireless device may multiplex the UCI in a PUSCH of the serving cell with the smallest ServCellIndex subject to the conditions for UCI multiplexing being fulfilled. If the wireless device transmits more than one PUSCHs in the slot on the serving cell with the smallest ServCellIndex that fulfil the conditions for UCI multiplexing, the wireless device may multiplex the UCI in the earliest PUSCH that the UE transmits in the slot.

In an example, if a wireless device transmits a PUSCH over multiple slots and the wireless device would transmit a PUCCH with HARQ-ACK information over a single slot and in a slot that overlaps with the PUSCH transmission in one or more slots of the multiple slots, and the PUSCH transmission in the one or more slots fulfills the conditions for multiplexing the HARQ-ACK information, the wireless device may multiplex the HARQ-ACK information in the PUSCH transmission in the one or more slots. The wireless device may not multiplex HARQ-ACK information in the PUSCH transmission in a slot from the multiple slots if the wireless device would not transmit a single-slot PUCCH with HARQ-ACK information in the slot in case the PUSCH transmission was absent.

In an example, if the PUSCH transmission over the multiple slots is scheduled by a DCI format 0_1, the same value of a DAI field is applicable for multiplexing HARQ-ACK information in the PUSCH transmission in any slot from the multiple slots where the UE multiplexes HARQ-ACK information.

In an example, A HARQ-ACK information bit value of 0 may represent a negative acknowledgement (NACK) while a HARQ-ACK information bit value of 1 may represent a positive acknowledgement (ACK).

In an example, two transmission schemes may be supported for 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 non-codebook based transmission when the higher layer parameter txConfig is set to ‘nonCodebook’. If the higher layer parameter txConfig is not configured, the wireless may be not expected to be scheduled by DCI format 0_1. If PUSCH is scheduled by DCI format 0_0, the PUSCH transmission may be based on a single antenna port. 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.

In an example, for codebook based transmission, PUSCH may be scheduled by DCI format 0_0, DCI format 0_1 or semi-statically configured to operate. If this PUSCH is scheduled by DCI format 0_1, or semi-statically configured to operate, the wireless device may determine its PUSCH transmission precoder based on SRS resource Indicator (SRI), Transmitted Precoding Matrix Indicator (TPMI) and the transmission rank, where the SRI, TPMI and the transmission rank may be given by DCI fields of SRS resource indicator and Precoding information and number of layers or given by srs-ResourceIndicator and precodingAndNumberOfLayers. The TPMI may be used to indicate the precoder to be applied over the layers {0 . . . v−1} and that corresponds to the SRS resource selected by the SRI when multiple SRS resources are configured, or if 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. The indicated SRI in slot n is associated with the most recent transmission of SRS resource identified by the SRI, where the SRS resource may be prior to the PDCCH carrying the SRI.

In an example, for codebook based transmission, the wireless device may determine its codebook subsets based on TPMI and upon the reception of higher layer parameter codebookSubset in pusch-Config which may be configured with ‘fullyAndPartialAndNonCoherent’, or ‘partialAndNonCoherent’, or ‘nonCoherent’ depending on the UE capability. The maximum transmission rank may be configured by the higher parameter maxRank in pusch-Config.

In an example, a wireless device reporting its UE capability of ‘partialAndNonCoherent’ transmission may not expect to be configured by codebookSubset with ‘fullyAndPartialAndNonCoherent’.

In an example, a wireless device reporting its UE capability of ‘nonCoherent’ transmission may not expect to be configured by codebookSubset with ‘fullyAndPartialAndNonCoherent’ or with ‘partialAndNonCoherent’.

In an example, a wireless device may not expect to be configured with the higher layer parameter codebookSubset set to ‘partialAndNonCoherent’ when higher layer parameter nrofSRS-Ports in an SRS-ResourceSet with usage set to ‘codebook’ indicates that two SRS antenna ports are configured.

In an example, for codebook based transmission, the wireless device may be configured with a single SRS-ResourceSet with usage set to ‘codebook’ and only one SRS resource may be indicated based on the SRI from within the SRS resource set. The maximum number of configured SRS resources for codebook based transmission may be 2. If aperiodic SRS is configured for a wireless device, the SRS request field in DCI may trigger the transmission of aperiodic SRS resources.

In an example, the wireless device may transmit PUSCH using the same antenna port(s) as the SRS port(s) in the SRS resource indicated by the DCI format 0_1 or by configuredGrantConfig.

In an example, the DM-RS antenna ports may be determined according to the ordering of DM-RS port(s) given by Tables.

In an example, when multiple SRS resources are configured by SRS-ResourceSet with usage set to ‘codebook’, the wireless device may expect that higher layer parameters nrofSRS-Ports in SRS-Resource in SRS-ResourceSet may be configured with the same value for all these SRS resources.

In an example, for non-codebook based transmission, PUSCH may be scheduled by DCI format 0_0, DCI format 0_1 or semi-statically configured to operate. The wireless device may determine its PUSCH precoder and transmission rank based on the SRI when multiple SRS resources are configured, where the SRI may be given by the SRS resource indicator in DCI, or the SRI is given by srs-ResourceIndicator. The UE may use one or more SRS resources for SRS transmission, where, in a SRS resource set, the maximum number of SRS resources which can be configured to the wireless device for simultaneous transmission in the same symbol and the maximum number of SRS resources may be UE capabilities. Only one SRS port for each SRS resource may be configured. Only one SRS resource set may be configured with higher layer parameter usage in SRS-ResourceSet set to ‘nonCodebook’. The maximum number of SRS resources that may be configured for non-codebook based uplink transmission may be 4. 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 may be prior to the PDCCH carrying the SRI.

In an example, for non-codebook based transmission, the wireless device may calculate the precoder used for the transmission of SRS based on measurement of an associated NZP CSI-RS resource. A wireless device may be configured with only one NZP CSI-RS resource for the SRS resource set with higher layer parameter usage in SRS-ResourceSet set to ‘nonCodebook’ if configured.

In an example, if aperiodic SRS resource set is configured, the associated NZP-CSI-RS may be indicated via SRS request field in DCI format 0_1 and 1_1, where AperiodicSRS-ResourceTrigger (indicating the association between aperiodic SRS triggering state and SRS resource sets), triggered SRS resource(s) srs-ResourceSetId, csi-RS (indicating the associated NZP-CSI-RS-ResourceId) may be higher layer configured in SRS-ResourceSet. A wireless device may be not expected to update the SRS precoding information if the gap from the last symbol of the reception of the aperiodic NZP-CSI-RS resource and the first symbol of the aperiodic SRS transmission is less than 42 OFDM symbols.

In an example, if the wireless device configured with aperiodic SRS associated with aperiodic NZP CSI-RS resource, the presence of the associated CSI-RS may be indicated by the SRS request field if the value of the SRS request field is not ‘00’ and if the scheduling DCI is not used for cross carrier or cross bandwidth part scheduling. The CSI-RS may be located in the same slot as the SRS request field. If the UE configured with aperiodic SRS associated with aperiodic NZP CSI-RS resource, any of the TCI states configured in the scheduled CC may not be configured with ‘QCL-TypeD’.

In an example, if periodic or semi-persistent SRS resource set is configured, the NZP-CSI-RS-ResourceConfigID for measurement may be indicated via higher layer parameter associatedCSI-RS in SRS-ResourceSet.

In an example, the wireless device may perform one-to-one mapping from the indicated SRI(s) to the indicated DM-RS ports(s) and their corresponding PUSCH layers {0 . . . v−1} given by DCI format 0_1 or by configuredGrantConfig according to subclause 6.1.2.3 in increasing order.

In an example, the wireless device may transmit PUSCH using the same antenna ports as the SRS port(s) in the SRS resource(s) indicated by SRI(s) given by DCI format 0_1 or by configuredGrantConfig, where the SRS port in (i+1)-th SRS resource in the SRS resource set is indexed as pi=1000+i.

In an example, the DM-RS antenna ports may be determined according to the ordering of DM-RS port(s) given by Tables.

In an example, for non-codebook based transmission, the wireless device may not expect to be configured with both spatialRelationInfo for SRS resource and associatedCSI-RS in SRS-ResourceSet for SRS resource set.

In an example, for non-codebook based transmission, the wireless device may be scheduled with DCI format 0_1 when at least one SRS resource is configured in SRS-ResourceSet with usage set to ‘nonCodebook’.

In an example, the wireless device may be configured with one or more Sounding Reference Signal (SRS) resource sets as configured by the higher layer parameter SRS-ResourceSet. For each SRS resource set, a wireless device may be configured with SRS resources (higher layer parameter SRS-Resource), where the maximum value of K may be indicated by SRS_capability. The SRS resource set applicability may be configured by the higher layer parameter usage in SRS-ResourceSet. When the higher layer parameter usage is set to ‘BeamManagement’, only one SRS resource in each of multiple SRS sets may be transmitted at a given time instant, the SRS resources in different SRS resource sets with the same time domain behavior in the same BWP may be transmitted simultaneously.

In an example, for aperiodic SRS at least one state of the DCI field may be used to select at least one out of the configured SRS resource set(s).

In an example, the SRS parameters may be semi-statically configurable by higher layer parameter SRS-Resource. srs-ResourceId may determine SRS resource configuration identify. Number of SRS ports as defined by the higher layer parameter nrofSRS-Ports. Time domain behavior of SRS resource configuration as indicated by the higher layer parameter resourceType, which may be periodic, semi-persistent, aperiodic SRS transmission. Slot level periodicity and slot level offset as defined by the higher layer parameters periodicityAndOffset-p or periodicityAndOffset-sp for an SRS resource of type periodic or semi-persistent. The UE may not expect to be configured with SRS resources in the same SRS resource set SRS-ResourceSet with different slot level periodicities. For an SRS-ResourceSet configured with higher layer parameter resourceType set to ‘aperiodic’, a slot level offset may be defined by the higher layer parameter slotOffset. Number of OFDM symbols in the SRS resource, starting OFDM symbol of the SRS resource within a slot including repetition factor R as defined by the higher layer parameter resourceMapping. SRS bandwidth B_SRSand C_SRS, as defined by the higher layer parameter freqHopping. Frequency hopping bandwidth, b_hop, as defined by the higher layer parameter freqHopping. Defining frequency domain position and configurable shift, as defined by the higher layer parameters freqDomainPosition and freqDomainShift, respectively. Cyclic shift, as defined by the higher layer parameter cyclicShift-n2 or cyclicShift-n4 for transmission comb value 2 and 4, respectively. Transmission comb value as defined by the higher layer parameter transmissionComb. Transmission comb offset as defined by the higher layer parameter combOffset-n2 or combOffset-n4 for transmission comb value 2 or 4, respectively. SRS sequence ID as defined by the higher layer parameter sequenceId. The configuration of the spatial relation between a reference RS and the target SRS, where the higher layer parameter spatialRelationInfo, if configured, contains the ID of the reference RS. The reference RS can be an SS/PBCH block, CSI-RS configured on serving cell indicated by higher layer parameter servingCellId if present, same serving cell as the target SRS otherwise, or an SRS configured on uplink BWP indicated by the higher layer parameter uplinkBWP, and serving cell indicated by the higher layer parameter servingCellId if present, same serving cell as the target SRS otherwise.

In an example, the wireless device may be configured by the higher layer parameter resourceMapping in SRS-Resource with an SRS resource occupying N_Sϵ{1,2,4} adjacent symbols within the last 6 symbols of the slot, where all antenna ports of the SRS resources are mapped to each symbol of the resource.

In an example, when PUSCH and SRS are transmitted in the same slot, the wireless device can only be configured to transmit SRS after the transmission of the PUSCH and the corresponding DM-RS.

In an example, for a wireless device configured with one or more SRS resource configuration(s), and when the higher layer parameter resourceType in SRS-Resource may be set to ‘periodic’: if the wireless device is configured with the higher layer parameter spatialRelationInfo containing the ID of a reference ‘ssb-Index’, the wireless device may transmit the target SRS resource with the same spatial domain transmission filter used for the reception of the reference SS/PBCH block, if the higher layer parameter spatialRelationInfo contains the ID of a reference ‘csi-RS-Index’, the wireless device may transmit the target SRS resource with the same spatial domain transmission filter used for the reception of the reference periodic CSI-RS or of the reference semi-persistent CSI-RS, if the higher layer parameter spatialRelationInfo containing the ID of a reference ‘srs’, the wireless device may transmit the target SRS resource with the same spatial domain transmission filter used for the transmission of the reference periodic SRS.

In an example, for a wireless device configured with one or more SRS resource configuration(s), and when the higher layer parameter resourceType in SRS-Resource is set to ‘semi-persistent’: when a wireless device receives an activation command for an SRS resource, and when the HARQ-ACK corresponding to the PDSCH carrying the selection command is transmitted in slot n, the corresponding actions and the UE assumptions on SRS transmission corresponding to the configured SRS resource set may be applied starting from slot n+3N_slot^subframe,μ+1. The activation command may also contain spatial relation assumptions provided by a list of references to reference signal IDs, one per element of the activated SRS resource set. Each ID in the list may refer to a reference SS/PBCH block, NZP CSI-RS resource configured on serving cell indicated by Resource Serving Cell ID field in the activation command if present, same serving cell as the SRS resource set otherwise, or SRS resource configured on serving cell and uplink bandwidth part indicated by Resource Serving Cell ID field and Resource BWP ID field in the activation command if present, same serving cell and bandwidth part as the SRS resource set otherwise. if an SRS resource in the activated resource set is configured with the higher layer parameter spatialRelationInfo, the UE shall assume that the ID of the reference signal in the activation command overrides the one configured in spatialRelationInfo. If an SRS resource in the activated resource set is configured with the higher layer parameter spatialRelationInfo, the wireless device may assume that the ID of the reference signal in the activation command overrides the one configured in spatialRelationInfo. When a wireless device receives a deactivation command for an activated SRS resource set, and when the HARQ-ACK corresponding to the PDSCH carrying the selection command is transmitted in slot n, the corresponding actions and UE assumption on cessation of SRS transmission corresponding to the deactivated SRS resource set shall apply starting from slot n+3N_slot^subframe,μ+1. If the wireless device is configured with the higher layer parameter spatialRelationInfo containing the ID of a reference ‘ssb-Index’, the wireless device may transmit the target SRS resource with the same spatial domain transmission filter used for the reception of the reference SS/PBCH block, if the higher layer parameter spatialRelationInfo contains the ID of a reference ‘csi-RS-Index’, the wireless device may transmit the target SRS resource with the same spatial domain transmission filter used for the reception of the reference periodic CSI-RS or of the reference semi-persistent CSI-RS, if the higher layer parameter spatialRelationInfo contains the ID of a reference ‘srs’, the wireless device may transmit the target SRS resource with the same spatial domain transmission filter used for the transmission of the reference periodic SRS or of the reference semi-persistent SRS.

In an example, the wireless device may be not expected to be configured with different time domain behavior for SRS resources in the same SRS resource set. The UE may be also not expected to be configured with different time domain behavior between SRS resource and associated SRS resources set.

In an example, the 2-bit SRS request field in DCI format 0_1, 1_1 may indicate the triggered SRS resource set given in Table. The 2-bit SRS request field in DCI format 2_3 may indicate the triggered SRS resource set if the wireless device is configured with higher layer parameter srs-TPC-PDCCH-Group set to ‘typeB’, or may indicate the SRS transmission on a set of serving cells configured by higher layers if the wireless device is configured with higher layer parameter srs-TPC-PDCCH-Group set to ‘typeA’.

In an example, for PUCCH and SRS on the same carrier, a wireless device may not transmit SRS when semi-persistent and periodic SRS are configured in the same symbol(s) with PUCCH carrying only CSI report(s), or only L1-RSRP report(s). A wireless device may not transmit SRS when semi-persistent or periodic SRS is configured or aperiodic SRS is triggered to be transmitted in the same symbol(s) with PUCCH carrying HARQ-ACK and/or SR. In the case that SRS is not transmitted due to overlap with PUCCH, only the SRS symbol(s) that overlap with PUCCH symbol(s) may be dropped. PUCCH may not be transmitted when aperiodic SRS is triggered to be transmitted to overlap in the same symbol with PUCCH carrying semi-persistent/periodic CSI report(s) or semi-persistent/periodic L1-RSRP report(s) only.

In an example, in case of intra-band carrier aggregation or in inter-band CA band-band combination where simultaneous SRS and PUCCH/PUSCH transmissions are not allowed, a wireless device may be not expected to be configured with SRS from a carrier and PUSCH/UL DM-RS/UL PT-RS/PUCCH formats from a different carrier in the same symbol.

In an example, in case of intra-band carrier aggregation or in inter-band CA band-band combination where simultaneous SRS and PRACH transmissions are not allowed, a wireless device may not transmit simultaneously SRS resource(s) from a carrier and PRACH from a different carrier.

In an example, in case where a SRS resource with SRS-resourceType set as ‘aperiodic’ is triggered on the OFDM symbol configured with periodic/semi-persistent SRS transmission, the wireless device may transmit the aperiodic SRS resource and not transmit the periodic/semi-persistent SRS resource(s) overlapping within the symbol(s). In case a SRS resource with SRS-resourceType set as ‘semi-persistent’ is triggered on the OFDM symbol configured with periodic SRS transmission, the wireless device may transmit the semi-persistent SRS resource and not transmit the periodic SRS resource(s) overlapping within the symbol(s).

In an example, when the wireless device is configured with the higher layer parameter usage in SRS-ResourceSet set to ‘antennaSwitching,’ and a guard period of Y symbols is configured, the wireless device may use the same priority rules as defined above during the guard period as if SRS was configured.

In an example, UCI types reported in a PUCCH may include HARQ-ACK information, SR, and CSI. UCI bits may include HARQ-ACK information bits, if any, SR information bits, if any, and CSI bits, if any. The HARQ-ACK information bits may correspond to a HARQ-ACK codebook.

In an example, a wireless device may transmit one or two PUCCHs on a serving cell in different symbols within a slot of N_symb^slotsymbols. When the wireless device transmits two PUCCHs in a slot, at least one of the two PUCCHs may use PUCCH format 0 or PUCCH format 2.

In an example, for the determination of the number of PRBs, a wireless device may assume 11 CRC bits if a number of respective UCI bits is larger than or equal to 360; otherwise, the wireless device may determine a number of CRC bits based on the number of respective UCI bits.

In an example, If a wireless device does not have dedicated PUCCH resource configuration, provided by PUCCH-ResourceSet in PUCCH-Config, a PUCCH resource set may be provided by pucch-ResourceCommon through an index to a row of given table for transmission of HARQ-ACK information on PUCCH in an initial UL BWP of N_BWP^sizePRBs. The PUCCH resource set may include sixteen resources, each corresponding to a PUCCH format, a first symbol, a duration, a PRB offset RB_BWP^offset, and a cyclic shift index set for a PUCCH transmission. The wireless device may transmit a PUCCH using frequency hopping. An orthogonal cover code with index 0 may be used for a PUCCH resource with PUCCH format 1. The wireless device may transmit the PUCCH using the same spatial domain transmission filter as for a PUSCH transmission scheduled by a RAR UL grant.

In an example, the wireless device may not expect to generate more than one HARQ-ACK information bit prior to establishing RRC connection.

In an example, if a wireless device has dedicated PUCCH resource configuration, the wireless device may be provided by higher layers with one or more PUCCH resources.

In an example, A PUCCH resource may include the following parameters: a PUCCH resource index provided by pucch-ResourceId, an index of the first PRB prior to frequency hopping or for no frequency hopping by startingPRB, an index of the first PRB after frequency hopping by secondHopPRB, an indication for intra-slot frequency hopping by intraSlotFrequencyHopping and a configuration for a PUCCH format, from PUCCH format 0 through PUCCH format 4, provided by format.

In an example, if the format indicates PUCCH-format0, the PUCCH format configured for a PUCCH resource may be PUCCH format 0, where the PUCCH resource may also include an index for an initial cyclic shift provided by initialCyclicShift, a number of symbols for a PUCCH transmission provided by nrofSymbols, a first symbol for the PUCCH transmission provided by startingSymbolIndex.

In an example, if the format indicates PUCCH-format1, the PUCCH format configured for a PUCCH resource may be PUCCH format 1, where the PUCCH resource may also include an index for an initial cyclic shift provided by initialCyclicShift, a number of symbols for a PUCCH transmission provided by nrofSymbols, a first symbol for the PUCCH transmission provided by startingSymbolIndex, and an index for an orthogonal cover code by timeDomainOCC.

In an example, if the format indicates PUCCH-format2 or PUCCH-format3, the PUCCH format configured for a PUCCH resource may be PUCCH format 2 or PUCCH format 3, respectively, where the PUCCH resource may also include a number of PRBs provided by nrofPRBs, a number of symbols for a PUCCH transmission provided by nrofSymbols, and a first symbol for the PUCCH transmission provided by startingSymbolIndex.

In an example, if the format indicates PUCCH-format4, the PUCCH format configured for a PUCCH resource is PUCCH format 4, where the PUCCH resource may also include a number of symbols for a PUCCH transmission provided by nrofSymbols, a length for an orthogonal cover code by occ-Length, an index for an orthogonal cover code by occ-Index, and a first symbol for the PUCCH transmission provided by startingSymbolIndex.

In an example, a wireless device may be configured up to four sets of PUCCH resources. A PUCCH resource set may be provided by PUCCH-ResourceSet and may be associated with a PUCCH resource set index provided by pucch-ResourceSetId, with a set of PUCCH resource indexes provided by resourceList that may provide a set of pucch-ResourceId used in the PUCCH resource set, and with a maximum number of UCI information bits the wireless device may transmit using a PUCCH resource in the PUCCH resource set provided by maxPayloadMinus1. For the first PUCCH resource set, the maximum number of UCI information bits may be 2. A maximum number of PUCCH resource indexes for a set of PUCCH resources may be provided by maxNrofPUCCH-ResourcesPerSet. The maximum number of PUCCH resources in the first PUCCH resource set may be 32 and the maximum number of PUCCH resources in the other PUCCH resource sets may be 8.

In an example, if the wireless device transmits O_UCIUCI information bits, that include HARQ-ACK information bits, the wireless device may determine a PUCCH resource set to be a first set of PUCCH resources with pucch-ResourceSetId=0 if O_UCI≤2 including 1 or 2 HARQ-ACK information bits and a positive or negative SR on one SR transmission occasion if transmission of HARQ-ACK information and SR occurs simultaneously, a second set of PUCCH resources with pucch-ResourceSetId=1, if provided by higher layers, if 2<O_UCI≤N₂where N₃may be provided by maxPayloadMinus1 for the PUCCH resource set with pucch-ResourceSetId=1, a third set of PUCCH resources with pucch-ResourceSetId=2, if provided by higher layers, if N₂<O_UCI≤N₃where N₃may be provided by maxPayloadMinus1 for the PUCCH resource set with pucch-ResourceSetId=2, or a fourth set of PUCCH resources with pucch-ResourceSetId=3, if provided by higher layers, if N₃<O_UCI≤1706.

In an example, if a wireless device is not transmitting PUSCH, and the wireless device is transmitting UCI, the wireless device may transmit UCI in a PUCCH using PUCCH format 0 if the transmission is over 1 symbol or 2 symbols, the number of HARQ-ACK information bits with positive or negative SR (HARQ-ACK/SR bits) is 1 or 2.

In an example, if a wireless device is not transmitting PUSCH, and the wireless device is transmitting UCI, the wireless device may transmit UCI in a PUCCH using PUCCH format 1 if the transmission is over 4 or more symbols, the number of HARQ-ACK/SR bits is 1 or 2.

In an example, if a wireless device is not transmitting PUSCH, and the wireless device is transmitting UCI, the wireless device may transmit UCI in a PUCCH using PUCCH format 2 if the transmission is over 1 symbol or 2 symbols, the number of UCI bits is more than 2.

In an example, if a wireless device is not transmitting PUSCH, and the wireless device is transmitting UCI, the wireless device may transmit UCI in a PUCCH using PUCCH format 3 if the transmission is over 4 or more symbols, the number of UCI bits is more than 2, the PUCCH resource does not include an orthogonal cover code.

In an example, if a wireless device is not transmitting PUSCH, and the wireless device is transmitting UCI, the wireless device may transmit UCI in a PUCCH using PUCCH format 4 if the transmission is over 4 or more symbols, the number of UCI bits is more than 2, the PUCCH resource includes an orthogonal cover code.

In an example, a spatial setting for a PUCCH transmission may be provided by PUCCH-SpatialRelationInfo if the wireless device is configured with a single value for pucch-SpatialRelationInfold; otherwise, if the wireless device is provided multiple values for PUCCH-SpatialRelationInfo, the wireless device may determine a spatial setting for the PUCCH transmission. The wireless device may apply corresponding actions and a corresponding setting for a spatial domain filter to transmit PUCCH 3 msec after the slot where the wireless device may transmit HARQ-ACK information with ACK value corresponding to a PDSCH reception providing the PUCCH-SpatialRelationInfo. If PUCCH-SpatialRelationInfo provides ssb-Index, the wireless may transmit the PUCCH using a same spatial domain filter as for a reception of a SS/PBCH block with index provided by ssb-Index for a same serving cell or, if servingCellId is provided, for a serving cell indicated by servingCellId, else if PUCCH-SpatialRelationInfo provides csi-RS-Index, the wireless device transmits the PUCCH using a same spatial domain filter as for a reception of a CSI-RS with resource index provided by csi-RS-Index for a same serving cell or, if servingCellId is provided, for a serving cell indicated by servingCellId, else PUCCH-SpatialRelationInfo provides srs, the wireless device may transmit the PUCCH using a same spatial domain filter as for a transmission of a SRS with resource index provided by resource for a same serving cell and/or active UL BWP or, if servingCellId and/or uplinkBWP are provided, for a serving cell indicated by servingCellId and/or for an UL BWP indicated by uplinkBWP.

In an example, a number of DMRS symbols for a PUCCH transmission using PUCCH format 3 or 4 may be provided by additionalDMRS.

In an example, use of L/2-PBSK, instead of QPSK, for a PUCCH transmission using PUCCH format 3 or 4 may be indicated by pi2BPSK.

In an example, a wireless device may not expect to transmit more than one PUCCH with HARQ-ACK information in a slot.

In an example, for DCI format 1_0, the PDSCH-to-HARQ-timing-indicator field values may map to {1, 2, 3, 4, 5, 6, 7, 8}. For DCI format 1_1, if present, the PDSCH-to-HARQ-timing-indicator field values may map to values for a set of number of slots provided by dl-DataToUL-ACK.

In an example, for a SPS PDSCH reception ending in slot n, the wireless device may transmit the PUCCH in slot n+k where k may be provided by the PDSCH-to-HARQ-timing-indicator field in DCI format 1_0 or, if present, in DCI format 1_1 activating the SPS PDSCH reception.

In an example, if the wireless device detects a DCI format 1_1 that may not include a PDSCH-to-HARQ-timing-indicator field and may schedule a PDSCH reception or may activate a SPS PDSCH reception ending in slot n, the wireless device may provide corresponding HARQ-ACK information in a PUCCH transmission within slot n+k where k may be provided by dl-DataToUL-ACK.

In an example, with reference to slots for PUCCH transmissions, if the wireless device detects a DCI format 1_0 or a DCI format 1_1 scheduling a PDSCH reception ending in slot n or if the wireless device detects a DCI format 1_0 indicating a SPS PDSCH release through a PDCCH reception ending in slot n, the wireless device may provide corresponding HARQ-ACK information in a PUCCH transmission within slot n+k, where k may be a number of slots and may be indicated by the PDSCH-to-HARQ-timing-indicator field in the DCI format, if present, or may be provided by dl-DataToUL-ACK. k=0 may correspond to the last slot of the PUCCH transmission that overlaps with the PDSCH reception or with the PDCCH reception in case of SPS PDSCH release.

In an example, a PUCCH transmission with HARQ-ACK information may be subject to the limitations for UE transmissions.

In an example, for a PUCCH transmission with HARQ-ACK information, a wireless device may determine a PUCCH resource after determining a set of PUCCH resources for HARQ-ACK information bits. The PUCCH resource determination may be based on a PUCCH resource indicator field in a last DCI format 1_0 or DCI format 1_1, among the DCI formats 1_0 or DCI formats 1_1 that may have a value of a PDSCH-to-HARQ_feedback timing indicator field indicating a same slot for the PUCCH transmission, that the wireless device may detect and for which the wireless device may transmit corresponding HARQ-ACK information in the PUCCH where, for PUCCH resource determination, detected DCI formats may be first indexed in an ascending order across serving cells indexes for a same PDCCH monitoring occasion and may be then indexed in an ascending order across PDCCH monitoring occasion indexes.

In an example, the PUCCH resource indicator field values may map to values of a set of PUCCH resource indexes provided by ResourceList for PUCCH resources from a set of PUCCH resources provided by PUCCH-ResourceSet with a maximum of eight PUCCH resources.

In an example, for the first set of PUCCH resources and when the size R_PUCCHof resourceList is larger than eight, when a wireless device provides HARQ-ACK information in a PUCCH transmission in response to detecting a last DCI format 1_0 or DCI format 1_1 in a PDCCH reception, among DCI formats 1_0 or DCI formats 1_1 with a value of the PDSCH-to-HARQ_feedback timing indicator field indicating a same slot for the PUCCH transmission, the wireless device may determine a PUCCH resource with index r_PUCCH, 0≤r_PUCCH≤R_PUCCH−1, as

r
PUCCH

=

{

⌊

n

CC
,
p

·

⌈

R
PUCCH

/
8

⌉

N

CCE
,
p

⌋

+

Δ
PRI

·

⌈

R
PUCCH

8

⌉

if
⁢

Δ
PRI

<

R
PUCCH

⁢
mod
⁢
8

⌊

n

CCE
,
p

·

⌊

R
PUCCH

/
8

⌋

N

CCE
,
p

⌋

+

Δ
PRI

·

⌊

R
PUCCH

8

⌋

+

R
PUCCH

⁢
mod
⁢
8

if
⁢

Δ
PRI

≥

R
PUCCH

⁢
mod
⁢
8

}

where N_CCE,pmay be a number of CCEs in CORESET p of the PDCCH reception for the DCI format 1_0 or DCI format 1_1, n_CCE,pmay be the index of a first CCE for the PDCCH reception, and Δ_PRIis a value of the PUCCH resource indicator field in the DCI format 1_0 or DCI format 1_1.

In an example, if a wireless device detects a first DCI format 1_0 or DCI format 1_1 indicating a first resource for a PUCCH transmission with corresponding HARQ-ACK information in a slot and also detects at a later time a second DCI format 1_0 or DCI format 1_1 indicating a second resource for a PUCCH transmission with corresponding HARQ-ACK information in the slot, the wireless device may not expect to multiplex HARQ-ACK information corresponding to the second DCI format in a PUCCH resource in the slot if the PDCCH reception that includes the second DCI format is not earlier than N₃symbols from a first symbol of the first resource for PUCCH transmission in the slot where, for UE processing capability 1 and SCS configuration μ, N₃=8 for μ=0, N₃=10 for μ=1, N₃=17 for μ=2, N₃=20 for μ=3, and for UE processing capability 2 and SCS configuration μ, N₃=3 for μ=0, N₃=4.5 for μ=1, N₃=9 for μ=2.

In an example, if a wireless device transmits HARQ-ACK information corresponding only to a PDSCH reception without a corresponding PDCCH, a PUCCH resource for corresponding PUCCH transmission with HARQ-ACK information may be provided by n1PUCCH-AN.

In an example, if a wireless device transmits a PUCCH with HARQ-ACK information using PUCCH format 0, the wireless device may determine values m₀and m_CSfor computing a value of cyclic shift a where m₀may be provided by initialCyclicShift of PUCCH-format0, and m_CSmay be determined from the value of one HARQ-ACK information bit or from the values of two HARQ-ACK information bits.

In an example, if a wireless device transmits a PUCCH with HARQ-ACK information using PUCCH format 1, the wireless device may be provided a value for m₀by initialCyclicShift of PUCCH-format1.

In an example, uplink power control may determine a power for PUSCH, PUCCH, SRS, and PRACH transmissions.

In an example, a wireless may not expect to simultaneously maintain more than four pathloss estimates per serving cell for all PUSCH/PUCCH/SRS transmissions.

In an example, a PUSCH/PUCCH/SRS/PRACH transmission occasion i may be defined by a slot index n_s,f^μ within a frame with system frame number SFN, a first symbol S within the slot, and a number of consecutive symbols L.

In an example, for a PUSCH transmission on active UL BWP b of carrier f of serving cell c, a wireless device may first calculate a linear value {circumflex over (P)}_PUSCH,b,f,c(i, j, q_d, l) of the transmit power P_PUSCH,b,f,c(i, j, q_d, l) with parameters. If the PUSCH transmission is scheduled by a DCI format 0_1 and when txConfig in PUSCH-Config is set to ‘codebook’, the wireless device may scale the linear value by the ratio of the number of antenna ports with a non-zero PUSCH transmission power to the maximum number of SRS ports supported by the UE in one SRS resource. The wireless device may split the power equally across the antenna ports on which the wireless device transmits the PUSCH with non-zero power.

In an example, if a wireless device transmits a PUSCH on active UL BWP b of carrier of serving cell c using parameter set configuration with index j and PUSCH power control adjustment state with index l, the wireless device may determine the PUSCH transmission power P_PUSCH,b,f,c(i j, q_d, l) in PUSCH transmission occasion i as

P

PUSCH
,
b
,
f
,
c

(

i
,
j
,

q
d

,
l

)

=

min
⁢

{

P

CMAX
,
f
,
c

(
i
)

,

P

O
⁢
_
⁢
PUSCH

,
b
,
f
,
c

(
j
)

+

10
⁢

log
10

(

2
μ

·

M

RB
,
b
,
f
,
c

PUSCH

(
i
)

)

+

α

b
,
f
,
c

(
j
)

·

PL

b
,
f
,
c

(

q
d

)

+

Δ

TF
,
b
,
f
,
c

(
i
)

+

f

b
,
f
,
c

(

i
,
l

)

}

[
dBm
]

In an example, P_CMAX,f,c(i) may be the configured transmit power for carrier f of serving cell c in PUSCH transmission occasion i.

In an example, P_{O_PUSCH,b,f,c}(j) may be a parameter composed of the sum of a component P_{O_NOMINAL_PUSCH,f,c}( ) and a component P_{O_UE_PUSCH,b,f,c}(j) where jϵ{0, 1, . . . , J−1}. If a wireless device is not provided PO-PUSCH-AlphaSet or for a PUSCH transmission scheduled by a RAR UL grant, j=0, P_{O_UE_PUSCH,b,f,c}(0)=0, and P_{O_NOMINAL_PUSCH,f,c}(0)=P_{O_PRE}+Δ_{PREAMBLE_Msg3}, where the parameter preambleReceivedTargetPower (for P_{O_PRE}) and msg3-DeltaPreamble (for Δ_{PREAMBLE_Msg3}) may be provided by higher layers, or Δ_{PREAMBLE_Msg3}=0 dB if msg3-DeltaPreamble is not provided, for carrier f of serving cell c.

For a PUSCH (re)transmission configured by ConfiguredGrantConfig, j=1, P_{O_NOMINAL_PUSCH,f,c}(1) may be provided by p0-NominalWithoutGrant, or P_{O_NOMINAL_PUSCH,f,c}(1)=P_{O_NOMINAL_PUSCH,f,c}(0) if p0-NominalWithoutGrant is not provided, and P_{O_UE_PUSCH,b,f,c}(1) is provided by p0 obtained from p0-PUSCH-Alpha in ConfiguredGrantConfig that may provide an index P0-PUSCH-AlphaSetId to a set of PO-PUSCH-AlphaSet for active UL BWP b of carrier f of serving cell c. For j ϵ{2, . . . , J−1}=S_J, a P_{O_NOMINAL_PUSCH,f,c}(j) value, applicable for all jϵS_J, may be provided by p0-NominalWithGrant, or P_{O_NOMINAL_PUSCH,f,c}(j)=P_{O_NOMINAL_PUSCH,f,c}(0) if p0-NominalWithGrant is not provided, for each carrier f of serving cell c and a set of P_{O_UE_PUSCH,b,f,c}(j) values may be provided by a set of p0 in P0-PUSCH-AlphaSet indicated by a respective set of p0-PUSCH-AlphaSetId for active UL BWP b of carrier f of serving cell c. If the wireless device is provided by SRI-PUSCH-PowerControl more than one values of p0-PUSCH-AlphaSetId and if DCI format 0_1 includes a SRI field, the wireless device may obtain a mapping from sri-PUSCH-PowerControlId in SRI-PUSCH-PowerControl between a set of values for the SRI field in DCI format 0_1 and a set of indexes provided by p0-PUSCH-AlphaSetId that may map to a set of P0-PUSCH-AlphaSet values. If the PUSCH transmission is scheduled by a DCI format 0_1 that includes a SRI field, the wireless device may determine the value of P_{O_UE_PUSCH,b,f,c}(j) from the p0-PUSCH-AlphaSetId value that is mapped to the SRI field value. If the PUSCH transmission is scheduled by a DCI format 0_0 or by a DCI format 0_1 that does not include a SRI field, or if SRI-PUSCHPowerControl is not provided to the wireless device, j=2, and the wireless device may determine P_{O_UE_PUSCH,b,f,c}(j) from the value of the first p0-Pusch-AlphaSet in p0-AlphaSets

In an example, for α_b,f,c(j), for j=0, α_b,f,c(0) may be a value of msg3-Alpha, when provided; otherwise, may be 1. For j=1, α_b,f,c(1) may be provided by alpha obtained from p0-PUSCH-Alpha in ConfiguredGrantConfig providing an index PO-PUSCH-AlphaSetId to a set of PO-PUSCH-AlphaSet for active UL BWP b of carrier f of serving cell c. For jϵS_J, a set of α_b,f,c(j) values may be provided by a set of alpha in PO-PUSCH-AlphaSet indicated by a respective set of p0-PUSCH-AlphaSetId for active UL BWP b of carrier f of serving cell c. If the wireless device is provided SRI-PUSCH-PowerControl and more than one values of p0-PUSCH-AlphaSetId, and if DCI format 0_1 includes a SRI field, the wireless device may obtain a mapping from sri-PUSCH-PowerControlId in SRI-PUSCH-PowerControl between a set of values for the SRI field in DCI format 0_1 and a set of indexes provided by p0-PUSCH-AlphaSetId that may map to a set of PO-PUSCH-AlphaSet values. If the PUSCH transmission is scheduled by a DCI format 0_1 that includes a SRI field, the wireless device may determine the values of α_b,f,c(j) from the p0-PUSCH-AlphaSetId value that is mapped to the SRI field value. If the PUSCH transmission is scheduled by a DCI format 0_0 or by a DCI format 0_1 that does not include a SRI field, or if SRI-PUSCH-PowerControl is not provided to the wireless device, j=2, and the wireless device determines α_b,f,c(j) from the value of the first p0-PUSCH-AlphaSet in p0-AlphaSets.

In an example, M_RB,b,f,c^PUSCH(i) may be the bandwidth of the PUSCH resource assignment expressed in number of resource blocks for PUSCH transmission occasion i on active UL BWP b of carrier f of serving cell c and μ is a SCS configuration.

In an example, PL_b,f,c(q_d) may be a downlink pathloss estimate in dB calculated by the wireless device using reference signal (RS) index qd for the active DL BWP of serving cell c.

In an example, PL_f,c(q_d)=referenceSignalPower-higher layer filtered RSRP, where referenceSignalPower may be provided by higher layers and RSRP for the reference serving cell and the higher layer filter configuration provided by QuantityConfig for the reference serving cell.

In an example, if the wireless device is not configured periodic CSI-RS reception, referenceSignalPower may be provided by ss-PBCH-BlockPower. If the wireless device is configured periodic CSI-RS reception, referenceSignalPower may be provided either by ss-PBCH-BlockPower or by powerControlOffsetSS providing an offset of the CSI-RS transmission power relative to the SS/PBCH block transmission power. If powerControlOffsetSS is not provided to the UE, the wireless device may assume an offset of 0 dB.

In an example, Δ_TF,b,f,c(i)=10 log₁₀((2^BPRE·K^s−1)·β_offset^PUSCH) for KS=1.25 and Δ_TF,b,f,c(i)=0 for KS=0 where KS is provided by deltaMCS for each UL BWP b of each carrier f and serving cell c. If the PUSCH transmission is over more than one layer, Δ_TF,b,f,c(i)=0. BPRE and β_offset^PUSCH, for active UL BWP b of each carrier f and each serving cell c may be computed.

In an example, for the PUSCH power control adjustment state f_b,f,c(i, l) for active UL BWP b of carrier f of serving cell c in PUSCH transmission occasion i, δ_PUSCH,b,f,c(i, l) may be a TPC command value included in a DCI format 0_0 or DCI format 0_1 that schedules the PUSCH transmission occasion i on active UL BWP b of carrier f of serving cell c or jointly coded with other TPC commands in a DCI format 2_2 with CRC scrambled by TPC-PUSCH-RNTI.

In an example, f_b,f,c(i, l)=f_b,f,c(i−i₀, l)+Σ_m=0^C(Dⁱ^)-1δ_PUSCH,b,f,c(m, l) may be the PUSCH power control adjustment state l for active UL BWP b of carrier f of serving cell c and PUSCH transmission occasion i if the wireless device is not provided tpc-Accumulation.

In an example, f_b,f,c(i, l)=δ_PUSCH,b,f,c(i, l) may be the PUSCH power control adjustment state for active UL BWP b of carrier f of serving cell c and PUSCH transmission occasion l if the wireless device is provided tpc-Accumulation.

In an example, f_b,f,c(i, l)=δ_PUSCH,b,f,c(i, l) may be the PUSCH power control adjustment state for active UL BWP b of carrier f of serving cell c and PUSCH transmission occasion i if the wireless device is provided tpc-Accumulation.

In an example, if the wireless device is configured with a SCG, the wireless device may apply the procedures described in this subclause for both MCG and SCG. When the procedures are applied for MCG, the term ‘serving cell’ in this subclause refers to serving cell belonging to the MCG. When the procedures are applied for SCG, the term ‘serving cell’ may refer to serving cell belonging to the SCG. The term ‘primary cell’ in this may refer to the PSCell of the SCG.

In an example, if the wireless device is configured with a PUCCH-SCell, the wireless device may apply the procedures for both primary PUCCH group and secondary PUCCH group. When the procedures are applied for the primary PUCCH group, the term ‘serving cell’ may refer to serving cell belonging to the primary PUCCH group. When the procedures are applied for the secondary PUCCH group, the term ‘serving cell’ may refer to serving cell belonging to the secondary PUCCH group. The term ‘primary cell’ may refer to the PUCCH-SCell of the secondary PUCCH group.

In an example, if a wireless device transmits a PUCCH on active UL BWP b of carrier f in the primary cell c using PUCCH power control adjustment state with index 1, the wireless device may determine the PUCCH transmission power P_PUCCH,b,f,c(i, q_u, q_d, l) in PUCCH transmission occasion i as

P

PUCCH
,
b
,
f
,
c

(

i
,

q
u

,

q
d

,
l

)

=

min
⁢

{

P

CMAX
,
f
,
c

(
i
)

,

P

O
⁢
_
⁢
PUCCH

,
b
,
f
,
c

(

q
u

)

+

10
⁢

log
10

(

2
μ

·

M

RB
,
b
,
f
,
c

PUCCH

(
i
)

)

+

PL

b
,
f
,
c

(

q
d

)

+

Δ

F
⁢
_
⁢
PUCCH

(
F
)

+

Δ

TF
,
b
,
f
,
c

(
i
)

+

g

b
,
f
,
c

(

i
,
l

)

}

[
dBm
]

In an example, P_CMAX,f,c(i) may be the configured transmit power for carrier f of serving cell c in PUCCH transmission occasion i.

In an example, P_{O_PUCCH,b,f,c}(q_u) may be a parameter composed of the sum of a component P_{O_NOMINAL_PUCCH}, provided by p0-nominal, or P_{O_NOMINAL_PUCCH}=0 dBm if p0-nominal is not provided, for carrier f of primary cell c and, if provided, a component P_{O_UE_PUCCH}(q_u) provided by p0-PUCCH-Value in PO-PUCCH for active UL BWP b of carrier f of primary cell c, where 0≤q_u<Q_u. Q_umay be a size for a set of P_{O_UE_PUCCH}values provided by maxNrofPUCCH-P0-PerSet. The set of P_{O_UE_PUCCH}values may be provided by p0-Set. If p0-Set is not provided to the wireless device, P_{O_UE_PUCCH}(q_u)=0, 0≤q_u<Q_u.

In an example, if the wireless device is provided PUCCH-SpatialRelationInfo, the wireless device may obtain a mapping, by an index provided by p0-PUCCH-Id, between a set of pucch-SpatialRelationInfold values and a set of p0-PUCCH-Value values. If the wireless device is provided more than one values for pucch-SpatialRelationInfold and the wireless device receives an activation command indicating a value of pucch-SpatialRelationInfold, the wireless device may determine the p0-PUCCH-Value value through the link to a corresponding p0-PUCCH-Id index. The wireless device may apply the activation command 3 msec after a slot where the wireless device transmits HARQ-ACK information for the PDSCH providing the activation command

In an example, if the wireless device is not provided PUCCH-SpatialRelationInfo, the wireless device may obtain the p0-PUCCH-Value value from the PO-PUCCH with p0-PUCCH-Id value equal to 0 in p0-Set.

In an example, M_RB,b,f,c^PUCCH(i) may be a bandwidth of the PUCCH resource assignment expressed in number of resource blocks for PUCCH transmission occasion i on active UL BWP b of carrier f of serving cell c and μ is a SCS configuration.

In an example, PL_b,f,c(q_d) may be a downlink pathloss estimate in dB calculated by the wireless device using RS resource index q_dfor the active DL BWP of carrier f of the primary cell c. If the wireless device is not provided pathlossReferenceRSs or before the wireless device is provided dedicated higher layer parameters, the wireless device may calculate PL_b,f,c(q_d) using a RS resource obtained from the SS/PBCH block that the wireless device uses to obtain MIB. If the wireless device is provided a number of RS resource indexes, the wireless device may calculate PL_b,f,c(q_d) using RS resource with index q_d, where 0≤q_d<Q_d. Q_dmay be a size for a set of RS resources provided by maxNrofPUCCH-PathlossReferenceRSs. The set of RS resources may be provided by pathlossReferenceRSs. The set of RS resources may include one or both of a set of SS/PBCH block indexes, each provided by ssb-Index in PUCCH-PathlossReferenceRS when a value of a corresponding pucch-PathlossReferenceRS-Id maps to a SS/PBCH block index, and a set of CSI-RS resource indexes, each provided by csi-RS-Index when a value of a corresponding pucch-PathlossReferenceRS-Id maps to a CSI-RS resource index. The wireless device may identify a RS resource in the set of RS resources to correspond either to a SS/PBCH block index or to a CSI-RS resource index as provided by pucch-PathlossReferenceRS-Id in PUCCH-PathlossReferenceRS. If the wireless device is provided PUCCH-SpatialRelationInfo, the wireless device may obtain a mapping, by indexes provided by corresponding values of pucch-PathlossReferenceRS-Id, between a set of pucch-SpatialRelationInfold values and a set of reference signal values provided by PUCCH-PathlossReferenceRS. If the wireless device is provided more than one values for pucch-SpatialRelationInfold and the wireless device receives an activation command [11, TS 38.321] indicating a value of pucch-SpatialRelationInfold, the wireless device may determine the reference signal value in PUCCH-PathlossReferenceRS through the link to a corresponding pucch-PathlossReferenceRS-Id index. The wireless device may apply the activation command 3 msec after a slot where the wireless device transmits HARQ-ACK information for the PDSCH providing the activation command. If PUCCH-SpatialRelationInfo includes servingCellId indicating a serving cell, the wireless device may receive the RS for resource index 9_don the active DL BWP of the serving cell. If the wireless device is not provided PUCCH-SpatialRelationInfo, the wireless device may obtain the reference signal value in PUCCH-PathlossReferenceRS from the pucch-PathlossReferenceRS-Id with index 0 in PUCCH-PathlossReferenceRS where the RS resource may be either on a same serving cell or, if provided, on a serving cell indicated by a value of pathlossReferenceLinking

In an example, the parameter Δ_{F_PUCCH}(F) may be provided by deltaF-PUCCH-f0 for PUCCH format 0, deltaF-PUCCH-f1 for PUCCH format 1, deltaF-PUCCH-f2 for PUCCH format 2, deltaF-PUCCH-f3 for PUCCH format 3, and deltaF-PUCCH-f4 for PUCCH format 4

In an example, Δ_TF,b,f,c(i) may be a PUCCH transmission power adjustment component on active UL BWP b of carrier f of primary cell c.

In an example, for the PUCCH power control adjustment state g_b,f,c(i, l) for active UL BWP b of carrier f of primary cell c and PUCCH transmission occasion i, δ_PUCCH,b,f,c(i, l) may be a TPC command value and may be included in a DCI format 1_0 or DCI format 1_1 for active UL BWP b of carrier f of the primary cell c that the wireless device may detect for PUCCH transmission occasion i or is jointly coded with other TPC commands in a DCI format 2_2 with CRC scrambled by TPC-PUCCH-RNTI.

In an example, g_b,f,c(i, l) g_b,f,c(i−i₀, l)+Σ_m=0^C(Cⁱ^)-1β_PUCCH,b,f,c(m, l) may be the current PUCCH power control adjustment state l for active UL BWP b of carrier f of serving cell c and PUCCH transmission occasion i.

In an example, for SRS, a wireless device may split a linear value {circumflex over (P)}_SRS,b,f,c(i, q_s, l) of the transmit power P_SRS,b,f,c(i, q_s, l) on active UL BWP b of carrier f of serving cell c equally across the configured antenna ports for SRS.

In an example, if a wireless device transmits SRS on active UL BWP b of carrier f of serving cell c using SRS power control adjustment state with index 1, the UE determines the SRS transmission power P_SRS,b,f,c(i, q_s, l) in SRS transmission occasion i as

P

SRS
,
b
,
f
,
c

(

i
,

q
s

,
l

)

=

min
⁢

{

P

CMAX
,
f
,
c

(
i
)

,

P

O
⁢
_
⁢
SRS

,
b
,
f
,
c

(

q
s

)

+

10
⁢

log
10

(

2
μ

·

M

SRS
,
b
,
f
,
c

(
i
)

)

+

α

SRS
,
b
,
f
,
c

(

q
s

)

·

PL

b
,
f
,
c

(

q
d

)

+

h

b
,
f
,
c

(

i
,
l

)

}

[
dBm
]

In an example, P_CMAX,f,c(i) may be the configured transmit power defined for carrier f of serving cell c in SRS transmission occasion i.

In an example, P_{O_SRS,b,f,c}(q_s) may be provided by p0 for active UL BWP b of carrier f of serving cell c and SRS resource set q_sprovided by SRS-ResourceSet and SRS-ResourceSetId; if p0 is not provided, P_{O_SRS,b,f,c}(q_s)=P_{O_NOMINAL_PUSCH,f,c}(0).

In an example, M_SRS,b,f,c(i) may be a SRS bandwidth expressed in number of resource blocks for SRS transmission occasion i on active UL BWP b of carrier f of serving cell c and μ is a SCS configuration.

In an example, α_SRS,b,f,c(q_s) may be provided by alpha for active UL BWP b of carrier f of serving cell c and SRS resource set q_s.

In an example, PL_b,f,c(q_d) is a downlink pathloss estimate in dB calculated by the wireless device using RS resource index q_dfor the active DL BWP of serving cell c and SRS resource set q_s. The RS resource index q_dmay be provided by pathlossReferenceRS associated with the SRS resource set q_sand may be either a ssb-Index providing a SS/PBCH block index or a csi-RS-Index providing a CSI-RS resource index. If the wireless device is not provided pathlossReferenceRS or before the wireless device is provided dedicated higher layer parameters, the wireless device may calculate PL_b,f,c(q_d) using a RS resource obtained from the SS/PBCH block that the wireless device uses to obtain MIB. If the wireless device is provided pathlossReferenceLinking, the RS resource may be on a serving cell indicated by a value of pathlossReferenceLinking.

In an example, for the SRS power control adjustment state for active UL BWP b of carrier f of serving cell c and SRS transmission occasion i, h_b,f,c(i, l) f_b,f,c(i, l), where f_b,f,c(i, l) may be the current PUSCH power control adjustment state, if srs-PowerControlAdjustmentStates indicates a same power control adjustment state for SRS transmissions and PUSCH transmissions or h_b,f,c(i)=h_b,f,c(i−1)+Σ_m=0^C(Sⁱ^)-1δ_SRS,b,f,c(m) if the wireless device is not configured for PUSCH transmissions on active UL BWP b of carrier f of serving cell c, or if srs-PowerControlAdjustmentStates indicates separate power control adjustment states between SRS transmissions and PUSCH transmissions, and if tpc-Accumulation is not provided.

In an example, h_b,f,c(i)=δ_SRS,b,f,c(i) if the wireless device is not configured for PUSCH transmissions on active UL BWP b of carrier f of serving cell c, or if srs-PowerControlAdjustmentStates indicates separate power control adjustment states between SRS transmissions and PUSCH transmissions, and tpc-Accumulation is provided, and the wireless device detects a DCI format 2_3 K_SRS,minsymbols before a first symbol of SRS transmission occasion i, where absolute values of δ_SRS,b,f,c.

In an example, if srs-PowerControlAdjustmentStates indicates a same power control adjustment state for SRS transmissions and PUSCH transmissions, the update of the power control adjustment state for SRS transmission occasion i may occur at the beginning of each SRS resource in the SRS resource set q_s; otherwise, the update of the power control adjustment state SRS transmission occasion i may occur at the beginning of the first transmitted SRS resource in the SRS resource set q_s.

In an example, for PUCCH transmission on a serving cell, a wireless device may be provided a TPC-PUCCH-RNTI for a DCI format 2_2 by tpc-PUCCH-RNTI, a field in DCI format 2_2 may be a TPC command of 2 bits mapping to δ_PUCCH,b,f,cvalues.

In an example, for PUCCH transmission on a serving cell, a wireless device may be provided an index for a location in DCI format 2_2 of a first bit for a TPC command field for the PCell, or the SpCell for EN-DC operation, or for a carrier of the PCell by tpc-IndexPCell.

In an example, for PUCCH transmission on a serving cell, a wireless device may be provided an index for a location in DCI format 2_2 of a first bit for a TPC command field for the PUCCH-SCell or for a carrier for the PUCCH-SCell by tpc-IndexPUCCH-Scell

In an example, for PUCCH transmission on a serving cell, a wireless device may be provided a mapping for the PUCCH power control adjustment state lϵ{0, 1}, by a corresponding {0, 1} value of a closed loop index field that is appended to the TPC command field in DCI format 2_2 if the UE indicates a capability to support two PUCCH power control adjustment states by twoDifferentTPC-Loop-PUCCH, and if the wireless device is configured for two PUCCH power control adjustment states by twoPUCCH-PC-AdjustmentStates

In an example, the wireless device may be also provided on a serving cell with a configuration for a search space set and a corresponding CORESET for monitoring PDCCH candidates for DCI format 2_2 with CRC scrambled by a TPC-PUCCH-RNTI.

In an example, for PUSCH transmission on a serving cell, a wireless device may be provided a TPC-PUSCH-RNTI for a DCI format 2_2 by tpc-PUSCH-RNTI.

In an example, for PUSCH transmission on a serving cell, a wireless device may be provided a field in DCI format 2_2 is a TPC command of 2 bits mapping to values as described in Subclause 7.1.1

In an example, for PUSCH transmission on a serving cell, a wireless device may be provided an index for a location in DCI format 2_2 of a first bit for a TPC command field for an uplink carrier of the serving cell by tpc-Index

In an example, for PUSCH transmission on a serving cell, a wireless device may be provided an index for a location in DCI format 2_2 of a first bit for a TPC command field for a supplementary uplink carrier of the serving cell by tpc-IndexSUL

In an example, for PUSCH transmission on a serving cell, a wireless device may be provided an index of the serving cell by targetCell. If targetCell is not provided, the serving cell may be the cell of the PDCCH reception for DCI format 2_2

In an example, for PUSCH transmission on a serving cell, a wireless device may be provided a mapping for the PUSCH power control adjustment state l ϵ{0, 1}, by a corresponding {0, 1} value of a closed loop index field that may be appended to the TPC command field for the uplink carrier or for the supplementary uplink carrier of the serving cell in DCI format 2_2 if the wireless device indicates a capability to support two PUSCH power control adjustment states, by twoDifferentTPC-Loop-PUSCH, and if the wireless device is configured for two PUSCH power control adjustment states by twoPUSCH-PC-AdjustmentStates

In an example, the wireless device is also provided for the serving cell of the PDCCH reception for DCI format 2_2 with a configuration for a search space set S and a corresponding CORESET p for monitoring PDCCH candidates for DCI format 2_2 with CRC scrambled by a TPC-PUSCH-RNTI.

FIG. 16 is an example diagram illustrating procedures for beam configuration activation, and indication procedures from a base station with a single Transmission and Reception Point (TRP) in accordance with embodiments of the present disclosure. In an example, the base station may configure one or more Transmission Configuration Indication (TCI) states in RRC configurations (e.g., 1610) to support configurations of one or more reference signals to acquire channel characteristics (e.g., Doppler spread, Doppler shift, average delay, delay spread, and spatial Rx parameter) of the wireless channel between the base station and the wireless device. Based on the configured TCI states in RRC configurations (e.g., 1610) and MAC CE signaling (e.g., 1620) from the base station may indicate one TCI state which may be used for the reception of downlink channels (e.g., PDCCH) among the configured TCI states in RRC configurations (e.g., 1610) of the wireless device.

For each DL BWP configured to a UE in a serving cell, a wireless device may be provided by higher layer signaling with up to 3 CORESETs. For each CORESET, the wireless device may be provided a CORESET index (e.g., 0≤p<12, by controlResourceSetId), a DMRS scrambling sequence initialization value (e.g., pdcch-DMRS-ScramblingID), a precoder granularity for a number of REGs in the frequency domain where the UE may assume use of a same DMRS precoder (e.g., precoderGranularity), a number of consecutive symbols (e.g., duration), a set of resource blocks provided by frequencyDomainResources, CCE-to-REG mapping parameters (e.g., cce-REG-MappingType), an antenna port quasi co-location, from a set of antenna port quasi co-locations provided by TCI-State, indicating quasi co-location information of the DMRS antenna port for PDCCH reception in a respective CORESET, and an indication for a presence or absence of a TCI field for DCI format 1_1 transmitted by a PDCCH in CORESET (e.g., TCI-PresentInDCI).

FIG. 17 is an example diagram illustrating applications of a configured or activated TCI state (e.g., 1710) in accordance with embodiments of the present disclosure. If a wireless device has not receive a MAC CE activation command (e.g., 1720) for a TCI state (e.g., 1710) for CORESETs other than a CORESET with index 0, a wireless device may assume that the DMRS port associated with PDCCH receptions may be quasi co-located with the SS/PBCH block the wireless device identified during the initial access procedure.

If a wireless device has not receive a MAC CE activation command (e.g., 1720) for a TCI state for CORESET with index 0, the wireless device may assume that DMRS antenna port for PDCCH receptions in the CORESET may be quasi co-located with a SS/PBCH block the wireless identified either during initial access or, if any, a most recent random access procedure not initiated by a PDCCH order that triggers a non-contention based random access procedure.

If a wireless is provided a TCI state (e.g., 1710) for a CORESET, or if the wireless device receives a MAC CE activation command via a MAC CE activation command (e.g., 1720), the wireless device may assume that the DMRS antenna port associated with PDCCH receptions in the CORESET may be quasi co-located with the one or more DL RS configured by the TCI state (e.g., 1710). For a CORESET with index 0, the wireless device may expect that QCL-TypeD of a CSI-RS in a TCI state indicated by a MAC CE activation command for the CORESET may be provided by a SS/PBCH block. If the wireless device receives a MAC CE activation command (e.g., 1720) for one of the TCI states (e.g., 1710), the wireless device may apply the activation command (e.g., 1720) 3 msec after a slot where the wireless device transmits HARQ-ACK information for the PDSCH providing the activation command (e.g., 1720). The active BWP may be defined as the active BWP in the slot when the activation command is applied.

FIG. 18 is an example diagram illustrating applications of a MAC CE activation command by a wireless device in accordance with embodiments of the present disclosure. The activation command may be identified by a MAC PDU subheader with LCID. It may have a fixed size of 16 bits. In the activation command, Serving Cell ID may indicate the identity of the Serving Cell for which the MAC CE applies. The length of the field may be 5 bits. In the activation command, CORESET ID may indicate a Control Resource Set identified with ControlResourceSetID for which the TCI state may be being indicated. In case the value of the field is 0, the field may refer to the Control Resource Set configured by controlResourceSetZero. The length of the field may be 4 bits. In the activation command, TCI State ID may indicate the TCI state identified by TCI-StateId applicable to the Control Resource Set identified by CORESET ID field. If the field of CORESET ID is set to 0, this field may indicate a TCI-StateId for a TCI state of the first 64 TCI states configured by tci-States-ToAddModList and tci-States-ToReleaseList in the PDSCH-Config in the active BWP. If the field of CORESET ID is set to the other value than 0, this field may indicate a TCI-StateId configured by tci-statesPDCCH-ToAddList and tci-StatesPDCCH-ToReleaseList in the controlResourceSet identified by the indicated CORESET ID. The length of the field may be 7 bits.

FIG. 19 is an example diagram illustrating procedures for beam configuration activation, and indication procedures from a base station with a single TRP in accordance with embodiments of the present disclosure. In an example, the base station may configure one or more TCI states in RRC configurations (e.g., 1910) to support configurations of one or more reference signals to acquire channel characteristics (e.g., Doppler spread, Doppler shift, average delay, delay spread, and spatial Rx parameter) of the wireless channel between the base station and the wireless device. Based on the configured TCI states in RRC configurations (e.g., 1910), MAC CE signaling (e.g., 1920) from the base station may activate or deactivate at least one TCI state among the configured TCI states in RRC configurations (e.g., 1910) of the wireless device. Among the activated TCI states, one of TCI states may be indicated via DCI (e.g., 1930) to indicate one of the activated TCI states that may be used for the reception of downlink channels (e.g., PDSCH) for the wireless device.

FIG. 20 is an example diagram illustrating applications of a configured or indicated TCI state by a wireless device in accordance with embodiments of the present disclosure. A base station may configure whether to use DCI based TCI state indication or not (e.g., TCI-PresentInDCI). When DCI based TCI state indication is not configured (e.g., TCI-PresentInDCI is not configured), one RRC configured TCI state may be used. Otherwise, DCI based TCI state indication may be used (e.g., TCI-PresentInDCI is configured). For TCI state configuration, activation, and indication, a threshold (e.g., 2020) to apply to the configured or indicated TCI state may be indicated by the wireless device. For example, the threshold (e.g., 2020) may be indicated via UE capability signaling. Based on the threshold (e.g., 2020), when a scheduling offset (e.g., the offset 2030 between scheduling DCI (e.g., 2010) and the downlink channel (e.g., 2040)) is smaller than the threshold (e.g., 2020), the indicated TCI state for one CORESET may be used. In an example, the CORESET may be the CORESET that has the lowest CORESET ID in the latest slot. Otherwise, when the scheduling offset (e.g., the offset 2050 between scheduling DCI 2010 and the downlink channel (e.g., 2060) is larger than threshold 2020)), the configured or indicated TCI state for the downlink channel may be used.

FIG. 21 is an example diagram illustrating detailed configurations in RRC configuration with a single TRP in accordance with embodiments of the present disclosure. A base station may configure multiple TCI state configurations (e.g., 2110) in RRC configuration. Based on the TCI state configurations (e.g., 2110), the base station may configure a list of TCI states (e.g., 2120) for the indication of TCI state for a transmission of downlink channels. In an example, the list of TCI states (e.g., 2120) may exist in a configuration for downlink transmissions, such as PDSCH config as shown in FIG. 18. The configuration for downlink transmissions may comprise other configurations such as DMRS, rate matching, RBG size, MCS table, PRB Bundling and ZP CSI-RS. Based on the list of TCI states (e.g., 2120), the base station may activate and deactivate one or more TCI states (e.g., 2130) to the wireless device among the configured TCI states (e.g., 2110) in the list of TCI states (e.g., 2120) via MAC CE signaling. Based on the activated TCI states in the activated and deactivated one or more TCI states (e.g., 2130), a scheduling DCI (e.g., 2140) may schedule a downlink channel with one TCI state among the activated TCI states.

FIG. 22 is an example diagram illustrating applications of a MAC CE activation command by a wireless device in accordance with embodiments of the present disclosure. The activation command may be identified by a MAC PDU subheader with LCID. In the activation command, Serving Cell ID may indicate the identity of the Serving Cell for which the MAC CE applies. In the activation command, BWP ID may indicate a DL BWP for which the MAC CE may apply as the codepoint of the DCI (e.g., bandwidth part indicator field). The length of the BWP ID field may be 2 bits. If there is a TCI state with TCI-StateId i, the Ti field may indicate the activation/deactivation status of the TCI state with TCI-StateId i, otherwise MAC entity shall ignore the Ti field. The Ti field may be set to “1” to indicate that the TCI state with TCI-StateId i shall be activated and mapped to the codepoint of the DCI field (e.g., Transmission Configuration Indication). The Ti field may be set to “0” to indicate that the TCI state with TCI-StateId i shall be deactivated is not mapped to the codepoint of the DCI field (e.g., Transmission Configuration Indication). The codepoint to which the TCI state is mapped may be determined by its ordinal position among all the TCI states with Ti field set to “1”, i.e. the first TCI state with Ti field set to “1” shall be mapped to the codepoint value 0, second TCI state with Ti field set to “1” shall be mapped to the codepoint value 1 and so on. The maximum number of activated TCI states may be 8. In the activation command, R may indicate Reserved bit which may be set to “0”.

FIG. 23 is an example diagram illustrating detailed operations with multiple TRPs in accordance with embodiments of the present disclosure. A base station may configure multiple transmission configurations (e.g., transmission config #0 and #1) for each TRP. The transmission configurations (e.g., transmission config #0 and #1) may comprise various dedicated configurations (e.g., CORESETs, TCI states, configurations for beam failure reporting, PDCCH config, PDSCH config, PUCCH config, PUSCH config, PRACH config, TPC config, SRS config, downlink/uplink bandwidth parts and/or etc.). Based on the transmission configurations (e.g., transmission config #0 and #1), the base station may then indicate one or more of the multiple transmission groups for transmission of downlink or uplink channels. Without transmission groups (e.g., transmission config #0 and #1), a base station may need to indicate every possible information in a DCI. This may lead a higher DCI payload size and/or decrease coverage of a TRP.

FIG. 24 is an example diagram illustrating detailed operations of TCI states with multiple TRPs in accordance with embodiments of the present disclosure. In an example, a transmission group may have dedicated TCI states (e.g., TCI states in transmission group #0 or #1). Without the dedicated TCI states (e.g., TCI states in transmission group #0 or #1) for a transmission group (e.g., transmission group #0 or #1), a base station may need to indicate one of all configured TCI states (e.g., TCI states in transmission group #0 and #1). In addition, a wireless device may need to activate all configured TCI states (e.g., TCI states in transmission group #0 and #1) for multiple panels of the wireless device. Supporting TCI states (e.g., TCI states in transmission group #0 or #1) in a transmission group (e.g., transmission group #0 or #1) may also reduce implementation complexity by reducing a number of activated TCI states (e.g., activated TCI state for each transmission group) for the wireless device. In an example, one or more TCI states may exist in one or more configurations for a transmission group (e.g., transmission group #0 or #1). Among the configured transmission groups (e.g., transmission group #0 and #1), the base station may indicate one or more transmission groups (e.g., transmission group #0 or #1) for the activation and deactivation of configured TCI states via indications in RRC, MAC CE and/or DCI signaling. Based on the indicated one or more transmission groups (e.g., transmission group #0 and #1), the base station may activate and deactivate one or more TCI states in the indicated one or more transmission groups (e.g., transmission group #0 and/or #1) to the wireless device. Among the activated transmission groups via RRC, MAC CE and/or DCI signaling, one or more scheduling DCIs may indicate one or more transmission groups for downlink and/or uplink transmissions. Based on the indication of transmission groups, one or more scheduling DCIs may schedule uplink and/or downlink channels with one or more activated TCI states in the indicated transmission groups. The indication of multiple transmission groups for activation/deactivation and uplink/downlink transmissions may be delivered via a single RRC, MAC CE and/or DCI signaling as well as multiple RRC, MAC CE and/or DCI signaling.

FIG. 25 is an example diagram illustrating detailed operations of CORESETs with multiple TRPs in accordance with embodiments of the present disclosure. For example, a transmission group may have dedicated CORESETs (CORESET #0, #1, #2, #3 and #4). Without the dedicated CORESETs (CORESET #0, #1, #2, #3 and #4) for a transmission group (e.g., transmission group #0 or #1), a wireless device may need to monitor all configured CORESETs (CORESET #0, #1, #2, #3 and #4) for multiple panels of the wireless device. Supporting CORESETs in a transmission group (e.g., transmission group #0 or #1) may also reduce implementation complexity by reducing monitoring and blind decoding of PDCCH by the wireless device. Among the configured transmission groups (e.g., transmission group #0 and #1), the base station may indicate one or more transmission groups for the activation and deactivation of configured CORESETs (CORESET #0, #1, #2, #3 and #4) via indications in RRC, MAC CE and/or DCI signaling. Based on the indicated one or more transmission groups, the base station may activate and deactivate one or more CORESETs in the indicated one or more transmission groups to the wireless device. Among the activated transmission groups via RRC, MAC CE and/or DCI signaling, one or more scheduling DCIs may indicate one or more transmission groups for uplink and/or downlink transmissions. Based on the indication of transmission groups, one or more scheduling DCIs may schedule uplink and/or downlink channels in the one or more CORESETs in the indicated transmission groups. The indication of multiple transmission groups for activation/deactivation and uplink/downlink transmissions may be delivered via a single RRC, MAC CE and/or DCI signaling as well as multiple RRC, MAC CE and/or DCI signaling.

Another configuration/activation/indication for one or more transmission groups may be indicated with various signaling such as an RRC configuration, a MAC CE and/or a DCI signaling. In an example, transmission group may be explicitly configured as a configuration of CORESET with a transmission group ID. In another example, a MAC CE may indicate transmission group ID for the CORESET explicitly by delivering transmission group ID. In another example, the MAC CE may indicate transmission group ID for the CORESET implicitly by delivering TCI state ID instead of transmission group ID. For example, when a wireless device receives a TCI state ID for a CORESET, the wireless device may identify the transmission group ID of the TCI state ID based on the RRC configuration (e.g., RRC configured lists for downlink transmissions, a group ID in TCI state configuration, or transmission group ID by TCI state ID).

In another example, an implicit group may be support by grouping configurations which have same or similar ID (e.g., physical cell ID, PDCCH DMRS ID, PDSCH DMRS ID, data scrambling ID, TRS ID, SSB ID and/or TCI state ID). FIG. 26 is an example diagram illustrating detailed operations of grouping based on configured IDs with multiple TRPs in accordance with embodiments of the present disclosure. As shown in FIG. 26, configurations which have identical or similar IDs (e.g., physical cell ID, PDCCH DMRS ID, PDSCH DMRS ID, data scrambling ID, TRS ID, SSB ID and/or TCI state ID) may be grouped together.

It should be noted that a transmission group may also be referred to as a list of TCI states, a group of TCI states, a group of CORESET, a transmission configuration group, a CORESET group, and/or a TRP group.

[00424] In existing technologies, a base station may transmit a downlink control information (DCI) comprising a field, wherein the field may indicate a sounding reference signal resource indicator (SRS resource indicator, SRI). The SRI may indicate one SRS resource of one or more SRS resources configured to a wireless device. A DCI may comprise a resource indicator for indicating one resource of one or more uplink resources such as PUCCH resources, uplink PT-RS resources, and/or DM-RS resources. With recent technologies, the wireless device may be configured with a plurality of TRPs of a cell. For example, the base station may configure a first TRP and a second TRP for the cell. Each TRP may provide a downlink carrier and/or an uplink carrier. The plurality of TRPs, compared to a single TRP, may require a larger number of SRS resources to be configured to the wireless device. The plurality of TRPs may require a larger number of uplink resources to be configured to the wireless device compared to a case of the single TRP. For example, the base station may need to configure a plurality of SRS resources combining one or more SRS resources for the first TRP and the one or more SRs resources for the second TRP. For example, the base station may need to configure a plurality of PUCCH resources combining one or more PUCCH resources for the first TRP and the one or more second PUCCH resources for the second TRP.

With existing technologies, an increased number of SRS resources may increase overhead in DCI signaling. For example, a size of the field may be three bits when eight SRS resources are configured for the single TRP case. A size of the field may be increased to four bits when sixteen SRS resources are configured for supporting the case of the plurality of TRPs. Additional overhead/increase of the overhead may not be desirable, as the wireless device may need to expect the increased DCI size. Embodiments enhance a DCI signaling based on a grouping of uplink resources such as SRS resources. Embodiments may reduce a DCI overhead and may allow a multi-TRP scenario with a low overhead.

FIG. 27 is an example diagram illustrating detailed operations of an uplink DCI with multiple TRPs in accordance with embodiments of the present disclosure. A base station may configure one or more transmission group configurations (e.g., one or more CORESET groups) and one or more SRS resource groups in RRC configuration. A transmission group may comprise one or more configuration parameters for a TRP. For example, the configuration parameters may comprise an index of a CORESET group that the TRP may be based on. A SRS resource group may comprise one or more second configuration parameters. For example, the second configuration parameters may comprise a SRS resource group index or an associated CORESET group index or an associated TRP index. The second configuration parameters may comprise one or more SRS resources. The second configurations parameters may comprise one or more SRS resource indicators/indexes. The group configuration of one or more transmission group and/or the group configuration of the one or more SRs resource groups may be either explicit or implicit. It should be noted that the SRS group may also be referred to as an SRS resource set, an uplink transmission configuration, an uplink transmission group, a spatial relation info group or a spatial relation group.

In an example, one or more SRS resource group may exist in one or more configurations for uplink transmissions (e.g., PUCCH config or PUSCH config). The one or more configurations may comprise other configurations. In an example, the other configurations may be parameters such as PUCCH resource configuration for possible formats (e.g. format 1, 2 3 and 4), scheduling request resources, multi-CSI-PUCCH resources, dl-DataToUL-ACK, spatial relation info list and/or pucch-PowerControl. In another example, the other parameters may be parameters such as PUSCH scrambling identity, txConfig, DMRS configuration, pusch-PowerControl, frequencyHopping, resource allocation type, PUSCH time domain allocation list, PUSCH aggregation factor, MCS table, transformPrecoder, codebook subset, maxRank, RBG size, UCI on PUSCH and/or Pi/2 BPSK.

The base station may associate a SRS resource group of the one or more SRS resource groups to a transmission group of the one or more transmission groups. The base station may configure a mapping between each SRS resource group of the one or more SRS resource groups with each transmission group of the one or more transmission groups. For example, the base station may configure one or more RRC signaling comprising one or more of {a SRS resource group index, a CORESET group index}, wherein a SRS resource group indicated by the SRS resource group index may be mapped to a CORESET group (or a transmission group) indicated by the CORESET group index. In order to configure multiple SRS resource groups, various explicit or implicit methods may be considered. In an example, one or more list ID may be configured in RRC configuration. For example, SRS resource group ID may be configured in the SRS resource or resource set configuration in addition to an SRS resource ID or a resource set ID. In an example, SRS resource group may be defined based on an SRS resource ID or a resource set ID. For example, an SRS resource ID which is less than a certain number (e.g., 8) may be defined as a first SRS resource group and an SRS resource ID which is equal or larger than a certain number (e.g., 8) may be defined as a second SRS resource group. In another example, an SRS resource set may be used as an SRS resource group. For example, an index value of an SRS resource group (e.g., SRS resource group index=0) may be mapped to a transmission group with the same index (e.g., CORESET group index=0). For example, an SRS resource without indicating with an SRS resource group index may be considered as a group index being zero. For example, a SRS resource without configuration of an SRS resource group index may be considered as a first SRS resource group with index=0. Embodiments to configure a plurality of SRS resource groups may be applied to a plurality of PUCCH resource groups and/or a plurality of TPC config groups shown in the specification.

Based on the configurations of transmission groups and SRS resource groups, associations between transmission group and SRS resource group may be supported. In an example, SRS resource group may have a transmission group ID in its configuration. In an example, SRS resource group and transmission group which have same ID may be associated. In an example, a transmission group of CSI-RS, SSB and/or TCI state of SSB/CSI-RS in a spatial relation of the SRS resource may be the associated transmission group of the SRS resource group. Embodiments allow to reduce a DCI field indicating a SRS resource of one or more SRS resource for a TRP, based on determining a SRS resource group based on a CORESET group/a TRP index.

In an example, the wireless device may decide a spatial information of uplink signal (e.g., PUCCH, PUSCH, SRS or PRACH) based on the association. For example, when a wireless device receives an uplink scheduling DCI via a CORESET of a transmission group, the wireless device may use one or more SRS resources in an SRS resource group associated with the transmission group of the CORESET. In an example, a dedicated SRS resource group for each transmission scheme (e.g., codebook based or non-codebook based) may be provided to a wireless device.

FIG. 28 is an example diagram illustrating detailed operations of a downlink DCI which indicates PUCCH resource in accordance with embodiments of the present disclosure. A base station may configure one or more transmission group configurations and one or more PUCCH resource groups in RRC configuration. The group configuration may be either explicit or implicit. It should be noted that the PUCCH resource group may also be referred to as a PUCCH resource set, a PUCCH transmission configuration or a PUCCH transmission group.

In an example, one or more PUCCH resource group may exist in one or more configurations for uplink operations (e.g., UL BWP). The one or more configurations may comprise other configurations. In an example, the other configurations may be parameters such as PUCCH resource configuration for possible formats (e.g. format 1, 2 3 and 4), scheduling request resources, multi-CSI-PUCCH resources, dl-DataToUL-ACK, spatial relation info list, pucch-PowerControl, DMRS configs for PUCCH, interslotFrequencyHopping, maxCodeRate, nrofSlots, pi2BPSK and/or simultaneousHARQ-ACK-CSI.

In order to configure multiple PUCCH resource groups, various explicit or implicit methods may be considered. In an example, one or more list ID may be configured in RRC configuration. For example, PUCCH resource group ID may be configured in the PUCCH resource or PUCCH resource set. In an example, additional PUCCH config may be supported and may be used as a second PUCCH resource group. In this case, existing PUCCH config for single TRP operation may be used as a first group of PUCCH resource group. In an example, PUCCH resource group may be defined based on a PUCCH resource ID or a PUCCH resource set ID. For example, a PUCCH resource ID which is less than a certain number (e.g., 8) may be defined as a first PUCCH resource group and a PUCCH resource ID which is equal or larger than a certain number (e.g., 8) may be defined as a second PUCCH resource group. In another example, a PUCCH resource set may be used as a PUCCH resource group.

Based on the configurations of transmission groups and PUCCH resource groups, associations between transmission group and PUCCH resource group may be supported. In an example, PUCCH resource group may have a transmission group ID in its configuration. In an example, PUCCH resource group and transmission group which have same ID may be associated. In an example, a transmission group of CSI-RS, SSB and/or TCI state of SSB/CSI-RS in a spatial relation of the PUCCH resource may be the associated transmission group of the PUCCH resource group.

In an example, the wireless device may send a PUCCH based on the association. For example, when a wireless device receives an uplink or downlink scheduling DCI via a CORESET of a transmission group, the wireless device may use PUCCH configurations of a PUCCH resource in a PUCCH resource group associated with the transmission group of the CORESET. In an example, a dedicated PUCCH resource for each or combined information (e.g., ACK/NACK, CSI and/or SR) may be provided to a wireless device.

FIG. 29 is an example diagram illustrating detailed operations of a DCI which allocates one or more uplink signals in accordance with embodiments of the present disclosure. A base station may configure one or more transmission group configurations and one or more TPC resource groups in RRC configuration. The group configuration may be either explicit or implicit. It should be noted that the TPC resource group may also be referred to as a TPC resource set, a TPC command configuration or a TPC list.

In an example, one or more TPC resource group may exist in one or more configurations for one or more uplink signals (e.g., PUCCH config, PUSCH config, and/or SRS config). The one or more configurations may comprise other configurations. In an example, the other configurations may be parameters such as tpc-Accumulation, msg3-Alpha, p0-NominalWithoutGrant, p0-AlphaSets, pathloss reference RS, twoPUSCH-PC-AdjustmentStatesdeltaMCS, and/or SRI to PUSCH mappings.

In order to configure multiple TPC resource groups, various explicit or implicit methods may be considered. In an example, one or more list ID may be configured in RRC configuration. For example, TPC resource group ID may be configured in the TPC resource group. In this case, the existing TPC resource may be used as a first group and additional TPC resources may support a TPC resource group ID. In an example, TPC resource group may be defined based on a TCP resource ID, an SRS resource ID or an SRS resource set ID. For example, a TPC resource ID which is less than a certain number (e.g., 16) may be defined as a first PUCCH resource group and a PUCCH resource ID which is equal or larger than a certain number (e.g., 16) may be defined as a second TPC resource group. In another example, a TPC resource set may be used as a TPC resource group. It should be noted that TPC resource ID may be referred to as an SRI-PUSCH-PowerControl ID.

Based on the configurations of transmission groups and TPC resource groups, associations between transmission group and TPC resource group may be supported. In an example, TPC resource group may have a transmission group ID in its configuration. In an example, TPC resource group and transmission group which have same ID may be associated. In an example, a transmission group of CSI-RS, SSB and/or TCI state of SSB/CSI-RS in a list of pathloss reference RS of the TPC resource may be the associated transmission group of the TPC resource group.

In an example, the wireless device may control a transmit power of its uplink signal based on the association. For example, when a wireless device receives an uplink scheduling DCI via a CORESET of a transmission group, the wireless device may use TPC configurations of a TPC resource in a TPC resource group associated with the transmission group of the CORESET. In an example, a dedicated TPC resource for each signal (e.g., PUCCH, PUSCH, PRACH or SRS) may be provided to a wireless device.

FIG. 30 is an example diagram illustrating detailed operations of a group DCI which indicates one or more TPC commands in accordance with embodiments of the present disclosure. A base station may configure one or more transmission group configurations and one or more TPC command groups in RRC configuration. The command group configuration may be either explicit or implicit. It should be noted that the TPC command group may also be referred to as a PDCCH Config, a TPC command set, a TPC command list, a TPC command config set, a TPC command list, a TPC command configuration, a TPC command config group or a TPC command config list.

In an example, one or more TPC command group may exist in one or more configurations for one or more uplink signals (e.g., PUCCH config, PUSCH config, and/or SRS config). The one or more configurations may comprise other configurations. In an example, the other configurations may be parameters such as CORESETs, search spaces, downlink preemption, tpc-Index, tpc-IndexSUL, targetCell, targetPCID, tpc-IndexPCell, tpc-IndexPUCCH-SCell, startingBitofFormat2-3, fieldTypeFormat2-3 and/or startingBitOfFormat2-3SUL. In an example, the other configurations may be configured for each transmission group. For example, the base station may configure a first set of configuration parameters such as tpc-Index, tpc-IndexSUL, targetCell, targetPCID, tpc-IndexPCell and tpc-IndexPUCCH-SCell for a first TRP of a cell. The base station may configure a second set of configuration parameters such as tpc-Index, tpc-IndexSUL, targetCell, targetPCID, tpc-IndexPCell, or tpc-IndexPUCCH-SCell for a second TRP of the cell. The wireless device may receive a TPC command from the first TRP (or a first CORESET group). The wireless device may apply the first set of configuration parameters (e.g., tpc-Index, tpc-IndexSUL, targetCell, targetPCID, tpc-IndexPCell, tpc-IndexPUCCH-SCell) to locate/identify a TPC entry for the cell among one or more entries from the TCP command. The wireless device may receive a second TPC command from the second TRP (or a second CORESET group). The wireless device may apply the second set of configuration parameters to locate/identify a second TPC entry for the cell among one or more entries from the second TPC command.

In order to configure multiple TPC command groups, various explicit or implicit methods may be considered. In an example, one or more list ID may be configured in RRC configuration. For example, TPC command group ID may be configured in the TPC resource group. In this case, the existing TPC command configurations may be used as a first group and additional TPC command configurations may support a TPC command group ID. In an example, TPC command group may be defined based on a PDCCH config ID, a PDSCH config ID, an SRS resource ID or an SRS resource set ID. In another example, a PDCCH config may be used as a TPC resource group.

Based on the configurations of transmission groups and TPC command groups, associations between transmission group and TPC command group may be supported. In an example, TPC resource group may have a transmission group ID in its configuration. In an example, TPC resource group and transmission group which have same ID may be associated. In an example, a transmission group of CSI-RS, SSB and/or TCI state of SSB/CSI-RS in a list of pathloss reference RS of the TPC resource may be the associated transmission group of the TPC resource group.

In an example, the wireless device may receive a TPC command of its uplink signal based on the association. For example, when a wireless device receives a group DCI for TPC commands, the wireless device may apply the TPC commands to the associated TPC resource group. Then, when the wireless device receives a downlink or an uplink DCI via a CORESET of a transmission group, the wireless device may use the TPC configurations of a TPC resource in the TPC resource group associated with the transmission group of the CORESET. In an example, a dedicated TPC resource for each signal (e.g., PUCCH, PUSCH, PRACH or SRS) may be provided to a wireless device.

In an example, a wireless device may receive, for a control resource set, a medium access control element indicating a transmission configuration of a plurality of transmission configurations. For example, the wireless device may determine the transmission configuration being associated with a transmission configuration group of a plurality of transmission configuration groups, wherein the transmission configuration group comprises at least one transmission configuration of the plurality of transmission configurations. For example, the wireless device may determine a sounding reference signal (SRS) resource group associated the transmission configuration group based on at least one reference signal of the at least one transmission configuration. For example, the wireless device may receive, via the control resource set, a downlink control information, indicating a sounding reference signal (SRS) resource indication index, for an uplink channel. For example, the wireless device may transmit the uplink channel based on the transmission configuration group based on the receiving the downlink control information via the control resource set associated with the SRS group.

In an example, the SRS resource indication index may indicate spatial relation information of an uplink signal.

In an example, the uplink signal may be a physical uplink control channel. In an example, the uplink signal may be a physical uplink shared channel. In an example, the uplink signal may be an SRS.

In an example, the uplink signal may be a physical random access channel.

In an example, one or more transmitted precoding matrix indicator and one or more transmission rank may be determined based on the SRS resource indication.

In an example, the SRS resource indication may indicate a power control information for an uplink signal.

In an example, the uplink signal may be a physical uplink shared channel.

In an example, a wireless device may receive a radio resource configuration message comprising a plurality of uplink control channel configurations comprising a plurality of uplink control channel resources. For example, the wireless device may receive, for a control resource set, a signaling indicating a transmission group. For example, the wireless device may determine a configuration of the plurality of uplink control channel configurations being associated with the transmission group, wherein the configuration indicates at least one uplink resource of the plurality of uplink control channel resources. For example, the wireless device may receive, via the control resource set, a downlink control information scheduling a downlink channel and indicating an uplink resource of the at least one uplink resource. For example, based on the receiving the downlink control information via the control resource set associated with the transmission group, the wireless device may receive the downlink channel based on the transmission group. For example, the wireless device may transmit an uplink control channel via the uplink resource.

In an example, the uplink control channel resource may indicate a starting physical resource block identity for the transmission of the uplink control channel.

In an example, the wireless device transmits the uplink control channel via the resources may indicate by physical resource block identity.

In an example, the uplink control channel resource may indicate a usage of intra slot frequency hopping for the transmission of the uplink control channel.

In an example, the uplink control channel resource may indicate a physical resource block identity for a second hop.

In an example, the wireless device may transmit the uplink control channel applying intra slot frequency hopping based on the indication.

In an example, the uplink control channel resource may indicate a format for the transmission of the uplink control channel.

In an example, the wireless device may transmit the uplink control channel based on the format.

In an example, a wireless device may receive a radio resource configuration message comprising a plurality of transmit power control (TPC) configurations. For example, the wireless device may receive, for a control resource set, a signaling indicating a transmission group. For example, the wireless device may determine a configuration of the plurality of TPC configurations being associated with the transmission group. For example, the wireless device may receive, via the control resource set, a downlink control information allocating an uplink signal. For example, based on the downlink control information via the control resource set associated with the transmission group, the wireless device may transmit the uplink signal based on the configuration.

In an example, the TPC configuration may indicate a usage of TPC accumulation.

In an example, the TPC configuration may indicate p0 and/or alpha.

In an example, the TPC configuration may indicate one or more pathloss reference signal.

In an example, the pathloss reference signal may be a synchronization signal block, a channel state information reference signal, or a sounding reference signal.

In an example, the TPC configuration may indicate a usage of delta MCS.

In an example, the TPC configuration may indicate a mapping between a sounding reference signal index and a physical uplink shared channel.

In an example, a wireless device may receive a radio resource configuration message comprising a plurality of positions for a transmit power control (TPC) command. For example, the wireless device may receive, for a control resource set, a signaling indicating a transmission group. For example, the wireless device may determine a position of the plurality of positions of TPC command being associated with the transmission group. For example, the wireless device may receive a first downlink control information comprising a plurality of TPC command fields. For example, the wireless device may determine a field of the plurality of TPC command fields based on the position. For example, the wireless device may receive, via the control resource set, a second downlink control information allocating an uplink signal. For example, the wireless device, based on the second downlink control information via the control resource set associated with the transmission group, may transmit the uplink signal based on the field.

In an example, first downlink control information may be transmitted with downlink control information format 2-2.

In an example, the position may determine a position of the first bit of TPC command in uplink inside the first downlink control information.

In an example, the position may determine a position of the first bit of TPC command in supplementary uplink inside the first downlink control information. In an example, the radio resource configuration message may comprise target serving cell.

In an example, the TPC commands may be applicable to an uplink signal in the serving cell.

In an example, the radio resource configuration message may comprise target physical cell identity.

In an example, the TPC commands may be applicable to an uplink signal associated with the physical cell identity.

According to various embodiments, a device such as, for example, a wireless device, off-network wireless device, a base station, and/or the like, may comprise one or more processors and memory. The memory may store instructions that, when executed by the one or more processors, cause the device to perform a series of actions. Embodiments of example actions are illustrated in the accompanying figures and specification. Features from various embodiments may be combined to create yet further embodiments.

FIG. 31 is a flow diagram as per an aspect of an example embodiment of the present disclosure. At 3110, a wireless device may receive one or more radio resource control (RRC) messages by a base station. The RRC messages may indicate a plurality of control resource set (coreset) groups for a cell and a plurality of sounding reference signal (SRS) resource sets for the cell. Each of the plurality of coreset groups may correspond with a respective one of the plurality of SRS resource sets. At 3120, the wireless device may receive, via a coreset group of the plurality of coreset groups, a downlink control information (DCI) comprising resource assignments and an SRS resource indication (SRI) index for an uplink channel of the cell. At 3130, the wireless device may determine an SRS resource set, from the plurality of SRS resource sets, corresponding to the coreset group. At 3140, the wireless device may determine an SRS resource from the SRS resource set based on the SRI. The wireless device may transmit the uplink channel with a spatial domain filter determined based on the SRS resource.

According to an example embodiment, the SRI index may indicate spatial relation information for the uplink channel. The uplink channel may be a physical uplink control channel. The uplink channel may be a physical uplink shared channel. The uplink channel may be an SRS. The uplink channel may be a physical random access channel.

According to an example embodiment, a first coreset group may correspond to a first SRS resource set. Group index values of the first coreset group and the first SRS resource set may be zero. A second coreset group may correspond to a second SRS resource set. Group index values of the second coreset group and the second SRS resource set may be one. According to an example embodiment, one or more transmitted precoding matrix indicator and one or more transmission rank for the uplink channel may be determined based on the SRS resource. According to an example embodiment, the wireless device may determine a power of the uplink channel based on the SRS resource.

According to an example embodiment, the wireless device may receive one or more second radio resource control messages comprising configuration parameters indicating a linkage between each of the plurality of coreset groups and a respective one of the plurality of SRS resource sets. Based on the linkage, a first coreset group of the plurality of coreset groups may correspond to a second SRS resource set of the plurality of SRS resource sets. Based on the linkage, a second coreset group of the plurality of coreset groups may correspond to a first SRS resource set of the plurality of SRS resource sets. A first coreset group of the plurality of coreset groups may correspond to a second SRS resource set. An index of the first coreset group may be configured to a SRS resource of the second SRS resource set of the plurality of SRS resource sets. A second coreset group of the plurality of coreset groups may correspond to the first SRS resource set. An index of the second coreset group may be configured to a SRS resource of the first SRS resource set of the plurality of SRS resource sets.

According to an example embodiment, a wireless device may receive one or more messages indicating a plurality of control resource set (coreset) groups for a cell; and a plurality of transmission power control (TPC) parameter sets for an uplink channel of the cell. The one or more messages may indicate that each of the plurality of coreset groups correspond to a respective one of the plurality of TPC parameter sets. The wireless device may receive, via a coreset group of the plurality of coreset groups, a downlink control information (DCI) comprising one or more TPC commands. The wireless device may determine a TPC parameter set, from the plurality of TPC parameter sets, corresponding to the coreset group. The wireless device may update an uplink power for the uplink channel based on a TCP command of the one or more TPC commands. The TPC command may be determined based on the TPC parameter set. The wireless device may transmit an uplink transmission of the uplink channel based on the uplink power.

According to an example embodiment, the DCI may be a group-common DCI and the DCI is based on a DCI format 2-2. The TPC parameter set may comprise a tpc-Index and a first cell index for the cell. The tpc-Index may indicate a position of a first bit of the TPC command among bits of the one or more TPC commands of the DCI. For example, the first cell index is a cell index of the cell. For example, the TPC parameter set may comprise a tpc-IndexSUL, wherein the cell is configured with a supplemental uplink (SUL). According to an example embodiment, the wireless device may determine a first TPC parameter set in response to receiving the DCI from a first coreset group. The first coreset group may correspond to the first TPC parameter set. According to an example embodiment, the wireless device may determine a second TPC parameter set in response to receiving the DCI from a first coreset group of the plurality of coreset groups. The first coreset group may correspond to the second TPC parameter set. According to an example embodiment, the first coreset group may correspond to the TPC parameter set. The group index values of the first coreset group and the first TPC parameter set may be zero. According to an example embodiment, a second coreset group may correspond to the second TPC parameter set. Group index values of the second coreset group and the second TPC parameter set may be one.

According to an example embodiment, a first coreset group may correspond to a second TPC parameter set based on a configuration. The first coreset group may correspond to the second TPC parameter set. An index of the first coreset group may be configured to the second TPC parameter set. According to an example embodiment, a second coreset group may correspond to a first TPC parameter set based on the configuration. The second coreset group may correspond to the first TPC parameter set. An index of the second coreset group may be configured to the first TPC parameter set.

According to an example embodiment, the wireless device may receive one or more second radio resource control messages comprising configuration parameters indicating a linkage between the each of the plurality of coreset groups and the respective one of the plurality of TPC parameter sets.

According to an example embodiment, a wireless device may receive one or more radio resource control (RRC) messages indicating a plurality of control resource set (coreset) groups for a cell and a plurality of sounding reference signal (SRS) resource sets for the cell. The one or more RRC messages may indicate that each of the plurality of coreset groups corresponds with a respective one of the plurality of SRS resource sets. The wireless device may receive, via a CORESET group of the plurality of coreset groups, a downlink control information (DCI) comprising resource assignments and an SRS resource indication (SRI) index for an uplink channel of the cell. The wireless device may determine an SRS resource set from the plurality of SRS resource sets based on a linkage and the coreset group. The wireless device may determine an SRS resource from the SRS resource set based on the SRI of the DCI. The wireless device may transmit the uplink channel based on the determined SRS.

According to an example embodiment, a wireless device may receive one or more radio resource control (RRC) messages indicating a plurality of control resource set (coreset) groups for a cell and a plurality of sounding reference signal (SRS) resource sets for the cell. The one or more RRC messages may indicate a linkage between each of the plurality of coreset groups corresponds with a respective one of the plurality of SRS resource sets. The wireless device may receive, via a control resource set, a downlink control information, indicating an SRS resource indication index (SRI), for an uplink channel. The wireless device may determine an SRS resource group from the plurality of SRS resource groups associated with a transmission configuration group, of the plurality of transmission groups, based on the control resource set. The wireless device may transmit the uplink channel based on an SRS resource determined from the SRI in the SRS resource group.

Embodiments may be configured to operate as needed. The disclosed mechanism may be performed when certain criteria are met, for example, in a wireless device, a base station, a radio environment, a network, a combination of the above, and/or the like. Example criteria may be based, at least in part, on for example, wireless device or network node configurations, traffic load, initial system set up, packet sizes, traffic characteristics, a combination of the above, and/or the like. When the one or more criteria are met, various example embodiments may be applied. Therefore, it may be possible to implement example embodiments that selectively implement disclosed protocols.

A base station may communicate with a mix of wireless devices. Wireless devices and/or base stations may support multiple technologies, and/or multiple releases of the same technology. Wireless devices may have some specific capability(ies) depending on wireless device category and/or capability(ies). A base station may comprise multiple sectors. When this disclosure refers to a base station communicating with a plurality of wireless devices, this disclosure may refer to a subset of the total wireless devices in a coverage area. This disclosure may refer to, for example, a plurality of wireless devices of a given LTE or 5G release with a given capability and in a given sector of the base station. The plurality of wireless devices in this disclosure may refer to a selected plurality of wireless devices, and/or a subset of total wireless devices in a coverage area which perform according to disclosed methods, and/or the like. There may be a plurality of base stations or a plurality of wireless devices in a coverage area that may not comply with the disclosed methods, for example, because those wireless devices or base stations perform based on older releases of LTE or 5G technology.

In this disclosure, “a” and “an” and similar phrases are to be interpreted as “at least one” and “one or more.” Similarly, any term that ends with the suffix “(s)” is to be interpreted as “at least one” and “one or more.” In this disclosure, the term “may” is to be interpreted as “may, for example.” In other words, the term “may” is indicative that the phrase following the term “may” is an example of one of a multitude of suitable possibilities that may, or may not, be employed to one or more of the various embodiments.

If A and B are sets and every element of A is also an element of B, A is called a subset of B. In this specification, only non-empty sets and subsets are considered. For example, possible subsets of B={cell1, cell2} are: {cell1}, {cell2}, and {cell1, cell2}. The phrase “based on” (or equally “based at least on”) is indicative that the phrase following the term “based on” is an example of one of a multitude of suitable possibilities that may, or may not, be employed to one or more of the various embodiments. The phrase “in response to” (or equally “in response at least to”) is indicative that the phrase following the phrase “in response to” is an example of one of a multitude of suitable possibilities that may, or may not, be employed to one or more of the various embodiments. The phrase “depending on” (or equally “depending at least to”) is indicative that the phrase following the phrase “depending on” is an example of one of a multitude of suitable possibilities that may, or may not, be employed to one or more of the various embodiments. The phrase “employing/using” (or equally “employing/using at least”) is indicative that the phrase following the phrase “employing/using” is an example of one of a multitude of suitable possibilities that may, or may not, be employed to one or more of the various embodiments.

The term configured may relate to the capacity of a device whether the device is in an operational or non-operational state. Configured may also refer to specific settings in a device that effect the operational characteristics of the device whether the device is in an operational or non-operational state. In other words, the hardware, software, firmware, registers, memory values, and/or the like may be “configured” within a device, whether the device is in an operational or nonoperational state, to provide the device with specific characteristics. Terms such as “a control message to cause in a device” may mean that a control message has parameters that may be used to configure specific characteristics or may be used to implement certain actions in the device, whether the device is in an operational or non-operational state

In this disclosure, various embodiments are disclosed. Limitations, features, and/or elements from the disclosed example embodiments may be combined to create further embodiments within the scope of the disclosure.

In this disclosure, parameters (or equally called, fields, or Information elements: IEs) may comprise one or more information objects, and an information object may comprise one or more other objects. For example, if parameter (IE) N comprises parameter (IE) M, and parameter (IE) M comprises parameter (IE) K, and parameter (IE) K comprises parameter (information element) J. Then, for example, N comprises K, and N comprises J. In an example embodiment, when one or more (or at least one) message(s) comprise a plurality of parameters, it implies that a parameter in the plurality of parameters is in at least one of the one or more messages, but does not have to be in each of the one or more messages. In an example embodiment, when one or more (or at least one) message(s) indicate a value, event and/or condition, it implies that the value, event and/or condition is indicated by at least one of the one or more messages, but does not have to be indicated by each of the one or more messages.

Furthermore, many features presented above are described as being optional through the use of “may” or the use of parentheses. For the sake of brevity and legibility, the present disclosure does not explicitly recite each and every permutation that may be obtained by choosing from the set of optional features. However, the present disclosure is to be interpreted as explicitly disclosing all such permutations. For example, a system described as having three optional features may be embodied in seven different ways, namely with just one of the three possible features, with any two of the three possible features or with all three of the three possible features.

Many of the elements described in the disclosed embodiments may be implemented as modules. A module is defined here as an element that performs a defined function and has a defined interface to other elements. The modules described in this disclosure may be implemented in hardware, software in combination with hardware, firmware, wetware (i.e. hardware with a biological element) or a combination thereof, all of which may be behaviorally equivalent. For example, modules may be implemented as a software routine written in a computer language configured to be executed by a hardware machine (such as C, C++, Fortran, Java, Basic, Matlab or the like) or a modeling/simulation program such as Simulink, Stateflow, GNU Octave, or LabVIEWMathScript. Additionally, it may be possible to implement modules using physical hardware that incorporates discrete or programmable analog, digital and/or quantum hardware. Examples of programmable hardware comprise: computers, microcontrollers, microprocessors, application-specific integrated circuits (ASICs); field programmable gate arrays (FPGAs); and complex programmable logic devices (CPLDs). Computers, microcontrollers and microprocessors are programmed using languages such as assembly, C, C++ or the like. FPGAs, ASICs and CPLDs are often programmed using hardware description languages (HDL) such as VHSIC hardware description language (VHDL) or Verilog that configure connections between internal hardware modules with lesser functionality on a programmable device. The above mentioned technologies are often used in combination to achieve the result of a functional module.

The disclosure of this patent document incorporates material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent file or records, for the limited purposes required by law, but otherwise reserves all copyright rights whatsoever.

While various embodiments have been described above, it should be understood that they have been presented by way of example, and not limitation. It will be apparent to persons skilled in the relevant art(s) that various changes in form and detail can be made therein without departing from the scope. In fact, after reading the above description, it will be apparent to one skilled in the relevant art(s) how to implement alternative embodiments. Thus, the present embodiments should not be limited by any of the above described exemplary embodiments.

In addition, it should be understood that any figures which highlight the functionality and advantages, are presented for example purposes only. The disclosed architecture is sufficiently flexible and configurable, such that it may be utilized in ways other than that shown. For example, the actions listed in any flowchart may be re-ordered or only optionally used in some embodiments.

Further, the purpose of the Abstract of the Disclosure is to enable the U.S. Patent and Trademark Office and the public generally, and especially the scientists, engineers and practitioners in the art who are not familiar with patent or legal terms or phraseology, to determine quickly from a cursory inspection the nature and essence of the technical disclosure of the application. The Abstract of the Disclosure is not intended to be limiting as to the scope in any way.

Finally, it is the applicant's intent that only claims that include the express language “means for” or “step for” be interpreted under 35 U.S.C. § 112. Claims that do not expressly include the phrase “means for” or “step for” are not to be interpreted under 35 U.S.C. § 112.