Multiplexing and prioritization in new radio

Abstract

A wireless device receives one or more radio resource control (RRC) messages. The RRC messages comprise: configuration parameters of a configured uplink grant; and a first control resource set (coreset) group index associated with the configured uplink grant. A determination is made that a physical uplink control channel (PUCCH) resource of uplink control information (UCI) overlaps in time with a physical uplink shared channel (PUSCH) resource of the configured uplink grant and that a coreset group index associated with the PUCCH resource is the same as the first coreset group index. The UCI is multiplexed in the PUSCH resource based on the determination. The UCI is transmitted via the PUSCH resource.

Description

[0001] Divisional application

[0002] This application is a divisional application of the invention application filed on March 27, 2020, with application number 202080039699.6 and titled "Multiplexing and Prioritization in New Radio".

[0003] Cross-reference to related applications

[0004] This application claims the benefit of U.S. Provisional Application No. 62 / 825,781, filed March 28, 2019, the entire contents of which are hereby incorporated by reference. Attached Figure Description

[0005] Examples of several embodiments of the various embodiments of this disclosure are described herein with reference to the accompanying drawings.

[0006] Figure 1 This is a diagram of an example RAN architecture according to an embodiment of the present disclosure;

[0007] Figure 2A This is a diagram of an example user plane protocol stack according to an embodiment of the present disclosure;

[0008] Figure 2B This is a diagram of an example control plane protocol stack according to aspects of embodiments of this disclosure;

[0009] Figure 3 This is a diagram of an example wireless device and two base stations according to aspects of embodiments of the present disclosure;

[0010] Figure 4A , Figure 4B , Figure 4C and Figure 4D These are example diagrams illustrating uplink and downlink signal transmissions according to embodiments of this disclosure;

[0011] Figure 5A This is a diagram of example uplink channel mapping and example uplink physical signals according to aspects of embodiments of this disclosure;

[0012] Figure 5B This is a diagram of an example downlink channel mapping and an example downlink physical signal according to aspects of embodiments of this disclosure;

[0013] Figure 6 It is a diagram depicting an example of the transmission or reception time of a carrier wave according to an embodiment of the present disclosure;

[0014] Figure 7A and Figure 7B This is a diagram depicting a set of examples of OFDM subcarriers according to aspects of embodiments of this disclosure;

[0015] Figure 8 This is a diagram depicting an example of OFDM radio resources according to an embodiment of the present disclosure;

[0016] Figure 9A It is a diagram depicting example CSI-RS and / or SS block transmissions in a multi-beam system;

[0017] Figure 9B This is a diagram depicting an example downlink beam management procedure according to an embodiment of the present disclosure;

[0018] Figure 10 These are example diagrams of a configured bandwidth portion (BWP) according to an embodiment of the present disclosure;

[0019] Figure 11A and Figure 11B This is a diagram illustrating multiple connectivity aspects of embodiments according to this disclosure;

[0020] Figure 12 A diagram of an example random access procedure according to an embodiment of the present disclosure;

[0021] Figure 13 This is an example of the structure of a MAC entity according to an embodiment of the present disclosure;

[0022] Figure 14 This is an example RAN architecture diagram according to aspects of embodiments of this disclosure;

[0023] Figure 15 This is a diagram of an example of an RRC state according to an embodiment of the present disclosure;

[0024] Figure 16 This is an example of a downlink beam management procedure according to an embodiment of the present disclosure;

[0025] Figure 17 This is an example of a downlink beam management procedure according to an embodiment of the present disclosure;

[0026] Figure 18 This is an example of a downlink beam management procedure according to an embodiment of the present disclosure;

[0027] Figure 19 This is an example of a downlink beam management procedure according to an embodiment of the present disclosure;

[0028] Figure 20 This is an example flowchart of a downlink beam management procedure according to an embodiment of the present disclosure;

[0029] Figure 21This is an example of uplink multiplexing according to aspects of embodiments of this disclosure;

[0030] Figure 22 This is an example of uplink multiplexing according to aspects of embodiments of this disclosure;

[0031] Figure 23 This is an example of uplink multiplexing according to aspects of embodiments of this disclosure;

[0032] Figure 24 This is an example flowchart of uplink multiplexing according to an embodiment of the present disclosure;

[0033] Figure 25 This is an example of uplink multiplexing according to aspects of embodiments of this disclosure;

[0034] Figure 26 This is an example flowchart of uplink multiplexing according to an embodiment of the present disclosure;

[0035] Figure 27 This is an example flowchart of uplink multiplexing according to an embodiment of the present disclosure;

[0036] Figure 28 This is an example flowchart of uplink multiplexing according to an embodiment of the present disclosure. Detailed Implementation

[0037] The exemplary embodiments disclosed herein implement the operation of a beam management procedure. Embodiments of the technology disclosed herein can be employed in the field of multi-carrier communication systems. More specifically, embodiments of the technology disclosed herein can relate to beam management procedures in multi-carrier communication systems.

[0038] The following abbreviations are used throughout this disclosure:

[0039] 3GPP 3rd Generation Partnership Project

[0040] 5GC 5G Core Network

[0041] ACK confirmation

[0042] AMF Access and Mobility Management Functions

[0043] ARQ (Automatic Repeat Request)

[0044] AS Access Layer

[0045] ASIC (Application-Specific Integrated Circuit)

[0046] BA bandwidth adaptation

[0047] BCCH Broadcast Control Channel

[0048] BCH Broadcast Channel

[0049] BPSK (Binary Phase Shift Keying)

[0050] BWP bandwidth portion

[0051] CA carrier aggregation

[0052] CC component carrier

[0053] CCCH (Common Control Channel)

[0054] CDMA Code Division Multiple Access

[0055] CN Core Network

[0056] CP cyclic prefix

[0057] CP-OFDM Cyclic Prefix-Orthogonal Frequency Division Multiplexing

[0058] C-RNTI Cell-Radio Network Temporary Identifier

[0059] CS configured scheduling

[0060] CSI Channel State Information

[0061] CSI-RS Channel State Information - Reference Signal

[0062] CQI Channel Quality Indicator

[0063] CSS Public Search Space

[0064] CU central unit

[0065] DC Dual Connection

[0066] DCCH Dedicated Control Channel

[0067] DCI Downlink Control Information

[0068] DL downlink

[0069] DL-SCH Downlink Shared Channel

[0070] DM-RS demodulation reference signal

[0071] DRB Data Radio Bearer

[0072] DRX discontinuous reception

[0073] DTCH Dedicated Service Channel

[0074] DU Allocation Unit

[0075] EPC Evolution Pack Core

[0076] E-UTRA Evolution of UMTS Terrestrial Radio Access

[0077] E-UTRAN Evolution - Universal Terrestrial Radio Access Network

[0078] FDD (Frequency Division Duplex)

[0079] FPGA (Field Programmable Gate Array)

[0080] F1-C F1-Control Plane

[0081] F1-U F1-User Plane

[0082] gNB Next Generation Node B

[0083] HARQ Hybrid Automatic Repeat Request

[0084] HDL Hardware Description Language

[0085] IE Information Elements

[0086] IP Internet Protocol

[0087] LCID (Logical Channel Identifier)

[0088] LTE Long Term Evolution

[0089] MAC Media Access Control

[0090] MCG Main Cell Group

[0091] MCS modulation and coding scheme

[0092] MeNB's lead actor enters node B

[0093] MIB Master Information Block

[0094] MME (Mobility Management Entity)

[0095] MN master node

[0096] NACK (Negative Acknowledgment)

[0097] NAS Non-access Layer

[0098] NG CP Next-Generation Control Plane

[0099] NGC Next Generation Core

[0100] NG-C NG-Control Plane

[0101] ng-eNB Next Generation Evolution Node B

[0102] NG-U NG-User Plane

[0103] NR New Radio

[0104] NR MAC New Radio MAC

[0105] NR PDCP New Radio PDCP

[0106] NR PHY New Radio Physics

[0107] NR RLC New Radio RLC

[0108] NR RRC New Radio RRC

[0109] NSSAI Network Layer Selection Auxiliary Information

[0110] O&M Operation and Maintenance

[0111] OFDM (Orthogonal Frequency Division Multiplexing)

[0112] PBCH (Physical Broadcast Channel)

[0113] PCC main component carrier

[0114] PCCH Paging Control Channel

[0115] PCell main cell

[0116] PCH Paging Channel

[0117] PDCCH Physical Downlink Control Channel

[0118] PDCP Packet Data Convergence Protocol

[0119] PDSCH Physical Downlink Shared Channel

[0120] PDU Protocol Data Unit

[0121] PHICH Physical HARQ Indicator Channel

[0122] PHY (Physics)

[0123] PLMN Public Land Mobile Network

[0124] PMI Precoding Matrix Indicator

[0125] PRACH Physical Random Access Channel

[0126] PRB Physical Resource Block

[0127] PSCell Primary and Secondary Communities

[0128] PSS Master Synchronization Signal

[0129] pTAG main timer advance group

[0130] PT-RS phase tracking reference signal

[0131] PUCCH (Physical Uplink Control Channel)

[0132] PUSCH Physical Uplink Shared Channel

[0133] QAM (Quadrature Amplitude Modulation)

[0134] QFI (Quality of Service Indicator)

[0135] QoS (Quality of Service)

[0136] QPSK (Quadrature Phase Shift Keying)

[0137] RA Random Access

[0138] RACH Random Access Channel

[0139] RAN (Radio Access Network)

[0140] RAT Radio Access Technology

[0141] RA-RNTI Random Access-Radio Network Temporary Identifier

[0142] RB resource block

[0143] RBG resource block group

[0144] RI rank indicator

[0145] RLC Radio Link Control

[0146] RRC Radio Resource Control

[0147] RS reference signal

[0148] RSRP reference signal received power

[0149] SCC secondary component carrier

[0150] SCell Auxiliary Community

[0151] SCG auxiliary community group

[0152] SC-FDMA Single Carrier Frequency Division Multiple Access

[0153] SDAP Service Data Adaptation Protocol

[0154] SDU Service Data Unit

[0155] SeNB Auxiliary Evolution Node B

[0156] SFN system frame number

[0157] S-GW Service Gateway

[0158] SI System Information

[0159] SIB System Information Block

[0160] SMF Session Management Function

[0161] SN auxiliary node

[0162] SpCell Special Cell

[0163] SRB signaling radio bearer

[0164] SRS Detection Reference Signal

[0165] SS synchronization signal

[0166] SSS auxiliary synchronization signal

[0167] sTAG timed advance group

[0168] TA scheduled in advance

[0169] TAG: Scheduled advance group

[0170] TAI Tracking Area Identifier

[0171] TAT Time Alignment Timer

[0172] TB transfer block

[0173] TC-RNTI Temporary Cell - Temporary Identifier for Radio Networks

[0174] TDD Time Division Duplex

[0175] TDMA Time Division Multiple Access

[0176] TTI Transmission Time Interval

[0177] UCI uplink control information

[0178] UE User Equipment

[0179] UL uplink

[0180] UL-SCH uplink shared channel

[0181] UPF User Plane Functions

[0182] UPGW User Plane Gateway

[0183] VHDL VHSIC Hardware Description Language

[0184] Xn-C Xn-Control Plane

[0185] Xn-U Xn-User Plane

[0186] Various physical layer modulation and transmission mechanisms can be used to implement exemplary embodiments of this disclosure. Exemplary 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 techniques, etc. Hybrid transmission mechanisms such as TDMA / CDMA and OFDM / CDMA can also be employed. Various modulation schemes can be applied to signal transmission in the physical layer. Examples of modulation schemes include, but are not limited to, phase, amplitude, code, and combinations thereof. Example radio transmission methods can use Binary Phase Shift Keying (BPSK), Quadrature Phase Shift Keying (QPSK), 16-QAM, 64-QAM, 256-QAM, 1024-QAM, etc., to implement Quadrature Amplitude Modulation (QAM). Physical radio transmission can be enhanced by dynamically or semi-dynamically changing the modulation and coding scheme according to transmission requirements and radio conditions.

[0187] Figure 1 This is an example radio access network (RAN) architecture according to an embodiment of the present disclosure. As shown in this example, the RAN node may be a next-generation node B (gNB) (e.g., 120A, 120B) that provides a new radio (NR) user plane and control plane protocol termination to a first radio device (e.g., 110A). In this example, the RAN node may be a next-generation evolved Node B (ng-eNB) (e.g., 120C, 120D) that provides an evolved UMTS terrestrial radio access (E-UTRA) user plane and control plane protocol termination to a second radio device (e.g., 110B). The first radio device can communicate with the gNB via a Uu interface. The second radio device can communicate with the ng-eNB via a Uu interface.

[0188] gNB or ng-eNB can manage functions such as: radio resource management and scheduling, IP header compression, data encryption and integrity protection, selection of Access and Mobility Management Functions (AMF) at the User Equipment (UE) Attachment, routing of user plane and control plane data, connection setup and release, scheduling and transmission of paging messages (originating from AMF), scheduling and transmission of system broadcast information (originating from AMF or Operation and Maintenance (O&M)), measurement and measurement report configuration, transport layer packet marking in the uplink, session management, network slice support, Quality of Service (QoS) flow management and mapping to data radio carriers, support for UEs in RRC_INACTIVE state, distribution of Non-Access Layer (NAS) messages, RAN sharing, and dual connectivity or tight interoperability between NR and E-UTRA.

[0189] In this example, one or more gNBs and / or one or more ng-eNBs can interconnect with each other via the Xn interface. The gNB or ng-eNB can connect to the 5G core network (5GC) via the NG interface. In this example, the 5GC may include one or more AMF / User Plane Function (UPF) functions (e.g., 130A or 130B). The gNB or ng-eNB can connect to the UPF via the NG User Plane (NG-U) interface. The NG-U interface can provide delivery of User Plane Protocol Data Units (PDUs) between the RAN node and the UPF (e.g., non-guaranteed delivery). The gNB or ng-eNB can connect to the AMF via the NG Control Plane (NG-C) interface. The NG-C interface can provide functions such as NG interface management, UE context management, UE mobility management, NAS message delivery, paging, PDU session management, configuration delivery, or warning message transmission.

[0190] In practice, a UPF can manage functions such as anchor points for intra / inter-Radio Access Technology (RAT) mobility (where applicable), external PDU session points for interconnection to data networks, packet routing and forwarding, user plane portions of packet inspection and policy rule enforcement, service usage reporting, uplink classifiers supporting the routing of service flows to data networks, branch points supporting multihomed PDU sessions, user plane QoS processing (e.g., packet filtering, gating), uplink (UL) / downlink (DL) rate enforcement, uplink service authentication (e.g., Service Data Flow (SDF) to QoS flow mapping), downlink packet buffering, and / or downlink data notification triggering.

[0191] In practice, the AMF can manage functions such as NAS signaling termination, NAS signaling security, access layer (AS) security control, core network (CN) inter-node signaling for mobility between 3GPP access networks, idle mode UE reachability (e.g., paging retransmission control and execution), registration area management, support for intra-system and inter-system mobility, access authentication, access authorization including roaming rights checks, mobility management control (subscription and policies), and support for network slice and / or session management function (SMF) selection.

[0192] Figure 2AThis is the instance user plane protocol stack, where the 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 the Physical (PHY) layer (e.g., 215 and 225) layer can terminate in the network-side radio device (e.g., 110) and gNB (e.g., 120). In the instance, the PHY layer provides delivery services to higher layers (e.g., MAC, RRC, etc.). In this example, the services and functions of the MAC sublayer may include mapping between logical channels and transport channels, multiplexing MAC Service Data Units (SDUs) belonging to one or different logical channels into / from transport blocks (TBs) delivered to / from the PHY layer, demultiplexing from said transport blocks, scheduling information reporting, error correction via Hybrid Automatic Repeat Request (HARQ) (e.g., one HARQ entity per carrier in the case of carrier aggregation (CA), priority handling between UEs via dynamic scheduling, and priority handling between logical channels of a UE via logical channel priority ordering and / or filling. MAC entities may support one or more parameter sets and / or transmit timings. In this example, mapping constraints in logical channel priority ordering can control which parameter set and / or transmit timing a logical channel can use. In this example, the RLC sublayer may support Transparent Mode (TM), Unacknowledged Mode (UM), and Acknowledged Mode (AM) transmit modes. RLC configuration can be based on each logical channel, independent of parameter sets and / or transmit time interval (TTI) durations. In this example, Automatic Repeat Request (ARQ) can operate on any set of parameters and / or TTI duration configured for the logical channel. In this example, services and functions of the PDCP layer for the user plane can include sequence numbering, header compression and decompression, delivery of user data, reordering and duplicate detection, PDCP PDU routing (e.g., in the case of split bearers), PDCP SDU retransmission, encryption, decryption and integrity protection, PDCP SDU dropping, PDCP reconstruction and data recovery for RLC AM, and / or PDCP PDU duplication. In this example, SDAP services and functions can include mapping between QoS flows and data radio bearers. In this example, SDAP services and functions can include mapping Quality of Service Indicators (QFIs) in DL and UL packets. In this example, SDAP protocol entities can be configured for individual PDU sessions.

[0193] Figure 2BThis is an instance control plane protocol stack, where the PDCP (e.g., 233 and 242), RLC (e.g., 234 and 243), and MAC (e.g., 235 and 244) sublayers and the PHY (e.g., 236 and 245) layer can terminate and perform the aforementioned services and functions in the radio device (e.g., 110) and the network-side gNB (e.g., 120). In this instance, RRC (e.g., 232 and 241) can terminate in both the radio device and the network-side gNB. In this example, the services and functions of RRC may include: broadcasting system information related to AS and NAS, paging initiated by 5GC or RAN, establishing, maintaining, and releasing RRC connections between the UE and RAN, security functions including key management, establishing, configuring, maintaining, and releasing signaling radio bearers (SRB) and data radio bearers (DRB), mobility functions, QoS management functions, UE measurement reporting and control of reports, detection and recovery of radio link failures, and / or the transmission of NAS messages from UE to NAS and from NAS to UE. In the example, the NAS control protocol (e.g., 231, 251) can be terminated in the radio device and the AMF (e.g., 130) on the network side, and can perform functions such as authentication, mobility management between the UE and the AMF for 3GPP access and non-3GPP access, and session management between the UE and the SMF for 3GPP access and non-3GPP access.

[0194] In the example, the base station can configure multiple logical channels for a wireless device. A logical channel among the multiple logical channels can correspond to a radio bearer, and the radio bearer can be associated with QoS requirements. In this example, the base station can configure a logical channel to map to one or more TTI / parameter sets among multiple TTI / parameter sets. The wireless device can receive downlink control information (DCI) indicating uplink grants via the physical downlink control channel (PDCCH). In this example, the uplink grant may be for a first TTI / parameter set and may indicate uplink resources for transmitting a transport block. The base station can configure each of the multiple logical channels, where one or more parameters will be used by a logical channel prioritization process at the MAC layer of the wireless device. The one or more parameters may include priority, prioritized bit rate, etc. A logical channel among the multiple logical channels can correspond to one or more buffers including data associated with the logical channel. The logical channel prioritization process can allocate uplink resources to one or more first logical channels and / or one or more MAC control elements (CEs) among the multiple logical channels. One or more first logical channels can be mapped to a first TTI / parameter set. The MAC layer at the wireless device can multiplex one or more MAC CEs and / or one or more MAC SDUs (e.g., logical channels) from a MAC PDU (e.g., a transport block). In an example, a MAC PDU may include a MAC header comprising multiple MAC sub-headers. These sub-headers may correspond to a MAC CE or MAC SDU (logical channel) within one or more MAC CEs and / or one or more MAC SDUs. In an example, a MAC CE or logical channel may be configured with a Logical Channel Identifier (LCID). In an example, the LCID for a logical channel or MAC CE may be fixed / pre-configured. In an example, the 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 MAC SDU may include the LCID associated with that MAC CE or MAC SDU.

[0195] In examples, a base station can activate and / or deactivate and / or influence one or more processes at a radio device (e.g., setting the value of one or more parameters of one or more processes, or starting and / or stopping one or more timers of one or more processes) by employing one or more MAC commands. One or more MAC commands may include one or more MAC control elements. In examples, one or more processes may include activation and / or deactivation of PDCP packet replication for one or more radio bearers. The base station may transmit a MAC CE including one or more fields, the values ​​of which indicate activation and / or deactivation of PDCP replication for one or more radio bearers. In examples, one or more processes may include Channel State Information (CSI) transmission on one or more cells. The base station may transmit one or more MAC CEs on one or more cells indicating activation and / or deactivation of CSI transmission. In examples, one or more processes may include activation or deactivation of one or more secondary cells. In examples, the base station may transmit MAC CEs indicating activation or deactivation of one or more secondary cells. In examples, the base station may transmit one or more MAC CEs indicating the start and / or stop of one or more Discontinuous Receive (DRX) timers at a radio device. In the example, the base station may transmit one or more MAC CEs indicating one or more timing advance values ​​of one or more timing advance groups (TAGs).

[0196] Figure 3 This is a block diagram of base stations (base station 1, 120A and base station 2, 120B) and a wireless device 110. The wireless device may be referred to as a UE. The base station may be referred to as an NB, eNB, gNB, and / or ng-eNB. In this example, the wireless device and / or base station may act as a relay node. Base station 1, 120A may include at least one communication interface 320A (e.g., a wireless modem, antenna, wired modem, etc.), at least one processor 321A, and at least one set of program code instructions 323A, which are stored in non-transitory memory 322A and executable by at least one processor 321A. Base station 2, 120B may include at least one communication interface 320B, at least one processor 321B, and at least one set of program code instructions 323B, which are stored in non-transitory memory 322B and executable by at least one processor 321B.

[0197] A base station may include many sectors, such as 1, 2, 3, 4, or 6 sectors. A base station may include many cells, for example, ranging from 1 to 50 cells or more. Cells can be classified, for example, as primary cells or secondary cells. During Radio Resource Control (RRC) connection establishment / re-establishment / handover, a serving cell can provide NAS (Non-Access Layer) mobility information (e.g., Tracking Area Identifier (TAI)). During RRC connection re-establishment / handover, a serving cell can provide security input. This cell can be referred to as the primary cell (PCell). In the downlink, the carrier corresponding to the PCell can be a DL primary component carrier (PCC), while in the uplink, the carrier can be a UL PCC. Depending on the radio device capabilities, secondary cells (SCells) can be configured to form a set of serving cells together with the PCells. In the downlink, the carrier corresponding to the SCell can be a downlink secondary component carrier (DL SCC), while in the uplink, the carrier can be an uplink secondary component carrier (UL SCC). SCells may or may not have an uplink carrier.

[0198] A physical cell ID and a cell index can be assigned to a cell that includes a downlink carrier and an optional uplink carrier. A carrier (downlink or uplink) can belong to a cell. The cell ID or cell index can also identify the cell's downlink or uplink carrier (depending on the context of its use). In this disclosure, a cell ID can be equivalently referred to as a carrier ID, and a cell index can be referred to as a carrier index. In embodiments, a physical cell ID or cell index can be assigned to a cell. The cell ID can be determined using a synchronization signal transmitted on the downlink carrier. The cell index can be determined using an RRC message. For example, when this disclosure relates to a first physical cell ID for a first downlink carrier, this disclosure can mean that the first physical cell ID is used for a cell that includes the first downlink carrier. The same concept can be applied, for example, to carrier activation. When this disclosure indicates that a first carrier is activated, this specification can similarly mean that a cell including the first carrier is activated.

[0199] A base station may transmit one or more messages (e.g., RRC messages) to a radio device, including multiple configuration parameters of one or more cells. The one or more cells may include at least one primary cell and at least one secondary cell. In this example, the RRC message may be broadcast or unicast to the radio device. In this example, the configuration parameters may include common parameters and private parameters.

[0200] The services and / or functions of the RRC sublayer may include at least one of the following: broadcasting system information related to AS and NAS; paging initiated by 5GC and / or NG-RAN; establishing, maintaining, and / or releasing RRC connections between radio devices and NG-RAN, which may include at least one of adding, modifying, and releasing carrier aggregation; or adding, modifying, and / or releasing dual connectivity in NR or between E-UTRA and NR. The services and / or functions of the RRC sublayer may additionally include at least one of the following security functions: key management; establishing, configuring, maintaining, and / or releasing signaling radio bearers (SRBs) and / or data radio bearers (DRBs); mobility functions, which may include at least one of handover (e.g., intra-NR mobility or inter-RAT mobility) and context passing; or radio device cell selection and reselection, and control of cell selection and reselection. The services and / or functions of an RRC sub-sub may additionally include at least one of the following: QoS management functions; radio device measurement configuration / reporting; detection and / or recovery of radio link failures; or the delivery of NAS messages from the radio device to a core network entity (e.g., AMF, Mobility Management Entity (MME)) / from a core network entity to the radio device.

[0201] The RRC sublayer can support the RRC_Idle, RRC_Inactive, and / or RRC_Connected states of a radio device. In the RRC_Idle state, the radio device can perform at least one of the following: Public Land Mobile Network (PLMN) selection; receiving broadcast system information; cell selection / reselection; monitoring / receiving paging for mobile termination data initiated by the 5GC; paging in a mobile termination data area managed by the 5GC; or DRX for CN paging configured via NAS. In the RRC_Inactive state, the radio device can perform at least one of the following: receiving broadcast system information; cell selection / reselection; monitoring / receiving RAN / CN paging initiated by the NG-RAN / 5GC; RAN-based notification area (RNA) managed by the NG-RAN; or DRX for RAN / CN paging configured by the NG-RAN / NAS. In the RRC_Idle state of the radio device, the base station (e.g., NG-RAN) can maintain a 5GC-NG-RAN connection (both C / U planes) for the radio device; and / or store the UE AS context for the radio device. In the RRC_Connected state of a radio device, the base station (e.g., NG-RAN) can perform at least one of the following: establish a 5GC-NG-RAN connection for the radio device (both C / U plane); store the UE AS context for the radio device; transmit / receive unicast data to / from the radio device; or perform network-controlled mobility based on measurements received from the radio device. In the RRC_Connected state of the radio device, the NG-RAN can determine the cell to which the radio device belongs.

[0202] System information (SI) can be divided into minimum SI and other SIs. Minimum SIs can be broadcast periodically. A minimum SI may include basic information required for initial access and information for obtaining any other SIs that are periodically broadcast or provided on demand, i.e., scheduling information. Other SIs may be broadcast, provided in a dedicated manner, triggered by the network, or requested by the radio device. Minimum SIs can be transmitted via two different downlink channels using different messages (e.g., MasterInformationBlock and SystemInformationBlockType1). Another SI can be transmitted via SystemInformationBlockType2. For radio devices in the RRC_Connected state, dedicated RRC signaling can be used for requesting and delivering other SIs. For radio devices in the RRC_Idle and / or RRC_Inactive states, the request can trigger a random access procedure.

[0203] A wireless device can report its radio access capability information, which may be static. A base station can request the wireless device to report certain capabilities based on frequency band information. When the network permits, the wireless device can send a temporary capability limitation request to signal to the base station the limited availability of certain capabilities (e.g., due to hardware sharing, interference, or overheating). The base station can acknowledge or reject the request. Temporary capability limitations can be transparent to the 5GC (e.g., static capabilities can be stored in the 5GC).

[0204] When CA is configured, a radio device can have an RRC connection to the network. During the RRC connection establishment / re-establishment / handover procedure, a serving cell can provide NAS mobility information, and during RRC connection re-establishment / handover, a serving cell can provide security input. This cell can be referred to as a PCell. Depending on the capabilities of the radio device, SCells can be configured to form a serving cell set together with the PCell. The serving cell set used for configuring the radio device can include one PCell and one or more SCells.

[0205] SCell reconfiguration, addition, and removal can be performed by RRC. During intra-NR handover, RRC can also add, remove, or reconfigure SCells for use with a target PCell. When adding a new SCell, dedicated RRC signaling can be used to send all the necessary system information for the SCell; that is, when in connected mode, the wireless device may not need to obtain broadcast system information directly from the SCell.

[0206] The purpose of an RRC connection reconfiguration procedure can be to modify the RRC connection (e.g., to establish, modify, and / or release RBs, perform handover, set, modify, and / or release measurements, add, modify, and / or release SCells and cell groups). As part of the RRC connection reconfiguration procedure, NAS-specific information can be passed from the network to the radio device. The RRCConnectionReconfiguration message can be a command to modify the RRC connection. It can convey information for measurement configuration, mobility control, radio resource configuration (e.g., RB, MAC master configuration, and physical channel configuration), including any associated NAS-specific information and security configurations. If the received RRC connection reconfiguration message includes sCellToReleaseList, the radio device can perform SCell release. If the received RRC connection reconfiguration message includes sCellToAddModList, the radio device can perform SCell addition or modification.

[0207] The RRC connection establishment (or re-establishment, restoration) procedure can be used to establish (or re-establish, restore) an RRC connection. The RRC connection establishment procedure may include SRB1 establishment. The RRC connection establishment procedure can be used to transmit initial NAS-specific information / messages from the wireless device to the E-UTRAN. The RRCConnectionReestablishment message can be used to rebuild SRB1.

[0208] The measurement reporting procedure can transmit measurement results from the wireless device to the NG-RAN. After successful security activation, the wireless device can initiate the measurement reporting procedure. Measurement results can be transmitted using measurement report messages.

[0209] The wireless device 110 may include at least one communication interface 310 (e.g., a wireless modem, antenna, etc.), at least one processor 314, and at least one set of program code instructions 316, which are stored in non-transitory memory 315 and can be executed by at least one processor 314. The wireless device 110 may also include at least one of the following: at least one speaker / microphone 311, at least one keypad 312, at least one display / touchpad 313, at least one power supply 317, at least one global positioning system (GPS) chipset 318, and other peripheral devices 319.

[0210] The processor 314 of wireless device 110, the processor 321A of base station 1 120A, and / or the processor 321B of base station 2 120B may include at least one of the following: 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 devices, discrete gate and / or transistor logic, discrete hardware components, etc. The processor 314 of wireless device 110, the processor 321A of base station 1 120A, and / or the processor 321B of base station 2 120B may perform at least one of the following: signal encoding / processing, data processing, power control, input / output processing, and / or any other function that enables wireless device 110, base station 1 120A, and / or base station 2 120B to operate in a wireless environment.

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

[0212] The processor 314 of the wireless device 110 can also be connected to other peripheral devices 319, which may include one or more software and / or hardware modules that provide additional features and / or functions. For example, peripheral device 319 may include at least one of the following: accelerometer, satellite transceiver, digital camera, universal serial bus (USB) port, hands-free headset, FM radio unit, media player, Internet browser, etc.

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

[0214] Wireless links 330A and / or 330B may include at least one of bidirectional links and / or directional links. The communication interface 310 of wireless device 110 may be configured to communicate with the communication interface 320A of base station 1 120A and / or with the communication interface 320B of base station 2 120B. Base station 1 120A and wireless device 110 and / or base station 2 120B and wireless device 110 may be configured to transmit and receive data blocks via wireless links 330A and / or 330B, respectively. Wireless links 330A and / or 330B may employ at least one frequency carrier. Depending on some different aspects of the embodiments, one or more transceivers may be employed. A transceiver may be a device that includes both a transmitter and a receiver. Transceivers may be used in devices such as wireless devices, base stations, relay nodes, etc. Figure 4A , Figure 4B , Figure 4C , Figure 4D , Figure 6 , Figure 7A , Figure 7B , Figure 8 Example embodiments of radio technology implemented in communication interfaces 310, 320A, 320B and wireless links 330A, 330B are shown in the relevant text.

[0215] In this example, other nodes in the wireless network (e.g., AMF, UPF, SMF, etc.) may include one or more communication interfaces, one or more processors, and memory for storing instructions.

[0216] Nodes (e.g., wireless devices, base stations, AMF, SMF, UPF, servers, switches, antennas, etc.) may include one or more processors and a memory storing instructions that, when executed by the one or more processors, cause the node to perform certain processes and / or functions. Example embodiments may implement single-carrier and / or multi-carrier communication operations. Other example embodiments may include a non-transitory tangible computer-readable medium containing instructions executable by one or more processors to enable single-carrier and / or multi-carrier communication operations. Still other example embodiments may include an article of manufacture comprising a non-transitory tangible computer-readable machine-accessible medium having instructions encoded thereon for enabling programmable hardware to enable the node to implement single-carrier and / or multi-carrier communication operations. A node may include a processor, memory, an interface, etc.

[0217] An interface may include at least one of a hardware interface, a firmware interface, a software interface, and / or a combination thereof. A hardware interface may include connectors, wires, electronic devices such as drivers and amplifiers. A software interface may include code stored in a memory device to implement one or more protocols, protocol layers, communication devices, device drivers, combinations thereof, etc. A firmware interface may include a combination of embedded hardware and code stored in and / or communicating with the memory device to implement connectivity, electronic device operation, one or more protocols, protocol layers, communication drivers, device drivers, hardware operation, combinations thereof, etc.

[0218] Figure 4A , Figure 4B , Figure 4C and Figure 4D These are example diagrams illustrating uplink and downlink signal transmissions according to embodiments of this disclosure. Figure 4AAn example uplink transmitter for at least one physical channel is shown. The baseband signal representing the physical uplink shared channel can perform one or more functions. These functions may include at least one of the following: scrambling; modulating scrambling bits to generate complex-valued symbols; mapping complex-valued modulated symbols onto one or more transmit layers; transform precoding to generate complex-valued symbols; precoding the complex-valued symbols; mapping the precoded complex-valued symbols to resource elements; generating complex-valued time-domain single-carrier frequency division multiple access (SC-FDMA) or CP-OFDM signals for antenna ports; and so on. In the example, when transform precoding is enabled, an SC-FDMA signal for uplink transmission can be generated. In the example, when transform precoding is not enabled, it can be... Figure 4A Generate CP-OFDM signals for uplink transmission. These functions are shown as examples, and other mechanisms are expected to be implemented in various embodiments.

[0219] An example structure for modulation and upconversion of the carrier frequency of complex-valued SC-FDMA or CP-OFDM baseband signals and / or complex-valued Physical Random Access Channel (PRACH) baseband signals at the antenna port is shown in Figure 4B In the middle. Filtering can be used before transmission.

[0220] Figure 4C The diagram illustrates an example structure for downlink transmission. The baseband signal representing the downlink physical channel can perform one or more functions. These functions may include: scrambling coded bits in a codeword to be transmitted on the physical channel; modulating the scrambled bits to generate complex-valued modulation symbols; mapping the complex-valued modulation symbols onto one or more transmission layers; precoding the complex-valued modulation symbols for transmission at the antenna port; mapping the complex-valued modulation symbols for the antenna port to resource elements; generating a complex-valued time-domain OFDM signal for the antenna port; and so on. These functions are shown as examples, and other mechanisms are contemplated for implementation in various embodiments.

[0221] In this example, the gNB can transmit a first symbol and a second symbol to a radio device at its antenna ports. The radio device can infer the channel used to transmit the second symbol at the antenna ports (e.g., fading gain, multipath delay, etc.) from the channel used to transmit the first symbol at the antenna ports. In this example, if one or more large-scale properties can be inferred from the channel on which the second symbol is transmitted at the second antenna port, then the first and second antenna ports can be quasi-co-located. The one or more large-scale properties may include at least one of the following: delay spread; Doppler spread; Doppler shift; average gain; average delay; and / or spatial reception (Rx) parameters.

[0222] Example modulation and upconversion of carrier frequency for complex-valued OFDM baseband signal at antenna port Figure 4D As shown in the diagram, filtering can be applied before transmission.

[0223] Figure 5A It is a diagram of instance uplink channel mapping and instance uplink physical signals. Figure 5B This is a diagram illustrating the downlink channel mapping and downlink physical signals in an example. In this example, the physical layer can provide one or more messaging services to the MAC and / or one or more higher layers. For instance, the physical layer can provide these messaging services to the MAC via one or more transport channels. The messaging services can indicate the manner and characteristics of data transmission over the radio interface.

[0224] In exemplary embodiments, a radio network may include one or more downlink and / or uplink transport channels. For example, Figure 5A The diagram illustrates an example uplink transport channel including an uplink shared channel (UL-SCH) 501 and a random access channel (RACH) 502. Figure 5B The diagram illustrates an example of a downlink transport channel including a downlink shared channel (DL-SCH) 511, a paging channel (PCH) 512, and a broadcast channel (BCH) 513. Transport channels can be mapped to one or more corresponding physical channels. For example, UL-SCH 501 can be mapped to a physical uplink shared channel (PUSCH) 503. RACH 502 can be mapped to PRACH 505. DL-SCH 511 and PCH 512 can be mapped to a physical downlink shared channel (PDSCH) 514. BCH 513 can be mapped to a physical broadcast channel (PBCH) 516.

[0225] There may be one or more physical channels without corresponding transmission channels. These physical channels may be used for uplink control information (UCI) 509 and / or downlink control information (DCI) 517. For example, the Physical Uplink Control Channel (PUCCH) 504 may carry UCI 509 from the UE to the base station. For example, the Physical Downlink Control Channel (PDCCH) 515 may carry DCI 517 from the base station to the UE. NR may support UCI 509 multiplexing in PUSCH 503 when UCI 509 and PUSCH 503 transmissions can at least partially overlap in time slots. UCI 509 may include at least one of CSI, ACK / NACK, and / or scheduling request. DCI 517 on PDCCH 515 may indicate at least one of the following: one or more downlink assignments and / or one or more uplink scheduling grants.

[0226] In the uplink, the UE may transmit one or more reference signals (RS) to the base station. For example, the one or more RS may be at least one of a demodulation-RS (DM-RS) 506, a phase-tracking-RS (PT-RS) 507, and / or a sounding RS (SRS) 508. In the downlink, the base station may transmit (e.g., unicast, multicast, and / or broadcast) one or more RS to the UE. For example, the one or more RS may be at least one of a primary synchronization signal (PSS) / secondary synchronization signal (SSS) 521, a CSI-RS 522, a DM-RS 523, and / or a PT-RS 524.

[0227] In this example, the UE can transmit one or more uplink DM-RS 506 to the base station for channel estimation, such as coherent demodulation for one or more uplink physical channels (e.g., PUSCH 503 and / or PUCCH 504). For instance, the UE can transmit at least one uplink DM-RS 506 to the base station using PUSCH 503 and / or PUCCH 504, wherein at least one uplink DM-RS 506 can span the same frequency range as the corresponding physical channel. In this example, the base station can configure the UE using one or more uplink DM-RS configurations. At least one DM-RS configuration can support a frontload DM-RS mode. Frontload DM-RS can be mapped on one or more OFDM symbols (e.g., 1 or 2 adjacent OFDM symbols). One or more additional uplink DM-RS can be configured to be transmitted at one or more symbols of the PUSCH and / or PUCCH. The base station can semi-statistically configure the UE using a maximum number of frontload DM-RS symbols for the PUSCH and / or PUCCH. For example, a UE can schedule single-symbol DM-RS and / or dual-symbol DM-RS based on the maximum number of preceding DM-RS symbols, where the base station can configure the UE using one or more additional uplink DM-RS for PUSCH and / or PUCCH. New radio networks can, for example, support a common DM-RS structure for DL ​​and UL at least for CP-OFDM, where DM-RS locations, DM-RS modes, and / or scrambling sequences can be the same or different.

[0228] In the example, the presence of uplink PT-RS 507 may depend on the RRC configuration. For example, the presence of uplink PT-RS can be UE-specific. For example, the presence and / or mode of uplink PT-RS 507 in the scheduled resources can be UE-specifically configured through a combination of RRC signaling and / or association with one or more parameters (e.g., modulation and coding scheme (MCS)) for other purposes, which can be indicated by the DCI. When configured, the dynamic presence of uplink PT-RS 507 can be associated with one or more DCI parameters including at least one MCS. The radio network can support multiple uplink PT-RS densities defined in the time / frequency domain. When present, the frequency domain density can be associated with at least one configuration of the scheduled bandwidth. The UE can use the same precoding for both DMRS ports and PT-RS ports. The number of PT-RS ports may be less than the number of DM-RS ports in the scheduled resources. For example, uplink PT-RS 507 can be restricted to the UE's scheduled time / frequency duration.

[0229] In an example, the UE can transmit SRS 508 to the base station for channel state estimation to support uplink channel-dependent scheduling and / or link adaptation. For instance, the SRS 508 transmitted by the UE can allow the base station to estimate uplink channel states at one or more different frequencies. The base station scheduler can use the uplink channel states to assign one or more high-quality resource blocks to uplink PUSCH transmissions from the UE. The base station can semi-statistically configure the UE using one or more SRS resource sets. For each SRS resource set, the base station can configure the UE using one or more SRS resources. SRS resource set suitability can be configured by higher-layer (e.g., RRC) parameters. For example, when higher-layer parameters indicate beam management, SRS resources from each of one or more SRS resource sets can be transmitted at a given time. The UE can transmit one or more SRS resources from different SRS resource sets simultaneously. The new radio network can support aperiodic, periodic, and / or semi-persistent SRS transmissions. The UE can transmit SRS resources based on one or more trigger types, wherein the one or more trigger types may include higher-layer signaling (e.g., RRC) and / or one or more DCI formats (e.g., at least one DCI format may be used for the UE to select at least one of one or more configured SRS resource sets). SRS trigger type 0 may refer to SRS triggered based on higher-layer signaling. SRS trigger type 1 may refer to SRS triggered based on one or more DCI formats. In an example, when PUSCH 503 and SRS 508 are transmitted in the same time slot, the UE can be configured to transmit SRS 508 after the transmission of PUSCH 503 and the corresponding uplink DM-RS 506.

[0230] In an example, the base station may semi-statistically configure the UE using one or more SRS configuration parameters that indicate at least one of the following: SRS resource configuration identifier, number of SRS ports, temporal behavior of SRS resource configuration (e.g., indication of periodic, semi-persistent, or aperiodic SRS), time slot (micro-slot and / or subframe) level periodicity and / or offset of periodic and / or aperiodic SRS resources, number of OFDM symbols in SRS resources, initiating OFDM symbols of SRS resources, SRS bandwidth, frequency hopping bandwidth, cyclic shift, and / or SRS sequence ID.

[0231] In the example, in the time domain, an SS / PBCH block may include one or more OFDM symbols within the SS / PBCH block (e.g., four OFDM symbols numbered in ascending order from 0 to 3). An SS / PBCH block may include PSS / SSS 521 and PBCH 516. In the example, in the frequency domain, an SS / PBCH block may include one or more consecutive subcarriers within the SS / PBCH block (e.g., 240 consecutive subcarriers numbered in ascending order from 0 to 239). For example, PSS / SSS 521 may occupy one OFDM symbol and 127 subcarriers. For example, PBCH 516 may span three OFDM symbols and 240 subcarriers. The UE may assume that one or more SS / PBCH blocks transmitted using the same block index may be quasi-co-located, for example, with respect to Doppler spread, Doppler shift, average gain, average delay, and spatial Rx parameters. The UE may not assume quasi-co-location of other SS / PBCH blocks transmitted. The periodicity of SS / PBCH blocks can be configured by the radio network (e.g., via RRC signaling), and one or more time locations where SS / PBCH blocks can be transmitted can be determined by the subcarrier spacing. In an example, the UE may assume a band-specific subcarrier spacing for the SS / PBCH blocks unless the radio network has configured the UE to use a different subcarrier spacing.

[0232] In this example, downlink CSI-RS 522 can be used to provide the UE with channel state information. The radio network can support periodic, non-periodic, and / or semi-persistent transmissions of downlink CSI-RS 522. For example, the base station can use periodic transmissions of downlink CSI-RS 522 to semi-statistically configure and / or reconfigure the UE. Configured CSI-RS resources can be activated and / or deactivated. For semi-persistent transmissions, activation and / or deactivation of CSI-RS resources can be dynamically triggered. In this example, CSI-RS configuration can include one or more parameters indicating at least the number of antenna ports. For example, the base station can configure the UE using 32 ports. The base station can semi-statistically configure the UE using one or more CSI-RS resource sets. One or more CSI-RS resources can be allocated from one or more CSI-RS resource sets to one or more UEs. For example, the base station can semi-statistically configure one or more parameters indicating CSI RS resource mapping, such as the time-domain location of one or more CSI-RS resources, the bandwidth of the CSI-RS resources, and / or periodicity. In this example, the UE can be configured to use the same OFDM symbols for both the downlink CSI-RS 522 and the control resource set (core set) when the downlink CSI-RS 522 and the core set are spatially quasi-co-located and resource elements associated with the downlink CSI-RS 522 are outside the PRB configured for the core set. In this example, the UE can also be configured to use the same OFDM symbols for both the downlink CSI-RS 522 and the SS / PBCH block when the downlink CSI-RS 522 and the SS / PBCH block are spatially quasi-co-located and resource elements associated with the downlink CSI-RS 522 are outside the PRB configured for the SS / PBCH block.

[0233] In an example, the UE can transmit one or more downlink DM-RS 523 signals to the base station for channel estimation, for example, for coherent demodulation of one or more downlink physical channels (e.g., PDSCH 514). For example, the radio network can support one or more variable and / or configurable DM-RS modes for data demodulation. At least one downlink DM-RS configuration can support a frontload DM-RS mode. Frontload DM-RS can be mapped on one or more OFDM symbols (e.g., 1 or 2 adjacent OFDM symbols). The base station can semi-statistically configure the UE using the maximum number of frontload DM-RS symbols for PDSCH 514. For example, the DM-RS configuration can support one or more DM-RS ports. For example, for single-user MIMO, the DM-RS configuration can support at least 8 orthogonal downlink DM-RS ports. For example, for multi-user MIMO, the DM-RS configuration can support 12 orthogonal downlink DM-RS ports. Radio networks may, for example, at least for CP-OFDM support a common DM-RS structure for DL ​​and UL, wherein the DM-RS location, DM-RS mode and / or scrambling sequence may be the same or different.

[0234] In the example, the presence of downlink PT-RS 524 may depend on the RRC configuration. For example, the presence of downlink PT-RS 524 can be UE-specific. For example, the presence and / or mode of downlink PT-RS 524 in the scheduled resources can be UE-specifically configured through a combination of RRC signaling and / or association with one or more parameters (e.g., MCS) that can be indicated by DCI for other purposes. When configured, the dynamic presence of downlink PT-RS 524 can be associated with one or more DCI parameters including at least MCS. The radio network can support multiple PT-RS densities defined in the time / frequency domain. When present, the frequency domain density can be associated with at least one configuration of the scheduled bandwidth. The UE can use the same precoding for DMRS ports and PT-RS ports. The number of PT-RS ports may be less than the number of DM-RS ports in the scheduled resources. For example, downlink PT-RS 524 can be restricted to the UE's scheduled time / frequency duration.

[0235] Figure 6 This is a diagram depicting example transmit and receive times for a carrier according to embodiments of this disclosure. A multi-carrier OFDM communication system may include one or more carriers, for example, ranging from 1 to 32 carriers in the case of carrier aggregation, or from 1 to 64 carriers in the case of dual connectivity. Different radio frame structures (e.g., for FDD and for TDD duplex mechanisms) may be supported. Figure 6 The example frame timing is shown. Downlink and uplink transmissions can be organized into radio frame 601. In this example, the radio frame duration is 10 milliseconds. In this example, the 10-millisecond radio frame 601 can be divided into ten equal-sized subframes 602 with a duration of 1 millisecond. One or more subframes may include one or more time slots (e.g., time slots 603 and 605), depending on the subcarrier spacing and / or CP length. For example, subframes with subcarrier spacings of 15 kHz, 30 kHz, 60 kHz, 120 kHz, 240 kHz, and 480 kHz can include one, two, four, eight, sixteen, and thirty-two time slots, respectively. Figure 6 In this context, a subframe can be divided into two equal-sized time slots 603 with a duration of 0.5 milliseconds. For example, with a 10-millisecond interval, 10 subframes can be used for downlink transmission and 10 subframes can be used for uplink transmission. Uplink and downlink transmissions can be split in the frequency domain. One or more time slots can include multiple OFDM symbols 604. The number of OFDM symbols 604 in time slot 605 can depend on the cyclic prefix length. For example, for the same subcarrier spacing up to 480 kHz with normal CP, the time slot can be 14 OFDM symbols. For the same subcarrier spacing of 60 kHz with extended CP, the time slot can be 12 OFDM symbols. A time slot can contain downlink, uplink, or a combination of downlink and uplink portions, etc.

[0236] Figure 7AThis is a diagram depicting a set of examples of OFDM subcarriers according to embodiments of the present disclosure. In an example, the gNB can communicate with a wireless device using a carrier having an example channel bandwidth 700. One or more arrows in the diagram can depict subcarriers in a multi-carrier OFDM system. The OFDM system can use technologies such as OFDM, SC-FDMA, etc. In an example, arrow 701 indicates a subcarrier transmitting information symbols. In an example, the subcarrier spacing 702 between two consecutive subcarriers in the carrier can be any of 15 kHz, 30 kHz, 60 kHz, 120 kHz, 240 kHz, etc. In an example, different subcarrier spacings can correspond to different sets of transmission parameters. In an example, the transmission parameter set can include at least: a parameter set index; a value for the subcarrier spacing; and a type of cyclic prefix (CP). In an example, the gNB can transmit to / receive from the UE on several subcarriers 703 in the carrier. In an example, due to guard bands 704 and 705, the bandwidth occupied by the several subcarriers 703 (transmission bandwidth) can be less than the channel bandwidth 700 of the carrier. In the example, guard bands 704 and 705 can be used to reduce interference to and from one or more adjacent carriers. The number of subcarriers in a carrier (transmit bandwidth) can depend on the carrier's channel bandwidth and subcarrier spacing. For example, for a carrier with a 20 MHz channel bandwidth and a 15 kHz subcarrier spacing, the transmit bandwidth could be 1024 subcarriers.

[0237] In this example, when CA is configured, the gNB and the radio device can communicate with multiple CCs. In this example, if CA is supported, different component carriers can have different bandwidths and / or subcarrier spacings. In this example, the gNB can transmit a first type of service to the UE on a first component carrier. The gNB can transmit a second type of service to the UE on a second component carrier. Different types of services can have different service requirements (e.g., data rate, latency, reliability), which can be adapted for transmission via different component carriers with different subcarrier spacings and / or bandwidths. Figure 7B An example embodiment is shown. The first component carrier may include a first number of subcarriers 706 having a first subcarrier spacing 709. The second component carrier may include a second number of subcarriers 707 having a second subcarrier spacing 710. The third component carrier may include a third number of subcarriers 708 having a third subcarrier spacing 711. The carriers in a multi-carrier OFDM communication system may be continuous carriers, discontinuous carriers, or a combination of continuous and discontinuous carriers.

[0238] Figure 8This is a diagram depicting OFDM radio resources according to aspects of embodiments of the present disclosure. In an example, the carrier may have a transmit bandwidth 801. In an example, the resource grid may have a frequency domain 802 and a time domain 803 structure. In an example, the resource grid may include a first number of OFDM symbols and a second number of resource blocks in a subframe, initiated from a common resource block for the transmit parameter set and the carrier, indicated by higher-layer signaling (e.g., RRC signaling). In an example, resource elements identified by subcarrier indices and symbol indices in the resource grid may be resource elements 805. In an example, depending on the parameter set associated with the carrier, the subframe may include a first number of OFDM symbols 807. For example, when the subcarrier spacing of the parameter set of the carrier is 15 kHz, the subframe may have 14 OFDM symbols for the carrier. When the subcarrier spacing of the parameter set is 30 kHz, the subframe may have 28 OFDM symbols. When the subcarrier spacing of the parameter set is 60 kHz, the subframe may have 56 OFDM symbols, and so on. In an example, the second number of resource blocks included in the carrier's resource grid can depend on the carrier's bandwidth and parameter set.

[0239] like Figure 8 As shown, resource block 806 may include 12 subcarriers. In the example, multiple resource blocks may be grouped into resource block groups (RBGs) 804. In the example, the size of an RBG may depend on at least one of the following: an RRC message indicating the RBG size configuration; the size of the carrier bandwidth; or the size of a bandwidth portion of the carrier. In the example, a carrier may include multiple bandwidth portions. A first bandwidth portion of the carrier may have a different frequency location and / or bandwidth than a second bandwidth portion of the carrier.

[0240] In this example, the gNB can transmit downlink control information to the radio device, including downlink or uplink resource block assignments. The base station can transmit or receive data packets (e.g., transport blocks) scheduled and transmitted via one or more resource blocks and one or more time slots, based on parameters in the downlink control information and / or one or more RRC messages. In this example, the gNB can indicate to the radio device a start symbol for a first time slot relative to the one or more time slots. In this example, the gNB can transmit or receive data packets scheduled on one or more RBGs and one or more time slots.

[0241] In this example, the gNB can transmit downlink control information, including downlink assignment, to a radio device via one or more PDCCHs. Downlink assignment may include parameters indicating at least modulation and coding formats; resource allocation; and / or HARQ information related to the DL-SCH. In this example, resource allocation may include parameters for resource block allocation; and / or time slot allocation. In this example, the gNB can dynamically allocate resources to the radio device via a Cell-Radio Network Temporary Identifier (C-RNTI) on one or more PDCCHs. The radio device can monitor the one or more PDCCHs to find possible allocations when its downlink reception is enabled. When the one or more PDCCHs are successfully detected, the radio device can receive one or more downlink packets on one or more PDSCHs scheduled by the one or more PDCCHs.

[0242] In this example, the gNB can allocate configured scheduling (CS) resources for downlink transmission to a radio device. The gNB can transmit one or more periodic RRC messages indicating CS permission. The gNB can transmit DCI via a PDCCH addressing a configured scheduling-RNTI (CS-RNTI) that activates the CS resource. The DCI may include parameters indicating that the downlink permission is CS permission. CS permission can be implicitly reused periodically, as defined by the one or more RRC messages, until deactivated.

[0243] In this example, the gNB can transmit downlink control information, including uplink grants, to a radio device via one or more PDCCHs. Uplink grants may include parameters indicating at least modulation and coding formats; resource allocation; and / or HARQ information related to the UL-SCH. In this example, resource allocation may include parameters for resource block allocation; and / or time slot allocation. In this example, the gNB can dynamically allocate resources to the radio device via C-RNTI on one or more PDCCHs. The radio device can monitor the one or more PDCCHs to identify possible resource allocations. When the one or more PDCCHs are successfully detected, the radio device can transmit one or more uplink packets via one or more PUSCHs scheduled by the one or more PDCCHs.

[0244] In this example, the gNB can allocate CS resources to a radio device for uplink data transmission. The gNB can transmit one or more periodic RRC messages indicating CS permission. The gNB can transmit DCI via a PDCCH addressing to the CS-RNTI activating the CS resource. The DCI may include parameters indicating that the uplink permission is CS permission. CS permission can be implicitly reused periodically according to the period defined by the one or more RRC messages until deactivated.

[0245] In this example, the base station can transmit DCI / control signaling via PDCCH. The DCI can take one of several formats. The DCI may include downlink and / or uplink scheduling information (e.g., resource allocation information, HARQ-related parameters, MCS), requests for CSI (e.g., aperiodic CQI reports), requests for SRS, uplink power control commands for one or more cells, one or more timing information (e.g., TB transmit / receive timing, HARQ feedback timing, etc.), etc. In this example, the DCI may indicate uplink clearance including transmit parameters for one or more transport blocks. In this example, the DCI may indicate downlink assignment, which indicates parameters for receiving one or more transport blocks. In this example, the base station can use the DCI to initiate contention-free random access at the radio device. In this example, the base station may transmit a DCI including a Slot Format Indicator (SFI) that notifies the slot format. In this example, the base station may transmit a DCI that includes a preemptive indication notifying one or more PRBs and / or one or more OFDM symbols, where the UE may assume there is no predetermined transmission for the UE. In this example, the base station may transmit a DCI for group power control of PUCCH, PUSCH, or SRS. In this example, the DCI may correspond to an RNTI. In this example, the radio device may acquire an RNTI (e.g., C-RNTI) in response to completion of initial access. In this example, the base station may configure an RNTI for the radio (e.g., CS-RNTI, TPC-CS-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI, TPC-SRS-RNTI). In this example, the radio device may calculate an RNTI (e.g., the radio device may calculate an RA-RNTI based on resources used for transmitting preambles). In this example, the RNTI may have a pre-configured value (e.g., P-RNTI or SI-RNTI). In this example, the radio device may monitor a group common search space, which may be used by the base station to transmit a predetermined DCI for a group of UEs. In this example, a group common DCI can correspond to an RNTI configured for a group of UEs. In this example, the radio device can monitor a UE-specific search space. In this example, a UE-specific DCI can correspond to an RNTI configured for the radio device.

[0246] The NR system can support single-beam operation and / or multi-beam operation. In multi-beam operation, the base station can perform downlink beam sweeping to provide coverage for a common control channel and / or downlink SS block that may include at least a PSS, SSS, and / or PBCH. The radio device can use one or more RSs to measure the quality of the beamp-link. One or more SS blocks, or one or more CSI-RS resources associated with a CSI-RS Resource Index (CRI), or one or more DM-RSs of the PBCH can be used as RSs for measuring the quality of the beamp-link. The quality of the beamp-link can 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 the RS resource. The base station can indicate whether the RS resource used to measure the quality of the beamp-link is quasi-co-located (QCL) with the DM-RS of the control channel. The RS resource and DM-RS of the control channel can be referred to as QCL when the channel characteristics of the transmissions from the RS to the radio device and the transmissions from the control channel to the radio device are similar or identical under the configured criteria. In multi-beam operation, a wireless device can perform uplink beam sweep to access a cell.

[0247] In this example, a radio device can be configured to simultaneously monitor one or more beamp-pair links for PDCCH, depending on its capabilities. This increases robustness against beamp-pair link blocking. The base station can transmit one or more messages to configure the radio device to monitor one or more beamp-pair links for PDCCH in different PDCCH OFDM symbols. For example, the base station can transmit higher-layer signaling (e.g., RRC signaling) or MAC CE, which includes parameters regarding the Rx beam settings of the radio device used to monitor one or more beamp-pair links for PDCCH. The base station can transmit an indication of the spatial QCL assumption between one or more DL RS antenna ports (e.g., cell-specific CSI-RS, or radio device-specific CSI-RS, or SS block, or PBCH with or without DM-RS) and one or more DL RS antenna ports used for demodulating the DL control channel. Signaling for beam indication of the PDCCH can be MAC CE signaling, or RRC signaling, or DCI signaling, or canonical transparent and / or implicit methods, and combinations of these signaling methods.

[0248] For unicast DL data channel reception, the base station may indicate spatial QCL parameters between one or more DL RS antenna ports and one or more DM-RS antenna ports of the DL data channel. The base station may transmit a DCI (e.g., downlink clearance) including information indicating one or more RS antenna ports. This information may indicate one or more RS antenna ports that can be QCLed with one or more DM-RS antenna ports. Different sets of one or more DM-RS antenna ports used for the DL data channel may be indicated as different sets of QCLs with one or more RS antenna ports.

[0249] Figure 9A This is an example of beam sweeping in a DL channel. In the RRC_INACTIVE or RRC_IDLE state, the radio device may assume that SS blocks form SS bursts 940 and SS burst sets 950. SS burst sets 950 may have a given periodicity. For example, in multi-beam operation, base station 120 may transmit SS blocks in multiple beams, thus forming SS burst 940 together. One or more SS blocks may be transmitted on one beam. If multiple SS bursts 940 are transmitted with multiple beams, then the SS bursts together can form SS burst sets 950.

[0250] In multi-beam operation, a wireless device may additionally use CSI-RS to estimate the beam quality of the link between the wireless device and the base station. The beam can be associated with the CSI-RS. For example, the wireless device may use a beam index associated with the RSRP value of a beam, as indicated in the CRI for downlink beam selection, based on an RSRP measurement report on the CSI-RS. The CSI-RS may be transmitted on a CSI-RS resource comprising at least one of one or more antenna ports and one or more time or frequency radio resources. The CSI-RS resource may be configured in a cell-specific manner by common RRC signaling or in a wireless device-specific manner by dedicated RRC signaling and / or L1 / L2 signaling. Multiple wireless devices covered by a cell may measure cell-specific CSI-RS resources. A dedicated subset of wireless devices covered by a cell may measure wireless device-specific CSI-RS resources.

[0251] CSI-RS resources can be transmitted periodically or using non-periodic transmission or multiple or semi-continuous transmission. For example, in Figure 9A In periodic transmission, base station 120 can periodically transmit configured CSI-RS resources 940 in the time domain using the configured periodicity. In non-periodic transmission, the configured CSI-RS resources can be transmitted in dedicated time slots. In multi-transmission or semi-continuous transmission, the configured CSI-RS resources can be transmitted within a configured period. The beam used for CSI-RS transmission can have a different beamwidth than the beam used for SS block transmission.

[0252] Figure 9B This is an example of a beam management procedure in a novel radio network. Base station 120 and / or wireless device 110 can execute downlink L1 / L2 beam management procedures. One or more of the following downlink L1 / L2 beam management procedures can be executed within one or more wireless devices 110 and one or more base stations 120. In this example, P-1 procedure 910 can be used to enable wireless device 110 to measure one or more transmit (Tx) beams associated with base station 120 to support the selection of a first set of Tx beams associated with base station 120 and a first set of Rx beams associated with wireless device 110. For beamforming at base station 120, base station 120 can sweep a different set of TX beams. For beamforming at wireless device 110, wireless device 110 can sweep a different set of Rx beams. In this example, P-2 procedure 920 can be used to enable wireless device 110 to measure one or more Tx beams associated with base station 120, possibly changing the first set of Tx beams associated with base station 120. Compared to P-1 procedure 910, P-2 procedure 920 can be performed on a potentially smaller set of beams for beam optimization. P-2 procedure 920 can be a special case of P-1 procedure 910. In an example, P-3 procedure 930 can be used to enable wireless device 110 to measure at least one Tx beam associated with base station 120 to change the first set of Rx beams associated with wireless device 110.

[0253] Wireless device 110 may transmit one or more beam management reports to base station 120. In these reports, wireless device 110 may indicate beampup quality parameters, including at least: one or more beam identifications of a subset of configured beams; RSRP; and precoding matrix indicator (PMI) / channel quality indicator (CQI) / rank indicator (RI). Based on these reports, base station 120 may transmit signals to wireless device 110 indicating that one or more beampup links are one or more serving beams. Base station 120 may use one or more serving beams to transmit PDCCH and PDSCH to wireless device 110.

[0254] In an exemplary embodiment, the novel radio network may support bandwidth adaptation (BA). In the example, the receive and / or transmit bandwidth configured by the UE employing BA may be small. For example, the receive and / or transmit bandwidth may be smaller than the bandwidth of the cell. The receive and / or transmit bandwidth can be adjustable. For example, the UE may change the receive and / or transmit bandwidth, e.g., shrinking it during low-activity periods to save power. For example, the UE may change the location of the receive and / or transmit bandwidth in the frequency domain, e.g., to increase scheduling flexibility. For example, the UE may change the subcarrier spacing, e.g., to allow different services.

[0255] In an example implementation, a subset of the total cell bandwidth may be referred to as a bandwidth portion (BWP). The base station may configure the UE to implement BA using one or more BWPs. For instance, the base station may indicate to the UE which of the one or more (configured) BWPs is the active BWP.

[0256] Figure 10 Here are three example configurations of BWPs: BWP1 (1010 and 1050), with a width of 40MHz and a subcarrier spacing of 15kHz; BWP2 (1020 and 1040), with a width of 10MHz and a subcarrier spacing of 15kHz; and BWP3 (1030), with a width of 20MHz and a subcarrier spacing of 60kHz.

[0257] In an example, a UE configured to operate in one or more BWPs in a cell can be configured by one or more higher layers (e.g., RRC layer) of the cell to receive in the DL bandwidth using at least one parameter DL-BWP, and to transmit in the UL bandwidth using at least one parameter UL-BWP for the cell using a set of one or more BWPs (e.g., up to four BWPs).

[0258] To enable BA on a PCell, the base station can configure the UE using one or more UL and DL BWP pairs. To enable BA on a SCell (e.g., in the case of CA), the base station can configure the UE with at least one or more DL BWPs (e.g., possibly none in the UL).

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

[0260] In this example, for unpaired spectrum operation, the UE can expect the center frequency of the DL BWP to be the same as the center frequency of the UL BWP.

[0261] For example, for a DLBWP or UL BWP in a set of one or more DL BWPs or one or more UL BWPs, the base station can semi-statistically configure the UE for the cell using one or more parameters, which indicate at least one of the following: subcarrier spacing; cyclic prefix; number of consecutive PRBs; index in the set of one or more DL BWPs and / or one or more UL BWPs; link between DL BWPs and UL BWPs from a set of configured DL BWPs and UL BWPs; DCI detection to PDSCH receive timing; PDSCH receive to HARQ-ACK transmit timing value; DCI detection to PUSCH transmit timing value; offset of the first PRB of the DL bandwidth or UL bandwidth relative to the first PRB of the bandwidth, respectively.

[0262] In an example, for a DL BWP in a set of one or more DL BWPs on a PCell, the base station can configure the UE using one or more sets of control resources for at least one type of common search space and / or a UE-specific search space. For instance, the base station cannot configure the UE on a PCell or PSCell where there is no common search space in an active DL BWP.

[0263] For one or more UL BWPs in a set, the base station can use one or more resource sets for one or more PUCCH transmissions to configure the UE.

[0264] In this example, if the DCI includes a BWP indicator field, then the BWP indicator field value can indicate the active DL BWP for one or more DL receivers from a configured DL BWP set. If the DCI includes a BWP indicator field, then the BWP indicator field value can indicate the active UL BWP for one or more UL transmitters from a configured UL BWP set.

[0265] In this example, for PCell, the base station can semi-statistically configure the UE using the default DL BWP from the configured DL BWPs. If no default DL BWP is provided to the UE, then the default BWP can be the initial active DL BWP.

[0266] In this example, the base station can use a timer value from the PCell to configure the UE. For instance, when the UE detects a DCI indicating that an active DL BWP other than the default DL BWP is used for paired spectrum operation, or when the UE detects a DCI indicating that an active DL BWP or UL BWP other than the default DL BWP is used for unpaired spectrum operation, the UE can start a timer called the BWP inactivity timer. If the UE does not detect a DCI during the interval for paired spectrum operation or unpaired spectrum operation, the UE can increment the timer by a first value interval (e.g., the first value could be 1 millisecond or 0.5 milliseconds). In this example, the timer can expire when the timer equals the timer value. When the timer expires, the UE can switch from the active DL BWP to the default DL BWP.

[0267] In an example, the base station may semi-statistically configure the UE using one or more BWPs. The UE may switch the active BWP from the first BWP to the second BWP (e.g., the second BWP could be the default BWP) in response to receiving a DCI indicating that the second BWP is the active BWP and / or in response to the expiration of a BWP inactivity timer. For example, Figure 10 This is an example diagram of three configured BWPs: BWP1 (1010 and 1050), BWP2 (1020 and 1040), and BWP3 (1030). BWP2 (1020 and 1040) can be the default BWP. BWP1 (1010) can be the initial active BWP. In this example, the UE can switch the active BWP from BWP1 1010 to BWP2 1020 in response to the expiration of a BWP inactivity timer. For instance, the UE can switch the active BWP from BWP2 1020 to BWP3 1030 in response to receiving a DCI indicating BWP3 1030 as the active BWP. Switching the active BWP from BWP3 1030 to BWP2 1040 and / or from BWP2 1040 to BWP1 1050 can be in response to receiving a DCI indicating the active BWP and / or in response to the expiration of a BWP inactivity timer.

[0268] In this example, if the UE is configured for the secondary cell using the default DL BWP and timer values ​​in the configured DL BWP, then the UE program on the secondary cell can be the same as the UE program on the primary cell using the timer values ​​and default DL BWP for the secondary cell.

[0269] In the example, if the base station configures the UE using the first active DL BWP and the first active UL BWP on the secondary cell or carrier, then the UE can use the DL BWP and the indicated UL BWP on the secondary cell as the corresponding first active DL BWP and first active UL BWP on the secondary cell or carrier.

[0270] Figure 11A and Figure 11B The diagram illustrates packet flows employing multiple connectivity (e.g., dual connectivity, multiple connectivity, tight interconnection, etc.). Figure 11A This is an example diagram of the protocol structure of a wireless device 110 (e.g., UE) with CA and / or multiple connectivity according to an embodiment. Figure 11B This is an example diagram of a protocol structure for multiple base stations with CA and / or multiple connectivity according to an embodiment. The multiple base stations may include a master node MN 1130 (e.g., master node, master base station, master gNB, master eNB, etc.) and a secondary node SN 1150 (e.g., secondary node, secondary base station, secondary gNB, secondary eNB, etc.). The master node 1130 and the secondary node 1150 may work together to communicate with the wireless device 110.

[0271] When multiple connectivity is configured for wireless device 110, wireless device 110, which can support multiple receive / transmit functions in RRC connected state, can be configured to utilize radio resources provided by multiple schedulers of multiple base stations. Multiple base stations can interconnect via non-ideal or ideal backhaul (e.g., Xn interface, X2 interface, etc.). The base stations involved in the multiple connectivity for a wireless device can perform at least one of two different roles: the base station can act as a primary base station or a secondary base station. In multiple connectivity, a wireless device can connect to one primary base station and one or more secondary base stations. In an example, the primary base station (e.g., MN 1130) can provide a Primary Cell Group (MCG) for the wireless device (e.g., wireless device 110), comprising a primary cell and / or one or more secondary cells. The secondary base station (e.g., SN 1150) can provide a Secondary Cell Group (SCG) for the wireless device (e.g., wireless device 110), comprising a primary secondary cell (PSCell) and / or one or more secondary cells.

[0272] In multi-connectivity, the radio protocol architecture employed by the bearer can depend on how the bearer is configured. In practice, three different types of bearer configuration options can be supported: MCG bearer, SCG bearer, and / or split bearer. A radio device can receive / transmit packets of an MCG bearer via one or more cells of an MCG, and / or can receive / transmit packets of an SCG bearer via one or more cells of an SCG. Multi-connectivity can also be described as having at least one bearer configured to use radio resources provided by a secondary base station. Multi-connectivity can be configured / implemented in some example embodiments, or it can be left unconfigured / unimplemented.

[0273] In an example, a wireless device (e.g., wireless device 110) may: transmit and / or receive packets carrying MCG bearers 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); transmit and / or receive packets carrying split bearers via an SDAP layer (e.g., SDAP 1110), a PDCP layer (e.g., NR PDCP 1112), one of a primary or secondary RLC layer (e.g., MN RLC 1115, SN RLC 1116), and one of a primary or secondary MAC layer (e.g., MN MAC 1118, SN MAC 1119); and / or transmit and / or receive packets carrying split bearers 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); and / or transmit and / or receive packets carrying split bearers 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). 1119) to transmit and / or receive packets carried by SCG.

[0274] In this example, the primary base station (e.g., MN 1130) and / or the secondary base station (e.g., SN 1150) can: transmit / receive packets carried by the MCG via the primary or secondary node SDAP layer (e.g., SDAP 1120, SDAP 1140), the primary or secondary node PDCP layer (e.g., NR PDCP1121, NRPDCP 1142), the primary node RLC layer (e.g., MN RLC 1124, MN RLC 1125), and the primary node MAC layer (e.g., MN MAC1128); and transmit / receive packets carried by the MCG via the primary or secondary node SDAP layer (e.g., SDAP 1120, SDAP 1140), the primary or secondary node PDCP layer (e.g., NR PDCP 1122, NR PDCP 1143), the secondary node RLC layer (e.g., SN RLC 1146, SNRLC 1147), and the secondary node MAC layer (e.g., SN MAC1128). 1148) Transmit / receive packets carried by SCG; transmit / receive packets carried by split bearers via the primary or secondary node SDAP layer (e.g., SDAP 1120, SDAP 1140), primary or secondary node PDCP layer (e.g., NR PDCP 1123, NR PDCP 1141), primary or secondary node RLC layer (e.g., MN RLC 1126, SN RLC 1144, SN RLC 1145, MN RLC 1127) and primary or secondary node MAC layer (e.g., MN MAC 1128, SN MAC 1148).

[0275] In multi-connectivity, a radio device can be configured with multiple MAC entities: one MAC entity for the primary base station (e.g., MN MAC 1118), and other MAC entities for the secondary base station (e.g., SN MAC 1119). In multi-connectivity, the set of serving cells for the configuration of the radio device can include two subsets: the MCG comprising the serving cells of the primary base station, and the SCG comprising the serving cells of the secondary base station. For an SCG, one or more of the following configurations can be applied: at least one cell of the SCG has a configured UL CC, and at least one cell of the SCG, referred to as the primary and secondary cells (PSCell, SCG's PCell, or sometimes simply PCell), is configured with PUCCH resources; when configuring an SCG, at least one SCG bearer or one split bearer can exist; after a physical layer problem or random access problem is detected on the PSCell, or after several NR RLC retransmissions associated with the SCG have been reached, or after an access problem is detected on the PSCell during SCG addition or change: the RRC connection reconstruction procedure cannot be triggered, UL transmission to the SCG cell can be stopped, the primary base station can be notified of the SCG fault type by the radio device, and for the split bearer, DL data transmission on the primary base station can be maintained; NR can be configured for the split bearer. RLC acknowledged mode (AM) bearer; PCell and / or PSCell may be inactive; PSCell can be changed using SCG change procedures (e.g., using security key change and RACH procedures); and / or may or may not support bearer type changes between split bearer and SCG bearer, or simultaneous configuration of SCG and split bearer.

[0276] Regarding the interaction between the primary and secondary base stations for multi-connectivity, one or more of the following can be applied: the primary and / or secondary base stations can maintain the RRM measurement configuration of the radio device; the primary base station can (e.g., based on received measurement reports, service conditions, and / or bearer type) decide to request the secondary base station to provide additional resources (e.g., serving cell) for the radio device; upon receiving a request from the primary base station, the secondary base station can create / modify a container that can result in configuring an additional serving cell for the radio device (or determine that the secondary base station does not have available resources to do so); for UE capability coordination, the primary base station can provide (partial) AS configuration and UE capabilities to the secondary base station; the primary and secondary base stations can communicate via... The RRC container (Inter-Node Message) carried by the Xn message is used to exchange information about the UE configuration; the secondary base station can initiate the reconfiguration of its existing serving cell (e.g., PUCCH toward the secondary base station); the secondary base station can determine which cell is the PSCell within the SCG; the primary base station can change or not change the content of the RRC configuration provided by the secondary base station; in the case of SCG addition and / or SCGSCell addition, the primary base station can provide the most recent (or latest) measurement results for one or more SCG cells; the primary and secondary base stations can receive SFN and / or subframe offset information from each other from OAM and / or via the Xn interface (e.g., for the purpose of DRX alignment and / or identification of measurement gaps). In the example, when a new SCG SCell is added, dedicated RRC signaling can be used to send the system information required for the CA cell, excluding the SFN obtained from the MIB of the SCG's PSCell.

[0277] Figure 12 This is an exemplary diagram of a random access procedure. One or more events can trigger a random access procedure. For example, one or more events can be at least one of the following: initial access from RRC_IDLE, RRC connection reconstruction procedure, handover, arrival of DL or UL data during RRC_CONNECTED when the UL synchronization state is asynchronous, transition from RRC_Inactive, and / or a request for other system information. For example, a PDCCH command, MAC entity, and / or beam fault indication can initiate a random access procedure.

[0278] In exemplary embodiments, the random access procedure can 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 include one or more Msg 11220 transmissions, one or more Msg2 1230 transmissions, one or more Msg3 1240 transmissions, and a contention resolution mechanism 1250. For example, a contention-free random access procedure may include one or more Msg 1 1220 transmissions and one or more Msg2 1230 transmissions.

[0279] In this example, the base station may transmit (e.g., unicast, multicast, or broadcast) RACH configuration 1210 to the UE via one or more beams. RACH configuration 1210 may include one or more parameters indicating at least one of the following: an available set of PRACH resources for transmitting random access preambles, an initial preamble power (e.g., initial receive target power for random access preambles), an RSRP threshold for selecting SS blocks and corresponding PRACH resources, a power ramp factor (e.g., random access preamble power ramp step size), a random access preamble index, a maximum number of preamble transmissions, preamble groups A and B, a threshold for determining random access preamble groups (e.g., message size), a set of one or more random access preambles and corresponding PRACH resources (if any) for system information requests, a set of one or more random access preambles and corresponding PRACH resources (if any) for beam fault recovery requests, a time window for monitoring RA responses, a time window for monitoring responses to beam fault recovery requests, and / or a contention resolution timer.

[0280] In this example, Msg1 1220 can be one or more transmissions of random access preambles. For a contention-based random access procedure, the UE can select an SS block whose RSRP is higher than the RSRP threshold. If a random access preamble group B exists, the UE can select one or more random access preambles from group A or group B based on the potential Msg3 1240 size. If no random access preamble group B exists, the UE can select one or more random access preambles from group A. The UE can randomly select a random access preamble index from one or more random access preambles associated with a selected group (e.g., with equal probability or a normal distribution). If the base station semi-statistically configures the UE using the association between random access preambles and SS blocks, the UE can randomly select a random access preamble index from one or more random access preambles associated with a selected SS block and a selected group with equal probability.

[0281] For example, a UE can initiate a contention-free random access procedure based on a beam fault indication from a lower layer. For example, a base station can semi-statistically configure the UE using one or more contention-free PRACH resources for a beam fault recovery request associated with at least one of the SS blocks and / or CSI-RS. If at least one of the SS blocks with an RSRP higher than a first RSRP threshold or at least one of the CSI-RS with an RSRP higher than a second RSRP threshold is available, then the UE can select a random access preamble index corresponding to the selected SS block or CSI-RS from a set of one or more random access preambles used for the beam fault recovery request.

[0282] For example, the UE can receive a random access preamble index from the base station via PDCCH or RRC for use in a contention-free random access procedure. If the base station does not configure the UE using at least one contention-free PRACH resource associated with an SS block or CSI-RS, the UE can select a random access preamble index. If the base station configures the UE using one or more contention-free PRACH resources associated with an SS block, and at least one SS block with an RSRP higher than a first RSRP threshold is available among the associated SS blocks, the UE can select the at least one SS block and select the random access preamble corresponding to the at least one SS block. If the base station configures the UE using one or more contention-free PRACH resources associated with a CSI-RS, and at least one CSI-RS with an RSRP higher than a second RSPR threshold is available among the associated CSI-RS, the UE can select the at least one CSI-RS and select the random access preamble corresponding to the at least one CSI-RS.

[0283] A UE can perform one or more Msg1 1220 transmissions by transmitting a selected random access preamble. For example, if the UE selects an SS block and configures one or more PRACH timings associated with one or more SS blocks, then the UE can determine a PRACH timing from one or more PRACH timings corresponding to the selected SS block. Similarly, if the UE selects a CSI-RS and configures one or more PRACH timings associated with one or more CSI-RSs, then the UE can determine a PRACH timing from one or more PRACH timings corresponding to the selected CSI-RS. The UE can transmit the selected random access preamble to the base station via the selected PRACH timing. The UE can determine the transmit power for transmitting the selected random access preamble based at least on the initial preamble power and power ramp factor. The UE can determine the RA-RNTI associated with the selected PRACH timing in which the selected random access preamble is transmitted. For example, the UE may not determine the RA-RNTI for a beam fault recovery request. The UE can determine the RA-RNTI based at least on the index of the first OFDM symbol and the index of the first time slot for the selected PRACH timing and / or the uplink carrier index for the transmission of Msg1 1220.

[0284] In this example, the UE can receive a random access response Msg 2 1230 from the base station. The UE can initiate a time window (e.g., ra-ResponseWindow) to monitor the random access response. For beam fault recovery requests, the base station can configure the UE to monitor responses to beam fault recovery requests using different time windows (e.g., bfr-ResponseWindow). For example, the UE can initiate a time window (e.g., ra-ResponseWindow or bfr-ResponseWindow) at the start of a first PDCCH timing after a fixed duration following one or more symbols from the end of the preamble transmission. If the UE transmits multiple preambles, the UE can initiate a time window at the start of a first PDCCH timing after a fixed duration following one or more symbols from the end of the first preamble transmission. The UE can monitor the cell's PDCCH for at least one random access response identified by the RA-RNTI or for at least one response to a beam fault recovery request identified by the C-RNTI during the time window's timer operation.

[0285] In this example, if at least one random access response includes a random access preamble identifier corresponding to a random access preamble transmitted by the UE, then the UE can consider the reception of the random access response to be successful. If the random access response is successfully received, then the UE can consider the contention-free random access procedure to have been successfully completed. If a contention-free random access procedure for a beam fault recovery request is triggered, then if the PDCCH transmission is addressed to the C-RNTI, the UE can consider the contention-free random access procedure to have been successfully completed. In this example, if at least one random access response includes a random access preamble identifier, then the UE can consider the random access procedure to have been successfully completed and can instruct the UE to receive acknowledgment of the system information request to the upper layer. If the UE has transmitted multiple preambles, then the UE can stop transmitting the remaining preambles (if any) in response to successfully receiving the corresponding random access response.

[0286] In an example, the UE may perform one or more Msg 3 1240 transmissions in response to successful reception of a random access response (e.g., for a contention-based random access procedure). The UE may adjust the uplink transmission timing based on a timing advance command indicated by the random access response, and may transmit one or more transport blocks based on an uplink clearance indicated by the random access response. The subcarrier spacing for the PUSCH transmission of Msg 3 1240 may be provided by at least one higher-layer (e.g., RRC) parameter. The UE may transmit a random access preamble via PRACH and Msg 3 1240 via PUSCH on the same cell. The base station may indicate the UL BWP for the PUSCH transmission of Msg 3 1240 via a system information block. The UE may use HARQ to retransmit Msg 3 1240.

[0287] In this example, multiple UEs can execute Msg 1 1220 by transmitting the same preamble to the base station and receiving the same random access response from the base station, including their identity (e.g., TC-RNTI). Contention resolution 1250 ensures that a UE does not mistakenly use the identity of another UE. For example, contention resolution 1250 can resolve identity contention based on the C-RNTI on the PDCCH or the UE contention on the DL-SCH. For example, if the base station assigns a C-RNTI to a UE, then the UE can execute contention resolution 1250 based on the reception of a PDCCH transmission addressing the C-RNTI. In response to the detection of a C-RNTI on the PDCCH, the UE can consider contention resolution 1250 successful and can consider the random access procedure successfully completed. If the UE does not have a valid C-RNTI, then contention resolution can be addressed by using the TC-RNTI. For example, if the MAC PDU is successfully decoded and the MAC PDU includes a UE contention resolution identity MAC CE that matches the CCCH SDU transmitted in Msg3 1250, then the UE can consider contention resolution 1250 to be successful and the random access procedure to be successfully completed.

[0288] Figure 13 This is an example structure of a MAC entity according to an embodiment. In this example, the wireless device can be configured to operate in a multi-connectivity mode. A wireless device in an RRC_CONNECTED with multiple RX / TX connections can be configured to utilize radio resources provided by multiple schedulers located in multiple base stations. The multiple base stations can be connected via non-ideal or ideal backhaul links on the Xn interface. In this example, a base station in the multiple base stations can act as a primary base station or a secondary base station. The wireless device can connect to one primary base station and one or more secondary base stations. The wireless device can be configured with multiple MAC entities, for example, one MAC entity for the primary base station and one or more other MAC entities for one or more secondary base stations. In this example, the serving cell set for the configuration of the wireless device can include two subsets: an MCG, which includes the serving cells of the primary base station; and one or more SCGs, which include the serving cells of one or more secondary base stations. Figure 13 This shows an instance structure of the MAC entity when the MCG and SCG are configured for a wireless device.

[0289] In this example, at least one cell in an SCG can have a configured UL CC, where the cell of at least one cell can be referred to as a PSCell or the PCell of the SCG, or sometimes simply as PCell. The PSCell can be configured with PUCCH resources. In this example, when configuring an SCG, there can be at least one SCG bearer or one split bearer. In this example, after a physical layer problem or random access problem is detected on the PSCell, or after reaching the RLC retransmission number associated with the SCG, or after an access problem is detected on the PSCell during SCG addition or change: the RRC connection re-establishment procedure cannot be triggered, UL transmission to the SCG cell can be stopped, the UE can notify the primary base station of the SCG fault type, and DL data transmission on the primary base station can be maintained.

[0290] In this example, the MAC sublayer can provide services such as data transmission and radio resource allocation to the upper layer (e.g., 1310 or 1320). The MAC sublayer can include multiple MAC entities (e.g., 1350 and 1360). The MAC sublayer can provide data transmission services on logical channels. To accommodate different types of data transmission services, various types of logical channels can be defined. Logical channels can support the transmission of specific types of information. The type of logical channel can be defined by the type of information transmitted (e.g., control or data). For example, BCCH, PCCH, CCCH, and DCCH can be control channels, and DTCH can be a traffic channel. In this example, a first MAC entity (e.g., 1310) can provide services on PCCH, BCCH, CCCH, DCCH, DTCH, and MAC control elements. In this example, a second MAC entity (e.g., 1320) can provide services on BCCH, DCCH, DTCH, and MAC control elements.

[0291] The MAC sublayer can anticipate services from the physical layer (e.g., 1330 or 1340), such as data delivery services, HARQ feedback signaling, scheduling requests, or signaling for measurements (e.g., CQI). In an example, in dual connectivity, two MAC entities can be configured for the wireless device: one for the MCG and one for the SCG. The MAC entities of the wireless device can handle multiple transport channels. In an example, the first MAC entity can handle a first transport channel, including the PCCH of the MCG, the first BCH of the MCG, one or more first DL-SCHs of the MCG, one or more first UL-SCHs of the MCG, and one or more first RACHs of the MCG. In an example, the second MAC entity can handle a second transport channel, including the second BCH of the SCG, one or more second DL-SCHs of the SCG, one or more second UL-SCHs of the SCG, and one or more second RACHs of the SCG.

[0292] In this example, if a MAC entity is configured with one or more SCells, then each MAC entity can have multiple DL-SCHs, multiple UL-SCHs, and multiple RACHs. In this example, one DL-SCH and one UL-SCH can exist on a SpCell. In this example, for an SCell, one DL-SCH, zero or one UL-SCH, and zero or one RACH can exist. DL-SCHs can support reception using different parameter sets and / or TTI durations within a MAC entity. UL-SCHs can also support transmission using different parameter sets and / or TTI durations within a MAC entity.

[0293] In an example, the MAC sublayer can support different functions, and these functions can be controlled using control elements (e.g., 1355 or 1365). Functions performed by the MAC entity can include mapping between logical channels and transport channels (e.g., in the uplink or downlink), multiplexing MAC SDUs from one or more logical channels (e.g., 1352 or 1362) onto a transport block (TB) to be delivered to the physical layer on the transport channel (e.g., in the uplink), demultiplexing MAC SDUs from a transport block (TB) delivered from the physical layer on the transport channel (e.g., 1352 or 1362) onto one or more logical channels (e.g., in the downlink), scheduling information reporting (e.g., in the uplink), error correction via HARQ in the uplink or downlink (e.g., 1363), and logical channel priority ordering in the uplink (e.g., 1351 or 1361). The MAC entity can handle random access procedures (e.g., 1354 or 1364).

[0294] Figure 14 This is an example diagram of a RAN architecture including one or more base stations. In this example, protocol stacks (e.g., RRC, SDAP, PDCP, RLC, MAC, and PHY) can be supported at the nodes. A base station (e.g., gNB 120A or 120B) can include 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 functional separation is configured). The upper protocol layer of the base station can reside in the base station CU, and the lower protocol layer can reside in the base station DU. The F1 interface connecting the base station CU and base station DU (e.g., CU-DU interface) can be ideal or non-ideal backhaul. F1-C can provide control plane connectivity via the F1 interface, and F1-U can provide user plane connectivity via the F1 interface. In this example, Xn interfaces can be configured between base station CUs.

[0295] In this example, a base station CU may include RRC functions, an SDAP layer, and a PDCP layer, while a base station DU may include an RLC layer, a MAC layer, and a PHY layer. In this example, various function splitting options between the base station CU and base station DU are possible by locating different combinations of upper-layer protocol layers (RAN functions) in the base station CU and different combinations of lower-layer protocol layers (RAN functions) in the base station DU. Function splitting supports the flexibility of moving protocol layers between the base station CU and base station DU based on service requirements and / or network environment.

[0296] In this example, function splitting options can be configured for each base station, each base station CU, each base station DU, each UE, each bearer, each slice, or at other granularities. Within each base station CU split, the base station CU can have fixed splitting options, and the base station DU can be configured to match the splitting options of the base station CU. Within each base station DU split, the base station DU can be configured with different splitting options, and the base station CU can provide different splitting options for different base station DUs. Within each UE split, the base station (base station CU and at least one base station DU) can provide different splitting options for different radio devices. Within each bearer split, different splitting options can be used for different bearers. Within each slice assembly, different splitting options can be applied to different slices.

[0297] Figure 15This is an example diagram illustrating the RRC state transitions of a wireless device. In this example, the wireless device may be in at least one of the following RRC states: RRC connected (e.g., RRC Connected 1530, RRC_Connected), RRC idle (e.g., RRC Idle 1510, RRC_Idle), and / or RRC inactive (e.g., RRC Inactive 1520, RRC_Inactive). In this example, in the RRC connected state, the wireless device may have at least one RRC connection with at least one base station (e.g., gNB and / or eNB), which may have the UE context of the wireless device. The UE context (e.g., the wireless device context) may include at least one of the following: access plane context, one or more radio link configuration parameters, bearer configuration information (e.g., data radio bearer (DRB), signaling radio bearer (SRB), logical channel, QoS flow, PDU session, etc.), security information, PHY / MAC / RLC / PDCP / SDAP layer configuration information, and / or similar configuration information for the wireless device. In one example, during the RRC idle state, the wireless device may not have an RRC connection with the base station, and the UE context of the wireless device may not be stored in the base station. In another example, during the RRC inactive state, the wireless device may not have an RRC connection with the base station. The UE context of the wireless device may be stored in the base station, which may be referred to as the anchor base station (e.g., the last serving base station).

[0298] In this example, the radio device can transition the UE RRC state between an RRC idle state and an RRC connected state in two ways (e.g., connection release 1540 or connection establishment 1550; or connection reconstruction) and / or between an RRC inactive state and an RRC connected state in two ways (e.g., connection deactivation 1570 or connection restoration 1580). In this example, the radio device can transition its RRC state from an RRC inactive state to an RRC idle state (e.g., connection release 1560).

[0299] In this example, the anchor base station can be a base station that maintains the UE context (radio device context) of the radio device at least during the time period during which the radio device remains in the RAN notification area (RNA) of the anchor base station and / or during the time period during which the radio device remains in the RRC inactive state. In this example, the anchor base station can be the base station to which the radio device in the RRC inactive state last connected in its latest RRC connection state, or the base station where the radio device last performed the RNA update procedure. In this example, the RNA can include one or more cells operated by one or more base stations. In this example, the base station can belong to one or more RNAs. In this example, the cell can belong to one or more RNAs.

[0300] In this example, the radio device can change the UE's RRC state from RRC connected state to RRC inactive state at the base station. The radio device can receive RNA information from the base station. The RNA information may include at least one of the following: RNA identifier, one or more cell identifiers of one or more cells of the RNA, base station identifier, base station IP address, radio device AS context identifier, recovery identifier, etc.

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

[0302] In this example, when a radio device in an RRC inactive state moves to a new RNA, the radio device can perform an RNA update (RNAU) procedure, which may include the radio device's random access procedure and / or UE context retrieval procedure. UE context retrieval may include: the base station receiving a random access preamble from the radio device; and the base station retrieving the radio device's UE context from the formerly anchored base station. Retrieval may include: sending a retrieve UE context request message including a recovery identifier to the formerly anchored base station, and receiving a retrieve UE context response message including the radio device's UE context from the formerly anchored base station.

[0303] In an example embodiment, a radio device in an RRC inactive state can select a cell to camp on based on measurements of at least one or more cells, cells that the radio device can monitor for RNA paging messages, and / or core network paging messages from a base station. In an example, a radio device in an RRC inactive state can select a cell to perform a random access procedure to restore RRC connectivity and / or transmit one or more packets to a base station (e.g., to the network). In an example, if the selected cell belongs to a different RNA than the RNA of the radio device in an RRC inactive state, the radio device can initiate a random access procedure to perform an RNA update procedure. In an example, if the radio device in an RRC inactive state has one or more packets in a buffer to transmit to the network, the radio device can initiate a random access procedure to transmit one or more packets to the base station of the cell selected by the radio device. A random access procedure can be performed between the radio device and the base station using two messages (e.g., level 2 random access) and / or four messages (e.g., level 4 random access).

[0304] In an example embodiment, a base station receiving one or more uplink packets from a radio device in an RRC inactive state can extract the UE context of the radio device by transmitting a UE context retrieval request message for the radio device to the anchor base station of the radio device, based on at least one of the AS context identifier, RNA identifier, base station identifier, recovery identifier, and / or cell identifier received from the radio device. In response to extracting the UE context, the base station can transmit a path handover request for the radio device to a core network entity (e.g., AMF, MME, etc.). The core network entity can update one or more downlink tunnel endpoint identifiers carried between the user plane core network entity (e.g., UPF, S-GW, etc.) and the RAN node (e.g., base station) for the radio device, for example, by changing the downlink tunnel endpoint identifier from the address of the anchor base station to the address of the base station.

[0305] A gNB can communicate with a wireless device via a wireless network employing one or more novel radio technologies. These radio technologies may include at least one of the following: multiple technologies related to the physical layer; multiple technologies related to the media access control layer; and / or multiple technologies related to the radio resource control layer. Example embodiments enhancing these radio technologies can improve the performance of the wireless network. Example embodiments can increase system throughput or data transmission rate. Example embodiments can reduce battery consumption of the wireless device. Example embodiments can improve latency for data transmission between the gNB and the wireless device. Example embodiments can improve network coverage of the wireless network. Example embodiments can improve the transmission efficiency of the wireless network.

[0306] Instance Downlink Control Information (DCI)

[0307] In an example, a gNB may transmit a DCI via PDCCH for at least one of the following: scheduling assignment / grant; slot format notification; preemption indication; and / or power control command. More specifically, a DCI may include at least one of the following: an identifier for the DCI format; downlink scheduling assignment; uplink scheduling grant; slot format indicator; preemption indication; power control for PUCCH / PUSCH; and / or power control for SRS.

[0308] In an example, downlink scheduling assignment (DCI) may include parameters indicating at least one of the following: an identifier for the DCI format; a PDSCH resource indication; a transmission format; HARQ information; control information regarding multiple antenna schemes; and / or commands for power control of the PUCCH.

[0309] In an example, the uplink scheduling permission DCI may include parameters indicating at least one of the following: an identifier for the DCI format; a PUSCH resource indication; a transport format; HARQ related information; and / or a PUSCH power control command.

[0310] In practice, different types of control information can correspond to different DCI message sizes. For example, supporting multiple beams and / or spatial multiplexing in the spatial domain and discontinuous allocation of RBs in the frequency domain may require a larger scheduling message than uplink permission taking into account frequency adjacency allocation. DCIs can be classified into different DCI formats, where the format corresponds to a certain message size and / or purpose.

[0311] In one example, the wireless device can monitor one or more PDCCHs for detecting one or more DCIs having one or more DCI formats in a common search space or a wireless device-specific search space. In another example, the wireless device can monitor PDCCHs with a limited set of DCI formats to conserve power. The more DCI formats to be detected, the more power is consumed at the wireless device.

[0312] In this example, the information in the DCI format used for downlink scheduling may include at least one of the following: a DCI format identifier; a carrier indicator; frequency domain resource allocation; time domain resource allocation; a bandwidth portion indicator; the number of HARQ processes; one or more MCSs; one or more NDIs; one or more RVs; MIMO-related information; a downlink assignment index (DAI); a PUCCH resource indicator; a PDSCH-to-HARQ_feedback timing indicator; a TPC for the PUCCH; an SRS request; and padding (if necessary). In this example, MIMO-related information may include at least one of the following: PMI; precoding information; a transport block switching flag; a power offset between the PDSCH and the reference signal; a reference signal scrambling sequence; the number of layers; and / or antenna ports used for transmission; and / or a transmit configuration indicator (TCI).

[0313] In an example, the information in the DCI format used for uplink scheduling may include at least one of the following: an identifier for the DCI format; a carrier indicator; a bandwidth portion indicator; a resource allocation type; a frequency domain resource assignment; a time domain resource assignment; an MCS; an NDI; a phase rotation of the uplink DMRS; precoding information; a CSI request; an SRS request; an uplink index / DAI; a TPC for PUSCH; and / or padding (if necessary).

[0314] In this example, the gNB can perform CRC scrambling for the DCI before transmitting it via the PDCCH. The gNB can perform CRC scrambling by adding multiple bits of at least one radio device identifier (e.g., C-RNTI, CS-RNTI, TPC-CS-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI, SP CSI C-RNTI, or TPC-SRS-RNTI) to the CRC bits of the DCI in binary form. When detecting the DCI, the radio device can check the CRC bits of the DCI. When the CRC is scrambled with the same bit sequence as at least one radio device identifier, the radio device can receive the DCI.

[0315] In this example, to support wide-bandwidth operation, the gNB can transmit one or more PDCCHs from different control resource sets (core sets). The gNB can transmit one or more RRC messages that include configuration parameters for one or more core sets. A core set may include at least one of the following: a first OFDM symbol; several consecutive OFDM symbols; a set of resource blocks; a CCE-to-REG mapping. In this example, the gNB may transmit PDCCHs from a sub-dedicated core set for a specific purpose (e.g., for beam fault recovery confirmation).

[0316] In one example, the wireless device can monitor the PDCCH used to detect one or more DCIs in a configured core set to reduce power consumption.

[0317] Example MAC PDU structure.

[0318] A gNB can transmit one or more MAC PDUs to a wireless device. In the example, the MAC PDU can be a bit string of length byte alignment (e.g., a multiple of eight bits). In the example, the bit string can be represented by a table, where the most significant bit is the leftmost bit of the first row of the table, and the least significant bit is the rightmost bit of the last row of the table. More generally, the bit string can be read from left to right, then in row-by-row order. In this example, the bit order of the parameter fields within the MAC PDU is represented by the first and most significant bits in the leftmost position and the last and least significant bits in the rightmost position.

[0319] In the example, the MAC SDU can be a bit string whose length is byte-aligned (e.g., a multiple of eight bits). In the example, the MAC SDU can be included in the MAC PDU starting from the first bit.

[0320] In the example, MAC CE can be a bit string whose length is byte-aligned (e.g., a multiple of eight bits).

[0321] In the example, the MAC subheader can be a bit string whose length is byte-aligned (e.g., a multiple of eight bits). In the example, the MAC subheader can be placed directly before the corresponding MAC SDU or MAC CE, or before padding.

[0322] In this instance, the MAC entity can ignore the values ​​of the reserved bits in the DL MAC PDU.

[0323] In the example, a MAC PDU may include one or more MAC sub-PDUs. A MAC sub-PDU within one or more MAC sub-PDUs may include at least one of the following: a MAC sub-header only (containing padding); a MAC sub-header and a MAC SDU; a MAC sub-header and a MAC CE; and / or a MAC sub-header and padding. In the example, the MAC SDU may be variable-sized. In the example, the MAC sub-header may correspond to a MAC SDU or a MAC CE or padding.

[0324] In the example, the MAC subheader may include: an R field with a length of one bit; an F field with a length of one bit; an LCID field with a length of multiple bits; and an L field with a length of multiple bits when the MAC subheader corresponds to a MAC SDU or a variable-size MAC CE or padding.

[0325] In one example, the MAC subheader may include an eight-bit L field. In another example, the LCID field may be six bits long, while the L field may be eight bits long. In yet another example, the MAC subheader may include a sixteen-bit L field. In yet another example, the LCID field may be six bits long, while the L field may be sixteen bits long.

[0326] In the example, the MAC subheader may include: an R field of two bits; and an LCID field of multiple bits when the MAC subheader corresponds to a fixed-size MAC CE or padding. In the example, the LCID field can be six bits long, while the R field can be two bits long.

[0327] In the example DL MAC PDU, multiple MAC CEs can be placed together. A MAC sub-PDU including a MAC CE can be placed before any MAC sub-PDU including a MAC SDU or before a MAC sub-PDU including a filler.

[0328] In the example UL MAC PDU, multiple MAC CEs can be placed together. A MAC sub-PDU including a MAC CE can be placed after all MAC sub-PDUs including the MAC SDU. A MAC sub-PDU can be placed before any MAC sub-PDUs including any filler MAC sub-PDUs.

[0329] In the example, the MAC entity of the gNB can transmit one or more MAC CEs to the MAC entity of the radio device. In the example, multiple LCIDs can be associated with one or more MAC CEs. In the example, one or more MAC CEs can include at least one of the following: SP ZP CSI-RS resource set activation / deactivation MAC CE; PUCCH spatial relationship activation / deactivation MAC CE; SP SRS activation / deactivation MAC CE; SP CSI report on PUCCH activation / deactivation MAC CE; TCI status indication of UE-specific PDCCH MAC CE; TCI status indication of UE-specific PDSCH MAC CE; non-periodic CSI triggered state sub-selection MAC CE; SP CSI-RS / CSI-IM resource set activation / deactivation MAC CE; UE contention resolution identification MAC CE; timing advance command MAC CE; DRX command MAC CE; long DRX command MAC CE; SCell activation / deactivation MAC CE (1 octet); SCell activation / deactivation MAC CE (4 octets); and / or copy activation / deactivation MAC CE. In the example, a MAC CE may have an LCID in its corresponding MAC subheader. Different MAC CEs may have different LCIDs in their corresponding MAC subheaders. For example, an LCID of 111011 in a MAC subheader may indicate that the MAC CE associated with the MAC subheader is a long DRX command MAC CE.

[0330] In this example, the MAC entity of the wireless device may transmit one or more MAC CEs to the MAC entity of the gNB. In this example, the one or more MAC CEs may include at least one of the following: a Short Buffer Status Report (BSR) MAC CE; a Long BSR MAC CE; a C-RNTI MAC CE; a Configured Grant Acknowledgment MAC CE; a Single-Entry PHR MAC CE; a Multi-Entry PHR MAC CE; a Truncated BSR; and / or a Truncated Long BSR. In this example, the MAC CE may have an LCID in its corresponding MAC subheader. Different MAC CEs may have different LCIDs in their corresponding MAC subheaders. For example, an LCID of 111011 in a MAC subheader may indicate that the MAC CE associated with that MAC subheader is a Truncated Command MAC CE.

[0331] Examples of carrier aggregation

[0332] In carrier aggregation (CA), two or more component carriers (CCs) can be aggregated. A wireless device can simultaneously receive or transmit on one or more CCs, depending on its capabilities. In the example, CA can be supported for consecutive CCs. In the example, CA can be supported for non-consecutive CCs.

[0333] When CA is configured, the radio device can have an RRC connection to the network. During RRC connection establishment / re-establishment / handover, the cell providing NAS mobility information can be the serving cell. During the RRC connection re-establishment / handover procedure, the cell providing security input can be the serving cell. In the example, the serving cell can be referred to as the primary cell (PCell). In the example, the gNB can, depending on the radio device's capabilities, transmit one or more messages to the radio device including configuration parameters for one or more secondary cells (SCells).

[0334] When CA is configured, the base station and / or wireless device can use the SCell activation / deactivation mechanism to effectively consume battery power. When a wireless device is configured with one or more SCells, the gNB can activate or deactivate at least one of the one or more SCells. After configuring an SCell, it can be deactivated.

[0335] In an example, the wireless device can activate / deactivate the SCell in response to receiving a SCell activation / deactivation MAC CE.

[0336] In the example, the base station may transmit one or more messages to the wireless device, including the sCellDeactivationTimer timer. In the example, the wireless device may deactivate the SCell in response to the expiration of the sCellDeactivationTimer timer.

[0337] When a wireless device receives a SCell activation / deactivation MAC CE to activate a SCell, the wireless device can activate the SCell. In response to SCell activation, the wireless device can perform the following operations: SRS transmission on the SCell; CQI / PMI / RI / CRI reporting on the SCell on the PCell; PDCCH monitoring on the SCell; PDCCH monitoring on the SCell on the PCell; and / or PUCCH transmission on the SCell.

[0338] In the example, in response to SCell activation, the wireless device can start or restart the sCellDeactivationTimer associated with the SCell. The wireless device can start or restart the sCellDeactivationTimer in a time slot when an SCell activation / deactivation MAC CE has been received. In the example, in response to SCell activation, the wireless device can (re)initialize one or more suspended configured uplink licenses of configured license type 1 associated with the SCell according to the stored configuration. In the example, in response to SCell activation, the wireless device can trigger a PHR.

[0339] In the example, when the wireless device receives a SCell activation / deactivation MAC CE to deactivate the activated SCell, the wireless device can deactivate the activated SCell.

[0340] In the example, when the sCellDeactivationTimer associated with the active SCell expires, the wireless device can deactivate the active SCell. In response to deactivating the active SCell, the wireless device can stop the first SCell timer associated with the active SCell. In the example, in response to deactivating the active SCell, the wireless device can clear one or more configured downlink assignments and / or one or more configured uplink permission types 2 associated with the active SCell. In the example, in response to deactivating the active SCell, the wireless device can also suspend one or more configured uplink permission types 1 associated with the active SCell. The wireless device can refresh the HARQ buffer associated with the active SCell.

[0341] In the example, when the SCell is deactivated, the wireless device may not perform the following operations: transmitting SRS on the SCell; reporting the CQI / PMI / RI / CRI of the SCell on the PCell; transmitting on the UL-SCH on the SCell; transmitting on the RACH on the SCell; monitoring at least one first PDCCH on the SCell; monitoring at least one second PDCCH of the SCell on the PCell; and / or transmitting PUCCH on the SCell.

[0342] In the example, when at least one first PDCCH on the activated SCell indicates uplink grant or downlink assignment, the radio device can restart the sCellDeactivationTimer timer associated with the activated SCell. In the example, when at least one second PDCCH on the serving cell scheduling the activated SCell (e.g., a PCell or SCell configured with a PUCCH, i.e., a PUCCHSCell) indicates uplink grant or downlink assignment for the activated SCell, the radio device can restart the sCellDeactivationTimer timer associated with the activated SCell.

[0343] In this example, when a SCell is deactivated, if there is an ongoing random access procedure on the SCell, the wireless device can terminate the ongoing random access procedure on the SCell.

[0344] SCell Activation / Deactivation of MAC-CE Examples

[0345] An instance of a SCell activation / deactivation MAC CE may include an octet. A first MACPDU subheader with a first LCID can identify an octet of SCell activation / deactivation MAC CE. An octet of SCell activation / deactivation MAC CE may have a fixed size. An octet of SCell activation / deactivation MAC CE may include a single octet. A single octet may include a first number of C fields (e.g., seven) and a second number of R fields (e.g., one).

[0346] An instance of a SCell activation / deactivation MAC CE may include four octets. A second MACPDU subheader with a second LCID can identify the four-octet SCell activation / deactivation MAC CE. The four-octet SCell activation / deactivation MAC CE may have a fixed size. The four-octet SCell activation / deactivation MAC CE may include four octets. The four octets may include a third number of C fields (e.g., 31) and a fourth number of R fields (e.g., 1).

[0347] In the example, if an SCell with SCell index i has been configured, then C i The field can indicate the active / deactivated status of an SCell with index i. In the example, when C i When a field is set to one, the SCell with index i is activated. In the example, when C... iWhen the field is set to zero, the SCell with SCell index i can be deactivated. In this instance, if no SCell with SCell index i is configured, the wireless device can ignore C. i Fields. In the example, the R field can indicate reserved bits. The R field can be set to zero.

[0348] Examples of beam management programs

[0349] The base station can configure a radio device to have a list of one or more TCI-State configurations using the higher-layer parameter PDSCH-Config for the serving cell. The number of one or more TCI states can depend on the capabilities of the radio device. The radio device can decode the PDSCH using one or more TCI states based on the detected PDCCH with DCI. DCI can be intended for both the radio device and the serving cell of the radio device.

[0350] In an example, a TCI state configured with one or more TCI states may contain one or more parameters. The wireless device may use one or more parameters to configure a quasi-co-address relationship between one or two downlink reference signals (e.g., a first DL RS and a second DL RS) and the DM-RS port of the PDSCH. This quasi-co-address relationship may be configured by the higher-layer parameter qcl-Type1 of the first DL RS. This quasi-co-address relationship may be configured by the higher-layer parameter qcl-Type2 of the second DL RS (if already configured).

[0351] In one instance, when a wireless device configures a quasi-co-location relationship between two downlink reference signals (e.g., a first DL RS and a second DL RS), the first QCL type of the first DL RS and the second QCL type of the second DL RS may be different. In another instance, the first DL RS and the second DL RS may be the same. In yet another instance, the first DL RS and the second DL RS may be different.

[0352] In an example, the quasi-co-location type (e.g., first QCL type, second QCL type) of the DL RS (e.g., first DLRS, second DLRS) can be provided to the wireless device via the higher-layer parameter qcl-Type in QCL-Info. The higher-layer parameter QCL-Type can take at least one of the following: 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}.

[0353] In this example, the wireless device can receive an activation command. This activation command can be used to map one or more TCI states (e.g., up to eight) to one or more code points in the DCI field "Transmit Configuration Indicator (TCI)". In this example, the wireless device can transmit a HARQ-ACK corresponding to the PDSCH in time slot n. The PDSCH may include / carry the activation command. In response to transmitting a HARQ-ACK in time slot n, the wireless device can receive a HARQ-ACK from the time slot. Begin applying a mapping between one or more TCI states and one or more code points in the DCI field "Emission Configuration Indication".

[0354] In this example, after the radio device receives the initial higher-layer configuration of one or more TCI states and before receiving the activation command, the radio device may assume that one or more DM-RS ports of the serving cell's PDSCH are quasi-co-located with the SSB / PBCH block. In this example, the radio device may determine the SSB / PBCH block relative to 'QCL-Type A' during the initial access procedure. In this example, the radio device may determine the SSB / PBCH block in the initial access procedure relative to 'QCL-Type D' (where applicable).

[0355] In this example, the radio device may be configured with the higher-layer parameter TCI-PresentInDCI by the base station. When the higher-layer parameter TCI-PresentInDCI is set to 'enabled' for the control resource set (core set) for scheduling PDSCH, the radio device may assume that the TCI field exists in the DL format (e.g., DCI format 1_1) of the PDCCH transmitted on the CORESET.

[0356] In this example, the base station may not configure the core set to have the higher-layer parameter TCI-PresentInDCI. In this example, the core set may schedule PDSCH. In this example, the time offset between the reception of DCI (e.g., DCI format 1_1, DCI format 1_0) and the (corresponding) PDSCH in the core set may be equal to or greater than a threshold (e.g., Threshold-Sched-Offset). In this example, the threshold may be based on reported UE capabilities. In this example, the radio device may apply a second TCI state to the core set for PDCCH transmissions used for DCI. In this example, the radio device may apply a second QCL assumption to the core set for PDCCH transmissions used for DCI. In this example, in response to the base station not configuring the core set to have the higher-layer parameter TCI-PresentInDCI, and the time offset between the reception of DCI and PDSCH being equal to or greater than the threshold, to determine the quasi-co-addressable antenna ports of the PDSCH, the radio device may assume that the first TCI state or first QCL assumption of the PDSCH is the same as the second TCI state or second QCL assumption applied to the core set.

[0357] In this example, the base station can configure the core set to have the higher-layer parameter TCI-PresentInDCI. In this example, the higher-layer parameter TCI-PresentInDCI can be set to "Enabled". In this example, the core set can schedule PDCCHs with DCI (e.g., DCI format 1_0). In this example, the DCI may not include a TCI field. In this example, the time offset between the reception of the DCI received in the core set and the (corresponding) PDSCH can be equal to or greater than a threshold (e.g., Threshold-Sched-Offset). In this example, the threshold can be based on reported UE capabilities. In this example, the radio device can apply a second TCI state to the core set for PDCCH transmissions used for DCI. In this example, the radio device can apply a second QCL assumption to the core set for PDCCH transmissions used for DCI. In an example, in response to a base station scheduling a PDSCH with a DCI that does not include a TCI field, and the time offset between the reception of the DCI and the PDSCH is equal to or greater than a threshold, in order to determine the quasi-co-addressable antenna port of the PDSCH, the radio device may assume that the first TCI state or the first QCL assumption of the PDSCH is the same as the second TCI state or the second QCL assumption applied to the core set.

[0358] In this example, the base station can configure the core set to have the higher-layer parameter TCI-PresentInDCI. In this example, the higher-layer parameter TCI-PresentInDCI can be set to "Enabled". The radio device can receive the DCI in the core set of the scheduled component carriers. The DCI may include a TCI field. In response to the higher-layer parameter TCI-PresentInDCI being set to "Enabled", the TCI field in the DCI of the scheduled component carrier can point to one or more active TCI states in the scheduled component carrier or DL ​​BWP (e.g., after receiving an activation command).

[0359] In this example, the base station can configure the core set to have the higher-layer parameter TCI-PresentInDCI. In this example, the higher-layer parameter TCI-PresentInDCI can be set to "Enabled". The radio device can receive DCI in the core set (e.g., DCI format 1_1). In this example, the DCI can schedule the radio device's PDSCH. In this example, the TCI field can be present in the DCI. In this example, the time offset between the reception of the DCI and the (correspondingly scheduled) PDSCH can be equal to or greater than a threshold (e.g., Threshold-Sched-Offset). In this example, the threshold can be based on the reported UE capability. In this example, in response to the presence of the TCI field in the DCI scheduling the PDSCH, and the higher-layer parameter TCI-PresentInDCI being set to "Enabled" for the core set, the radio device can use the TCI state based on the detected value of the TCI field in the PDCCH with DCI to determine the antenna port quasi-co-address of the PDSCH. In an example, using the TCI state based on the TCI field value may include the radio device assuming that, when the time offset between the DCI and PDSCH reception is equal to or greater than a threshold, one or more DM-RS ports of the serving cell's PDSCH are quasi-co-located with one or more RS quasi-co-located in the TCI state relative to one or more QCL type parameters given by the TCI state. In an example, the TCI field value can indicate the TCI state.

[0360] In this example, a base station can configure a core set to have a single-slot PDSCH. In this example, a single-slot PDSCH can be scheduled within a slot. In this example, the base station can activate one or more TCI states within the slot. In response to the configuration of a single-slot PDSCH, the TCI state (e.g., indicated by the TCI field in the DCI that schedules the single-slot PDSCH) can be based on one or more active TCI states within the slot that have the scheduled single-slot PDSCH. In this example, the TCI state can be one of one or more active TCI states within the slot. In this example, the TCI field in the DCI can indicate the TCI state of one or more active TCI states within the slot.

[0361] In this example, the radio device may be configured with a core set. In this example, the core set may be associated with a search space set for cross-carrier scheduling. In this example, in response to the core set being associated with a search space set for cross-carrier scheduling, the radio device may expect the higher-layer parameter TCI-PresentInDCI to be set to 'enabled' for the core set. In this example, the base station may configure the serving cell using TCI states. In this example, the radio device may detect PDCCHs with DCIs that schedule PDSCHs within the search space set. In this example, the TCI field in the DCI may indicate at least one of one or more TCI states. In this example, at least one of one or more TCI states (scheduled by the search space set) may include / contain a QCL type (e.g., QCL-TypeD). In this example, in response to at least one of one or more TCI states scheduled by a search space set containing a QCL type, the radio device may expect the time offset between the reception of the PDCCH detected in the search space set and the (corresponding) PDSCH to be greater than or equal to a threshold (e.g., Threshold-Sched-Offset).

[0362] In this example, the base station can configure the core set to have the higher-layer parameter TCI-PresentInDCI. In this example, the higher-layer parameter TCI-PresentInDCI can be set to "Enabled". In this example, when the higher-layer parameter TCI-PresentInDCI is set to "Enabled" for the core set, the offset between the DCI reception in the core set and the PDSCH scheduled by the DCI can be less than a threshold (e.g., Threshold-Sched-Offset).

[0363] In this instance, the base station may not configure the core set with the higher-layer parameter TCI-PresentInDCI. In this instance, the radio device may be in RRC connected mode. In this instance, the radio device may be in RRC idle mode. In this instance, the radio device may be in RRC inactive mode. In this instance, when the higher-layer parameter TCI-PresentInDCI is not configured for the core set, the offset between the DCI reception in the core set and the PDSCH scheduled by the DCI may be less than a threshold (e.g., Threshold-Sched-Offset).

[0364] In one instance, the radio device can monitor one or more core sets (or one or more search spaces) within / in the active BWP (e.g., active downlink BWP) of the serving cell in one or more time slots. In one instance, monitoring one or more core sets within / in the active BWP of the serving cell in one or more time slots may include monitoring at least one core set within / in the active BWP of the serving cell in each of the one or more time slots. In one instance, the latest time slot in one or more time slots may be the most recently occurring. In one instance, the radio device can monitor one or more second core sets of one or more core sets in the latest time slot within / in the active BWP of the serving cell. In response to monitoring one or more second core sets in the latest time slot and the most recently occurring latest time slot, the radio device can determine the latest time slot. In one instance, each core set in one or more second core sets may be identified by a core set-specific index (e.g., indicated by a higher-layer CORESET-ID). In one instance, the core set-specific index of the core set of one or more secondary core sets may be the lowest among the core set-specific indices of one or more second core sets. In one instance, the radio device can monitor the search space associated with the core set in the latest time slot. In this instance, in response to the core set-specific index of the core set being the lowest and monitoring the search space associated with the core set in the latest time slot, the wireless device can select the core set of one or more secondary core sets.

[0365] In an example, when the offset between the DCI reception in the core set and the PDSCH scheduled by the DCI is less than a threshold (e.g., Threshold-Sched-Offset), the radio device may assume that one or more DM-RS ports of the serving cell's PDSCH are quasi-co-located with one or more RSs in the TCI state relative to one or more QCL type parameters. In response to the selection of a core set, one or more RSs in the TCI state can be used for PDCCH quasi-co-location indication of one or more second core sets (selected).

[0366] In this example, the radio device can receive the DCI via the PDCCH in the core set. In this example, the DCI can schedule the PDSCH. In this example, the offset between the received DCI and the PDSCH can be less than a threshold (e.g., Threshold-Sched-Offset). The first QCL type (e.g., 'QCL-TypeD') of one or more DM-RS ports of the PDSCH can be different from the second QCL type (e.g., 'QCL-TypeD') of one or more second DM-RS ports of the PDCCH. In this example, the PDSCH and PDCCH can overlap in at least one symbol. In this example, in response to the PDSCH and PDCCH overlapping in at least one symbol and the first QCL type being different from the second QCL type, the radio device can prioritize the reception of the PDCCH associated with the core set. In this example, priority prioritization can be applied to in-band CA cases (when the PDSCH and the core set are in different component carriers). In this example, prioritizing the reception of the PDCCH may include receiving the PDSCH of the second QCL type with one or more second DM-RS ports of the PDCCH. In one example, prioritizing the reception of PDCCH may include rewriting the first QCL type of one or more DM-RS ports of PDSCH with the second QCL type of one or more second DM-RS ports of PDCCH. In another example, prioritizing the reception of PDCCH may include assuming a spatial QCL (e.g., a second QCL type) on PDSCH for simultaneous reception of PDCCH and PDSCH. In yet another example, prioritizing the reception of PDCCH may include applying a spatial QCL (e.g., a second QCL type) on PDSCH for simultaneous reception of PDCCH and PDSCH.

[0367] In this example, none of the configured TCI states can contain a QCL type (e.g., "QCL-TypeD"). In response to the absence of a configured TCI state containing a QCL type, the radio device can derive additional QCL assumptions for its scheduled PDSCH from the indicated TCI state, regardless of the time offset between the DCI reception and the corresponding PDSCH.

[0368] In an example, a wireless device may use CSI-RS for at least one of the following: time / frequency tracking, CSI calculation, L1-RSRP calculation, and mobility.

[0369] In this example, a base station can configure a radio device to monitor a core set on one or more symbols. In this example, CSI-RS resources can be associated with an NZP-CSI-RS-ResourceSet. The higher-layer parameter repeat of the NZP-CSI-RS-ResourceSet can be set to "On". In this example, in response to the CSI-RS resources associated with an NZP-CSI-RS-ResourceSet whose higher-layer parameter repeat is set to "On", the radio device may not expect CSI-RS resources configured on one or more symbols.

[0370] In this example, the higher-layer parameter repetition of the NZP-CSI-RS-ResourceSet may not be set to "On". In this example, the base station may configure CSI-RS resources and one or more search space sets associated with a core set in the same one or more symbols (e.g., OFDM symbols). In this example, in response to the higher-layer parameter repetition of the NZP-CSI-RS-ResourceSet not being set to "On", and the CSI-RS resources and one or more search space sets associated with the core set being configured in the same one or more symbols, the radio device may assume that the CSI-RS of the CSI-RS resources and one or more DM-RS ports of the PDCCH are quasi-co-located with 'QCL-TypeD'. In this example, the base station may transmit PDCCH in one or more search space sets associated with the core set.

[0371] In this example, the higher-layer parameter repetition of the NZP-CSI-RS-ResourceSet may not be set to "On". In this example, the base station may configure the CSI-RS resources of the first cell and one or more search space sets associated with the core set of the second cell in the same one or more symbols (e.g., OFDM symbols). In this example, in response to the higher-layer parameter repetition of the NZP-CSI-RS-ResourceSet not being set to "On", and the CSI-RS resources and one or more search space sets associated with the core set being configured in the same one or more symbols, the radio device may assume that the CSI-RS of the CSI-RS resources and one or more DM-RS ports of the PDCCH are quasi-co-located with 'QCL-Type D'. In this example, the base station may transmit the PDCCH in one or more search space sets associated with the core set. In this example, the first cell and the second cell may be located in different in-band component carriers.

[0372] In one example, the base station may configure the radio device to have CSI-RS in the first set of PRBs. In another example, the base station may configure the radio device to have one or more search space sets associated with one or more symbols (e.g., OFDM symbols) and a core set in the second set of PRBs. In yet another example, the radio device may not expect the first and second sets of PRBs to overlap in one or more symbols.

[0373] In this example, the base station can configure a radio device to have CSI-RS resources and SS / PBCH blocks in one or more of the same (OFDM) symbols. In this example, in response to the CSI-RS resources and SS / PBCH blocks configured in the same one or more (OFDM) symbols, the radio device can assume that the CSI-RS resources and SS / PBCH blocks are quasi-co-located with QCL type (e.g., 'QCL-Type D').

[0374] In this example, the base station can configure CSI-RS resources in the first PRB for the radio device. In this example, the base station can configure SS / PBCH blocks in the second PRB for the radio device. In this example, the radio device may not expect the first and second PRBs to overlap.

[0375] In one example, the base station can configure CSI-RS resources with a first subcarrier spacing for the wireless device. In another example, the base station can configure SS / PBCH blocks with a second subcarrier spacing for the wireless device. In yet another example, the wireless device can expect the first and second subcarrier spacings to be the same.

[0376] In this example, the base station can configure a radio device to have an NZP-CSI-RS-ResourceSet. In this example, the NZP-CSI-RS-ResourceSet can be configured with higher-layer parameter repetition set to "On". In this example, in response to the NZP-CSI-RS-ResourceSet being configured with higher-layer parameter repetition set to "On", the radio device can assume that the base station transmits one or more CSI-RS resources with the same downlink spatial domain transmit filter within the NZP-CSI-RS-ResourceSet. In this example, the base station can transmit each CSI-RS resource in one or more CSI-RS resources in different symbols (e.g., OFDM symbols).

[0377] In this example, the NZP-CSI-RS-ResourceSet can be configured with higher-layer parameter repetition set to "Off". In this example, in response to the NZP-CSI-RS-ResourceSet being configured with higher-layer parameter repetition set to "Off", the wireless device may not assume that the base station transmits one or more CSI-RS resources with the same downlink spatial domain transmit filter within the NZP-CSI-RS-ResourceSet.

[0378] In this example, the base station can configure the radio device to have the higher-layer parameter `groupBasedBeamReporting`. In this example, the base station can set the higher-layer parameter `groupBasedBeamReporting` to "Enabled". In response to the higher-layer parameter `groupBasedBeamReporting` being set to "Enabled", the radio device can report at least two different resource indicators (e.g., CRI, SSBRI) in a single reporting instance for reporting settings of one or more reporting settings. In this example, the radio device can simultaneously receive at least two RSs (e.g., CSI-RS, SSB) indicated by at least two different resource indicators. In this example, the radio device can simultaneously receive at least two RSs with a single spatial domain receive filter. In this example, the radio device can simultaneously receive at least two RSs with multiple simultaneous spatial domain receive filters.

[0379] In this example, the radio device may be configured with one or more serving cells by a base station. In this example, the base station may activate one or more second serving cells of the one or more serving cells. In this example, the base station may configure each active serving cell of the one or more second serving cells through corresponding PDCCH monitoring. In this example, the radio device may monitor a set of PDCCH candidates in one or more core sets on the active DL BWP of each active serving cell configured with corresponding PDCCH monitoring. In this example, the radio device may monitor this set of PDCCH candidates in one or more core sets according to a corresponding search space set. In this example, monitoring may include decoding each PDCCH candidate in the set according to the monitored DCI format.

[0380] In this example, a set of PDCCH candidates for the radio device to be monitored can be defined according to a PDCCH search space set. In this example, the search space set can be a general search space (CSS) set or a UE-specific search space (USS) set.

[0381] In this example, one or more PDCCH monitoring opportunities may be associated with an SS / PBCH block. In this example, the SS / PBCH block may be quasi-co-located with CSI-RS. In this example, the TCI state of an active BWP may include CSI-RS. In this example, an active BWP may include a core set identified by an index equal to zero (e.g., core set zero). In this example, the radio device may determine the TCI state by the most recent of the following: an indication of a MAC CE activation command or a random access procedure not initiated by a PDCCH command that triggers a non-contention-based random access procedure. In this example, for a DCI format with a CRC scrambled by C-RNTI, the radio device may monitor the corresponding PDCCH candidate at one or more PDCCH monitoring opportunities in response to one or more PDCCH monitoring opportunities associated with an SS / PBCH block.

[0382] In this example, a base station can configure a radio device to have one or more DL BWPs in the serving cell. In this example, for one or more DL BWPs, the radio device can be provided by higher-layer signaling having one or more (e.g., 2, 3) control resource groups (core sets). For one or more core sets, the base station may provide the radio device with at least one of the following through the higher-layer parameter ControlResourceSet: core set index (e.g., provided by the higher-layer parameter controlResourceSetId), DMRS scrambling sequence initialization value (e.g., provided by the higher-layer parameter pdcch-DMRS-ScramblingID); multiple consecutive symbols (e.g., provided by the higher-layer parameter duration), a set of resource blocks (e.g., provided by the higher-layer parameter frequencyDomainResources), CCE-to-REG mapping parameters (e.g., provided by the higher-layer parameter cce-REG-MappingType), antenna port quasi-co-address (e.g., a set of antenna port quasi-co-address provided by the first higher-layer parameter tci-StatesPDCCH-ToAddList and the second higher-layer parameter tci-StatesPDCCH-ToReleaseList), and an indication of the presence or absence of the Transmission Configuration Indication (TCI) field for the DCI format (e.g., DCI format 1_1) transmitted by the PDCCH in the core set (e.g., provided by the higher-layer parameter TCI-PresentInDCI). In this example, antenna port quasi-co-address can indicate the quasi-co-address information of one or more DM-RS antenna ports used for PDCCH reception in the core set. In this example, the core set index can be unique within one or more DL BWPs of the serving cell. In this example, when the higher-layer parameter TCI-PresentInDCI is absent, the radio device can consider the TCI field to be absent / disabled in DCI format.

[0383] In this example, the first higher-layer parameter `tci-StatesPDCCH-ToAddList` and the second higher-layer parameter `tci-StatesPDCCH-ToReleaseList` can provide a subset of TCI states defined in the pdsch-Config. In this example, the wireless device can use this subset of TCI states to provide one or more QCL relationships between one or more RSs in the subset of TCI states and one or more DM-RS ports received by the PDCCH in the core set.

[0384] In this example, the base station can configure a core set for the radio device. In this example, the core set index (e.g., provided by the higher-layer parameter controlResourceSetId) can be non-zero. In this example, the base station may not provide the radio device with a configuration of one or more TCI states via the first higher-layer parameter tci-StatesPDCCH-ToAddList and / or the second higher-layer parameter tci-StatesPDCCH-ToReleaseList for the core set. In this example, in response to the lack of a configuration of one or more TCI states for the core set, the radio device may assume that one or more DMRS antenna ports used for PDCCH reception in the core set are quasi-co-located with RSs (e.g., SS / PBCH blocks). In this example, the radio device can identify RSs during the initial access procedure.

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

[0386] In this example, the base station can configure a core set for the radio device. In this example, the core set index (e.g., provided by the higher-layer parameter controlResourceSetId) can be equal to zero. In this example, the radio device may not receive a MAC CE activation command for the TCI state of the core set. In response to the lack of a MAC CE activation command, the radio device may assume that one or more DMRS antenna ports used for PDCCH reception in the core set are quasi-co-located with the RS (e.g., SS / PBCH block). In this example, the radio device can identify the RS during the initial access procedure. In this example, the radio device can identify the RS from the most recent random access procedure. In this example, the radio device may initiate a new random access procedure without responding to receiving a PDCCH command that triggers a non-contention-based random access procedure.

[0387] In this example, the base station can provide a single TCI state for the core set to the radio device. In this example, the base station can provide a single TCI state via a first higher-layer parameter tci-StatesPDCCH-ToAddList and / or a second higher-layer parameter tci-StatesPDCCH-ToReleaseList. In response to providing a single TCI state for the core set, the radio device can assume that one or more DM-RS antenna ports used for PDCCH reception in the core set are quasi-co-located with one or more DL-RS quasi-co-located by the single TCI state.

[0388] In this example, the base station can configure a core set for the radio device. In this example, the base station can provide the radio device with a configuration of at least two TCI states via a first higher-layer parameter tci-StatesPDCCH-ToAddList and / or a second higher-layer parameter tci-StatesPDCCH-ToReleaseList for the core set. In this example, the radio device can receive the configuration of at least two TCI states from the base station. In this example, the radio device can receive a MAC CE activation command for at least one of the at least two TCI states of the core set. In response to receiving a MAC CE activation command for at least one of the at least two TCI states, the radio device can assume that one or more DM-RS antenna ports used for PDCCH reception in the core set are quasi-co-located with one or more DL RS quasi-co-located by a single TCI state.

[0389] In this example, the base station can configure a core set for the radio device. In this example, the core set index (e.g., provided by the higher-layer parameter controlResourceSetId) can be equal to zero. In this example, the base station can provide the radio device with configurations for at least two TCI states of the core set. In this example, the radio device can receive configurations for at least two TCI states from the base station. In this example, the radio device can receive a MAC CE activation command for at least one of the at least two TCI states of the core set. In this example, in response to the core set index being equal to zero, the radio device can anticipate the QCL type (e.g., QCL-TypeD) of the first RS (e.g., CSI-RS) in at least one of the at least two TCI states provided by the second RS (e.g., SS / PBCH block). In this example, in response to the core set index being equal to zero, the radio device can anticipate the QCL type (e.g., QCL-TypeD) of the first RS (e.g., CSI-RS) in at least one of the at least two TCI states to perform spatial QCL with the second RS (e.g., SS / PBSH block).

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

[0391] In this example, a base station can configure a radio device to have one or more DL BWPs in the serving cell. In this example, for one or more DL BWPs, the radio device can be provided by a higher layer having one or more (e.g., 3, 5, 10) search space sets. In an example, for a search space set within one or more search space sets, the radio device may provide at least one of the following by the higher-layer parameter SearchSpace: a search space set index (e.g., provided by the higher-layer parameter searchSpaceId); an association between the search space set and the core set (e.g., provided by the higher-layer parameter controlResourceSetId); a PDCCH monitoring period with a first number of slots and a PDCCH monitoring offset with a second number of slots (e.g., provided by the higher-layer parameter monitoringSlotPeriodicityAndOffset); a PDCCH monitoring pattern within the slot, indicating one or more first symbols of the core set within the slot for PDCCH monitoring (e.g., provided by the higher-layer parameter monitoringSymbolsWithinSlot); a third number of slots (e.g., provided by the higher-layer parameter duration); multiple PDCCH candidates; and an indication that the search space set is a general search space set or a UE-specific search space set (e.g., provided by the higher-layer parameter searchSpaceType). In an example, the duration may indicate the number of slots in which the search space set may exist.

[0392] In this example, based on the PDCCH monitoring period, PDCCH monitoring offset, and PDCCH monitoring mode within a time slot, the wireless device can determine the PDCCH monitoring timing on the active DL BWP. In this example, for a search space set, the wireless device can determine the existence of a PDCCH monitoring timing within a time slot. In this example, the wireless device can monitor at least one PDCCH of the search space set for a duration of a third (continuous) time slot starting from the beginning of the time slot.

[0393] In this example, the radio device can monitor one or more PDCCH candidates in the USS set on the active DL BWP of the serving cell. In this example, the base station may not configure the radio device with a carrier indicator field. In response to the absence of a carrier indicator field, the radio device can monitor one or more PDCCH candidates that do not have a carrier indicator field.

[0394] In this example, the radio device can monitor one or more PDCCH candidates in the USS set on the active DL BWP of the serving cell. In this example, the base station can configure the radio device to have a carrier indicator field. In response to the carrier indicator field being configured, the radio device can monitor one or more PDCCH candidates that have the carrier indicator field.

[0395] In one example, the base station can configure the radio device to monitor one or more PDCCH candidates with a carrier indicator field in a first cell. In another example, the carrier indicator field may indicate a second cell. In yet another example, the carrier indicator field may correspond to a second cell. In response to monitoring one or more PDCCH candidates in the first cell, where the carrier indicator field indicates a second cell, the radio device may not intend to monitor one or more PDCCH candidates on an active DL BWP in the second cell.

[0396] In this example, the radio device can monitor one or more PDCCH candidates on the active DL BWP of the serving cell. In response to monitoring one or more PDCCH candidates on the active DL BWP of the serving cell, the radio device can monitor one or more PDCCH candidates of the serving cell.

[0397] In this example, the radio device can monitor one or more PDCCH candidates on the active DL BWP of the serving cell. In response to monitoring one or more PDCCH candidates on the active DL BWP of the serving cell, the radio device can monitor at least one or more PDCCH candidates for the serving cell. In this example, the radio device can monitor one or more PDCCH candidates for the serving cell and at least a second serving cell.

[0398] In one example, a base station may configure a radio device to have one or more cells. In another example, when the number of one or more cells is one, the base station may configure the radio device for single-cell operation. In yet another example, when the number of one or more cells is more than one, the base station may configure the radio device for operation involving carrier aggregation within the same frequency band (e.g., in-band).

[0399] In this example, a wireless device can monitor one or more active DL BWPs on one or more cells, with multiple core sets on one or more PDCCH candidates during overlapping PDCCH monitoring periods. In this example, multiple core sets can have different QCL-TypeD attributes.

[0400] In one example, the timing of a first PDCCH monitoring in a first core set of multiple core sets of a first cell may overlap with the timing of a second PDCCH monitoring in a second core set of multiple core sets of the first cell. In another example, the radio device may monitor at least one first PDCCH candidate on an active DL BWP of one or more active DL BWPs in the first cell during the first PDCCH monitoring timing. In yet another example, the radio device may monitor at least one second PDCCH candidate on an active DL BWP of one or more active DL BWPs in the first cell during the second PDCCH monitoring timing.

[0401] In one example, the timing of a first PDCCH monitoring in the first core set of multiple core sets of a first cell (one or more cells) may overlap with the timing of a second PDCCH monitoring in the second core set of multiple core sets of a second cell (one or more cells). In another example, the radio device may monitor at least one first PDCCH candidate on the first active DL BWP of one or more active DL BWPs in the first PDCCH monitoring timing. Similarly, in another example, the radio device may monitor at least one second PDCCH candidate on the second active DL BWP of one or more active DL BWPs in the second PDCCH monitoring timing.

[0402] In an instance, the first QCL type property of the first core set (e.g., QCL-TypeD) may be different from the second QCL type property of the second core set (e.g., QCL-TypeD).

[0403] In this example, in response to monitoring one or more PDCCH candidates in overlapping PDCCH monitoring moments across multiple core sets and multiple core sets with different QCL-TypeD attributes, the radio device can determine a selected core set from multiple core sets in one or more cells, based on a core set determination rule. In this example, in response to this determination, the radio device can monitor at least one PDCCH candidate in overlapping PDCCH monitoring moments on the active DL BWP of the cell. In this example, the selected core set can be associated with a search space set (e.g., an association provided by the higher-layer parameter controlResourceSetId).

[0404] In this instance, one or more core sets from multiple core sets can be associated with a CSS set. In this instance, one or more core sets from multiple core sets associated with a CSS set may include at least one PDCCH candidate in overlapping PDCCH monitoring moments for at least one search space set of core sets from one or more core sets (e.g., the association between at least one search space set and a core set provided by the higher-level parameter controlResourceSetId), and / or a CSS set.

[0405] In this example, a first core set may be associated with a first CSS set. In this example, a first core set may be associated with a first USS set. In this example, a second core set may be associated with a second CSS set. In this example, a second core set may be associated with a second USS set. In this example, a core set (e.g., a first core set, a second core set) associated with a CSS set (e.g., a first CSS set, a second CSS set) may include at least one search space for the core set as the CSS set. In this example, a core set (e.g., a first USS set, a second USS set) associated with a USS set (e.g., a first core set, a second core set) may include at least one search space for the core set as the USS set.

[0406] In an example, when a first core set is associated with a first CSS set and a second core set is associated with a second CSS set, one or more core sets may include the first core set and the second core set.

[0407] In an example, when one or more core sets include a first core set and a second core set, in response to the first core set being configured in a first cell and the second core set being configured in a second cell, one or more selected cells may include the first cell and the second cell.

[0408] In one instance, when one or more core sets include a first core set and a second core set, in response to the first core set being configured in a first cell and the second core set being configured in a first cell, one or more selected cells may include the first cell. In one instance, at least one core set may include a first core set and a second core set. In one instance, the first search space set of the first core set of at least one core set can be identified by a first search space set-specific index (e.g., provided by the higher-layer parameter searchSpaceId). In one instance, the radio device can monitor at least one first PDCCH candidate in the first PDCCH monitoring timing within the first core set associated with the first search space set (e.g., the association provided by the higher-layer parameter controlResourceSetId). In one instance, the second search space set of the second core set of at least one core set can be identified by a second search space set-specific index (e.g., provided by the higher-layer parameter searchSpaceId). In one instance, the radio device can monitor at least one second PDCCH candidate in the second PDCCH monitoring timing within the second core set associated with the second search space set (e.g., the association provided by the higher-layer parameter controlResourceSetId). In this example, the index specific to the first search space set may be lower than the index specific to the second search space set. In response to the index specific to the first search space set being lower than the index specific to the second search space set, the radio device can select the first search space set for the core set determination rule. In this example, in response to this selection, for the core set determination rule, the radio device can monitor at least one first PDCCH candidate in the first PDCCH timing within the first core set of the active DL BWP of the first cell. In this example, in response to this selection, for the core set determination rule, the radio device can stop monitoring at least one second PDCCH candidate in the second PDCCH monitoring timing within the second core set of the active DL BWP of the first cell. In this example, in response to this selection, the radio device can abandon monitoring at least one second PDCCH candidate in the second PDCCH monitoring timing within the second core set of the active DL BWP of the first cell.

[0409] In this example, the first cell can be identified using a first-cell-specific index. In this example, the second cell can be identified using a second-cell-specific index. In this example, the first-cell-specific index can be lower than the second-cell-specific index. In this example, when one or more selected cells include both the first and second cells, the radio device can select the first cell in response to the first-cell-specific index being lower than the second-cell-specific index.

[0410] In this instance, when a first core set is associated with a first CSS set and a second core set is associated with a second USS set, one or more core sets may include the first core set. In this instance, when one or more core sets include the first core set, in response to the first core set being configured in a first cell, one or more selected cells may include the first cell.

[0411] In this instance, when a first core set is associated with a first USS set and a second core set is associated with a second CSS set, one or more core sets may include the second core set. In this instance, when one or more core sets include the second core set, in response to the second core set being configured in a first cell, one or more selected cells may include the first cell. In this instance, when one or more core sets include the second core set, in response to the second core set being configured in a second cell, one or more selected cells may include the second cell.

[0412] In this example, the wireless device can determine that one or more core sets are associated with one or more selected cells of one or more cells. In this example, the base station can configure a first core set of one or more core sets in a first cell of one or more selected cells. In this example, the base station can configure a second core set of one or more core sets in the first cell. In this example, the base station can configure a third core set of one or more core sets in a second cell of one or more selected cells. In this example, the first cell and the second cell can be different.

[0413] In one instance, the wireless device may receive one or more configuration parameters from a base station. These configuration parameters may indicate a cell-specific index for one or more cells (e.g., provided by the higher-layer parameter `servCellIndex`). In this instance, each of the one or more cells may be identified by a corresponding cell-specific index. In this instance, the cell-specific index of one or more selected cells may be the lowest among the cell-specific indices of the one or more selected cells.

[0414] In an example, when a radio device determines that one or more core sets are associated with one or more selected cells of one or more cells, the radio device can select a cell in response to a core set determination rule, provided that the cell-specific index of the cell is the lowest among the cell-specific indices of one or more selected cells.

[0415] In this example, a base station may configure at least one core set of one or more core sets in a (selected) cell. In this example, at least one search space set of at least one core set may have at least one PDCCH candidate and / or may be a CSS set during overlapping PDCCH monitoring events.

[0416] In this instance, one or more configuration parameters may indicate a search space set-specific index for at least one search space set of the cell (e.g., provided by the higher-layer parameter `searchSpaceId`). In this instance, each search space set in at least one search space set can be identified by a corresponding search space set-specific index of the search space set-specific index. In this instance, the radio device may determine that the search space set-specific index of the search space set in at least one search space set is likely the lowest among the search space set-specific indices of at least one search space set. In response to determining that the search space set-specific index of the search space set-specific index is the lowest among the search space set-specific indices of at least one search space set, the radio device may select a search space set for a core set determination rule. In this instance, a search space set may be associated with a selected core set of at least one core set (e.g., an association provided by the higher-layer parameter `controlResourceSetId`).

[0417] In this example, when a radio device monitors one or more PDCCH candidates in overlapping PDCCH monitoring moments across multiple core sets, and the multiple core sets have different QCL-TypeD attributes, in response to selecting a cell and / or selecting a search space set associated with the selected core set, the radio device can monitor at least one PDCCH in the selected core set across the multiple core sets on the active DL BWP of the cell in one or more cells. In this example, for the core set determination rule, the radio device can select a selected core set associated with a search space set and a cell.

[0418] In this instance, the selected core set can have a first QCL-TypeD property. In this instance, a second core set of multiple core sets can have a second QCL-TypeD property. In this instance, the selected core set and the second core set can be different.

[0419] In this example, the first QCL-TypeD attribute and the second QCL-TypeD attribute can be the same. In this example, in response to the first QCL-TypeD attribute of the selected core set being the same as the second QCL-TypeD attribute of the second core set, the wireless device can monitor at least one second PDCCH candidate in the second core set of multiple core sets (during overlapping PDCCH monitoring events).

[0420] In this example, the first QCL-TypeD attribute and the second QCL-TypeD attribute can be different. In this example, in response to the first QCL-TypeD attribute of the selected core set differing from the second QCL-TypeD attribute of the second core set, the wireless device can stop monitoring at least one second PDCCH candidate in the second core set of multiple core sets (during overlapping PDCCH monitoring periods). In this example, in response to the first QCL-TypeD attribute of the selected core set differing from the second QCL-TypeD attribute of the second core set, the wireless device can abandon monitoring at least one second PDCCH candidate in the second core set of multiple core sets (during overlapping PDCCH monitoring periods).

[0421] In an example, for the core set determination rule, the wireless device may consider that the first QCL type (e.g., QCL TypeD) attribute (e.g., SS / PBCH block) of the first RS differs from the second QCL type (e.g., QCL TypeD) attribute of the second RS (CSI-RS)

[0422] In one instance, for the core set determination rule, a first RS (e.g., CSI-RS) may be associated with an RS (e.g., SS / PBCH block) in a first cell (e.g., for QCL). In another instance, a second RS (e.g., CSI-RS) may be associated with an RS in a second cell (e.g., for QCL). In response to the association of the first and second RSs with RSs, the radio device may consider that the first QCL type (e.g., QCL TypeD) attribute of the first RS is the same as the second QCL type (e.g., QCL TypeD) attribute of the second RS.

[0423] In this example, the wireless device can determine the TCI states of multiple active devices from multiple core sets.

[0424] In this example, the radio device can monitor multiple search space sets associated with different cores for one or more cells (e.g., for single-cell operation or for carrier aggregation with the same frequency band). In this example, at least two monitoring events for at least two search space sets among the multiple search space sets can overlap in time (e.g., at least one symbol, at least one time slot, subframe, etc.). In this example, at least two search space sets can be associated with at least two first core sets. The at least two first core sets can have different QCL-TypeD attributes. In this example, for core set determination rules, the radio device can monitor at least one search space set associated with a selected core set in the cell's active DL BWP. In this example, at least one search space set can be a CSS set. In this example, the cell-specific index of the cell can be the lowest among the cell-specific indices of one or more cells including the cell. In this example, at least two second core sets of the cell can include CSS sets. In response to at least two second core sets of a cell including a CSS set, the wireless device may select a selected core set of at least two second core sets if the search space-specific index of the search space set associated with the selected core set is the lowest among the search space-specific indices of the search space sets associated with the at least two second core sets. In an example, the wireless device monitors the search space set in at least two monitoring moments.

[0425] In this example, the wireless device can determine that at least two first core sets are unrelated to a CSS set. In this example, the wireless device can determine that each core set in the at least two first core sets is unrelated to a CSS set. In this example, for a core set determination rule, in response to the determination, the wireless device can monitor at least one search space set associated with a selected core set in the cell's active DL BWP. In this example, at least one search space set can be a USS set. In this example, the cell-specific index of the cell can be the lowest among the cell-specific indices of one or more cells including the cell. In this example, at least two second core sets of the cell can include USS sets. In response to at least two second core sets of the cell including USS sets, the wireless device can select a selected core set of at least two second core sets in response to the search space-specific index of the search space set associated with the selected core set being the lowest among the search space-specific indices of the search space sets associated with the at least two second core sets. In this example, the wireless device monitors search space sets in at least two monitoring times.

[0426] In this example, the base station can indicate the TCI status of PDCCH reception for the core set of the serving cell to the radio device by sending a TCI status indication for a UE-specific PDCCH MAC CE. In this example, when the MAC entity of the radio device receives a TCI status indication for a UE-specific PDCCH MAC CE on / for the serving cell, the MAC entity can indicate information about the TCI status indication for the UE-specific PDCCH MAC CE to a lower layer (e.g., the PHY).

[0427] In this example, the TCI status indication of a UE-specific PDCCH MAC CE can be identified through a MAC PDU subheader with an LCID. The TCI status indication of a UE-specific PDCCH MAC CE can have a fixed 16-bit size including one or more fields. In this example, one or more fields may include the serving cell ID, core set ID, TCI status ID, and reserved bits.

[0428] In this example, the serving cell ID can indicate the identity of the serving cell as indicated by the TCI status of the UE-specific PDCCH MAC CE. The serving cell ID can be n bits long (e.g., n = 5 bits).

[0429] In this example, the core set ID can indicate a control resource set. A control resource set can be identified by its control resource set ID (e.g., ControlResourceSetId). The TCI status is indicated by its control resource set ID. The core set ID can be n3 bits long (e.g., n3 = 4 bits).

[0430] In an example, the TCI State ID can indicate the TCI state identified by the TCI-StateId. The TCI state can be applied to a control resource set identified by the core set ID. The length of the TCI State ID can be n4 bits (e.g., n4 = 6 bits).

[0431] The ControlResourceSet information element can be used to configure the time / frequency control resource set (CORESET) used for searching downlink control information.

[0432] The information element TCI-State can associate one or two DL reference signals with the corresponding quasi-co-location (QCL) type. The TCI-State element may include one or more fields, including TCI-StateId and QCL-Info. QCL-Info may include one or more second fields. These second fields may include the serving cell index, BWP ID, reference signal index (e.g., SSB-index, NZP-CSI-RS-ResourceID), and QCL type (e.g., QCL-typeA, QCL-typeB, QCL-typeC, QCL-typeD). In an example, TCI-StateID identifies the configuration of the TCI state.

[0433] In this example, the serving cell index can indicate the serving cell where the reference signal, indicated by the reference signal index, resides. When the serving cell index is not present in the information element TCI-State, the information element TCI-State can be applied to the serving cell in which the information element TCI-State is configured. A reference signal can only reside on a second serving cell different from the serving cell in which the information element TCI-State is configured, if the QCL-Type is configured as a first type (e.g., Type D, Type A, Type B). In this example, the BWP ID can indicate the downlink BWP of the serving cell where the reference signal resides.

[0434] The SearchSpace information element defines the method / location for searching PDCCH candidates within the search space. The search space can be identified by the SearchSpaceId field in the SearchSpace information element. Each search space can be associated with a control resource set (e.g., ControlResourceSet). The control resource set can be identified by the controlResourceSetId field in the SearchSpace information element. This controlResourceSetId field indicates the control resource set (CORESET) applicable to the SearchSpace.

[0435] In this example, the base station may require one or more (additional) UE radio access capability information from the radio device. In response to the need for UE radio access capability information, the base station may initiate a procedure to request one or more UE radio access capability information from the radio device (e.g., via the information element UECapenabilityEquiry). In this example, the radio device may use an information element (e.g., a UECapabilityInformation message) to convey one or more UE radio access capability information requested by the base station. In this example, the radio device may provide "timeDurationForQCL" in a FeatureSetDownlink indicating a set of features supported by the radio device.

[0436] In an example, a wireless device can report to a base station its RF capabilities for transmitting and / or receiving via capability signaling. Upon receiving capability signaling, the base station can determine whether the wireless device can simultaneously receive (transmit) the physical channel and / or RS from one or more component carriers in the downlink (uplink) via different receive (transmit) beams.

[0437] In an example, under in-band carrier aggregation (CA), a base station can configure one or more component carriers in the same frequency band to a radio device. The one or more component carriers can be powered by the same single RF chain. In this case, the radio device can simultaneously apply a single and identical set of TX / RX spatial parameters to one or more component carriers in the same frequency band. In this example, applying a single and identical set of TX / RX spatial parameters can impose limitations on the flexibility of multiplexed physical channels (e.g., PDSCH / PUSCH, PDCCH / PUCCH, SRS, PRACH, etc.) and / or reference signals (RS) (e.g., CSI-RS, SSB, etc.) within and across one or more component carriers.

[0438] In an example, when a first channel / RS of a first serving cell (e.g., PCell, BWP) is associated with a second channel / RS of a second serving cell (e.g., SCell, BWP) (e.g., QCL-Type D'), the first channel / RS and the second channel / RS can be multiplexed in the same OFDM symbol. The radio device can simultaneously transmit (or receive) the multiplexed first channel / RS and second channel / RS in the uplink (or downlink).

[0439] In this example, one or more first antenna ports of the first serving cell and one or more second antenna ports of the second serving cell may be unrelated (e.g., QCL-TypeD'). The radio device may not infer one or more channel characteristics of one or more first antenna ports of the first serving cell from one or more second antenna ports of the second serving cell.

[0440] In this example, the first channel / RS (e.g., PDSCH / PUSCH, PDCCH / PUCCH, SRS, PRACH, CSI-RS, SSB, etc.) and the second channel / RS (e.g., PDSCH / PUSCH, PDCCH / PUCCH, SRS, PRACH, PRACH, CSI-RS, SSB, etc.) can be uncorrelated (QCL-Type D). The base station can configure a first channel / RS with a first QCL assumption and a second channel / RS with a second QCL assumption. In this example, the first transmission / reception of the first channel / RS and the second transmission / reception of the second channel / RS can overlap (e.g., in at least one OFDM symbol). When the first QCL assumption and the second QCL assumption are different, the radio device can perform the first transmission / reception and the second transmission / reception at different times.

[0441] Figure 16 An example of a TCI status information element (IE) for a downlink beam management procedure is shown according to an embodiment of the present disclosure.

[0442] In this example, the base station can configure the radio device to have one or more TCI-State configurations via higher-layer parameters (e.g., tci-StatesToAddModList, tci-StatesToReleaseList in IE PDSCH-Config) for the serving cell (e.g., PCell, SCell). In this example, the radio device can detect a PDCCH with DCI for the serving cell. The radio device can use at least one of the TCI states configured in one or more TCI states to decode a PDSCH scheduled by the PDCCH (or DCI) (or for receiving a PDSCH). The DCI may be intended for use with the radio device and / or the serving cell of the radio device.

[0443] In the example, Figure 16This illustrates an instance of one or more TCI-State configurations for the TCI state. In this instance, the DCI can indicate the TCI state. In this instance, the wireless device can receive the PDSCH (or PDCCH) based on the TCI state. The TCI state can include one or more parameters (e.g., qcl-Type1, qcl-Type2, referenceSignal, etc.). In this instance, the TCI state can be indexed by the TCI state index (e.g., ...). Figure 16 The TCI-StateId is used for identification. In an example, receiving PDSCH (or PDCCH) based on the TCI state can include the radio device using one or more parameters in the TCI state to configure one or more quasi-co-address relationships between at least one downlink reference signal (e.g., SS / PBCH block, CSI-RS) and at least one DM-RS port of the PDSCH (scheduled by DCI). In an example, in Figure 16 In this context, the first quasi-co-location relationship of one or more quasi-co-location relationships can be determined by the first DL RS of at least one downlink reference signal (e.g., by...). Figure 16 The higher-level parameter qcl-Type1 (the referenceSignal indicator in the code) is used for configuration. In the example, in Figure 16 In this context, the second quasi-co-location relationship in one or more quasi-co-location relationships can be determined by (e.g., by) a downlink reference signal used for at least one downlink reference signal. Figure 16 The referenceSignal indicates the high-level parameter qcl-Type2 configuration of the second DL RS (if it is already configured).

[0444] In the example, it can be done through Figure 16 The higher-layer parameter `qcl-Type` in the `QCL-Info` provides the wireless device with at least one quasi-co-location type of at least one downlink reference signal (e.g., a first DL RS, a second DL RS). The first quasi-co-location relationship of the first DL RS may include a first QCL type of at least one quasi-co-location type (e.g., `QCL-TypeA`, `QCL-TypeB`). The second quasi-co-location relationship of the second DL RS may include a second QCL type of at least one quasi-co-location type (e.g., `QCL-TypeC`, `QCL-TypeD`). In some instances, the first QCL type of the first DL RS and the second QCL type of the second DL RS may be different. In some instances, the first DL RS and the second DL RS may be the same. In some instances, the first DL RS and the second DL RS may be different.

[0445] In one example, configuring one or more quasi-co-address relationships between at least one downlink reference signal (e.g., a first DL RS and a second DL RS) and at least one DM-RS port of the PDSCH (or PDCCH) using one or more parameters in the TCI state may include quasi-co-addressing of at least one DM-RS port of the PDSCH (or PDCCH) with the first DLRS relative to a first QCL type. In another example, configuring one or more quasi-co-address relationships between at least one downlink reference signal (e.g., a first DL RS and a second DL RS) and at least one DM-RS port of the PDSCH (or PDCCH) using one or more parameters in the TCI state may include quasi-co-addressing of at least one DM-RS port of the PDSCH (or PDCCH) with the second DLRS relative to a second QCL type.

[0446] Figure 17 An example of a downlink beam management procedure according to an embodiment of the present disclosure is shown.

[0447] In one instance, a wireless device may receive one or more messages from a base station. These messages may include one or more configuration parameters for one or more cells (e.g., PCell, SCell, SpCell). The one or more cells may include a first cell and a second cell.

[0448] In this instance, one or more configuration parameters can indicate a cell-specific index for one or more cells (e.g., provided by the higher-level parameter `servCellIndex`). In this instance, each of the one or more cells can be identified by a corresponding cell-specific index. In this instance, the first cell can be identified by a first cell-specific index. In this instance, the second cell can be identified by a second cell-specific index.

[0449] In an instance, one or more configuration parameters can indicate one or more control resource sets (core sets). One or more core sets may include a first core set, a second core set, and a third core set.

[0450] In this instance, one or more configuration parameters can indicate a core set-specific index for one or more core sets (e.g., provided by the higher-level parameter `controlResourceSetId`). In this instance, each core set within one or more core sets can be identified by a corresponding core set-specific index. In this instance, the first core set (e.g., ...) Figure 17 The PDCCH-1 in the first core set can be identified by a specific index of the first core set. In the instance, the second core set (e.g., Figure 17The PDCCH-2 in the second core set can be identified through a specific index of the second core set. In the instance, the third core set (e.g., Figure 17 The PDCCH-3 in the core set can be identified through a specific index of the third core set.

[0451] In this example, the wireless device can access the second core set (e.g., Figure 17 The second PDCCH receive in PDCCH-3 applies a second QCL assumption (or a second TCI state). In an example, the second QCL assumption (or second TCI state) may indicate at least one second RS (e.g., CSI-RS, SS / PBCH block, etc.). Figure 17 (RS-1 in the example). In an instance, the second QCL assumption (or the second TCI state) may indicate the second QCL type (e.g., QCL-TypeD).

[0452] In this example, the radio device can identify / use / select at least one second RS for random access procedures (e.g., initial access procedures). In this example, the radio device can determine / use at least one second RS for second PDCCH reception in the second core set based on receiving a first higher-layer parameter tci-StatesPDCCH-ToAddList and / or a second higher-layer parameter tci-StatesPDCCH-ToReleaseList for the second core set. In this example, one or more configuration parameters may include the first higher-layer parameter tci-StatesPDCCH-ToAddList and / or the second higher-layer parameter tci-StatesPDCCH-ToReleaseList. In this example, the radio device can determine / use at least one second RS for second PDCCH reception in the second core set based on a MAC CE activation command for the second core set (e.g., a TCI state indication for a UE-specific PDCCH MAC CE).

[0453] In this example, based on applying a second QCL assumption (or a second TCI state) to the second PDCCH reception in the second core set, the wireless device can determine that at least one second DM-RS antenna port of the second PDCCH reception in the second core set is quasi-co-located with at least one second RS having a second QCL type.

[0454] In this example, the wireless device can access a third core set (e.g., Figure 17The third PDCCH receive in PDCCH-3 applies the third QCL assumption (or third TCI state). In an example, the third QCL assumption (or third TCI state) may indicate at least one third RS (e.g., CSI-RS, SS / PBCH block, etc.). Figure 17 (RS-2 in the example). In an example, the third QCL assumption (or the third TCI state) can indicate the third QCL type (e.g., QCL-TypeD).

[0455] In this example, the radio device can identify / use / select at least one third RS for random access procedures (e.g., initial access procedures). In this example, the radio device can determine / use at least one third RS for third PDCCH reception in the third core set based on receiving a first higher-layer parameter tci-StatesPDCCH-ToAddList and / or a second higher-layer parameter tci-StatesPDCCH-ToReleaseList for the third core set. In this example, one or more configuration parameters may include the first higher-layer parameter tci-StatesPDCCH-ToAddList and / or the second higher-layer parameter tci-StatesPDCCH-ToReleaseList. In this example, the radio device can determine / use at least one third RS for third PDCCH reception in the third core set based on a MAC CE activation command for the third core set (e.g., a TCI state indication for a UE-specific PDCCH MAC CE).

[0456] In this example, based on applying the third QCL assumption (or third TCI state) to the third PDCCH reception in the third core set, the wireless device can determine that at least one third DM-RS antenna port of the third PDCCH reception in the third core set is quasi-co-located with at least one third RS having a third QCL type.

[0457] In this example, the wireless device can receive DCI. In this example, the wireless device can detect a PDCCH with DCI. In this example, the wireless device can receive DCI while monitoring a PDCCH. In this example, DCI can schedule PDSCH (e.g., Figure 17 (PDSCH in the core). In an example, the wireless device can receive the DCI from the first core set (e.g., Figure 17 (PDCCH-1 in the text).

[0458] In this example, the wireless device may apply a first QCL assumption (or a first TCI state) to receive the PDSCH. In this example, the first QCL assumption (or first TCI state) may indicate at least one first RS (e.g., CSI-RS, SS / PBCH block, etc.). Figure 17 (RS-3 in the example). In an example, the first QCL assumption (or the first TCI state) may indicate the first QCL type (e.g., QCL-TypeD).

[0459] In this example, based on the application of a first QCL assumption (or a first TCI state) to the reception of the PDSCH, the wireless device can determine that at least one first DM-RS antenna port of the PDSCH is quasi-co-located with at least one first RS of the first QCL type.

[0460] In an example, the wireless device may be based on an indication of a first QCL assumption (or a first TCI state, for example...) Figure 17 The DCI field of the DCI→TCI-State→RS-3 in the PDSCH is used to determine at least one first RS for PDSCH reception. For example, the first TCI state can indicate at least one first RS.

[0461] In this example, the wireless device can determine at least one first RS based on the default PDSCH RS selection for the first QCL assumption (or first TCI state). In this example, when the time offset between DCI reception and PDSCH reception (e.g., ...) Figure 17 When the offset in the DCI is below a threshold (e.g., timeDurationForQCL, Threshold-Sched-Offset), the radio device can perform a default PDSCH RS selection. In one instance, the radio device can perform the default PDSCH RS selection based on the first core set of the DCI that received the scheduled PDSCH (without the TCI-PresentInDCI field configured). In another instance, the radio device can perform the default PDSCH RS selection based on a DCI format without (or without) the TCI field (e.g., DCI format 1_0).

[0462] In this example, the wireless device can determine that the PDSCH overlaps with the second and third core sets during the duration. In this example, the duration can be at least one symbol. In this example, the duration can be at least one microslot. In this example, the duration can be at least one slot. In this example, the duration can be at least one subframe. In this example, the duration can be at least one frame.

[0463] In an example, the first QCL assumption of the PDSCH may differ from the second QCL assumption of the second core set and the third QCL assumption of the second core set (e.g., during the duration). In an example, the first QCL assumption differs from the second QCL assumption, and the third QCL assumption may include the radio device not simultaneously receiving the PDSCH and monitoring the second core set for second PDCCH reception during the duration. In an example, the first QCL assumption differing from both the second and third QCL assumptions may include the radio device not simultaneously receiving the PDSCH and monitoring the third core set for third PDCCH reception during the duration. In an example, the first QCL assumption differing from both the second and third QCL assumptions may include at least one first RS differing from at least one second RS and at least one third RS. In an example, the first QCL assumption differing from both the second and third QCL assumptions may include at least one first RS not performing QCL with at least one second RS and at least one third RS (e.g., QCLTypeD).

[0464] In this example, the wireless device can monitor a second core set for second PDCCH reception with a second QCL assumption, and simultaneously monitor a third core set for third PDCCH reception with a third QCL assumption. In this example, the wireless device can perform both second and third PDCCH reception simultaneously.

[0465] In one instance, the time offset between DCI reception and PDSCH reception can be less than a threshold (e.g., timeDurationForQCL, Threshold-Sched-Offset). In another instance, the time offset between DCI reception and PDSCH reception can be equal to or greater than a threshold (e.g., timeDurationForQCL, Threshold-Sched-Offset). In yet another instance, the threshold can be based on reported UE capabilities. In yet another instance, a time offset below the threshold may include scheduling PDSCH before the threshold.

[0466] In the example, based on the determination that the PDSCH overlaps with the second core set and the third core set during the duration, the wireless device selects the selected core set from the second core set and the third core set.

[0467] In this example, the wireless device can select a chosen core set based on one or more standards. In this example, the wireless device can select a chosen core set based on a variety of standards.

[0468] The wireless device can select a core set based on, for example, a second core set-specific index of a second core set and a third core set-specific index of a third core set. In an example, selection based on the second core set-specific index and the third core set-specific index may include selecting the core set with the lowest (or highest) core set-specific index from the two core set-specific indexes. In another example, selecting a core set based on the second core set-specific index and the third core set-specific index may include the wireless device comparing the second core set-specific index and the third core set-specific index.

[0469] In this example, based on comparison, the wireless device can determine that an index specific to the third core set is lower (or higher) than an index specific to the second core set. Based on this determination, the wireless device can select the third core set as the chosen core set.

[0470] In this example, based on comparison, the wireless device can determine that an index specific to the second core set is lower (or higher) than an index specific to the third core set. Based on this determination, the wireless device can select the second core set as the selected core set.

[0471] In one example, a base station can configure a second core set for a first cell identified via a first cell-specific index (e.g., provided by the higher-layer parameter servCellIndex). In another example, a base station can configure a third core set for a second cell identified via a second cell-specific index (e.g., provided by the higher-layer parameter servCellIndex).

[0472] The wireless device may select a core set based on, for example, a first cell-specific index and a second cell-specific index. In one example, selecting a core set based on a first cell-specific index and a second cell-specific index may include selecting a cell with the lowest (or highest) cell-specific index from the first and second cell-specific indexes. In another example, selecting a core set based on a first cell-specific index and a second cell-specific index may include the wireless device comparing the first cell-specific index and the second cell-specific index.

[0473] In this example, based on this comparison, the wireless device can determine that a first cell-specific index is lower (or higher) than a second cell-specific index. Based on this determination, the wireless device can select the first cell as the selected cell. Based on selecting the first cell as the selected cell, the wireless device can select a second core set as the selected core set.

[0474] In this example, based on comparison, the wireless device can determine that a second cell-specific index is lower (or higher) than a first cell-specific index. Based on this determination, the wireless device can select the second cell as the selected cell. Based on selecting the second cell as the selected cell, the wireless device can select a third core set as the selected core set.

[0475] In an instance, one or more core sets can be associated with one or more groups (e.g., one-to-one, one-to-many, many-to-one). In an instance, each core set within one or more core sets can be associated with a group within one or more groups. In an instance, a first core set can be associated with a first group (e.g., a first TCI state group, a first antenna port group, a first HARQ process group, a first core set, a second TCI state group, a second antenna port group, a second HARQ process group, a second core cluster group). In an instance, a second core set can be associated with a second group (e.g., a first TCI state group, a first antenna port group, a first HARQ process group, a first core cluster group). In an instance, a third core set can be associated with a third group (e.g., a second TCI state group, a second antenna port group, a second HARQ process group, a second core cluster group). In an instance, one or more configuration parameters can indicate the association between one or more core sets and one or more groups (e.g., TCI state group-specific indexes, HARQ process group-specific indexes, antenna panel group-specific indexes, core cluster group-specific indexes, etc.).

[0476] In this instance, Group 1 and Group 2 can be the same. In this instance, Group 1 and Group 2 can be different. In this instance, Group 1 and Group 3 can be the same. In this instance, Group 1 and Group 3 can be different. In this instance, Group 3 and Group 2 can be the same. In this instance, Group 3 and Group 2 can be different.

[0477] In an example, the wireless device may select a core set based on, for example, a first group, a second group, and a third group. In an example, selecting a core set based on a first group, a second group, and a third group may include selecting a core set that has the same group (scheduling PDSCH) as the first core set (e.g., a second group, a third group). In an example, the first group and the second group may be the same. In an example, the first group and the third group may be different. Based on the first group and the second group being the same, and the first group and the third group being different, the wireless device may select a second core set associated with the second group as the selected core set. In an example, the first group and the third group may be the same. In an example, the first group and the second group may be different. Based on the first group and the third group being the same, and the first group and the second group being different, the wireless device may select a third core set associated with the third group as the selected core set.

[0478] In an instance, one or more configuration parameters can indicate one or more TCI states. In an instance, one or more TCI states can be grouped / formed into one or more TCI state groups.

[0479] In this instance, one or more TCI states may include TCI-State-0, TCI-State-1, TCI-State-2...TCI-State-127. In this instance, one or more TCI state groups may include a first TCI state group and a second TCI state group. The first TCI state group may include TCI-State-0, TCI-State-1, TCI-State-2...TCI-State-63. The second TCI state group may include TCI-State-64, TCI-State-65, TCI-State-66...TCI-State-127.

[0480] In this instance, one or more configuration parameters can indicate a TCI state group-specific index (e.g., provided by a higher-level parameter) for one or more TCI state groups. In this instance, each TCI state group can be identified by a corresponding TCI state group-specific index. In this instance, the first TCI state group can be identified by a first TCI state group-specific index. In this instance, the second TCI state group can be identified by a second TCI state group-specific index.

[0481] In this example, a first core set may be associated with a first TCI state group. The first core set associated with the first TCI state group may include the QCL assumptions (or TCI states) of the first core set within the first TCI state group (e.g., TCI-State-0, TCI-State-1, TCI-State-2, ..., TCI-State-63). In this example, a second core set may be associated with the first TCI state group. The second core set associated with the first TCI state group may include the second QCL assumptions (or second TCI states) of the second core set within the first TCI state group (e.g., TCI-State-0, TCI-State-1, TCI-State-2...TCI-State-63). In this example, a third core set may be associated with the second TCI state group. A third core set associated with the second TCI state group may include a third QCL assumption (or a third TCI state) of the third core set within the second TCI state group (e.g., TCI-State-64, TCI-State-65, TCI-State-66...TCI-State-127). In one instance, the first and second core sets may be the same, based on their association with the first TCI state group. In another instance, the first and third core sets may be different, based on their association with the first TCI state group and the third core set's association with the second TCI state group. In yet another instance, the second and third core sets may be different, based on their association with the first TCI state group and the third core set's association with the second TCI state group.

[0482] In this example, the wireless device may be served by one or more TRPs, including a first TRP and a second TRP. In this example, the first TRP may be associated with a first TCI state group. In this example, the second TRP may be associated with a second TCI state group. In this example, the first TRP associated with the first TCI state group may include the QCL assumptions (or TCI states) of downlink channels (e.g., PDSCH, PDCCH) scheduled / transmitted by the first TRP in the first TCI state group (e.g., TCI-State-0, TCI-State-1, TCI-State-2...TCI-State-63). In this example, the second TRP associated with the second TCI state group may include the QCL assumptions (or TCI states) of downlink channels (e.g., PDSCH, PDCCH) scheduled / transmitted by the second TRP in the second TCI state group (e.g., TCI-State-64, TCI-State-65...TCI-State-127).

[0483] In this example, since the first group and the second group are the same and the first TRP is associated with the first TCI state group, the wireless device can receive the first PDCCH of the first core set and the second PDCCH of the second core set from the same TRP (e.g., the first TRP). In this example, the first TRP can transmit the first DCI of the first core set and the second DCI of the second core set. Based on the transmission of the first DCI of the first core set and the second DCI of the second core set by the first TRP, the first group and the second group can be the same.

[0484] In one example, the second TRP is associated with a second TCI state group, and the wireless device can receive the third PDCCH from the third core set from the second TRP. In another example, the second TRP may transmit the first DCI from the third core set. In yet another example, the second TRP may not transmit the second DCI from the first and second core sets. If the second TRP transmits the first DCI from the third core set but not the second DCI from the second core set, the third group and the second group may be different. If the second TRP transmits the first DCI from the third core set but not the second DCI from the first core set, the third group and the first group may be different.

[0485] In this example, one or more configuration parameters can indicate one or more antenna ports. In this example, one or more antenna ports can be grouped / formed into one or more antenna port groups. In this example, one or more antenna port groups can include a first antenna port group and a second antenna port group. In this example, a wireless device can use the first antenna port group to receive a second PDCCH in a second core set. In this example, a wireless device can use the second antenna port group to receive a third PDCCH in a third core set.

[0486] In this example, one or more configuration parameters can indicate an antenna port group-specific index for one or more antenna port groups (e.g., provided by higher-level parameters). In this example, each antenna port group within the one or more antenna port groups can be identified by a corresponding antenna port group-specific index. In this example, the first antenna port group can be identified by a first antenna port group-specific index. In this example, the second antenna port group can be identified by a second antenna port group-specific index.

[0487] In this example, a first TRP can be associated with a first antenna port group. In this example, a second TRP can be associated with a second antenna port group. In this example, a first core set can be associated with a first antenna port group. In this example, a second core set can be associated with a first antenna port group. In this example, a third core set can be associated with a second antenna port group. In this example, the first group and the second group can be the same based on the first core set and the second core set associated with the first antenna port group.

[0488] In this instance, one or more configuration parameters can indicate one or more HARQ process indices. In this instance, one or more HARQ process indices can form one or more HARQ process groups. In this instance, one or more HARQ process groups can include a first HARQ process group and a second HARQ process group. In this instance, the wireless device can use the first HARQ process group to receive a second PDCCH in a second core set. In this instance, the wireless device can use the second HARQ process group to receive a third PDCCH in a third core set.

[0489] In this instance, one or more configuration parameters can indicate a HARQ process group-specific index (e.g., provided by higher-level parameters) for one or more HARQ process groups. In this instance, each HARQ process group within one or more HARQ process groups can be identified by a corresponding HARQ process group-specific index. In this instance, the first HARQ process group can be identified by a first HARQ process group-specific index. In this instance, the second HARQ process group can be identified by a second antenna port group-specific index.

[0490] In this example, the first TRP can be associated with a first antenna port group. In this example, the second TRP can be associated with a second antenna port group. In this example, the first core set can be associated with a first HARQ process group. In this example, the second core set can be associated with a first HARQ process group. In this example, the third core set can be associated with a second HARQ process group. In this example, based on the association of the first and second core sets with the first HARQ process group, the first group and the second group can be the same.

[0491] In this example, based on the selection of a core set, the wireless device can use selected RSs of the selected core set (or associated with it) for receiving PDSCH.

[0492] In this example, based on the selection of a selected core set, the wireless device can apply selected QCL assumptions (or selected TCI states) of the selected core set (or associated with it) to the reception of PDSCH.

[0493] In this example, based on the selection of a selected core set, the wireless device can apply selected RSs (or associated RSs) of the selected core set when receiving a PDSCH. In this example, based on the selection of a selected core set, the wireless device can receive a PDSCH with selected RSs of the selected core set (or associated RSs).

[0494] In this example, when the selected core set is the second core set, the selected RS can be at least one second RS. In this example, when the selected core set is the third core set, the selected RS can be at least one third RS.

[0495] In one instance, when the selected core set is the second core set, the selected QCL hypothesis (or selected TCI state) can be the second QCL hypothesis (or second TCI state). In another instance, when the selected core set is the third core set, the selected QCL hypothesis (or selected TCI state) can be the third QCL hypothesis (or third TCI state).

[0496] Figure 18 and Figure 19 An example of a downlink beam management procedure according to an embodiment of the present disclosure is shown. Figure 20 yes Figure 18 The flowchart of BWP operation is publicly available.

[0497] In this instance, the wireless device can receive one or more messages. These messages may include one or more configuration parameters. These configuration parameters may indicate one or more control resource sets, including a second core set.

[0498] In this example, the wireless device can access the second core set (e.g., Figure 18 The second PDCCH receive in PDCCH-2 applies a second QCL assumption (or a second TCI state). In an example, the second QCL assumption (or second TCI state) may indicate at least one second RS (e.g., CSI-RS, SS / PBCH block, etc.). Figure 18 (RS-2 in the example). In the example, the second QCL assumption (or the second TCI state) can indicate the second QCL type (e.g., QCL-TypeD).

[0499] In this example, the wireless device can receive DCI. In this example, the wireless device can detect a PDCCH with DCI. In this example, the wireless device can receive DCI while monitoring a PDCCH. In this example, DCI can schedule PDSCH (e.g., Figure 18 (PDSCH in the core). In an example, the wireless device can receive the DCI from the first core set (e.g., Figure 18 (PDCCH-1 in the PDCCH-1). In an example, the wireless device can receive DCI from the second core set (e.g., Figure 18 (PDCCH-2 in the middle).

[0500] In this example, the wireless device may apply a first QCL assumption (or a first TCI state) to receive the PDSCH. In this example, the first QCL assumption (or first TCI state) may indicate at least one first RS (e.g., CSI-RS, SS / PBCH block, etc.). Figure 18 (RS-1 in the example). In an example, the first QCL assumption (or the first TCI state) may indicate the first QCL type (e.g., QCL-TypeD).

[0501] In this example, the wireless device can determine that the PDSCH overlaps with the second core set during the duration. In this example, the duration can be at least one symbol. In this example, the duration can be at least one microslot. In this example, the duration can be at least one slot. In this example, the duration can be at least one subframe. In this example, the duration can be at least one frame.

[0502] In this example, the wireless device can determine that the PDSCH overlaps with the second core set during its duration and that the PDSCH is a multi-slot transmission. Based on this determination, the wireless device can prioritize the PDSCH over the second core set.

[0503] In this example, based on determining that the PDSCH overlaps with the second core set during its duration, the wireless device can determine whether the PDSCH is a single-slot transmission or a multi-slot transmission. In this example, a single-slot transmission may include a PDSCH duration of a single (or one) slot. In this example, a multi-slot transmission may include a PDSCH duration of at least two slots (e.g., Figure 18 (The first, second, and third time slots in the PDSCH). In an example, single-slot transmission may include a PDSCH duration of a single (or one) micro-slot. In an example, multi-slot transmission may include a PDSCH duration of at least two micro-slots.

[0504] In this example, the wireless device can determine that the PDSCH is a multi-slot transmission. In this example, the wireless device can prioritize the PDSCH over the second core set based on the determination that the PDSCH is a multi-slot transmission.

[0505] In this example, the wireless device can determine that the PDSCH is a single-slot transmission. In this example, the wireless device can prioritize the second core set over the PDSCH based on the determination that the PDSCH is a single-slot transmission.

[0506] In the example, the time offset between the reception of DCI and the reception of PDSCH (e.g., Figure 18 The offset in the time interval can be less than a threshold (e.g., timeDurationForQCL, e.g.) Figure 18 (The threshold in the example). In this example, the time offset between the reception of DCI and the reception of PDSCH can be equal to or greater than the threshold (e.g., timeDurationForQCL, Threshold-Sched-Offset). In this example, the threshold can be based on the reported UE capabilities. In this example, time offsets below the threshold can include scheduling PDSCH before the threshold.

[0507] In one example, prioritizing the PDSCH over the second core set may include the wireless device prioritizing a first QCL assumption (or a first TCI state) of the PDSCH over a second QCL assumption (or a second TCI state) of the second core set. In another example, prioritizing the first QCL assumption of the PDSCH over the second QCL assumption of the second core set may include at least one second DM-RS antenna port of the second PDCCH reception in the second core set being quasi-co-located with at least one first RS (based on the first QCL assumption). In yet another example, prioritizing the first QCL assumption of the PDSCH over the second QCL assumption of the second core set may include the wireless device applying at least one first RS (based on the first QCL assumption) to the second PDCCH reception in the second core set.

[0508] In an example, prioritizing the first QCL hypothesis of PDSCH over the second QCL hypothesis of the second core set may include covering the second QCL hypothesis over the duration of the first QCL hypothesis.

[0509] In one example, prioritizing the first QCL assumption over the second QCL assumption may include the radio device relinquishing the reception of the second PDCCH in the second core set. In another example, the radio device may relinquish the reception of the second PDCCH for at least a duration. In yet another example, relinquishing the reception of the second PDCCH may include the radio device stopping the reception of the second PDCCH.

[0510] In one example, prioritizing the first QCL assumption over the second QCL assumption may include the wireless device performing a second PDCCH reception with at least one second RS outside the duration (the non-overlapping portion of the PDSCH and the second core set). In another example, at least one second DM-RS antenna port for second PDCCH reception in the second core set is quasi-co-located with at least one second RS (as assumed by the second QCL) outside the duration (the non-overlapping portion of the PDSCH and the second core set).

[0511] Figure 19 An example of a downlink beam management procedure according to an embodiment of the present disclosure is shown.

[0512] In this example, the PDSCH can be a multi-slot transmission. Based on the multi-slot transmission, the PDSCH can include at least two time slots (e.g., Figure 19 (The first time slot, the second time slot, and the third time slot in the middle).

[0513] In this instance, the PDSCH can overlap with the second core set in at least two time slots. In this instance, the duration (e.g., at least one symbol) can be within a time slot. In this instance, the time slot can differ from the first time slot of at least two time slots (e.g., Figure 19 (The first time slot in the middle). In the example, in Figure 19 In this context, the time slot can be a second time slot. In the example, in... Figure 19 In this context, the time slot can be the third time slot.

[0514] In this example, based on the determination that the PDSCH overlaps with the second core set in a time slot different from the first time slot, the wireless device can apply a second QCL assumption (or a second TCI state) to receive the PDSCH. In this example, based on the application of the second QCL assumption to the reception of the PDSCH, the wireless device can determine that at least one first DM-RS antenna port of the PDSCH is quasi-co-located with at least one second RS (second QCL assumption).

[0515] In this example, the wireless device may apply a first QCL assumption to the first time slot of the PDSCH. In this example, based on the application of the first QCL assumption (or first TCI state) to the first time slot of the PDSCH, the wireless device may determine that at least one first DM-RS antenna port of the first time slot of the PDSCH is quasi-co-located with at least one first RS.

[0516] In one example, based on the determination that the PDSCH overlaps with the second core set in a time slot different from the first time slot, the wireless device can apply a second QCL assumption (or a second TCI state) to receive the PDSCH in the first time slot. In another example, based on the application of the second QCL assumption to the reception of the PDSCH in the first time slot, the wireless device can determine that at least one first DM-RS antenna port of the PDSCH in the first time slot is quasi-co-located with at least one second RS (as assumed by the second QCL).

[0517] Figure 21 , Figure 22 and Figure 23 An example of uplink multiplexing according to an embodiment of this disclosure is shown. Figure 24 yes Figure 21 , Figure 22 and Figure 23 The flowchart of uplink multiplexing is publicly available.

[0518] In an example, the wireless device can transmit a first Physical Uplink Shared Channel (PUSCH) via a first frequency resource (e.g., subcarrier, BWP, cell, frequency band) in a first time resource (e.g., symbol, microslot, time slot, subframe, frame). The first PUSCH is Figures 21 to 23 PUSCH-1 in the middle.

[0519] In an example, the wireless device can transmit a second PUSCH in a second time resource (e.g., symbol, micro-slot, slot, subframe, frame) via a second frequency resource (e.g., subcarrier, BWP, cell, band). The second PUSCH is Figures 21 to 23 PUSCH-2 in the middle.

[0520] In this example, the first frequency resource and the second frequency resource can be the same (e.g., Figure 21 , Figure 23 In an example, the first frequency resource and the second frequency resource can be different (e.g., Figure 22 In an instance, the first-time resource and the second-time resource can be the same (e.g., Figure 22 , Figure 23 In an instance, the first-time resource and the second-time resource can be different (e.g., Figure 21 ).

[0521] In an example, the wireless device can determine that the uplink control information (UCI) overlaps with (e.g., in the first time resource and the second time resource) the first PUSCH and the second PUSCH during a duration (e.g., at least one symbol, at least one microslot, at least one slot, etc.).

[0522] In this example, based on the determination that the UCI overlaps with the first PUSCH and the second PUSCH, the wireless device can select a PUSCH from the first PUSCH and the second PUSCH.

[0523] In this example, the wireless device can select a chosen PUSCH based on one or more criteria. In this example, the wireless device can select a chosen PUSCH based on a variety of criteria.

[0524] In one example, the radio device may transmit a first PUSCH on / via a first cell identified by a first cell-specific index (e.g., provided by the higher-layer parameter servCellIndex). In another example, the radio device may transmit a second PUSCH on / via a second cell identified by a second cell-specific index (e.g., provided by the higher-layer parameter servCellIndex).

[0525] The wireless device may select a PUSCH based on, for example, a first cell-specific index and a second cell-specific index. In one example, selecting a PUSCH based on a first cell-specific index and a second cell-specific index may include selecting a cell with the lowest (or highest) cell-specific index from the first and second cell-specific indexes. In another example, selecting a PUSCH based on a first cell-specific index and a second cell-specific index may include the wireless device comparing the first cell-specific index and the second cell-specific index.

[0526] In this example, based on this comparison, the wireless device can determine that a first cell-specific index is lower (or higher) than a second cell-specific index. Based on this determination, the wireless device can select the first cell as the selected cell. Based on selecting the first cell as the selected cell, the wireless device can select the first PUSCH as the selected PUSCH.

[0527] In this example, based on comparison, the wireless device can determine that a second cell-specific index is lower (or higher) than a first cell-specific index. Based on this determination, the wireless device can select the second cell as the selected cell. Based on selecting the second cell as the selected cell, the wireless device can select a second PUSCH as the selected PUSCH.

[0528] The wireless device may select a PUSCH based on, for example, a first time resource and a second time resource. In an example, selecting a PUSCH based on the first and second time resources may include selecting the earliest (or latest) selected time resource from the first and second time resources. In an example, selecting a pixel based on the first and second time resources may include the wireless device comparing the first and second time resources.

[0529] In this example, based on comparison, the wireless device can determine that a first time resource is earlier (or later) than a second time resource. Based on this determination, the wireless device can select the first time resource as the selected time resource. Based on selecting the first time resource as the selected time resource, the wireless device can select a first PUSCH as the selected PUSCH.

[0530] In this example, based on comparison, the wireless device can determine that the second time resource is earlier (or later) than the first time resource. Based on this determination, the wireless device can select the second time resource as the selected time resource. Based on selecting the second time resource as the selected time resource, the wireless device can select the second PUSCH as the selected PUSCH.

[0531] The wireless device may select a chosen PUSCH based on, for example, a first frequency resource and a second frequency resource. In one example, selecting a chosen PUSCH based on the first and second frequency resources may include selecting a lower (or higher) frequency resource from the first and second frequency resources. In another example, selecting a chosen PUSCH based on the first and second frequency resources may include the wireless device comparing the first and second frequency resources.

[0532] In this example, based on comparison, the wireless device can determine that a first frequency resource is lower (or higher) than a second frequency resource. Based on this determination, the wireless device can select the first frequency resource as the selected frequency resource. Based on selecting the first frequency resource as the selected frequency resource, the wireless device can select a first PUSCH as the selected PUSCH.

[0533] In this example, based on comparison, the wireless device can determine that the second frequency resource is lower (or higher) than the first frequency resource. Based on this determination, the wireless device can select the second frequency resource as the selected frequency resource. Based on selecting the second frequency resource as the selected frequency resource, the wireless device can select the second PUSCH as the selected PUSCH.

[0534] In one example, the wireless device can receive a first DCI in a first core set identified by a specific index of a first core set. The first DCI can schedule a first PUSCH. In another example, the wireless device can receive a second DCI in a second core set identified by a specific index of a second core set. The second DCI can schedule a second PUSCH.

[0535] The wireless device can select a PUSCH based on, for example, a first core set-specific index and a second core set-specific index. In one example, selection based on a first core set-specific index and a second core set-specific index may include selecting a core set with the lowest (or highest) core set-specific index from the first and second core set-specific indexes. In another example, selecting a PUSCH based on a first core set-specific index and a second core set-specific index may include the wireless device comparing the first and second core set-specific indexes.

[0536] In this example, based on this comparison, the wireless device can determine that an index specific to the first core set is lower (or higher) than an index specific to the second core set. Based on this determination, the wireless device can select the first core set as the selected core set. Based on selecting the first core set as the selected core set, the wireless device can select the first PUSCH as the selected PUSCH.

[0537] In this example, based on this comparison, the wireless device can determine that an index specific to the second core set is lower (or higher) than an index specific to the first core set. Based on this determination, the wireless device can select the second core set as the selected core set. Based on selecting the second core set as the selected core set, the wireless device can select the second PUSCH as the selected PUSCH.

[0538] In this example, the wireless device may be equipped with one or more antenna panels. In this example, one or more configuration parameters may indicate a panel-specific index (e.g., provided by higher-level parameters) for one or more antenna panels. In this example, each antenna panel in the one or more antenna panels may be identified by a corresponding panel-specific index. In this example, a first antenna panel of the one or more antenna panels may be identified by a first panel-specific index. In this example, a second antenna panel of the one or more antenna panels may be identified by a second panel-specific index.

[0539] In this example, wireless devices and / or base stations can use panel-specific indexes to indicate the antenna panel (or antenna panel-specific UL transmittance) of one or more antenna panels. In this example, the panel-specific index can be an SRS resource set ID. In this example, the panel-specific index can be associated with a reference RS resource and / or resource set. In this example, the panel-specific index can be associated with (or assigned to) a target RS resource and / or resource set. In this example, the panel-specific index can be configured in spatial relationship information.

[0540] In one example, the wireless device can transmit a first PUSCH via a first antenna panel identified by a specific index of the first panel. In another example, the wireless device can transmit a second PUSCH via a second antenna panel identified by a specific index of the second panel.

[0541] The wireless device can select a selected pixel based on, for example, a first panel-specific index and a second panel-specific index. In one example, selection based on a first panel-specific index and a second panel-specific index may include selecting the panel with the lowest (or highest) panel-specific index from the first and second panel-specific indexes. In another example, selecting a selected PUSCH based on a first panel-specific index and a second template-specific index may include the wireless device comparing the first template-specific index and the second template-specific index.

[0542] In this example, based on this comparison, the wireless device can determine that a specific index of the first panel is lower (higher) than a specific index of the second panel. Based on this determination, the wireless device can select the first antenna panel as the selected panel. Based on selecting the first antenna panel as the selected panel, the wireless device can select the first PUSCH as the selected PUSCH.

[0543] In this example, based on this comparison, the wireless device can determine that a specific index of the second panel is lower (or higher) than a specific index of the first panel. Based on this determination, the wireless device can select the second antenna panel as the selected panel. Based on selecting the second antenna panel as the selected panel, the wireless device can select the second PUSCH as the selected PUSCH.

[0544] The wireless device can select a PUSCH based on, for example, a first duration of a first PUSCH and a second duration of a second PUSCH. In an example, selection based on the first and second durations may include selecting the PUSCH with the lowest (or highest) PUSCH duration from the first and second durations. In another example, selecting a PUSCH based on the first and second durations may include the wireless device comparing the first and second durations.

[0545] In this example, based on this comparison, the wireless device can determine that the first duration is less than (or more than) the second duration. Based on this determination, the wireless device can select the first PUSCH as the selected PUSCH.

[0546] In this example, based on this comparison, the wireless device can determine that the second duration is shorter than (or longer than) the first duration. Based on this determination, the wireless device can select the second PUSCH as the selected PUSCH.

[0547] In this instance, the first PUSCH can be scheduled by the first DCI (e.g., dynamic uplink grant). In this instance, the second PUSCH can be scheduled by the second DCI (e.g., dynamic uplink grant).

[0548] In this instance, the first PUSCH may be transmitted via a first periodic uplink resource configured by a first configured uplink grant (e.g., a configured uplink grant). In this instance, the second PUSCH may be scheduled by a second DCI (e.g., a dynamic uplink grant).

[0549] In one example, the wireless device may select a PUSCH based on, for example, a first service of the first PUSCH (e.g., URLLC, eMBB, mMTC) and a second service of the second PUSCH (e.g., URLLC, eMBB, mMTC). In another example, selection based on the first and second services may include selecting the PUSCH with the highest priority from the first and second services. In yet another example, selecting a PUSCH based on the first and second services may include the wireless device comparing the first priority of the first PUSCH and the second priority of the second PUSCH.

[0550] In this example, based on this comparison, the wireless device can determine that the first priority of the first service is higher than the second priority of the second service. Based on this determination, the wireless device can select the first PUSCH as the selected PUSCH.

[0551] In this example, based on this comparison, the wireless device can determine that the first priority of the first service is lower than the second priority of the second service. Based on this determination, the wireless device can select the second PUSCH as the selected PUSCH.

[0552] In this instance, the first PUSCH can be scheduled by the first DCI (e.g., dynamic uplink grant). In this instance, the second PUSCH can be scheduled by the second DCI (e.g., dynamic uplink grant).

[0553] In this instance, the first PUSCH may be transmitted via a first periodic uplink resource configured by a first configured uplink grant (e.g., a configured uplink grant). In this instance, the second PUSCH may be scheduled by a second DCI (e.g., a dynamic uplink grant).

[0554] In an example, the wireless device may select a PUSCH based on, for example, a first group of UCI (e.g., TCI state group, antenna port group, HARQ process group, core cluster group), a second group of the first PUSCH, and a third group of the second PUSCH. In an example, selecting a PUSCH based on the first, second, and third groups may include selecting a PUSCH that shares the same group as the first group of UCI (e.g., the second and third groups). In an example, the first and second groups may be the same. In an example, the first and third groups may be different. Based on the first and second groups being the same and the first and third groups being different, the wireless device may select the first PUSCH associated with the second group as the selected PUSCH. In an example, the first and third groups may be the same. In an example, the first and second groups may be different. Based on the first and third groups being the same and the first and second groups being different, the wireless device may select the second PUSCH associated with the third group as the selected PUSCH.

[0555] In this example, based on the selection of a chosen PUSCH, the wireless device multiplexes the UCI within that chosen PUSCH. The wireless device can then transmit the chosen PUSCH with the UCI based on / after multiplexing.

[0556] Figure 25 An example of uplink multiplexing according to an embodiment of this disclosure is shown. Figure 26 yes Figure 25 The flowchart of uplink multiplexing is publicly available.

[0557] In this example, the wireless device can receive one or more messages. These messages may include one or more configuration parameters.

[0558] In this instance, one or more configuration parameters can indicate one or more core sets. In this instance, one or more core sets can be grouped / formed into one or more core cluster groups, including a first core cluster group and a second core cluster group. In this instance, a first core cluster group within one or more core cluster groups may include a first core set. In this instance, a second core cluster group within one or more core cluster groups may include a second core set.

[0559] In this instance, one or more configuration parameters can indicate configured uplink permissions. Configured uplink permissions can indicate a second time resource. Configured uplink permissions can indicate a second frequency resource. In this instance, the second time resource can be periodic. In this instance, one or more configuration parameters can associate configured uplink permissions with a second core cluster group. In this instance, one or more configuration parameters can indicate an identifier for the second core cluster group in the configuration of the configured uplink permissions. In this instance, one or more configuration parameters can indicate an identifier for the second core cluster group of the configured uplink permissions (e.g., TCI state group, TRP ID, antenna port group, HARQ process group, core cluster group).

[0560] In this instance, the wireless device can receive the first DCI. In this instance, the wireless device can receive the first DCI in the first core set of the first core cluster group (one or more core cluster groups). In this instance, the first DCI can schedule the transmission of the first PUSCH in the first resource.

[0561] In one example, the wireless device may determine that for configured uplink granting, a first time resource overlaps with a second time resource of a second PUSCH. In another example, determining that the first and second time resources overlap may include the first and second PUSCHs overlapping for a duration (e.g., at least one symbol, at least one microslot, at least one slot, etc.).

[0562] In this example, the wireless device can determine that the UCI overlaps with the first PUSCH and the second PUSCH during the duration. In this example, the wireless device can receive the second DCI in the second core set of the second core cluster group (one or more core cluster groups). In this example, the second DCI can schedule the second PDSCH. In this example, the wireless device can transmit the UCI of the PDSCH scheduled by the second DCI (received in the second core set).

[0563] In this example, based on the determination that the UCI of the PDSCH scheduled by the second DCI is received in the second core set associated with the second core cluster group, the radio device can multiplex the UCI in the second PUSCH for a duration. The radio device can then transmit a second PUSCH with the UCI based on this multiplexing.

[0564] In this example, based on determining that the UCI overlaps with the first and second PUSCHs during the duration, the wireless device can select a PUSCH from the first and second PUSCHs based on whether the second core set belongs to the first or second core cluster group. In this example, based on this selection, the wireless device can reuse the UCI in the selected PUSCH. In this example, the wireless device can... Figures 21 to 23 One or more criteria are discussed in the text to select the chosen PUSCH.

[0565] In this example, the transmission of Uplink Control Information (UCI) may overlap with the transmission of transport blocks in time. A radio device may not simultaneously transmit UCI via Physical Uplink Control Channel (PUCCH) resources and transmit transport blocks via Physical Uplink Shared Channel (PUSCH) resources. A radio device may not be able to transmit PUSCH and PUCCH simultaneously. In this example, PUCCH and PUSCH resources may be on / in the same cell. A radio device may reuse UCI from PUSCH resources. A radio device may reuse UCI from PUSCH resources because it cannot transmit PUSCH and PUCCH simultaneously. Based on this reuse, the radio device can transmit UCI via PUSCH resources.

[0566] In this example, the wireless device may be served by multiple TRPs, including a first TRP and a second TRP. The backhaul between the first and second TRPs may be non-ideal (e.g., 5ms latency, 10ms latency, 50ms latency, etc.). Because the backhaul is non-ideal, scheduling decisions at the first and second TRPs may be independent. Independent scheduling decisions at the first and second TRPs can lead to conflicts (e.g., PUCCH / PUSCH conflicts between the first and second TRPs). For example, when the first TRP schedules the transmission of a transport block via a PUSCH resource in a time slot, the second TRP may configure / instruct the transmission of a UCI via a PUCCH resource in the same time slot. The transmission of a transport block via the first TRP's PUSCH resource may overlap with the UCI via the second TRP's PUCCH resource in the same time slot. The wireless device may not simultaneously transmit a transport block to the first TRP and transmit a UCI to the second TRP.

[0567] The implementation of legacy behaviors, where a radio device reuses a UCI of a second TRP within the PUSCH resources of a first TRP, can lead to performance degradation. For example, when a radio device transmits a UCI via PUSCH resources, the first TRP may not be aware that the UCI is multiplexed in the PUSCH resources due to a non-ideal backhaul (e.g., long latency). Based on this lack of awareness of UCI multiplexing in the PUSCH resources, the first TRP may not decode / receive transport blocks transmitted via the PUSCH resources. This can reduce data rates and / or increase latency / wait time for successful communication. Similarly, based on a non-ideal backhaul, the second TRP may not be aware that the UCI is multiplexed in the first TRP's PUSCH resources. When a radio device transmits a UCI via the first TRP's PUSCH resources, the second TRP may not receive the UCI. If the UCI is an ACK / NACK for a PDSCH scheduled by the second TRP, the second TRP may transmit downlink control information (DCI) to reschedule the PDSCH based on the failure to receive the UCI. This can increase signaling overhead. When a wireless device is served by multiple TRPs, it is necessary to enhance the multiplexing of UCI in the PUSCH resources.

[0568] In an example, when multiple TRPs serve a radio device, the PUCCH resource of the UCI can overlap temporally with the PUSCH resource of a transport block. In an example embodiment, when the UCI and PUSCH resources are configured / indicated for (or belong to) the same TRP, the radio device can multiplex the UCI in the PUSCH resource. For example, the UCI and PUSCH resources can be configured / indicated for (or may belong to) a first TRP among multiple TRPs. The radio device can multiplex the UCI of the first TRP in the PUSCH resource of the first TRP and transmit via the PUSCH resource of the first TRP. The first TRP may know that the PUCCH resource overlaps temporally with the PUSCH resource. The first TRP may know that the UCI in the PUSCH resource is multiplexed. The first TRP can successfully decode / receive the transport block and the UCI based on its knowledge of the multiplexing. In an example embodiment, when the UCI and PUSCH resources are configured / indicated for (or belong to) different TRPs, the radio device may not multiplex the UCI in the PUSCH resource.

[0569] In this example, multiplexing the UCI in the PUSCH resource when the UCI and PUSCH are configured / indicated for the same TRP, and not multiplexing the UCI in the PUSCH resource when the UCI and PUSCH are configured / indicated for different TRPs, can reduce data communication latency / delay. This reduces signaling overhead. This can increase the data rate. Reducing signaling overhead and latency / delay can reduce power consumption at the radio device and / or base station.

[0570] In this example, the wireless device can distinguish PUCCH / PUSCH resources configured / indicated for (or belonging to) TRP.

[0571] In this example, a wireless device can receive DCIs via PUSCH resource scheduling blocks through a control resource set (core set). The base station can configure the core set to have a core set pool index (or TRP index or core set group index). The core set pool index indicates the TRP of the PUSCH resource. Based on the core set pool index of the core set through which the wireless device receives the DCI, the wireless device can determine the TRP of the PUSCH resource. For example, a first TRP can be transmitted via one or more first core sets configured with a first core set pool index equal to zero. A second TRP can be transmitted via one or more second core sets configured with a second core set pool index equal to one. A first TRP may not be transmitted via one or more second core sets. A second TRP may not be transmitted via one or more first core sets. When the wireless device receives the DCI via a core set with a first core set pool index, the PUSCH resource can be associated with the first TRP. When the wireless device receives the DCI via a core set with a second core set pool index, the PUSCH resource can be associated with the second TRP.

[0572] In this example, the radio device may not receive the DCI for scheduling transport blocks for a configured uplink permission (e.g., a Type-1 configured uplink permission). The base station may activate the configured uplink permission without transmitting the DCI via the core set. Based on the absence of a received DCI for the configured uplink permission, the radio device may not distinguish the TRP of the PUSCH resources for the configured uplink permission. In this example, the base station may configure the core set pool index for the configured uplink permission. The radio device may distinguish the TRP of the PUSCH resources for the configured uplink permission based on the core set pool index configured for the configured uplink permission. For example, a first configured uplink permission can be configured using an RRC configuration parameter transmitted by the base station with a first core set pool index equal to zero. A second configured uplink permission can be configured using an RRC configuration parameter transmitted by the base station with a second core set pool index equal to one. The uplink grant configuration based on the first configuration has a first core pool index equal to zero, and the PUSCH resources granted by the uplink grant configuration based on the first configuration are associated with the first TRP. The uplink grant configuration based on the second configuration has a second core pool index equal to one, and the PUSCH resources granted by the uplink grant configuration based on the second configuration can be associated with the second TRP.

[0573] Based on distinguishing PUCCH / PUSCH resources configured / indicated for (or belonging to) a TRP across multiple TRPs, the radio device may or may not reuse the UCI in the PUSCH resource. This reduces signaling overhead. This increases data rate. Reducing signaling overhead and latency / delay can lower power consumption at the radio device and / or base station.

[0574] According to various embodiments, an apparatus (e.g., a wireless device, an off-grid wireless device, a base station, etc.) may include one or more processors and a memory. The memory may store instructions that, when executed by the one or more processors, cause the apparatus to perform a series of actions. Embodiments of exemplary action are illustrated in the accompanying drawings and description. Features from various embodiments may be combined to create other embodiments.

[0575] Figure 27 This is a flowchart illustrating an aspect of an embodiment according to the present disclosure. At 2710, the wireless device may receive one or more Radio Resource Control (RRC) messages. One or more RRC messages may include configuration parameters for configured uplink grants. One or more RRC messages may include a first control resource set (core set) group index associated with the configured uplink grant. At 2720, the wireless device may determine that the Physical Uplink Control Channel (PUCCH) resource (UCI) of the uplink control information overlaps temporally with the Physical Uplink Shared Channel (PUSCH) resource of the configured uplink grant. At 2730, the wireless device may determine that the core trunking group index associated with the PUCCH resource is the same as the first core trunking group index. At 2740, based on the determination that the PUCCH resource and the PUSCH resource overlap temporally and that the core trunking group index is the same as the first core trunking group index, the wireless device may reuse the UCI in the PUSCH resource. At 2750, the wireless device may transmit the UCI via the PUSCH resource.

[0576] Figure 28This is a flowchart illustrating an aspect of an exemplary embodiment of this disclosure. At 2810, the base station may transmit one or more Radio Resource Control (RRC) messages. The one or more RRC messages may include configuration parameters for configured uplink grants. The one or more RRC messages may include a first control resource set (core set) group index associated with the configured uplink grant. At 2820, the base station may determine that the Physical Uplink Control Channel (PUCCH) resource (UCI) of the uplink control information overlaps temporally with the Physical Uplink Shared Channel (PUSCH) resource of the configured uplink grant. At 2830, the base station may determine that the core trunking group index associated with the PUCCH resource is the same as the first core trunking group index. At 2840, based on the determination that the PUCCH resource and the PUSCH resource overlap temporally and that the core trunking group index is the same as the first core trunking group index, the base station may receive the UCI via the PUSCH resource.

[0577] According to an example embodiment, the wireless device can receive one or more Radio Resource Control (RRC) messages. The one or more RRC messages may include configuration parameters for configured uplink grants. The one or more RRC messages may include a first control resource set (core set) group index associated with the configured uplink grant. According to an example embodiment, the wireless device can determine that the Physical Uplink Control Channel (PUCCH) resource (UCI) of the uplink control information overlaps temporally with the Physical Uplink Shared Channel (PUSCH) resource of the configured uplink grant. According to an example embodiment, the wireless device can determine that the core trunking group index associated with the PUCCH resource is the same as the first core trunking group index. According to an example embodiment, based on the determination that the PUCCH resource and the PUSCH resource overlap temporally and that the core trunking group index is the same as the first core trunking group index, the wireless device can reuse the UCI in the PUSCH resource. According to an example embodiment, the wireless device can transmit the UCI via the PUSCH resource.

[0578] According to an example embodiment, based on the fact that the second PUCCH resource for determining the second UCI overlaps in time with the configured uplink-granted second PUSCH resource, and that the core cluster group index associated with the second PUCCH resource is different from the first core cluster group index, the radio device can transmit the second UCI via the second PUCCH resource. According to an example embodiment, the radio device may not reuse the second UCI in the second PUSCH resource.

[0579] According to the example implementation, the first core set index can identify the first core set associated with the configured uplink permission.

[0580] According to an example implementation, one or more RRC messages may include the core cluster group index of the PUCCH resource.

[0581] According to an example embodiment, the PUCCH resource associated with the core cluster group index may include receiving downlink control information (DCI) via a core set having the core cluster group index. The DCI may schedule the Physical Downlink Shared Channel (PDSCH). The DCI may instruct the PUCCH resource to be used for the transmission of the UCI for the PDSCH. According to an example embodiment, one or more RRC messages may include the core cluster group index of the core set. According to an example embodiment, the UCI may be a Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) for the PDSCH.

[0582] According to an example embodiment, a temporally overlapping UCI may include a UCI overlapping in at least one symbol. According to an example embodiment, a temporally overlapping UCI may include a UCI overlapping in at least one microslot. According to an example embodiment, a temporally overlapping UCI may include a UCI overlapping in at least one slot.

[0583] According to an example embodiment, the UCI may include a scheduling request. According to an example embodiment, the UCI may include a HARQ-ACK. According to an example embodiment, the UCI may include a Channel State Information (CSI) report.

[0584] According to an example embodiment, the configured uplink permission can be used to transmit transport blocks to a transmit-receive point (TRP) associated with a first core set index. According to an example embodiment, the TRP associated with the first core set index may include a TRP that transmits one or more downlink control messages via one or more first core sets having the first core set index. According to an example embodiment, the TRP associated with the first core set index may include a TRP that does not transmit one or more downlink control messages via one or more second core sets having a second core set index different from the first core set index. According to an example embodiment, one or more RRC messages may include the first core set index of one or more first core sets. According to an example embodiment, one or more RRC messages may include the second core set index of one or more second core sets.

[0585] According to an example embodiment, the wireless device can receive one or more Radio Resource Control (RRC) messages. The one or more RRC messages may include configuration parameters for configured uplink grants. The one or more RRC messages may include a first core trunking group index associated with the configured uplink grant. According to an example embodiment, based on the determination that the Physical Uplink Control Channel (PUCCH) resource and the PUSCH resource of the UCI overlap in time; and that the core trunking group index associated with the PUCCH resource is the same as the first core trunking group index, the wireless device can reuse uplink control information in the Physical Uplink Shared Channel (PUSCH) resource of the configured uplink grant. According to an example embodiment, the wireless device can transmit the UCI via the PUSCH resource.

[0586] According to an example embodiment, the wireless device can receive one or more Radio Resource Control (RRC) messages. The one or more RRC messages may include configuration parameters for configured uplink grants. The one or more RRC messages may include a first core trunking group index associated with the configured uplink grant. According to an example embodiment, based on the determination that the Physical Uplink Control Channel (PUCCH) resources and PUSCH resources of the UCI overlap in time; and that the core trunking group index associated with the PUCCH resources is the same as the first core trunking group index, the wireless device can transmit uplink control information (UCI) via the configured uplink granted Physical Uplink Shared Channel (PUSCH) resources.

[0587] According to an example embodiment, the wireless device may receive one or more Radio Resource Control (RRC) messages. The one or more RRC messages may include configuration parameters for configured uplink permissions. The one or more RRC messages may include a first control resource set (core set) group index associated with the configured uplink permissions. According to an example embodiment, the wireless device may determine uplink control information (UCI) for reusing resources with configured uplink permissions based on the first core set group index. According to an example embodiment, the wireless device may transmit the UCI via resources.

[0588] According to an example embodiment, the wireless device may receive one or more Radio Resource Control (RRC) messages. The one or more RRC messages may include a first control resource set (core set) group index associated with a configured uplink grant. According to an example embodiment, the wireless device may transmit uplink control information (UCI) via the resources of the configured uplink grant based on the first core set group index.

[0589] According to an example embodiment, the wireless device may receive one or more Radio Resource Control (RRC) messages. The one or more RRC messages may include configuration parameters for configured uplink permissions. The one or more RRC messages may include a first control resource set (core set) group index associated with the configured uplink permissions. According to an example embodiment, the wireless device may transmit transport blocks via the configured uplink permissions resources based on the first core set group index.

[0590] According to an example embodiment, the wireless device may receive one or more Radio Resource Control (RRC) messages. The one or more RRC messages may include configuration parameters for configured uplink grants. The one or more RRC messages may include a first control resource set (core set) group index for configured uplink grants. According to an example embodiment, the wireless device may transmit transport blocks via the configured uplink-granted resources based on the first core set group index.

[0591] According to an example embodiment, the wireless device can receive one or more Radio Resource Control (RRC) messages. The one or more RRC messages may include configuration parameters for configured uplink grants. The one or more RRC messages may include a first control resource set (core set) group index for configured uplink grants. According to an example embodiment, the wireless device can transmit uplink control information based on the first core set group index via the configured uplink granted resources.

[0592] According to an example embodiment, the wireless device may receive one or more Radio Resource Control (RRC) messages. The one or more RRC messages may include a first control resource set (core set) group index associated with a configured uplink grant. According to an example embodiment, the wireless device may transmit uplink control information (UCI) via the resources of the configured uplink grant based on the first core set group index.

[0593] According to an example embodiment, the configured uplink grant may have type 1. According to an example embodiment, one or more RRC messages may include configuration parameters for the configured uplink grant having type 1. According to an example embodiment, the resource may be a Physical Uplink Shared Channel (PUSCH) resource. According to an example embodiment, the radio device may determine that the Physical Uplink Control Channel (PUCCH) resource of the UCI overlaps in time with the PUSCH resource of the configured uplink grant; and that the core cluster group index associated with the PUCCH resource is the same as the first core cluster group index. According to an example embodiment, transmitting the UCI based on the first core cluster group index may include determining the UCI in the multiplexed PUSCH resource; and transmitting the UCI via the PUSCH resource.

[0594] According to an example embodiment, the wireless device can receive downlink control information (DCI) in a control resource set (core set) having a first core cluster group index. According to an example embodiment, the DCI can schedule the transmission of a transport block via a Physical Uplink Shared Channel (PUSCH) resource. According to an example embodiment, the wireless device can determine that the Physical Uplink Control Channel (PUCCH) resource of the uplink control information (UCI) overlaps temporally with the PUSCH resource of the transport block. According to an example embodiment, the wireless device can determine that the core cluster group index associated with the PUCCH resource is the same as the first core cluster group index. According to an example embodiment, based on the determination that the PUCCH resource and the PUSCH resource overlap temporally and that the core cluster group index is the same as the first core cluster group index, the wireless device can reuse the UCI in the PUSCH resource. According to an example embodiment, the wireless device can transmit the UCI via the PUSCH resource.

[0595] According to an example embodiment, the wireless device can receive a second DCI in a second core set having a second core cluster group index. According to an example embodiment, the second DCI can schedule the transmission of a second transport block via a second PUSCH resource. According to an example embodiment, based on the fact that the second PUSCH resource of the second UCI overlaps with the second PUSCH resource of the second transport block in time, and that the core cluster group index associated with the second PUSCH resource is different from the second core cluster group index, the wireless device can transmit the second UCI via the second PUSCH resource. According to an example embodiment, the wireless device can choose not to reuse the second UCI in the second PUSCH resource.

[0596] According to an example embodiment, the PUCCH resource associated with the core cluster group index may include a DCI received via a core set having the core cluster group index. The second DCI may schedule a Physical Downlink Shared Channel (PDSCH). The second DCI may instruct the PUCCH resource to be used for the transmission of a UCI for the PDSCH.

[0597] According to an example embodiment, the wireless device can receive one or more Radio Resource Control (RRC) messages that include configuration parameters. According to an example embodiment, the configuration parameters may indicate the core cluster group index of the PUCCH resource. According to an example embodiment, the configuration parameters may indicate the core cluster group index of the core set.

[0598] According to an example embodiment, the wireless device can receive one or more Radio Resource Control (RRC) messages. The one or more RRC messages may include configuration parameters for configured uplink grants. The one or more RRC messages may include a first control resource set (core set) group index associated with the configured uplink grant. According to an example embodiment, if the Physical Uplink Control Channel (PUCCH) resource based on uplink control information (UCI) overlaps in time with the Physical Uplink Shared Channel (PUSCH) resource of the configured uplink grant, the wireless device can determine whether the core trunking group index associated with the PUCCH resource is the same as a first core trunking group index. According to an example embodiment, based on the determination that the core trunking group index and the first core trunking group index are the same, the wireless device can reuse the UCI in the PUSCH resource. According to an example embodiment, the wireless device can transmit UCI via the PUSCH resource.

[0599] According to an example embodiment, the wireless device can determine that the Physical Uplink Control Channel (PUCCH) resource (UCI) for uplink control information overlaps with a first Physical Uplink Shared Channel (PUSCH) resource and a second PUSCH resource in time. The PUCCH resource can be associated with a first core cluster group index. The first PUSCH resource can be associated with a second core cluster group index. The second PUSCH resource can be associated with a third core cluster group index. According to an example embodiment, the wireless device can select a PUSCH resource from the first and second PUSCH resources based on the first, second, and third core cluster group indices. According to an example embodiment, the wireless device can reuse the UCI in the selected PUSCH resource. According to an example embodiment, the wireless device can transmit the UCI via the selected PUSCH resource.

[0600] According to an example embodiment, selecting a PUSCH resource based on a first core cluster group index, a second core cluster group index, and a third core cluster group index may include selecting a PUSCH resource associated with a core cluster group index that is the same as the first core cluster group index. According to an example embodiment, the wireless device may select a first PUSCH resource as the selected PUSCH resource based on the first core cluster group index being the same as the second core cluster group index, and the first core cluster group index and the third core cluster group index being different. According to an example embodiment, the wireless device may select a second PUSCH resource as the selected PUSCH resource based on the first core cluster group index and the third core cluster group index being the same, and the first core cluster group index and the second core cluster group index being different.

[0601] According to an example embodiment, the PUCCH resource associated with the first core set index may include receiving downlink control information (DCI) via a first core set having the first core set index. The DCI may schedule the Physical Downlink Shared Channel (PDSCH). The DCI may instruct the PUCCH resource to be used for the transmission of UCI for the PDSCH.

[0602] According to an example embodiment, a first PUSCH resource associated with a second core cluster group index may include receiving a second DCI via a second core set having the second core cluster group index. The second DCI may schedule a first transport block via the first PUSCH resource. According to an example embodiment, a second PUSCH resource associated with a third core cluster group index may include receiving a third DCI via a third core set having the third core cluster group index. The third DCI may schedule a second transport block via the second PUSCH resource. According to an example embodiment, the second core set may be identified by a first core set index. According to an example embodiment, the third core set may be identified by a second core set index. According to an example embodiment, selecting a selected PUSCH resource may be further based on the first core set index and the second core set index. According to an example embodiment, selecting a selected PUSCH resource based on the first core set index and the second core set index may include selecting the first PUSCH resource as the selected PUSCH resource based on whether the first core set index is higher or lower than the second core set index.

[0603] According to an example embodiment, the wireless device can receive one or more messages including one or more configuration parameters. The one or more configuration parameters may indicate a second core cluster group index granted by a first configured uplink. According to an example embodiment, the one or more configuration parameters may indicate a third core cluster group index granted by a second configured uplink. According to an example embodiment, a first PUSCH resource associated with the second core cluster group index may include transmitting a first transport block via the first PUSCH resource granted by the first configured uplink. According to an example embodiment, a second PUSCH resource associated with the third core cluster group index may include transmitting a second transport block via the second PUSCH resource granted by the second configured uplink.

[0604] According to an example embodiment, a wireless device can transmit UCI based on multiplexing UCI in a selected PUSCH resource.

[0605] According to an example embodiment, the wireless device may transmit a first transport block via a first PUSCH resource of a first cell identified by a first cell index. According to an example embodiment, the wireless device may transmit a second transport block via a second PUSCH resource of a second cell identified by a second cell index. According to an example embodiment, selecting a selected PUSCH resource may be further based on the first cell index and the second cell index. According to an example embodiment, selecting a selected PUSCH resource based on the first cell index and the second cell index may include selecting the first PUSCH resource as the selected PUSCH resource based on whether the first cell index is lower or higher than the second cell index.

[0606] According to an example embodiment, the first PUSCH resource may include a first time resource. According to an example embodiment, the second PUSCH resource may include a second time resource. According to an example embodiment, selecting the selected "PUSCH" resource may be further based on the first time resource and the second time resource. According to an example embodiment, selecting the selected PUSCH resource based on the first time resource and the second time resource may include selecting the first PUSCH resource as the selected PUSCH resource based on the first time resource being earlier or later than the second time resource in time.

[0607] According to an example embodiment, the first PUSCH resource may include a first frequency resource. According to an example embodiment, the second PUSCH resource may include a second frequency resource. According to an example embodiment, selecting the selected PUSCH resource may be further based on the first frequency resource and the second frequency resource. According to an example embodiment, selecting the selected PUSCH resource based on the first frequency resource and the second frequency resource may include selecting the first PUSCH resource as the selected PUSCH resource based on the first frequency resource being higher or lower than the second frequency resource in frequency.

[0608] According to an example embodiment, a wireless device may transmit a first transport block via a first PUSCH resource having a first antenna panel identified by a first antenna panel index. According to an example embodiment, a wireless device may transmit a second transport block via a second PUSCH resource having a second antenna panel identified by a second antenna panel index. According to an example embodiment, selecting a selected PUSCH resource may be further based on the first antenna panel index and the second antenna panel index. According to an example embodiment, selecting a selected PUSCH resource based on the first antenna panel index and the second antenna panel index may include selecting the first PUSCH resource as the selected PUSCH resource based on whether the first antenna panel index is higher or lower than the second antenna panel index.

[0609] According to an example embodiment, selecting a PUSCH resource may be further based on a first duration of a first PUSCH resource and a second duration of a second PUSCH resource. According to an example embodiment, selecting a PUSCH resource based on the first and second durations may include selecting the first PUSCH resource as the selected PUSCH resource based on the first duration being longer or shorter than the second duration in time.

[0610] According to an example embodiment, selecting a chosen PUSCH resource may be further based on a first service type of the first PUSCH resource and a second service type of the second PUSCH resource. According to an example embodiment, selecting a chosen PUSCH resource based on the first and second service types may include selecting the first PUSCH resource as the chosen PUSCH resource based on whether the first service type has a higher or lower priority than the second service type. According to an example embodiment, the first service type may be enhanced mobile broadband (eMBB). According to an example embodiment, the first service type may be ultra-reliable low latency communication (uRLLC). According to an example embodiment, the first service type may be massive machine-type communication (mMTC).

[0611] According to an example embodiment, the wireless device can receive downlink control information (DCI) via a first control resource set (core set) having a first core cluster group index. The DCI can schedule the Physical Downlink Shared Channel (PDSCH). According to an example embodiment, the wireless device can determine that the PDSCH overlaps in time with a second core set having a second core cluster group index and a third core set having a third core cluster group index. According to an example embodiment, in response to determining that the PDSCH overlaps in time with the second and third core sets, the wireless device can select a selected core set based on the first, second, and third core cluster group indices. According to an example embodiment, the wireless device can receive the PDSCH based on a reference signal associated with the selected core set.

[0612] According to an example embodiment, selecting a core set may include selecting a core set that has the same core cluster group index as the first core cluster group index. According to an example embodiment, based on the fact that the second core cluster group index is the same as the first core cluster group index, and the third core cluster group index is different from the first core cluster group index, the selected core set may be the second core set. According to an example embodiment, based on the fact that the third core cluster group index is the same as the first core cluster group index, and the second core cluster group index is different from the first core cluster group index, the selected core set may be the third core set.

[0613] According to an example embodiment, a base station may transmit one or more Radio Resource Control (RRC) messages. The one or more RRC messages may include configuration parameters for configured uplink grants. The one or more RRC messages may include a first core trunking group index associated with the configured uplink grant. According to an example embodiment, the base station may determine that the Physical Uplink Control Channel (PUCCH) resource (UCI) of the uplink control information overlaps in time with the Physical Uplink Shared Channel (PUSCH) resource of the configured uplink grant. According to an example embodiment, the base station may determine that the core trunking group index associated with the PUCCH resource is the same as the first core trunking group index. According to an example embodiment, based on the determination that the PUCCH resource and the PUSCH resource overlap in time and that the core trunking group index is the same as the first core trunking group index, the base station may receive the UCI via the configured uplink PUSCH resource.

[0614] According to an example embodiment, a base station may transmit one or more Radio Resource Control (RRC) messages. The one or more RRC messages may include a first core trunking group index associated with a configured uplink grant. According to an example embodiment, based on the first core trunking group index, the base station may receive uplink control information (UCI) via the resources granted for the configured uplink grant.

[0615] The embodiments can be configured to operate as needed. The disclosed mechanisms can be executed when certain criteria are met, such as in a wireless device, base station, radio environment, network, or combination thereof. Instance criteria may be based at least in part on, for example, wireless device or network node configuration, traffic load, initial system setup, packet size, service characteristics, or combinations thereof. Various exemplary embodiments can be applied when one or more criteria are met. Therefore, exemplary embodiments selectively implementing the disclosed protocols can be implemented.

[0616] A base station can communicate with a mixture of wireless devices. The wireless devices and / or base stations can support multiple technologies and / or multiple versions of the same technology. Wireless devices may have certain specific capabilities, depending on the wireless device category and / or capabilities. A base station may include multiple sectors. When this disclosure refers to a base station communicating with multiple wireless devices, this disclosure may mean a subset of the total number of wireless devices in the coverage area. For example, this disclosure may mean multiple wireless devices having a given capability and in a given sector of a base station with a given LTE or 5G version. Multiple wireless devices in this disclosure may refer to a selected set of wireless devices, and / or a subset of the total number of wireless devices in the coverage area performing according to the disclosed method, etc. Multiple base stations or multiple wireless devices may exist in the coverage area that may not conform to the disclosed method, for example, because these wireless devices or base stations are based on older versions of LTE or 5G technology.

[0617] In this disclosure, “a” and “an” and similar phrases will be interpreted as “at least one” and “one or more”. Similarly, any term ending with the suffix “(s)” will be interpreted as “at least one” and “one or more”. In this disclosure, the term “may” is interpreted as “may, for example”. In other words, the term “may” indicates that the phrase following the term “may” is an instance of one of a variety of suitable possibilities that may or may not be used in one or more of the various embodiments.

[0618] If A and B are sets, and every element of A is also an element of B, then A is called a subset of B. In this specification, only non-empty sets and subsets are considered. For example, possible subsets of B = {cell1, cell2} are: {cell1}, {cell2}, and {cell1, cell2}. The phrase "based on" (or equivalently "at least based on") indicates that the phrase following the term "based on" is an instance of one of a variety of suitable possibilities that may or may not be used in one or more different embodiments. The phrase "in response to" (or equivalently "at least in response to") indicates that the phrase following the phrase "in response to" is an instance of one of a variety of suitable possibilities that may or may not be used in one or more different embodiments. The phrase "depends on" (or equivalently "at least depends on") indicates that the phrase following the phrase "depends on" is an instance of one of a variety of suitable possibilities that may or may not be used in one or more different embodiments. The phrase "adopts / uses" (or equivalently "at least adopts / uses") indicates that the phrase following the phrase "adopts / uses" is an instance of one of a variety of suitable possibilities that may or may not be used in one or more different embodiments.

[0619] The term "configurable" can refer to the capabilities of a device, whether the device is in an operational or non-operational state. "Configurable" can also mean specific settings within the device that affect its operational characteristics, regardless of whether the device is in an operational or non-operational state. In other words, hardware, software, firmware, registers, memory values, etc., can be "configured" within the device to provide specific characteristics to the device, whether the device is in an operational or non-operational state. Similarly, the term "control messages generated in the device" can mean that the control messages have parameters that can be used to configure specific characteristics in the device or to implement certain actions in the device, regardless of whether the device is in an operational or non-operational state.

[0620] Various embodiments are disclosed in this disclosure. Limitations, features, and / or elements from the disclosed exemplary embodiments may be combined to create other embodiments within the scope of this disclosure.

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

[0622] Furthermore, many of the features presented above are described as optional using the use of "may" or parentheses. For brevity and readability, this disclosure does not explicitly describe every permutation that can be obtained by selecting from the group of optional features. However, this disclosure should be interpreted as explicitly disclosing all such permutations. For example, a system described as having three optional features can be embodied in seven different ways: having only one of the three possible features, having any two of the three possible features, or having all three of the three possible features.

[0623] Many of the elements described in the disclosed embodiments can be implemented as modules. A module is defined herein as an element that performs the defined function and has defined interfaces to other elements. Modules described in this disclosure can be implemented in hardware, software combined with hardware, firmware, wet hardware (i.e., hardware with biological elements), or combinations thereof, all of which may be behaviorally equivalent. For example, a module can be implemented as software routines written in a computer language configured to be executed by a hardware machine (e.g., C, C++, Fortran, Java, Basic, Matlab, etc.) or a modeling / simulation program (e.g., Simulink, Stateflow, GNU Octave, or LabVIEW MathScript). Alternatively, it is possible to implement modules using physical hardware incorporating discrete or programmable analog, digital, and / or quantum hardware. Examples of programmable hardware include: computers, microcontrollers, microprocessors, application-specific integrated circuits (ASICs); field-programmable gate arrays (FPGAs); and complex programmable logic devices (CPLDs). Computers, microcontrollers, and microprocessors are programmed using languages ​​such as assembly, C, and C++. FPGAs, ASICs, and CPLDs are frequently programmed using Hardware Description Languages ​​(HDLs), such as VHSIC Hardware Description Language (VHDL) or Verilog. These languages ​​configure connections between a limited number of internal hardware modules on a programmable device. The techniques mentioned above are often used in combination to achieve the desired functional module results.

[0624] The disclosure of this patent document incorporates copyrighted material. The copyright holder does not object to anyone making an exact copy of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office's patent documents or records for limited purposes required by law, but otherwise reserves all copyright rights.

[0625] Although various embodiments have been described above, it should be understood that they are presented by way of example and not limitation. Those skilled in the art will appreciate that various changes in form and detail may be made therein without departing from the scope of the invention. Indeed, after reading the above description, it will be apparent to those skilled in the art how alternative embodiments can be implemented. Therefore, the present embodiments should not be limited to any of the exemplary embodiments described above.

[0626] Furthermore, it should be understood that any diagrams highlighting functionality and advantages are given for illustrative purpo...

Claims

1. A method comprising: The wireless device receives downlink control information (DCI) via a first coreset having a first control resource set (coreset) group index, and the DCI schedules the reception of the physical downlink shared channel (PDSCH). Sure: The first quasi-co-address Type D of the PDSCH reception differs from the second quasi-co-address Type D of the Physical Downlink Control Channel (PDCCH) reception, which is received via a second coreset, and the PDCCH reception overlaps with the PDSCH reception on at least one symbol; and The first coreset group index is the same as the second coreset group index of the second coreset; as well as Based on the determination, the PDCCH received via the second coreset is prioritized.

2. The method according to claim 1, wherein the time offset between the DCI and the PDSCH reception is less than a threshold.

3. The method according to claim 2 further includes transmitting user equipment (UE) capability information indicating the threshold to the base station.

4. The method according to claim 2 or 3, further comprising determining the first quasi-co-address TypeD received by the PDSCH based on the quasi-co-address of the coreset with the lowest coreset index.

5. The method of claim 4, wherein determining the first quasi-co-address TypeD based on the quasi-co-address of the coreset is performed in response to the time offset being less than the threshold.

6. A wireless device, comprising: One or more processors; and A memory for storing instructions that, when executed by the one or more processors, cause the wireless device to perform the method according to any one of claims 1 to 5.

7. A non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to perform the method according to any one of claims 1 to 5.

8. A method comprising: The base station transmits downlink control information (DCI) to the radio device via a first coreset having a first control resource set (coreset) group index. The DCI schedules the transmission of the physical downlink shared channel (PDSCH), wherein: The first quasi-co-address Type D of the PDSCH transmission is different from the second quasi-co-address Type D of the Physical Downlink Control Channel (PDCCH) transmission. The PDCCH transmission is transmitted via a second coreset, and the PDCCH transmission overlaps with the PDSCH transmission on at least one symbol. The first coreset group index is the same as the second coreset group index of the second coreset; and Prioritize the PDCCH transmissions transmitted via the second coreset.

9. The method of claim 8, wherein the time offset between the DCI and the PDSCH transmission is less than a threshold.

10. The method of claim 9, further comprising receiving user equipment (UE) capability information indicating the threshold from the wireless device.

11. The method of claim 9 or 10, further comprising determining the first quasi-co-address TypeD of the PDSCH transmission based on the quasi-co-address of the coreset having the lowest coreset index.

12. The method of claim 11, wherein determining the first quasi-co-address TypeD based on the quasi-co-address of the coreset is performed in response to the time offset being less than the threshold.

13. A base station, comprising: One or more processors; and A memory for storing instructions that, when executed by the one or more processors, cause the base station to perform the method according to any one of claims 8 to 12.

14. A non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to perform the method according to any one of claims 8 to 12.

15. A system comprising: A base station includes one or more first processors; and a first memory storing a first instruction, which, when executed by the one or more first processors, causes the base station to: Downlink control information (DCI) is transmitted via a first coreset having a first control resource set (coreset) group index, and the DCI schedules the transmission of the physical downlink shared channel (PDSCH). as well as A wireless device, including one or more second processors; and a second memory storing a second instruction, which, when executed by the one or more second processors, causes the wireless device to: DCI is received via the first coreset; Sure: The first quasi-co-location Type D of the PDSCH transmission is different from the second quasi-co-location Type D of the Physical Downlink Control Channel (PDCCH) transmission. The PDCCH transmission is transmitted via a second coreset, and the PDCCH transmission overlaps with the PDSCH transmission on at least one symbol. The first coreset group index is the same as the second coreset group index of the second coreset; as well as Based on the determination, the PDCCH transmissions via the second coreset are prioritized.

Images