Multiple advance timing groups

Abstract

A wireless device is provided. The wireless device clears the downlink assignment based on the Transmission Configuration Indicator (TCI) state of the uplink resources used for downlink assignment, associated with a TAG in one of the two Timing Advance Groups (TAGs) of the cell that has an expiring time-aligned timer.

Description

Cross-reference to related applications

[0001] This application claims the benefit of U.S. Provisional Application No. 63 / 546,300, filed on October 30, 2023, which is hereby incorporated by reference in its entirety. Attached Figure Description

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

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

[0004] Figure 2A and Figure 2B The protocol stacks for the New Radio (NR) user plane and control plane are shown respectively.

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

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

[0007] Figure 4B This shows an example format of the MAC subheader in a MAC PDU.

[0008] Figures 5A and 5B show the mapping between logical channels, transport channels, and physical channels used for downlink and uplink, respectively.

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

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

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

[0012] Figure 9 An example of bandwidth adaptation using three configured BWPs with NR carriers is shown.

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

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

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

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

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

[0018] Figure 13A , Figure 13B and Figure 13C Four-step contention-based random access procedures, two-step contention-free random access procedures, and another two-step random access procedure are shown respectively.

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

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

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

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

[0023] Figure 17 Aspects of exemplary embodiments according to this disclosure are shown.

[0024] Figure 18 A flowchart is shown according to an example embodiment of the present disclosure.

[0025] Figure 19 A flowchart is shown according to an example embodiment of the present disclosure.

[0026] Figure 20 A flowchart is shown according to an example embodiment of the present disclosure. Detailed Implementation

[0027] In this disclosure, various embodiments are presented as 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 can be made therein without departing from the scope of the invention. Indeed, alternative embodiments will be apparent to those skilled in the art upon reading the specification. The embodiments of the invention should not be limited to any of the exemplary embodiments described. Embodiments of this disclosure will be described with reference to the accompanying drawings. Limitations, features, and / or elements from the disclosed exemplary embodiments can be combined to create further embodiments within the scope of this disclosure. Any figures 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, any actions listed in any flowchart can be reordered or used only optionally in certain embodiments.

[0028] The embodiments 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. Example 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 example embodiments can be applied when one or more criteria are met. Therefore, example embodiments that selectively implement the disclosed protocols can be implemented.

[0029] A base station can communicate with a mixture of wireless devices. The wireless devices and / or base stations can support multiple technologies and / or multiple versions of the same technology. Wireless devices may have certain specific capabilities, depending on the type and / or capability of the wireless device. When this disclosure refers to a base station communicating with multiple wireless devices, this disclosure can refer to a subset of the total number of wireless devices in the coverage area. For example, this disclosure can mean multiple wireless devices having a given capability and in a given sector of a base station using a given LTE or 5G version. Multiple wireless devices in this disclosure can 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.

[0030] In this disclosure, “a (a)” and “an (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 variety of suitable possibilities that may or may not be used in one or more of the 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.

[0031] 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 in one or more different embodiments. The phrase "in response to" (or equivalently "at least in response to") indicates that the phrase following the phrase "in response to" is an example of one of a variety of suitable possibilities that may or may not be used in one or more different embodiments. The phrase "depending on" (or equivalently "at least depending on") indicates that the phrase following the phrase "depending on" is an example of one of a variety of suitable possibilities that may or may not be used in one or more different embodiments. The phrase "adopting / using" (or equivalently "at least adopting / using") indicates that the phrase following the phrase "adopting / using" is an example of one of a variety of suitable possibilities that may or may not be used in one or more different embodiments.

[0032] The term "configured" can refer to the capabilities of a device, whether the device is in an operational or non-operational state. "Configured" can refer to 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.

[0033] 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 an example 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.

[0034] 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.

[0035] 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 the defined interface to other elements. Modules described in this disclosure can be implemented as 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 a software routine written in a computer language configured to be executed by a hardware machine (e.g., C, C++, Fortran, Java, Basic, MATLAB, etc.) or a modeling / simulation program (e.g., Simulink, Stateflow, GNU Octave, or LabVIEW MathScript). 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 typically programmed using hardware description languages ​​(HDLs), such as VHSIC Hardware Description Language (VHDL) or Verilog, which configure connections between internal hardware modules with limited functionality on the programmable device. The aforementioned techniques are often used in combination to achieve the desired result of functional modules.

[0036] 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 be, for example, 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 radio device 106.

[0037] 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 the one or more DNs, authenticate the wireless device 106, and provide charging functionality.

[0038] 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 the two duplexing technologies.

[0039] The term "wireless device" is 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 can be a telephone, smartphone, tablet, computer, laptop computer, sensor, instrument, wearable device, Internet of Things (IoT) device, roadside unit (RSU), 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.

[0040] 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); First 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).

[0041] 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 of the base stations may include three sets of antennas to control three cells (or sectors) respectively. The size of the cells 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.

[0042] 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.

[0043] RAN 104 can be deployed as a homogeneous network with macrocell base stations having 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 "hotspots") 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 femtocell base stations.

[0044] The Third Generation Partnership Project (3GPP) was established in 1998 to facilitate collaboration with... Figure 1A The mobile communication network 100 in the text provides globally standardized specifications 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). 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 can be applied 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.

[0045] Figure 1BAnother example mobile communication network 150 in which embodiments of the present disclosure can 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 manner as the corresponding components described.

[0046] 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).

[0047] 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 interconnecting 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.

[0048] 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.

[0049] 5G-CN 152 may include, for clarity Figure 1B One or more additional network functions not 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 Open Function (NEF), Unified Data Management (UDM), Application Function (AF), and / or Authentication Server Function (AUSF).

[0050] 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, denoted as gNB 160A and gNB 160B (collectively referred to as gNB 160); and / or one or more ng-eNBs, denoted 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.

[0051] 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.

[0052] 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 AMF 158A 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.

[0053] 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.

[0054] 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.

[0055] 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.

[0056] 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.

[0057] 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 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 Serving Data Application Protocol (SDAP) 215 and 225. These four protocols together constitute Layer 2 of the OSI model, or the Data Link Layer.

[0058] 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 the 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 the 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, SDAP 225 at gNB 220 can mark downlink packets with QoS flow indicators (QFIs), which can be observed by SDAP 215 at UE 210 to determine the mapping / demapping between QoS flows and data radio bearers.

[0059] 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.

[0060] although Figure 3 Although not shown, PDCP 214 and 224 can perform mapping / demapping between split radio bearers and RLC channels in a dual connectivity scenario. Dual connectivity is a technique that allows a UE to connect to two cells or more generally to two cell groups: a primary cell group (MCG) and a secondary cell group (SCG). Split bearers are split bearers 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.

[0061] 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 the logical channel, independent of the parameter set 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.

[0062] 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, MACs 212 and 222 can provide logical channels as services to RLCs 213 and 223.

[0063] 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.

[0064] Figure 4A An example downlink data flow is shown that passes through the NR user plane protocol stack. Figure 4AThe diagram shows three IP packets, each with a terabyte (TB), flowing through the NR user plane protocol stack to generate at the gNB 220. n , n+1 and m The downlink data stream. The uplink data stream flowing through the NR user plane protocol stack can be... Figure 4A The downlink data flow described in the text is similar.

[0065] 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 the middle, SDAP 225 will send IP packets n and n+1 Mapped to the first radio bearer 402, and the IP packet... m Mapped to the second radio bearer 404. 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 SDAP 225 is the SDU of the lower protocol layer PDCP 224 and the PDU of SDAP 225.

[0066] 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 Regarding IP packets m (As shown) 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 across MAC PDUs, such as... Figure 4A As shown in the diagram. In LTE, the MAC subheader 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 subheader can be computed before the complete MAC PDU is assembled.

[0067] Figure 4BAn example 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.

[0068] 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 used 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.

[0069] 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.

[0070] Figures 5A and 5B illustrate the mapping between logical channels, transport channels, and physical channels for downlink and uplink, respectively. 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: --Paging Control Channel (PCCH), which carries paging messages for paging UEs whose location is unknown to the network at the cell level; --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 it operates within the cell; --Common Control Channel (CCCH), which is used to carry control messages and random access; --Dedicated Control Channel (DCCH), used to carry control messages to a specific UE / carry control messages from a specific UE to configure the UE; and --Dedicated Service Channel (DTCH), which is used to carry user data to a specific UE or carry user data from a specific UE.

[0071] 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: --Paging Channel (PCH), which is used to carry paging messages originating from PCCH; --Broadcast channel (BCH), which is used to carry MIBs from the BCCH; --Downlink Shared Channel (DL-SCH), which is used to carry downlink data and signaling messages, including SIBs from BCCH; --Uplink Shared Channel (UL-SCH), used to carry uplink data and signaling messages; and --Random Access Channel (RACH), which is used to allow a UE to access the network without any prior scheduling.

[0072] 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 the NR includes, for example: --Physical Broadcast Channel (PBCH), which is used to carry MIBs from the BCH; --Physical Downlink Shared Channel (PDSCH), which is used to carry downlink data and signaling messages from DL-SCH and paging messages from PCH; --Physical downlink control channel (PDCCH), which carries downlink control information (DCI), which may include downlink scheduling commands, uplink scheduling authorizations, and uplink power control commands; --The Physical Uplink Shared Channel (PUSCH) is used to carry uplink data and signaling messages from the UL-SCH, and in some cases carries uplink control information (UCI) as described below. --Physical Uplink Control Channel (PUCCH), which carries a UCI, the UCI including HARQ acknowledgment, Channel Quality Indicator (CQI), Precoding Matrix Indicator (PMI), Rank Indicator (RI), and Scheduling Request (SR); and --Physical Random Access Channel (PRACH), which is used for random access.

[0073] Similar to the physical control channel, the physical layer generates physical signals to support its low-level operations. As shown in Figures 5A and 5B, the physical layer signals defined by the 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.

[0074] Figure 2B An example 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 example 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.

[0075] 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.

[0076] 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 radio bearers and data radio bearers; mobility functions; QoS management functions; UE measurement reporting and control of said reports; 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.

[0077] 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 depicted in the text 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).

[0078] 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 gNB 220 depicted in this disclosure; or any other base station described herein. A base station connected to a UE may have an RRC context for the 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 handover to a cell of 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.

[0079] 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 called cell reselection. The RRC state can be transitioned from RRC Idle 604 to RRC Connection 602 via Connection Establishment Procedure 612, which may involve a random access procedure, as discussed in more detail below.

[0080] 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 connected 602 via connection resumption 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.

[0081] 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).

[0082] 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.

[0083] 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 the RAN notification area assigned to it, the UE can perform a notification area update on the RAN to update its RAN notification area.

[0084] The base station storing the RRC context for the UE, or the UE's last serving base station, may 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.

[0085] 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.

[0086] In NR, physical signals and physical channels (discussed in Figures 5A and 5B) can be mapped onto Orthogonal Frequency Division Multiplexing (OFDM) symbols. OFDM is a multi-carrier communication scheme that uses... F Data is transmitted via orthogonal subcarriers (or tones). Before transmission, the data can be mapped to a series of complex symbols called source symbols (e.g., M-QAM symbols or M-PSK symbols), and is divided into... F A parallel symbol stream. F The parallel symbol streams can be viewed as if they were in the frequency domain and used as input to blocks of Inverse Fast Fourier Transform (IFFT) symbols that transform them to the time domain. An IFFT block can take... FSource symbols (from) F (One source symbol is taken from each of the parallel symbol streams), and each source symbol is used to modulate the signal with... F Corresponding to each orthogonal subcarrier F The amplitude and phase of one of the sinusoidal basis functions. The output of the IFFT block can represent... F The sum of orthogonal subcarriers F Each time-domain sample. F Each time-domain sample can form a single OFDM symbol. After some processing (e.g., the addition of a cyclic prefix) and upconversion, the OFDM symbol provided by the IFFT block can be transmitted over the air interface at the carrier frequency. F The parallel symbol streams can be mixed using an FFT block before being processed by an 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 OFDM symbols can be inversely processed at the receiver using an FFT block to recover the data mapped to the source symbols.

[0087] Figure 7 An example 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.

[0088] The duration of a time slot can depend on the set of parameters used for the OFDM symbols in that time slot. In NR, flexible parameter sets are supported 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.

[0089] 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 (A 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.

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

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

[0092] NR can support wide carrier bandwidths (e.g., up to 400 MHz for a subcarrier spacing of 120 kHz). 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.

[0093] The NR defines a Bandwidth Component (BWP) to support UEs that cannot receive the full carrier bandwidth and to support bandwidth adaptation. In an example, a BWP can be defined by a subset of consecutive Relay Buses (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.

[0094] 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 be linked 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.

[0095] 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 time-domain and frequency-domain locations 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.

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

[0097] One or more BWP indicator fields may 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.

[0098] 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.

[0099] The base station can configure the BWP inactivity timer value for the UE using 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 under the following circumstances: a When the UE detects a DCI indicating an active downlink BWP other than the default downlink BWP for paired spectrum operation; or ( b When the UE detects a DCI (Distributed Indication Code) for unpaired spectrum operation, indicating an active downlink BWP or active uplink BWP other than the default downlink BWP or uplink BWP, the UE can proceed as follows: If the UE does not detect the DCI within a time interval (e.g., 1 ms or 0.5 ms), the UE can advance the BWP inactivity timer towards its expiration (e.g., by incrementing from zero to the BWP inactivity timer value, or decrementing 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.

[0100] In the example, the base station can semi-statically configure the UE with 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).

[0101] 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 BWP inactivity timers, and / or the initiation of random access.

[0102] 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: BWP902 with a bandwidth of 40 MHz and a subcarrier spacing of 15 kHz; BWP904 with a bandwidth of 10 MHz and a subcarrier spacing of 15 kHz; and BWP906 with a bandwidth of 20 MHz and a subcarrier spacing of 60 kHz. BWP902 can be the initial active BWP, and BWP904 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.

[0103] 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.

[0104] 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, with one serving cell per CC. A CC can have three configurations in the frequency domain.

[0105] Figure 10AThree 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 positioned 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 positioned in frequency bands (band A and band B).

[0106] 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.

[0107] 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, reconstruction, 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).

[0108] The configured SCell for the UE can be activated and deactivated based on, for example, traffic and channel conditions. Deactivation of an SCell can mean stopping PDCCH and PDSCH reception on the SCell, and stopping PUSCH, SRS, and CQI transmissions on the SCell. (The remaining text appears to be incomplete and requires further context.) Figure 4BThe 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).

[0109] Downlink control information for a cell (such as scheduling assignment and scheduling grant) can be transmitted on the cell corresponding to the assignment and grant; this is called self-scheduling. A cell's DCI can be transmitted on another cell; this is called 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 aggregation downlink CCs, the PCell's PUCCH may become overloaded. Cells can be divided into multiple PUCCH groups.

[0110] 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 10B In 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 10BIf 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.

[0111] 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 carriers. 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 the first carrier is activated.

[0112] 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 / grant of each serving cell. Transport blocks and their potential HARQ retransmissions can be mapped to the serving cell.

[0113] 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, as shown in Figure 5A). In the uplink, the UE can transmit one or more RS to the base station (e.g., DMRS, PT-RS, and / or SRS, as shown in Figure 5B). PSS and SSS can be transmitted by the base station and used by the UE to synchronize 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.

[0114] 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 in the diagram). 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 periodicity of the burst, 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 factors. 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.

[0115] 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.

[0116] 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 grid. 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 grid. In the example, cell selection / search and / or reselection can be based on the CD-SSB.

[0117] 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.

[0118] 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.

[0119] The UE may assume that one or more SS / PBCH blocks transmitted with 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.

[0120] 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.

[0121] 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.

[0122] CSI-RS can be transmitted by the base station and used by the UE to acquire Channel State Information (CSI). The base station can use 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., estimated downlink channel state) to perform link adaptation.

[0123] A base station can semi-statically configure a 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 be activated and / or deactivated.

[0124] The base station can configure the UE to report CSI measurements. The base station can configure the UE to provide CSI reports periodically, non-periodically, or semi-persistently. For periodic CSI reporting, the UE can be configured with multiple CSI report timings and / or periods. For non-periodic 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.

[0125] 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.

[0126] 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 the one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). The base station can semi-statically configure the UE with 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.

[0127] 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. The set of PRBs can be represented as a Precode Resource Block Group (PRG).

[0128] 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.

[0129] 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 association with one or more parameters (e.g., modulation and coding scheme (MCS)) indicated by the 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. The NR network can support multiple PT-RS densities defined in the time and / or frequency domains. 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.

[0130] 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 of 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.

[0131] 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.

[0132] 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.

[0133] 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 to 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, wherein the one or more 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.

[0134] 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 periodicity; offset of periodic and / or aperiodic SRS resources; number of OFDM symbols in SRS resources; initiation OFDM symbols for SRS resources; SRS bandwidth; frequency hopping bandwidth; cyclic shift; and / or SRS sequence ID.

[0135] 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, a receiver can infer from the channel through which the first symbol on the antenna port is transmitted (e.g., fading gain, multipath delay, etc.). 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. The 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.

[0136] 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 establishing an RRC connection with the base station, the UE can perform the downlink beam measurement procedure.

[0137] Figure 11B An example of a Channel State Information Reference Signal (CSI-RS) mapped in the time and frequency domains is shown. Figure 11B The square shown can represent a resource block (RB) within the cell's bandwidth. The base station can 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 identifier, 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, transmission comb, and 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).

[0138] Figure 11BThe 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-RS 1101) 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.

[0139] CSI-RS, such as Figure 11B Those shown (e.g., CSI-RS 1101, 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) of a configured CSI-RS resource. 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.

[0140] 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 the 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).

[0141] Figure 12A Examples of three downlink beam management procedures are shown: P1, P2, and P3. Procedure P1 can enable UE measurement of the transmission (Tx) beams for a Transport Receiver 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 a Tx beam scan for the beam set (shown as an ellipse rotating counterclockwise in the top rows of P1 and P2, indicated by dashed arrows). Beamforming at the UE can include an Rx beam scan for the beam set (shown as an ellipse 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 an ellipse 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 than that used in procedure P1. This may be referred to as beam refinement. The UE may perform procedure P3 for Rx beam determination by using the same Tx beam at the base station and sweeping the Rx beam at the UE.

[0142] Figure 12BExamples 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 base station Rx beams (shown as ellipses in the top and bottom rows of U1, respectively). Beamforming at the UE may include, for example, a Tx beam scan from a set of beams (shown as an ellipse rotating clockwise in the bottom rows of U1 and U3, indicated by dashed arrows). Beamforming at the base station may include, for example, an Rx beam scan from a set of beams (shown as an ellipse rotating counterclockwise in the top rows of U1 and U2, indicated by dashed arrows). 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 use a smaller beam set than that used in procedure P1, or use a narrower beam than that used in procedure P1, to perform procedure U2. This can be called beam refinement. The UE can execute procedure U3 to adjust its Tx beam when the base station is using a fixed Rx beam.

[0143] The UE can initiate a beam failure recovery (BFR) procedure based on the detection of beam failure. The UE can transmit a BFR request (e.g., preamble, UCI, SR, MAC CE, etc.) based on the initiation of the BFR procedure. The UE can detect beam failure 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.).

[0144] The UE can use one or more reference signals (RS) to measure the quality of the beamp-link, including 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 can 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 can 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.

[0145] The network (e.g., gNB and / or the network's ng-eNB) and / or the UE can initiate a random access procedure. 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 failure recovery requests. The network can initiate random access procedures for handover and / or for establishing time alignment for SCell additions.

[0146] Figure 13A A four-step contention-based random access procedure is illustrated. Before initiating the procedure, the base station may transmit configuration message 1310 to the UE. Figure 13A The procedure shown involves 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).

[0147] Configuration message 1310 may be transmitted, for example, using one or more RRC messages. The one or more RRC messages may indicate one or more Random Access Channel (RACH) parameters to the UE. The one or more RACH parameters may 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 special parameters (e.g., RACH- configDedicatedThe base station may broadcast or multicast the one or more RRC messages to one or more UEs. The one or more RRC messages may be UE-specific (e.g., dedicated RRC messages transmitted to the UE in the RRC_CONNECTED state and / or RRC_INACTIVE state). The UE may determine the time-frequency resources and / or uplink transmission power for transmitting Msg 11311 and / or Msg 3 1313 based on the one or more RACH parameters. Based on the one or more RACH parameters, the UE may determine the receive timing and downlink channel for receiving Msg 2 1312 and Msg 4 1314.

[0148] The one or more RACH parameters provided in configuration message 1310 can indicate one or more physical RACH (PRACH) timings that can be used to transmit Msg 11311. These one or more PRACH timings can be predefined. The one or more RACH parameters can indicate one or more available sets of one or more PRACH timings (e.g., prach- ConfigIndex The one or more RACH parameters may indicate the association between (a) one or more PRACH timings and (b) one or more reference signals. The one or more RACH parameters may indicate the association between (a) one or more preambles and (b) one or more reference signals. The one or more reference signals may be SS / PBCH blocks and / or CSI-RS. For example, the 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.

[0149] 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 Msg 3 1313. For example, the one or more RACH parameters can indicate a reference power for preamble transmission (e.g., target power for reception and / or initial power for 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).

[0150] Msg 1 1311 may include one or more preamble transmissions (e.g., preamble transmission and one or more preamble retransmissions). RRC messages can 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 the 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 an RRC message, the UE can select at least one preamble associated with the one or more reference signals and / or a selected preamble group.

[0151] The UE can determine the preamble based on 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 This can indicate the correlation between the PRACH timing and the one or more reference signals.

[0152] If no response is received after the preamble transmission, the UE can perform a preamble retransmission. The UE can increase the uplink transmission power used for preamble retransmission. The UE can select the initial preamble transmission power based on path loss measurements and / or the target received preamble power configured by the network. The UE can determine the preamble to be retransmitted and can ramp up the uplink transmission power. The UE can receive one or more RACH parameters (e.g., indicating the ramp step size for preamble retransmission) indicating the ramp step size for preamble retransmission. PREAMBLE_POWER_RAMPING_STEP The ramp-up step size can be the amount by which the uplink transmission power used for retransmissions is incrementally increased. If the UE determines that the same reference signal (e.g., SSB and / or CSI-RS) is used as in previous preamble transmissions, the UE can ramp up the uplink transmission power. The UE can 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 of the RACH parameters (e.g., preambleTransMax If the UE determines that the random access procedure was not completed successfully, then the UE can be sure that the random access procedure was not completed successfully.

[0153] 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 timing alignment command that the UE can use to adjust the UE's transmission timing, a scheduling permission 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 The UE can monitor the PDCCH of Msg 21312. The UE can determine when to initiate a time window based on the PRACH timing in which it transmits the preamble. For example, the UE can 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). The one or more symbols can be determined based on a set of parameters. The PDCCH can be in a common search space configured by RRC messages (e.g., a Type 1-PDCCH common search space). The UE can identify the RAR based on a Radio Network Temporary Identifier (RNTI). The RNTI can be used depending on one or more events that initiate a random access procedure. The UE can use a Random Access RNTI (RA-RNTI). The RA-RNTI can be associated with the PRACH timing in which the UE transmits the preamble. For example, the UE can determine the RA-RNTI based on: OFDM symbol index; time slot index; frequency domain index; and / or the UL carrier indicator of the PRACH timing. Examples of RA-RNTIs include: RA-RNTI = 1 + s_id + 14 × t_id + 14 × 80 × f_id + 14 × 80 × 8 × ul_carrier_id, 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).

[0154] The UE may transmit Msg 3 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. A conflict may occur if the multiple UEs interpret the RAR as corresponding to themselves. 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, a UE may include a 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).

[0155] 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 an RRC_IDLE state or is 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 identifier 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.

[0156] The UE can be configured with Supplemental Uplink (SUL) carriers and Normal Uplink (NUL) carriers. Initial access (e.g., random access procedure) 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 during the random access procedure (e.g., Msg 1 1311 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).

[0157] Figure 13B This illustrates a two-step contention-free random access procedure. (Compared to...) Figure 13A Similar to the four-step contention-based random access procedure shown, 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 program 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 a contention-free random access procedure may not include messages such as Msg 3 1313 and / or Msg 4 1314.

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

[0159] 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 search the space indicated by the RRC message (e.g., recoverySearchSpaceIdThe UE can be configured with a separate time window and / or a separate PDCCH. The UE can monitor PDCCH transmissions addressed to the Cell RNTI (C-RNTI) in 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 the response is an indication of confirmation of the SI request.

[0160] Figure 13C Another two-step random access procedure is shown. (Compared to...) 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 program shown includes the transmission of two messages: Msg A1331 and Msg B1332.

[0161] Msg A 1331 can be transmitted by the UE in an 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 Msg 3 1313 is similar to and / or equivalent to that of Msg 3 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 that shown in Msg 3 1313. Figure 13A and Figure 13B The Msg 2 1312 shown (e.g., RAR) and / or Figure 13A The content shown in Msg 41314 is similar to and / or equivalent to the content shown.

[0162] UE can initiate [activities] on licensed spectrum and / or unlicensed spectrum. Figure 13CThe 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. The 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.

[0163] 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.

[0164] 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 advance command; a power control command; uplink grant (e.g., radio resource allocation 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).

[0165] 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.

[0166] Downlink control signaling may include: downlink scheduling assignment; uplink scheduling permission 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.

[0167] 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 modulo-2 addition (or XOR operation) of the identifier value and the CRC parity bits. The identifier can include a 16-bit value of the Radio Network Temporary Identifier (RNTI).

[0168] 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 a paging RNTI (P-RNTI) can indicate paging information and / or system information change notifications. A P-RNTI can be predefined as "FFFE" in hexadecimal. A DCI with CRC parity bits scrambled using a system information RNTI (SI-RNTI) can indicate broadcast transmission of system information. A SI-RNTI can be predefined as "FFFF" in hexadecimal. A DCI with CRC parity bits scrambled using a random access RNTI (RA-RNTI) can indicate a random access response (RAR). A DCI with CRC parity bits scrambled using a 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 a 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: 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), Interruption 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.

[0169] 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 to schedule PUSCH 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 to schedule PUSCH in a cell (e.g., with a larger DCI payload than DCI format 0_0). DCI format 1_0 can be used to schedule PDSCH 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 to schedule PDSCH 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 transport power control (TPC) commands for PUCCH or PUSCH. DCI format 2_3 can be used to transmit TPC command groups 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.

[0170] 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).

[0171] 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 of 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 of the time slot. The fourth CORESET 1404 appears at the seventh symbol of the time slot. CORESETs can have different numbers of resource blocks in the frequency domain.

[0172] 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.

[0173] 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).

[0174] 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, time slot format indication, downlink preemption, etc.).

[0175] 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.

[0176] 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.

[0177] The base station can transmit configuration parameters for multiple PUCCH resource sets to the UE using, for example, RRC messages. 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; and multiple PUCCH resources (e.g., PUCCH resource resources identified by PUCCH resource identifiers). pucch-Resourceid The UE can transmit multiple (e.g., a maximum number) UCI ​​information bits using one of the multiple PUCCH resources in a PUCCH resource set. When multiple PUCCH resource sets are configured, the UE can select one of the multiple PUCCH resource sets (e.g., HARQ-ACK, SR, and / or CSI) based on the total bit length of the UCI information bits. 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 bit length of the UCI information bits is greater than two and less than or equal to the first configured value, the UE can select a second PUCCH resource set with a PUCCH resource set index equal to "1". If the total bit length of the UCI information bits is greater than the first configured value and less than or equal to the second configured value, the UE can select a third PUCCH resource set with a PUCCH resource set index equal to "2". If the total bit length of the UCI information bits is greater than the second configured 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".

[0178] 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).

[0179] Figure 15 An example of a wireless device 1502 communicating with a base station 1504 according to an embodiment of the present 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.

[0180] 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.

[0181] 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. The data can be provided to processing system 1508 via, for example, a 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, information about… Figure 2A , Figure 2B , Figure 3 and Figure 4A The SDAP layer, PDCP layer, RLC layer, and MAC layer are included. Layer 3 may include, for example, the SDAP layer, PDCP layer, RLC layer, and MAC layer. Figure 2B The RRC layer.

[0182] After being processed by processing system 1508, data to be transmitted 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 transmitted 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.

[0183] 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.

[0184] 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.

[0185] 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.

[0186] 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.

[0187] 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. Processing system 1518 in wireless device 1502 may receive power from a power source and / or may 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, a solar cell unit, a fuel cell unit, 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.

[0188] Figure 16AAn example architecture 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 of complex-valued symbols; mapping 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, etc. 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 embodiments.

[0189] Figure 16B An example architecture for modulation and upsampling 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.

[0190] Figure 16C An example 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, etc. These functions are shown as examples, and other mechanisms are contemplated for implementation in various embodiments.

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

[0192] 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 cells). The wireless device can communicate with at least one base station (e.g., two or more base stations in dual connectivity) via these multiple cells. The one or more 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 layer 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.

[0193] A timer can begin running once started and continues running until it stops or expires. If the timer is not running, it can be started, or if it is running, it can be restarted. The timer can be associated with a value (e.g., the 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 the timer may not be updated until the timer stops or expires (e.g., due to BWP switching). The timer can be used to measure time periods / windows of a process. When the specification refers to embodiments and procedures relating 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 the multiple ways of implementing the timer can be used to measure time periods / windows of a process. 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 example embodiments for restarting the measurement of a time window can be provided.

[0194] The wireless device may receive, for example, one or more messages (e.g., RRC messages) from a base station, including one or more configuration parameters of the cell or for the cell.

[0195] One or more configuration parameters can indicate two tags for a cell.

[0196] For example, when the second time alignment timer of the second tag in two tags is running, the first time alignment timer of the first tag in two tags may expire.

[0197] The wireless device can apply the TCI state to the configured downlink assignment. The wireless device can receive the configured downlink assignment based on the TCI state. The wireless device can receive PDSCH reception via the configured downlink assignment based on the TCI state.

[0198] In existing implementations, when a first time alignment timer for a first TAG expires while a second time alignment timer for a second TAG is running, the wireless device can, for example, clear the configured downlink assignment based on the TCI state associated with the first TAG.

[0199] One or more configuration parameters can indicate the uniform TCI state type of a cell. When the uniform TCI state type of a cell is set to "Separate," the TCI state applied to the configured downlink assignment may not be associated with a TAG. When the TCI state is not associated with any TAG in two TAGs, the radio device may be unable to determine whether to clear the configured downlink assignment when the first time alignment timer of the first TAG expires and the second time alignment timer of the second TAG is running. This can lead to wasted resources. For example, when the TCI state is associated with the first TAG and the radio device has not cleared the configured downlink assignment, the base station may not transmit any PDSCH via the configured downlink assignment, and the base station may not reassign the configured downlink assignment (or the resources indicated by the configured downlink assignment) to the second radio device.

[0200] When the cell’s unified TCI status type is set to “separate”, the example implementation enhances the clearing of configured downlink assignments.

[0201] In an example embodiment, when the first time alignment timer for the first TAG expires while the second time alignment timer for the second TAG is running, the radio device can, for example, clear the configured downlink assignment by associating the uplink TCI state of the PUCCH resources applied to the configured downlink assignment with the first TAG. The radio device can then use the PUCCH resources to transmit HARQ-ACK information configured downlink (or received via a configured downlink PDSCH).

[0202] In an example embodiment, when the first time alignment timer of the first TAG expires while the second time alignment timer of the second TAG is running, the wireless device may, for example, instruct the first TAG to clear the configured downlink assignment based on the TAG ID pointer configured by the SPS of the configured downlink assignment.

[0203] In an implementation of the example embodiment, when the first time alignment timer for the first TAG expires while the second time alignment timer for the second TAG is running, the wireless device can determine whether to clear the configured downlink assignment. This can improve resource management efficiency.

[0204] Wireless devices can be configured with higher-level parameters. PDSCH-Config Internal / TCI state configured via the higher-level parameters (e.g., TCI-State A list of TCI states is used to decode PDSCH based on detected PDCCH, which has DCIs designed for use by the radio device and a given cell (e.g., a given serving cell, a given non-serving / candidate / target cell). The number of TCI states in the list may depend on UE capability parameters. maxNumberConfiguredTCI statesPerCC Each TCI state (e.g., TCI-State This can contain / comprise / include / indicate / have corresponding parameters for configuring a quasi-co-address relationship between one or two downlink reference signals and the DM-RS port of the PDSCH, the DM-RS port of the PDCCH, or the CSI-RS port of the CSI-RS resource. The quasi-co-address relationship can be defined by higher-layer parameters for the first downlink reference signal in one or more downlink reference signals. qcl- Type1 To configure. Quasi-colocation relationships can be established using higher-layer parameters for the second downlink reference signal in one or more downlink reference signals. qcl-Type2 Configured. When two downlink reference signals, including a first downlink reference signal and a second downlink reference signal, are indicated by the TCI state, the QCL types of the two downlink reference signals can be different, regardless of whether the first downlink reference signal and the second downlink reference signal are the same or different. The quasi-co-address type corresponding to the downlink reference signal in one or more downlink reference signals can be configured by higher-layer parameters. QCL-Info Higher-level parameters qcl-Type Specify, and one of the following values ​​can be used: - "typeA": {Doppler shift, Doppler spread, average delay, delay spread} - "typeB": {Doppler frequency shift, Doppler spread} -"typeC": {Doppler shift, average delay} - "typeD": {space Rx parameter} The wireless device can be configured with including PDSCH-Config Higher-level parameters dl-OrJointTCI- StateListA list of TCI states configured via the higher-layer parameters (e.g., up to 128 TCI-State configurations). The TCI states in the list can provide / indicate reference signals for quasi-co-location of: i) DM-RS of PDSCH, ii) DM-RS of PDCCH in BWP / cell, and / or iii) CSI-RS. The TCI states in the list can provide / indicate reference signals for determining uplink transmission spatial filters of: i) dynamically licensed PUSCH, ii) configured licensed PUSCH, iii) PUCCH resources in BWP / cell, and / or iv) SRS.

[0205] The wireless device can receive activation commands (e.g., MAC-CE, DCI, unified TCI state activation / deactivation MAC-CE, enhanced unified TCI state activation / deactivation MAC-CE, enhanced unified TCI state activation / deactivation MAC-CE for joint TCI state mode, enhanced unified TCI state activation / deactivation MAC-CE for separate TCI state mode, etc.), which are used to map multiple TCI states and / or multiple pairs of TCI states (e.g., up to 8 TCI states and / or 8 pairs of TCI states) together with one TCI state for downlink channel / signal and / or one TCI state for uplink channel / signal to the code point of the "Transmission Configuration Indication" field of the DCI field for a cell or a group of cells / downlink BWP and / or up to multiple groups of TCI states (e.g., up to 8 groups of TCI states). Each of the multiple groups may include up to a number of TCI states (e.g., up to two TCI states) for downlink and uplink signals / channels, or mapped to DCI fields for a cell or a group of cells / downlink BWPs, and where applicable, for a cell or a group of cells / uplink BWPs. "Transmission Configuration Indicator" The code point can specify at most a few TCI states (e.g., at most two TCI states) for the downlink channel / signal and several TCI states (e.g., at most two TCI states) for the uplink channel / signal. When an activation command activates a set of TCI state IDs for a set of cells / downlink BWPs and, where applicable, for a set of cells / uplink BWPs, the radio device can apply (the same set) of TCI state IDs to / for all downlink and / or uplink BWPs in the indicated cell (or the applicable cell list) if the radio device can determine the list of applicable cells from the cell indicated in the activation command. If the activation command will TCI-State and / or TCI-UL-StateMapped to only one (or a single) TCI code point, once the radio device applies the indication mapping for a single TCI code point, the radio device can apply (indication) to a cell or a group of cells / downlink BWPs and, where applicable, to a cell or a group of cells / uplink BWPs. TCI-State and / or TCI-UL-State .

[0206] when tci-PresentInDCI Set to "Enabled" or tci-PresentDCI-1-2 When configured for CORESET, 1) it is configured via one or more configuration parameters (e.g., RRC messages / parameters). dl-OrJointTCI-StateList And activated by the command TCI-State Activation or 2) configured via one or more configuration parameters (e.g., RRC messages / parameters). ul-TCI-StateList And activated by the command TCI-UL-State The activated wireless device can receive DCI format (e.g., DCI format 1_1 / 1_2), which provides / indicates parameters for updating via synchronized TCI (e.g., simultaneousU-TCI-UpdateList1, simultaneousU-TCI-UpdateList2, simultaneousU- TCI-UpdateList3, simultaneousU-TCI-UpdateList4 The TCI status of one or all cells in the same cell list configured (e.g., TCI-State and / or TCI-UL-State The DCI format may or may not have downlink assignment. Synchronous TCI update parameters can be higher-layer parameters (e.g., RRC parameters).

[0207] When configured via one or more configuration parameters (e.g., RRC message / parameters) dl-OrJointTCI- StateList The wireless device transmits data with an indication of the indicated TCI state (e.g., TCI-State and / or TCI-UL- State When the indicated TCI state corresponds to a positive HARQ-ACK uplink transmission (e.g., PUCCH transmission, PUSCH transmission) in the DCI format, and if the indicated TCI state differs from the previously indicated TCI state, the radio device may apply the indicated TCI state from the first / starting / earliest time slot. TCI-State The time slot is at least a number of symbols following the last symbol of the uplink transmission (e.g., Symbols). The first / starting / earliest time slot and multiple symbols can be determined by the radio device based on the active BWP with the smallest subcarrier spacing among the BWPs of the cell indicated by the application's TCI-State, which is valid at the end of an uplink transmission carrying / with a positive HARQ-ACK. Multiple symbols can be indicated / provided to the radio device via RRC messages (e.g., one or more configuration parameters).

[0208] When the wireless device supports the DCI field "Transmission Configuration Indicator" When two TCI states are in the code point, the wireless device can receive an activation command (e.g., MAC-CE, DCI), which is used to map up to eight combinations of one or two TCI states to the DCI field. "Transmission Configuration Indicator" The code points. The wireless device may not expect to receive more than 8 TCI states in the activation command.

[0209] When the wireless device passes through higher layer parameters cjtSchemePDSCH and dl-OrJointTCI-StateList configuration, And when indicated that there are two TCI states applicable to PDSCH reception and / or reports support for two joint TCI states for PDSCH-CJT: -If the wireless device is configured with higher layer parameters cjtSchemeA Then the wireless device can assume that, relative to QCL-Type A, the PDSCH received PDSCH DM-RS port is quasi-co-located (QCL) with the downlink reference signals of the two indicated TCI states.

[0210] -If the wireless device is configured with higher layer parameters cjtSchemeB Then the wireless device can assume that, relative to QCL-Type A, which does not include the two (indicated) TCI states, the PDSCH receiving PDSCH DM-RS port is quasi-co-located (QCL) with the downlink reference signal of the two indicated TCI states.

[0211] When the wireless device is configured with higher-level parameters dl-OrJointTCI-StateList or higher level parameters TCI-UL- State And by including ControlResourceSet In coresetPoolIndex Two different values ​​(e.g., 0 and 1) of higher-level parameters PDCCH-Config When the higher-level parameters are configured, if the indicated TCI state is related to... coresetPoolIndex The DCI field "Transmission Configuration Indicator" associated with the value in DCI format 1_1 / 1_2 indicates that the indicated TCI state is specific to... coresetPoolIndex The value (e.g., 0 or 1). When the wireless device is in contact with... coresetPoolIndex When DCI format 1_0 / 1_1 / 1_2 is received / detected in the associated CORESET, DCI format 1_1 / 1_2 can be associated with... coresetPoolIndex Values ​​are related.

[0212] When the wireless device is configured with higher-level parametersdl-OrJointTCI-StateList And when there are two indicated TCI states, if the wireless device does not report its capability of two default beams in frequency range 2 and when the offset between the reception of scheduled / activated DCI format 1_0 / 1_1 / 1_2 and the reception of scheduled or activated PDSCH is less than the threshold in frequency range 2 (e.g., timeDurationForQCL If the wireless device receives the first of two indicated TCI states from the scheduled or activated PDSCH, then the wireless device can apply the first indicated TCI state from the two indicated TCI states.

[0213] When the wireless device is configured with higher-level parameters dl-OrJointTCI-StateList And when there are two indicated TCI states, including a first TCI state and a second TCI state (e.g., a combined / DL TCI state of the two indications): -Regardless of the time / scheduling offset between the reception of DCI format 1_0 / 1_1 / 1_2 and the PDSCH reception scheduled / activated by DCI format 1_0 / 1_1 / 1_2, if the wireless device is in frequency range 1 (FR1), or the wireless device reports the capability of two default beams in frequency range 2 (FR2), or - If the wireless device does not report the capability of the two default beams in FR2, and if the time / scheduling offset between the reception of DCI format 1_0 / 1_1 / 1_2 and the PDSCH reception scheduled / activated by DCI format 1_0 / 1_1 / 1_2 is equal to or greater than a threshold (e.g., ) ○ Wireless devices can utilize higher-level parameters timeDurationForQCL Configured to indicate whether the first TCI state, the second TCI state, or both indicated TCI states are applied to PDSCH reception scheduled or activated by DCI format 1_0. Higher layer parameters applyIndicatedTCIState It can be one of the values ​​{"first", "second", "both"}. Only if the wireless device is configured with higher-level parameters. applyIndicatedTCIState When and / or the wireless device reports support for the two joint TCI states for PDSCH-CJT, or when the wireless device is configured with higher-layer parameters cjtSchemePDSCH At that time, the wireless device can be configured with a value set to " sfnSchemePdsch Higher-level parameters both When higher-level parameters applyIndicatedTCIState The value was set to " applyIndicatedTCIStateAt that time, the wireless device can apply both indicated TCI states to the PDSCH reception scheduled or activated by DCI format 1_0 on the search space set of the CORESET (e.g., CORESET#0) except for the CORESET with index zero (e.g., CORESET#0) or the search space set of the Type 0 / 0A / 2 CSS set associated with the CORESET with index zero. The wireless device can receive DCI format 1_0 on / via the search space set different from the search space set of the Type 0 / 0A / 2 CSS set associated with the CORESET with index zero.

[0214] ○ If the wireless device is not equipped with both Then the first indicated TCI-state applies to PDSCH reception scheduled or activated by DCI format 1_0.

[0215] ○ When the wireless device is configured with higher layer parameters applyIndicatedTCIState When the wireless device receives DCI format 1_1 / 1_2 for scheduling or activating PDSCH reception during / via PDSCH transmission, the wireless device can determine the indicated TCI state (e.g., the indicated joint / DL TCI state) for PDSCH reception from the two indicated TCI states according to the following: ■ If DCI format 1_1 / 1_2 indicates the code point "00" in the TCI selection field, the wireless device can apply the first of the two indicated TCI states to all PDSCH DM-RS ports during the PDSCH transmission time scheduled or activated by DCI format 1_1 / 1_2.

[0216] ■ If DCI format 1_1 / 1_2 indicates code point "01" in the TCI selection field, the wireless device can apply the second TCI state of the two indicated TCI states to all PDSCH DM-RS ports during the PDSCH transmission time scheduled or activated by DCI format 1_1 / 1_2.

[0217] ■ If DCI format 1_1 / 1_2 indicates code point "10" in the TCI selection field, the wireless device can apply these two indicated TCI states to the PDSCH receiver scheduled or activated by DCI format 1_1 / 1_2.

[0218] ○ If the wireless device is not configured with higher-level parameters tciSelection-PresentInDCIFurthermore, when the wireless device receives a DCI format 1_1 / 1_2 that schedules / activates PDSCH reception, the wireless device can apply the two indicated TCI states to the PDSCH reception scheduled or activated by DCI format 1_1 / 1_2. In the example, when / if the wireless device does not report / support the use of the SFN default beam for a DCI format that schedules PDSCH reception and does not have a TCI selection field (e.g., tciSelection-PresentInDCI sfn- When the wireless device has the capability to achieve this, it can be expected to be configured with higher-level parameters. DefaultDL-BeamSetup tciSelection- In the example, when / if the base station does not receive from the radio device an instruction to use the SFN default beam for DCI format that is scheduled for PDSCH reception and does not have a TCI selection field (e.g., PresentInDCI When reporting support / capabilities (e.g., UE capability messages), the base station can transmit higher-layer parameters to the radio device. sfn-DefaultDL-BeamSetup tciSelection-PresentInDCI One or more configuration parameters (e.g., in an RRC message). In the example, when / if the base station receives from the radio device an instruction to use the SFN default beam for a DCI format that is scheduled for PDSCH reception and does not have a TCI selection field (e.g., sfn-DefaultDL-BeamSetup When reporting (e.g., UE capability messages), the base station may or may not transmit higher-layer parameters to the radio device. tciSelection-PresentInDCI One or more configuration parameters (e.g., in an RRC message).

[0219] ○ Each downlink BWP can provide / indicate to the radio device whether a first TCI state, a second TCI state, or both indicated TCI states are applied to higher-layer parameters received by the PDSCH scheduled / activated by DCI format 1_0. applyIndicatedTCIState .

[0220] When the wireless device is configured / indicated by the base station with higher-level parameters dl-OrJointTCI-StateList or higher level parameters TCI-UL-State And when there are two indicated TCI states (or two indicated uplink TCI states) including the first indicated TCI state and the second indicated TCI state: - A wireless device with PUSCH transmission scheduled or activated by DCI format 0_0 can transmit the application's first indicated TCI state to the PUSCH. - Wireless devices configured with base stations to transmit PUSCH corresponding to Type 1 configured authorization can be expected to be configured with higher-layer parameters. applyIndicatedTCIState .

[0221] ○ If higher-level parameters applyIndicatedTCIStateWhen set to "first", the wireless device can transmit the first indicated TCI state to the PUSCH. The wireless device can apply the first indicated TCI state to each PUSCH transmission.

[0222] ○ If higher-level parameters applyIndicatedTCIState When set to "Second", the wireless device can transmit the TCI state indicated by the second application to the PUSCH. The wireless device can apply the TCI state indicated by the second application to each PUSCH transmission.

[0223] ○ If higher-level parameters applyIndicatedTCIState If set to "both", the wireless device can transmit the TCI states indicated by these two parameters to the PUSCH. If the higher-layer parameter... applyIndicatedTCIState If set to "both" (or if both indicated TCI states are indicated to apply to PUSCH transmissions), the wireless device can apply: ■ The timing of PUSCH transmission associated with the first SRS resource set used for codebook / non-codebook transmission, or the first indicated TCI state of the PUSCH antenna port, and ■ The timing of PUSCH transmission associated with the second SRS resource set used for codebook / non-codebook transmission or the second indicated TCI state of the PUSCH antenna port.

[0224] ○ If the wireless device is transmitted by the base station through a channel containing / including different ControlResourceSets Higher-level parameters coresetPoolIndex Two different values ​​of higher-level parameters PDCCH-Config If configured / indicated, then the first indicated TCI state and the second indicated TCI state may be specific to higher-level parameters having a value of 0. coresetPoolIndex and higher-level parameters with a value of 1 coresetPoolIndex Yes. If the wireless device is transmitted by the base station through a method that includes / includes different... ControlResourceSets Higher-level parameters coresetPoolIndex Two different values ​​of higher-level parameters PDCCH-Config Configuration / indication, then higher-level parameters applyIndicatedTCIState It can be excluded from being set as an indicator. this two The indicated TCI status will apply to both PUSCH transmissions. When the wireless device is configured with higher-level parameters dl-OrJointTCI-StateList , through including ControlResourceSet In coresetPoolIndex Two different values ​​of higher-level parameters PDCCH-Config During configuration, if the wireless device does not report its frequency range 2 per... coresetPoolIndexThe default beam capability: -When AND equals 0 coresetPoolIndex The offset between the reception of DCI format 1_0 / 1_1 / 1_2 in the associated CORESET and the PDSCH reception scheduled / activated by DCI format 1_0 / 1_1 / 1_2 is less than the threshold in frequency range 2 (e.g., timeDurationForQCL When ), the wireless device can send an application-specific PDSCH to the scheduled / activated PDSCH, equal to 0. coresetPoolIndex The value indicates the combined / DL TCI status.

[0225] - Wireless devices may not expect a value equal to 1. coresetPoolIndex The offset between the reception of DCI format 1_0 / 1_1 / 1_2 in the associated CORESET and the PDSCH reception scheduled / activated by DCI format 1_0 / 1_1 / 1_2 is less than the threshold in frequency range 2 (e.g., timeDurationForQCL ).

[0226] When the wireless device is configured with higher-level parameters dl-OrJointTCI-StateList And when having two indicated TCI states (e.g., a combined / DL TCI state of the two indicated states) including a first TCI state and a second TCI state, the wireless device can be configured / equipped with higher-layer parameters per / for / corresponding to aperiodic CSI-RS resource sets or aperiodic CSI-RS resources within aperiodic CSI-RS resource sets. applyIndicatedTCIState The higher-level parameters are configured / equipped to instruct the wireless device to apply a first TCI state or a second TCI state to an aperiodic CSI-RS resource set or to aperiodic CSI-RS resources within an aperiodic CSI-RS resource set. The wireless device can be configured with higher-level parameters for aperiodic CSI-RS resource sets for CSI or beam management (BM). followUnifiedTCIState The time / scheduling offset between the last symbol of the PDCCH carrying / having DCI and the first / starting / earliest symbol of the aperiodic CSI-RS resource in the aperiodic CSI-RS resource set triggered by DCI can be equal to or greater than a threshold (e.g., beamSwitchTiming ).

[0227] If the wireless device includes / comprises different cores (e.g.) ControlResourceSets Higher-level parameters in ) CORESETPoolIndex Two different values ​​of higher-level parameters PDCCH-Config If configured, the first TCI state and the second TCI state may be respectively associated with higher-level parameters having a value of 0. coresetPoolIndex and higher-level parameters with a value of 1 coresetPoolIndex The two indicated TCI states correspond to each other.

[0228] When the wireless device is configured with higher-level parameters dl-OrJointTCI-StateList And when there are two indicated TCI states including a first TCI state and a second TCI state (e.g., a combined / DL TCI state of two indicated states), and if the time / scheduling offset between the last symbol of the PDCCH carrying / having DCI and the first / starting / earliest symbol of the aperiodic CSI-RS resource in the aperiodic CSI-RS resource set triggered by DCI is less than a threshold (e.g., beamSwitchTiming ): -If no downlink signal exists in the same symbol as the aperiodic CSI-RS resource: If the wireless device is in frequency range 1 (FR1), or if the wireless device reports the ability of two default beams in frequency range 2 (FR2), then the wireless device may provide / indicate higher-layer parameters based on (or according to) to / for aperiodic CSI-RS resources or a set of aperiodic CSI-RS resources including aperiodic CSI-RS resources. applyIndicatedTCIState Apply the first TCI state or the second TCI state to the aperiodic CSI-RS via the aperiodic CSI-RS resource.

[0229] Otherwise, the wireless device may apply the first TCI state to the aperiodic CSI-RS via the aperiodic CSI-RS resource.

[0230] Otherwise, if a downlink signal with the indicated TCI state exists in the same symbol as the aperiodic CSI-RS resource, the wireless device can apply the QCL assumptions (e.g., the indicated TCI state) of the downlink signal when receiving aperiodic CSI-RS via the aperiodic CSI-RS resource. The downlink signal can be indicated by a threshold greater than or equal to... timeDurationForQCL The offset scheduling of PDSCH, periodic CSI-RS, semi-persistent CSI-RS, or at a threshold greater than or equal to that reported by the wireless device. beamSwitchTiming Aperiodic CSI-RS for offset scheduling 。 If a PDSCH with a combined / DL TCI state applying two indications exists in the same symbol as the aperiodic CSI-RS resource, the radio device can proceed according to the higher-level configuration provided / indicated to the aperiodic CSI-RS resource or the aperiodic CSI-RS resource set. applyIndicatedTCIState Apply the first indication of the combined / DL TCI status or the second indication of the combined / DL TCI status to the aperiodic CSI-RS via the aperiodic CSI-RS resource.

[0231] When wireless device i) is configured with higher layer parameters ​ii) By including / compiling different CORESETS (e.g., ​ Higher-level parameters in ) ​ Two different values ​​of higher-level parameters ​ Configuration, iii) has two indicated TCI states including a first TCI state and a second TCI state (e.g., a combined / DL TCI state of the two indicated states), and if the time / scheduling offset between the last symbol of the PDCCH carrying / having DCI and the first / starting / earliest symbol of the aperiodic CSI-RS resource in the aperiodic CSI-RS resource set triggered by DCI is less than a threshold (e.g., ​ ): -If no downlink signal exists in the same symbol as the aperiodic CSI-RS resource: If the wireless device is in frequency range 1 (FR1), or if the wireless device reports the default beam indexed per coreset pool in frequency range 2 (FR2), then the wireless device may provide / indicate higher-layer parameters based on (or according to) to / for aperiodic CSI-RS resources or a set of aperiodic CSI-RS resources including aperiodic CSI-RS resources. ​ Apply the first TCI state or the second TCI state to the aperiodic CSI-RS via the aperiodic CSI-RS resource.

[0232] Otherwise, the wireless device can use the aperiodic CSI-RS resource to apply parameters to the aperiodic CSI-RS application with a value of 0. ​ The associated (or specific to the higher-level parameter, or the higher-level parameter) first TCI state.

[0233] Otherwise, if a downlink signal with the indicated TCI state exists in the same symbol as the aperiodic CSI-RS resource, the wireless device can apply the QCL assumptions (e.g., the indicated TCI state) of the downlink signal when receiving aperiodic CSI-RS via the aperiodic CSI-RS resource. The downlink signal can be indicated by a threshold greater than or equal to... ​ The offset scheduling of PDSCH, periodic CSI-RS, semi-persistent CSI-RS, or at a threshold greater than or equal to that reported by the wireless device. ​ Aperiodic CSI-RS for offset scheduling 。

[0234] For CORESET with index 0 -If the wireless device is equipped with / indicated to TCI status and is indicated / configured with higher-level parameters for CORESET. ​The wireless device can then assume that the DM-RS antenna port used for PDCCH reception in the CORESET and the DM-RS antenna port used for PDSCH reception in DCI format scheduling provided by the PDCCH reception in the CORESET are quasi-co-located with the reference signal provided / indicated by the indicated TCI state. - Otherwise, if the wireless device is equipped with / instructed to / configured with higher-level parameters dl-OrJointTCI- StateList It is indicated to have a first TCI state and a second TCI state, and is equipped with / indicated / configured with higher-level parameters for CORESET. apply-IndicatedTCIState : ○ If higher-level parameters apply-IndicatedTCIState = "First", then the wireless device can assume that the DM-RS antenna port used for PDCCH reception in CORESET is quasi-co-located with the reference signal provided / indicated by the first TCI state. ○ If higher-level parameters apply-IndicatedTCIState = "Second", then the wireless device can assume that the DM-RS antenna port used for PDCCH reception in CORESET is quasi-co-located with the reference signal provided / indicated by the first TCI state. ○ If higher-level parameters apply-IndicatedTCIState = "both", then the wireless device can assume that the DM-RS antenna port used for PDCCH reception in CORESET is quasi-co-located with the reference signal provided / indicated by the first TCI state and the second TCI state.

[0235] - Otherwise, the wireless device may assume that the DM-RS antenna port used for PDCCH reception in CORESET is quasi-co-located with the following: ○ The reference signal (if present) provided / indicated / configured by the TCI status indicated by the MAC CE activation command for CORESET, or ○ If no MAC CE activation command indicating the TCI state for CORESET is received after the most recent random access procedure, then it is either the SS / PBCH block identified by the radio device during the most recent random access procedure that was not initiated by a PDCCH command that triggered a contention-free random access procedure, or the SS / PBCH block identified by the radio device during the most recent configured-authorized PUSCH transmission for small data transmission (SDT).

[0236] If the wireless device is equipped with / configured with / indicated higher-level parameters dl-OrJointTCI-StateList And is indicated to have a first TCI state and a second TCI state, and is equipped with / indicated / configured with higher-level parameters for CORESETs other than the CORESET with index 0. apply-IndicatedTCIState , -If CORESET is only associated with the USS set and / or the Type3-PDCCH CSS set ○ If higher-level parameters apply-IndicatedTCIState = "First", then the wireless device can assume that the DM-RS antenna port used for PDCCH reception in CORESET is quasi-co-located with the reference signal provided / indicated by the first TCI state. ○ If higher-level parameters apply-IndicatedTCIState = "Second", then the wireless device can assume that the DM-RS antenna port used for PDCCH reception in CORESET is quasi-co-located with the reference signal provided / indicated by the first TCI state. ○ If higher-level parameters apply-IndicatedTCIState = "both", then the wireless device can assume that the DM-RS antenna port used for PDCCH reception in CORESET is quasi-co-located with the reference signal provided / indicated by the first TCI state and the second TCI state.

[0237] - If CORESET is associated with at least one CSS set other than the Type3-PDCCH CSS set, ○ If higher-level parameters apply-IndicatedTCIState = "First", then the wireless device can assume that the DM-RS antenna port used for PDCCH reception in CORESET is quasi-co-located with the reference signal provided / indicated by the first TCI state. ○ If higher-level parameters apply-IndicatedTCIState = "Second", then the wireless device can assume that the DM-RS antenna port used for PDCCH reception in CORESET is quasi-co-located with the reference signal provided / indicated by the first TCI state. ○ If higher-level parameters apply-IndicatedTCIState = "both", then the wireless device can assume that the DM-RS antenna port used for PDCCH reception in CORESET is quasi-co-located with the reference signal provided / indicated by the first TCI state and the second TCI state. ○ If higher-level parameters apply-IndicatedTCIState = "None", then the wireless device can assume that the DM-RS antenna port used for PDCCH reception in CORESET is quasi-co-located with the reference signal provided / indicated / configured by the TCI state indicated by the MAC CE activation command for CORESET. If the wireless device is provided / configured / indicated with higher-level parameters dl-OrJointTCI-StateList ,and - For the first core set on the active DL BWP of the serving cell, no higher-level parameters are provided / configured / indicated. coresetPoolIndexOr it may be provided / configured / indicated to a higher-level parameter with a value of 0. coresetPoolIndex , - For the second CORESET on the active DL BWP of the serving cell, a higher-layer parameter with a value of 1 is provided / configured / indicated. coresetPoolIndex ,and - For CORESET excluding index 0, and a) associated only with the USS set and / or the Type3-PDCCH CSS set, or b) associated with a CSS set other than the Type3-PDCCH CSS set and provided / configured / indicated with higher-level parameters. followUnifiedTCI-State The first core set and the second core set, The wireless device may assume that the DM-RS antenna port used for PDCCH reception in the first CORESET and the second CORESET, and the DM-RS antenna port used for PDSCH reception in DCI format scheduled by the PDCCH reception in the first CORESET and the second CORESET, are respectively connected to the DM-RS antenna port specifically for the first CORESET (or the second CORESET). coresetPoolIndex =0) and the second CORESET (or coresetPoolIndex The reference signal quasi-co-address provided by the TCI state indicated by =1) ○ Wireless devices can be used separately and separately specific to the first CORESET (or coresetPoolIndex =0) and the second CORESET (or coresetPoolIndex =1) corresponding spatial domain filter to transmit PUSCH in DCI format scheduled by PDCCH reception in the first CORESET and the second CORESET.

[0238] When the wireless device is configured / indicated by the base station with higher-level parameters dl-OrJointTCI-StateList or higher level parameters TCI-UL-State And when there are two indicated TCI states (or two indicated uplink TCI states) including the first indicated TCI state and the second indicated TCI state: - A wireless device with PUSCH transmission scheduled or activated by DCI format 0_0 can transmit the application's first indicated TCI state to the PUSCH. - Wireless devices configured with base stations to transmit PUSCH corresponding to Type 1 configured authorization can be expected to be configured with higher-layer parameters. applyIndicatedTCIState .

[0239] ○ If higher-level parameters applyIndicatedTCIStateWhen set to "first", the wireless device can transmit the first indicated TCI state to the PUSCH. The wireless device can apply the first indicated TCI state to each PUSCH transmission.

[0240] ○ If higher-level parameters applyIndicatedTCIState When set to "Second", the wireless device can transmit the TCI state indicated by the second application to the PUSCH. The wireless device can apply the TCI state indicated by the second application to each PUSCH transmission.

[0241] ○ If higher-level parameters [[ID=二十九]]applyIndicatedTCIState If set to "both", the wireless device can transmit the TCI states indicated by these two parameters to the PUSCH. If the higher-layer parameter... applyIndicatedTCIState If set to "both" (or if both indicated TCI states are indicated to apply to PUSCH transmissions), the wireless device can apply: ■ The timing of PUSCH transmission associated with the first SRS resource set used for codebook / non-codebook transmission, or the first indicated TCI state of the PUSCH antenna port, and ■ The timing of PUSCH transmission associated with the second SRS resource set used for codebook / non-codebook transmission or the second indicated TCI state of the PUSCH antenna port.

[0242] ○ If the wireless device is transmitted by the base station through a channel containing / including different ControlResourceSets Higher-level parameters coresetPoolIndex Two different values ​​of higher-level parameters PDCCH-Config If configured / indicated, then the first indicated TCI state and the second indicated TCI state may be specific to higher-level parameters having a value of 0. coresetPoolIndex and higher-level parameters with a value of 1 coresetPoolIndex Yes. If the wireless device is transmitted by the base station through a method that includes / includes different... ControlResourceSets Higher-level parameters coresetPoolIndex Two different values ​​of higher-level parameters PDCCH-Config Configuration / indication, then higher-level parameters applyIndicatedTCIState It can be excluded from being set as an indicator. these two The indicated TCI status will apply to both PUSCH transmissions.

[0243] When the following conditions exist: the wireless device is configured with higher-level parameters dl-OrJointTCI-StateList or higher level parameters TCI-UL-State Furthermore, the two SRS resource sets have higher-level parameters. srs-ResourceSetToAddModList In or SRS-ResourceSet Higher-level parametersusage Higher-level parameters set to "codebook" or "nonCodebook" srs-ResourceSetToAddModListDCI-0-2 Configuration in the middle, and higher-level parameters multipanelScheme The higher-layer parameter is set to "SDMscheme" or "SFNscheme" and configured with uplink grant (e.g., type 1 configured with uplink grant). rrc-ConfiguredUplinkGrant Excluding / not including higher-level parameters srs-ResourceIndicator2 or higher level parameters precodingAndNumberOfLayers2 PUSCH transmission timing with configured uplink authorization: applied to higher layer parameters in the first indicated TCI state (or TCI-UL state). rrc-ConfiguredUplinkGrant (Or, with uplink authorization configured) it can be associated with the first SRS resource set in two SRS resource sets, and the second indicated TCI state (or TCI-UL state) is applied to the higher-layer parameters. rrc-ConfiguredUplinkGrant (Or, with uplink authorization configured) it can be associated with the second SRS resource set in two SRS resource sets.

[0244] When the following conditions exist: higher-level parameters multipanelScheme Set to "SDMScheme" and both SRS resource sets are configured by the base station at a higher layer parameter. srs-ResourceSetToAddModList In the middle or higher level parameters SRS- ResourceSet Higher-level parameters usage Higher-level parameter set to "codebook" srs- ResourceSetToAddModListDCI-0-2 In the configuration / indication, the two SRIs and two TPMIs can be given / provided / indicated for DCI formats 0_1 and 0_2 / in the two SRS resource indicator fields and two precoding information and layer number fields in the DCI format: -when SRS Resource Set Indicator When the code point "10" is indicated in DCI format 0_1 / 0_2: ○ The first TPMI of the two TPMIs can indicate the transport precoder to be applied to layers {0…v1-1}, where v1 is the layer number indicated by the first TPMI. The first TPMI corresponds to the SRS resource selected by the first SRI of the two SRSs when multiple SRS resources are configured for the first SRS resource set, or if a single SRS resource is configured for the first SRS resource set. ○ The second TPMI of the two TPMIs can indicate the transport precoder to be applied to layers {v1…v2+v1-1}, where v2 is the layer number indicated by the second TPMI, which corresponds to the SRS resource selected by the second SRI of the two SRIs when multiple SRS resources are configured for the second SRS resource set, or if a single SRS resource is configured for the second SRS resource set, v1≤ maxRankSdm and v2≤ maxRankSdm or maxRankSdmDCI-0-2 and maxRankSdm or maxRankSdmDCI-0-2 The maximum number of layers that can be applied to the first SRS resource set and the second SRS resource set can be defined separately.

[0245] -when SRS Resource Set Indicator The code point "00" or "01" in DCI format 0_1 / 0_2 When the instructions are given, The second SRI and the second TPMI can be retained, and the first TPMI can indicate the precoder to be applied to layers {0…v-1}, where v ≤ maxRank in maxRank You can define the maximum number of layers.

[0246] - Can retain DCI format 0_1 / 0_2 SRS Resource Set Indicator The code point "11".

[0247] - For one or two TPMIs, a transport precoder can be selected from an uplink codebook having a number of antenna ports equal to the higher-layer parameters for the indicated SRI. SRS-Config Higher-level parameters nrofSRS-Ports .

[0248] - When two SRIs are indicated, the wireless device can expect the same number of SRS antenna ports associated with both indicated SRIs. This applies when the wireless device is configured / indicated with higher-level parameters set to "codebook". txConfig At that time, the wireless device can be configured / indicated to have at least one SRS resource. Time slot n Each of the one or two SRIs indicated in the configuration can be associated with the most recent transmission of an SRS resource in the associated SRS resource set identified by one of the two SRIs, where the SRS resource predates the reception of the PDCCH carrying the SRI in DCI format 0_1 / 0_2. When the two SRS resource sets are at a higher layer parameter... srs-ResourceSetToAddModList In the middle or higher level parameters SRS-ResourceSet Higher-level parameters usage Higher-level parameter set to "codebook" srs-ResourceSetToAddModListDCI-0-2When configuring / instructing, it may not be expected that the wireless device will have a different number of SRS resources configured in the two SRS resource sets.

[0249] When the following conditions exist: higher-level parameters multipanelScheme Set to "SFNScheme" and both SRS resource sets are determined by the base station at a higher layer parameter. srs-ResourceSetToAddModList In the middle or higher level parameters SRS- ResourceSet Higher-level parameters usage Higher-level parameter set to "codebook" srs- ResourceSetToAddModListDCI-0-2 In the configuration / indication, the two SRIs and two TPMIs can be given / provided / indicated for DCI formats 0_1 and 0_2 / in the two SRS resource indicator fields and two precoding information and layer number fields in the DCI format: -when SRS Resource Set Indicator When the code point "10" is indicated in DCI format 0_1 / 0_2: ○ The first TPMI of the two TPMIs can indicate the transport precoder to be applied to layers {0…v-1}, and the second TPMI of the two TPMIs can indicate the transport precoder to be applied to layers {0…v-1}, where v ≤ maxRankSfn or maxRankSfnDCI-0-2 and maxRankSfn or maxRankSfnDCI-0-2 The maximum number of layers that can be applied to the first SRS resource set and the second SRS resource set can be defined separately.

[0250] -when SRS Resource Set Indicator The code point "00" or "01" in DCI format 0_1 / 0_2 When the instructions are given, The second SRI and the second TPMI can be retained, and the first TPMI can indicate the precoder to be applied to layers {0…v-1}, where v ≤ maxRank in maxRank You can define the maximum number of layers.

[0251] - Can retain DCI format 0_1 / 0_2 SRS Resource Set Indicator The code point "11".

[0252] - For one or two TPMIs, a transport precoder can be selected from an uplink codebook having a number of antenna ports equal to the higher-layer parameters for the indicated SRI. SRS-Config Higher-level parameters nrofSRS-Ports .

[0253] - When two SRIs are indicated, the wireless device can expect the same number of SRS antenna ports associated with both indicated SRIs. This applies when the wireless device is configured / indicated with higher-level parameters set to "codebook". txConfig At that time, the wireless device can be configured / indicated to have at least one SRS resource. Time slot n Each of the one or two SRIs indicated in the configuration can be associated with the most recent transmission of an SRS resource in the associated SRS resource set identified by one of the two SRIs, where the SRS resource predates the reception of the PDCCH carrying the SRI in DCI format 0_1 / 0_2. When the two SRS resource sets are at a higher layer parameter... srs-ResourceSetToAddModList In the middle or higher level parameters SRS-ResourceSet Higher-level parameters usage Higher-level parameter set to "codebook" srs-ResourceSetToAddModListDCI-0-2 When configuring / instructing, it may not be expected that the wireless device will have a different number of SRS resources configured in the two SRS resource sets.

[0254] When the following conditions exist: higher-level parameters multipanelScheme Set to "SDMScheme" and both SRS resource sets are configured by the base station at a higher layer parameter. srs-ResourceSetToAddModList In the middle or higher level parameters SRS- ResourceSet Higher-level parameters usage Higher-level parameters set to "nonCodebook" srs- ResourceSetToAddModListDCI-0-2 In the configuration / indication, the two SRIs can be given / provided / indicated through the two SRS resource indicator fields for DCI format 0_1 ​​and DCI format 0_2 / in the DCI format: -when SRS Resource Set Indicator When the code point "10" is indicated in DCI format 0_1 / 0_2: ○ The first SRI of the two SRIs can indicate the resource to be associated with layer {0…v1-1}, where v1 is the layer number indicated by the first SRI, and the second SRI of the two SRIs can indicate the resource to be associated with layer {v1…v2+v1-1}, where v1≤…v2+v1-1. L max And v2≤ L max .

[0255] -when SRS Resource Set Indicator The code point "00" or "01" in DCI format 0_1 / 0_2 When the instructions are given, The second SRI can be retained, and the first SRI can indicate the resource associated with layer {0…v-1}, where v ≤ Lmax .

[0256] When the following conditions exist: higher-level parameters multipanelScheme Set to "SFNScheme" and both SRS resource sets are determined by the base station at a higher layer parameter. srs-ResourceSetToAddModList In the middle or higher level parameters SRS- ResourceSet Higher-level parameters usage Higher-level parameters set to "nonCodebook" srs- ResourceSetToAddModListDCI-0-2 In the configuration / indication, the two SRIs can be given / provided / indicated through the two SRS resource indicator fields for DCI format 0_1 ​​and DCI format 0_2 / in the DCI format: -when SRS Resource Set Indicator When the code point "10" is indicated in DCI format 0_1 / 0_2: ○ The first SRI of the two SRIs can indicate the resource associated with layer {0…v-1}, and the second SRI of the two SRIs can indicate the resource associated with layer {0…v-1}, where v ≤ L max .

[0257] -when SRS Resource Set Indicator The code point "00" or "01" in DCI format 0_1 / 0_2 When the instructions are given, The second SRI can be retained, and the first SRI can indicate the resource associated with layer {0…v-1}, where v ≤ L max When two SRIs are indicated, the wireless device can expect the same number of SRS antenna ports associated with both indicated SRIs.

[0258] - When the wireless device is configured / indicated with a higher-level parameter set to "nonCodebook" txConfig At that time, the wireless device can be configured / indicated to have at least one SRS resource. Time slot n Each of the one or two SRIs indicated in the configuration can be associated with the most recent transmission of an SRS resource in the associated SRS resource set identified by one of the two SRIs, where the SRS resource predates the reception of the PDCCH carrying the SRI in DCI format 0_1 / 0_2. When the two SRS resource sets are at a higher layer parameter... srs-ResourceSetToAddModList In the middle or higher level parameters SRS-ResourceSet Higher-level parameters usage Higher-level parameters set to "nonCodebook" srs-ResourceSetToAddModListDCI-0-2 When configuring / instructing, it may not be expected that the wireless device will have a different number of SRS resources configured in the two SRS resource sets.

[0259] When the following conditions exist: the wireless device is configured / instructed by the base station with higher-level parameters. dl-OrJointTCI- StateList or higher level parameters TCI-UL-State And it has two indicated TCI states (or a combined / uplink TCI state of the two indicated states) including a first indicated TCI state and a second indicated TCI state, and the two SRS resource sets are determined by the base station at a higher layer parameter. srs-ResourceSetToAddModList In the middle or higher level parameters SRS-ResourceSet Higher-level parameters usage Higher-level parameters set to "codebook" or "nonCodebook" srs- ResourceSetToAddModListDCI-0-2 Configuration / indication in the middle, for PUSCH repeating type A or type B, or for higher-level parameters multipanelScheme When PUSCH transmission is set to "SDMscheme" or "SFNscheme", the association between the first indicated TCI state and the second indicated TCI state and the PUSCH transmission timing or the corresponding PUSCH antenna port can be determined as follows: -If DCI format 0_1 ​​or DCI format 0_2 indicates SRS Resource Set Indicator If the code point is "00" or "01", then the first indicated TCI state or the second indicated TCI state can be applied by the wireless device to all PUSCH transmission times respectively.

[0260] -If DCI format 0_1 ​​or DCI format 0_2 indicates SRS Resource Set Indicator The code point "10" or "11", and higher-level parameters multipanelScheme Not configured. The first indicated TCI state can be applied by the wireless device to the PUSCH transmission timing associated with the first SRS resource set in the two SRS resource sets, and the second indicated TCI state can be applied to the PUSCH transmission timing associated with the second SRS resource set in the SRS resource set, wherein it can be based on higher-layer parameters. PUSCH-Config Higher-level parameters cyclicMapping or higher level parameters sequentialMapping Whether it is enabled determines the correlation between PUSCH transmission timing and the two SRS resource sets.

[0261] -If DCI format 0_1 ​​or DCI format 0_2 indicates SRS Resource Set Indicator The code point "10", and higher-level parameters multipanelScheme It is configured and set to "SDMscheme" or "SFNscheme". The first indicated TCI state can be applied by the wireless device to the first PUSCH antenna port during a PUSCH transmission associated with the first SRS resource set, and the second indicated TCI state can be applied by the wireless device to the second PUSCH antenna port during a PUSCH transmission associated with the second SRS resource set. The first PUSCH antenna port and the second PUSCH antenna port can be the same or different.

[0262] When the wireless device is configured / instructed / provided with higher-level parameters dl-OrJointTCI-StateList or higher level parameters TCI-UL-State And when there are two indicated TCI states (or two indicated uplink TCI states) including the first indicated TCI state and the second indicated TCI state, for SRS-ResourceSet Higher-level parameters usage Set to " codebook "", nonCodebook "or" antennaSwitching "periodic, semi-persistent, or aperiodic SRS resource sets, or for SRS-ResourceSet Higher-level parameters usage Set to " beamManagement "Aperiodic SRS resource set" - Wireless devices can target SRS resource sets via higher-level parameters applyIndicatedTCIState The higher-level parameters are configured / indicated / provided / configured / indicated / provided to indicate whether the wireless device applies a first indicated TCI state or a second indicated TCI state to the SRS resource set.

[0263] ○ When a wireless device passes through a channel containing higher-level parameters ControlResourceSet Higher-level parameters coresetPoolIndex Two different values ​​of higher-level parameters PDCCH-Config During configuration, the first indicated TCI state and the second indicated TCI state are respectively associated with higher-level parameters having a value of 0. coresetPoolIndex and higher-level parameters with a value of 1 coresetPoolIndex The indicated TCI status (or uplink TCI status) corresponds to the TCI status.

[0264] -When a wireless device includes / contains higher-layer parameters ControlResourceSet Higher-level parameters X Two different values ​​of higher-level parameters coresetPoolIndex The higher-level parameters are configured / indicated / provided / configured / indicated / provided, but higher-level parameters for aperiodic SRS resource sets are not configured / indicated / provided. PDCCH-Config When, if the non-periodic SRS resource set is composed of and applyIndicatedTCIStateIf the PDCCH on the associated CORESET is triggered, the wireless device can apply a specific application to the aperiodic SRS resource set. coresetPoolIndex The value indicates the TCI status (or uplink TCI status).

[0265] -When higher-level parameters are included coresetPoolIndex Higher-level parameters SRS-ResourceSet When two SRS resource sets, the first SRS resource set and the second SRS resource set, are configured / indicated / provided and set to "codebook" or "nonCodebook", the wireless device may not expect the first indicated TCI state to be applied to the second SRS resource set and the second indicated TCI state to be applied to the first SRS resource set.

[0266] Wireless devices can target PUCCH resources via higher-layer parameters usage The higher-layer parameters are configured / indicated / provided / configured / indicated / provided to instruct the radio device to apply a first indicated TCI state, a second indicated TCI state, or both indicated TCI states to the PUCCH resource. Higher-layer parameters applyIndicatedTCIState It can be an indication of one or both of the indicated TCI states applied to the PUCCH resource.

[0267] -If higher level parameters applyIndicatedTCIState When set to "first", the wireless device can transmit PUCCH data via PUCCH resource utilization / using the spatial domain filter corresponding to the TCI state indicated by "first". -If higher level parameters applyIndicatedTCIState When set to "Second", the wireless device can transmit PUCCH data via PUCCH resource utilization / using the spatial domain filter corresponding to the TCI state indicated by the second setting. -If higher level parameters applyIndicatedTCIState When set to "both", the wireless device can transmit PUCCH data via PUCCH resource utilization / use of a spatial domain filter corresponding to the first indicated TCI state and a spatial domain filter corresponding to the second indicated TCI state.

[0268] If wireless device - No higher-layer parameters were provided for the first core set on the active downlink BWP of the cell. applyIndicatedTCIState Or it may be provided with a higher-level parameter having a value of 0. coresetPoolIndex ,and - The second CORESET on the active downlink BWP of the cell is provided with a higher-layer parameter having a value of 1. X The first indicated TCI state and the second indicated TCI state can be specific to the first CORESET (or a higher-level parameter with a value of 0), respectively. coresetPoolIndex ) and the second CORESET (or a higher-level parameter with a value of 1) coresetPoolIndex ).

[0269] The base station can instruct the wireless device to use / via PUCCH resources in multiple time slots (e.g., PUCCH transmission is carried out over a time slot. This applies if the PUCCH resource is indicated by a DCI format and includes (or is configured with) higher-layer parameters. coresetPoolIndex The number of time slots can then be determined by higher-level parameters. coresetPoolIndex pucch-RepetitionNrofSlots Indication. If the PUCCH resource is not indicated by the DCI format, or if the PUCCH resource does not include (or is not configured with) higher-level parameters. pucch- The number of time slots can then be determined by higher-level parameters. RepetitionNrofSlots instruct.

[0270] When repeated PUCCH resources used for PUCCH transmissions performed by a wireless device include a first TCI state and a second TCI state (e.g., pucch-RepetitionNrofSlots = "both") and the wireless device was not provided with higher-level parameters. nrofSlots At that time, wireless device - In time slots (e.g., When the number of time slots is equal to two, the first indicated TCI state and the second indicated TCI state are used for the first and second repetitions of PUCCH transmission, respectively. - Transmitted via PUCCH This process repeats, alternating between the first indicated TCI state and the second indicated TCI state, where if the higher-level parameter... applyIndicatedTCIState = "cyclicMapping", then Otherwise (e.g., if higher-level parameters) multipanelSfnScheme = " mappingPattern "),but .

[0271] When a wireless device transmits a repetition of PUSCH transmission over or across K time slots (e.g., K consecutive time slots) (K = 2), the wireless device and / or base station may apply a first SRS resource set and a second SRS resource set to the first and second time slots of the two time slots, respectively.

[0272] When a wireless device transmits repeated PUSCH transmissions over or across K time slots (e.g., K consecutive time slots) for more than two time slots, and when higher-layer parameters... mappingPatternWhen “cyclicMapping” is enabled, the wireless device and / or base station can apply the first SRS resource set and the second SRS resource set to the first and second time slots in the K time slots, respectively, and the same SRS resource set mapping pattern can continue to be applied to the remaining time slots in the K time slots.

[0273] When a wireless device transmits repeated PUSCH transmissions over or across K time slots (e.g., K consecutive time slots) for more than two time slots, and when higher-layer parameters... sequentialMapping X mappingPattern mappingPattern = " "sequentialMapping" At that time, the wireless device and / or base station may apply the first SRS resource set to the first and second time slots in the K time slots, and the wireless device and / or base station may apply the second SRS resource set to the third and fourth time slots in the K time slots, and the same SRS resource set mapping pattern may continue to be applied to the remaining time slots in the K time slots.

[0274] Throughout this specification, unless otherwise specified, the sizes of the various fields in the time domain can be expressed in time units. To express, among which Hz and .constant ,in , and .

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

[0276] For subcarrier spacing configuration ○ (For example, 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 within a time slot. 1 consecutive OFDM symbol, of which It can be based on / depend 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.

[0277] Transmissions (e.g., downlink transmissions, uplink transmissions, and sidelink transmissions) can be organized into sequences with... A frame of duration. A frame can include... The duration is ten subframes (or composed of them). The number of consecutive OFDM symbols in each subframe can be... Each frame can be divided into two equal-sized half-frames, each consisting of five subframes. Half-frame 0 is composed of subframes 0-4, and half-frame 1 is composed of subframes 5-9.

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

[0279] Uplink frame number used for transmission from wireless devices It can be started before the corresponding downlink frame is started at the wireless device. ,in - It can be the timing advance (or timing advance value) between the downlink and uplink, and This can be a fixed offset used to calculate timing advance. For example, for the msgA transmission on PUSCH, It can be used by wireless devices.

[0280] - Parameters can be obtained from higher layers (or RRC or one or more configurations) by a wireless device. TACommon , TACommonDrift and TACommonDriftVariation (If configured) Export / OK (or be instructed 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.

[0281] - 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.

[0282] The wireless device can receive one or more messages including 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 of the cell (e.g., serving cell, non-serving cell) for the cell (e.g., timing advance offset for the cell). The value of ). In the example, one or more configuration parameters may not indicate the cell's / the timing advance offset used for the cell (e.g., The value of n-TimingAdvanceOffset. One or more configuration parameters may not include n-TimingAdvanceOffset. The timing advance offset for the cell / used by the cell is not indicated based on one or more configuration parameters (e.g., The wireless device can determine the timing advance offset for / for the cell (e.g., ) value, The default value for the cell's timing advance offset.

[0283] If, for the serving cell, the radio device is provided / configured / indicated via one or more messages, there are two [cores] for the first core and the second core. coresetPoolIndex Values ​​0 and 1, or no value is provided for the first CORESET. coresetPoolIndex The value is also provided for the second core set. coresetPoolIndex A value of 1 indicates that the wireless device can be provided / configured / indicated as useful via one or more messages. n-TimingAdvanceOffset The first timing advance offset is indicated (e.g., ) and use n-TimingAdvanceOffset2 The second timing advance offset is indicated (e.g., These two timing advance offsets are used for transmissions employing the TCI states associated with the first and second CORESETs, respectively. Besides being used for transmissions corresponding to the serving cell... physCellId The first timing advance offset of the transmission of the spatial domain filter associated with the TCI state (e.g., In addition to this, the wireless device may also be provided / instructed / configured with a second timing advance offset (e.g., The second timing advance offset is used to employ the timing advance offset corresponding to the serving cell. physCellId Different physCellId The transmission of spatial domain filters associated with the TCI state. The first timing advance offset and the second timing advance offset can correspond to the first TAG of the serving cell and the second TAG of the serving cell, respectively. The first TAG and the second TAG can have [characteristics / features]... tag-Id-ptr The indications are different from those of dl-OrJointTCI-StateList The first joint TCI state and the second joint TCI state provided or combined with those provided by ul - TCI-State-List The association between the first UL TCI status and the second UL TCI status is provided.

[0284] 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., ...) to the first and second uplink carriers. 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.

[0285] 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.

[0286] The radio 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 radio device can 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 radio device can, 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 radio device can, for example, base the timing advance command on the timing advance offset (e.g., 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.

[0287] for A subcarrier spacing (SCS) of kHz, for one or more TAGs, a timing advance command received by the radio device can be used. The multiple aspect indicates the change in uplink timing relative to the current uplink timing for the TAG.

[0288] The wireless device can receive a timing advance command for one or more tags in a tag (e.g., ).

[0289] 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., ...). ) indicates the timing advance value (e.g., Wireless devices can make SCS (Self-Service Class) The amount / quantity of the timing advance value (or time alignment) of the kHz TAG / for the TAG is determined / calculated / adjusted. 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.

[0290] In the example, the timing advance command MAC CE can indicate / include a timing advance command. The wireless device can receive the timing advance command within the timing advance command MAC CE. The timing advance command can be received via an index value (e.g., ...). Indicates the current timing advance value To the new timing advance value Adjustments. For With a kHz SCS, the wireless device can determine the new timing advance value as .

[0291] 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 the multiple uplink BWPs of the multiple uplink BWPs of the multiple uplink carriers of the at least one cell in the TAG (or may activate a corresponding uplink BWP of the multiple uplink BWPs of the multiple uplink carriers of the at least one cell in the TAG). 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.,) is used for the uplink BWP with the lower SCS among the multiple uplink BWPs. 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.

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

[0293] The wireless device can receive timing advance commands for one or more tags. A tag can include at least one cell from one or more cells. The wireless device can receive these commands in uplink time slots. The wireless device receives a timing advance command via the uplink. The wireless device can adjust the uplink transmission timing based on the timing advance command. The wireless device can apply the uplink transmission timing adjustment starting from the second uplink time slot. The wireless device can apply the uplink transmission timing adjustment for uplink signal transmission (e.g., PUSCH / PUSCH / SRS transmission). The wireless device can apply the uplink transmission timing adjustment for uplink signal transmission via at least one cell (or via the 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 can 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 the uplink time slot. ,in .For example, This can be the PDSCH processing time corresponding to UE processing capability 1 when the additional PDSCH DM-RS is configured (or indicated by one or more configuration parameters). The duration of each symbol in msec. For example, This could be corresponding to the PUSCH preparation time for UE processing capability 1. The duration of each symbol in msec. For example, This can be the maximum timing advance value in msecs that can be provided by the 12-bit TA command field. For example, This could be the number of time slots per subframe. For example, This could be a subframe duration of 1 msec. For example, In the example, one or more configuration parameters can indicate... (For example, provided by Koffset in ServingCellConfigCommon). In the example, one or more configuration parameters may not indicate the purpose of... The value (e.g., Koffset is not in ServingCellConfigCommon). Wireless devices may not indicate the value used based on one or more configuration parameters. The value determines the value used for The default value. For example, a wireless device can receive an instruction. The MACCE command. For example, a wireless device may not receive instructions for use. The value of the MAC CE command. The wireless device can use the absence of an indication for... The MAC CE command determines the value used for The default value. The wireless device can determine the minimum SCS among the SCS of all uplink BWP configurations for all uplink carriers used in at least one cell in the TAG and the SCS of all downlink BWP configurations for the corresponding downlink carriers (or for at least one cell). and .for Wireless devices can determine / assume The wireless device can determine the uplink slot based on the minimum SCS among all configured uplink BWPs for all uplink carriers used in at least one cell in the TAG. and The wireless device can determine the minimum SCS among all configurations of the uplink BWP relative to all uplink carriers for 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). Uplink time slot It can be a hypothesis The last uplink time slot that overlaps with the PDSCH reception time slot, wherein the PDSCH reception indicates / includes / provides a timing advance command.

[0294] The radio device can change the active uplink BWP of at least one cell in the 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 to the uplink transmission timing are applied. 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 timing advance value) based on the SCS of the new active UL BWP. 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.

[0295] 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., ).

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

[0297] A radio 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 configurations (e.g., tag-Config). TAG configurations may be used by the radio device and / or the base station to configure parameters for time alignment groups. TAG configurations may 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.).

[0298] 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.

[0299] 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., 500 ms, 750 ms, ..., 5120 ms, 10240 ms, 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.

[0300] 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.

[0301] In RRC_CONNECTED, the base station can maintain timing advance to keep the Layer 1 (L1) synchronization of the radio device. 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 TAG in 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).

[0302] 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.

[0303] 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.

[0304] If the wireless device uses an active downlink BWP that includes / includes the serving cell... coresetPoolIndex The higher-level parameter of CORESET with two different values PDCCH-Config Configuration / instruction, or if the wireless device is configured with higher-level parameters. SSB-MTC-AddtionalPCI And it is configured to include / include higher-level parameters. ControlResourceSet In coresetPoolIndex Two different values ​​of higher-level parameters PDCCH-Config And if the wireless device is configured with Two TAGs It is also configured with higher-layer parameters specific to the serving cell. dl- OrJointTCI-StateList or higher level parameters TCI-UL-State Then each TCI-State or TCI-UL-State It can be associated with the corresponding TAG in two TAGs of the serving cell, which are used to determine timing adjustments for the corresponding uplink transmission. Unless reported in the UE capability, the UE may not expect to interact with a... coresetPoolIndex Related TCI-states or TCI-UL-States This corresponds to two tags.

[0305] when timeAlignmentTimer Upon expiration: -if timeAlignmentTimer Associated with a PTAG and only one PTAG is configured for SpCell; or -if timeAlignmentTimerAssociated with a PTAG, and if the SpCell is configured with two PTAGs, and associated with another PTAG timeAlignmentTimer If not in operation, the wireless device can: ○ Refresh all HARQ buffers in all serving cells; ○ Notify RRC to release the PUCCH of all serving cells, if configured; ○ Notify RRC to release the SRS of all serving cells, if configured; ○ Clear any configured downlink assignments and configured uplink authorizations; ○ Remove any PUSCH resources used for semi-persistent CSI reporting; ○ All running timeAlignmentTimer It is considered due; -Otherwise, if timeAlignmentTimer If associated with STAG, it applies to all serving cells that only have this TAG configured; or -if timeAlignmentTimer If associated with a TAG, then for those TAGs configured with this TAG and another TAG and associated with that other TAG... timeAlignmentTimer In all serving cells that are not in operation, wireless devices can: ○ Refresh all HARQ buffers; ○ If configured, notify RRC to release PUCCH; ○ If configured, notify RRC to release SRS; ○ Clear any configured downlink assignments and configured uplink authorizations; ○ Remove any PUSCH resources used for semi-persistent CSI reporting; -Otherwise, if timeAlignmentTimer If associated with a TAG, then for those TAGs configured with this TAG and another TAG and associated with that other TAG... timeAlignmentTimer In all serving cells currently in operation, wireless devices can: ○ If the corresponding activated TCI state is associated with the TAG of an expired timeAlignmentTimer, then notify RRC to release the PUCCH. ○ If the corresponding activated TCI state is associated with the TAG of an expired timeAlignmentTimer, then notify RRC to release the SRS; ○ Clear any configured downlink assignments and configured uplink authorizations of the application that have a TCI state associated with the TAG of the expired timeAlignmentTimer; ○Clear the expired ones timeAlignmentTimerAny PUSCH resource associated with the TAG-related TCI state scheduling semi-persistent CSI report; Figure 17 Examples of several tags are shown for aspects of embodiments according to this disclosure.

[0306] In this example, the wireless device can receive one or more messages. In this example, the wireless device can receive one or more messages from a base station. The base station can transmit the one or more messages. In this example, the wireless device can receive one or more messages from a relay node. In this 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.). The one or more messages may include one or more configuration parameters (e.g., ...). Figure 17 (Configuration parameters in the file).

[0307] In the example, one or more configuration parameters can be one or more RRC configuration parameters. In the example, one or more configuration parameters can be one or more RRC reconfiguration parameters (e.g., RRCReconfiguration, reconfigurationWithSync ).

[0308] In the example, one or more messages can be one or more RRC messages. In the example, one or more messages can be one or more RRC reconfiguration messages (e.g., RRCReconfiguration, reconfigurationWithSync ).

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

[0310] The cell can be, for example, a serving cell. In the example, at least one of the configuration parameters can be cell-specific. In the example, the cell can be a primary cell (PCell). In the example, the cell can be, for example, a primary-secondary cell (PSCell). In the example, the cell can be a secondary cell (SCell). The cell can be a secondary cell configured with a PUCCH (e.g., a PUCCH SCell).

[0311] The cell can be, for example, a non-serving cell (or a neighboring cell). The cell can be, for example, a candidate cell for Layer 1 / Layer 2 triggered mobility (LTM). The cell's Physical Cell Index / Identifier (PCI) can be, for example, different from the PCI of the serving cell of the radio device.

[0312] In the example, the cell can be a special cell (SpCell). For dual connectivity (DC) operation, SpCell can refer to (or indicate) the PCell of the MCG or the PSCell of the SCG; otherwise, SpCell can refer to (or indicate) the PCell.

[0313] In the example, the cell could be the primary SCG cell (PSCell). For dual connectivity operation, when performing a synchronization reconfiguration procedure, the radio device can, for example, perform a random access procedure via the PSCell.

[0314] In the examples, a cell can be, for example, an unlicensed cell operating in an unlicensed frequency band. In the examples, a cell can be, for example, a licensed cell operating in a licensed frequency band. In the examples, a cell can operate in a first frequency range (FR1). For example, FR1 can include a frequency band below 6 GHz. In the examples, a cell can operate in a second frequency range (FR2). For example, FR2 can include a frequency band from 24 GHz to 52.6 GHz. In the examples, a cell can operate in a third frequency range (FR3). For example, FR3 can include a frequency band from 52.6 GHz to 71 GHz. For example, FR3 can include a frequency band starting at (or above) 52.6 GHz.

[0315] In the example, the radio 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 radio 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.

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

[0317] In the example, a cell may include multiple BWPs. One or more configuration parameters may indicate multiple BWPs for a cell. 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.

[0318] In the example, one of the multiple BWPs can be in an active state or an inactive state (or a deactivated state). In the example, when one or more downlink BWPs are active, the radio 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 are active, the radio device can receive PDSCH on / through / for the downlink BWP. In the example, when one or more downlink BWPs are inactive, the radio 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 are inactive, the radio 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 are inactive, the radio 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 is inactive, the radio device cannot receive PDSCH on / via / for the downlink BWP. When one or more downlink BWPs is inactive, the radio device may stop receiving PDSCH on / via / for the downlink BWP.

[0319] 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.

[0320] 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.

[0321] In the example, the radio device can activate one or more uplink BWPs of the cell. In the example, activating an uplink BWP can include the radio 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.

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

[0323] 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.

[0324] 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.

[0325] In the example, one or more configuration parameters can indicate two coreset pool indices for multiple coresets, including the first coreset pool index (e.g., CoresetPoolIndex = 0) and the second coreset pool index (e.g., CoresetPoolIndex= 1). One or more configuration parameters can indicate the first coreset pool index for one or more first coresets among multiple coresets. One or more configuration parameters can indicate the first coreset pool index for one or more second coresets among multiple coresets. One or more configuration parameters can indicate the corresponding coreset pool index among two coreset pool indices for each coreset among multiple coresets.

[0326] One or more configuration parameters can indicate two tags for a cell. These two tags include the first tag (e.g., Figure 17 TAG 1) and the second TAG (e.g., Figure 17 (TAG 2 in the text).

[0327] One or more configuration parameters may include an indication / identification of the first TAG of two TAGs (e.g., TAG-Id One or more configuration parameters may include a second TAG index / identifier / identity that indicates / identifies the second TAG in two TAGs (e.g., TAG-Id2 ).

[0328] The first tag can be, for example, the first primary tag (PTAG). The first tag can also be, for example, the first secondary tag (STAG).

[0329] The second tag can be, for example, the second PTAG. The second tag can be, for example, the second STAG.

[0330] One or more configuration parameters can indicate the first time alignment timer for the first TAG (e.g., Figure 17 The first time alignment timer controls the duration for which the MAC entity of the radio device considers cells in the first tag (or belonging to or associated with the first tag) as having uplink time alignment for the first tag.

[0331] One or more configuration parameters can indicate a second time-aligned timer for the second TAG (e.g., Figure 17 (TAT 2 in the text). The second time alignment timer can control the duration for which the MAC entity of the radio device considers cells in the second TAG (or belonging to or associated with the second TAG) as having uplink time alignment for the second TAG.

[0332] One or more configuration parameters can indicate multiple TCI states for a cell. These parameters may include a TCI state list parameter indicating a list of TCI states (e.g., parameters from higher layers, such as RRC).dl-OrJoint- TCIStateList Provided). The TCI status list may include multiple TCI states. One or more configuration parameters may include one or more PDSCH configuration parameters (e.g., PDSCH-Config For example, it includes a TCI state list parameter indicating multiple TCI states. For example, the multiple TCI states in the TCI state list can be TCI state 1, ..., TCI state M.

[0333] One or more configuration parameters can indicate multiple TCI state indices / identities for multiple TCI states (e.g., TCI-StateId One or more configuration parameters can indicate a corresponding TCI state index in a plurality of TCI state indices for each TCI state among a plurality of TCI states. Each TCI state among a plurality of TCI states can be indicated / identified by a corresponding TCI state index in a plurality of TCI state indices. For example, one or more configuration parameters can indicate a first TCI state index in a plurality of TCI state indices for a first TCI state among a plurality of TCI states. One or more configuration parameters can indicate a second TCI state index in a plurality of TCI state indices for a second TCI state among a plurality of TCI states.

[0334] One or more configuration parameters can indicate multiple TCI states, which in turn indicate a unified TCI state for the cell.

[0335] One or more configuration parameters may include one or more PDSCH configuration parameters, for example, for / about the cell's downlink BWP (e.g., active downlink BWP). One or more configuration parameters indicate multiple TCI states of the cell's downlink BWP.

[0336] 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 cells may include a second cell. One or more configuration parameters indicate multiple TCI states of the second downlink BWP of the second cell. One or more configuration parameters may include, for / about the downlink BWP of the cell, parameters referencing a unified TCI state list (e.g., ...). unifiedTCI-StateRef This indicates the second downlink BWP of the second cell. Reference to the Unified TCI status list parameters may include a BWP index (e.g., BWP-Id) that identifies / indicates the second downlink BWP. Reference to the Unified TCI status list parameters may include a cell index (e.g., cell index) that identifies / indicates the second cell. ServCellIndexThe second downlink BWP of the second cell can be a reference BWP of a reference cell for the downlink BWP of the second cell. The downlink BWP of the cell can be a target BWP of the target cell. For example, the downlink BWP of the cell may include reference unified TCI state list parameters based on one or more configuration parameters, and one or more PDSCH configuration parameters of the downlink BWP of the cell may not include higher-layer (e.g., RRC) parameters. dl-OrJoint-TCIStateList .

[0337] One or more configuration parameters may include a uniform TCI status type parameter (e.g., unifiedtci- StateType One or more configuration parameters may include one or more serving cell parameters (e.g., ServingCellConfig ), which includes the Uniform TCI State Type Parameter (e.g., Figure 17 In UnifiedTCI- StateType The Unified TCI Status Type parameter can indicate the cell-level / cell-specific Unified TCI Status Type.

[0338] For example, the unified TCI state type for a cell / cell can be "Unified". The value of the unified TCI state type parameter can be set to "Unified". For example, based on one or more configuration parameters including a unified TCI state type parameter set to "Unified", a wireless device can use / apply multiple TCI states for both (e.g., by...). dl-OrJoint- TCIStateList Provided / Indicated: Uplink transmissions occurring in / via the cell (e.g., PUSCH / PUCCH / SRS transmissions) and downlink receptions occurring in / via the cell (e.g., PDCCH / PDSCH / CSI-RS receptions). For example, when the Unified TCI State Type parameter is set to "Unified", multiple TCI states can be multiple Unified TCI states (or can be used interchangeably with multiple Unified TCI states).

[0339] When the unified TCI status type parameter is set to "joint", one or more configuration parameters can indicate the corresponding TAG in the two TAGs of the cell for each TCI status in multiple TCI statuses (or multiple joint TCI statuses).

[0340] When the unified TCI state type parameter is set to "Unified", one or more configuration parameters for each TCI state in multiple TCI states include / indicate the TAG index / identifier / identity pointer of the corresponding TAG in the two TAGs indicating the cell (e.g., tag-Id-ptr ).

[0341] For example, the first value (e.g., 0) of the TAG index / identifier / identity pointer can indicate the value of the first TAG index / identifier / identity (e.g., TAG-Id The first TAG indicates / identifies the user. The second value (e.g., 1) of the TAG index / identifier / identity pointer can indicate the first TAG index / identifier / identity (e.g., ...). TAG-Id2 The second tag that indicates / identifies.

[0342] For example, the cell-specific / cell-specific unified TCI status type can be "Separate". The value of the unified TCI status type parameter can be set to "Separate" (e.g., Figure 17 In UnifiedTCI-StateType = {Separate}). For example, based on one or more configuration parameters including a unified TCI state type parameter set to "Separate", a wireless device can use / apply multiple TCI states for the following (e.g., by higher-level parameters). dl-OrJoint-TCIStateList Provided / Indicated: Downlink reception occurring in / via the cell (e.g., PDCCH / PDSCH / CSI-RS reception). For example, based on one or more configuration parameters including a unified TCI state type parameter set to "Separate", the radio device may not be able to use / apply multiple TCI states for: uplink transmissions occurring in / via the cell (e.g., PUSCH / PUCCH / SRS transmissions). For example, when the unified TCI state type parameter is set to "Separate", multiple TCI states can be multiple downlink TCI states (or can be used interchangeably with multiple downlink TCI states). Figure 17 In the process, multiple TCI states are DL TCI state 1, DL TCI state 2, ..., DL TCI state M.

[0343] One or more configuration parameters can indicate a second or more TCI states. One or more configuration parameters may include an uplink TCI state list parameter indicating a list of uplink TCI states (e.g., determined by higher-layer parameters). ul-TCI- StateList (Provided / Indicated). The uplink TCI status list may include a second or more TCI statuses. One or more configuration parameters may include one or more uplink BWP configuration parameters, which include an uplink TCI status list parameter indicating the second or more TCI statuses.

[0344] For example, for a cell's uplink BWP (e.g., an active uplink BWP), one or more configuration parameters may include one or more uplink BWP configuration parameters. One or more configuration parameters indicate a second or more TCI states for the cell's uplink BWP.

[0345] 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 configuration parameters may include, for the uplink BWP of a cell, a reference unified TCI state list parameter indicating the second uplink BWP of the second cell (e.g., unifiedtci-StateType The parameters in the unified TCI status list can include the BWP index (e.g., BWP-Id) that identifies / indicates the second uplink BWP. The parameters in the unified TCI status list can also include the cell index (e.g., cell index) that identifies / indicates the second cell. ServCellIndex The second uplink BWP for the second cell can be a reference BWP for a reference cell of the cell's uplink BWP. The cell's uplink BWP can be a target BWP for the target cell. For example, while the cell's uplink BWP may include reference unified TCI status list parameters based on one or more configuration parameters, one or more uplink BWP configuration parameters for the cell's uplink BWP may not include higher-layer (e.g., RRC) parameters. ul-TCI-StateList .

[0346] For example, based on one or more configuration parameters including a unified TCI state type parameter set to "Separate", the radio device can use / apply a second multiple TCI state for: uplink transmissions occurring in / via the cell (e.g., PUSCH / PUCCH / SRS transmissions). For example, based on one or more configuration parameters including a unified TCI state type parameter set to "Separate", the radio device may not be able to use / apply a second multiple TCI state for: downlink receptions occurring in / via the cell (e.g., PDCCH / PDSCH / CSI-RS receptions). For example, when the unified TCI state type parameter is set to "Separate", the second multiple TCI state can be multiple uplink TCI states (or can be used interchangeably with multiple uplink TCI states). Figure 17 In the middle, the second multiple TCI states are UL TCI state 1, UL TCI state 2, ..., UL TCI state N.

[0347] When the unified TCI status type parameter is set to "separate", one or more configuration parameters can indicate the corresponding TAG in the two TAGs of the cell for each TCI status in the second or more TCI statuses (or multiple uplink TCI statuses).

[0348] When the unified TCI status type parameter is set to "separate", one or more configuration parameters for each TCI status in the second plurality of TCI statuses include / indicate the TAG index / identifier / identity pointer of the corresponding TAG in the two TAGs indicating the cell (e.g., tag-Id-ptr , Figure 17 (Tag-Id-ptr in the text).

[0349] For example, the first value (e.g., 0) of the TAG index / identifier / identity pointer can indicate the value of the first TAG index / identifier / identity (e.g., TAG-Id The first TAG indicates / identifies the user. The second value (e.g., 1) of the TAG index / identifier / identity pointer can indicate the first TAG index / identifier / identity (e.g., ...). TAG-Id2 The second tag that indicates / identifies.

[0350] When the Uniform TCI State Type parameter is set to "Decoupled", one or more configuration parameters for each / any TCI state in multiple TCI states (or multiple downlink TCI states) do not include / indicate a TAG index / identifier / identity pointer (e.g., tag-Id-ptr ).

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

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

[0353] 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 radio device can use multiple TCI states of the second downlink BWP of the second cell for downlink reception via the cell's downlink BWP.

[0354] 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 radio device can receive multiple TCI states using the second downlink BWP of the second cell for uplink transmission via the uplink BWP of the cell.

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

[0356] 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 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.

[0357] A cell can be served by multiple TRPs, including a first TRP and a second TRP. Wireless devices can be served by multiple TRPs via the cell.

[0358] The radio device can receive a first downlink reception (e.g., PDSCH, PDCCH, CSI-RS) from a first TRP via a cell. The first TRP can transmit the first downlink reception to the radio device. The radio device can receive a second downlink reception (e.g., PDSCH, PDCCH, CSI-RS) from a second TRP via a cell. The second TRP can transmit the second downlink reception to the radio device.

[0359] The radio device can transmit a first uplink transmission (e.g., PUSCH, PUCCH, SRS) to a first TRP via a cell. The first TRP can receive the first uplink transmission from the radio device. The radio device can transmit a second uplink transmission (e.g., PUSCH, PUCCH, SRS) to a second TRP via a cell. The second TRP can receive the second uplink transmission from the radio device.

[0360] In the example, the wireless device may receive one or more activation commands (e.g., MAC-CE, DCI, RRC, one or more control commands, one or more downlink control commands / messages, one or more control commands / messages, unified TCI state activation / deactivation MAC CE, enhanced unified TCI state activation / deactivation MAC CE, enhanced unified TCI state activation / deactivation MAC-CE for joint TCI state mode, enhanced unified TCI state activation / deactivation MAC-CE for separate TCI state mode, etc.).

[0361] For example, when one or more configuration parameters do not indicate two distinct values ​​for the coreset pool index of the coreset in the cell's downlink BWP, one or more activation commands can be an activation command (or a single activation command or one activation command). One or more configuration parameters may not include / include different coresets that include / include the cell's downlink BWP (e.g., ControlResourceSets Higher-level parameters in ) CORESETPoolIndex One or more PDCCH configuration parameters with two different values ​​(e.g., PDCCH-Config ).

[0362] For example, when one or more configuration parameters indicate two distinct values ​​for the coreset pool index of the coreset in the downlink BWP for a cell, the one or more activation commands can be at least two activation commands. One or more configuration parameters can include different coresets that contain / include the downlink BWP of the cell (e.g., ControlResourceSets Higher-level parameters in ) CORESETPoolIndex One or more PDCCH configuration parameters with two different values ​​(e.g., PDCCH-Config At least two activation commands can include a first activation command and a second activation command.

[0363] For example, one or more activation commands can indicate multiple TCI states (e.g., DLorJoint- TCIStateList The activation of a subset of TCI states in ( ). The subset of TCI states can be, for example, a subset of joint TCI states from multiple joint TCI states. The subset of TCI states can be, for example, a subset of downlink TCI states from multiple downlink TCI states.

[0364] For example, one or more activation commands can indicate a second or more TCI states (e.g., ul-TCI- StateList Activation of a subset of TCI states in ). The subset of TCI states can be, for example, a subset of uplink TCI states from multiple uplink TCI states.

[0365] When one or more configuration parameters include / include different coresets (e.g., ControlResourceSets Higher-level parameters in ) CORESETPoolIndex One or more PDCCH configuration parameters with two different values ​​(e.g., PDCCH-Config When this occurs, the TCI state subset may include the index of the first coreset pool (e.g., CoresetPoolIndex= 0) associated with one or more first TCI states and with the second coreset pool index (e.g., CoresetPoolIndex = 1) One or more associated second TCI states. For example, the first activation command in one or more activation commands could indicate an activation of the index for the first coreset pool (e.g., CoresetPoolIndex The first activation command may include the activation of one or more first TCI states (equal to 0). The first activation command may include a field set to a first coreset pool index. One or more first TCI states may be for (or associated with) a first TRP. The first activation command may instruct / activate one or more first TCI states for a first coreset pool index equal to zero. One or more first TCI states may be associated with (or correspond to) a first coreset pool index equal to zero. The radio device may, for example, receive downlink reception associated with a first coreset pool index based on one or more first TCI states. The radio device may, for example, transmit uplink transmissions associated with a first coreset pool index based on one or more first TCI states.

[0366] For example, a second activation command in one or more activation commands could instruct an index targeting a second coreset pool (e.g., CoresetPoolIndex The activation of one or more second TCI states equal to 1. The second activation command may include a field set to a second coreset pool index. One or more second TCI states may be for (or associated with) a second TRP. The second activation command may instruct / activate one or more second TCI states for a second coreset pool index equal to 1. One or more second TCI states may be associated with (or correspond to) a second coreset pool index equal to 1. The radio device may, for example, receive downlink reception associated with a second coreset pool index based on one or more second TCI states. The radio device may, for example, transmit uplink transmission associated with a second coreset pool index based on one or more second TCI states.

[0367] The base station can activate and / or deactivate a subset of TCI states, for example, by sending / transmitting one or more activation commands.

[0368] A radio device can map a subset of TCI states to one or more TCI code points for a cell. One or more activation commands can indicate the mapping of a subset of TCI states to one or more TCI code points. A radio device can map a corresponding TCI state in a subset of TCI states to a corresponding TCI code point in one or more TCI code points. One or more TCI code points can indicate / include a subset of TCI states. Each TCI code point in one or more TCI code points can indicate (or can be mapped to) a corresponding TCI state in a subset of TCI states. Each TCI code point in one or more TCI code points can indicate / include (or map to) one or more TCI states.

[0369] For example, one or more TCI code points can be TCI code point 000, TCI code point 001, ..., TCI code point 110, TCI code point 111. A subset of TCI states includes TCI state 4, TCI state 5, TCI state 8, ..., TCI state 26 and TCI state 61. TCI code point 000 can include / indicate (or can be mapped to) TCI state 4. TCI code point 001 can include / indicate (or can be mapped to) TCI state 5 and TCI state 8. TCI code point 110 can include / indicate (or can be mapped to) TCI state 26. TCI code point 111 can include / indicate (or can be mapped to) TCI state 26 and TCI state 61. For example, TCI code points 000 and 110 can indicate a single TCI state (e.g., a single combined TCI state, a single downlink TCI state, a single uplink TCI state, etc.). TCI code point 001 and TCI code point 111 indicate two TCI states (e.g., two joint TCI states, two uplink TCI states, two downlink TCI states, etc.).

[0370] When one or more configuration parameters include / include different coresets (e.g., ControlResourceSets Higher-level parameters in ) CORESETPoolIndex One or more PDCCH configuration parameters with two different values ​​(e.g., PDCCH-ConfigWhen a first activation command is executed, the wireless device may map one or more first TCI states to one or more first TCI code points. One or more TCI code points may include one or more first TCI code points. The first activation command may indicate the mapping of one or more first TCI states to one or more first TCI code points. The wireless device may map each of the one or more first TCI states to a corresponding TCI code point among the one or more first TCI code points. One or more first TCI code points may indicate / include one or more first TCI states. Each of the one or more first TCI code points may indicate (or may be mapped to) a corresponding TCI state among the one or more first TCI states. Each of the one or more first TCI code points may indicate / include (or be mapped to) a TCI state.

[0371] In the example, one or more first TCI states can be TCI state 4, TCI state 5, TCI state 26, and TCI state 49. One or more first TCI code points can be or can include a first TCI code point (e.g., TCI code point 000), a second TCI code point (e.g., TCI code point 001), a third TCI code point (e.g., TCI code point 010), and a fourth TCI code point (e.g., TCI code point 011). A first TCI code point (e.g., TCI code point 000) can include / indicate TCI state 4. A second TCI code point (e.g., TCI code point 001) can include / indicate TCI state 5. A third TCI code point (e.g., TCI code point 010) can include / indicate TCI state 26. A fourth TCI code point (e.g., TCI code point 011) can include / indicate TCI state 49. For example, each TCI code point in one or more first TCI code points can indicate a single TCI state (e.g., a joint TCI state, an uplink TCI state, a downlink TCI state, etc.). The first activation command can be / can include a coreset pool index field set to zero / equal to zero (e.g., CoresetPoolIndex = 0).

[0372] When one or more configuration parameters include / include different coresets (e.g., ControlResourceSets Higher-level parameters in ) CORESETPoolIndex One or more PDCCH configuration parameters with two different values ​​(e.g., PDCCH-ConfigWhen a second activation command is executed, the wireless device may map one or more second TCI states to one or more second TCI code points. One or more TCI code points may include one or more second TCI code points. The second activation command may indicate the mapping of one or more second TCI states to one or more second TCI code points. The wireless device may map each of the one or more second TCI states to a corresponding TCI code point among the one or more second TCI code points. One or more second TCI code points may indicate / include one or more second TCI states. Each of the one or more second TCI code points may indicate (or be mapped to) a corresponding TCI state among the one or more second TCI states. Each of the one or more second TCI code points may indicate / include (or be mapped to) a TCI state.

[0373] In the example, one or more second TCI states can be TCI state 8, TCI state 14, TCI state 33, and TCI state 61. One or more second TCI code points can include a first TCI code point (e.g., TCI code point 000), a second TCI code point (e.g., TCI code point 001), a third TCI code point (e.g., TCI code point 010), and a fourth TCI code point (e.g., TCI code point 011). The first TCI code point (e.g., TCI code point 000) can include / indicate TCI state 8. The second TCI code point (e.g., TCI code point 001) can include / indicate TCI state 14. The third TCI code point (e.g., TCI code point 010) can include / indicate TCI state 33. The fourth TCI code point (e.g., TCI code point 011) can include / indicate TCI state 61. For example, each of one or more second TCI code points can indicate a single TCI state (e.g., a joint TCI state, an uplink TCI state, a downlink TCI state, etc.).

[0374] A wireless device can receive one or more control commands.

[0375] In the example, one or more control commands can be a single control command (or a single control command). For example, one or more control commands can be a single control command when one or more configuration parameters do not indicate two distinct values ​​for the coreset pool index of the coreset in the downlink BWP for the cell. One or more configuration parameters may not include different coresets that include / include the downlink BWP of the cell (e.g., ControlResourceSets Higher-level parameters in ) CORESETPoolIndexOne or more PDCCH configuration parameters with two different values ​​(e.g., PDCCH-Config ).

[0376] Control commands can be, for example, MAC-CE. Control commands can be, for example, DCI (e.g., DCI format 1_2 / 1_2). Control commands can be, for example, downlink control commands (e.g., activation commands).

[0377] Control commands can indicate at least two TCI states from a subset of TCI states for a cell. The at least two TCI states can include a first TCI state and a second TCI state. The first TCI state can be for (or associated with) a first TRP. The second TCI state can be for (or associated with) a second TRP. In the example, one or more configuration parameters can include downlink or joint TCI state parameters for the cell / cell (e.g., dl-OrJointTCI-StateList A list of ( ). For example, a wireless device may have at least two TCI states for a cell, based on control commands indicating at least two TCI states for that cell.

[0378] In the example, for downlink receptions occurring via the cell (e.g., PDCCH, PDSCH, CSI-RS), the control command can indicate at least two TCI states.

[0379] In the example, for uplink transmissions occurring via the cell (e.g., PUCCH, PUSCH, SRS), the control command can indicate at least two TCI states.

[0380] In the example, the number of one or more TCI code points can be equal to one (e.g., a single TCI code point). A single TCI code point can indicate at least two TCI states. For example, based on the fact that the number of one or more TCI code points is equal to one, a control command indicating at least two TCI states can be an activation command that activates a subset of TCI states. For example, based on the fact that the number of one or more TCI code points is equal to one, at least two TCI states can be a subset of TCI states. Based on the fact that the number of one or more TCI code points is equal to one, an activation command can indicate at least two TCI states. The control command can be, for example, MAC-CE.

[0381] In the example, the number of one or more TCI code points can be greater than one. For example, based on the fact that the number of one or more TCI code points is greater than one, a control command indicating at least two TCI states can be different from an activation command activating a subset of TCI states. The wireless device can receive the control command after receiving the activation command. The control command can be, for example, a DCI (e.g., DCI format 1_2 / 1_2). The control command (e.g., DCI format 1_1 / 1_2) can include a TCI field indicating at least two TCI states. The value of the TCI field (e.g., "111") can be equal to the TCI code point (e.g., TCI code point 111) among one or more TCI code points that indicates at least two TCI states (e.g., TCI state 26 and TCI state 61). The control command can indicate TCI code points for TCI fields. At least two TCI states can be mapped to TCI code points.

[0382] In the example, one or more control commands can be at least two control commands. For instance, when one or more configuration parameters indicate two distinct values ​​for the coreset pool index of the coreset in the downlink BWP for a cell, one or more control commands can be at least two control commands. One or more configuration parameters can include different coresets that include / include the downlink BWP of the cell (e.g., ControlResourceSets Higher-level parameters in ) CORESETPoolIndex One or more PDCCH configuration parameters with two different values ​​(e.g., PDCCH-Config At least two control commands may include a first control command and a control command.

[0383] The first control command can be, for example, a first MAC-CE. The first control command can be, for example, a first DCI (e.g., DCI format 1_1, DCI format 1_2). The first control command can be, for example, a first downlink control command (e.g., an activation command). The second control command can be, for example, a second MAC-CE. The second control command can be, for example, a second DCI (e.g., DCI format 1_1, DCI format 1_2). The second control command can be, for example, a second downlink control command (e.g., an activation command).

[0384] One or more control commands (or at least two control commands) can indicate at least two TCI states in a subset of TCI states. The at least two TCI states can include a first TCI state and a second TCI state.

[0385] The first control command can indicate the first TCI state in at least two TCI states. One or more first TCI states associated with the first coreset pool index can include the first TCI state. The first TCI state can be associated with a higher-level parameter having a value of 0.coresetPoolIndex The first TCI state can be associated with (or specific to or belonging to) the higher-layer parameters. It can be directed to (or associated with) the first TRP. For example, based on receiving a first control command (e.g., DCI) via a first coreset with a first coreset pool index, the first TCI state can be associated with the first coreset pool index. Multiple coresets of the downlink BWP can include the first coreset. One or more configuration parameters can indicate the first coreset pool index for the first coreset. The radio device can, for example, receive downlink reception associated with the first coreset pool index based on the first TCI state. The radio device can, for example, transmit uplink transmissions associated with the first coreset pool index based on the first TCI state.

[0386] The second control command can indicate a second TCI state in at least two TCI states. One or more second TCI states associated with a second coreset pool index can include the second TCI state. The second TCI state can be associated with a higher-level parameter having a value of 1. coresetPoolIndex The second TCI state can be associated with (or specific to or belonging to) the higher-layer parameters. It can be directed to (or associated with) the second TRP. For example, based on receiving a second control command (e.g., DCI) via a second coreset with a second coreset pool index, the second TCI state can be associated with the second coreset pool index. Multiple coresets of the downlink BWP can include the second coreset. One or more configuration parameters can indicate the second coreset pool index for the second coreset. The radio device can, for example, receive downlink reception associated with the second coreset pool index based on the second TCI state. The radio device can, for example, transmit uplink transmissions associated with the second coreset pool index based on the second TCI state.

[0387] In the example, the number of one or more first TCI code points can be equal to one (e.g., a single TCI code point). A single TCI code point can indicate a first TCI state. Based on the fact that the number of one or more first TCI code points is equal to one, a first control command indicating a first TCI state can be a first activation command that activates one or more first TCI states. Based on the fact that the number of one or more first TCI code points is equal to one, a first TCI state can be one or more first TCI states. Based on the fact that the number of one or more first TCI code points is equal to one, a first activation command can indicate a first TCI state.

[0388] In the example, the number of one or more first TCI code points can be greater than one. Based on the fact that the number of one or more first TCI code points is greater than one, the first control command indicating the first TCI state can be different from the first activation command activating one or more first TCI states. The wireless device can receive the first control command after receiving the first activation command. The first control command (e.g., DCI) may include a TCI field indicating the first TCI state. The value of the TCI field can be equal to the first TCI code point indicating the first TCI state among the one or more first TCI code points. The first TCI state can be mapped to the first TCI code points.

[0389] In the example, the number of one or more second TCI code points can be equal to one (e.g., a single TCI code point). A single TCI code point can indicate a second TCI state. Based on the fact that the number of one or more second TCI code points is equal to one, a second control command indicating a second TCI state can be a second activation command that activates one or more second TCI states. Based on the fact that the number of one or more second TCI code points is equal to one, a second TCI state can be one or more second TCI states. Based on the fact that the number of one or more second TCI code points is equal to one, a second activation command can indicate a second TCI state.

[0390] In the example, the number of one or more second TCI code points can be greater than one. Based on the fact that the number of one or more second TCI code points is greater than one, a second control command indicating a second TCI state can be a second activation command activating one or more second TCI states. The wireless device can receive the second control command after receiving the second activation command. The second control command (e.g., DCI) can include a TCI field indicating a second TCI state. The value of the TCI field can be equal to the second TCI code point indicating the second TCI state among one or more second TCI code points. The second TCI state can be mapped to second TCI code points.

[0391] At least two TCI states can be, for example, at least two joint TCI states. At least two TCI states can be, for example, at least two downlink TCI states.

[0392] At least two TCI states can be, for example, at least two uplink TCI states.

[0393] 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).

[0394] 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).

[0395] When the unified TCI state type parameter is set to "unified", the first TCI state is the first unified TCI state, and the second TCI state is the second unified TCI state.

[0396] When the unified TCI state type parameter is set to "Separate", the first TCI state includes / is the first downlink TCI state and the first uplink TCI state. When the unified TCI state type parameter is set to "Separate", the second TCI state includes / is the second downlink TCI state and the second uplink TCI state.

[0397] One or more configuration parameters may include instructions for / targeting / belonging to / configuring SPS configurations (e.g., Figure 17 One or more SPS configuration parameters in the SPS configuration (e.g., SPS-Config ).

[0398] The wireless device can receive / detect DCI indicating activation of the SPS configuration via the first coreset (e.g., Figure 17 DCI in (the context of DCI).

[0399] The multiple coresets may include the first coreset.

[0400] In the example, a first coreset can be associated with a first coreset pool index. For example, a first coreset can be associated with a first coreset pool index based on one or more configuration parameters that indicate the first coreset pool index. For example, a coreset may include a coreset pool index parameter with a value indicating the first coreset pool index based on one or more configuration parameters (e.g., ...). CoresetPoolIndex The first coreset can be associated with the first coreset pool index. For example, a coreset can be configured based on one or more configuration parameters that do not include the coreset pool index parameter (e.g., ...). CoresetPoolIndex The first coreset can be associated with the first coreset pool index.

[0401] The DCI may include one or more fields (e.g., RV, HARQ process, MCS, etc.) that are set to predefined values ​​(e.g., 0, 1) indicating activation of the SPS configuration. The wireless device may verify the DCI based on the predefined values ​​of one or more fields (e.g., RV, HARQ process, MCS, etc.). The wireless device may activate the SPS configuration based on the verified DCI.

[0402] SPS configuration can indicate, for example, the configured downlink assignment for PDSCH reception with SPS configuration. Configured downlink assignment can indicate the resources used for PDSCH reception with SPS configuration.

[0403] Configurable downlink assignment can be configured downlink authorization (or can be used interchangeably with configured downlink authorization).

[0404] The wireless device can apply a first TCI state to the PDSCH reception configured by the SPS. The wireless device can receive the PDSCH reception configured by the SPS based on (or using) the first TCI state. At least one DM-RS port of the PDSCH reception can be quasi-co-located with a first reference signal indicated by the first TCI state. At least one DM-RS port of the PDSCH reception can be quasi-co-located with the first reference signal relative to the first quasi-co-location type indicated by the first TCI state.

[0405] The wireless device may, for example, receive the PDSCH of the SPS configuration based on (or using) the first TCI state in response to receiving a DCI indicating activation of the SPS configuration via a first coreset having a first coreset pool index.

[0406] The wireless device may, for example, receive a PDSCH reception of the SPS configuration based on (or using) the first TCI state, in response to receiving a DCI indicating activation of the SPS configuration via a first coreset having a first coreset pool index associated with the first TCI state.

[0407] The wireless device may, for example, receive PDSCH based on (or using) the first TCI state in response to an indication of activation of the DCI for the SPS configuration, which includes a TCI selection field having a value indicating the first TCI state.

[0408] In the example, the first time alignment timer for the first tag may have expired (or may not be running). The second time alignment timer for the second tag may be running (or may not have expired). When the first time alignment timer for the first tag expires, the second time alignment timer for the second tag may be running. When the second time alignment timer for the second tag is running, the first time alignment timer for the first tag may have expired.

[0409] The wireless device can, for example, clear the configured downlink assignment of the SPS configuration based on the expiration of the first time alignment timer of the first TAG.

[0410] When the first time alignment timer for the first tag of a cell expires, the radio device can clear the configured downlink assignment in the SPS configuration of the cell while the second time alignment timer for the second tag is running.

[0411] When the value of the unified TCI state type parameter in the cell is set to "Unified", the first TCI state applied to the SPS configuration (or the configured downlink assignment of the SPS configuration) can be the first unified TCI state. The first unified TCI state can be associated with a first TAG. One or more configuration parameters can indicate the first TAG of two TAGs in the cell for the first unified TCI state. One or more configuration parameters for the first unified TCI state include / indicate a TAG index / identifier / identity pointer that indicates the first TAG (e.g., tag-Id to ptr For example, a TAG index / identifier / identity pointer can be set to indicate the first TAG index / identifier / identity (e.g., TAG-Id The first value of the first tag that indicates / identifies (e.g., 0).

[0412] For example, a radio device can clear the configured downlink assignment of the SPS configuration based on the expiration of a first time alignment timer for a first TAG associated with a first joint TCI state applied to the SPS configuration.

[0413] For example, based on the association of a first joint TCI state with a first TAG having / having an expired first time alignment timer, the radio device can clear the configured downlink assignment with the SPS configuration applied to the first joint TCI state. For example, based on the value of the uniform TCI state type parameter of the cell being set to "joint", the radio device can clear the configured downlink assignment with the SPS configuration applied to the first joint TCI state.

[0414] When the value of the uniform TCI state type parameter in the cell is set to "separate", the first TCI state applied to the SPS configuration (or the configured downlink assignment of the SPS configuration) can be the first downlink TCI state (e.g., Figure 17 The first downlink TCI state (in the cell). The first downlink TCI state may not be associated with any of the two TAGs of the cell. One or more configuration parameters may be used for the first downlink TCI state that do not indicate the TAGs of the cell. For the first downlink TCI state, one or more configuration parameters do not include / indicate the TAG index / identifier / identity pointer that indicates the TAGs of the cell (e.g., tag-Id-ptr ).

[0415] One or more SPS configuration parameters may include PUCCH resources that indicate / identify the HARQ-ACK feedback transmission for PDSCH reception used in the SPS configuration (e.g., Figure 17 The PUCCH resource parameters (e.g., in the PUCCH resource) of the PUCCH resource. n1PUCCH-AN, n1PUCCH-AN-PUCCHsSCell, PUCCH-ResourceId ).

[0416] When the value of the uniform TCI state type parameter of the cell / cell is set to "separate", the radio device can apply the first uplink TCI state to the PUCCH resource. The radio device can transmit uplink transmissions (e.g., PUCCH transmissions, uplink control information, HARQ-ACK feedback, etc.) via the PUCCH resource based on (or using) the first uplink TCI state.

[0417] For example, based on one or more configuration parameters, the PUCCH resource indicates / including the application-indicated TCI state parameter (e.g., 0, "first") having a value indicating a first uplink TCI state. applyIndicatedTCIState) The wireless device can apply the first uplink TCI state to the PUCCH resource.

[0418] The first uplink TCI state can be associated with the first TAG. One or more configuration parameters can indicate the first TAG of the two TAGs in the cell for the first uplink TCI state. For the first uplink TCI state, one or more configuration parameters include / indicate the TAG index / identifier / identity pointer that indicates the first TAG (e.g., tag-Id-ptr For example, a TAG index / identifier / identity pointer can be set to indicate the first TAG index / identifier / identity (e.g., TAG- Id The first value of the first tag that indicates / identifies (e.g., 0).

[0419] The wireless device can, for example, clear the configured downlink assignment of the SPS configuration based on the expiration of a first time alignment timer for a first TAG associated with the first uplink TCI state of the PUCCH resource applied to the SPS configuration.

[0420] For example, based on the association of the first uplink TCI state with a first TAG having / having an expired first time alignment timer, the radio device can clear the configured downlink assignment with PUCCH resources applied to the SPS configuration. For example, based on the value of the uniform TCI state type parameter of the cell being set to "separate", the radio device can clear the configured downlink assignment with PUCCH resources applied to the first uplink TCI state.

[0421] For example, based on one or more configuration parameters, including feedback mode parameters set to "detach" (e.g., ackNackFeedbackMode The radio device can clear the configured downlink assignment with PUCCH resources having the first uplink TCI state applied in the SPS configuration. The feedback mode parameter set to "Separate" can indicate separate / independent ACK / NACK feedback for two TRPs. The feedback mode parameter set to "Separate" can indicate separate ACK / NACK feedback for two coreset pool indices. The feedback mode parameter set to "Separate" can indicate separate ACK / NACK feedback for downlink receptions (e.g., PDSCH reception, PDCCH reception) associated with two coreset pool indices. For example, when the feedback mode parameter is set to "Separate," the radio device may not multiplex / transmit the first HARQ-ACK feedback associated with the first coreset pool index (e.g., the first TRP) and the second HARQ-ACK feedback associated with the second coreset pool index (e.g., the second TRP) in the HARQ-ACK codebook.

[0422] One or more SPS configuration parameters can include a TAG index / identifier / identity pointer (e.g., Figure 17 In the SPS configuration tag-Id-ptr, Tag-Id-ptr). The first value (e.g., 0) of the TAG index / identifier / identity pointer configured in SPS can indicate the value of the first TAG index / identifier / identity (e.g., TAG-Id The first TAG indicates / identifies the user. The second value (e.g., 1) of the SPS-configured TAG index / identifier / identity pointer can indicate the first TAG index / identifier / identity (e.g., ...). TAG-Id2 The second tag that indicates / identifies.

[0423] SPS configuration can be associated with the first TAG. One or more configuration parameters can be used to indicate the first TAG of two TAGs in the cell for the SPS configuration. For the first uplink TCI state, one or more configuration parameters include / indicate the TAG index / identifier / identity pointer that indicates the first TAG (e.g., tag-Id-ptr For example, a TAG index / identifier / identity pointer can be set to indicate the first TAG index / identifier / identity (e.g., TAG-Id The first value of the first tag that indicates / identifies (e.g., 0).

[0424] For example, based on one or more configuration parameters indicating two TAGs for a cell, one or more SPS configuration parameters in the SPS configuration may include TAG index / identifier / identity pointer.

[0425] For example, based on one or more configuration parameters, a second TAG index / identifier / identity that indicates / identifies the cell / for the cell (e.g., TAG-Id2 One or more SPS configuration parameters in the SPS configuration may include a TAG index / identifier / identity pointer.

[0426] For example, the value of the unified TCI status type parameter based on the cell / cell is set to "separate", and one or more SPS configuration parameters of the SPS configuration may include TAG index / identifier / identity pointer.

[0427] For example, based on one or more configuration parameters, including feedback mode parameters set to "union" (e.g., ackNackFeedbackMode One or more SPS configuration parameters in the SPS configuration may include a TAG index / identifier / identity pointer. A feedback mode parameter set to "Unified" can indicate unified ACK / NACK feedback for two TRPs. A feedback mode parameter set to "Unified" can indicate unified ACK / NACK feedback for two coreset pool indices. A feedback mode parameter set to "Unified" can indicate unified ACK / NACK feedback for downlink receptions (e.g., PDSCH reception, PDCCH reception) associated with two coreset pool indices. For example, when the feedback mode parameter is set to "Unified," the radio device can multiplex / transmit a first HARQ-ACK feedback associated with a first coreset pool index (e.g., a first TRP) and a second HARQ-ACK feedback associated with a second coreset pool index (e.g., a second TRP) in the HARQ-ACK codebook.

[0428] For example, the radio device can clear the configured downlink assignment of the SPS configuration based on the expiration of the first time alignment timer of the first TAG associated with the SPS configuration.

[0429] For example, based on the SPS configuration associated with a first TAG that has / has an expired first time alignment timer, the radio device can clear the configured downlink assignment of the SPS configuration that has a TAG index / identifier / identity pointer indicating / identifying the first TAG. For example, based on the expiration of the first time alignment timer for the first TAG, the radio device can clear the configured downlink assignment of the SPS configuration that has a TAG index / identifier / identity pointer indicating / identifying the first TAG.

[0430] For example, if the value of the uniform TCI status type parameter in the cell is set to "separate", the radio device can clear the configured downlink assignment of the SPS configuration with a TAG index / identifier / identity pointer that indicates / identifies the first TAG.

[0431] For example, based on one or more configuration parameters, including feedback mode parameters set to "union" (e.g., ackNackFeedbackMode The wireless device can clear the configured downlink assignment of the SPS configuration with a TAG index / identifier / identity pointer that indicates / identifies the first TAG.

[0432] Figure 18 Example flowcharts of several tags for aspects of embodiments according to this disclosure are shown.

[0433] A wireless device may, for example, receive one or more messages from a base station that include one or more configuration parameters. A base station may transmit one or more configuration parameters to the wireless device.

[0434] One or more configuration parameters can indicate two timing advance groups (TAGs) for a cell.

[0435] One or more configuration parameters can indicate the Uniform Transport Configuration Indication (TCI) status type for a cell.

[0436] One or more configuration parameters can indicate / include semi-persistent scheduling (SPS) configuration for a cell.

[0437] The wireless device can receive downlink control information (DCI) indicating the activation of the SPS configuration. The base station can transmit the DCI indicating the activation of the SPS configuration.

[0438] In the example, the first time alignment timer of the first tag in the two tags may expire. The second time alignment timer of the second tag in the two tags may be running. While the second time alignment timer of the second tag in the two tags is running / during which the first time alignment timer of the first tag in the two tags may expire (e.g., Figure 18 The upper middle part is "no".

[0439] The radio device can clear the configured downlink assignment in the SPS configuration based on the expiration of the first time alignment timer and the cell's unified TCI state type. The base station can clear the configured downlink assignment in the SPS configuration based on the expiration of the first time alignment timer and the cell's unified TCI state type.

[0440] The radio device can determine whether to clear the configured downlink assignment in the SPS configuration based on the expiration of the first time alignment timer and the cell's unified TCI state type. The base station can also determine whether to clear the configured downlink assignment in the SPS configuration based on the expiration of the first time alignment timer and the cell's unified TCI state type.

[0441] The radio device can determine the configured downlink assignment to clear the SPS configuration based on the expiration of the first time alignment timer and the cell's unified TCI state type. The base station can determine the configured downlink assignment to clear the SPS configuration based on the expiration of the first time alignment timer and the cell's unified TCI state type.

[0442] When the first time alignment timer expires, the radio device can determine the configured downlink assignment to be cleared from the SPS configuration based on the cell's unified TCI state type. When the first time alignment timer expires, the base station can determine the configured downlink assignment to be cleared from the SPS configuration based on the cell's unified TCI state type.

[0443] When the first time alignment timer expires, the radio device can determine whether to clear the configured downlink assignment in the SPS configuration based on the cell's unified TCI state type. When the first time alignment timer expires, the base station can determine whether to clear the configured downlink assignment in the SPS configuration based on the cell's unified TCI state type.

[0444] In the example, the unified TCI status type of the cell / cell can be (and can be set to) "Unified" (e.g., unifiedTCI-StateType = "Joint" ).

[0445] The wireless device can apply a first joint TCI state to the PDSCH reception configured by the SPS. The wireless device can receive the PDSCH reception configured by the SPS based on (or using) the first joint TCI state.

[0446] The base station can transmit the first joint TCI state to the PDSCH configured by the SPS. The base station can transmit the PDSCH configured by the SPS to the radio device based on (or using) the first joint TCI state.

[0447] When the unified TCI state type of the cell is "joint" and the first time alignment timer of the first TAG expires, the radio device and / or base station can determine whether to clear the configured downlink assignment of the SPS configuration based on whether the first joint TCI state applied to the SPS configuration is associated with the first TAG.

[0448] In the example, when the first time alignment timer for the first TAG expires, the radio device can clear the configured downlink assignment of the SPS configuration based on the first joint TCI state applied to the SPS configuration and associated with the first TAG. In the example, when the first time alignment timer for the first TAG expires, the base station can clear the configured downlink assignment of the SPS configuration based on the first joint TCI state applied to the SPS configuration and associated with the first TAG. For the first joint TCI state, one or more configuration parameters may include a TAG ID pointer (e.g., 0) indicating the value of the first TAG among two TAGs. tag-Id-ptr ).

[0449] In the example, when the first time alignment timer for the first TAG expires, the radio device can associate a second TAG, different from the first TAG, with the first joint TCI state applied to the SPS configuration, without clearing the configured downlink assignment of the SPS configuration. When the first time alignment timer for the first TAG expires, the base station can associate a second TAG, different from the first TAG, with the first joint TCI state applied to the SPS configuration, without clearing the configured downlink assignment of the SPS configuration. For the first joint TCI state, one or more configuration parameters may include a TAG ID pointer (e.g., 1) indicating the value of the second TAG among the two TAGs. tag-Id-ptr ).

[0450] In the example, the unified TCI status type of the cell / cell can be (and can be set to) "separate" (e.g., unifiedTCI-StateType = "Separate", Figure 18 (No (separate path) in the middle).

[0451] The wireless device can apply the first downlink TCI state to the PDSCH reception configured by the SPS. The wireless device can receive the PDSCH reception configured by the SPS based on (or using) the first downlink TCI state.

[0452] The base station can transmit the application first downlink TCI state to the PDSCH configured by the SPS. The base station can transmit the SPS-configured PDSCH to the radio device based on (or using) the first downlink TCI state.

[0453] One or more configuration parameters can indicate the PUCCH resources for HARQ-ACK feedback transmission of PDSCH received for SPS configuration. The radio device can transmit the first uplink TCI state to the PUCCH via the PUCCH resources. The radio device can transmit PUCCH transmissions based on (or using) the first uplink TCI state via the PUCCH resources.

[0454] The base station can receive the first uplink TCI state from the PUCCH via PUCCH resources. The base station can receive PUCCH reception from the radio device based on (or using) the first uplink TCI state via PUCCH resources.

[0455] When the uniform TCI status type of the cell is "separated" and the first time alignment timer of the first TAG expires, the radio device and / or base station can determine whether to clear the configured downlink assignment of the SPS configuration based on whether the first uplink TCI status of the PUCCH resources applied to the SPS configuration is associated with the first TAG.

[0456] In the example, when the first time alignment timer for the first TAG expires, the radio device can clear the configured downlink assignment of the SPS configuration based on the first uplink TCI state of the PUCCH resources applied to the SPS configuration associated with the first TAG. When the first time alignment timer for the first TAG expires, the base station can clear the configured downlink assignment of the SPS configuration based on the first uplink TCI state of the PUCCH resources applied to the SPS configuration associated with the first TAG. For the first uplink TCI state, one or more configuration parameters may include / indicate a TAG ID pointer (e.g., 0) having a value (e.g., 0) indicating the first TAG among two TAGs. tag-Id-ptr ).

[0457] In the example, when the first time alignment timer for the first TAG expires, the radio device can associate a second TAG, different from the first TAG, with the first uplink TCI state of the PUCCH resources applied to the SPS configuration, without clearing the configured downlink assignment of the SPS configuration. When the first time alignment timer for the first TAG expires, the base station can associate a second TAG, different from the first TAG, with the first uplink TCI state of the PUCCH resources applied to the SPS configuration, without clearing the configured downlink assignment of the SPS configuration. For the first uplink TCI state, one or more configuration parameters may include a TAG ID pointer (e.g., 1) indicating the value of the second TAG among the two TAGs. tag-Id-ptr ).

[0458] For SPS configurations, one or more configurations may include / indicate a pointer to a TAG ID with a certain value (e.g., tag-Id-ptr ).

[0459] When the cell’s unified TCI status type is “separated” and the first time alignment timer of the first TAG expires, the radio device and / or base station can determine whether to clear the configured downlink assignment in the SPS configuration based on whether the value of the TAG ID pointer in the SPS configuration indicates the first TAG.

[0460] In the example, when the first time alignment timer of the first TAG expires, the radio device can instruct the first TAG to clear the configured downlink assignment in the SPS configuration based on the value of the TAG ID pointer configured in the SPS configuration (e.g., 0). When the first time alignment timer of the first TAG expires, the base station can instruct the first TAG to clear the configured downlink assignment in the SPS configuration based on the value of the TAG ID pointer configured in the SPS configuration (e.g., 0).

[0461] In the example, when the first time alignment timer for the first TAG expires, the radio device can indicate the second TAG based on the value of the TAG ID pointer configured in the SPS (e.g., 1), without clearing the configured downlink assignment in the SPS. When the first time alignment timer for the first TAG expires, the base station can indicate the second TAG based on the value of the TAG ID pointer configured in the SPS (e.g., 1), without clearing the configured downlink assignment in the SPS.

[0462] In the example, the first time alignment timer for the first TAG may expire (or may not be running). The second time alignment timer for the second TAG may not be running (or may expire). Both the first and second time alignment timers may not be running (or may expire).

[0463] For example, if both the first time alignment timer based on the first TAG and the second time alignment timer based on the second TAG are not running (or have expired), the wireless device can clear the configured downlink assignment in the SPS configuration.

[0464] For example, if the first time alignment timer based on the first TAG and the second time alignment timer based on the second TAG are both not running (or have expired), the base station can clear the configured downlink assignment in the SPS configuration.

[0465] In the example, clearing a configured downlink assignment may include a radio device not receiving PDSCH receive blocks via at least one radio resource indicated by the configured downlink assignment. In the example, clearing a configured downlink assignment may include a radio device not receiving PDSCH reception for the configured downlink assignment. In the example, a base station may assign / allocate a configured downlink assignment (or at least one radio resource indicated by the configured downlink assignment) to a second radio device. If the radio device does not clear the configured downlink assignment, the radio device may receive PDSCH reception via at least one radio resource indicated by the configured downlink assignment. Receiving PDSCH reception via at least one radio resource may result in a conflict with the second radio device. In the example, clearing a configured downlink assignment may include a radio device not using the configured downlink assignment for PDSCH reception. When a radio device clears a configured downlink assignment, the radio device may not release the configuration of the configured downlink assignment. When a radio device clears a configured downlink assignment, the radio device may save / store the configuration of the configured downlink assignment.

[0466] When associated with a TAG timeAlignmentTimer Upon expiration, for cells configured with a TAG (or in or belonging to the TAG) and those with operational... timeAlignmentTimer The second tag, wireless devices can: -Parameters in the cell / higher floors of the cell unifiedTCI-StateType The value is Union In the case of clearing the application with an expiration date, timeAlignmentTimer Any configured downlink assignment of the TCI state associated with the TAG; -Parameters in the cell / higher floors of the cell unifiedTCI-StateType The value is Separation In the case of clearing out items with expiration dates, timeAlignmentTimer Any configured downlink assignment of PUCCH resources whose TAG-associated TCI status is activated / indicated; When associated with a TAG timeAlignmentTimerUpon expiration, for cells configured with a TAG (or in or belonging to the TAG) and those with operational... timeAlignmentTimer The second tag, wireless devices can: -Parameters in the cell / higher floors of the cell unifiedTCI-StateType The value is Union In the case of clearing the application with an expiration date, timeAlignmentTimer Any configured downlink assignment of the TCI state associated with the TAG; -Parameters in the cell / higher floors of the cell unifiedTCI-StateType The value is Separation In this case, clear the configured / instructed / provided indication with an expir...

Claims

1. A method comprising: The wireless device receives one or more messages including one or more configuration parameters of the cell, wherein the one or more configuration parameters indicate: The two advance timing groups TAG of the community; as well as The Physical Downlink Shared Control Channel (PDSCH) resources used for the Semi-Persistent Scheduling (SPS) configuration of the cell receive the Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) feedback transmission of the Physical Uplink Control Channel (PUCCH). Determine whether the time alignment timer for the first of the two tags has expired; as well as Based on the Transport Configuration Indicator (TCI) state for the PUCCH resource used in the SPS configuration being associated with the first TAG having an expired time-aligned timer, one or more downlink assignments of the SPS configuration are cleared.

2. A method comprising clearing the downlink assignment by a wireless device based on a Transmission Configuration Indicator (TCI) state for uplink resources assigned to the downlink and a TAG with an expiration time-aligned timer in one of two timing advance groups (TAGs) of the cell.

3. The method of claim 2, further comprising determining whether the time alignment timer of one of the two TAGs has expired.

4. The method according to any one of claims 2 to 3, further comprising receiving one or more messages including one or more configuration parameters of the cell, wherein the one or more configuration parameters indicate: The two tags of the cell; and The Physical Downlink Shared Control Channel (PDSCH) resources used for the semi-persistent scheduling (SPS) configuration of the cell, the Physical Uplink Control Channel (PUCCH) resources received by the HARQ-ACK feedback transmission.

5. The method of claim 4, wherein the downlink assignment has the SPS configuration.

6. The method of claim 5, wherein the uplink resource for the downlink assignment is the physical uplink control channel (PUCCH) resource for the SPS configuration.

7. The method according to any one of claims 2 to 6, wherein: The TAG is the first of the two TAGs in the cell; and When the time alignment timer of the first TAG expires, the time alignment timer of the second TAG of the two TAGs is running.

8. The method of claim 7, further comprising associating a second TCI state of a second PUCCH resource based on a second SPS configuration with a second TAG having a running time alignment timer, without clearing the downlink assignment of the second SPS configuration.

9. The method according to any one of claims 4 to 8, further comprising receiving downlink control information (DCI) indicating activation of the SPS configuration.

10. The method according to any one of claims 2 to 9, further comprising receiving one or more control commands indicating two TCI states for the cell, wherein the two TCI states include the TCI state.

11. The method of claim 10, wherein the one or more configuration parameters include a TCI status parameter of the PUCCH resource, wherein the value of the TCI status parameter indicates the TCI status for the PUCCH resource among the two TCI states.

12. The method of claim 11, wherein: Based on the TCI state parameter being set to a first value, the TCI state is the first TCI state among the two TCI states; or Based on the TCI state parameter being set to a second value, the TCI state is the second TCI state among the two TCI states.

13. The method of claim 12, wherein: The first TCI state is for the first control resource set coreset pool index; and The second TCI state is for the second coreset pool index.

14. The method according to any one of claims 5 to 13, wherein clearing the downlink assignment of the SPS configuration includes not using the downlink assignment of the SPS configuration for Physical Downlink Shared Control Channel (PDSCH) reception of the SPS configuration.

15. The method according to any one of claims 4 to 14, wherein the one or more configuration parameters indicate the TAG identifier pointer of the TAG to the TCI status indication.

16. The method of claim 15, wherein the value of the TAG identifier pointer indicates the TAG of the two TAGs.

17. The method of claim 15, wherein the value of the TAG identifier pointer indicates the second TAG of the two TAGs.

18. The method according to any one of claims 2 to 17, wherein: The TAG is the first of the two TAGs in the cell; and The method further includes associating the second TCI state of the second PUCCH resource based on the second SPS configuration with the second TAG having a running time alignment timer, without clearing the downlink assignment of the second SPS configuration.

19. The method according to any one of claims 2 to 18, wherein the cell is the serving cell of the wireless device.

20. The method of claim 19, wherein the serving cell is a special cell (SpCell) or a secondary cell (SCell).

21. The method of claim 20, wherein the serving cell is a SpCell of a primary cell group (MCG) or a secondary cell group (SCG).

22. The method according to any one of claims 4 to 21, wherein the one or more configuration parameters of the cell include parameters for timing advance offset.

23. A method comprising: The wireless device receives one or more messages including one or more configuration parameters of the cell, wherein the one or more configuration parameters indicate: For the two timing advance group TAGs of the cell, wherein the two TAGs include a first TAG and a second TAG; as well as The multi-panel scheme parameters are set to the spatial domain multiplexing SDM scheme. as well as The following criteria are used to clear uplink authorization for PUSCH transports: The first time alignment timer of the first TAG expires, while the second time alignment timer of the second TAG is running; The parameters of the multi-panel scheme are set to the SDM scheme; as well as The PUSCH transmission is indicated to have two TCI states.

24. A method comprising a wireless device clearing an uplink license for uplink transmissions based on: The first time alignment timer for the first tag in the two time advance group tags of the cell expires; The parameters for the multi-panel scheme are set to the spatial domain reuse SDM scheme; as well as The uplink transmission is indicated by two Transport Configuration Indicator (TCI) states.

25. The method of claim 24, wherein a second time alignment timer for the second TAG of the two TAGs is running.

26. The method according to claim 24 or 25, further comprising: Receive one or more messages including one or more configuration parameters of the cell, wherein the one or more configuration parameters indicate: Regarding the two tags of the aforementioned cell; as well as The multi-panel scheme parameters are set to the SDM scheme.

27. The method according to any one of claims 24 to 26, wherein the uplink transmission is a Physical Uplink Shared Channel (PUSCH) transmission.

28. The method according to any one of claims 24 to 27, wherein the uplink authorization is a configured uplink authorization.

29. The method of claim 28, wherein the one or more configuration parameters include the configured uplink authorized TCI status parameter, wherein the TCI status parameter is set to indicate the application of two TCI status values ​​to the configured uplink authorized PUSCH transmission.

30. The method of any one of claims 24 to 29, wherein the uplink authorization is a PUSCH resource for semi-persistent CSI reporting.

31. The method of claim 30, further comprising receiving downlink control information (DCI) activating the semi-persistent CSI report generated via the PUSCH resource, wherein the DCI includes an SRS resource set indicator field, the SRS resource set indicator field being configured to indicate the application of values ​​of the two TCI states to the PUSCH transport of the semi-persistent CSI report generated via the PUSCH resource.

32. An apparatus comprising one or more processors and a memory storing instructions, said instructions, when executed by said one or more processors, causing the apparatus to perform at least the method according to any one of claims 1 to 31.

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

Images