Maintenance of multiple advance timing groups

Abstract

A wireless device can receive downlink messages via a cell associated with at least two Timing Advance Groups (TAGs), indicating uplink resources for Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) feedback. These uplink resources can be associated with Transmission Configuration Indicator (TCI) states of at least two active TCI states of the cell. Based on the fact that the time alignment timers for the TAGs in at least two TAGs of the cell associated with the TCI states are running, the wireless device can instruct its physical layer to generate an acknowledgment. The wireless device can then transmit HARQ-ACK feedback, including the acknowledgment, via the cell and based on the TCI states.

Description

[0001] Cross-references to related applications

[0002] This application claims the benefit of U.S. Provisional Application No. 63 / 334,985, filed April 26, 2022, the entire contents of which are incorporated herein by reference. Attached Figure Description

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

[0004] Figure 1A and Figure 1B An exemplary mobile communication network in which embodiments of the present disclosure may be implemented is shown.

[0005] Figure 2A and Figure 2B The new radio (NR) user plane and control plane protocol stacks are shown respectively.

[0006] Figure 3 It shows in Figure 2A An example of the services provided between the protocol layers of the NR user plane protocol stack.

[0007] Figure 4A It shows the flow through Figure 2A An example downlink data stream of the NR user plane protocol stack.

[0008] Figure 4B An exemplary format of the MAC subheader in a MAC PDU is shown.

[0009] Figure 5A and Figure 5B The mappings between logical channels, transport channels, and physical channels used for downlink and uplink are shown respectively.

[0010] Figure 6 This is an example diagram illustrating the RRC state transition of the UE.

[0011] Figure 7 An exemplary configuration is shown in which OFDM symbols are grouped into NR frames.

[0012] Figure 8 An exemplary configuration of time slots in the time and frequency domains of an NR carrier is shown.

[0013] Figure 9 Three examples of bandwidth adaptation using NR carriers with configured BWPs are shown.

[0014] Figure 10A Three carrier aggregation configurations with two component carriers are shown.

[0015] Figure 10B An example is shown of how aggregated cells can be configured into one or more PUCCH groups.

[0016] Figure 11A An example of the SS / PBCH block structure and location is shown.

[0017] Figure 11B An example of CSI-RS mapped in the time and frequency domains is shown.

[0018] Figure 12A and Figure 12B Examples of three downlink and uplink beam management procedures are shown respectively.

[0019] Figure 13A , Figure 13B and Figure 13C The four-step contention-based random access procedure, the two-step contention-free random access procedure, and another two-step random access procedure are shown respectively.

[0020] Figure 14A An example of the CORESET configuration for the bandwidth portion is shown.

[0021] Figure 14B An example of CCE-to-REG mapping for DCI transport is shown on CORESET and PDCCH processing.

[0022] Figure 15 An example of a wireless device communicating with a base station is shown.

[0023] Figure 16A , Figure 16B , Figure 16C and Figure 16D An exemplary structure for uplink and downlink transmission is shown.

[0024] Figure 17 An example of multiple timing advance groups according to one aspect of an embodiment of this disclosure is shown.

[0025] Figure 18 An example of multiple timing advance groups according to one aspect of an embodiment of this disclosure is shown.

[0026] Figure 19 An exemplary flowchart of multiple timing advance groups according to one aspect of an embodiment of the present disclosure is shown.

[0027] Figure 20 An example of managing multiple time alignment timers according to one aspect of an embodiment of this disclosure is shown.

[0028] Figure 21An exemplary flowchart illustrating the management of multiple time alignment timers according to one aspect of an embodiment of this disclosure is shown. Detailed Implementation

[0029] In this disclosure, various embodiments are presented in the form of examples of how the disclosed techniques can be implemented and / or how the disclosed techniques can be practiced in environments and scenarios. It will be apparent to those skilled in the art that various changes in form and detail may be made therein without departing from the scope of the invention. Indeed, after reading the specification, it will be apparent to those skilled in the art how to implement alternative embodiments. Embodiments of the invention should not be limited to any of the described exemplary embodiments. Embodiments of this disclosure will be described with reference to the accompanying drawings. Limitations, features, and / or elements from the disclosed exemplary embodiments may be combined to create additional embodiments within the scope of this disclosure. Any diagrams highlighting functionality and advantages are given for illustrative purposes only. The disclosed architecture is flexible and configurable enough that it can be utilized in ways other than those shown. For example, actions listed in any flowchart may be reordered or optionally used only in certain embodiments.

[0030] The implementation scheme can be configured to operate as needed. For example, in wireless devices, base stations, radio environments, networks, combinations thereof, etc., the disclosed mechanisms can be executed when certain criteria are met. Exemplary 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, combinations thereof, etc. Various exemplary implementation schemes can be applied when one or more criteria are met. Therefore, exemplary implementation schemes that selectively implement the disclosed protocols can be implemented.

[0031] A base station can communicate with a hybrid of wireless devices. 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. When this disclosure refers to a base station communicating with multiple wireless devices, this disclosure may refer to a subset of the total number of wireless devices in the coverage area. For example, this disclosure may refer to multiple wireless devices having a given capability and being in a given sector of a base station using 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, these wireless devices or base stations may be based on older versions of LTE or 5G technology.

[0032] In this disclosure, “a” (“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 example of one of a number of suitable possibilities that may or may not be used in one or more embodiments of various embodiments. As used herein, the terms “comprising” and “consisting of” enumerate one or more components of the element being described. The terms “comprising” and “including” are interchangeable and do not exclude the inclusion of unlisted components in the element being described. In contrast, “consisting of” provides a complete enumeration of the one or more components of the element being described. As used herein, the term “based on” should be interpreted as “at least partially based on” rather than, for example, “based on only”. As used herein, the term “and / or” indicates any possible combination of the enumerated elements. For example, "A, B and / or C" can mean A; B; C; A and B; A and C; B and C; or A, B and C.

[0033] 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 example of one of a variety of suitable possibilities that may or may not be used for one or more different implementations. The phrase “in response to” (or equivalently “at least in response to”) indicates that the phrase following the phrase “in response to” is an example of one of a variety of suitable possibilities that may or may not be used for one or more different implementations. The phrase “depends on” (or equivalently “at least depends on”) indicates that the phrase following the phrase “depends on” is an example of one of a variety of suitable possibilities that may or may not be used for one or more different implementations. The phrase “adopts / uses” (or equivalently “at least adopts / uses”) indicates that the phrase following the phrase “adopts / uses” is an example of one of a variety of suitable possibilities that may or may not be used for one or more different implementations.

[0034] 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 perform certain actions in the device, regardless of whether the device is in an operational or non-operational state.

[0035] 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 one exemplary embodiment, 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.

[0036] Many of the proposed features are described as optional using the word "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. 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 three of the three possible features.

[0037] Many 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 (e.g., 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 (such as C, C++, Fortran, Java, Basic, Matlab, etc.) or a modeling / simulation program (such as Simulink, Stateflow, GNU Octave, or LabVIEW MathScript). 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, C++, etc. 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 limited internal hardware modules on a programmable device. The aforementioned techniques are often combined to achieve the desired functional module results.

[0038] Figure 1A An example of a mobile communication network 100 in which embodiments of the present disclosure may be implemented is shown. The mobile communication network 100 may, for example, be a Public Land Mobile Network (PLMN) operated by a network operator. Figure 1A As shown, the mobile communication network 100 includes a core network (CN) 102, a radio access network (RAN) 104, and a wireless device 106.

[0039] CN 102 can provide the wireless device 106 with an interface to one or more data networks (DNs) (such as public DNs (e.g., the Internet), private DNs, and / or carrier-internal DNs). As part of the interface functionality, CN 102 can establish an end-to-end connection between the wireless device 106 and one or more DNs, authenticate the wireless device 106, and provide charging functionality.

[0040] RAN 104 can connect CN 102 to radio device 106 via radio communication through an air interface. As part of the radio communication, RAN 104 can provide scheduling, radio resource management, and retransmission protocols. The communication direction from RAN 104 to radio device 106 via the air interface is referred to as the downlink, while the communication direction from radio device 106 to RAN 104 via the air interface is referred to as the uplink. Downlink transmissions can be separated from uplink transmissions using Frequency Division Duplex (FDD), Time Division Duplex (TDD), and / or some combination of these two duplex technologies.

[0041] The term "wireless device" may be used throughout this disclosure to mean and cover any mobile or fixed (non-mobile) device that requires or can use wireless communication. For example, a wireless device may be a telephone, smartphone, tablet, computer, laptop, sensor, instrument, wearable device, Internet of Things (IoT) device, roadside unit (RSU) of a vehicle, relay node, automobile, and / or any combination thereof. The term "wireless device" also encompasses other terms including user equipment (UE), user terminal (UT), access terminal (AT), mobile station, handheld device, wireless transmit and receive unit (WTRU), and / or wireless communication device.

[0042] RAN 104 may include one or more base stations (not shown). The term "base station" may be used throughout this disclosure to mean and encompass: Node B (associated with UMTS and / or 3G standards); Evolved Node B (eNB, associated with E-UTRA and / or 4G standards); Remote Radio Header (RRH); Baseband Processing Unit coupled to one or more RRHs; Repeater Node or Relay Node for extending the coverage area of ​​the donor Node; Next Generation Evolved Node B (ng-eNB); Generation Node B (gNB, associated with NR and / or 5G standards); Access Point (AP, associated with, for example, WiFi or any other suitable wireless communication standard); and / or any combination thereof. A base station may include at least one gNB Central Unit (gNB-CU) and at least one gNB Distributed Unit (gNB-DU).

[0043] The base stations included in RAN 104 may include one or more sets of antennas for communicating with wireless device 106 via an air interface. For example, one or more base stations in this RAN may include three sets of antennas to control three cells (or sectors) respectively. The size of a cell may be determined by the range within which a receiver (e.g., a base station receiver) can successfully receive transmissions from a transmitter (e.g., a wireless device transmitter) operating within the cell. The cells of the base stations may together provide radio coverage over a wide geographical area to wireless device 106 to support wireless device mobility.

[0044] Besides three-sector sites, other implementations of the base stations are also possible. For example, one or more base stations in RAN 104 can be implemented as sectorized sites with more or fewer than three sectors. One or more base stations in RAN 104 can be implemented as access points, baseband processing units coupled to several remote radio heads (RRHs), and / or repeater or relay nodes for extending the coverage area of ​​the donor node. The baseband processing units coupled to the RRHs can be part of a centralized or cloud RAN architecture, where the baseband processing units can be centralized in a pool of baseband processing units or virtualized. Repeater nodes can amplify and replay radio signals received from the donor node. Relay nodes can perform the same / similar functions as repeater nodes, but can decode the radio signals received from the donor node to remove noise before amplifying and replaying the radio signals.

[0045] RAN 104 can be deployed as a homogeneous network of macrocell base stations with similar antenna configurations and similar high-level transmission power. RAN 104 can also be deployed as a heterogeneous network. In a heterogeneous network, small cell base stations can be used to provide small coverage areas, such as coverage areas overlapping with the relatively large coverage areas provided by macrocell base stations. Small coverage areas can be provided in areas with high data traffic (or so-called "hot spots") or in areas where macrocell coverage is weak. Examples of small cell base stations, in descending order of coverage area, include: microcell base stations, picocell base stations, and femtocell base stations or home base stations.

[0046] The Third Generation Partnership Project (3GPP) was established in 1998 to facilitate collaboration with... Figure 1A The mobile communication network 100 in this disclosure provides global standardization for similar mobile communication networks. To date, 3GPP has defined specifications for three generations of mobile networks: the third-generation (3G) network known as Universal Mobile Telecommunications System (UMTS), the fourth-generation (4G) network known as Long Term Evolution (LTE), and the fifth-generation (5G) network known as 5G System (5GS). The embodiments of this disclosure are described with reference to the RAN of the 3GPP 5G network, known as Next Generation RAN (NG-RAN). These embodiments are applicable to the RAN of other mobile communication networks, such as... Figure 1A RAN 104, the RAN of early 3G and 4G networks, and those RANs of future networks that have not yet been specified (e.g., 3GPP 6G networks). NG-RAN implements 5G radio access technology known as New Radio (NR) and can be configured to implement 4G radio access technology or other radio access technologies, including non-3GPP radio access technologies.

[0047] Figure 1BAnother exemplary mobile communication network 150 in which embodiments of the present disclosure may be implemented is shown. The mobile communication network 150 may be, for example, a PLMN operated by a network operator. Figure 1B As shown, the mobile communication network 150 includes a 5G core network (5G-CN) 152, an NG-RAN 154, and UEs 156A and 156B (collectively referred to as UE 156). This can be compared with... Figure 1A These components are implemented and operated in the same or similar ways as the corresponding components described.

[0048] 5G-CN 152 provides UE 156 with an interface to one or more DNs, such as public DNs (e.g., the Internet), private DNs, and / or operator-internal DNs. As part of the interface functionality, 5G-CN 152 can establish end-to-end connections between UE 156 and the one or more DNs, authenticate UE 156, and provide charging functions. Compared to the CNs in 3GPP 4G networks, the foundation of 5G-CN 152 can be a service-based architecture. This means that the architecture of the nodes constituting 5G-CN 152 can be defined as network functions that provide services to other network functions via the interface. The network functions of 5G-CN 152 can be implemented in several ways, including as network elements on dedicated or shared hardware, as software instances running on dedicated or shared hardware, or as virtualized functions instantiated on a platform (e.g., a cloud-based platform).

[0049] like Figure 1B As shown, 5G-CN 152 includes Access and Mobility Management Functions (AMF) 158A and User Plane Functions (UPF) 158B. For ease of explanation, in Figure 1B These are shown as a single component, AMF / UPF 158. UPF 158B can act as a gateway between NG-RAN 154 and the one or more DNs. Functions that UPF 158B can perform include: packet routing and forwarding, packet inspection and user plane policy rule enforcement, service usage reporting, uplink classification supporting the routing of service flows to the one or more DNs, user plane Quality of Service (QoS) processing (e.g., packet filtering, gating, uplink / downlink rate enforcement, and uplink service authentication), downlink packet buffering, and downlink data notification triggering. UPF 158B can act as an anchor point for intra / inter-Radio Access Technology (RAT) mobility, an external Protocol (or Packet) Data Unit (PDU) session point interconnected with the one or more DNs, and / or a pivot point supporting multihomed PDU sessions. UE 156 can be configured to receive services via a PDU session, which is a logical connection between the UE and the DN.

[0050] The AMF 158A can perform functions such as: Non-Access Layer (NAS) signaling termination, NAS signaling security, Access Layer (AS) security control, inter-CN node signaling for mobility between 3GPP access networks, idle mode UE reachability (e.g., control and execution of paging retransmission), registration area management, intra-system and inter-system mobility support, access authentication, access authorization including roaming rights verification, mobility management control (subscription and policies), network slicing support, and / or Session Management Function (SMF) selection. NAS can refer to functions operating between the CN and the UE, and AS can refer to functions operating between the UE and the RAN.

[0051] 5G-CN 152 may include, for clarity, not listed here. Figure 1B One or more additional network functions are shown in the diagram. For example, 5G-CN 152 may include one or more of the following: Session Management Function (SMF), NR Repository Function (NRF), Policy Control Function (PCF), Network Openness Function (NEF), Unified Data Management (UDM), Application Function (AF), and / or Authentication Server Function (AUSF).

[0052] NG-RAN 154 can connect 5G-CN 152 to UE 156 via radio communication over an air interface. NG-RAN 154 may include: one or more gNBs, shown as gNB 160A and gNB 160B (collectively referred to as gNB 160); and / or one or more ng-eNBs, shown as ng-eNB 162A and ng-eNB 162B (collectively referred to as ng-eNB 162). gNB 160 and ng-eNB 162 may be more generally referred to as base stations. gNB 160 and ng-eNB 162 may include one or more sets of antennas for communicating with UE 156 over the air interface. For example, one or more gNBs in gNB 160 and / or one or more ng-eNBs in ng-eNB 162 may include three sets of antennas to control three cells (or sectors) respectively. The gNB 160 and ng-eNB 162 cells can work together to provide UE 156 with radio coverage over a wide geographical area to support UE mobility.

[0053] like Figure 1BAs shown, gNB 160 and / or ng-eNB 162 can connect to 5G-CN 152 via the NG interface and to other base stations via the Xn interface. The NG and Xn interfaces can be established using a direct physical connection and / or an indirect connection via an underlying transport network (such as an Internet Protocol (IP) transport network). gNB 160 and / or ng-eNB 162 can connect to UE 156 via the Uu interface. For example, as... Figure 1B As shown, the gNB 160A can connect to the UE156A via the Uu interface. The NG, Xn, and Uu interfaces are associated with a protocol stack. The protocol stack associated with the interface can be... Figure 1B The network elements in the system are used to exchange data and signaling messages, and can include two planes: a user plane and a control plane. The user plane can handle data that is of interest to the user. The control plane can handle signaling messages that are of interest to the network elements.

[0054] The gNB 160 and / or ng-eNB 162 can connect to one or more AMF / UPF functions of the 5G-CN 152, such as AMF / UPF 158, via one or more NG interfaces. For example, the gNB 160A can connect to the UPF 158B of the AMF / UPF 158 via an NG user plane (NG-U) interface. The NG-U interface can provide user plane PDU delivery (e.g., non-guaranteed delivery) between the gNB 160A and the UPF 158B. The gNB 160A can connect to the AMF158A via an NG control plane (NG-C) interface. The NG-C interface can provide, for example, NG interface management, UE context management, UE mobility management, NAS message delivery, paging, PDU session management, and configuration delivery and / or warning message transmission.

[0055] The gNB 160 can provide NR user plane and control plane protocol termination to UE 156 via the Uu interface. For example, the gNB 160A can provide NR user plane and control plane protocol termination to UE 156A via the Uu interface associated with the first protocol stack. The ng-eNB 162 can provide Evolved UMTS Terrestrial Radio Access (E-UTRA) user plane and control plane protocol termination to UE 156 via the Uu interface, where E-UTRA refers to 3GPP 4G radio access technology. For example, the ng-eNB 162B can provide E-UTRA user plane and control plane protocol termination to UE 156B via the Uu interface associated with the second protocol stack.

[0056] 5G-CN 152 is described as being configured to handle NR and 4G radio access. Those skilled in the art will understand that NR can potentially connect to the 4G core network in a mode known as “non-standalone operation.” In non-standalone operation, the 4G core network is used to provide (or at least support) control plane functions (e.g., initial access, mobility, and paging). Although Figure 1B The diagram shows only one AMF / UPF 158, but a gNB or ng-eNB can connect to multiple AMF / UPF nodes to provide redundancy and / or load sharing across those multiple AMF / UPF nodes.

[0057] As discussed, Figure 1B The interfaces between network elements (e.g., Uu, Xn, and NG interfaces) can be associated with the protocol stack used by the network elements to exchange data and signaling messages. The protocol stack can include two planes: a user plane and a control plane. The user plane handles data of interest to the user, while the control plane handles signaling messages of interest to the network elements.

[0058] Figure 2A and Figure 2B Examples of NR user plane and NR control plane protocol stacks for the Uu interface located between UE 210 and gNB 220 are shown respectively. Figure 2A and Figure 2B The protocol stack shown can be used with, for example, Figure 1B The protocol stacks of the Uu interface between UE156A and gNB 160A shown are the same or similar.

[0059] Figure 2A The diagram illustrates a five-layer NR user plane protocol stack implemented in UE 210 and gNB 220. At the bottom of the stack, the Physical Layer (PHY) 211 and 221 provide transport services to the higher layers and can correspond to Layer 1 of the Open Systems Interconnection (OSI) model. The next four protocols above PHY 211 and 221 include Media Access Control (MAC) 212 and 222, Radio Link Control (RLC) 213 and 223, Packet Data Convergence Protocol (PDCP) 214 and 224, and Service Data Application Protocol (SDAP) 215 and 225. These four protocols together can constitute Layer 2 or the Data Link Layer of the OSI model.

[0060] Figure 3 This illustrates an example of services provided between protocol layers in the NR user plane protocol stack. From Figure 2A and Figure 3Starting from the top, SDAPs 215 and 225 can perform QoS flow processing. UE 210 can receive services through a PDU session, which can be a logical connection between UE 210 and the DN. The PDU session can have one or more QoS flows. The CN's UPF (e.g., UPF 158B) can map IP packets to these one or more QoS flows of the PDU session based on QoS requirements (e.g., in terms of latency, data rate, and / or error rate). SDAPs 215 and 225 can perform mapping / demapping between these one or more QoS flows and one or more data radio bearers. The mapping / demapping between QoS flows and data radio bearers can be determined by SDAP 225 at gNB 220. SDAP 215 at UE 210 can learn the mapping between QoS flows and data radio bearers through reflected mapping or control signaling received from gNB 220. For reflective mapping, the SDAP 225 at gNB 220 can mark downlink packets with a QoS Flow Indicator (QFI), which can be observed by the SDAP 215 at UE 210 to determine the mapping / demapping between QoS flows and data radio bearers.

[0061] PDCP 214 and 224 can perform header compression / decompression to reduce the amount of data that needs to be transmitted over the air interface, can perform encryption / decryption to prevent unauthorized decoding of data transmitted over the air interface, and can perform integrity protection to ensure that control messages originate from their intended source. PDCP 214 and 224 can perform retransmission of undelivered packets, reordering and repackaging of packets, and removal of duplicate packets received due to, for example, intra-gNB handover. PDCP 214 and 224 can perform packet duplication to increase the likelihood of packet reception and remove any duplicate packets at the receiver. Packet duplication can be suitable for services requiring high reliability.

[0062] although Figure 3 Although not shown, PDCP 214 and 224 can perform mapping / demapping between split radio bearers and RLC channels in dual connectivity scenarios. Dual connectivity is a technique that allows a UE to connect to two cells or more generally to two cell groups: a primary cell group (MCG) and a secondary cell group (SCG). Split bearers are those that are split when a single radio bearer (such as one of the radio bearers provided by PDCP 214 and 224 as a service to SDAP 215 and 225) is handled by a cell group in dual connectivity. PDCP 214 and 224 can map / demapping split radio bearers between RLC channels belonging to a cell group.

[0063] RLCs 213 and 223 can respectively perform segmentation, retransmission via Automatic Repeat Request (ARQ), and removal of duplicate data units received from MACs 212 and 222. RLCs 213 and 223 can support three transmission modes: Transparent Mode (TM); Unacknowledged Mode (UM); and Acknowledged Mode (AM). Based on the transmission mode the RLC is operating in, the RLC can perform one or more of the aforementioned functions. RLC configuration can be based on each logical channel, independent of parameter sets and / or Transmission Time Interval (TTI) duration. Figure 3 As shown, RLC 213 and 223 can provide RLC channels as services to PDCP 214 and 224, respectively.

[0064] MACs 212 and 222 can perform multiplexing / demultiplexing of logical channels and / or mapping between logical channels and transport channels. Multiplexing / demultiplexing may include multiplexing data units belonging to one or more logical channels into / from transport blocks (TBs) delivered to / from PHYs 211 and 221. MAC 222 can be configured to perform scheduling, scheduling information reporting, and priority processing between UEs by means of dynamic scheduling. Scheduling can be performed for downlink and uplink in gNB 220 (at MAC 222). MACs 212 and 222 can be configured to perform error correction via Hybrid Automatic Repeat Request (HARQ) (e.g., one HARQ entity per carrier in the case of carrier aggregation (CA), priority processing between logical channels of UE 210 by means of logical channel priority ordering, and / or padding. MACs 212 and 222 may support one or more parameter sets and / or transmission timing. In the example, the mapping constraints in logical channel priority ordering can control which set of parameters and / or transmission timing the logical channel can use. For example... Figure 3 As shown, MAC 212 and 222 can provide logical channels as services to RLC 213 and 223.

[0065] PHYs 211 and 221 can perform transport-to-physical channel mapping and digital and analog signal processing functions for transmitting and receiving information over the air interface. These digital and analog signal processing functions may include, for example, encoding / decoding and modulation / demodulation. PHYs 211 and 221 can perform multi-antenna mapping. For example... Figure 3 As shown, PHYs 211 and 221 can provide one or more transport channels as services to MACs 212 and 222.

[0066] Figure 4A An exemplary downlink data flow through the NR user plane protocol stack is shown. Figure 4AThe diagram illustrates the downlink data flow through the NR user plane protocol stack to generate three IP packets (n, n+1, and m) of two TB at the gNB 220. The uplink data flow through the NR user plane protocol stack can be compared with... Figure 4A The downlink data flow described in the text is similar.

[0067] Figure 4A The downlink data flow begins when SDAP 225 receives three IP packets from one or more QoS flows and maps those three packets to a radio bearer. Figure 4A In SDAP 225, IP packets n and n+1 are mapped to the first radio bearer 402, and IP packet m is mapped to the second radio bearer 404. The SDAP header (in...) Figure 4A Data units marked with "H" are added to IP packets. Data units originating from / going to a higher protocol layer are called lower protocol layer Service Data Units (SDUs), and data units originating from / going to a lower protocol layer are called higher protocol layer Protocol Data Units (PDUs). Figure 4A As shown, the data unit from SDAP225 is the SDU of the lower protocol layer PDCP 224 and the PDU of SDAP 225.

[0068] Figure 4A The remaining protocol layers can perform their associated functions (e.g., regarding...). Figure 3 This involves adding the corresponding headers and forwarding their output to the next lower layer. For example, PDCP 224 can perform IP header compression and encryption, and forward its output to RLC 223. RLC 223 can optionally perform fragmentation (e.g., as...). Figure 4A (As shown in the image regarding IP packet m) and forwards its output to MAC 222. MAC 222 can multiplex many RLC PDUs and can attach MAC subheaders to RLC PDUs to form transport blocks. In NR, MAC subheaders can be distributed throughout MAC PDUs, such as... Figure 4A As shown in the diagram. In LTE, the MAC sub-header can be located entirely at the beginning of the MAC PDU. The NR MAC PDU structure can reduce processing time and associated latency because the MAC PDU sub-header can be computed before the complete MAC PDU is assembled.

[0069] Figure 4BAn exemplary format of the MAC subheader in a MAC PDU is shown. The MAC subheader includes: an SDU length field indicating the length (e.g., in bytes) of the MAC SDU to which the MAC subheader corresponds; a Logical Channel Identifier (LCID) field identifying the logical channel from which the MAC SDU originates to assist in the demultiplexing process; a flag (F) indicating the size of the SDU length field; and a reserved bit (R) field for future use.

[0070] Figure 4B The diagram further illustrates the MAC control element (CE) inserted into the MAC PDU by a MAC (such as MAC 223 or MAC 222). For example, Figure 4B This shows two MAC CEs inserted into the MAC PDU. Downlink transmissions can be initiated at the beginning of the MAC PDU (e.g., ...). Figure 4B (As shown in the diagram) and a MAC CE is inserted at the end of the uplink transmission of the MAC PDU. MAC CEs can be used for in-band control signaling. Example MAC CEs include: scheduling-related MAC CEs, such as buffer status reports and power headroom reports; activation / deactivation MAC CEs, such as those for PDCP repeated detection, channel state information (CSI) reports, sounding reference signal (SRS) transmissions, and activation / deactivation of previously configured components; discontinuous reception (DRX)-related MAC CEs; timing advance MAC CEs; and random access-related MAC CEs. A MAC subheader with a format similar to that described with respect to the MAC SDU may precede the MAC CE, and the MAC CE may be identified by a reserved value in the LCID field indicating the type of control information included in the MAC CE.

[0071] Before describing the NR control plane protocol stack, we will first describe the mapping between logical channels, transport channels, and physical channels, as well as channel types. One or more of these channels can be used to perform functions associated with the NR control plane protocol stack, which will be described later below.

[0072] Figure 5A and Figure 5BThe mappings between logical channels, transport channels, and physical channels are shown for both downlink and uplink. Information is transmitted through channels between the RLC, MAC, and PHY of the NR protocol stack. Logical channels can be used between the RLC and MAC and can be classified as control channels carrying control and configuration information in the NR control plane, or as service channels carrying data in the NR user plane. Logical channels can be classified as dedicated logical channels for a specific UE, or as common logical channels that can be used by more than one UE. Logical channels can also be defined by the type of information they carry. The set of logical channels defined by NR includes, for example:

[0073] - Paging Control Channel (PCCH), which carries paging messages for paging UEs whose location is unknown to the network at the cell level;

[0074] - Broadcast Control Channel (BCCH), which carries system information messages in the form of a Master Information Block (MIB) and several System Information Blocks (SIB), wherein the system information messages can be used by the UE to obtain information about how the cell is configured and how to operate within the cell;

[0075] - Common Control Channel (CCCH), which is used to carry control messages and random access;

[0076] - Dedicated Control Channel (DCCH), used to carry control messages to a specific UE / carry control messages from a specific UE to configure that UE; and

[0077] - Dedicated Service Channel (DTCH), which is used to carry user data to a specific UE or carry user data from a specific UE.

[0078] Transport channels are used between the MAC layer and the PHY layer, and can be defined by how the information they carry is transmitted over the air interface. The set of transport channels defined by NR includes, for example:

[0079] - Paging Channel (PCH), which is used to carry paging messages originating from PCCH;

[0080] - Broadcast channel (BCH), which is used to carry MIBs from the BCCH;

[0081] - Downlink Shared Channel (DL-SCH), which is used to carry downlink data and signaling messages, including SIBs from BCCH;

[0082] - Uplink Shared Channel (UL-SCH), used to carry uplink data and signaling messages; and

[0083] - Random Access Channel (RACH), which is used to allow a UE to access the network without any prior scheduling.

[0084] The PHY can use physical channels to transfer information between processing levels of the PHY. A physical channel can be a set of associated time-frequency resources used to carry information from one or more transport channels. The PHY can generate control information to support lower-level PHY operations and provide this control information to lower levels of the PHY via physical control channels (referred to as L1 / L2 control channels). The set of physical channels and physical control channels defined by NR includes, for example:

[0085] - Physical Broadcast Channel (PBCH), which is used to carry MIBs from the BCH;

[0086] - The Physical Downlink Shared Channel (PDSCH) is used to carry downlink data and signaling messages from the DL-SCH and paging messages from the PCH;

[0087] - The Physical Downlink Control Channel (PDCCH) carries downlink control information (DCI), which may include downlink scheduling commands, uplink scheduling authorizations, and uplink power control commands;

[0088] - The Physical Uplink Shared Channel (PUSCH) is used to carry uplink data and signaling messages from the UL-SCH, and in some cases, uplink control information (UCI) as described below.

[0089] - The Physical Uplink Control Channel (PUCCH), which carries the UCI, including HARQ acknowledgments, Channel Quality Indicator (CQI), Precoding Matrix Indicator (PMI), Rank Indicator (RI), and Scheduling Request (SR); and

[0090] - Physical Random Access Channel (PRACH), which is used for random access.

[0091] Similar to the physical control channel, the physical layer generates physical signals to support low-level physical layer operations. For example... Figure 5A and Figure 5B As shown, the physical layer signals defined by NR include: Primary Synchronization Signal (PSS), Secondary Synchronization Signal (SSS), Channel State Information Reference Signal (CSI-RS), Demodulation Reference Signal (DMRS), Sounding Reference Signal (SRS), and Phase Tracking Reference Signal (PT-RS). These physical layer signals will be described in more detail below.

[0092] Figure 2B An exemplary NR control plane protocol stack is shown. Figure 2BAs shown, the NR control plane protocol stack can use the same / similar first four protocol layers as the exemplary NR user plane protocol stack. These four protocol layers include PHY 211 and 221, MAC 212 and 222, RLC 213 and 223, and PDCP 214 and 224. Instead of having SDAP 215 and 225 at the top of the stack as in the NR user plane protocol stack, the NR control plane protocol stack has Radio Resource Control (RRC) 216 and 226 and NAS protocols 217 and 237 at the top of the NR control plane protocol stack.

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

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

[0095] Figure 6 This is an example diagram illustrating the RRC state transition of the UE. The UE can interact with... Figure 1A The wireless device 106 described in the document Figure 2A and Figure 2B The UE 210 depicted herein is the same as or similar to any other wireless device described in this disclosure. Figure 6 As shown, the UE can be in at least one of three RRC states: RRC connected 602 (e.g., RRC_CONNECTED), RRC idle 604 (e.g., RRC_IDLE), and RRC inactive 606 (e.g., RRC_INACTIVE).

[0096] In RRC connection 602, the UE has an established RRC context and may have at least one RRC connection with a base station. The base station may be similar to one of the following: Figure 1A The one or more base stations included in RAN 104 as depicted herein; Figure 1B One of gNB 160 or ng-eNB 162 described herein; Figure 2A and Figure 2B The gNB220 depicted in this disclosure; or any other base station described herein. A base station connected to a UE may have an RRC context for that UE. The RRC context, referred to as the UE context, may include parameters for communication between the UE and the base station. These parameters may include, for example: one or more AS contexts; one or more radio link configuration parameters; bearer configuration information (e.g., relating to data radio bearers, signaling radio bearers, logical channels, QoS flows, and / or PDU sessions); security information; and / or PHY, MAC, RLC, PDCP, and / or SDAP layer configuration information. When in RRC connection 602, the UE's mobility may be managed by the RAN (e.g., RAN 104 or NG-RAN 154). The UE may measure signal levels (e.g., reference signal levels) from the serving cell and neighboring cells and report these measurements to the base station currently serving the UE. The UE's serving base station may request a cell transfer to one of the neighboring base stations based on the reported measurements. The RRC state can be changed from RRC connection 602 to RRC idle 604 through connection release procedure 608, or to RRC inactive 606 through connection deactivation procedure 610.

[0097] In RRC Idle 604, an RRC context may not have been established for the UE. In RRC Idle 604, the UE may not have an RRC connection with the base station. When in RRC Idle 604, the UE may be in sleep mode most of the time (e.g., to conserve battery power). The UE may wake up periodically (e.g., once in each discontinuous reception cycle) to monitor paging messages from the RAN. The UE's mobility can be managed by the UE through a procedure known as cell reselection. The RRC state can be transitioned from RRC Idle 604 to RRC Connection 602 via Connection Establishment Procedure 612, which may involve random access procedures, as discussed in more detail below.

[0098] In RRC inactivity 606, the previously established RRC context is maintained in both the UE and the base station. This allows for a faster transition to RRC connection 602 with reduced signaling overhead compared to the transition from RRC idle 604 to RRC connected 602. While in RRC inactivity 606, the UE can be in a sleep state, and its mobility can be managed by the UE via cell reselection. The RRC state can transition from RRC inactivity 606 to RRC connection 602 via connection recovery procedure 614, or to RRC idle 604 via connection release procedure 616, which can be the same as or similar to connection release procedure 608.

[0099] RRC states can be associated with mobility management mechanisms. In RRC Idle 604 and RRC Inactive 606, mobility is managed by the UE through cell reselection. The purpose of mobility management in RRC Idle 604 and RRC Inactive 606 is to allow the network to notify the UE of events via paging messages without having to broadcast paging messages across the entire mobile network. The mobility management mechanisms used in RRC Idle 604 and RRC Inactive 606 allow the network to track the UE at the cell group level, so that paging messages can be broadcast on the cells in the cell group where the UE is currently camped, rather than across the entire mobile network. Mobility management mechanisms for RRC Idle 604 and RRC Inactive 606 track the UE at the cell group level. These mobility management mechanisms can do this using groupings of different granularities. For example, there can be three levels of cell grouping granularity: a single cell; cells within a RAN area identified by a RAN Area Identifier (RAI); and cells within a group of RAN areas called tracking areas and identified by a Tracking Area Identifier (TAI).

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

[0101] RAN areas can be used to track UEs at the RAN level. For a UE in an RRC inactive 606 state, a RAN notification area can be assigned to that UE. A RAN notification area can include one or more cell identifiers, a list of RAIs, or a list of TAIs. In the example, a base station can belong to one or more RAN notification areas. In the example, a cell can belong to one or more RAN notification areas. If a UE moves via cell reselection to a cell not included in its assigned RAN notification area, the UE can perform a notification area update to update its RAN notification area.

[0102] The base station that stores the RRC context for the UE, or the UE's last serving base station, can be referred to as the anchor base station. The anchor base station may maintain the RRC context for the UE at least during the period when the UE remains in the anchor base station's RAN notification area and / or during the period when the UE remains in RRC inactivity 606.

[0103] gNB, such as Figure 1B The gNB 160 can be divided into two parts: a central unit (gNB-CU) and one or more distributed units (gNB-DU). The gNB-CU can be coupled to one or more gNB-DUs using an F1 interface. The gNB-CU may include RRC, PDCP, and SDAP. The gNB-DU may include RLC, MAC, and PHY.

[0104] In NR, physical signals and physical channels (about Figure 5A and Figure 5BThe data discussed can be mapped onto Orthogonal Frequency Division Multiplexing (OFDM) symbols. OFDM is a multi-carrier communication scheme that transmits data via F orthogonal subcarriers (or tones). Before transmission, the data can be mapped onto a series of complex symbols called source symbols (e.g., M-QAM or M-PSK symbols) and divided into F parallel symbol streams. These F parallel symbol streams can be treated as if they were in the frequency domain and used as input to an Inverse Fast Fourier Transform (IFFT) block that transforms them into the time domain. The IFFT block takes F source symbols at a time (one source symbol from each of the F parallel symbol streams) and uses each source symbol to modulate the amplitude and phase of one of the F sinusoidal basis functions corresponding to the F orthogonal subcarriers. The output of the IFFT block can be F time-domain samples representing the sum of the F orthogonal subcarriers. These F time-domain samples can form a single OFDM symbol. After some processing (e.g., addition of a cyclic prefix) and upsampling, the OFDM symbols provided by the IFFT block can be transmitted over the air interface at the carrier frequency. The F parallel symbol streams can be mixed using an FFT block before being processed by the IFFT block. This operation produces OFDM symbols precoded with Discrete Fourier Transform (DFT) and can be used by the UE in the uplink to reduce the peak-to-average power ratio (PAPR). The inverse processing of the OFDM symbols at the receiver can be performed using the FFT block to recover the data mapped to the source symbols.

[0105] Figure 7 An exemplary configuration of NR frames in which OFDM symbols are grouped is shown. NR frames can be identified by a System Frame Number (SFN). SFNs can repeat at a period of 1024 frames. As shown, the duration of an NR frame can be 10 milliseconds (ms) and can include 10 subframes with a duration of 1 ms. Subframes can be divided into time slots, which include, for example, 14 OFDM symbols per time slot.

[0106] The duration of a time slot can depend on the set of parameters used for the OFDM symbols in that time slot. NR supports flexible parameter sets to accommodate different cell deployments (e.g., cells with carrier frequencies below 1 GHz, up to cells with carrier frequencies in the mmWave range). The parameter set can be defined in terms of subcarrier spacing and cyclic prefix duration. For the parameter set in NR, the subcarrier spacing can be scaled up from a baseline subcarrier spacing of 15 kHz by powers of two, and the cyclic prefix duration can be scaled down from a baseline cyclic prefix duration of 4.7 μs by powers of two. For example, NR defines parameter sets with the following combinations of subcarrier spacing / cyclic prefix duration: 15 kHz / 4.7 μs; 30 kHz / 2.3 μs; 60 kHz / 1.2 μs; 120 kHz / 0.59 μs; and 240 kHz / 0.29 μs.

[0107] A time slot can have a fixed number of OFDM symbols (e.g., 14 OFDM symbols). Parameter sets with higher subcarrier spacing have shorter time slot durations and correspondingly more time slots per subframe. Figure 7 This illustrates the transmission structure of the time slot duration and per subframe time slot related to the parameter set (for ease of explanation). Figure 7 (The parameter set with a subcarrier spacing of 240 kHz is not shown in the diagram). Subframes in NR can be used as a time reference independent of the parameter set, while time slots can be used as units for scheduling uplink and downlink transmissions. To support low latency, scheduling in NR can be separated from the time slot duration and begin at any OFDM symbol, continuing to transmit as many symbols as needed. These partial time slot transmissions can be referred to as micro-time slots or sub-time slot transmissions.

[0108] Figure 8 An exemplary configuration of a time slot in the time and frequency domains of an NR carrier is shown. This time slot includes a resource element (RE) and a resource block (RB). An RE is the smallest physical resource in NR. An RE spans one OFDM symbol in the time domain via a subcarrier in the frequency domain, such as... Figure 8 As shown. RB spans twelve consecutive REs in the frequency domain, as... Figure 8 As shown. NR carriers can be limited to a width of 275RB or 275×12=3300 subcarriers. If this limitation is used, then for subcarrier spacing of 15kHz, 30kHz, 60kHz, and 120kHz, NR carriers can be limited to 50MHz, 100MHz, 200MHz, and 400MHz respectively, where the 400MHz bandwidth can be set based on a bandwidth limit of 400MHz per carrier.

[0109] Figure 8This illustrates a single set of parameters used across the entire bandwidth of an NR carrier. In other exemplary configurations, multiple sets of parameters can be supported on the same carrier.

[0110] NR can support wide carrier bandwidths (e.g., up to 400MHz for a subcarrier spacing of 120kHz). Not all UEs can receive the full carrier bandwidth (e.g., due to hardware limitations). Moreover, receiving the full carrier bandwidth can be prohibitively expensive in terms of UE power consumption. In the example, to reduce power consumption and / or for other purposes, the UE can adjust the size of its receive bandwidth based on the amount of traffic it plans to receive. This is called bandwidth adaptation.

[0111] The NR defines a Bandwidth Component (BWP) to support UEs that cannot receive the full carrier bandwidth and to support bandwidth adaptation. In the example, a BWP can be defined by a subset of consecutive Relays (RBs) on a carrier. A UE can be configured (e.g., via the RRC layer) to have one or more downlink BWPs and one or more uplink BWPs per serving cell (e.g., up to four downlink BWPs and up to four uplink BWPs per serving cell). At a given time, one or more of the configured BWPs for the serving cell can be active. These one or more BWPs can be referred to as the active BWPs of the serving cell. When the serving cell is configured with a secondary uplink carrier, the serving cell can have one or more first active BWPs on the uplink carrier and one or more second active BWPs on the secondary uplink carrier.

[0112] For unpaired spectrum, if the downlink BWP index of the downlink BWP is the same as the uplink BWP index of the uplink BWP, then the downlink BWP from the set of configured downlink BWPs can link with the uplink BWP from the set of configured uplink BWPs. For unpaired spectrum, the UE can expect the center frequency of the downlink BWP to be the same as the center frequency of the uplink BWP.

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

[0114] For an uplink BWP in the set of configured uplink BWPs, the BS can configure one or more resource sets for the UE to transmit one or more PUCCHs. The UE can receive downlink reception (e.g., PDCCH or PDSCH) in the downlink BWP based on the configured set of parameters (e.g., subcarrier spacing and cyclic prefix duration) used for the downlink BWP. The UE can transmit uplink transmissions (e.g., PUCCH or PUSCH) in the uplink BWP based on the configured set of parameters (e.g., subcarrier spacing and cyclic prefix length of the uplink BWP).

[0115] One or more BWP indicator fields can be provided in the downlink control information (DCI). The value of the BWP indicator field can indicate which BWP in the set of configured BWPs is the active downlink BWP for one or more downlink receptions. The value of the one or more BWP indicator fields can indicate the active uplink BWP for one or more uplink transmissions.

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

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

[0118] In the example, the base station can semi-statically configure the UE using one or more BWPs. The UE can switch the active BWP from the first BWP to the second 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 (e.g., in the case that the second BWP is the default BWP).

[0119] Downlink and uplink BWP handovers can be performed independently in paired spectrum (where BWP handover refers to switching from the currently active BWP to a non-currently active BWP). In unpaired spectrum, downlink and uplink BWP handovers can be performed simultaneously. Handovers can occur between configured BWPs based on RRC signaling, DCI, the expiration of a BWP inactivity timer, and / or the initiation of random access.

[0120] Figure 9 An example of bandwidth adaptation using three configured BWPs on an NR carrier is shown. A UE configured with these three BWPs can switch from one BWP to another at a handover point. Figure 9 In the example shown, the BWPs include: BWP 902 with a bandwidth of 40MHz and a subcarrier spacing of 15kHz; BWP 904 with a bandwidth of 10MHz and a subcarrier spacing of 15kHz; and BWP 906 with a bandwidth of 20MHz and a subcarrier spacing of 60kHz. BWP 902 can be the initial active BWP, and BWP 904 can be the default BWP. The UE can switch between BWPs at a handover point. Figure 9 In the example, the UE can switch from BWP 902 to BWP 904 at handover point 908. The handover at handover point 908 can occur for any suitable reason, such as in response to the expiration of a BWP inactivity timer (indicating a switch to the default BWP) and / or in response to receiving a DCI indicating that BWP 904 is the active BWP. The UE can switch from active BWP 904 to BWP 906 at handover point 910 in response to receiving a DCI indicating that BWP 906 is the active BWP. The UE can switch from active BWP 906 to BWP 904 at handover point 912 in response to the expiration of a BWP inactivity timer and / or in response to receiving a DCI indicating that BWP 904 is the active BWP. The UE can switch from active BWP 904 to BWP 902 at handover point 914 in response to receiving a DCI indicating that BWP 902 is the active BWP.

[0121] If a UE is configured for a secondary cell with a default downlink BWP and timer values ​​from a set of configured downlink BWPs, the UE procedure for switching BWPs on the secondary cell can be the same as / similar to those on the primary cell. For example, the UE can use these values ​​on the secondary cell in the same / similar way as the UE would use the timer values ​​and default downlink BWP of the primary cell.

[0122] To provide higher data rates, carrier aggregation (CA) can be used to combine two or more carriers and transmit them simultaneously to / from the same UE. The aggregated carriers in CA can be referred to as component carriers (CCs). When using CA, there are multiple serving cells for the UE, one serving cell per CC. A CC can have three configurations in the frequency domain.

[0123] Figure 10A Three CA configurations with two CCs are shown. In the intra-band contiguous configuration 1002, the two CCs are aggregated in the same frequency band (band A) and located directly adjacent to each other within the band. In the intra-band discontinuous configuration 1004, the two CCs are aggregated in the same frequency band (band A) and separated by a certain gap within the band. In the inter-band configuration 1006, the two CCs are located in frequency bands (band A and band B).

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

[0125] When using CA, one of the aggregated cells used for the UE can be referred to as the primary cell (PCell). The PCell can be the serving cell to which the UE initially connects during RRC connection establishment, re-establishment, and / or handover. The PCell provides the UE with NAS mobility information and security input. The UE can have different PCells. In the downlink, the carrier corresponding to the PCell can be referred to as the downlink primary CC (DL PCC). In the uplink, the carrier corresponding to the PCell can be referred to as the uplink primary CC (UL PCC). Other aggregated cells used for the UE can be referred to as secondary cells (SCells). In the example, the SCell can be configured after the PCell is configured for the UE. For example, the SCell can be configured via an RRC connection reconfiguration procedure. In the downlink, the carrier corresponding to the SCell can be referred to as the downlink secondary CC (DL SCC). In the uplink, the carrier corresponding to the SCell can be referred to as the uplink secondary CC (UL SCC).

[0126] Configurable SCells for the UE can be activated and deactivated based on factors such as traffic and channel conditions. Deactivating an SCell can mean ceasing PDCCH and PDSCH reception on the SCell, and ceasing PUSCH, SRS, and CQI transmissions on the SCell. (The remaining text appears to be incomplete and requires further context.) Figure 4B The MAC CE is used to activate and deactivate configured SCells. For example, the MAC CE can use a bitmap (e.g., one bit per SCell) to indicate which SCells for the UE (e.g., in a subset of configured SCells) are activated or deactivated. Configured SCells can be deactivated in response to the expiration of a SCell deactivation timer (e.g., one SCell deactivation timer per SCell).

[0127] Downlink control information for a cell (such as scheduling assignments and scheduling grants) can be transmitted on the cell corresponding to the assignment and grant, a process known as self-scheduling. A cell's DCI can be transmitted on another cell, a process known as cross-carrier scheduling. Uplink control information used for aggregation cells (e.g., HARQ acknowledgments and channel state feedback, such as CQI, PMI, and / or RI) can be transmitted on the PCell's PUCCH. For a large number of aggregated downlink CCs, the PCell's PUCCH may become overloaded. Cells can be divided into multiple PUCCH groups.

[0128] Figure 10B This illustrates an example of how aggregated cells can be configured into one or more PUCCH groups. PUCCH group 1010 and PUCCH group 1050 can each include one or more downlink CCs. Figure 10BIn the example, PUCCH group 1010 includes three downlink CCs: PCell 1011, SCell 1012, and SCell 1013. PUCCH group 1050 in this example includes three downlink CCs: PCell 1051, SCell 1052, and SCell 1053. One or more uplink CCs can be configured as PCell 1021, SCell 1022, and SCell 1023. One or more other uplink CCs can be configured as primary Scell ​​(PSCell) 1061, SCell 1062, and SCell 1063. Uplink control information (UCI) related to the downlink CCs of PUCCH group 1010 (shown as UCI 1031, UCI 1032, and UCI 1033) can be transmitted in the uplink of PCell 1021. Uplink control information (UCI) related to the downlink CC of PUCCH group 1050 (shown as UCI 1071, UCI 1072, and UCI 1073) can be transmitted in the uplink of PSCell 1061. In the example, if Figure 10B If the aggregated cell depicted is not divided into PUCCH group 1010 and PUCCH group 1050, a single uplink PCell will transmit UCIs associated with the downlink CC, and the PCell may become overloaded. Overload can be prevented by allocating UCI transmissions between PCell 1021 and PSCell 1061.

[0129] A physical cell ID and a cell index can be assigned to a cell that includes a downlink carrier and an optional uplink carrier. The physical cell ID or cell index can identify the cell's downlink carrier and / or uplink carrier, for example, depending on the context in which the physical cell ID is used. The physical cell ID can be determined using synchronization signals transmitted on the downlink component carrier. The cell index can be determined using RRC messages. In this disclosure, the physical cell ID can be referred to as a carrier ID, and the cell index can be referred to as a carrier index. 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 / similar concepts can be applied, for example, to carrier activation. When this disclosure indicates that a first carrier is activated, this specification can mean that a cell including that first carrier is activated.

[0130] In CA, the multi-carrier nature of the PHY can be exposed to the MAC. In the example, the HARQ entity can operate on the serving cell. Transport blocks can be generated based on the assignment / authorization of each serving cell. Transport blocks and their potential HARQ retransmissions can be mapped to the serving cell.

[0131] In the downlink, the base station can transmit one or more reference signals (RS) (e.g., unicast, multicast, and / or broadcast) to the UE (e.g., PSS, SSS, CSI-RS, DMRS, and / or PT-RS, such as...). Figure 5A (As shown). In the uplink, the UE can transmit one or more RSs to the base station (e.g., DMRS, PT-RS, and / or SRS, such as...). Figure 5B (As shown). PSS and SSS can be transmitted by the base station and used by the UE to synchronize the UE with the base station. PSS and SSS can be provided in a synchronization signal (SS) / physical broadcast channel (PBCH) block that includes PSS, SSS, and PBCH. The base station can periodically transmit bursts of SS / PBCH blocks.

[0132] Figure 11A An example of the structure and location of SS / PBCH blocks is shown. A burst of SS / PBCH blocks can include one or more SS / PBCH blocks (e.g., 4 SS / PBCH blocks, such as...). Figure 11A (As shown). Bursts can be transmitted periodically (e.g., every 2 frames or 20 ms). Bursts can be limited to half-frames (e.g., the first half-frame lasting 5 ms). It should be understood that... Figure 11A This is an example, and these parameters (the number of SS / PBCH blocks per burst, the burst period, and the burst location within a frame) can be configured based on, for example, the carrier frequency of the cell in which the SS / PBCH blocks are transmitted; the cell's parameter set or subcarrier spacing; configuration performed by the network (e.g., using RRC signaling); or any other suitable factor. In this example, the UE can assume the subcarrier spacing of the SS / PBCH blocks based on the carrier frequency being monitored, unless the radio network configures the UE to assume a different subcarrier spacing.

[0133] SS / PBCH blocks can span one or more OFDM symbols in the time domain (e.g., 4 OFDM symbols, such as...). Figure 11A As shown in the example, and can span one or more subcarriers in the frequency domain (e.g., 240 consecutive subcarriers). PSS, SSS, and PBCH can have a common center frequency. PSS can be transmitted first and can span, for example, 1 OFDM symbol and 127 subcarriers. SSS can be transmitted after PSS (e.g., after two symbols) and can span 1 OFDM symbol and 127 subcarriers. PBCH can be transmitted after PSS (e.g., spanning the next 3 OFDM symbols) and can span 240 subcarriers.

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

[0135] The SS / PBCH block can be used by the UE to determine one or more parameters of the cell. For example, the UE can determine the physical cell identifier (PCI) of the cell based on the sequence of the PSS and SSS, respectively. The UE can determine the location of the cell's frame boundary based on the location of the SS / PBCH block. For example, the SS / PBCH block can indicate that it has been transmitted according to a transmission mode in which the SS / PBCH block is at a known distance from the frame boundary.

[0136] The PBCH can use QPSK modulation and forward error correction (FEC). FEC can use polarity coding. One or more symbols spanned by the PBCH can carry one or more DMRS for PBCH demodulation. The PBCH can include an indication of the cell's current system frame number (SFN) and / or an SS / PBCH block timing index. These parameters can help the UE synchronize time with the base station. The PBCH can include a Master Information Block (MIB) to provide one or more parameters to the UE. The MIB can be used by the UE to locate the Residual Minimum System Information (RMSI) associated with the cell. The RMSI can include System Information Block Type 1 (SIB1). SIB1 can contain information required for the UE to access the cell. The UE can use one or more parameters of the MIB to monitor the PDCCH that can be used to schedule the PDSCH. The PDSCH can include SIB1. SIB1 can be decoded using the parameters provided in the MIB. The PBCH can indicate that SIB1 does not exist. Based on the PBCH indicating that SIB1 does not exist, the UE can point to a frequency. The UE can search for SS / PBCH blocks at the frequency pointed to by the UE.

[0137] The UE may assume that one or more SS / PBCH blocks transmitted using the same SS / PBCH block index are quasi-co-located (QCLed) (e.g., having the same / similar Doppler spread, Doppler shift, average gain, average delay, and / or spatial Rx parameters). The UE may not assume QCL for SS / PBCH blocks transmitted with different SS / PBCH block indices.

[0138] SS / PBCH blocks (e.g., those within a half-frame) can be transmitted in spatial directions (e.g., using different beams across the coverage area of ​​the cell). In the example, the first SS / PBCH block can be transmitted in the first spatial direction using the first beam, and the second SS / PBCH block can be transmitted in the second spatial direction using the second beam.

[0139] In the example, within the carrier's frequency range, the base station can transmit multiple SS / PBCH blocks. In the example, the first PCI of the first SS / PBCH block among the multiple SS / PBCH blocks can be different from the second PCI of the second SS / PBCH block among the multiple SS / PBCH blocks. The PCIs of SS / PBCH blocks transmitted at different frequency locations can be different or the same.

[0140] CSI-RS can be transmitted by the base station and used by the UE to acquire Channel State Information (CSI). The base station can utilize one or more CSI-RS to configure the UE for channel estimation or any other suitable purpose. The base station can utilize one or more of the same / similar CSI-RS to configure the UE. The UE can measure the one or more CSI-RS. The UE can estimate the downlink channel state and / or generate a CSI report based on the measurements of the one or more downlink CSI-RS. The UE can provide the CSI report to the base station. The base station can use the feedback provided by the UE (e.g., the estimated downlink channel state) to perform link adaptation.

[0141] The base station can semi-statically configure the UE using one or more CSI-RS resource sets. CSI-RS resources can be associated with location and periodicity in the time and frequency domains. The base station can selectively activate and / or deactivate CSI-RS resources. The base station can instruct the UE that CSI-RS resources in the CSI-RS resource set are activated and / or deactivated.

[0142] The base station can configure the UE to report CSI measurements. The base station can configure the UE to provide CSI reports periodically, aperiodically, or semi-persistently. For periodic CSI reporting, the UE can be configured with multiple CSI report timings and / or periods. For aperiodic CSI reporting, the base station can request CSI reports. For example, the base station can command the UE to measure configured CSI-RS resources and provide CSI reports related to the measurements. For semi-persistent CSI reporting, the base station can configure the UE to transmit periodically and selectively activate or deactivate periodic reports. The base station can configure the UE using CSI-RS resource sets and CSI reports using RRC signaling.

[0143] CSI-RS configuration may include one or more parameters indicating, for example, up to 32 antenna ports. The UE can be configured to use the same OFDM symbols for both the downlink CSI-RS and the control resource set (CORESET) when the downlink CSI-RS and CORESET are spatially QCLed and the resource elements associated with the downlink CSI-RS are outside the physical resource block (PRB) configured for the CORESET. The UE can also be configured to use the same OFDM symbols for both the downlink CSI-RS and the SS / PBCH block when the downlink CSI-RS and SS / PBCH block are spatially QCLed and the resource elements associated with the downlink CSI-RS are outside the PRB configured for the SS / PBCH block.

[0144] Downlink DMRS can be transmitted by the base station and used by the UE for channel estimation. For example, downlink DMRS can be used for consistent demodulation of one or more downlink physical channels (e.g., PDSCH). The NR network can support one or more variable and / or configurable DMRS modes for data demodulation. At least one downlink DMRS configuration can support a frontload DMRS mode. Frontload DMRS can be mapped on one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). The base station can semi-statically configure the UE using the number (e.g., maximum number) of frontload DMRS symbols used for PDSCH. A DMRS configuration can support one or more DMRS ports. For example, for single-user MIMO, a DMRS configuration can support up to eight orthogonal downlink DMRS ports per UE. For multi-user MIMO, a DMRS configuration can support up to four orthogonal downlink DMRS ports per UE. The radio network can (e.g., at least for CP-OFDM) support a common DMRS structure for downlink and uplink, where DMRS locations, DMRS types, and / or scrambling sequences can be the same or different. The base station can use the same precoding matrix to transmit downlink DMRS and the corresponding PDSCH. The UE can use one or more downlink DMRS to perform consistent demodulation / channel estimation of the PDSCH.

[0145] In the example, the transmitter (e.g., a base station) can use a precoder matrix for a portion of the transmission bandwidth. For example, the transmitter can use a first precoder matrix for a first bandwidth and a second precoder matrix for a second bandwidth. The first and second precoder matrices can differ based on the first and second bandwidths being different. The UE can assume that the same precoder matrix is ​​used across the set of PRBs. This set of PRBs can be indicated as a Precoder Resource Block Group (PRG).

[0146] A PDSCH may include one or more layers. The UE may assume that at least one symbol with DMRS exists on one or more layers of the PDSCH. A higher layer may configure up to three DMRS for the PDSCH.

[0147] Downlink PT-RS can be transmitted by the base station and used by the UE for phase noise compensation. The presence of downlink PT-RS can depend on RRC configuration. The presence and / or type of downlink PT-RS can be configured UE-specifically using a combination of RRC signaling and / or associated with one or more parameters (e.g., modulation and coding scheme (MCS)) that can be indicated by DCI for other purposes. When configured, the dynamic presence of downlink PT-RS can be associated with one or more DCI parameters including at least one MCS. NR networks 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 employ the same precoding for both DMRS ports and PT-RS ports. The number of PT-RS ports can be less than the number of DMRS ports in the scheduled resources. Downlink PT-RS can be limited to the UE's scheduled time / frequency duration. Downlink PT-RS can be transmitted on symbols to facilitate phase tracking at the receiver.

[0148] The UE can transmit uplink DMRS to the base station for channel estimation. For example, the base station can use uplink DMRS to perform consistent demodulation of one or more uplink physical channels. For example, the UE can transmit uplink DMRS with PUSCH and / or PUCCH. Uplink DMRS can span a frequency range similar to the frequency range associated with the corresponding physical channel. The base station can configure the UE using one or more uplink DMRS configurations. At least one DMRS configuration can support a frontload DMRS mode. Frontload DMRS can be mapped on one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). One or more uplink DMRS can be configured to be transmitted at one or more symbols of PUSCH and / or PUCCH. The base station can semi-statically configure the UE with the number (e.g., maximum number) of frontload DMRS symbols for PUSCH and / or PUCCH, which the UE can use to schedule single-symbol DMRS and / or dual-symbol DMRS. NR networks can support (e.g., for Cyclic Prefix Orthogonal Frequency Division Multiplexing (CP-OFDM)) a common DMRS structure for both downlink and uplink, where the DMRS location, DMRS type, and / or scrambling sequence of the DMRS can be the same or different.

[0149] A PUSCH may include one or more layers, and a UE may transmit at least one symbol having DMRS on one or more layers present in the PUSCH. In the example, a higher layer may configure up to three DMRS for the PUSCH.

[0150] Depending on the UE's RRC configuration, the uplink PT-RS (which can be used by the base station for phase tracking and / or phase noise compensation) may or may not be present. The presence and / or type of the uplink PT-RS can be configured based on the UE through a combination of RRC signaling and / or one or more parameters indicated by the DCI for other purposes (e.g., modulation and coding scheme (MCS)). When configured, the dynamic presence of the uplink PT-RS 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 can be less than the number of DMRS ports in the scheduled resources. For example, the uplink PT-RS can be limited to the UE's scheduled time / frequency duration.

[0151] The UE can transmit SRS to the base station for channel state estimation to support uplink channel-dependent scheduling and / or link adaptation. The SRS transmitted by the UE allows the base station to estimate the uplink channel state at one or more frequencies. The scheduler at the base station can use the estimated uplink channel state to assign one or more resource blocks for uplink PUSCH transmissions from the UE. The base station can semi-statically 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 in one or more SRS resource sets (e.g., having the same / similar time-domain behavior, periodic, aperiodic, etc.) can be transmitted at certain times (e.g., simultaneously). The UE can transmit one or more SRS resources from the SRS resource set. The NR network can support aperiodic, periodic, and / or semi-persistent SRS transmissions. The UE can transmit SRS resources based on one or more trigger types, where the trigger types may include higher-layer signaling (e.g., RRC) and / or one or more DCI formats. In the example, at least one DCI format may be used for the UE to select at least one configured SRS resource set from 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 the example, when PUSCH and SRS are transmitted in the same time slot, the UE can be configured to transmit SRS after the transmission of PUSCH and the corresponding uplink DMRS.

[0152] The base station can semi-statically configure the UE using one or more SRS configuration parameters indicating 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-time slot, and / or subframe level period; time slots of periodic and / or aperiodic SRS resources; number of OFDM symbols in SRS resources; initiating OFDM symbols for SRS resources; SRS bandwidth; frequency hopping bandwidth; cyclic shift; and / or SRS sequence ID.

[0153] Antenna ports are defined such that a symbol on an antenna port, through the channel through which it is transmitted, can be inferred from another symbol on the same antenna port through the channel through which it is transmitted. If a first symbol and a second symbol are transmitted on the same antenna port, the receiver can infer the channel (e.g., fading gain, multipath delay, etc.) used to transmit the second symbol on the antenna port from the channel used to transmit the first symbol on the antenna port. A first antenna port and a second antenna port can be referred to as quasi-co-located (QCLed) if one or more large-scale properties can be inferred from the channel through which the second symbol on the second antenna port is transmitted, and the channel through which the first symbol on the first antenna port is transmitted. These one or more large-scale properties can include at least one of the following: delay spread; Doppler spread; Doppler shift; average gain; average delay; and / or spatial reception (Rx) parameters.

[0154] Channels using beamforming require beam management. Beam management can include beam measurement, beam selection, and beam indication. A beam can be associated with one or more reference signals. For example, a beam can be identified by one or more beamforming reference signals. The UE can perform downlink beam measurements and generate a beam measurement report based on downlink reference signals (e.g., Channel State Information Reference Signal (CSI-RS)). After setting up an RRC connection with the base station, the UE can execute the downlink beam measurement procedure.

[0155] Figure 11B An example of a Channel State Information Reference Signal (CSI-RS) mapped in the time and frequency domains is shown. Figure 11BThe square shown may represent a resource block (RB) within the cell's bandwidth. The base station may transmit one or more RRC messages including CSI-RS resource configuration parameters indicating one or more CSI-RS. One or more of the following parameters can be configured for CSI-RS resource configuration via higher-layer signaling (e.g., RRC and / or MAC signaling): CSI-RS resource configuration identity, number of CSI-RS ports, CSI-RS configuration (e.g., symbol and resource element (RE) positions in subframes), CSI-RS subframe configuration (e.g., subframe position, offset, and periodicity in radio frames), CSI-RS power parameters, CSI-RS sequence parameters, Code Division Multiplexing (CDM) type parameters, frequency density, transport comb, Quasi-Co-location (QCL) parameters (e.g., QCL-scramblingidentity, crs-portscount, mbsfn-subframeconfiglist, csi-rs-configZPid, qcl-csi-rs-configNZPid), and / or other radio resource parameters.

[0156] Figure 11B The three beams shown can be configured for use in a UE-specific configuration. Figure 11B The diagram shows three beams (beam #1, beam #2, and beam #3), with the possibility of configuring more or fewer beams. CSI-RS1101 can be assigned to beam #1, which can be transmitted on one or more subcarriers in the RB of the first symbol. CSI-RS1102 can be assigned to beam #2, which can be transmitted on one or more subcarriers in the RB of the second symbol. CSI-RS1103 can be assigned to beam #3, which can be transmitted on one or more subcarriers in the RB of the third symbol. By using frequency division multiplexing (FDM), the base station can use other subcarriers in the same RB (e.g., those not used to transmit CSI-RS1101) to transmit another CSI-RS associated with a beam of another UE. By using time domain multiplexing (TDM), the beam for a UE can be configured such that the beam for the UE uses symbols from beams of other UEs.

[0157] CSI-RS, such as Figure 11BThose shown (e.g., CSI-RS1101, 1102, 1103) can be transmitted by the base station and used by the UE for one or more measurements. For example, the UE can measure the Reference Signal Received Power (RSRP) configured with CSI-RS resources. The base station can configure the UE using a reporting configuration, and the UE can report RSRP measurements to the network (e.g., via one or more base stations) based on the reporting configuration. In the example, the base station can determine one or more Transmission Configuration Indication (TCI) states, including multiple reference signals, based on the reported measurement results. In the example, the base station can indicate one or more TCI states to the UE (e.g., via RRC signaling, MAC CE, and / or DCI). The UE can receive downlink transmissions with a receive (Rx) beam determined based on the one or more TCI states. In the example, the UE may or may not have beam correspondence capability. If the UE has beam correspondence capability, the UE can determine the spatial domain filter for the transmit (Tx) beam based on the spatial domain filter corresponding to the Rx beam. If the UE does not have beam correspondence capability, the UE can perform an uplink beam selection procedure to determine the spatial domain filter for the Tx beam. The UE can perform the uplink beam selection procedure based on one or more Sounding Reference Signal (SRS) resources configured for the UE by the base station. The base station can select and indicate the UE's uplink beam based on measurements of one or more SRS resources transmitted by the UE.

[0158] In the beam management procedure, the UE can assess (e.g., measure) the channel quality of one or more beampup links, including beampup links containing transmit beams transmitted by the base station, and receive beams received by the UE. Based on this assessment, the UE can transmit a beam measurement report indicating one or more beampup quality parameters, including, for example, one or more beam identifiers (e.g., beam index, reference signal index, etc.), RSRP, precoding matrix indicator (PMI), channel quality indicator (CQI), and / or rank indicator (RI).

[0159] Figure 12AExamples of three downlink beam management procedures are shown: P1, P2, and P3. Procedure P1 can enable UE measurement of the transmit (Tx) beams for a Transport Receive Point (TRP) (or multiple TRPs), for example, to support the selection of one or more base station Tx beams and / or UE Rx beams (shown as ellipses in the top and bottom rows of P1, respectively). Beamforming at the TRP can include Tx beam sweeping for the beam set (shown as ellipses rotating counterclockwise in the top rows of P1 and P2, indicated by dashed arrows). Beamforming at the UE can include Rx beam sweeping for the beam set (shown as ellipses rotating clockwise in the bottom rows of P1 and P3, indicated by dashed arrows). Procedure P2 can be used to enable UE measurement of the Tx beams for a TRP (shown as ellipses rotating counterclockwise in the top row of P2, indicated by dashed arrows). The UE and / or base station may perform procedure P2 using a smaller beam set than that used in procedure P1, or using a narrower beam set than that used in procedure P1. This can be referred to as beam refinement. The UE may perform procedure P3 for Rx beam determination by using the same Tx beam at the base station and sweeping the Rx beam at the UE.

[0160] Figure 12B Examples of three uplink beam management procedures are shown: U1, U2, and U3. Procedure U1 can be used to enable the base station to perform measurements on the UE's Tx beam, for example, to support the selection of one or more UE Tx beams and / or the base station Rx beam (shown as ellipses in the top and bottom rows of U1, respectively). Beamforming at the UE can include, for example, an Rx beam sweep from the set of beams (shown as an ellipse rotating clockwise in the bottom rows of U1 and U3, indicated by the dashed arrow). Beamforming at the base station can include, for example, an Rx beam sweep from the set of beams (shown as an ellipse rotating counterclockwise in the top rows of U1 and U2, indicated by the dashed arrow). When the UE uses a fixed Tx beam, procedure U2 can be used to enable the base station to adjust its Rx beam. The UE and / or base station may execute procedure U2 using a smaller beam set than that used in procedure P1, or using a narrower beam than that used in procedure P1. This may be referred to as beam refinement. The UE may execute procedure U3 to adjust its Tx beam when the base station uses a fixed Rx beam.

[0161] The UE can initiate a beam fault recovery (BFR) procedure based on the detection of a beam fault. The UE can initiate a BFR request (e.g., preamble, UCI, SR, MAC CE, etc.) based on the BFR procedure. The UE can detect a beam fault based on the determination that the quality of the beam pair link in the associated control channel is unsatisfactory (e.g., an error rate higher than the error rate threshold, received signal power lower than the received signal power threshold, timer expiration, etc.).

[0162] The UE can use one or more reference signals (RS) to measure the quality of the beamp-link, which may include one or more SS / PBCH blocks, one or more CSI-RS resources, and / or one or more demodulation reference signals (DMRS). The quality of the beamp-link can be based on one or more of the following: block error rate (BLER), RSRP value, signal-to-interference-plus-noise ratio (SINR) value, reference signal reception quality (RSRQ) value, and / or CSI value measured on the RS resources. The base station may indicate one or more DM-RS quasi-co-located (QCLed) RS resources and channels (e.g., control channels, shared data channels, etc.). The one or more DMRS of the RS resources and channels may be QCLed when the channel characteristics (e.g., Doppler shift, Doppler spread, average delay, delay spread, spatial Rx parameter, fading, etc.) from the transmission to the UE via the RS resources are similar to or the same as the channel characteristics from the transmission to the UE via the channels.

[0163] The network (e.g., gNB and / or the network's ng-eNB) and / or the UE can initiate random access procedures. A UE in the RRC_IDLE state and / or RRC_INACTIVE state can initiate a random access procedure to request connection settings to the network. A UE can initiate a random access procedure from the RRC_CONNECTED state. A UE can initiate a random access procedure to request uplink resources (e.g., for uplink transmission of SR when no PUCCH resources are available) and / or to acquire uplink timing (e.g., when the uplink synchronization state is not synchronized). A UE can initiate a random access procedure to request one or more System Information Blocks (SIBs) (e.g., other system information such as SIB2, SIB3, etc.). A UE can initiate a random access procedure for beam fault recovery requests. The network can initiate random access procedures for handover and / or for establishing time alignment for SCell additions.

[0164] Figure 13A A four-step contention-based random access procedure is shown. Before initiating this procedure, the base station can transmit configuration message 1310 to the UE. Figure 13AThe procedure shown includes the transmission of four messages: Msg 1 1311, Msg 2 1312, Msg 3 1313, and Msg 4 1314. Msg 1 1311 may include and / or be referred to as a preamble (or random access preamble). Msg 2 1312 may include and / or be referred to as a random access response (RAR).

[0165] Configuration message 1310 may be transmitted, for example, using one or more RRC messages. These one or more RRC messages may indicate one or more Random Access Channel (RACH) parameters to the UE. These one or more RACH parameters may include at least one of the following: general parameters for one or more random access procedures (e.g., RACH-configGeneral); cell-specific parameters (e.g., RACH-ConfigCommon); and / or dedicated parameters (e.g., RACH-configDedicated). The base station may broadcast or multicast these one or more RRC messages to one or more UEs. These one or more RRC messages may be UE-specific (e.g., dedicated RRC messages transmitted to the UE in the RRC_CONNECTED state and / or RRC_INACTIVE state). The UE may determine the time and frequency resources and / or uplink transmission power for transmitting Msg 1 1311 and / or Msg 3 1313 based on these one or more RACH parameters. Based on these one or more RACH parameters, the UE may determine the receive timing and downlink channel for receiving Msg 2 1312 and Msg 4 1314.

[0166] The one or more RACH parameters provided in configuration message 1310 may indicate one or more physical RACH (PRACH) timings available for transmitting Msg 11311. These one or more PRACH timings may be predefined. These one or more RACH parameters may indicate one or more available sets of one or more PRACH timings (e.g., prach-ConfigIndex). These one or more RACH parameters may indicate a relationship between (a) one or more PRACH timings and (b) one or more reference signals. These one or more RACH parameters may indicate a relationship between (a) one or more preambles and (b) one or more reference signals. These one or more reference signals may be SS / PBCH blocks and / or CSI-RS. For example, these one or more RACH parameters may indicate the number of SS / PBCH blocks mapped to PRACH timings and / or the number of preambles mapped to SS / PBCH blocks.

[0167] The one or more RACH parameters provided in configuration message 1310 can be used to determine the uplink transmission power of Msg 1 1311 and / or Msg3 1313. For example, the one or more RACH parameters can indicate a reference power for preamble transmission (e.g., the received target power and / or the initial power of the preamble transmission). One or more power offsets indicated by the one or more RACH parameters may exist. For example, the one or more RACH parameters can indicate: power ramp step size; power offset between SSB and CSI-RS; power offset between transmissions of Msg 1 1311 and Msg 3 1313; and / or power offset values ​​between preamble groups. The one or more RACH parameters can indicate one or more thresholds upon which the UE can determine at least one reference signal (e.g., SSB and / or CSI-RS) and / or uplink carrier (e.g., normal uplink (NUL) carrier and / or supplementary uplink (SUL) carrier).

[0168] Msg 1 1311 may include one or more preamble transmissions (e.g., preamble transmission and one or more preamble retransmissions). The RRC message may be used to configure one or more preamble groups (e.g., group A and / or group B). A preamble group may include one or more preambles. The UE may determine the preamble group based on path loss measurements and / or the magnitude of Msg 3 1313. The UE may measure the RSRP of one or more reference signals (e.g., SSB and / or CSI-RS) and determine at least one reference signal with an RSRP higher than an RSRP threshold (e.g., rsrp-ThresholdSSB and / or rsrp-ThresholdCSI-RS). For example, if the association between the one or more preambles and the at least one reference signal is configured by the RRC message, the UE can select at least one preamble associated with the one or more reference signals and / or the selected preamble group.

[0169] The UE can determine the preamble based on the one or more RACH parameters provided in configuration message 1310. For example, the UE can determine the preamble based on path loss measurement, RSRP measurement, and / or the size of Msg 3 1313. As another example, the one or more RACH parameters can indicate: the preamble format; the maximum number of preamble transmissions; and / or one or more thresholds for determining one or more preamble groups (e.g., group A and group B). The base station can use the one or more RACH parameters to configure an association between one or more preambles and one or more reference signals (e.g., SSB and / or CSI-RS) for the UE. If the association is configured, the UE can determine the preamble included in Msg 1 1311 based on the association. Msg 1 1311 can be transmitted to the base station via one or more PRACH timings. The UE can use one or more reference signals (e.g., SSB and / or CSI-RS) for selecting the preamble and for determining the PRACH timing. One or more RACH parameters (e.g., ra-ssb-OccasionMskIndex and / or ra-OccasionList) can indicate the association between the PRACH timing and the one or more reference signals.

[0170] If no response is received after the preamble transmission, the UE may perform a preamble retransmission. The UE may increase the uplink transmission power used for the preamble retransmission. The UE may select the initial preamble transmission power based on path loss measurements and / or the target received preamble power configured by the network. The UE may determine the preamble to be retransmitted and may ramp up the uplink transmission power. The UE may receive one or more RACH parameters (e.g., PREAMBLE_POWER_RAMPING_STEP) indicating the ramp step size used for the preamble retransmission. The ramp step size may be the amount by which the uplink transmission power used for the retransmission is incrementally increased. If the UE determines that the same reference signal (e.g., SSB and / or CSI-RS) is used as in the previous preamble transmission, the UE may ramp up the uplink transmission power. The UE may count the number of preamble transmissions and / or retransmissions (e.g., PREAMBLE_TRANSMISSION_COUNTER). For example, if the number of preamble transmissions exceeds a threshold configured by one or more RACH parameters (e.g., preambleTransMax), the UE can determine that the random access procedure has not been successfully completed.

[0171] The Msg 2 1312 received by the UE may include a RAR. In some scenarios, Msg 2 1312 may include multiple RARs corresponding to multiple UEs. Msg 2 1312 may be received after or in response to the transmission of Msg 1 1311. Msg 2 1312 may be scheduled on the DL-SCH and indicated on the PDCCH using a Random Access RNTI (RA-RNTI). Msg 2 1312 may indicate that Msg 1 1311 was received by the base station. Msg 2 1312 may include a time comparison command that the UE can use to adjust the transmission timing of the UE, a scheduling grant for transmitting Msg 3 1313, and / or a Temporary Cell RNTI (TC-RNTI). After transmitting the preamble, the UE may initiate a time window (e.g., ra-ResponseWindow) to monitor the PDCCH of Msg 2 1312. The UE may determine when to initiate the time window based on the PRACH timing used by the UE to transmit the preamble. For example, the UE may initiate a time window of one or more symbols after the last symbol of the preamble (e.g., at the first PDCCH timing starting from the end of the preamble transmission). These one or more symbols may be determined based on a set of parameters. The PDCCH may be in a common search space configured by RRC messages (e.g., a Type 1-PDCCH common search space). The UE may identify the RAR based on a Radio Network Temporary Identifier (RNTI). The RNTI may be used depending on one or more events that initiate the random access procedure. The UE may use a Random Access RNTI (RA-RNTI). The RA-RNTI may be associated with the PRACH timing in which the UE transmits the preamble. For example, the UE may determine the RA-RNTI based on: the OFDM symbol index; the time slot index; the frequency domain index; and / or the UL carrier indicator of the PRACH timing. Examples of RA-RNTIs include:

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

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

[0174] The UE may transmit Msg3 1313 in response to successful reception of Msg 2 1312 (e.g., using the resource identified in Msg 2 1312). Msg 3 1313 can be used for, for example... Figure 13A The diagram illustrates contention resolution in a contention-based random access procedure. In some scenarios, multiple UEs may transmit the same preamble to a base station, and the base station may provide a RAR corresponding to each UE. If these multiple UEs interpret the RAR as corresponding to themselves, a conflict may occur. Contention resolution (e.g., using Msg 3 1313 and Msg 4 1314) can be used to increase the likelihood that a UE will not mistakenly use the identity of another UE. To perform contention resolution, the UE may include the device identifier in Msg 3 1313 (e.g., the TC-RNTI included in Msg 2 1312 if a C-RNTI is assigned, and / or any other suitable identifier).

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

[0176] The UE can be configured with Supplemental Uplink (SUL) carriers and Normal Uplink (NUL) carriers. Initial access (e.g., random access procedures) can be supported on the uplink carriers. For example, the base station can configure two separate RACH configurations for the UE: one for the SUL carrier and another for the NUL carrier. To enable random access in a cell configured with an SUL carrier, the network can indicate which carrier (NUL or SUL) to use. For example, the UE can determine the SUL carrier if the measured quality of one or more reference signals is below a broadcast threshold. Uplink transmissions of the random access procedure (e.g., Msg 11311 and / or Msg 3 1313) can be preserved on the selected carrier. In one or more cases, the UE can switch uplink carriers during the random access procedure (e.g., between Msg 1 1311 and Msg 3 1313). For example, the UE can determine and / or switch uplink carriers for Msg 1 1311 and / or Msg 3 1313 based on channel clarity assessment (e.g., listen before speaking).

[0177] Figure 13B This illustrates a two-step contention-free random access procedure. (Compared to...) Figure 13A The four-step contention-based random access procedure shown is similar, and the base station can transmit configuration message 1320 to the UE before the procedure is initiated. Configuration message 1320 may be similar to configuration message 1310 in some respects. Figure 13B The procedure shown involves the transmission of two messages: Msg 1 1321 and Msg 2 1322. Msg 1 1321 and Msg 2 1322 can be similar in some respects to... Figure 13A The Msg 1 1311 and Msg2 1312 are shown. (As from...) Figure 13A and Figure 13B It will be understood that contention-free random access procedures may not include messages such as Msg 3 1313 and / or Msg4 1314.

[0178] It can be initiated for beam failure recovery, other SI requests, SCell addition and / or handover. Figure 13B The contention-free random access procedure is illustrated. For example, the base station may indicate or assign a preamble to the UE for Msg 1 1321. The UE may receive the preamble indication (e.g., ra-PreambleIndex) from the base station via PDCCH and / or RRC.

[0179] After transmitting the preamble, the UE can initiate a time window (e.g., ra-ResponseWindow) to monitor the PDCCH of the RAR. In the event of a beam failure recovery request, the base station can configure the UE with a separate time window and / or a separate PDCCH within the search space indicated by the RRC message (e.g., recoverySearchSpaceId). The UE can monitor the PDCCH transmission of the Cell RNTI (C-RNTI) addressed to the search space. Figure 13B In the contention-free random access procedure shown, the UE can determine that the random access procedure was successfully completed after or in response to the transmission of Msg 1 1321 and the reception of the corresponding Msg 2 1322. For example, if the PDCCH transmission addresses to the C-RNTI, the UE can determine that the random access procedure was successfully completed. For example, if the UE receives a RAR including a preamble identifier corresponding to the preamble transmitted by the UE and / or the RAR includes a MAC sub-PDU with a preamble identifier, the UE can determine that the random access procedure was successfully completed. The UE can determine that this response is an indication of confirmation of the SI request.

[0180] Figure 13C Another two-step random access procedure is shown. Figure 13A and Figure 13B Similar to the random access procedure shown, the base station can transmit configuration message 1330 to the UE before the procedure is initiated. Configuration message 1330 may be similar in some respects to configuration message 1310 and / or configuration message 1320. Figure 13C The procedure shown includes the transmission of two messages: Msg A1331 and Msg B1332.

[0181] Msg A 1331 can be transmitted by the UE in uplink transmission. Msg A 1331 may include one or more transmissions of preamble 1341 and / or one or more transmissions of transport block 1342. Transport block 1342 may include... Figure 13A The content shown in Msg3 1313 is similar to and / or equivalent to that of Msg3 1313. Transport block 1342 may include UCIs (e.g., SR, HARQ ACK / NACK, etc.). The UE may receive Msg B 1332 after or in response to the transmission of Msg A 1331. Msg B 1332 may include content similar to and / or equivalent to Msg3 1313. Figure 13A and Figure 13B The Msg 2 1312 shown (e.g., RAR) and / or Figure 13A The content shown in Msg 4 1314 is similar to and / or equivalent to the content shown in Msg 4 1314.

[0182] UE can initiate [activities] on licensed spectrum and / or unlicensed spectrum. Figure 13C The two-step random access procedure is used in the UE. The UE may determine whether to initiate a two-step random access procedure based on one or more factors. These one or more factors may be: the radio access technology being used (e.g., LTE, NR, etc.); whether the UE has a valid TA; cell size; the UE's RRC status; the type of spectrum (e.g., licensed vs. unlicensed); and / or any other suitable factors.

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

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

[0185] The UE and the base station can exchange control signaling. The control signaling may be referred to as L1 / L2 control signaling and may originate from the PHY layer (e.g., Layer 1) and / or the MAC layer (e.g., Layer 2). The control signaling may include downlink control signaling transmitted from the base station to the UE and / or uplink control signaling transmitted from the UE to the base station.

[0186] Downlink control signaling may include: downlink scheduling assignment; uplink scheduling authorization indicating uplink radio resources and / or transmission format; time slot format information; preemption indication; power control command; and / or any other suitable signaling. The UE may receive downlink control signaling in the payload transmitted by the base station on the Physical Downlink Control Channel (PDCCH). The payload transmitted on the PDCCH may be referred to as Downlink Control Information (DCI). In some scenarios, the PDCCH may be a group-shared PDCCH (GC-PDCCH) common to the UE group.

[0187] A base station can attach one or more Cyclic Redundancy Check (CRC) parity bits to the DCI to aid in the detection of transmission errors. When the DCI is intended for use with a UE (or a group of UEs), the base station can scramble the CRC parity bits with the UE's identifier (or the UE group's identifier). Scrambling the CRC parity bits with the identifier can include a Modulo-2 appending (or an exclusive OR operation) of the identifier value and the CRC parity bits. This identifier can include the 16-bit value of the Radio Network Temporary Identifier (RNTI).

[0188] DCIs can be used for various purposes. The purpose can be indicated by the type of RNTI used to scramble the CRC parity bits. For example, a DCI with CRC parity bits scrambled using the Paging RNTI (P-RNTI) can indicate paging information and / or system information change notifications. The P-RNTI can be predefined as "FFFE" in hexadecimal. A DCI with CRC parity bits scrambled using the System Information RNTI (SI-RNTI) can indicate broadcast transmission of system information. The SI-RNTI can be predefined as "FFFF" in hexadecimal. A DCI with CRC parity bits scrambled using the Random Access RNTI (RA-RNTI) can indicate a Random Access Response (RAR). A DCI with CRC parity bits scrambled using the Cell RNTI (C-RNTI) can indicate dynamically scheduled unicast transmissions and / or triggering of PDCCH ordered random access. A DCI with CRC parity bits scrambled using the Temporary Cell RNTI (TC-RNTI) can indicate contention resolution (e.g., similar to...). Figure 13AThe Msg 3 shown is Msg 3 of 1313. Other RNTIs configured by the base station for the UE may include: the configured scheduling RNTI (CS-RNTI), transmission power control PUCCH RNTI (TPC-PUCCH-RNTI), transmission power control PUSCH RNTI (TPC-PUSCH-RNTI), transmission power control SRS RNTI (TPC-SRS-RNTI), interrupt RNTI (INT-RNTI), slot format indication RNTI (SFI-RNTI), semi-persistent CSI RNTI (SP-CSI-RNTI), modulation and coding scheme cell RNTI (MCS-C-RNTI), etc.

[0189] Depending on the purpose and / or content of the DCI, the base station may transmit DCI with one or more DCI formats. For example, DCI format 0_0 can be used for PUSCH scheduling in a cell. DCI format 0_0 can be a fallback DCI format (e.g., with a compact DCI payload). DCI format 0_1 ​​can be used for PUSCH scheduling in a cell (e.g., with a larger DCI payload than DCI format 0_0). DCI format 1_0 can be used for PDSCH scheduling in a cell. DCI format 1_0 can be a fallback DCI format (e.g., with a compact DCI payload). DCI format 1_1 can be used for PDSCH scheduling in a cell (e.g., with a larger DCI payload than DCI format 1_0). DCI format 2_0 can be used to provide slot format indication to UE groups. DCI format 2_1 can be used to notify UE groups of physical resource blocks and / or OFDM symbols, where UEs may assume that transmission to UEs is not expected. DCI format 2_2 can be used to transmit Transmission Power Control (TPC) commands for PUCCH or PUSCH. DCI format 2_3 can be used to transmit a set of TPC commands for SRS transmission by one or more UEs. New DCI formats for new features can be defined in future versions. DCI formats can have different DCI sizes, or they can share the same DCI size.

[0190] After scrambling the DCI with RNTI, the base station can process the DCI using channel coding (e.g., polarity coding), rate matching, scrambling, and / or QPSK modulation. The base station can map the coded and modulated DCI onto resource elements used for and / or configured for the PDCCH. Based on the DCI payload size and / or the base station's coverage area, the base station can transmit the DCI via a PDCCH occupying multiple consecutive control channel elements (CCEs). The number of consecutive CCEs (referred to as the aggregation level) can be 1, 2, 4, 8, 16, and / or any other suitable number. CCEs can include the number of resource element groups (REGs) (e.g., 6). REGs can include resource blocks in OFDM symbols. The mapping of the coded and modulated DCI onto resource elements can be based on the mapping between CCEs and REGs (e.g., CCE-to-REG mapping).

[0191] Figure 14A An example of a CORESET configuration for the bandwidth portion is shown. A base station can transmit DCI via PDCCH on one or more control resource sets (CORESETs). A CORESET can include time-frequency resources in which a UE attempts to decode the DCI using one or more search spaces. The base station can configure the CORESET in the time-frequency domain. Figure 14A In the example, the first CORESET 1401 and the second CORESET 1402 appear at the first symbol in the time slot. The first CORESET 1401 overlaps with the second CORESET 1402 in the frequency domain. The third CORESET 1403 appears at the third symbol in the time slot. The fourth CORESET 1404 appears at the seventh symbol in the time slot. CORESETs can have different numbers of resource blocks in the frequency domain.

[0192] Figure 14B An example of CCE-to-REG mapping for DCI transmission is shown in CORESET and PDCCH processing. CCE-to-REG mapping can be interleaved (e.g., for providing frequency diversity) or non-interleaved (e.g., for facilitating interference coordination and / or frequency-selective transmission in the control channel). The base station can perform different or the same CCE-to-REG mappings for different CORESETs. A CORESET can be associated with CCE-to-REG mapping via RRC configuration. A CORESET can be configured with antenna port quasi-co-location (QCL) parameters. Antenna port QCL parameters can indicate the QCL information for the demodulation reference signal (DMRS) used for PDCCH reception in the CORESET.

[0193] The base station can transmit an RRC message to the UE containing configuration parameters for one or more CORESETs and one or more search space sets. The configuration parameters can indicate the association between the search space set and the CORESET. The search space set can include a set of PDCCH candidates formed by CCEs at a given aggregation level. The configuration parameters can indicate: the number of PDCCH candidates to be monitored at each aggregation level; the PDCCH monitoring period and PDCCH monitoring type; one or more DCI formats to be monitored by the UE; and / or whether the search space set is a common search space set or a UE-specific search space set. The set of CCEs in the common search space set can be predefined and known to the UE. The set of CCEs in the UE-specific search space set can be configured based on the UE's identifier (e.g., C-RNTI).

[0194] like Figure 14B As shown, the UE can determine the time-frequency resources of the CORESET based on RRC messages. The UE can determine the CCE-to-REG mapping of the CORESET (e.g., interleaved or non-interleaved and / or mapping parameters) based on the CORESET's configuration parameters. The UE can determine the number of search space sets configured on the CORESET (e.g., up to 10) based on RRC messages. The UE can monitor a set of PDCCH candidates based on the configuration parameters of the search space sets. The UE can monitor a set of PDCCH candidates in one or more CORESETs for detecting one or more DCIs. Monitoring may include decoding one or more PDCCH candidates in the set of PDCCH candidates according to the monitored DCI format. Monitoring may include decoding the DCI content of one or more PDCCH candidates, which have possible (or configured) PDCCH locations, possible (or configured) PDCCH formats (e.g., the number of CCEs, the number of PDCCH candidates in the common search space, and / or the number of PDCCH candidates in the UE-specific search space), and possible (or configured) DCI formats. Decoding may be referred to as blind decoding. The UE can determine that the DCI is valid for the UE in response to a CRC check (e.g., scrambling bits of the CRC parity bit of the DCI that match the RNTI value). The UE can process the information contained in the DCI (e.g., scheduling assignment, uplink grant, power control, slot format indication, downlink preemption, etc.).

[0195] The UE can transmit uplink control signaling (e.g., uplink control information (UCI)) to the base station. Uplink control signaling transmission may include a Hybrid Automatic Repeat Request (HARQ) acknowledgment for a received DL-SCH transport block. The UE may transmit the HARQ acknowledgment after receiving the DL-SCH transport block. Uplink control signaling may include channel state information (CSI) indicating the channel quality of the physical downlink channel. The UE may transmit the CSI to the base station. Based on the received CSI, the base station can determine transmission format parameters (e.g., including multiple antennas and beamforming schemes) for downlink transmission. Uplink control signaling may include a scheduling request (SR). The UE may transmit an SR indicating that uplink data is available for transmission to the base station. The UE may transmit UCI (e.g., HARQ acknowledgment, CSI report, SR, etc.) via the Physical Uplink Control Channel (PUCCH) or the Physical Uplink Shared Channel (PUSCH). The UE may use one of several PUCCH formats to transmit uplink control signaling via the PUCCH.

[0196] Five PUCCH formats can exist, and the UE can determine the PUCCH format based on the size of the UCI (e.g., the number of uplink symbols transmitted in the UCI and the number of UCI bits). PUCCH format 0 can have a length of one or two OFDM symbols and can include two or fewer bits. If more than one or two symbols are transmitted and the number of HARQ-ACK information bits (HARQ-ACK / SR bits) with positive or negative SR is one or two, the UE can use PUCCH format 0 to transmit the UCI in the PUCCH resource. PUCCH format 1 can occupy between four and fourteen OFDM symbols and can include two or fewer bits. If four or more symbols are transmitted and the number of HARQ-ACK / SR bits is one or two, the UE can use PUCCH format 1. PUCCH format 2 can occupy one or two OFDM symbols and can include more than two bits. If more than one or two symbols are transmitted and the number of UCI bits is two or more, the UE can use PUCCH format 2. PUCCH format 3 can occupy between four and fourteen OFDM symbols and can include more than two bits. If four or more symbols are transmitted, the number of UCI bits is two or more, and the PUCCH resource does not include an orthogonal overlay code, the UE can use PUCCH format 3. PUCCH format 4 can occupy between four and fourteen OFDM symbols and can include more than two bits. If four or more symbols are transmitted, the number of UCI bits is two or more, and the PUCCH resource includes an orthogonal overlay code, the UE can use PUCCH format 4.

[0197] The base station can transmit configuration parameters for multiple PUCCH resource sets to the UE using, for example, an RRC message. These multiple PUCCH resource sets (e.g., up to four sets) can be configured on the cell's uplink BWP. A PUCCH resource set can be configured with: a PUCCH resource set index; multiple PUCCH resources (e.g., pucch-Resourceid) with PUCCH resources identified by a PUCCH resource identifier; and / or multiple (e.g., a maximum number) UCI ​​information bits that the UE can transmit using one of the multiple PUCCH resources in the PUCCH resource set. When multiple PUCCH resource sets are configured, the UE can select one of the multiple PUCCH resource sets based on the total bit length of the UCI information bits (e.g., HARQ-ACK, SR, and / or CSI). If the total bit length of the UCI information bits is two or less, the UE can select a first PUCCH resource set with a PUCCH resource set index equal to "0". If the total length of the UCI information bits is greater than two and less than or equal to the first configuration value, the UE can select a second PUCCH resource set with a PUCCH resource set index equal to "1". If the total length of the UCI information bits is greater than the first configuration value and less than or equal to the second configuration value, the UE can select a third PUCCH resource set with a PUCCH resource set index equal to "2". If the total length of the UCI information bits is greater than the second configuration value and less than or equal to the third value (e.g., 1406), the UE can select a fourth PUCCH resource set with a PUCCH resource set index equal to "3".

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

[0199] Figure 15 An example of a wireless device 1502 communicating with a base station 1504 according to an embodiment of this disclosure is shown. The wireless device 1502 and the base station 1504 may be part of a mobile communication network, such as... Figure 1A The mobile communication network 100 shown Figure 1B The mobile communication network 150 shown or any other communication network. Figure 15 The diagram shows only one wireless device 1502 and one base station 1504, but it should be understood that a mobile communication network may include more than one UE and / or more than one base station, which have the same characteristics as... Figure 15 The same or similar configurations shown.

[0200] Base station 1504 can connect wireless device 1502 to the core network (not shown) via radio communication through air interface (or radio interface) 1506. The communication direction from base station 1504 to wireless device 1502 via air interface 1506 is referred to as the downlink, while the communication direction from wireless device 1502 to base station 1504 via air interface 1506 is referred to as the uplink. Downlink transmissions can be separated from uplink transmissions using some combination of FDD, TDD, and / or two duplex technologies.

[0201] In the downlink, data to be transmitted from base station 1504 to wireless device 1502 can be provided to processing system 1508 of base station 1504. This data can be provided to processing system 1508 via, for example, the core network. In the uplink, data to be transmitted from wireless device 1502 to base station 1504 can be provided to processing system 1518 of wireless device 1502. Processing systems 1508 and 1518 can implement Layer 3 and Layer 2 OSI functions to process the data for transmission. Layer 2 may include, for example, regarding… Figure 2A , Figure 2B , Figure 3 and Figure 4A The SDAP layer, PDCP layer, RLC layer, and MAC layer. Layer 3 may include, for example, the SDAP layer, PDCP layer, RLC layer, and MAC layer. Figure 2B The RRC layer.

[0202] After being processed by processing system 1508, data to be sent to wireless device 1502 can be provided to transmission processing system 1510 of base station 1504. Similarly, after being processed by processing system 1518, data to be sent to base station 1504 can be provided to transmission processing system 1520 of wireless device 1502. Transmission processing systems 1510 and 1520 can implement Layer 1 OSI functions. Layer 1 may include information about... Figure 2A , Figure 2B , Figure 3 and Figure 4A The PHY layer. For transmission processing, the PHY layer can perform operations such as forward error correction coding of the transport channel, interleaving, rate matching, mapping of the transport channel to the physical channel, modulation of the physical channel, multiple-input multiple-output (MIMO) or multiple-antenna processing, etc.

[0203] At base station 1504, receiving processing system 1512 can receive uplink transmissions from wireless device 1502. At wireless device 1502, receiving processing system 1522 can receive downlink transmissions from base station 1504. Receiving processing systems 1512 and 1522 can implement Layer 1 OSI functions. Layer 1 may include information about... Figure 2A , Figure 2B , Figure 3 and Figure 4A The PHY layer. For receive processing, the PHY layer can perform tasks such as error detection, forward error correction decoding, deinterleaving, demapping of the transport channel to the physical channel, demodulation of the physical channel, MIMO or multi-antenna processing, etc.

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

[0205] Processing systems 1508 and 1518 may be associated with memory 1514 and memory 1524, respectively. Memory 1514 and memory 1524 (e.g., one or more non-transitory computer-readable media) may store computer program instructions or code that can be executed by processing systems 1508 and / or 1518 to perform one or more of the functions discussed in this application. Although Figure 15 Although not shown, the transmission processing system 1510, transmission processing system 1520, receiving processing system 1512 and / or receiving processing system 1522 may be coupled to a memory (e.g., one or more non-transitory computer-readable media) storing computer program instructions or code that can be executed to perform one or more of their respective functions.

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

[0207] Processing system 1508 and / or processing system 1518 may be connected to one or more peripheral devices 1516 and one or more peripheral devices 1526, respectively. The one or more peripheral devices 1516 and 1526 may include software and / or hardware providing features and / or functions, such as speakers, microphones, keyboards, displays, touchpads, power supplies, satellite transceivers, universal serial bus (USB) ports, hands-free headsets, FM radio units, media players, internet browsers, electronic control units (e.g., for motor vehicles), and / or one or more sensors (e.g., accelerometers, gyroscopes, temperature sensors, radar sensors, lidar sensors, ultrasonic sensors, light sensors, cameras, etc.). Processing system 1508 and / or processing system 1518 may receive user input data from the one or more peripheral devices 1516 and / or the one or more peripheral devices 1526 and / or provide user output data to the aforementioned one or more peripheral devices. The processing system 1518 in wireless device 1502 can receive power from a power source and / or can be configured to distribute power to other components in wireless device 1502. The power source may include one or more power sources, such as a battery, solar cell, fuel cell, or any combination thereof. Processing system 1508 and / or processing system 1518 may be connected to GPS chipset 1517 and GPS chipset 1527, respectively. GPS chipset 1517 and GPS chipset 1527 may be configured to provide geographic location information for wireless device 1502 and base station 1504, respectively.

[0208] Figure 16AAn exemplary structure for uplink transmission 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 modulation symbols onto one or more transport 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 achieved through... Figure 16A Generate CP-OFDM signals for uplink transmission. These functions are shown as examples, and other mechanisms are expected to be implemented in various implementation schemes.

[0209] Figure 16B An exemplary structure for modulation and upconversion of a baseband signal to a carrier frequency is shown. The baseband signal can be a complex-value SC-FDMA or CP-OFDM baseband signal from the antenna port and / or a complex-value Physical Random Access Channel (PRACH) baseband signal. Filtering can be applied before transmission.

[0210] Figure 16C An exemplary structure for downlink transmission is shown. The baseband signal representing the physical downlink channel can perform one or more functions. These functions may include: scrambling coded bits in a codeword to be transmitted over the physical channel; modulating the scrambled bits to generate complex-valued modulation symbols; mapping the complex-valued modulation symbols onto one or more transport 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.

[0211] Figure 16D Another exemplary structure for modulation and upconversion of a baseband signal to a carrier frequency is shown. The baseband signal can be a complex-value OFDM baseband signal at the antenna port. Filtering can be applied before transmission.

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

[0213] A timer can begin running once started and continues running until it stops or expires. If a timer is not running, it can be started, or if it is running, it can be restarted. A timer can be associated with a value (e.g., a timer can start or restart from a certain value, or it can start from zero and expire once it reaches that value). The duration of a timer may not be updated until the timer stops or expires (e.g., due to BWP switching). Timers can be used to measure time periods / windows of a process. When the specification refers to implementations and procedures related to one or more timers, it should be understood that there are multiple ways to implement the one or more timers. For example, it should be understood that one or more of these multiple ways of implementing a timer can be used to measure time periods / windows of a procedure. For example, a random access response window timer can be used to measure a time window for receiving a random access response. In the example, instead of starting and expiring the random access response window timer, the time difference between two timestamps can be used. When the timer restarts, the measurement process for the time window can be restarted. Other exemplary implementations can be provided to restart the measurement of a time window.

[0214] For example, a wireless device can receive one or more messages from a base station that include one or more configuration parameters for a cell.

[0215] The wireless device can be served by multiple TRPs, including a first TRP and a second TRP (e.g., transmitting to or receiving from these multiple TRPs). The first TRP and the second TRP may not be quasi-co-located. The first distance between the first TRP and the wireless device may differ from the second distance between the second TRP and the wireless device.

[0216] The first TRP can be associated with (or belong to) a cell (e.g., the serving cell). The second TRP can be associated with (or belong to) a cell. The wireless device can be in a multi-TRP operation / mode / scenario within the cell.

[0217] The first TRP can be associated with (or belong to) a cell (e.g., the serving cell). The second TRP can be associated with (or belong to) a second cell (e.g., a non-serving cell or a neighboring cell) that is different from the first cell (or the second PCI of the second cell can be different from the PCI of the first cell). The wireless device can be in an inter-cell multi-TRP operation / mode / scenario.

[0218] A wireless device may be equipped with multiple antenna panels. The wireless device may use a first antenna panel to transmit a first uplink signal / transmission (e.g., PUSCH / PUCCH / SRS transmission). For example, the wireless device may transmit the first uplink signal / transmission to a first TRP. The wireless device may use a second antenna panel to transmit a second uplink signal / transmission (e.g., PUSCH / PUCCH / SRS transmission). For example, the wireless device may transmit the second uplink signal / transmission to a second TRP. The first propagation path / distance of the first uplink signal / transmission between the first antenna panel and the first TRP may be different from the second propagation path / distance of the second uplink signal / transmission between the second antenna panel and the second TRP. For example, the first TRP and the second TRP may be different.

[0219] One or more configuration parameters can indicate at least two tags for the cell. The at least two tags can include a first tag and a second tag.

[0220] In the prior art, one or more configuration parameters can indicate at least two tags for a cell, for example, for multiple TRP operations (e.g., inter-cell multiple TRP operations, intra-cell multiple TRP operations, etc.). Each of the at least two tags can be used for (or associated with) a corresponding TRP in multiple TRPs. For example, the first tag of the at least two tags can be associated with a first TRP. The second tag of the at least two tags can be associated with a second TRP.

[0221] For example, in prior art implementations, when the first time alignment timer of the first TAG among at least two TAGs of a cell expires / stops, the wireless device may not perform any uplink transmissions via the cell based on the first time alignment timer of the first TAG, which includes the cell expiring / stopping (or not running). This may be ineffective when the cell is associated with at least two TAGs and the second time alignment timer of the second TAG among at least two TAGs may be running. Stopping (or not performing) uplink transmissions can reduce data rates and increase communication latency. The wireless device may transmit uplink signals based on the second TAG (or to / to the second TRP) regardless of the expiration / stopping of the first time alignment timer of the first TAG associated with the first TRP. The wireless device may transmit to the second TRP without increasing interference (e.g., inter-symbol interference in other cells and / or wireless devices).

[0222] When a cell is associated with at least two tags, including a first tag and a second tag, the exemplary implementation enhances uplink transmission.

[0223] In an exemplary implementation, a first time alignment timer for the first tag may be running. When a second time alignment timer for the second tag expires / stops, the wireless device may i) continue transmitting the first uplink signal associated with the first tag via the cell, and ii) stop / abort (or not perform) transmitting the second uplink signal associated with the second tag via the cell.

[0224] In an exemplary implementation, a second time alignment timer for the second TAG may be running. When the first time alignment timer for the first TAG expires / stops, the wireless device may i) continue transmitting the second uplink signal associated with the second TAG via the cell, and ii) stop / abort (or not perform) transmitting the first uplink signal associated with the first TAG via the cell.

[0225] A first uplink signal associated with a first control resource set pool index, a first SRS resource set, or a cell's PCI may be associated with a first TAG. A second uplink signal associated with a second control resource set pool index, a second SRS resource set, or a second PCI different from the cell's PCI may be associated with a second TAG.

[0226] Exemplary implementations can increase data rates and reduce communication latency.

[0227] For example, in prior art implementations, when the first time alignment timer of the first TAG of at least two TAGs in a cell expires / stops, the MAC layer of the radio device may not command the PHY layer of the radio device to generate an acknowledgment (e.g., ACK / NACK) for the transport block. The radio device (or the PHY layer of the radio device) may not transmit uplink signals (e.g., HARQ-ACK information feedback / bits) that indicate / include acknowledgment (e.g., ACK / NACK) for the transport block. This may be invalid when the cell is associated with at least two TAGs and the second time alignment timer of the second TAG of at least two TAGs may be running. The base station may not know whether the radio device has successfully or unsuccessfully received / decoded the transport block. The base station may transmit downlink signals (e.g., DCI) to reschedule the transport block, even if the radio device has successfully decoded the transport block. This may increase the latency of communication and increase power consumption at the radio device and / or the base station. For example, the transport block may be associated with a second TRP. For example, an uplink signal including / indicating / acknowledgment for the transport block may be associated with the second TAG.

[0228] When a cell is associated with at least two tags, including a first tag and a second tag, an exemplary implementation enhances uplink transmission (e.g., HARQ-ACK information feedback / bits).

[0229] In an exemplary implementation, a first time alignment timer for the first tag may be running. When a second time alignment timer for the second tag expires / stops, the wireless device may i) transmit a first HARQ-ACK information feedback / bit of the first transport block associated with the first tag via the cell, and ii) not transmit a second HARQ-ACK information feedback / bit of the second transport block associated with the second tag via the cell. The MAC layer may, for example, instruct the PHY layer to generate an acknowledgment for the first transport block based on the first time alignment timer of the first tag being running. For example, the first transport block may be associated with the first tag. For example, the first HARQ-ACK information feedback / bit may be associated with the first tag. For example, based on the second time alignment timer of the second tag expiring / stopping (or not running), the MAC layer may not instruct the PHY layer to generate an acknowledgment for the second transport block. For example, the second transport block may be associated with the second tag. For example, the second HARQ-ACK information feedback / bit may be associated with the second tag.

[0230] In an exemplary implementation, the second time alignment timer for the second TAG may be running. When the first time alignment timer for the first TAG expires / stops, the wireless device may i) transmit a second HARQ-ACK information feedback / bit of the second transport block associated with the second TAG via the cell, and ii) not transmit a first HARQ-ACK information feedback / bit of the first transport block associated with the first TAG via the cell. For example, the MAC layer may instruct the PHY layer to generate an acknowledgment for the second transport block based on the second time alignment timer for the second TAG being running. For example, the second transport block may be associated with the second TAG. For example, the second HARQ-ACK information feedback / bit may be associated with the second TAG. For example, based on the expiration / stop (or non-running) of the first time alignment timer for the first TAG, the MAC layer may not instruct the PHY layer to generate an acknowledgment for the first transport block. For example, the first transport block may be associated with the first TAG. For example, the first HARQ-ACK information feedback / bit may be associated with the first TAG.

[0231] Exemplary implementations can reduce communication latency and power consumption at wireless devices and / or base stations.

[0232] Throughout this specification, unless otherwise specified, the magnitudes of the various fields in the time domain can be expressed in time units, where Hz and . The constant k = T s / T c =64, where T s =1 / (Δf) ref ·N f,ref ), Δf ref =15·10 3 Hz and N f，ref =2048.

[0233] Multiple OFDM parameter sets can be supported by the wireless device. The subcarrier spacing (e.g., μ) and cyclic prefix used for the downlink BWP or uplink BWP can be obtained by the wireless device from higher-layer (e.g., RRC or one or more configurations) parameters subcarrierSpacing and cyclicPrefix, respectively.

[0234] For a subcarrier spacing configuration μ (e.g., μ = 0, 1, 2, 3, ...), the time slots can be numbered in ascending order within the subframe. And numbered in ascending order within the frame as follows It can exist in a time slot 10 consecutive OFDM symbols, of which It can be based on / depends on the cyclic prefix (e.g., normal cyclic prefix or extended cyclic prefix). Time slots in subframes. The startup can be time-dependent with OFDM symbols in the same subframe. The start-up alignment.

[0235] Transmissions (e.g., downlink transmissions, uplink transmissions, and sidelink transmissions) can be organized into T... f =(Δf max N f / 100)·T c = A frame with a duration of 10ms. A frame can include T sf =(Δf max N f / 1000)·T c = Ten subframes (or a combination thereof) with a duration of 1 ms. The number of consecutive OFDM symbols in each subframe can be... Each frame can be divided into two equal-sized half-frames with five subframes, where half-frame 0 consists of subframes 0-4 and half-frame 1 consists of subframes 5-9.

[0236] On a carrier, there can be one set of frames in the uplink and one set of frames in the downlink.

[0237] The uplink frame number i used for transmission from the wireless device can be initiated before the corresponding downlink frame is initiated at the wireless device. in

[0238] -N TA It can be the timing advance (or timing advance value) between the downlink and uplink, and N TA,offset This can be a fixed offset used to calculate timing advance. For example, for a msgA transmission on PUSCH, N TA =0 can be used by wireless devices.

[0239] - The higher-level (or RRC or one or more configuration) parameters TACommon, TACommonDrift, and TACommonDriftVariation (if configured) can be exported / determined by the wireless device (or indicated to the wireless device by these higher-level (or RRC or one or more configuration) parameters), otherwise... It can be a timed calibration for network control.

[0240] - This can be calculated / determined by the wireless device based on higher-level parameters (e.g., RRC or one or more configurations) related to satellite ephemeris (if configured); otherwise... It can be a timed correction exported by the UE.

[0241] The wireless device can receive one or more messages that include one or more configuration parameters (e.g., higher-layer parameters, RRC parameters, etc.). One or more configuration parameters (e.g., via n-TimingAdvanceOffset) can indicate the timing advance offset (e.g., N) for the cell (e.g., serving cell, non-serving cell). TA.offset The value of ). In the example, one or more configuration parameters may not indicate the cell's / used cell's timing advance offset (e.g., N). TA,offset The value of ). One or more configuration parameters may not include n-TimingAdvanceOffset. Based on one or more configuration parameters, the cell's / the timing advance offset used for the cell (e.g., N) is not indicated. TA，offset The wireless device can determine the timing advance offset (N) for the cell / used for the cell by setting the value of N. TA，offset The default value for the cell's timing advance offset.

[0242] One or more configuration parameters can indicate at least two uplink carriers for a cell. The at least two uplink carriers can include a first uplink carrier (e.g., NUL) and a second uplink carrier (e.g., SUL). The radio device can apply a timing advance offset (e.g., N...) to the first and second uplink carriers. TA，offset The wireless device can determine / calculate the first timing advance based on the timing advance offset value (or default value) for transmitting the first uplink signal via the first uplink carrier. The wireless device can transmit the first uplink signal via the first uplink carrier based on the first timing advance. The wireless device can determine / calculate the second timing advance based on the timing advance offset value (or default value) for transmitting the second uplink signal via the second uplink carrier. The wireless device can transmit the second uplink signal via the second uplink carrier based on the second timing advance. In the example, the first timing advance of the first uplink carrier (or associated with or corresponding to it) and the second timing advance of the second uplink carrier (or associated with or corresponding to it) can be the same.

[0243] One or more configuration parameters can indicate one or more timing advance groups (TAGs). One or more TAGs can include one or more cells (or be associated with one or more cells). Each TAG in one or more TAGs can include a corresponding cell in one or more cells. One or more configuration parameters can indicate the corresponding TAG in one or more TAGs for each cell in one or more cells.

[0244] A wireless device can receive a timing advance command for a TAG in one or more TAGs (e.g., in a random access response or in an absolute timing advance command MAC CE or a timing advance command MAC CE). The timing advance command may, for example, include a field indicating / identifying the TAG (e.g., TAG ID). The wireless device may receive the timing advance command, for example, via a cell associated with the TAG. The TAG may include at least one cell having said cell. One or more cells may include at least one cell having said cell. The wireless device may, for example, adjust / determine the uplink timing for uplink transmissions (e.g., PUCCH / PUSCH / SRS transmissions) on / via each of the at least one cell in the TAG based on the timing advance command. The wireless device may, for example, base the timing advance command on a timing advance offset (e.g., N...). TA,offset The value (or default value) is used to adjust / determine the uplink timing for uplink transmissions on / via each of at least one cell in the TAG. In the example, the timing advance offset value (or default value) can be the same for each of at least one cell in the TAG. In the example, the uplink timing can be the same for each of at least one cell in the TAG. In the example, the uplink timing for uplink transmissions (e.g., PUCCH / PUSCH / SRS transmissions) can be the same for each of at least one cell.

[0245] For 2 μ A subcarrier spacing (SCS) of 0.15 kHz, and a timing advance command received by the radio device for one or more TAGs within a TAG, can be used in 16.64.T c / 2 μ The multiple aspect indicates the change in uplink timing relative to the current uplink timing for the TAG.

[0246] The wireless device can receive a timing advance command for one or more tags in a TAG (e.g., T). A ).

[0247] In the example, the random access response or absolute timing advance command MAC CE can indicate / include a timing advance command. The wireless device can receive the timing advance command in the random access response or in the absolute timing advance command MAC CE. The timing advance command can be indicated by an index value (e.g., T). A =0, 1, 2, ..., 3846) indicates the timing advance value (e.g., N). TA Wireless devices can set SCS to 2. μ ·15kH zThe TAG for SCS is...kH z The timing advance value (or time alignment) of the TAG is determined / calculated / adjusted to N. TA =T A ·16·64 / 2 μ The timing advance value can be relative to the SCS of the start / earliest / first uplink transmission from the wireless device after receiving the random access response or absolute timing advance command MAC CE.

[0248] In the example, the Timing Advance Command MAC CE can indicate / include a timing advance command. Wireless devices can receive timing advance commands within the Timing Advance Command MAC CE. Timing advance commands can be indicated by index values ​​(e.g., T). A =0, 1, 2, ..., 63) indicates the current timing advance value N. TA_old To the new timing advance value N TA_new Adjustments. For 2 μ • With a 15kHz SCS, the wireless device can determine the new timing advance value as N. TA_new =N TA_old +(T A -31)·16·64 / 2 μ .

[0249] Each cell in at least one cell of the TAG may have / include (or be indicated / configured by one or more configuration parameters) a corresponding uplink carrier (e.g., NUL and / or SUL). For example, a first cell in at least one cell may include a first uplink carrier (e.g., NUL). A second cell in at least one cell may include a second uplink carrier (e.g., SUL). A third cell in at least one cell may include a first uplink carrier (e.g., NUL) and a second uplink carrier (e.g., SUL). A radio device may operate in / for one or more uplink BWPs of at least one cell in the TAG (or may activate one or more uplink carriers of at least one cell in the TAG). A radio device may operate in a corresponding uplink BWP of one or more uplink carriers of each cell in at least one cell (or may activate a corresponding uplink BWP of one or more uplink carriers of each cell in at least one cell). A TAG may include multiple uplink BWPs for at least one cell. The timing advance command (or the value in the timing advance command (or indicated by the timing advance command)) may be relative to the multiple uplink BWPs / the largest SCS among them. A new timing advance value (e.g., N) is used for the uplink BWP with the lower SCS among the multiple uplink BWPs. TA_new The time advance granularity can be rounded by the wireless device to align with the timing advance granularity used for uplink BWP with a lower SCS.

[0250] The timing advance value (e.g., N) will be advanced. TA Adjusting the positive or negative value can respectively indicate whether the uplink transmission timing for TAG is advanced or delayed by the corresponding amount.

[0251] A wireless device can receive a timing advance command for a TAG in one or more TAGs. A TAG may include at least one cell from one or more cells. The wireless device may receive the timing advance command in / on / via uplink time slot n. The wireless device may adjust uplink transmission timing based on the timing advance command. The wireless device may apply the uplink transmission timing adjustment starting from a second uplink time slot. The wireless device may apply the uplink transmission timing adjustment for uplink signal transmission (e.g., PUSCH / PUSCH / SRS transmission). The wireless device may apply the uplink transmission timing adjustment for uplink signal transmission via at least one cell (or via an uplink carrier of at least one cell). Uplink signal transmission may not include, for example, PUSCH transmissions scheduled via RAR uplink grant or fallbackRAR uplink grant. Uplink signal transmission may not include, for example, PUCCH transmissions with HARQ-ACK information in response to successRAR. The wireless device may apply the uplink transmission timing adjustment for uplink transmission via at least one cell. The wireless device can determine the second uplink time slot as uplink time slot n+k+1+2 μ ·K offset ,in For example, N T，1 This can be the duration, in msec, of N1 symbols corresponding to the PDSCH processing time for UE processing capability 1 when the additional PDSCH DM-RS is configured (or indicated by one or more configuration parameters). For example, N T，2 This can be the duration in msec for N2 symbols corresponding to the PUSCH preparation time for UE processing capability 1. For example, N TA，max This can be the maximum timing advance value in msecs that can be provided by the 12-bit TA command field. For example, This can be the number of time slots per subframe. For example, T sf It can be a subframe duration of 1 msec. For example, K offset =K cell,offset -K UE,offset In the example, one or more configuration parameters can indicate K. cell，offset (For example, provided by Koffset in ServingCellConfigCommon). In the example, one or more configuration parameters may not indicate the use of K. cell，offset The value (e.g., Koffset is not in ServingCellConfigCommon). Wireless devices may not indicate the value used for Koffset based on one or more configuration parameters. cell，offset=0 determines the value used for K cell，offset The default value. For example, a wireless device can receive an instruction K. UE，offset The MAC CE command. For example, a wireless device may not receive instructions for K. UE，offset The value of the MAC CE command. Wireless devices can use the K command based on the absence of an indication. UE,offset The MAC CE command determines the value of K based on the value of 0. UE，offset The default values ​​are used. The radio device can determine N1 and N2 using the minimum SCS among the SCS of all configured uplink BWPs for all uplink carriers used in at least one cell in the TAG and the minimum SCS of all configured downlink BWPs for the corresponding downlink carriers (or for at least one cell). For μ = 0, the radio device can determine / assume N1.0 = 14. The radio device can determine the uplink slot n and N2 using the minimum SCS among the SCS of all configured uplink BWPs for all uplink carriers used in at least one cell in the TAG. The wireless device can determine N by taking the minimum SCS among all configurations of the uplink BWP relative to all uplink carriers used in at least one cell in the TAG and for the initial uplink BWP of all configurations indicated by one or more configuration parameters (e.g., provided by the initialUplinkBWP). TA,max The uplink time slot n can be assumed to be T. TA =0 The last uplink time slot that overlaps with the PDSCH reception time slot, wherein the PDSCH reception indicates / includes / provides a timing advance command.

[0252] A radio device can change the active uplink BWP of at least one cell in a TAG. The radio device can activate (or switch to) a new uplink BWP for the cell based on the change of the active uplink BWP. The radio device can change the active uplink BWP between a first time when a timing advance command is received and a second time when adjustments are made to the uplink transmission timing. Based on the change of the active uplink BWP between the first and second times, the radio device can determine the value of the timing advance command (or the timing advance value) based on the SCS of the new active ULBWP. The radio device can change the active uplink BWP after the second time. The radio device can determine / assume the same absolute value (or the same absolute timing advance value) for the timing advance command before and after the change of the active uplink BWP.

[0253] The received downlink timing can be changed. Changes in the received downlink timing may be uncompensated or partially compensated by adjusting the uplink transmission timing without a timing advance command. In this case, the wireless device can adjust the timing advance value accordingly (e.g., N). TA ).

[0254] Two adjacent time slots can overlap, for example, based on timing advance commands. For instance, based on the overlap of two adjacent time slots, the latter time slot can be reduced in duration relative to the former time slot. During the actual transmission time window used for uplink transmissions (e.g., PUSCH / PUCCH / SRS transmissions), the wireless device may not change the timing advance value (e.g., N). TA ).

[0255] A wireless device may receive, for example, one or more messages from a base station that include one or more configuration parameters (e.g., RRC configuration parameters, RRC reconfiguration parameters). The one or more configuration parameters include one or more cell group configuration parameters (e.g., provided by MAC-CellGroupConfig). The one or more cell group configuration parameters may include TAG configuration (e.g., tag-Config). TAG configuration can be used by the wireless device and / or the base station to configure parameters for time alignment groups. TAG configuration can indicate one or more TAGs. The maximum number of one or more TAGs (e.g., maxNrofTAGs) may be equal to a value (e.g., 4, 5, 6, 7, 8, etc.).

[0256] A TAG configuration can specify one or more TAG indices / identifiers (e.g., TAG-Id) for one or more TAGs. A TAG configuration can specify a corresponding TAG index / identifier from one or more TAG indices / identifiers for each TAG within one or more TAGs. Each TAG within one or more TAGs can be identified by / using a corresponding TAG index from one or more TAG indices (e.g., 0, 1, ..., maxNrofTAGs-1). A TAG index of a TAG within one or more TAGs can indicate a TAG for a cell (e.g., SpCell, SCell). A TAG index of a TAG within one or more TAGs can indicate a TAG within a range of cell groups (e.g., MCG, SCG). One or more TAG indices can include TAG indexes.

[0257] A TAG configuration can instruct one or more time alignment timers (e.g., TimeAlignmentTimer) for one or more TAGs. A TAG configuration can instruct a corresponding time alignment timer among one or more time alignment timers for each of the one or more TAGs. Each of the one or more TAGs can be associated with (or correspond to) a corresponding time alignment timer among the one or more time alignment timers. The value of the time alignment timer among the one or more time alignment timers can be in milliseconds (e.g., 500ms, 750ms, ..., 5120ms, 10240ms, or infinity). The time alignment timer of a TAG can instruct / control how long the cell uplink time alignment is for (or belongs to, is associated with, or corresponds to) the TAG. One or more time alignment timers can include the time alignment timer. One or more TAGs can include the TAG.

[0258] One or more configuration parameters can indicate a TAG index within one or more TAG indices for a cell. A TAG index can indicate / identify a TAG within one or more TAGs. One or more configuration parameters can include one or more serving cell configuration parameters for the cell (e.g., ServingCellConfig). One or more serving cell configuration parameters for the cell can include / indicate a TAG index that indicates / identifies a TAG. For example, based on one or more configuration parameters indicating a TAG index for the cell (TAG index indicating / identifying a TAG), the cell may belong to (or may be associated with or may correspond to) a TAG. For example, based on one or more configuration parameters indicating a TAG index for the cell (TAG index indicating / identifying a TAG), a TAG may include (or may be associated with or may correspond to) the cell.

[0259] Wireless devices can handle the relative transmission timing difference between the subframe timing boundary of an E-UTRA PCell and the nearest slot timing boundary of the PSCell to be aggregated for EN-DC operation.

[0260] Wireless devices can handle the relative transmission timing difference between the closest time slot timing boundaries of different carriers to be aggregated in NR carrier aggregation.

[0261] Wireless devices can handle the relative transmission timing difference between the time slot timing boundary of the PCell and the subframe timing boundary of the E-UTRA PSCell to be aggregated for NE-DC operation.

[0262] Wireless devices can handle the relative transmission timing difference between the PCell's time slot timing boundary and the nearest time slot timing boundary of the PSCell to be aggregated in NR DC operation.

[0263] The wireless device can handle the relative transmission timing difference between time slot timings for at least all pairs of TAGs (or all pairs of one or more TAGs). For example, based on one or more configuration parameters indicating a primary TAG (pTAG) and secondary TAG (sTAG) for inter-band NR carrier aggregation in standalone (SA) or NR-DC mode, the wireless device can handle the relative transmission timing difference between time slot timings for at least all pairs of TAGs. Similarly, based on one or more configuration parameters indicating more than one sTAG for inter-band NR carrier aggregation in EN-DC or NE-DC mode, the wireless device can handle the relative transmission timing difference between time slot timings for at least all pairs of TAGs.

[0264] One or more tags may include a first tag and a second tag.

[0265] The first tag can be / operating on FR1. The second tag can be / operating on FR1. The maximum uplink transmission time difference between the first tag and the second tag can be 34.6 microseconds ( / mu).

[0266] The first tag can be / operates on FR2. The second tag can be / operates on FR2. The maximum uplink transmission time difference between the first tag and the second tag can be 8.5 microseconds ( / mu). The wireless device can perform independent beam management for FR2 inter-band carrier aggregation.

[0267] In the example, the first tag can be / operates at FR1 and the second tag can be / operates at FR2. In the example, the first tag can be / operates at FR2 and the second tag can be / operates at FR1. The maximum uplink transmission time difference between the first and second tags can be 26.1 microseconds ( / mu).

[0268] In RRC_CONNECTED, the base station can maintain timing advance to keep the Layer 1 (L1) synchronization of the radio equipment. Serving cells that have / have the same timing advance applied to their uplinks and use the same timing reference cell can be grouped by the base station into one or more TAGs. Each of the one or more TAGs can contain / include at least one serving cell configured with an uplink. The mapping of each serving cell to (corresponding) TAG can be configured / indicated by RRC configuration parameters (e.g., tag-Id).

[0269] For the primary TAG (pTAG), in addition to utilizing the shared spectrum channel access that can also be used in some cases with SCells, the radio device can use the PCell as a timing reference. In the secondary TAG (sTAG), the radio device can use any of the active SCells of this TAG (or sTAG) as a timing reference cell.

[0270] Pre-update timing can be signaled / indicated by the base station to the wireless device via a MAC CE command. Based on the received MAC CE command, the wireless device can start or restart a TAG-specific timer (e.g., a time alignment timer). The TAG-specific timer can indicate whether the wireless device's L1 is synchronized. For example, when the TAG-specific timer is running, L1 can be (considered) synchronized. When the TAG-specific timer is not running, L1 can be (considered) asynchronous. When L1 is asynchronous, the wireless device can transmit / perform uplink transmissions via / MSG1 / MSGA. When L1 is asynchronous, the wireless device may not transmit / perform uplink transmissions via / PUSCH / PUCCH / SRS.

[0271] A wireless device can transmit / report User Equipment (UE) capability messages (e.g., UE capability information) to a base station. The wireless device can transmit / report UE capability messages to the base station, for example, based on receiving a UE capability query / request from the base station. The base station can request / transmit UE capability messages from the wireless device via / through a UE capability query / request. UE capability messages (or UE capability information) can be RRC messages transmitted / sent / reported by the wireless device to the base station. The wireless device can transmit UE capability messages, for example, during the initial registration process.

[0272] The UE capability message can indicate the number of supported tags (supportedNumberTAG). The UE capability message may include carrier aggregation (CA) parameters, indicated by the radio device, that include the number of supported tags. The number of supported tags can be applied by the radio device and / or base station for NR CA, NR-DC, (NG)EN-DC / NE-DC, and DAPS handover.

[0273] For (NG)EN-DC / NE-DC, the number of supported TAGs can indicate the number of TAGs used for NR CG. The number of TAGs used for LTEMCG can be signaled / indicated from the base station to the radio device via LTE TAG capability signaling. For NRCA / NR-DC band combinations, if the band combination includes more than one band entry (i.e., non-contiguous band combinations between or within bands), the number of supported TAGs can indicate the different timing advances supported on different band entries. For NR-DC, the number of supported TAGs can be more than one. Radio devices can be forced to support more than one TAG for NR-DC.

[0274] For inter-frequency DAPS, the number of supported tags can be two. Radio devices can be forced to support two tags for inter-frequency DAPS. For mixed inter-band and intra-band NR CA / NR-DC band combinations, if the base station configures more discontinuous uplink serving cells than the number of supported tags, for example, through one or more configuration parameters, then the one or more configuration parameters indicate the same tag (or the same tag ID / index) for one or more uplink serving cells in the same band.

[0275] The UE capability message may not indicate / include the number of supported tags (supportedNumberTAG). The number of supported tags may not be in the UE capability message. The radio device may support a single tag (or only one tag) based on the absence of the number of supported tags in the UE capability message. The radio device may support a single tag for NR.

[0276] The maximum number of one or more TAGs indicated by one or more configuration parameters (or TAG configurations) (e.g., maxNrofTAGs) can be equal to or less than the number of TAGs supported. The maximum number of one or more TAGs indicated by one or more configuration parameters (or TAG configurations) (e.g., maxNrofTAGs) can be no greater than the number of TAGs supported.

[0277] A TAG may include a group of cells (e.g., serving cells). One or more configuration parameters may indicate a TAG for a group of cells. One or more TAGs include the TAG. One or more configuration parameters may indicate uplink (e.g., PUCCH, PUSCH, PRACH, SRS, etc.) for a group of cells (or for each cell in a group of cells). The radio device may use the same timing reference cell for a group of cells (or for each cell in a group of cells). The radio device may use the same timing advance for a group of cells (or for each cell in a group of cells). The radio device may transmit a first uplink signal / transmission (e.g., PUCCH / PUSCH / SRS / PRACH transmission) based on the timing reference cell via a first cell in the group of cells. The radio device may transmit a second uplink signal / transmission (e.g., PUCCH / PUSCH / SRS / PRACH transmission) based on the (same) timing reference cell via a second cell in the group of cells. The radio device may transmit a first uplink signal / transmission based on a timing advance value via a first cell in the group of cells. Wireless devices can transmit a second uplink signal / transmission via a second cell in a cell group based on the (same) timing advance value.

[0278] A SpCell's TAG that includes / contains the MAC entity of a wireless device can be referred to as the Primary Timing Advance Group (PTAG). A SpCell's TAG that does not include / contains the MAC entity of a wireless device can be referred to as the Secondary Timing Advance Group (STAG).

[0279] For dual-connectivity operation, depending on whether the radio device's MAC entity is associated with the MCG or SCG respectively, the special cell (SpCell) can refer to the primary cell (PCell) of the MCG or the primary / secondary cell (PSCell) of the SCG. Otherwise, the SpCell can refer to the PCell. The SpCell can support PUCCH transmission and contention-based random access. The SpCell can be activated. The SpCell can not be deactivated (e.g., always active).

[0280] One or more configuration parameters may indicate a TAG within one or more TAGs for a cell. One or more configuration parameters may indicate a first uplink carrier (e.g., NUL) and a second uplink carrier (e.g., SUL) for a cell. One or more configuration parameters may include supplementary uplink parameters (e.g., supplementaryUplink) indicating the second uplink carrier. The cell's first uplink carrier and second uplink carrier may belong to the same TAG. A cell configured with a second uplink carrier (or supplementaryUplink) may belong to a single TAG. A cell configured with a second uplink carrier (or supplementaryUplink) may not belong to a second TAG different from the stated TAG within one or more TAGs.

[0281] One or more TAGs may include PTAGs. PTAGs may include SpCells (e.g., PCells).

[0282] One or more configuration parameters can instruct one or more time alignment timers (e.g., timeAlignmentTimer) for one or more TAGs. One or more configuration parameters can instruct a corresponding time alignment timer among one or more time alignment timers for each TAG in one or more TAGs. One or more configuration parameters can instruct one or more time alignment timers, for example, for maintaining uplink time alignment. For example, one or more configuration parameters can instruct a first time alignment timer among one or more time alignment timers for a first TAG in one or more TAGs. One or more configuration parameters can instruct a second time alignment timer among one or more time alignment timers for a second TAG in one or more TAGs. For example, the time alignment timers among one or more time alignment timers can be per TAG. For example, each time alignment timer among one or more time alignment timers can be per TAG.

[0283] One or more configuration parameters can instruct one or more time alignment timers for a TAG within one or more TAGs. A TAG can include at least one cell. At least one cell can belong to (or be associated with) a TAG. One or more configuration parameters can instruct a TAG for at least one cell. One or more configuration parameters can instruct a TAG for each cell in at least one cell. The time alignment timer can control how long the MAC entity of the radio device considers uplink time alignment for at least one cell (e.g., at least one serving cell) belonging to the TAG.

[0284] The wireless device can receive a timing advance command MAC CE. The timing advance command MAC CE can indicate one or more TAGs. The timing advance command MAC CE can indicate / include a timing advance command. The wireless device can maintain a timing advance (or a timing advance value or N) for the indicated TAG. TA The wireless device can apply a timing advance command to the indicated TAG. The wireless device can start or restart the time alignment timer associated with the indicated TAG. One or more configuration parameters can instruct one or more time alignment timers in the time alignment timer list for the indicated TAG.

[0285] The wireless device may transmit a random access preamble for a random access procedure. The wireless device may receive a random access response (or random access response message) from / for a cell (e.g., the serving cell). The random access response may correspond to (or be associated with) the random access preamble. The random access response may include a timing advance command. The cell may belong to one or more TAGs. One or more configuration parameters may indicate TAGs for the cell. One or more configuration parameters may indicate one or more time alignment timers for the TAG.

[0286] The random access procedure can be, for example, a four-step random access procedure. The random access procedure can also be, for example, a two-step random access procedure. The random access response can be a MsgB of a two-step random access procedure. When the random access procedure is a two-step random access procedure, the cell can be, for example, a SpCell.

[0287] For example, a wireless device (or the MAC entity of a wireless device) may not select a random access preamble from one or more random access preambles used / configured for a contention-based random access procedure. The random access procedure can be, for example, a contention-free random access procedure (e.g., PDCCH command, handover, beam failure recovery, etc.). The wireless device may apply a timing advance command in the random access response for a TAG including the cell. The wireless device may start or restart a time alignment timer associated with a TAG including the cell.

[0288] For example, a wireless device (or its MAC entity) can select a random access preamble from one or more random access preambles used / configured for a contention-based random access procedure. The random access procedure can be, for example, a contention-based random access procedure. The time alignment timer for the cell's TAG may not be running. The wireless device can apply a timing advance command to the random access response for the cell's TAG. The wireless device can start the time alignment timer associated with the cell's TAG. The wireless device can start the time alignment timer, for example, based on receiving a random access response.

[0289] A wireless device can stop the time alignment timer associated with a TAG that includes the cell. For example, if contention resolution based on a random access protocol (or a contention-based random access protocol) is unsuccessful (or not successful), the wireless device can stop the time alignment timer.

[0290] The radio device can stop the time alignment timer associated with the TAG that includes the cell. For example, the radio device can stop the time alignment timer based on the HARQ feedback transmitted for the MAC PDU that includes / includes the UE contention resolution identity MAC CE. Contention resolution of the random access procedure (or contention-based random access procedure) can be successful. The radio device can initiate a random access procedure (or transmit a random access preamble) in response to a System Information (SI) request.

[0291] For example, a wireless device (or its MAC entity) can select a random access preamble from one or more random access preambles used / configured for a contention-based random access procedure. The random access procedure can be, for example, a contention-based random access procedure. A time alignment timer, including the cell's TAG, may be running. The wireless device can ignore timing advance commands in the random access response.

[0292] The wireless device can transmit MSGA transmissions for a two-step random access procedure (e.g., random access preamble plus PUSCH transmission). The MSGA transmission may include / include a C-RNTI MAC CE. The wireless device can receive an absolute timing advance command MAC CE. For example, based on the MSGA transmission including / including a C-RNTI MAC CE, the wireless device can receive an absolute timing advance command MAC CE. The absolute timing advance command MAC CE may indicate / include a timing advance command. The wireless device can apply a timing advance command to a PTAG. One or more configuration parameters can indicate one or more time alignment timers in a time alignment timer for the PTAG. The wireless device can, for example, start a time alignment timer associated with the PTAG based on receiving an absolute timing advance command MAC CE.

[0293] One or more configuration parameters can instruct one or more time alignment timers for one or more TAGs. Time alignment timers may expire.

[0294] A TAG can be a PTAG. A time alignment timer can be associated with a PTAG. Based on the expiration of the time alignment timer, the wireless device can perform at least one of the following:

[0295] Refresh all HARQ buffers in all serving cells;

[0296] Notify RRC to release the PUCCH of all serving cells, if configured;

[0297] Notify RRC to release the SRS of all serving cells, if configured;

[0298] Clear any configured downlink assignments and configured uplink permissions;

[0299] Remove any PUSCH resources used for semi-persistent CSI reporting;

[0300] Treat all running timeAlignmentTimers (e.g., the one or more time alignment timers) as expired;

[0301] Maintain the timing advance value for all TAGs (or one or more of the TAGs) (e.g., NTA ).

[0302] A TAG can be a STAG. A time alignment timer can be associated with a STAG. Based on the expiration of the time alignment timer, the wireless device can perform at least one of the following:

[0303] Flush all HARQ buffers;

[0304] If configured, notify RRC to release PUCCH;

[0305] If configured, notify RRC to release SRS;

[0306] Clear any configured downlink assignments and configured uplink permissions;

[0307] Remove any PUSCH resources used for semi-persistent CSI reporting;

[0308] Maintain the timing advance value of STAG (e.g., NTA).

[0309] In the example, the maximum uplink transmission time difference between the first and second tags may be exceeded. One or more tags may include the first tag and the second tag. The radio device (or the MAC entity of the radio device) may stop / abort uplink transmissions via / for a cell (e.g., SCell). For example, based on the maximum uplink transmission time difference between the first and second tags being exceeded, the radio device (or the MAC entity of the radio device) may stop / abort uplink transmissions via / for the cell. The tags in one or more tags may include the cell. For example, the tag may be different from the first tag. The tag may be different from the second tag. For example, the tag may be the first tag. For example, the tag may be the second tag. One or more configuration parameters may instruct one or more time alignment timers in one or more time alignment timers for the tags in one or more tags. The radio device may determine / assume / consider the time alignment timer of the tag associated with the cell to expire. For example, based on the maximum uplink transmission time difference between the first and second tags being exceeded, the radio device may determine / assume / consider the time alignment timer of the tag associated with the cell to expire.

[0310] One or more configuration parameters can instruct one or more time alignment timers for one or more TAGs. A TAG can include at least one cell. One or more configuration parameters can instruct a TAG for at least one cell (or for each cell in at least one cell). Time alignment timers may expire (or may not be running).

[0311] For example, based on the expiration (or non-operation) of the time alignment timer, the wireless device may not transmit uplink transmissions via at least one cell in the TAG / on at least one cell in the TAG. For example, based on the expiration (or non-operation) of the time alignment timer, the wireless device may stop uplink transmissions via at least one cell (or via each of at least one cell). For example, based on the expiration (or non-operation) of the time alignment timer, the wireless device may not perform uplink transmissions via at least one cell (or via each of at least one cell). For example, based on the expiration (or non-operation) of the time alignment timer, the wireless device may not perform uplink transmissions via at least one cell. Uplink transmissions may include PUSCH / PUCCH / SRS transmissions. Uplink transmissions may not include PRACH transmissions (e.g., random access preamble and MSGA transmissions).

[0312] In the example, a TAG can be a PTAG. For example, based on the expiration (or non-operation) of the time alignment timer associated with the PTAG, the wireless device may not transmit uplink transmissions via one or more cells in one or more TAGs / on one or more cells in one or more TAGs. For example, based on the expiration (or non-operation) of the time alignment timer associated with the PTAG, the wireless device may not transmit uplink transmissions via each cell in one or more TAGs / on each cell in one or more TAGs. For example, based on the expiration (or non-operation) of the time alignment timer associated with the PTAG, the wireless device may stop uplink transmissions via one or more cells (or via each cell in one or more TAGs). For example, based on the expiration (or non-operation) of the time alignment timer associated with the PTAG, the wireless device may not perform uplink transmissions via one or more cells (or via each cell in one or more TAGs). For example, based on the expiration (or non-operation) of the time alignment timer associated with the PTAG, the wireless device may not perform uplink transmissions via cells in one or more cells in one or more TAGs. Uplink transmissions may include PUSCH / PUCCH / SRS transmissions. Uplink transmissions may exclude PRACH transmissions (e.g., random access preamble and MSGA transmissions) on SpCell (e.g., PCell).

[0313] A timing advance command (MAC CE) can be identified by a MAC subheader with an LCID (e.g., 61). A timing advance command (MAC CE) can have a fixed size. A timing advance command (MAC CE) can comprise a single octet.

[0314] The scheduled advance command MAC CE can include one or more fields.

[0315] One or more fields may include a TAG identity (TAG ID). The field may indicate / include the TAG identity of the TAG. One or more TAGs may include the TAG. A TAG that includes / includes a SpCell may have a TAG identity equal to 0. The field length may be 2 bits.

[0316] One or more fields may include a timing advance command. This field may indicate an index value (e.g., T) of the timing adjustment amount that must be applied to control the wireless device or (or the wireless device's MAC entity). A =0, 1, 2...63). The field length can be 6 bits.

[0317] An absolute timing advance command (MAC CE) can be identified by a MAC subheader with an LCID. An absolute timing advance command (MAC CE) can have a fixed size. An absolute timing advance command (MAC CE) can include two octets.

[0318] The absolute timing advance command MAC CE can include one or more fields.

[0319] One or more fields may include a timing advance command. This field may indicate an index value (e.g., T) of the timing adjustment amount that must be applied to control the wireless device or (or the wireless device's MAC entity). A The field length can be 12 bits.

[0320] In the example, for a two-step random access procedure (BAP), the wireless device can transmit a random access preamble (e.g., an MSGA preamble). The BAP can transmit an MSGA transmission. The MSGA transmission may include the transmission of the random access preamble and a PUSCH transmission. The wireless device may initiate a response window (e.g., a msgB-ResponseWindow) based, for example, on the transmitted random access preamble. The PUSCH transmission may include / indicate a C-RNTI MAC CE, which instructs the wireless device's C-RNTI. The wireless device may monitor the downlink control channel on / via the SpCell for a DCI scheduled for a random access response corresponding to (or associated with) the random access preamble. The wireless device may monitor the downlink control channel during / while the response window is running for the DCI scheduled for the random access response. The CRC of the DCI may be scrambled by the C-RNTI. The wireless device may receive the DCI scheduled for the random access response. For beam failure recovery, the wireless device may not initiate a two-step random access procedure. For beam failure recovery, the radio device may not transmit the random access preamble. A time alignment timer associated with the PTAG may be running. One or more configuration parameters can instruct the time alignment timer for the PTAG. One or more PTAGs may include the TAG. One or more time alignment timers may include the time alignment timer. The DCI (or random access response) may include / indicate an uplink grant. The uplink grant may be for a new uplink transmission. Based on the running of the time alignment timer associated with the PTAG, the radio device can determine / consider the reception of the random access response successful. Based on the running of the time alignment timer associated with the PTAG, the radio device can stop the response window. Based on the running of the time alignment timer associated with the PTAG, the radio device can determine / consider the two-step random access procedure successful.

[0321] The wireless device can receive DCI. The wireless device can receive DCI during / via PDCCH monitoring time (or PDCCH time). The wireless device can monitor the downlink control channel for DCI during PDCCH monitoring time.

[0322] For example, DCI can include / indicate downlink assignment.

[0323] The CRC of a DCI can be scrambled by, for example, C-RNTI. The CRC of a DCI can be scrambled by, for example, CS-RNTI. The CRC of a DCI can be scrambled by, for example, temporary C-RNTI.

[0324] One or more configuration parameters can indicate the configured downlink assignment (e.g., SPS PDSCH configuration). The wireless device can receive one or more SPS PDSCHs (or one or more SPS PDSCH receptions) for the configured downlink assignment.

[0325] In the example, the DCI can indicate that the SPS is disabled / released. The DCI can include a New Data Indicator (NDI) field. The value of the NDI field can be, for example, equal to zero. The DCI can include one or more fields (e.g., RV, HARQ, TDRA, FDRA) that are set to indicate that the SPS is disabled. For example, based on receiving a DCI indicating that the SPS is disabled, the wireless device can clear the configured downlink assignment. For example, based on clearing the configured downlink assignment, the wireless device can not receive one or more SPS PDSCHs (or one or more SPS PDSCH receptions) for the configured downlink assignment. The DCI may or may not schedule PDSCH receptions.

[0326] The wireless device can transmit (or decides to transmit) HARQ-ACK information feedback / bits for SPS deactivation. The wireless device can transmit HARQ-ACK information feedback / bits, for example, to acknowledge receipt of DCI indicating SPS deactivation.

[0327] In the example, DCI can schedule PDSCH reception (or transport blocks). The wireless device can transmit (or decide to transmit) HARQ-ACK information feedback / bits for PDSCH reception (or for transport block reception).

[0328] In the example, the DCI can indicate SCell sleep for one or more cells. The radio device can transmit (or decides to transmit) HARQ-ACK information feedback / bits for SCell sleep. The radio device can transmit HARQ-ACK information feedback / bits, for example, to acknowledge receipt of the DCI indicating SCell sleep. The DCI may or may not schedule PDSCH reception.

[0329] In the example, the DCI can indicate a TCI state update (e.g., a unified TCI state) for one or more cells. The radio device can transmit (or decides to transmit) a HARQ-ACK information feedback / bit for the TCI state update. The radio device can transmit the HARQ-ACK information feedback / bit, for example, to acknowledge receipt of the DCI indicating the TCI state update. The DCI may or may not schedule PDSCH reception.

[0330] Wireless devices can transmit HARQ-ACK information feedback / bits via a cell. One or more configuration parameters can indicate one or more tags in a tag for a cell. A tag can include a cell. A cell can belong to a tag. One or more configuration parameters can indicate one or more time alignment timers in a time alignment timer for a tag that includes a cell.

[0331] In the example, the time alignment timer may be running.

[0332] A wireless device (or its MAC layer) can indicate a positive acknowledgment to its physical layer. For example, based on the running of a time alignment timer, the wireless device (or its MAC layer) can indicate a positive acknowledgment to its physical layer. For example, based on the running of a time alignment timer, the wireless device (or its physical layer) can transmit a positive acknowledgment via cell transmission. For example, based on the running of a time alignment timer, the wireless device (or its physical layer) can transmit a HARQ-ACK information feedback / bit set to (or indicating) a positive acknowledgment via cell transmission.

[0333] It is confirmed that, for example, SPS can be disabled. It is confirmed that, for example, PDSCH reception scheduled by DCI can be enabled. It is confirmed that, for example, SCell sleep can be enabled. It is confirmed that, for example, TCI status updates can be enabled.

[0334] In the example, the time alignment timer may not be running (or may have been stopped or may have expired).

[0335] A wireless device (or its MAC layer) may not command its physical layer to generate an acknowledgment (e.g., a positive or negative acknowledgment). For example, if the time alignment timer is not running, the wireless device (or its MAC layer) may not command its physical layer to generate an acknowledgment. Similarly, if the time alignment timer is running, the wireless device (or its physical layer) may not transmit an acknowledgment via the cell. Furthermore, if the time alignment timer is running, the wireless device (or its physical layer) may not transmit HARQ-ACK information feedback / bits via the cell.

[0336] For example, if the time alignment timer is not running (or has been stopped or expired), the wireless device (or its MAC layer) may not instruct the physical layer to generate an acknowledgment for SPS disabling. Similarly, if the time alignment timer is not running (or has been stopped or expired), the wireless device (or its MAC layer) may not instruct the physical layer to generate an acknowledgment for PDSCH reception scheduled by DCI. Likewise, if the time alignment timer is not running (or has been stopped or expired), the wireless device (or its MAC layer) may not instruct the physical layer to generate an acknowledgment for SCell sleep. Finally, if the time alignment timer is not running (or has been stopped or expired), the wireless device (or its MAC layer) may not instruct the physical layer to generate an acknowledgment for TCI state updates.

[0337] The HARQ-ACK information feedback bit can be used, for example, for SPS deactivation. The HARQ-ACK information feedback bit can be used, for example, for PDSCH reception scheduled by DCI. The HARQ-ACK information feedback bit can be used, for example, for SCell sleep. The HARQ-ACK information feedback bit can be used, for example, for TCI status updates.

[0338] In the example, one or more configuration parameters may include one or more sidelink PUCCH configuration parameters (e.g., sl-PUCCH-Config).

[0339] Figure 17 and Figure 18 An example of multiple timing advance groups according to one aspect of an embodiment of this disclosure is shown.

[0340] In the example, the wireless device can receive one or more messages. In the example, the wireless device can receive one or more messages from a base station. In the example, the wireless device can receive one or more messages from a relay node. In the example, the wireless device can receive one or more messages from another wireless device (e.g., a TRP, a vehicle, a remote wireless head, etc.). One or more messages may include one or more configuration parameters (e.g., ...). Figure 17(Configuration parameters at time T1). In the example, one or more configuration parameters can be RRC configuration parameters. In the example, one or more configuration parameters can be RRC reconfiguration parameters.

[0341] In the example, one or more configuration parameters can be applied to one or more cells.

[0342] One or more cells may include a cell. The cell may be, for example, a serving cell. In the example, at least one of the one or more configuration parameters may be cell-specific. In the example, the cell may be a primary cell (PCell). In the example, the cell may be a secondary cell (SCell). The cell may be a secondary cell configured with a PUCCH (e.g., a PUCCH SCell). In the example, the cell may be, for example, an unlicensed cell operating in an unlicensed frequency band. In the example, the cell may be, for example, a licensed cell operating in a licensed frequency band. In the example, the cell may operate in a first frequency range (FR1). For example, FR1 may include frequency bands below 6 GHz. In the example, the cell may operate in a second frequency range (FR2). For example, FR2 may include frequency bands from 24 GHz to 52.6 GHz. In the example, the cell may operate in a third frequency range (FR3). For example, FR3 may include frequency bands from 52.6 GHz to 71 GHz. For example, FR3 may include frequency bands starting at (or above) 52.6 GHz.

[0343] In the example, the wireless device can perform uplink transmissions (e.g., PUSCH, PUCCH, PUCCH) of the cell / via the cell at a first time and at a first frequency. The wireless device can perform downlink receptions (e.g., PDCCH, PDSCH) of the cell / via the cell at a second time and at a second frequency. In the example, the cell can operate in Time Division Duplex (TDD) mode. In TDD mode, the first and second frequencies can be the same. In TDD mode, the first and second times can be different. In the example, the cell can operate in Frequency Division Duplex (FDD) mode. In FDD mode, the first and second frequencies can be different. In FDD mode, the first and second times can be the same.

[0344] In the example, the wireless device can be in RRC connected mode. In the example, the wireless device can be in RRC idle mode. In the example, the wireless device can be in RRC inactive mode.

[0345] In the example, a cell may include multiple BWPs. These multiple BWPs may include one or more uplink BWPs, which include the cell's uplink BWPs. These multiple BWPs may also include one or more downlink BWPs, which include the cell's downlink BWPs.

[0346] In the example, one of the multiple downlink BWPs can be in an active or inactive state. In the example, when one or more downlink BWPs is active, the wireless device can monitor downlink channels / signals (e.g., PDCCH, DCI, CSI-RS, PDSCH) on / through / via the downlink BWP. In the example, when one or more downlink BWPs is active, the wireless device can receive PDSCH on / through / for the downlink BWP. In the example, when one or more downlink BWPs is inactive, the wireless device cannot monitor downlink channels / signals (e.g., PDCCH, DCI, CSI-RS, PDSCH) on / through / for the downlink BWP. In the example, when one or more downlink BWPs is inactive, the wireless device cannot monitor downlink channels / signals (e.g., PDCCH, DCI, CSI-RS, PDSCH) on / through / for the downlink BWP. When one or more downlink BWPs is inactive, the wireless device can stop monitoring (or receiving) downlink channels / signals (e.g., PDCCH, DCI, CSI-RS, PDSCH) on / through / for the downlink BWP. In the example, when one or more downlink BWPs are inactive, the radio device cannot receive PDSCH on / via / for the downlink BWP. When one or more downlink BWPs are inactive, the radio device can stop receiving PDSCH on / via / for the downlink BWP.

[0347] In the example, when one or more uplink BWPs is active, the wireless device can transmit uplink signals / channels (e.g., PUCCH, preamble, PUSCH, PRACH, PUCCH, etc.) on / via the uplink BWP. In the example, when one or more uplink BWPs is inactive, the wireless device cannot transmit uplink signals / channels (e.g., PUCCH, preamble, PUSCH, PRACH, PUCCH, etc.) on / via the uplink BWP.

[0348] In the example, the wireless device can activate one or more downlink BWPs in the cell. In the example, activating a downlink BWP can include setting (or switching) the downlink BWP to the active downlink BWP of the cell. In the example, activating a downlink BWP can include setting the downlink BWP to an active state. In the example, activating a downlink BWP can include switching the downlink BWP from an inactive state to an active state.

[0349] In the example, the wireless device can activate one or more uplink BWPs of the cell. In the example, activating an uplink BWP can include the wireless device setting (or switching) the uplink BWP to the cell's active uplink BWP. In the example, activating an uplink BWP can include setting the uplink BWP to an active state. In the example, activating an uplink BWP can include switching the uplink BWP from an inactive state to an active state.

[0350] In the example, the one or more configuration parameters can be for the (active) downlink BWP of the cell. In the example, at least one of the one or more configuration parameters can be for the downlink BWP of the cell.

[0351] In the example, the one or more configuration parameters can be for the (active) uplink BWP of the cell. In the example, at least one of the one or more configuration parameters can be for the uplink BWP of the cell.

[0352] One or more configuration parameters can indicate the subcarrier spacing (or set of parameters) used for the downlink BWP.

[0353] One or more configuration parameters can indicate the subcarrier spacing (or set of parameters) used for the uplink BWP.

[0354] The subcarrier spacing value (for the downlink BWP and / or uplink BWP) can be / indicated, for example, 15kHz (mu=0). The subcarrier spacing value can be / indicated, for example, 30kHz (mu=1). The subcarrier spacing value can be / indicated, for example, 60kHz (mu=2). The subcarrier spacing value can be / indicated, for example, 120kHz (mu=3). The subcarrier spacing value can be / indicated, for example, 240kHz (mu=4). The subcarrier spacing value can be / indicated, for example, 480kHz (mu=5). The subcarrier spacing value can be / indicated, for example, 960kHz (mu=6). For example, 480kHz may be valid / applicable in FR3. For example, 960kHz may be valid / applicable in FR3. For example, 240kHz may be valid / applicable in FR3. For example, 120kHz may be valid / applicable in FR3.

[0355] In the example, one or more configuration parameters can indicate multiple control resource sets (coresets). One or more configuration parameters can indicate multiple coresets for the (active) downlink BWP of the cell. The (active) downlink BWP can include multiple coresets.

[0356] In the example, one or more configuration parameters can indicate multiple coreset indices / identifiers / indicators (e.g., provided by the higher-level parameter ControlResourceSetId) for multiple coresets. In the example, each coreset in the multiple coresets can be identified / indicated by a corresponding coreset index among the multiple coreset indices. In the example, the first coreset in the multiple coresets can be identified by the first coreset index among the multiple coreset indices. The second coreset in the multiple coresets can be identified by the second coreset index among the multiple coreset indices.

[0357] In the example, one or more configuration parameters can indicate one or more coreset pool indices for multiple coresets (e.g., provided by the higher-level parameter `CoresetPoolIndex`). In the example, each coreset in the multiple coresets can include a corresponding coreset pool index among one or more coreset pool indices (e.g., 0, 1) (or configured / indicated by one or more configuration parameters). One or more configuration parameters can indicate a corresponding coreset pool index among one or more coreset pool indices for each coreset in the multiple coresets. For example, one or more configuration parameters can indicate a first coreset pool index (`CoresetPoolIndex = 0`) for the first coreset in the multiple coresets. One or more configuration parameters can indicate a second coreset pool index (`CoresetPoolIndex = 1`) for the second coreset in the multiple coresets. One or more coreset pool indices can include a first coreset pool index and a second coreset pool index.

[0358] In the example, one or more configuration parameters may not indicate the coreset pool index for a coreset across multiple coresets. The higher-level parameter `CoresetPoolIndex` may not be present in the coreset's configuration parameters. The wireless device may determine the first coreset pool index (CoresetPoolIndex = 0) as the value (or default value) of the coreset pool index for the coreset or the coreset pool index used for the coreset. For example, based on one or more configuration parameters not indicating the coreset pool index for a coreset, the wireless device may determine the first coreset pool index as the value (or default value) of the coreset pool index for the coreset or the coreset pool index used for the coreset. For example, based on one or more configuration parameters not indicating the coreset pool index for a coreset, the first coreset pool index (CoresetPoolIndex = 0) can be the coreset pool index for the coreset.

[0359] In the example, a first coreset pool (e.g., Coreset pool 0) may include one or more first coresets having a coreset pool index equal to the first coreset pool index (e.g., CoresetPoolIndex = 0). One or more configuration parameters may indicate the first coreset pool index used for each coreset in one or more first coresets within the first coreset pool. Multiple coresets may include one or more first coresets.

[0360] In the example, a second coreset pool (e.g., Coreset pool 1) may include one or more second coresets having a coreset pool index equal to the second coreset pool index (e.g., CoresetPoolIndex = 1). One or more configuration parameters may indicate the second coreset pool index used for each coreset in one or more second coresets within the second coreset pool. Multiple coresets may include one or more second coresets.

[0361] In the example, one or more configuration parameters may not indicate the coreset pool index for a coreset across multiple coresets. Based on one or more configuration parameters that do not indicate the coreset pool index for a coreset, the wireless device can determine a default value for the coreset pool index of the coreset. In the example, the default value may be equal to zero (CoresetPoolIndex = 0). In the example, the default value may be equal to the first coreset pool index (e.g., zero). The first coreset pool may include the coreset based on one or more configuration parameters not indicating the coreset pool index for the coreset. The first coreset pool may include the coreset based on the default value of the coreset pool index of the coreset / the coreset pool index used for the coreset being equal to the first coreset pool index.

[0362] In the example, the first coreset pool index of the first coreset and the second coreset pool index of the second coreset can be the same. For example, one or more configuration parameters can indicate the same coreset pool index for the first and second coresets. Multiple coresets can include the first coreset and the second coreset. One or more coreset pool indices can include the first coreset pool index and the second coreset pool index. Based on the fact that the first coreset pool index of the first coreset and the second coreset pool index of the second coreset are the same, the wireless device can group the first coreset and the second coreset into the same coreset pool (e.g., CoresetPoolIndex = 0 or CoresetPoolIndex = 1). Based on the fact that the first coreset pool index of the first coreset and the second coreset pool index of the second coreset are the same, the first coreset pool including the first coreset and the second coreset pool including the second coreset can be the same.

[0363] In the example, the first coreset pool index of the first coreset and the second coreset pool index of the second coreset can be different. Multiple coresets can include a first coreset and a second coreset. One or more coreset pool indices can include a first coreset pool index and a second coreset pool index. Based on the difference between the first coreset pool index of the first coreset and the second coreset pool index of the second coreset, the wireless device can group the first coreset and the second coreset into different coreset pools. In the example, the wireless device can group the first coreset into the first coreset pool (e.g., CoresetPoolIndex = 0). Based on the difference between the first coreset pool index and the second coreset pool index, the wireless device can group the second coreset into a second coreset pool different from the first coreset pool (e.g., CoresetPoolIndex = 1). Based on the difference between the first coreset pool index of the first coreset and the second coreset pool index of the second coreset, the first coreset pool and the second coreset pool can be different.

[0364] In the example, one or more configuration parameters may indicate at least two coreset pool indices (e.g., 0 and 1) for the higher-level parameter CORESETPoolIndex. One or more configuration parameters may include a higher-level parameter CORESETPoolIndex that has (or is set to) at least two coreset pool indices. In the example, at least two coreset pool indices may include one or more first coresets among a plurality of coresets / a first coreset pool index for one or more first coresets among a plurality of coresets (e.g., 0). At least two coreset pool indices may include one or more second coresets among a plurality of coresets / a second coreset pool index for one or more second coresets among a plurality of coresets that is different from the first coreset pool index (e.g., 1). One or more first coresets may include one or more third coresets among a plurality of coresets without a value for the higher-level parameter CORESETPoolIndex. One or more configuration parameters may not include a higher-level parameter CORESETPoolIndex for one or more third coresets.

[0365] In one example, a cell may include multiple Transmit and Receive Points (TRPs). Multiple TRPs can serve the cell (or can serve radio devices within / via the cell / serve radio devices in the cell). Multiple TRPs may include a first TRP and a second TRP.

[0366] The first TRP may transmit downlink signals / transmissions (e.g., PDSCH, PDCCH, DCI) via the first coreset pool. Transmitting downlink signals / transmissions (e.g., PDCCH, DCI) via the first coreset pool may include the first TRP transmitting downlink signals / transmissions via a first coreset having (e.g., configured with or associated with) a first coreset pool index. The first TRP may not transmit downlink signals / transmissions (e.g., PDSCH, PDCCH, DCI) via the second coreset pool. Not transmitting downlink signals / transmissions (e.g., PDSCH, PDCCH, DCI) via the second coreset pool may include the first TRP not transmitting downlink signals / transmissions via a second coreset having (e.g., configured with or associated with) a second coreset pool index.

[0367] The second TRP may transmit downlink signals / transmissions (e.g., PDSCH, PDCCH, DCI) via the second coreset pool. Transmitting downlink signals / transmissions (e.g., PDCCH, DCI) via the second coreset pool can include the second TRP transmitting downlink signals / transmissions via a second coreset that has (e.g., is configured with or associated with) a second coreset pool index. The second TRP may also transmit downlink signals / transmissions (e.g., PDCCH, DCI) without transmitting them via the first coreset pool. Transmitting downlink signals / transmissions (e.g., PDCCH, DCI) without transmitting them via the first coreset pool can include the second TRP not transmitting downlink signals / transmissions via a first coreset that has (e.g., is configured with or associated with) a first coreset pool index.

[0368] In the example, one or more configuration parameters can indicate multiple uplink resources (e.g., PUCCH-Resource, SRS-Resource, etc.). One or more configuration parameters can indicate multiple uplink resources for the (active) uplink BWP of the cell. The (active) uplink BWP can include multiple uplink resources. The (active) uplink BWP of the cell's uplink carrier (e.g., NUL, SUL) can include multiple uplink resources.

[0369] Multiple uplink resources may include / are, for example, multiple PUCCH resources. Multiple uplink resources may include / are, for example, multiple SRS resources. Multiple uplink resources may include / are, for example, multiple PUSCH resources.

[0370] One or more configuration parameters can indicate one or more uplink resource groups / sets (e.g., PUCCH-ResourceGroup, SRS-ResourceSet). One or more uplink resource groups / sets can include multiple uplink resources. Each uplink resource group / set within one or more uplink resource groups / sets can include a corresponding uplink resource from among multiple uplink resources. For example, a first uplink resource group / set within one or more uplink resource groups / sets can include one or more first uplink resources from among multiple uplink resources. A second uplink resource group / set within one or more uplink resource groups / sets can include one or more second uplink resources from among multiple uplink resources. In the example, the first and second uplink resource groups / sets may not share / include common / shared / identical uplink resources from among multiple uplink resources. A first uplink resource in the first uplink resource group / set (or belonging to the first uplink resource group / set) may not be in the second uplink resource group / set (or belong to the second uplink resource group / set).

[0371] In the example, one or more configuration parameters can indicate multiple uplink resource indices / identifiers / indicators for multiple uplink resources (e.g., provided by higher-layer parameters PUCCH-ResourceId, SRS-ResourceId). In the example, each of the multiple uplink resources can be identified / indicated by a corresponding uplink resource index among the multiple uplink resource indices. In the example, the first uplink resource among the multiple uplink resources can be identified by the first uplink resource index among the multiple uplink resource indices. The second uplink resource among the multiple uplink resources can be identified by the second uplink resource index among the multiple uplink resource indices.

[0372] In the example, one or more configuration parameters may indicate one or more uplink resource group / set indices / identifiers / indicators (e.g., provided by higher-level parameters PUCCH-ResourceGroupId, SRS-ResourceSetId) for one or more uplink resource groups / sets. In the example, each uplink resource group / set in one or more uplink resource groups / sets may be identified / indicated by a corresponding uplink resource group / set index in one or more uplink resource group / set indices. In the example, a first uplink resource group / set in one or more uplink resource groups / sets may be identified by a first uplink resource group / set index in one or more uplink resource group / set indices. A second uplink resource group / set in one or more uplink resource groups / sets may be identified by a second uplink resource group / set index in one or more uplink resource group / set indices.

[0373] In the example, one or more configuration parameters can indicate one or more coreset pool indices (e.g., provided by the higher-level parameter CoresetPoolIndex) for multiple uplink resources. In the example, each of the multiple uplink resources can include (or be configured / indicated by one or more configuration parameters) a corresponding coreset pool index among one or more coreset pool indices (e.g., 0, 1). One or more configuration parameters can indicate a corresponding coreset pool index among one or more coreset pool indices for each of the multiple uplink resources. For example, one or more configuration parameters can indicate a first coreset pool index (CoresetPoolIndex = 0) for a first uplink resource among the multiple uplink resources. One or more configuration parameters can indicate a second coreset pool index (CoresetPoolIndex = 1) for a second uplink resource among the multiple uplink resources. One or more coreset pool indices can include a first coreset pool index and a second coreset pool index.

[0374] In the example, one or more configuration parameters may not indicate the coreset pool index for uplink resources across multiple uplink resources. The higher-level parameter `CoresetPoolIndex` may not be present in the configuration parameters for the uplink resource. The wireless device may determine the first coreset pool index (CoresetPoolIndex = 0) as the value (or default value) of the coreset pool index for the uplink resource / the coreset pool index used for the uplink resource. For example, based on one or more configuration parameters not indicating the coreset pool index for the uplink resource, the wireless device may determine the first coreset pool index as the value (or default value) of the coreset pool index for the uplink resource / the coreset pool index used for the uplink resource. For example, based on one or more configuration parameters not indicating the coreset pool index for the uplink resource, the first coreset pool index (CoresetPoolIndex = 0) may be the coreset pool index for the uplink resource.

[0375] In the example, one or more configuration parameters may indicate at least two coreset pool indices (e.g., 0 and 1) for the higher-level parameter CORESETPoolIndex. One or more configuration parameters may include a higher-level parameter CORESETPoolIndex that has (or is set to) at least two coreset pool indices. In the example, at least two coreset pool indices may include a first coreset pool index (e.g., 0) for one or more first uplink resources among a plurality of uplink resources. At least two coreset pool indices may include a second coreset pool index (e.g., 1) for one or more second uplink resources among a plurality of uplink resources, different from the first coreset pool index. One or more first uplink resources may include one or more third uplink resources among a plurality of uplink resources without a value for the higher-level parameter CORESETPoolIndex. One or more configuration parameters may not include a higher-level parameter CORESETPoolIndex for one or more third uplink resources.

[0376] In one example, a cell may include multiple Transmit and Receive Points (TRPs). Multiple TRPs can serve the cell (or can serve radio devices within / via the cell / serve radio devices in the cell). Multiple TRPs may include a first TRP and a second TRP.

[0377] The first TRP may receive uplink signals / transmissions (e.g., PUSCH, PUCCH, SRS, UCI, PRACH) via a first uplink resource among multiple uplink resources that has (e.g., is configured with or associated with) a first coreset pool index. The first TRP may also receive uplink signals / transmissions (e.g., PUSCH, PUCCH, SRS, UCI, PRACH) without via a second uplink resource among multiple uplink resources that has (e.g., is configured with or associated with) a second coreset pool index.

[0378] The second TRP may receive uplink signals / transmissions (e.g., PUSCH, PUCCH, SRS, UCI, PRACH) via a second uplink resource among multiple uplink resources that has (e.g., is configured with or associated with) a second coreset pool index. The second TRP may also receive uplink signals / transmissions (e.g., PUSCH, PUCCH, SRS, UCI, PRACH) without via a first uplink resource among multiple uplink resources that has (e.g., is configured with or associated with) a first coreset pool index.

[0379] In the example, one or more configuration parameters can indicate one or more uplink resource indices (e.g., provided by the higher-level parameter CoresetPoolIndex) for one or more uplink resource groups / sets. In the example, each uplink resource group / set within one or more uplink resource groups / sets can include (or be configured / indicated by one or more configuration parameters) a corresponding coreset pool index among one or more coreset pool indices (e.g., 0, 1). One or more configuration parameters can indicate a corresponding coreset pool index among one or more coreset pool indices for each uplink resource group / set within one or more uplink resource groups / sets. For example, one or more configuration parameters can indicate a first coreset pool index (CoresetPoolIndex = 0) for a first uplink resource group / set within one or more uplink resource groups / sets. One or more configuration parameters can indicate a second coreset pool index (CoresetPoolIndex = 1) for a second uplink resource group / set within one or more uplink resource groups / sets. One or more coreset pool indices can include a first coreset pool index and a second coreset pool index.

[0380] In the example, one or more configuration parameters may not indicate the coreset pool index for one or more uplink resource groups / sets. The higher-level parameter `CoresetPoolIndex` may not be in the configuration parameters for the uplink resource group / set. The wireless device may determine the value (or default value) of the coreset pool index for the uplink resource group / set / set as the first coreset pool index (CoresetPoolIndex = 0). For example, based on one or more configuration parameters not indicating the coreset pool index for the uplink resource group / set, the wireless device may determine the value (or default value) of the coreset pool index for the uplink resource group / set / set as the first coreset pool index. For example, based on one or more configuration parameters not indicating the coreset pool index for the uplink resource group / set, the first coreset pool index (CoresetPoolIndex = 0) may be the coreset pool index for the uplink resource group / set.

[0381] In the example, one or more configuration parameters may indicate at least two coreset pool indices (e.g., 0 and 1) for the higher-level parameter CORESETPoolIndex. One or more configuration parameters may include a higher-level parameter CORESETPoolIndex that has (or is set to) at least two coreset pool indices. In the example, at least two coreset pool indices may include a first coreset pool index (e.g., 0) for one or more first uplink resource groups / sets within one or more uplink resource groups / sets. At least two coreset pool indices may include a second coreset pool index (e.g., 1) for one or more second uplink resource groups / sets within one or more uplink resource groups / sets, different from the first coreset pool index. One or more first uplink resource groups / sets may include one or more third uplink resource groups / sets within one or more uplink resource groups / sets without a value for the higher-level parameter CORESETPoolIndex. One or more configuration parameters may exclude the higher-level parameter CORESETPoolIndex used for one or more third uplink resource groups / sets.

[0382] In one example, a cell may include multiple Transmit and Receive Points (TRPs). Multiple TRPs can serve the cell (or can serve radio devices within / via the cell / serve radio devices in the cell). Multiple TRPs may include a first TRP and a second TRP.

[0383] The first TRP may receive uplink signals / transmissions (e.g., PUSCH, PUCCH, SRS, UCI, PRACH) via one or more uplink resource groups / sets having (e.g., configured with or associated with) a first coreset pool index. The first TRP may also receive uplink signals / transmissions (e.g., PUSCH, PUCCH, SRS, UCI, PRACH) without via one or more uplink resource groups / sets having (e.g., configured with or associated with) a second coreset pool index.

[0384] The second TRP may receive uplink signals / transmissions (e.g., PUSCH, PUCCH, SRS, UCI, PRACH) via one or more uplink resource groups / sets that have (e.g., configured with or associated with) a second coreset pool index. The second TRP may also receive uplink signals / transmissions (e.g., PUSCH, PUCCH, SRS, UCI, PRACH) without via one or more uplink resource groups / sets that have (e.g., configured with or associated with) a first coreset pool index.

[0385] Wireless devices can transmit uplink signals / transmissions (e.g., PUSCH / PUCCH / SRS transmissions) via uplink resources. Multiple uplink resources can be included. One or more uplink resource groups / sets can include uplink resources.

[0386] Wireless devices can receive downlink control information (DCI) from a coreset of multiple coresets, which schedules / triggers / indicates the transmission of uplink signals / transmissions. DCI can schedule / trigger / indicate the transmission of uplink signals / transmissions via uplink resources. DCI can indicate uplink resources. DCI may include fields indicating uplink resources.

[0387] For example, uplink signaling / transmissions can be PUSCH transmissions (e.g., transport blocks). Uplink resources can be PUCCH resources. DCI can schedule PUSCH transmissions.

[0388] For example, uplink signaling / transmission can be a PUCCH transmission (e.g., HARQ-ACK feedback). Uplink resources can be PUCCH resources. DCI can schedule the reception of transport blocks (or PDSCH reception). Uplink signaling / transmission can be HARQ-ACK feedback of transport blocks.

[0389] For example, uplink signaling / transmission can be SRS. Uplink resources can be SRS resources. DCI can schedule SRS transmissions. SRS can be, for example, aperiodic SRS.

[0390] The coreset that a wireless device receives DCI from can be associated with a coreset pool index. One or more coreset pool indices can be included. For example, one or more configuration parameters can indicate a coreset pool index for a coreset. For example, one or more configuration parameters can not indicate a coreset pool index for a coreset (CoresetPoolIndex = 0 or CoresetPoolIndex = 1). For example, if one or more configuration parameters do not indicate a coreset pool index for a coreset, the value (or default value) of the coreset pool index can be equal to the first coreset pool index (CoresetPoolIndex = 0).

[0391] Uplink resources can be associated with a coreset pool index. For example, an uplink resource can be associated with a coreset pool index, based on a DCI that schedules / triggers / indicates uplink signaling / transmissions via a coreset associated with the coreset pool index.

[0392] An uplink resource group / set, including uplink resources, can be associated with a coreset pool index. For example, an uplink resource group / set can be associated with a coreset pool index to receive, schedule / trigger / indicate, uplink signaling / transmissions via uplink resources within the uplink resource group / set (belonging to the uplink resource group / set). An uplink resource group / set can include one or more uplink resources having uplink resources. For example, based on an uplink resource group / set including one or more uplink resources being associated with a coreset pool index, one or more uplink resources can be associated with a coreset pool index. For example, based on an uplink resource group / set being associated with a coreset pool index, each of the one or more uplink resources can be associated with a coreset pool index.

[0393] Uplink semaphores / transmissions can be associated with a coreset pool index. For example, an uplink semaphore / transmission can be associated with a coreset pool index based on a DCI that schedules / triggers / indicates a transmission for uplink semaphores / transmissions received via a coreset associated with that coreset pool index.

[0394] One or more configuration parameters can indicate at least two SRS resource sets. The at least two SRS resource sets can include a first SRS resource set and a second SRS resource set.

[0395] One or more configuration parameters can include corresponding usage parameters for each of at least two SRS resource sets.

[0396] For example, usage parameters can be set to a codebook. Usage parameters for each of at least two SRS resource sets can be set to a codebook. One or more configuration parameters can, for example, indicate a codebook for each of at least two SRS resource sets. One or more configuration parameters can indicate a codebook (or usage parameters set to a codebook) for a first SRS resource set. One or more configuration parameters can indicate a codebook (or usage parameters set to a codebook) for a second SRS resource set.

[0397] For example, usage parameters can be set to non-codebook. Usage parameters for each of at least two SRS resource sets can be set to non-codebook. One or more configuration parameters can, for example, indicate non-codebook for each of at least two SRS resource sets. One or more configuration parameters can indicate non-codebook (or be set to non-codebook) for a first SRS resource set. One or more configuration parameters can indicate non-codebook (or be set to non-codebook) for a second SRS resource set.

[0398] One or more configuration parameters can indicate at least two SRS resource set indices for at least two SRS resource sets. One or more configuration parameters can indicate the corresponding SRS resource set index in at least two SRS resource set indices for each SRS resource set in at least two SRS resource sets. Each SRS resource set in at least two SRS resource sets can be identified / indicated by the corresponding SRS resource set index in at least two SRS resource set indices. The first SRS resource set in at least two SRS resource sets can be identified / indicated by the first SRS resource set index in at least two SRS resource set indices. The second SRS resource set in at least two SRS resource sets can be identified / indicated by the second SRS resource set index in at least two SRS resource set indices.

[0399] In the example, the first SRS resource set index of the first SRS resource set can be lower than / less than the second SRS resource set index of the second SRS resource set.

[0400] The wireless device can transmit uplink signal / transmission repetitions (e.g., repetitions of transport blocks, repetitions of PUSCH transmissions, repetitions of UCIs, repetitions of PUCCH transmissions, etc.). For example, the wireless device can receive a DCI that schedules / activates the transmission of uplink signal / transmission repetitions. The wireless device can transmit uplink signal / transmission repetitions based on the received DCI. For example, the uplink signal / transmission repetitions can be for a configured uplink license. One or more configuration parameters can indicate the configured uplink license. The configured uplink license can be, for example, a type 1 configured uplink license. The wireless device can transmit uplink signal / transmission repetitions based on receiving one or more configuration parameters indicating the configured uplink license.

[0401] The DCI that schedules / activates repetitive transmissions of uplink signals / transmissions may include an SRS resource set indicator field. The length / size of the SRS resource set indicator field can be 2 bits.

[0402] A wireless device can transmit one or more first repetitions of uplink signals / transmissions based on a first SRS resource set. One or more configuration parameters can indicate the number of first SRS ports (e.g., nrofSRS-Ports) for the first SRS resource. The wireless device can transmit one or more first repetitions of uplink signals / transmissions, for example, based on the number of first SRS ports of the first SRS resource in the first SRS resource set. For example, the wireless device can utilize / use a first transmission precoder determined based on the number of first SRS ports to transmit one or more first repetitions of uplink signals / transmissions. For example, the wireless device can utilize / use a first spatial domain transmission filter / beam determined based on the first SRS resource to transmit one or more first repetitions of uplink signals / transmissions. For example, in response to transmitting one or more first repetitions of uplink signals / transmissions based on the first SRS resource in the first SRS resource set, one or more first repetitions of uplink signals / transmissions can be associated with the first SRS resource set.

[0403] A wireless device can transmit one or more second repetitions of uplink signals / transmissions based on a second SRS resource set. One or more configuration parameters can indicate the number of second SRS ports (e.g., nrofSRS-Ports) for the second SRS resource. The wireless device can transmit one or more second repetitions of uplink signals / transmissions, for example, based on the number of second SRS ports of the second SRS resource in the second SRS resource set. For example, the wireless device can utilize / use a second transmission precoder determined based on the number of second SRS ports to transmit one or more second repetitions of uplink signals / transmissions. For example, the wireless device can utilize / use a second spatial domain transmission filter / beam determined based on the second SRS resource to transmit one or more second repetitions of uplink signals / transmissions. For example, in response to transmitting one or more second repetitions of uplink signals / transmissions based on the second SRS resource in the second SRS resource set, one or more second repetitions of uplink signals / transmissions can be associated with a second SRS resource set.

[0404] In response to the SRS resource set indicator field being equal to or set to a first value (e.g., 10, 11), the wireless device can transmit uplink signals / transmit one or more first repetitions based on a first SRS resource set and transmit uplink signals / transmit one or more second repetitions based on a second SRS resource set.

[0405] The wireless device may transmit uplink signal / transmission repetitions based on a first SRS resource set. The wireless device may also transmit uplink signal / transmission repetitions without using a second SRS resource set. The wireless device may transmit uplink signal / transmission repetitions based on first SRS resources within the first SRS resource set. One or more configuration parameters may indicate the number of first SRS ports (e.g., nrofSRS-Ports) for the first SRS resources. The wireless device may, for example, transmit uplink signal / transmission repetitions based on the number of first SRS ports in the first SRS resource set. For example, the wireless device may utilize / use a first transmission precoder determined based on the number of first SRS ports to transmit uplink signal / transmission repetitions. For example, the wireless device may utilize / use a first spatial domain transmission filter / beam determined based on the first SRS resources to transmit uplink signal / transmission repetitions. For example, in response to transmitting uplink signal / transmission repetitions based on first SRS resources within the first SRS resource set, the uplink signal / transmission repetitions may be associated with the first SRS resource set. Each repetition in an uplink signaling / transmission repetition may be associated with a first SRS resource set. A repetition in an uplink signaling / transmission repetition may not be associated with a second SRS resource set.

[0406] In response to the SRS resource set indicator field being equal to or set to a second value (e.g., 00), the wireless device may transmit uplink signals / transmission repetitions based on the first SRS resource set. In response to the SRS resource set indicator field being equal to or set to a second value (e.g., 00), the wireless device may transmit uplink signals / transmission repetitions without using the second SRS resource set.

[0407] The wireless device may transmit uplink signal / transmission repetitions based on a second SRS resource set. The wireless device may also transmit repetitions of uplink signal / transmissions without using a first SRS resource set. The wireless device may transmit uplink signal / transmission repetitions based on second SRS resources within the second SRS resource set. One or more configuration parameters may indicate the number of second SRS ports (e.g., nrofSRS-Ports) for the second SRS resources. The wireless device may, for example, transmit uplink signal / transmission repetitions based on the number of second SRS ports in the second SRS resource set. For example, the wireless device may utilize / use a second transmission precoder determined based on the number of second SRS ports to transmit uplink signal / transmission repetitions. For example, the wireless device may utilize / use a second spatial domain transmission filter / beam determined based on the second SRS resources to transmit uplink signal / transmission repetitions. For example, in response to transmitting uplink signal / transmission repetitions based on second SRS resources within the second SRS resource set, the uplink signal / transmission repetitions may be associated with the second SRS resource set. Each repetition in an uplink signaling / transmission repetition may be associated with a second SRS resource set. A repetition in an uplink signaling / transmission repetition may not be associated with a first SRS resource set.

[0408] In response to the SRS resource set indicator field being equal to or set to a third value (e.g., 01), the wireless device may transmit uplink signals / transmission repetitions based on the second SRS resource set. In response to the SRS resource set indicator field being equal to or set to a third value (e.g., 01), the wireless device may transmit uplink signals / transmission repetitions without using the first SRS resource set.

[0409] Wireless devices can transmit uplink signals / transmissions (e.g., transport blocks, PUSCH transmissions, UCI, PUCCH transmissions, etc.). For example, a wireless device can receive a DCI that schedules / activates the transmission of an uplink signal / transmission. The wireless device can transmit uplink signals / transmissions based on the received DCI. For example, the uplink signal / transmission may be for a configured uplink license. One or more configuration parameters may indicate the configured uplink license. The configured uplink license may be, for example, a type 1 configured uplink license. The wireless device can transmit uplink signals / transmissions based on receiving one or more configuration parameters indicating the configured uplink license.

[0410] The DCI that schedules / activates uplink signaling / transmissions may include an SRS resource set indicator field. The length / size of the SRS resource set indicator field can be 2 bits.

[0411] A wireless device may transmit a first portion of an uplink signal / transmission (e.g., one or more first data layers / streams) based on a first SRS resource set. The wireless device may transmit the first portion of an uplink signal / transmission based on first SRS resources within the first SRS resource set. One or more configuration parameters may indicate the number of first SRS ports (e.g., nrofSRS-Ports) for the first SRS resources. The wireless device may, for example, transmit the first portion of an uplink signal / transmission based on the number of first SRS ports of the first SRS resources within the first SRS resource set. For example, the wireless device may utilize / use a first transmission precoder determined based on the number of first SRS ports to transmit the first portion of the uplink signal / transmission. For example, the wireless device may utilize / use a first spatial domain transmission filter / beam determined based on the first SRS resources to transmit the first portion of the uplink signal / transmission. For example, in response to transmitting the first portion of an uplink signal / transmission based on the first SRS resources within the first SRS resource set, the first portion of the uplink signal / transmission may be associated with the first SRS resource set.

[0412] A wireless device can transmit a second portion of uplink signals / transmissions (e.g., one or more second data layers / streams) based on a second SRS resource set. The wireless device can transmit the second portion of uplink signals / transmissions based on second SRS resources within the second SRS resource set. One or more configuration parameters can indicate the number of second SRS ports (e.g., nrofSRS-Ports) for the second SRS resources. The wireless device can transmit the second portion of uplink signals / transmissions, for example, based on the number of second SRS ports of the second SRS resources within the second SRS resource set. For example, the wireless device can utilize / use a second transmission precoder determined based on the number of second SRS ports to transmit the second portion of uplink signals / transmissions. For example, the wireless device can utilize / use a second spatial domain transmission filter / beam determined based on the second SRS resources to transmit the second portion of uplink signals / transmissions. For example, in response to transmitting the second portion of uplink signals / transmissions based on second SRS resources within the second SRS resource set, the second portion of the uplink signals / transmissions can be associated with the second SRS resource set.

[0413] In response to the SRS resource set indicator field being equal to or set to a first value (e.g., 10, 11), the wireless device can transmit the first part of the uplink signal / transmission based on the first SRS resource set and transmit the second part of the uplink signal / transmission based on the second SRS resource set.

[0414] Uplink signaling / transmission may include one or more data layers / streams.

[0415] In the example, one or more data layers / streams may include one or more first data layers / streams and one or more second data layers / streams. The one or more first data layers / streams and one or more second data layers / streams may be different. The one or more first data layers / streams and one or more second data layers / streams may not share data layers / streams. For example, one or more first data layers / streams may include data layer / stream 1 and data layer / stream 2. One or more second data layers / streams may include data layer / stream 3 and data layer / stream 4. For example, one or more first data layers / streams may include data layer / stream 1 and data layer / stream 2. One or more second data layers / streams may include data layer / stream 3, data layer / stream 4, and data layer / stream 5.

[0416] In the example, one or more first data layers / streams and one or more second data layers / streams can be the same. For example, in a single-frequency network (SFN), one or more first data layers / streams and one or more second data layers / streams can be the same. One or more configuration parameters can indicate the SFN (e.g., sfn-pusch, sfn-pucch, etc.) for uplink transmissions (e.g., PUSCH / PUCCH / SRS transmissions). One or more first data layers / streams can be one or more data layers / streams of uplink signaling / transmissions. One or more second data layers / streams can be one or more data layers / streams of uplink signaling / transmissions.

[0417] A wireless device can transmit uplink signals / transmissions based on a first SRS resource set. A wireless device can also transmit uplink signals / transmissions based on first SRS resources within a second SRS resource set. One or more configuration parameters can indicate the number of first SRS ports (e.g., nrofSRS-Ports) for the first SRS resources. The wireless device can transmit uplink signals / transmissions, for example, based on the number of first SRS ports in the first SRS resources within the first SRS resource set. For example, the wireless device can utilize / use a first transmission precoder determined based on the number of first SRS ports to transmit uplink signals / transmissions. For example, the wireless device can utilize / use a first spatial domain transmission filter / beam determined based on the first SRS resources to transmit uplink signals / transmissions.

[0418] In response to the SRS resource set indicator field being equal to or set to a second value (e.g., 00), the wireless device can transmit uplink signals / transmissions based on the first SRS resource set.

[0419] The wireless device can transmit uplink signals / transmissions based on a second SRS resource set. One or more configuration parameters can indicate the number of second SRS ports (e.g., nrofSRS-Ports) for the second SRS resources. The wireless device can transmit uplink signals / transmissions, for example, based on the number of second SRS ports of the second SRS resources in the second SRS resource set. For example, the wireless device can utilize / use a second transmission precoder determined based on the number of second SRS ports to transmit uplink signals / transmissions. For example, the wireless device can utilize / use a second spatial domain transmission filter / beam determined based on the second SRS resources to transmit uplink signals / transmissions.

[0420] In response to the SRS resource set indicator field being equal to or set to a third value (e.g., 01), the wireless device can transmit uplink signals / transmissions based on the second SRS resource set.

[0421] One or more configuration parameters can indicate multiple TCI states (e.g., DL- or Joint-TCIState). One or more configuration parameters can include, for example, one or more PDSCH configuration parameters indicating multiple TCI states.

[0422] One or more configuration parameters may include, for example, one or more PDSCH configuration parameters for the cell's downlink BWP. One or more configuration parameters indicate multiple TCI states of the cell's downlink BWP.

[0423] One or more configuration parameters may include, for example, one or more PDSCH configuration parameters for a second downlink BWP of a second cell. One or more configuration parameters indicate multiple TCI states of the second downlink BWP of the second cell. One or more cells may include a second cell. One or more configuration parameters may include, for the downlink BWP of a cell, a reference unified TCI state list parameter (e.g., refUnifiedTCIStateList) indicating the second downlink BWP of the second cell. The reference unified TCI state list parameter may include a BWP index (e.g., BWP-Id) identifying / indicating the second downlink BWP. The reference unified TCI state list parameter may include a cell index (e.g., ServCellIndex) identifying / indicating the second cell.

[0424] One or more configuration parameters may include the unified-TCI-state-type parameter (e.g., unifiedtci-StateType). One or more configuration parameters may include one or more serving cell parameters (e.g., ServingCellConfig) that have the unified-TCI-state-type parameter. The unified-TCI-state-type parameter may indicate the unified TCI state type of the cell.

[0425] For example, the unified-TCI-state-type parameter can be set to "JointULDL". For example, based on one or more configuration parameters including the unified-TCI-state-type parameter set to "JointULDL", the wireless device can use / apply multiple TCI states for both uplink transmission (e.g., PUSCH / PUCCH / SRS transmission) and downlink reception (e.g., PDCCH / PDSCH / CSI-RS reception) of the cell.

[0426] For example, the `unified-TCI-state-type` parameter can be set to "SeparateULDL". For example, based on one or more configuration parameters including the `unified-TCI-state-type` parameter set to "SeparateULDL", the radio device can use / apply multiple TCI states for / to the cell's downlink reception (e.g., PDCCH / PDSCH / CSI-RS reception). For example, based on one or more configuration parameters including the `unified-TCI-state-type` parameter set to "SeparateULDL", the radio device can choose not to use / apply multiple TCI states for / to the cell's uplink transmission (e.g., PUSCH / PUCCH / SRS transmission).

[0427] One or more configuration parameters may indicate a second or more TCI states (e.g., UL-TCIState). One or more configuration parameters may include, for example, one or more uplink BWP configuration parameters indicating a second or more TCI state.

[0428] One or more configuration parameters may include, for example, one or more uplink BWP configuration parameters for the cell's uplink BWP. One or more configuration parameters indicate a second or more TCI states for the cell's uplink BWP.

[0429] One or more configuration parameters may include, for example, one or more uplink BWP configuration parameters for a second uplink BWP of a second cell. One or more configuration parameters indicate a second plurality of TCI states for the second uplink BWP of the second cell. One or more cells may include the second cell. One or more configuration parameters may include, for the uplink BWP of a cell, a reference unified TCI state list parameter (e.g., refUnifiedTCIStateList) indicating the second uplink BWP of the second cell. The reference unified TCI state list parameter may include a BWP index (e.g., BWP-Id) identifying / indicating the second uplink BWP. The reference unified TCI state list parameter may include a cell index (e.g., ServCellIndex) identifying / indicating the second cell.

[0430] For example, based on one or more configuration parameters including the unified-TCI-state-type parameter set to "SeparateULDL", the radio device may use / apply a second or more TCI states for / to the uplink transmission of the cell (e.g., PUSCH / PUCCH / SRS transmission). For example, based on one or more configuration parameters including the unified-TCI-state-type parameter set to "SeparateULDL", the radio device may not use / apply the second or more TCI states for / to the downlink reception of the cell (e.g., PDCCH / PDSCH / CSI-RS reception).

[0431] In the example, for instance, based on one or more configuration parameters indicating multiple TCI states of the cell's downlink BWP, the wireless device can use multiple TCI states for downlink reception via the cell's downlink BWP.

[0432] In the example, for instance, based on one or more configuration parameters indicating multiple TCI states of the cell's downlink BWP, the wireless device can use multiple TCI states for uplink transmission reception via the cell's uplink BWP.

[0433] In the example, for instance, based on the reference unified TCI state list parameters indicating the second downlink BWP of the second cell for the downlink BWP of the cell, the wireless device can use multiple TCI states of the second cell's second downlink BWP for downlink reception via the cell's downlink BWP.

[0434] In the example, for instance, based on the reference unified TCI state list parameters indicating the second downlink BWP of the second cell for the downlink BWP of the cell, the wireless device can receive multiple TCI states using the second downlink BWP of the second cell for uplink transmissions via the uplink BWP of the cell.

[0435] In the example, for instance, a second plurality of TCI states may be used by a radio device for uplink transmission reception via the cell's uplink BWP, based on one or more configuration parameters indicating the second plurality of TCI states of the cell's uplink BWP.

[0436] In the example, for instance, based on the reference unified TCI state list parameters indicating the second uplink BWP of the second cell for the uplink BWP of the second cell, the radio device can receive a second plurality of TCI states using the second uplink BWP of the second cell for uplink transmissions via the uplink BWP of the cell.

[0437] One or more configuration parameters can indicate the Physical Cell Index / Identity / Identifier (PCI) for a cell.

[0438] One or more configuration parameters can indicate one or more PCIs for one or more cells. The one or more PCIs can include the PCI of the cell. One or more configuration parameters can include the higher-layer (or RRC) parameter physCellId indicating one or more PCIs for one or more cells. One or more configuration parameters can indicate the corresponding PCI among one or more PCIs for each of the one or more cells. For example, one or more configuration parameters can indicate the first PCI among one or more PCIs for a first cell in one or more cells. The first PCI can identify the physical cell identity of the first cell. One or more configuration parameters can indicate the second PCI among one or more PCIs for a second cell in one or more cells. The second PCI can identify the physical cell identity of the second cell.

[0439] One or more configuration parameters may indicate a list of PCI sets (e.g., indicated by the RRC parameter additionalPCIList). One or more configuration parameters may include one or more serving cell parameters (e.g., ServingCellConfig) indicating a list of PCI sets.

[0440] A list of PCI sets may include / indicate at least one PCI from one or more PCIs (e.g., additional PCI). Each PCI set in the list of PCI sets may include / indicate a corresponding PCI from at least one PCI. One or more configuration parameters may indicate a corresponding PCI from at least one PCI for each PCI set in the list of PCI sets. At least one PCI may not include the cell's PCI. Each PCI in at least one PCI may be different from the cell's PCI. One or more PCIs may include at least one PCI and the cell's PCI. At least one PCI may indicate / identify at least one cell from one or more cells. Each PCI in at least one PCI may indicate / identify a corresponding cell from at least one cell. For example, a first PCI set in the list of PCI sets may include a first PCI from at least one PCI. The first PCI may indicate / identify a first cell from at least one cell. A second PCI set in the list of PCI sets may include a second PCI from at least one PCI. The second PCI may indicate / identify a second cell from at least one cell. At least one cell may not include the cell. Each cell in at least one cell may be different from the cell. One or more cells may include at least one cell and the cell.

[0441] At least one cell can be, for example, at least one non-serving cell. At least one cell can be, for example, at least one neighboring cell. At least one cell can be, for example, at least one candidate / auxiliary cell.

[0442] The maximum size / length of the list of PCI sets can be equal to a single value (e.g., 7).

[0443] The list of PCI sets may include / indicate at least one additional PCI index (e.g., additionalPCIndex). Each PCI set in the list of PCI sets may include / indicate a corresponding additional PCI index among at least one additional PCI index. One or more configuration parameters may indicate at least one additional PCI index for the list of PCI sets. One or more configuration parameters may indicate a corresponding additional PCI index among at least one additional PCI index for each PCI set in the list of PCI sets. Each PCI set in the list of PCI sets may be identified / indicated by a corresponding additional PCI index among at least one additional PCI index. For example, a first PCI set in the list of PCI sets may be identified / indicated by a first additional PCI index among at least one additional PCI index. A second PCI set in the list of PCI sets may be identified / indicated by a second additional PCI index among at least one additional PCI index.

[0444] One or more configuration parameters may, for example, specify a list of PCI sets for inter-cell beam management. One or more configuration parameters may, for example, specify a list of PCI sets for inter-cell multi-TRP operation / mode.

[0445] For example, the list of PCI sets is [{0,PCI 5},{1,PCI 2},{2,PCI 4},{3,PCI 10},{4,PCI21}]. The PCI of a cell is different from PCI 5, PCI 2, PCI 4, PCI 10, and PCI 21.

[0446] • {0, PCI 5} is the first PCI set in the list of PCI sets. “0” is the first additional PCI index of the first PCI set. PCI 5 is the first PCI indicating / identifying the first cell / the first PCI of the first cell.

[0447] • {1, PCI 2} is the second PCI set in the list of PCI sets. “1” is the second additional PCI index of the second PCI set. PCI 2 is the second PCI indicating / identifying the second cell / the second PCI of the second cell.

[0448] • {2, PCI 4} is the third PCI set in the list of PCI sets. “2” is the third additional PCI index of the third PCI set. PCI 4 is the third PCI indicating / identifying the third cell / the third PCI of the third cell.

[0449] • {3, PCI 10} is the fourth PCI set in the list of PCI sets. “3” is the fourth additional PCI index of the fourth PCI set. PCI 10 is the fourth PCI indicating / identifying the fourth cell / the fourth PCI of the fourth cell.

[0450] • {4, PCI 21} is the fifth PCI set in the list of PCI sets. “4” is the fifth additional PCI index of the fifth PCI set. PCI 21 is the fifth PCI indicating / identifying the fifth cell / the fifth PCI of the fifth cell.

[0451] o At least one additional PCI index includes a first additional PCI index (0), a second additional PCI index (1), a third additional PCI index (2), a fourth additional PCI index (3), and a fifth additional PCI index (4).

[0452] In the example, one or more configuration parameters can indicate at least one additional PCI index for one or more TCI states out of a plurality of TCI states. One or more configuration parameters can indicate a corresponding additional PCI index (e.g., additionalPCI, AdditionalPCIIndex) in at least one additional PCI index for each of the one or more TCI states. For example, one or more configuration parameters can indicate a first additional PCI index (e.g., 0) in at least one additional PCI index for a first TCI state out of one or more TCI states. The first additional PCI index can indicate / identify a first PCI set in a list of PCI sets. One or more configuration parameters can indicate a second additional PCI index (e.g., 1) in at least one additional PCI index for a second TCI state out of one or more TCI states. The second additional PCI index can indicate / identify a second PCI set in a list of PCI sets. One or more configuration parameters can indicate a third additional PCI index (e.g., 2) in at least one additional PCI index for a third TCI state out of one or more TCI states. The third additional PCI index can indicate / identify a third PCI set in a list of PCI sets.

[0453] For example, based on one or more configuration parameters, an additional PCI index is indicated for the TCI state. One or more TCI states can be associated with an additional PCI index in at least one additional PCI index. A TCI state may include / have an additional PCI index. An additional PCI index may indicate / identify a set of PCIs in a list of PCI sets. A PCI set may include / indicate / have a second PCI in at least one PCI. A second PCI may indicate / identify a second cell in at least one cell. For example, based on one or more configuration parameters, an additional PCI index indicating a second PCI (or a second cell) is indicated for the TCI state, and the TCI state can be associated with the second PCI (or the second cell). The second PCI of the second cell may, for example, be different from the PCI of the cell.

[0454] In the example, one or more configuration parameters may not indicate an additional PCI index in at least one additional PCI index for one or more TCI states out of multiple TCI states. The additional PCI index may not be (or may not exist) in the configuration parameters of one or more TCI states. One or more configuration parameters may include configuration parameters for one or more TCI states. One or more TCI states may not be associated with an additional PCI index. One or more TCI states may not include / have an additional PCI index. Each of one or more TCI states may not include / have an additional PCI index. For example, based on one or more configuration parameters not indicating an additional PCI index for one or more TCI states out of multiple TCI states, one or more TCI states may be associated with a cell (or the cell's PCI). For example, based on one or more configuration parameters not indicating an additional PCI index for each of one or more TCI states out of one or more TCI states, one or more TCI states may be associated with a cell (or the cell's PCI). For example, based on one or more configuration parameters not indicating an additional PCI index in at least one additional PCI index for each of one or more TCI states out of one or more TCI states, one or more TCI states may be associated with a cell (or the cell's PCI).

[0455] In the example, one or more configuration parameters can indicate at least one additional PCI index for one or more TCI states in a second plurality of TCI states. One or more configuration parameters can indicate a corresponding additional PCI index (e.g., additionalPCI, AdditionalPCIIndex) in at least one additional PCI index for each TCI state in one or more TCI states. For example, one or more configuration parameters can indicate a first additional PCI index (e.g., 0) in at least one additional PCI index for a first TCI state in one or more TCI states. The first additional PCI index can indicate / identify a first PCI set in a list of PCI sets. One or more configuration parameters can indicate a second additional PCI index (e.g., 1) in at least one additional PCI index for a second TCI state in one or more TCI states. The second additional PCI index can indicate / identify a second PCI set in a list of PCI sets. One or more configuration parameters can indicate a third additional PCI index (e.g., 2) in at least one additional PCI index for a third TCI state in one or more TCI states, etc. The third additional PCI index can indicate / identify a third PCI set in a list of PCI sets.

[0456] For example, based on one or more configuration parameters, an additional PCI index is indicated for the TCI state. One or more TCI states can be associated with an additional PCI index in at least one additional PCI index. A TCI state may include / have an additional PCI index. An additional PCI index may indicate / identify a set of PCIs in a list of PCI sets. A PCI set may include / indicate / have a second PCI in at least one PCI. A second PCI may indicate / identify a second cell in at least one cell. For example, based on one or more configuration parameters, an additional PCI index indicating a second PCI (or a second cell) is indicated for the TCI state, and the TCI state can be associated with the second PCI (or the second cell). The second PCI of the second cell may, for example, be different from the PCI of the cell.

[0457] In the example, one or more configuration parameters may not indicate an additional PCI index in at least one additional PCI index for one or more TCI states in a second plurality of TCI states. The additional PCI index may not be (or may not exist) in the configuration parameters of one or more TCI states. One or more configuration parameters may include configuration parameters for one or more TCI states. One or more TCI states in a second plurality of TCI states may not be associated with an additional PCI index. One or more TCI states may not include / have an additional PCI index. Each of one or more TCI states may not include / have an additional PCI index. For example, based on one or more configuration parameters not indicating an additional PCI index for one or more TCI states in a second plurality of TCI states, one or more TCI states may be associated with a cell (or the cell's PCI). For example, based on one or more configuration parameters not indicating an additional PCI index for each of one or more TCI states in a second plurality of TCI states, one or more TCI states may be associated with a cell (or the cell's PCI). For example, based on one or more configuration parameters not indicating an additional PCI index in at least one additional PCI index for each of one or more TCI states in a second plurality of TCI states, one or more TCI states may be associated with a cell (or the cell's PCI).

[0458] In the example, the wireless device can receive control commands (e.g., MAC-CE, DCI, downlink control commands, unified TCI status activation / deactivation of MAC CE, etc.).

[0459] For example, control commands can instruct the activation of a subset of TCI states from multiple TCI states (e.g., DLorJoint-TCIState).

[0460] For example, control commands can instruct the activation of a subset of TCI states from multiple TCI states (e.g., UL-TCIState).

[0461] A wireless device can map a subset of TCI states to one or more TCI code points. A wireless device can map a corresponding TCI state within a subset of TCI states to a corresponding TCI code point within one or more TCI code points. One or more TCI code points can indicate a subset of TCI states. Each TCI code point within one or more TCI code points can indicate a corresponding TCI state within a subset of TCI states. Each TCI code point within one or more TCI code points can indicate / include one or more TCI code points. For example, a subset of TCI states can be / include TCI states 1, 5, 8, 23, 34, and 48. One or more TCI code points can be / include a first TCI code point, a second TCI code point, a third TCI code point, and a fourth TCI code point. The first TCI code point can include / indicate TCI state 5. The second TCI code point can include / indicate TCI states 8 and 48. The third TCI code point can include / indicate TCI states 1 and 23. The fourth TCI code point may include / indicate TCI state 34.

[0462] Wireless devices can receive DCI. DCI may include a TCI field. The TCI field may indicate one or more TCI code points. The value of the TCI field may indicate (or be equal to) a TCI code point.

[0463] A TCI code point may include / indicate at least two TCI states. A subset of TCI states may include at least two TCI states from a TCI code point. The at least two TCI states may include a first TCI state and a second TCI state.

[0464] The first TCI state may include / indicate a first reference signal (e.g., CSI-RS, SSB / PBCH block, DM-RS, SRS, etc.). The first TCI state may include / indicate a first quasi-co-address type (e.g., QCL Type A, QCL Type B, QCL Type C, QCL Type D).

[0465] In the example, the first TCI state can be associated with the cell's PCI. The first TCI may not include / have an additional PCI index from at least one additional PCI index. The additional PCI index may not be in the configuration parameters of the first TCI state. One or more configuration parameters may include configuration parameters for the first TCI state. For example, based on the first TCI not including / having an additional PCI index from at least one additional PCI index, the first TCI state can be associated with the cell's PCI. In the example, the first reference signal can be quasi-co-located with the first SS / PBCH block. The first SS / PBCH block can be associated with the cell. The first SS / PBCH block can be associated with the cell's PCI. One or more configuration parameters can indicate the first SS / PBCH block for the cell.

[0466] The second TCI state may include / indicate a second reference signal (e.g., CSI-RS, SSB / PBCH block, DM-RS, SRS, etc.). The second TCI state may include / indicate a second quasi-co-address type (e.g., QCL Type A, QCL Type B, QCL Type C, QCL Type D).

[0467] In the example, the second TCI state can be associated with the second PCI of the second cell. At least one of one or more cells can include the second cell. At least one PCI in the list of PCI sets (or indicated by the list of PCI sets) can include the second PCI. The second PCI can indicate / identify the second cell. The second TCI can include / have an additional PCI index in at least one additional PCI index. One or more configuration parameters can indicate an additional PCI index for the second TCI. The additional PCI index can indicate a PCI set in the list of PCI sets. The PCI set can include / indicate the second PCI of the second cell. For example, based on the second TCI indicating the second PCI of the second cell including / having an additional PCI index, the second TCI state can be associated with the second PCI of the second cell. For example, based on one or more configuration parameters indicating an additional PCI index indicating the second PCI of the second cell for the second TCI, the second TCI state can be associated with the second PCI of the second cell. In the example, the second reference signal can be quasi-co-located with the second SS / PBCH block. The second SS / PBCH block can be associated with the second cell. The second SS / PBCH block can be associated with the second PCI of the second cell. One or more configuration parameters can indicate the second SS / PBCH block for the second cell.

[0468] One or more configuration parameters can indicate a first TCI state index (e.g., tci-StateId) for a first TCI state. One or more configuration parameters can indicate a second TCI state index for a second TCI state. In the example, the first TCI state index can be lower than / less than the second TCI state index.

[0469] A control command indicating the activation of a subset of TCI states may include multiple fields. The first field among these fields may indicate a first TCI state. For example, the first field may include a first TCI state index indicating / identifying the first TCI state. The first field may appear in / be located in (or be positioned within) the first octet of the control command. A second field among these fields may indicate a second TCI state. For example, the second field may include a second TCI state index indicating / identifying the second TCI state. The second field may appear in / be located in (or be positioned within) the second octet of the control command. The first octet may be lower than / less than the second octet. For example, the first octet may be Octet 5, and the second octet may be Octet 6. For example, the first octet may be Octet 1, and the second octet may be Octet 2. For example, the first octet may be Octet 8, and the second octet may be Octet 10.

[0470] Control commands can indicate a list / set / vector of at least two TCI states within a TCI code point, map a list / set / vector of at least two TCI states to a TCI code point, or activate a list / set / vector of at least two TCI states for a TCI code point. Control commands can indicate the mapping / association / activation of a list / set / vector of at least two TCI states to / for a TCI code point. The at least two TCI states can include a first TCI state and a second TCI state. The first TCI state can be the first to appear in the list / set / vector of at least two TCI states. The first TCI state can be the first / starting / earliest / initial TCI state in the list / set / vector of at least two TCI states. The second TCI state can be the second to appear in the list / set / vector of at least two TCI states. The second TCI state can be the last / latest / end TCI state in the list / set / vector of at least two TCI states.

[0471] The wireless device can transmit the first uplink signal / transmission (e.g., PUSCH / PUCCH / SRS transmission, transport block, UCI, etc.) based on the first TCI state.

[0472] The wireless device may, for example, utilize / use a first spatial domain transmit / transfer filter / beam determined based on a first TCI state to transmit a first uplink signal / transmission. The wireless device may determine a first spatial domain transmission filter / beam based on a first reference signal indicated by the first TCI state.

[0473] The first spatial domain transmit / transmit filter / beam may, for example, be the same as (or substantially the same as) the spatial domain receive / receive filter / beam used to receive the first reference signal, differing by x degrees, where x = 0, 1, 5, 10, etc.

[0474] In the example, at least one DMRS antenna port of the first uplink signal / transmission may be quasi-co-located with a first reference signal indicated by a first TCI state. At least one DMRS antenna port of the first uplink signal / transmission may be quasi-co-located with the first reference signal relative to a first quasi-co-location type (e.g., QCL Type A, QCL Type B, QCL Type C, QCL Type D) indicated by the first TCI state.

[0475] A wireless device may, for example, utilize / use a first transmission power determined based on a first TCI state to transmit a first uplink signal / transmission. The first TCI state may indicate (or include, be mapped to, or be associated with) one or more first power control parameters (e.g., target received power, closed-loop index, path loss compensation factor, α, path loss reference signal, etc.). The wireless device may determine the first transmission power based on one or more first power control parameters indicated by (or included in, associated with, or mapped to) the first TCI state. One or more configuration parameters may indicate one or more first power control parameters for the first TCI state.

[0476] One or more configuration parameters may indicate one or more uplink power control sets (e.g., Uplink-powerControl). One or more configuration parameters may include one or more serving cell parameters (e.g., ServingCellConfig) indicating one or more uplink power control sets. One or more configuration parameters may indicate one or more uplink power control set indices / identifiers / identities for one or more uplink power control sets (e.g., Uplink-powerControlId). One or more configuration parameters may indicate a corresponding uplink power control set index in one or more uplink power control set indices / identifiers / identities for each uplink power control set in one or more uplink power control sets. For example, one or more uplink power control sets may include a first uplink power control set and a second uplink power control set. The first uplink power control set may be indicated / identified by a first uplink power control set index in one or more uplink power control set indices / identifiers / identities. The second uplink power control set may be indicated / identified by a second uplink power control set index in one or more uplink power control set indices / identifiers / identities.

[0477] For example, one or more configuration parameters may indicate a first uplink power control set index (e.g., Uplink-powerControlId) in one or more uplink power control set indices / identifiers / identities for a first TCI state. The first TCI state may include / have a first power control index. The first uplink power control set index may indicate / identify a first uplink power control set in one or more uplink power control sets. The first uplink power control set may include / indicate one or more first power control parameters.

[0478] Wireless devices can transmit second uplink signals / transmissions (e.g., PUSCH / PUCCH / SRS transmissions, transport blocks, UCI, etc.) based on the second TCI state.

[0479] The wireless device may, for example, utilize / use a second spatial domain transmit / transmit filter / beam determined based on a second TCI state to transmit a second uplink signal / transmission. The wireless device may determine a second spatial domain transmit filter / beam based on a second reference signal indicated by the second TCI state.

[0480] The second spatial domain transmit / transmit filter / beam may, for example, be the same as (or substantially the same as) the spatial domain receive / receive filter / beam used to receive the second reference signal, differing by x degrees, where x = 0, 1, 5, 10, etc.

[0481] In the example, at least one DMRS antenna port of the second uplink signal / transmission may be quasi-co-located with a second reference signal indicated by a second TCI state. At least one DMRS antenna port of the second uplink signal / transmission may be quasi-co-located with a second reference signal relative to a second quasi-co-location type (e.g., QCL Type A, QCL Type B, QCL Type C, QCL Type D) indicated by the second TCI state.

[0482] A wireless device may, for example, utilize / use a second transmission power determined based on a second TCI state to transmit a second uplink signal / transmission. The second TCI state may indicate (or include, be mapped to, or be associated with) one or more second power control parameters (e.g., target received power, closed-loop index, path loss compensation factor, α, path loss reference signal, etc.). The wireless device may determine a second transmission power based on one or more second power control parameters indicated by (or included in, associated with, or mapped to) the second TCI state. One or more configuration parameters may indicate one or more second power control parameters for the second TCI state.

[0483] For example, one or more configuration parameters may indicate a second uplink power control set index (e.g., Uplink-powerControlId) in one or more uplink power control set indices / identifiers / identities for a second TCI state. The second TCI state may include / have a second power control index. The second uplink power control set index may indicate / identify a second uplink power control set in one or more uplink power control sets. The second uplink power control set may include / indicate one or more second power control parameters.

[0484] In the example, the first uplink signal / transmission and the second uplink signal / transmission can be different.

[0485] In the example, the first uplink signal / transmission and the second uplink signal / transmission can be different. The first uplink signal / transmission can be a transmission of a first portion of the uplink signal (e.g., a first data layer / stream). The second uplink signal / transmission can be a transmission of a second portion of the uplink signal (e.g., a second data layer / stream).

[0486] In the example, the first uplink signal / transmission and the second uplink signal / transmission can be the same. The first uplink signal / transmission and the second uplink signal / transmission can be repetitions of uplink transmissions (e.g., PUSCH / PUCCH repetition, transport block repetition, etc.). Repetition can be, for example, in the frequency domain (e.g., FDM). Repetition can be, for example, in the time domain (e.g., TDM). Repetition can be, for example, in the spatial domain (e.g., SDM, SFN).

[0487] One or more configuration parameters may include one or more cell group configuration parameters (e.g., provided by MAC-CellGroupConfig). One or more cell group configuration parameters may indicate multiple tags. For example, one or more cell group configuration parameters may indicate multiple tags for one or more cells. One or more configuration parameters may indicate the corresponding tag among multiple tags for each cell in one or more cells. For example, one or more cell group configuration parameters may indicate multiple tags for a subset of cells in one or more cells. One or more configuration parameters may indicate the corresponding tag among multiple tags for each cell in a subset of cells in one or more cells.

[0488] One or more configuration parameters (or one or more cell group configuration parameters) can indicate multiple TAG indices / identifiers / identities (e.g., TAG-Id) for multiple TAGs. One or more configuration parameters (or one or more cell group configuration parameters) can indicate a corresponding TAG index among multiple TAG indices for each of the multiple TAGs. For example, one or more configuration parameters can indicate the first TAG index among multiple TAG indices for the first TAG. The first TAG index can indicate / identify the first TAG. One or more configuration parameters can indicate the second TAG index among multiple TAG indices for the second TAG. The second TAG index can indicate / identify the second TAG.

[0489] For example, in Figure 18 In this context, multiple tags include TAG 0, TAG 1, and TAG 2. One or more cells (or subsets of cells) include Cell 1, Cell 2, Cell 3, Cell 4, and Cell 5. For example, in... Figure 17In this configuration, TAG-ID 0 can indicate / identify TAG 0, TAG-ID 1 can indicate / identify TAG 1, and TAG-ID 2 can indicate / identify TAG 2. One or more configuration parameters indicate TAG 0 (or TAG-ID 0 indicating / identifying TAG 0) for cell 1. One or more configuration parameters indicate TAG 0 and TAG 2 (or TAG-ID 0 indicating / identifying TAG 0 and TAG-ID 2 indicating / identifying TAG 2) for cell 2. One or more configuration parameters indicate TAG 1 (or TAG-ID 1 indicating / identifying TAG 1) for cell 3. One or more configuration parameters indicate TAG 1 (or TAG-ID 1 indicating / identifying TAG 1) for cell 4. One or more configuration parameters indicate TAG 1 and TAG 2 (or TAG-ID 1 indicating / identifying TAG 1 and TAG-ID 2 indicating / identifying TAG 2) for cell 5.

[0490] One or more configuration parameters can indicate at least two of a plurality of tags for a cell. The at least two tags can include a first tag and a second tag.

[0491] One or more configuration parameters may include one or more serving cell configuration parameters for the cell (e.g., provided by ServingCellConfig). One or more serving cell configuration parameters may indicate / include at least two tags for the cell. One or more serving cell configuration parameters may indicate / include a list / set / vector of at least two tag indices that identify / indicate at least two tags. Multiple tag indices may include at least two tag indices. Each tag index in the at least two tag indices may identify / indicate a corresponding tag in the at least two tags. The at least two tag indices may include a first tag index and a second tag index. For example, a first tag index may identify / indicate a first tag in the at least two tags. A second tag index may identify / indicate a second tag in the at least two tags.

[0492] For example, in Figure 18 In this context, the cell can be cell 2. At least two tags are required: TAG 0 and TAG 2. Figure 17 In this context, the list / set / vector of at least two TAG indices for cell 2 is {TAG-ID 0, TAG-ID 2}.

[0493] For example, in Figure 18 In the context, the neighborhood can be neighborhood 5. At least two tags are required: TAG 1 and TAG 2. Figure 17In the context of cell 5, the list / set / vector of at least two TAG indices is {TAG-ID 1, TAG-ID 2}.

[0494] In the example, the first tag index of the first tag in at least two tags can be lower than / less than the second tag index of the second tag in at least two tags. The second tag index of the second tag in at least two tags can be greater than / higher than the first tag index of the first tag in at least two tags.

[0495] For example, in Figure 18 In this context, cell 2 can be a separate cell. At least two tags are TAG 0 and TAG 2. TAG 0 can be indicated / identified by TAG-ID 0. TAG 2 can be indicated / identified by TAG-ID 2. For example, if TAG-ID 0 based on TAG 0 is lower / less than TAG-ID 2 of TAG 2, the first tag among the at least two tags can be TAG 0. Similarly, if TAG-ID 0 based on TAG 0 is lower / less than TAG-ID 2 of TAG 2, the second tag among the at least two tags can be TAG 2. Likewise, if TAG-ID 2 based on TAG 2 is greater / higher than TAG-ID 0 of TAG 0, the second tag among the at least two tags can be TAG 2.

[0496] For example, in Figure 18 In this context, the cell can be cell 5. At least two tags are TAG 1 and TAG 2. TAG 1 can be indicated / identified by TAG-ID 1. TAG 2 can be indicated / identified by TAG-ID 2. For example, if TAG-ID 1 based on TAG 1 is lower / less than TAG-ID 2 of TAG 2, the first tag in at least two tags can be TAG 1. Similarly, if TAG-ID 1 based on TAG 1 is lower / less than TAG-ID 2 of TAG 2, the second tag in at least two tags can be TAG 2. Likewise, if TAG-ID 2 based on TAG 2 is greater / higher than TAG-ID 1 of TAG 1, the second tag in at least two tags can be TAG 2.

[0497] In the example, the first TAG index can be the first / starting / earliest TAG index in a list / set / vector of at least two TAG indices. The first TAG index can be the first one to appear in a list / set / vector of at least two TAG indices. The orientation / position of the first TAG index can be the starting / first / earliest orientation / position / entry / element in a list / set / vector of at least two TAG indices.

[0498] In the example, the second TAG index can be the last / newest / end / second start / second earliest / second TAG index in a list / set / vector of at least two TAG indices. The second TAG index can be the second to appear in a list / set / vector of at least two TAG indices. The location / position of the second TAG index can be the last / newest / end / second start / second earliest / second location / position / entry / element in a list / set / vector of at least two TAG indices. In a list / set / vector of at least two TAG indices, the location / position of the first TAG index can precede (or be earlier than or preceding) the location / position of the second TAG index.

[0499] For example, in Figure 18 In this context, the cell can be cell 2. At least two tags are required: TAG 0 and TAG 2. Figure 17In this context, the list / set / vector of at least two TAG indices for cell 2 is {TAG-ID 0, TAG-ID 2}. TAG 0 can be indicated / identified by TAG-ID 0. TAG 2 can be indicated / identified by TAG-ID 2. For example, based on TAG-ID 0 being the first / starting / earliest TAG index in the list / set / vector of at least two TAG indices (or the list / set / vector of TAG-ID 0 and TAG-ID 2), the first TAG index can be TAG-ID 0. Similarly, based on TAG-ID 0 being the first / starting / earliest TAG index in the list / set / vector of at least two TAG indices (or the list / set / vector of TAG-ID 0 and TAG-ID 2), the second TAG index can be TAG-ID 2. For example, if TAG-ID 2 is the last / latest / end / second start / second earliest / second TAG index in a list / set / vector of at least two TAG indices (or a list / set / vector of TAG-ID 0 and TAG-ID 2), the second TAG index can be TAG-ID 2. For example, if TAG-ID 0, which indicates / identifies TAG 0, is the first / start / earliest TAG index in a list / set / vector of at least two TAG indices, the first TAG among the at least two TAGs can be TAG0. For example, if TAG-ID 0, which indicates / identifies TAG 0, first appears in a list / set / vector of at least two TAG indices, the first TAG among the at least two TAGs can be TAG 0. For example, if TAG-ID 0, which indicates / identifies TAG 0, is the first / start / earliest TAG index in a list / set / vector of at least two TAG indices, the second TAG among the at least two TAGs can be TAG 2. For example, TAG-ID 2, based on the indicator / identifier TAG 2, is the last / latest / end / second start / second earliest / second TAG index in a list / set / vector of at least two TAG indices, where the second TAG among at least two TAGs can be TAG 2. For example, TAG-ID 2, based on the indicator / identifier TAG 2, appears second in a list / set / vector of at least two TAG indices, where the second TAG among at least two TAGs can be TAG 2.

[0500] For example, in Figure 18 In the context, the neighborhood can be neighborhood 5. At least two tags are required: TAG 1 and TAG 2. Figure 17In this context, the list / set / vector of at least two TAG indices for cell 5 is {TAG-ID 1, TAG-ID 2}. TAG 1 can be indicated / identified by TAG-ID 1. TAG 2 can be indicated / identified by TAG-ID 2. For example, based on TAG-ID 1 being the first / starting / earliest TAG index in the list / set / vector of at least two TAG indices (or the list / set / vector of TAG-ID 1 and TAG-ID 2), the first TAG index can be TAG-ID 1. Similarly, based on TAG-ID 1 being the first / starting / earliest TAG index in the list / set / vector of at least two TAG indices (or the list / set / vector of TAG-ID 1 and TAG-ID 2), the second TAG index can be TAG-ID 2. For example, if TAG-ID 2 is the last / latest / end / second start / second earliest / second TAG index in a list / set / vector of at least two TAG indices (or a list / set / vector of TAG-ID 1 and TAG-ID 2), the second TAG index can be TAG-ID 2. For example, if TAG-ID 1, which indicates / identifies TAG 1, is the first / starting / earliest TAG index in a list / set / vector of at least two TAG indices, the first TAG among the at least two TAGs can be TAG 1. For example, if TAG-ID 1, which indicates / identifies TAG 1, first appears in a list / set / vector of at least two TAG indices, the first TAG among the at least two TAGs can be TAG 1. For example, if TAG-ID 1, which indicates / identifies TAG 1, is the first / starting / earliest TAG index in a list / set / vector of at least two TAG indices, the second TAG among the at least two TAGs can be TAG 2. For example, if TAG-ID 2, based on the indicator / identifier of TAG 2, is the last / latest / end / second start / second earliest / second TAG index in a list / set / vector of at least two TAG indices, then the second TAG among the at least two TAGs can be TAG 2. For example, if TAG-ID 2, based on the indicator / identifier of TAG 2, appears second in a list / set / vector of at least two TAG indices, then the second TAG among the at least two TAGs can be TAG 2.

[0501] For example, a list / set / vector of at least two TAG indices for a cell could be {TAG-ID 3, TAG-ID 2}. TAG 3 can be indicated / identified by TAG-ID 3. TAG 2 can be indicated / identified by TAG-ID 2. For example, based on TAG-ID 3 being the first / starting / earliest TAG index in a list / set / vector of at least two TAG indices (or a list / set / vector of TAG-ID 3 and TAG-ID 2), the first TAG index could be TAG-ID 3. For example, based on TAG-ID 1 being the first / starting / earliest TAG index in a list / set / vector of at least two TAG indices (or a list / set / vector of TAG-ID 3 and TAG-ID 2), the second TAG index could be TAG-ID 2. For example, if TAG-ID 2 is the last / latest / end / second start / second earliest / second TAG index in a list / set / vector of at least two TAG indices (or a list / set / vector of TAG-ID 3 and TAG-ID 2), the second TAG index can be TAG-ID 2. For example, if TAG-ID 3, which indicates / identifies TAG 3, is the first / start / earliest TAG index in a list / set / vector of at least two TAG indices, the first TAG among the at least two TAGs can be TAG 3. For example, if TAG-ID 3, which indicates / identifies TAG 3, first appears in a list / set / vector of at least two TAG indices, the first TAG among the at least two TAGs can be TAG 3. For example, if TAG-ID 3, which indicates / identifies TAG 3, is the first / start / earliest TAG index in a list / set / vector of at least two TAG indices, the second TAG among the at least two TAGs can be TAG 2. For example, if TAG-ID 2, based on the indicator / identifier of TAG 2, is the last / latest / end / second start / second earliest / second TAG index in a list / set / vector of at least two TAG indices, then the second TAG among the at least two TAGs can be TAG 2. For example, if TAG-ID 2, based on the indicator / identifier of TAG 2, appears second in a list / set / vector of at least two TAG indices, then the second TAG among the at least two TAGs can be TAG 2.

[0502] For example, based on one or more configuration parameters (or one or more serving cell configuration parameters), at least two tags are indicated for a cell, and the cell may belong to (or be associated with) at least two tags.

[0503] One or more configuration parameters can indicate a first tag for one or more first cells. One or more configuration parameters can indicate a first tag for each of the one or more first cells. One or more configuration parameters can indicate one or more first cells for a first tag. One or more cells can include one or more first cells. One or more first cells can include the cells mentioned above. A first tag can include one or more first cells. One or more first cells can belong to (or be associated with) a first tag.

[0504] One or more configuration parameters can indicate a second tag for one or more second cells. One or more configuration parameters can indicate a second tag for each of the one or more second cells. One or more configuration parameters can indicate one or more second cells for a second tag. One or more cells can include one or more second cells. One or more second cells can include the cells mentioned above. A second tag can include one or more second cells. One or more second cells can belong to (or be associated with) a second tag.

[0505] exist Figure 18 In this context, when cell 2 is the first cell, one or more first cells in the first tag (e.g., tag 0) (or belonging to the first tag) are cell 1 and cell 2. One or more second cells in the second tag (e.g., tag 2) (or belonging to the second tag) are cell 2 and cell 5.

[0506] exist Figure 18 In this context, when cell 5 is the first cell, one or more first cells in the first tag (e.g., tag 1) (or belonging to the first tag) are cells 3, 4, and 5. One or more second cells in the second tag (e.g., tag 2) (or belonging to the second tag) are cells 2 and 5.

[0507] The first of at least two tags can be associated with a first timing advance value. The wireless device can determine / calculate / compute the first timing advance value, for example, based on receiving a first timing advance command (e.g., in a random access response, an absolute timing advance command MAC CE, or a timing advance command MAC CE). The wireless device can receive a first control command (e.g., a random access response, an absolute timing advance command MAC CE, or a timing advance command MAC CE) that includes / indicates the first timing advance command.

[0508] For example, a first control command may include a field indicating a first TAG. This field may include a first TAG index indicating / identifying the first TAG. Multiple TAG indices may include a first TAG index. At least two TAG indices may include a first TAG index. For example, in response to a first control command indicating a first TAG to calculate / compute a first timing advance value, the first TAG in at least two TAGs may be associated with the first timing advance value.

[0509] The wireless device ...

Claims

1. A wireless communication device, comprising: one or more processors; and memory storing instructions that, when executed by the one or more processors, cause the wireless device to: receive one or more messages indicating at least two timing advance groups (TAGs) for a cell, wherein each of the at least two TAGs is associated with a respective transmission configuration indicator (TCI) state; receive a downlink control information (DCI) indicating: a semi-persistent scheduling (SPS) deactivation; and an uplink resource for hybrid automatic repeat request-acknowledgement (HARQ-ACK) feedback; in response to a time alignment timer of a TAG of the at least two TAGs associated with a TCI state used to transmit the HARQ-ACK feedback being running, indicate a positive acknowledgement for the SPS deactivation to a physical layer of the wireless device; and transmit, via the cell and based on the TCI state, the HARQ-ACK feedback including the positive acknowledgement. The one or more messages are one or more radio resource control (RRC) messages. The one or more messages further indicate one or more configured downlink assignments for SPS physical downlink shared channel (PDSCH) reception.

4. The wireless communication device of claim 3, further comprising clearing the one or more configured downlink assignments for SPS PDSCH reception based on receiving the DCI indicating the SPS deactivation.

2. The wireless communication device of claim 1, wherein, The HARQ-ACK feedback is transmitted based on a timing advance value associated with the TAG.

3. The wireless communication device of claim 1, wherein, 6. The wireless communication device of claim 1, wherein: the time alignment timer of the TAG is a first time alignment timer of a first TAG of the at least two TAGs; 5. The wireless communication device of claim 1, wherein, and indicating the positive acknowledgement to the physical layer is: in response to the first time alignment timer of the first TAG being running; and regardless of a second time alignment timer of a second TAG of the at least two TAGs being running or not running. The one or more messages indicate: a first control resource set (coreset) pool index for one or more first coresets for the cell; and a second coreset pool index for one or more second coresets for the cell.

7. The wireless communication device of claim 1, wherein, 8. A method of wireless communication, comprising: receiving, by a wireless device, one or more messages indicating at least two timing advance groups (TAGs) for a cell, wherein each of the at least two TAGs is associated with a respective transmission configuration indicator (TCI) state; receiving a downlink control information (DCI) indicating: a semi-persistent scheduling (SPS) deactivation; and an uplink resource for hybrid automatic repeat request-acknowledgement (HARQ-ACK) feedback; in response to a time alignment timer of a TAG of the at least two TAGs associated with a TCI state used to transmit the HARQ-ACK feedback being running, indicating a positive acknowledgement for the SPS deactivation to a physical layer of the wireless device; and transmitting, via the cell and based on the TCI state, the HARQ-ACK feedback including the positive acknowledgement. ​ ​ ​ ​ transmit, via the cell and based on the TCI state, the HARQ-ACK feedback including the positive acknowledgement.

9. The wireless communication method according to claim 8, wherein, The one or more messages are one or more radio resource control (RRC) messages.

10. The wireless communication method according to claim 8, wherein, The one or more messages further indicate one or more configured downlink assignments for SPS physical downlink shared channel (PDSCH) receptions.

11. The method of wireless communication of claim 10, further comprising clearing the one or more configured downlink assignments for SPS PDSCH receptions based on receiving the DCI indicating the SPS deactivation.

12. The wireless communication method according to claim 8, wherein, transmit the HARQ-ACK feedback based on a timing advance value associated with the TAG.

13. The method of wireless communication of claim 8, wherein: the time alignment timer of the TAG is a first time alignment timer of a first TAG of the at least two TAGs; and indicating to the physical layer that the positive acknowledgement is: in response to the first time alignment timer of the first TAG being running; and regardless of a second time alignment timer of a second TAG of the at least two TAGs being running or not running.

14. The wireless communication method of claim 8, wherein, The one or more messages indicate: a first control resource set (coreset) pool index for one or more first coresets of the cell; and a second coreset pool index for one or more second coresets of the cell.

15. A non-transitory computer-readable medium comprising instructions that, when executed by one or more processors of a wireless device, cause the wireless device to: receive one or more messages indicating at least two timing advance groups (TAGs) for a cell, wherein each TAG of the at least two TAGs is associated with a respective transmission configuration indicator (TCI) state; receive a downlink control information (DCI) indicating: Semi-Persistent Scheduling (SPS) deactivation; and an uplink resource for hybrid automatic repeat request acknowledgement (HARQ-ACK) feedback; in response to a time alignment timer of a TAG of the at least two TAGs associated with a TCI state used to transmit the HARQ-ACK feedback being running, indicate to a physical layer of the wireless device a positive acknowledgement for the SPS deactivation; and transmit, via the cell and based on the TCI state, the HARQ-ACK feedback including the positive acknowledgement.

16. The non-transitory computer-readable medium of claim 15, wherein, The one or more messages are one or more radio resource control (RRC) messages.

17. The non-transitory computer-readable medium of claim 15, wherein, The one or more messages further indicate one or more configured downlink assignments for SPS physical downlink shared channel (PDSCH) receptions.

18. The non-transitory computer-readable medium of claim 15, wherein, transmit the HARQ-ACK feedback based on a timing advance value associated with the TAG.

19. The non-transitory computer-readable medium of claim 15, wherein: the time alignment timer of the TAG is a first time alignment timer of a first TAG of the at least two TAGs; and indicating to the physical layer that the positive acknowledgement is: in response to a first time alignment timer of a second TAG of the at least two TAGs being running or not running; and in response to a second time alignment timer of a second TAG of the at least two TAGs being running or not running.

20. The non-transitory computer-readable medium of claim 15, wherein, the one or more messages indicate: a first control resource set, coreset, pool index for one or more first coresets of the cell; and a second coreset pool index for one or more second coresets of the cell. the one or more messages indicate: a first control resource set, coreset, pool index for one or more first coresets of the cell; and a second coreset pool index for one or more second coresets of the cell.

Images