Maintenance of multiple timing advance groups

Abstract

A wireless device may receive a downlink message via cells associated with at least two timing advance groups (TAGs), the downlink message indicating uplink resources for hybrid automatic repeat request acknowledgement (HARQ-ACK) feedback. The uplink resource may be associated with a transmission configuration indicator (TCI) state for at least two active TCI states of the cell. The wireless device may command a physical layer of the wireless device to generate an acknowledgement based on a time alignment timer of a TAG of the at least two TAGs of the cell associated with the TCI state being running. The wireless device may transmit HARQ-ACK feedback including an acknowledgement via the cell and based on the TCI state.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. Provisional Application No. 63 / 334,985, filed on April 26, 2022, the entire contents of which are hereby incorporated by reference. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

[0005] Figure 2A and Figure 2B New Radio (NR) user plane and control plane protocol stacks are shown separately.

[0006] Figure 3 Shown in Figure 2A Examples of services provided between the protocol layers of the NR user plane protocol stack.

[0007] Figure 4A Shows the flow Figure 2A Figure 2 shows an exemplary downlink data flow of the NR user plane protocol stack.

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

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

[0010] Figure 6 is an example diagram showing RRC state transition of a UE.

[0011] Figure 7 An exemplary configuration of an NR frame into which OFDM symbols are grouped is shown.

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

[0013] Fig. 9 An example of bandwidth adaptation using three configured BWPs for NR carriers is shown.

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

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

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

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

[0018] Fig. 12A and Fig. 12B Three examples of downlink and uplink beam management procedures are shown respectively.

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

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

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

[0022] Fig.15 An example of a wireless device in communication with a base station is shown.

[0023] Fig.16A , Fig. 16B , Fig. 16C and Fig.16D Exemplary structures for uplink and downlink transmissions are shown.

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

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

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

[0027] Fig. 20 An example of management of multiple time alignment timers according to one aspect of an embodiment of the present disclosure is shown.

[0028] Fig.21An exemplary flow chart of management of multiple time alignment timers according to one aspect of an embodiment of the present disclosure is shown. DETAILED DESCRIPTION

[0029] In the present disclosure, various embodiments are presented in the form of examples of how the disclosed technology can be implemented and / or how the disclosed technology can be practiced in environments and scenarios. It will be apparent to those skilled in the relevant art that various changes in form and detail can be made therein without departing from the scope of the present invention. In fact, after reading the specification, it will be apparent to those skilled in the relevant art how to implement alternative embodiments. The embodiments of the present invention should not be limited to any described exemplary embodiments. The embodiments of the present disclosure will be described with reference to the accompanying drawings. Restrictions, features and / or elements from the disclosed exemplary embodiments can be combined to create additional embodiments within the scope of the present disclosure. Any figure highlighting functionality and advantages is provided only for illustrative purposes. The disclosed architecture is flexible and configurable enough so that it can be utilized in a manner different from that shown. For example, the actions listed in any flow chart can be reordered or only optionally used in certain embodiments.

[0030] Embodiments may be configured to operate as desired. For example, in a wireless device, a base station, a radio environment, a network, a combination of the above, etc., when certain criteria are met, the disclosed mechanism may be executed. Exemplary criteria may be based at least in part on, for example, wireless device or network node configuration, traffic load, initial system settings, packet size, traffic characteristics, a combination of the above, etc. When one or more criteria are met, various exemplary embodiments may be applied. Therefore, exemplary embodiments that selectively implement the disclosed protocol may be implemented.

[0031] A base station may communicate with a mixture of wireless devices. A wireless device and / or base station may support multiple technologies and / or multiple versions of the same technology. A wireless device may have certain specific capabilities, depending on the wireless device category and / or capabilities. When the present disclosure refers to a base station communicating with multiple wireless devices, the present disclosure may refer to a subset of the total wireless devices in the coverage area. For example, the present disclosure may refer to multiple wireless devices of a given LTE or 5G version with a given capability and in a given sector of a base station. The multiple wireless devices in the present disclosure may refer to a selected plurality of wireless devices, and / or a subset of the total wireless devices in the coverage area that perform according to the disclosed methods, etc. There may be multiple base stations or multiple wireless devices in the coverage area that may not comply with the disclosed methods, for example, these wireless devices or base stations may perform based on older versions of LTE or 5G technology.

[0032] In the present disclosure, "a" and "an" and similar phrases will be interpreted as "at least one" and "one or more". Similarly, any term ending with the suffix "(s)" will be interpreted as "at least one" and "one or more". In the present disclosure, the term "may" is interpreted as "may, for example". In other words, the term "may" indicates that the phrase after the term "may" is an example of a suitable possibility among multiple suitable possibilities that may or may not be used for one or more embodiments in various embodiments. As used herein, the terms "including" and "consisting of..." list one or more components of the element being described. The terms "including" and "comprising" are interchangeable and do not exclude that unlisted components are included in the element being described. In contrast, "consisting of..." provides a complete listing of the one or more components of the element being described. As used herein, the term "based on" should be interpreted as "based at least in part on" rather than, for example, "based only on". As used herein, the term "and / or" represents any possible combination of the listed elements. For example, “A, B and / or C” can mean A; B; C; A and B; A and C; B and C; or A, B and C.

[0033] If A and B are sets, and every element of A is also an element of B, then A is called a subset of B. In this specification, only non-empty sets and subsets are considered. For example, the 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 after the term "based on" is an example of one of multiple suitable possibilities that may or may not be used for one or more different embodiments. The phrase "in response to" (or equivalently "at least in response to") indicates that the phrase after the phrase "in response to" is an example of one of multiple suitable possibilities that may or may not be used for one or more different embodiments. The phrase "depends on" (or equivalently "at least depends on") indicates that the phrase after the phrase "depends on" is an example of one of multiple suitable possibilities that may or may not be used for one or more different embodiments. The phrase "adopting / using" (or equivalently "at least adopting / using") indicates that the phrase after the phrase "adopting / using" is an example of one of multiple suitable possibilities that may or may not be used for one or more different embodiments.

[0034] The term configured may relate to the capabilities of a device, whether the device is in an operational state or a non-operational state. "Configured" may also mean a specific setting in a device that affects the operational characteristics of the device, whether the device is in an operational state or a non-operational state. In other words, hardware, software, firmware, registers, memory values, etc. may be "configured" within a device to provide specific characteristics to the device, whether the device is in an operational state or a non-operational state. Terms such as "a control message caused in a device" may mean that the control message has parameters that can be used to configure specific characteristics in the device or parameters that can be used to implement certain actions in the device, whether the device is in an operational state or a non-operational state.

[0035] In the present 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 exemplary embodiment, when one or more messages include multiple parameters, it means that a parameter of the multiple parameters is in at least one of the one or more messages, but not necessarily in each of the one or more messages.

[0036] Many of the features set forth are described as optional, either by the use of "may" or by the use of parentheses. For the sake of brevity and readability, the present disclosure does not explicitly recite every permutation that can be obtained by selecting from the set of optional features. The present 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, i.e., having only one of the three possible features, having any two of the three possible features, or having three of the three possible features.

[0037] Many elements described in the disclosed embodiments can be implemented as modules.Modules are defined here as elements that perform defined functions and have defined interfaces to other elements.Modules described in the present disclosure can be implemented by hardware, software, firmware, wetware (for example, hardware with biological elements) in combination with hardware, or a combination thereof, all of which can be equivalent in behavior.For example, a module can be implemented as a software routine written in a computer language, which is configured to be executed by a hardware machine (such as, C, C++, Fortran, Java, Basic, Matlab, etc.) or a modeling / simulation program (such as, Simulink, Stateflow, GNU Octave or LabVIEWMathScript).It is possible to implement a module using physical hardware that incorporates 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 often programmed using a hardware description language (HDL), such as VHSIC Hardware Description Language (VHDL) or Verilog, which configures the connections between less functional internal hardware blocks on the programmable device. The mentioned techniques are often used in combination to achieve the results of the functional blocks.

[0038] Figure 1A 1 shows an example of a mobile communication network 100 in which embodiments of the present disclosure may be implemented. 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 wireless devices 106 .

[0039] The CN 102 may provide an interface to one or more data networks (DNs), such as a public DN (e.g., the Internet), a private DN, and / or an intra-carrier DN, for the wireless device 106. As part of the interface functionality, the CN 102 may set up 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.

[0040] The RAN 104 may connect the CN 102 to the wireless device 106 via radio communications over an air interface. As part of the radio communications, the RAN 104 may provide scheduling, radio resource management, and retransmission protocols. The direction of communication from the RAN 104 to the wireless device 106 over the air interface is referred to as downlink, while the direction of communication from the wireless device 106 to the RAN 104 over the air interface is referred to as uplink. Downlink transmissions may be separated from uplink transmissions using frequency division duplex (FDD), time division duplex (TDD), and / or some combination of the two duplex technologies.

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

[0042] The 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: a Node B (associated with UMTS and / or 3G standards); an evolved Node B (eNB, associated with E-UTRA and / or 4G standards); a remote radio head (RRH); a baseband processing unit coupled to one or more RRHs; a repeater node or relay node used to extend the coverage area of ​​a donor node; a next generation evolved Node B (ng-eNB); a generation Node B (gNB, associated with NR and / or 5G standards); an access point (AP, associated with, for example, WiFi or any other suitable wireless communication standard); and / or any combination thereof. A base station may include at least one gNB central unit (gNB-CU) and at least one gNB distributed unit (gNB-DU).

[0043] The base stations included in the RAN 104 may include one or more sets of antennas for communicating with the wireless devices 106 over the 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 cell may be determined by the range at which a receiver (e.g., a base station receiver) can successfully receive transmissions from a transmitter (e.g., a wireless device transmitter) operating in the cell. The cells of the base stations may together provide radio coverage to the wireless devices 106 over a wide geographic area to support wireless device mobility.

[0044] In addition to three-sector sites, other implementations of the base station are possible. For example, one or more of the base stations in the RAN 104 may be implemented as a sectorized site with more or less than three sectors. One or more of the base stations in the RAN 104 may be implemented as an access point, a baseband processing unit coupled to several remote radio heads (RRHs), and / or a repeater or relay node for extending the coverage area of ​​a donor node. The baseband processing unit coupled to the RRH may be part of a centralized or cloud RAN architecture, where the baseband processing unit may be centralized in a baseband processing unit pool or virtualized. The repeater node may amplify and rebroadcast the radio signal received from the donor node. The relay node may perform the same / similar functions as the repeater node, but may decode the radio signal received from the donor node to eliminate noise before amplifying and rebroadcasting the radio signal.

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

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

[0047] Figure 1BAnother exemplary mobile communication network 150 in which embodiments of the present disclosure may be implemented is shown. The mobile communication network 150 may be, for example, a PLMN operated by a network operator. Figure 1B As shown in FIG. 1 , 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). Figure 1A The corresponding components described are implemented and operate in the same or similar manner.

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

[0049] like Figure 1B As shown, 5G-CN 152 includes an access and mobility management function (AMF) 158A and a user plane function (UPF) 158B. For ease of explanation, Figure 1B They are shown as one component AMF / UPF 158 in FIG. UPF 158B can act as a gateway between NG-RAN 154 and the one or more DNs. UPF 158B can perform functions such as: packet routing and forwarding, packet inspection and user plane policy rule enforcement, service usage reporting, uplink classification to support 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 verification), downlink packet buffering and downlink data notification triggering. UPF 158B can act as an anchor point for intra / inter-radio access technology (RAT) mobility, an external protocol (or packet) data unit (PDU) session point interconnected with the one or more DNs, and / or a fulcrum for supporting multi-host PDU sessions. UE 156 can be configured to receive services through a PDU session, which is a logical connection between the UE and the DN.

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

[0051] 5G-CN 152 may include Figure 1B , one or more additional network functions shown in . 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 exposure function (NEF), unified data management (UDM), application function (AF) and / or authentication server function (AUSF).

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

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

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

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

[0056] 5G-CN 152 is described as being configured to handle both NR and 4G radio access. One of ordinary skill in the art will appreciate that it is possible for NR to be connected to a 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 Only one AMF / UPF 158 is shown in the figure, but a gNB or ng-eNB can be connected to multiple AMF / UPF nodes to provide redundancy and / or load sharing across the multiple AMF / UPF nodes.

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

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

[0059] Figure 2A An NR user plane protocol stack including five layers implemented in a UE 210 and a gNB 220 is shown. At the bottom of the protocol stack, a physical layer (PHY) 211 and 221 may provide transport services to higher layers of the protocol stack and may correspond to layer 1 of the open system interconnection (OSI) model. The next four protocols above the PHY 211 and 221 include a medium access control layer (MAC) 212 and 222, a radio link control layer (RLC) 213 and 223, a packet data convergence protocol layer (PDCP) 214 and 224, and a service data application protocol layer (SDAP) 215 and 225. Together, these four protocols may constitute layer 2 or the data link layer of the OSI model.

[0060] Figure 3 An example of services provided between protocol layers of the NR user plane protocol stack is shown. Figure 2A and Figure 3Starting from the top of , SDAP 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 DN. A PDU session can have one or more QoS flows. The UPF of the CN (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 delay, data rate and / or error rate). SDAP 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 the QoS flows and the data radio bearers can be determined by the SDAP 225 at the gNB 220. The SDAP 215 at the UE 210 can learn the mapping between the QoS flows and the data radio bearers through reflective mapping or control signaling received from the gNB 220. For reflective mapping, the SDAP 225 at the gNB 220 may mark downlink packets with a QoS flow indicator (QFI), which may be observed by the SDAP 215 at the UE 210 to determine the mapping / demapping between QoS flows and data radio bearers.

[0061] The PDCP 214 and 224 may perform header compression / decompression to reduce the amount of data that needs to be transmitted over the air interface, may perform encryption / decryption to prevent unauthorized decoding of data transmitted over the air interface, and may perform integrity protection to ensure that control messages originate from the intended source. The PDCP 214 and 224 may perform retransmission of undelivered packets, in-sequence delivery and reordering of packets, and removal of duplicate received packets due to, for example, intra-gNB handovers. The PDCP 214 and 224 may perform packet repetition to increase the likelihood that a packet is received, and remove any duplicate packets at the receiver. Packet repetition may be applicable to services that require high reliability.

[0062] although Figure 3 Not shown, but PDCP 214 and 224 can perform mapping / de-mapping between split radio bearers and RLC channels in a dual connectivity scenario. Dual connectivity is a technology 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). A split bearer is a split bearer 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 / demapped split radio bearers between RLC channels belonging to a cell group.

[0063] RLC 213 and 223 can perform segmentation, retransmission through automatic repeat request (ARQ), and removal of duplicate data units received from MAC 212 and 222, respectively. RLC 213 and 223 can support three transmission modes: transparent mode (TM); unacknowledged mode (UM); and acknowledged mode (AM). Based on the transmission mode in which the RLC is operating, the RLC can perform one or more of the functions described. RLC configuration can be based on each logical channel, independent of parameter sets and / or transmission time interval (TTI) duration. As shown in FIG. Figure 3 As shown in FIG. 1 , RLC 213 and 223 may provide RLC channels as services to PDCP 214 and 224, respectively.

[0064] The MAC 212 and 222 may perform multiplexing / demultiplexing of logical channels and / or mapping between logical channels and transport channels. The multiplexing / demultiplexing may include multiplexing / demultiplexing data units belonging to the one or more logical channels into / from a transport block (TB) delivered to / from the PHY 211 and 221. The MAC 222 may be configured to perform scheduling, scheduling information reporting, and priority handling between UEs with the aid of dynamic scheduling. Scheduling may be performed in the gNB 220 (at the MAC 222) for downlink and uplink. The MAC 212 and 222 may be configured to perform error correction by hybrid automatic repeat request (HARQ) (e.g., one HARQ entity per carrier in the case of carrier aggregation (CA)), priority handling between logical channels of the UE 210 with the aid of logical channel prioritization, and / or padding. The MAC 212 and 222 may support one or more parameter sets and / or transmission timing. In an example, mapping restrictions in logical channel prioritization may control which parameter sets and / or transmission timings a logical channel may use. Figure 3 As shown, MAC 212 and 222 may provide logical channels as services to RLC 213 and 223 .

[0065] PHY 211 and 221 can perform mapping of transport channels to physical channels and digital and analog signal processing functions for sending and receiving information over the air interface. These digital and analog signal processing functions may include, for example, encoding / decoding and modulation / demodulation. PHY 211 and 221 can perform multi-antenna mapping. Figure 3 As shown in , PHY 211 and 221 may provide one or more transport channels as a service to MAC 212 and 222 .

[0066] Figure 4A An exemplary downlink data flow through the NR user plane protocol stack is shown. Figure 4AThe downlink data flow of three IP packets (n, n+1, and m) flowing through the NR user plane protocol stack to generate two TBs at the gNB 220 is shown. The uplink data flow flowing through the NR user plane protocol stack can be the same as Figure 4A The downlink data flow is similar to that depicted in .

[0067] Figure 4A The downlink data flow of starts when SDAP 225 receives three IP packets from one or more QoS flows and maps the three packets to a radio bearer. Figure 4A In the SDAP header (in Figure 4A The data unit from / to a higher protocol layer is called a service data unit (SDU) of the lower protocol layer, and the data unit to / from a lower protocol layer is called a protocol data unit (PDU) of the higher protocol layer. Figure 4A As shown in , the data unit from SDAP 225 is the SDU of the lower protocol layer PDCP 224 and is the PDU of SDAP 225 .

[0068] Figure 4A The remaining protocol layers in can perform their associated functions (e.g., Figure 3 ), add the corresponding headers, and forward their corresponding outputs to the next lower layer. For example, PDCP 224 may perform IP header compression and encryption, and forward its output to RLC 223. RLC 223 may optionally perform segmentation (e.g., Figure 4A 222) and forwards its output to MAC 222. MAC 222 may multiplex many RLC PDUs and may attach MAC subheaders to the RLC PDUs to form a transport block. In NR, MAC subheaders may be distributed throughout the MAC PDU, as shown in FIG. Figure 4A 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 calculated before assembling the complete MAC PDU.

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

[0070] Figure 4B Further shown is a MAC Control Element (CE) inserted into the MAC PDU by a MAC (such as MAC 223 or MAC 222). For example, Figure 4B Two MAC CEs are shown inserted into the MAC PDU. Figure 4B ) and inserting a MAC CE at the end of a MAC PDU for uplink transmission. MAC CE may be used for in-band control signaling. Example MAC CEs include: scheduling-related MAC CEs, such as buffer status reports and power headroom reports; activation / deactivation MAC CEs, such as those used for PDCP duplicate detection, channel state information (CSI) reporting, sounding reference signal (SRS) transmission, 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 having a format similar to that described for a MAC SDU may be present before the MAC CE, and the MAC CE may be identified with a reserved value in the LCID field that indicates the type of control information included in the MAC CE.

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

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

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

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

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

[0076] - a dedicated control channel (DCCH) used to carry control messages to / from a specific UE to configure the UE; and

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

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

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

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

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

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

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

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

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

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

[0087] - Physical Downlink Control Channel (PDCCH), which is used to carry downlink control information (DCI), which may include downlink scheduling commands, uplink scheduling grants, and uplink power control commands;

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

[0089] - Physical Uplink Control Channel (PUCCH), which is used to carry UCI, which may include HARQ acknowledgment, channel quality indicator (CQI), precoding matrix indicator (PMI), rank indicator (RI) and scheduling request (SR); and

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

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

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

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

[0094] The RRCs 216 and 226 may provide control plane functions between the UE 210 and the gNB 220 or more generally between the UE 210 and the RAN. The RRCs 216 and 226 may provide control plane functions between the UE 210 and the gNB 220 via signaling messages referred to as RRC messages. The RRC messages may be transported between the UE 210 and the RAN using signaling radio bearers and the same / similar PDCP, RLC, MAC, and PHY protocol layers. The MAC may multiplex control plane and user plane data into the same transport block (TB). The RRC 216 and 226 may provide control plane functions such as: broadcast of system information related to AS and NAS; paging initiated by CN or RAN; establishment, maintenance and release of an RRC connection 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 the reporting; detection of radio link failure (RLF) and recovery from radio link failure; and / or NAS messaging. As part of establishing an RRC connection, the RRC 216 and 226 may establish an RRC context, which may involve configuring parameters for communication between the UE 210 and the RAN.

[0095] Figure 6 is an example diagram showing the RRC state transition of the UE. The UE can Figure 1A The wireless device 106 depicted in Figure 2A and Figure 2B The UE 210 depicted in FIG. 1 and any other wireless device described in the present disclosure may be the same or similar. Figure 6 As shown in , the UE may be in at least one of three RRC states: RRC connected 602 (eg, RRC_CONNECTED), RRC idle 604 (eg, RRC_IDLE), and RRC inactive 606 (eg, RRC_INACTIVE).

[0096] In RRC connection 602, the UE has an established RRC context and may have at least one RRC connection with a base station. The base station may be similar to one of the following: Figure 1A The one or more base stations included in the RAN 104 depicted in FIG. Figure 1B One of the gNB 160 or ng-eNB 162 depicted in FIG. Figure 2A and Figure 2B gNB220 depicted in ; or any other base station described in the present disclosure. 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., involving 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 mobility of the UE 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 a serving cell and neighboring cells, and report these measurements to the base station currently serving the UE. The UE's serving base station may request handover to a cell of one of the neighboring base stations based on the reported measurements. The RRC state may transition from RRC connected 602 to RRC idle 604 via a connection release procedure 608 , or to RRC inactive 606 via a connection deactivation procedure 610 .

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

[0098] In RRC inactive 606, the previously established RRC context is maintained in the UE and the base station. This allows a quick transition to RRC connected 602 with reduced signaling overhead compared to the transition from RRC idle 604 to RRC connected 602. When in RRC inactive 606, the UE may be in a sleep state, and the mobility of the UE may be managed by the UE through cell reselection. The RRC state may transition from RRC inactive 606 to RRC connected 602 through a connection recovery procedure 614, or to RRC idle 604 through a connection release procedure 616, which may be the same or similar to the connection release procedure 608.

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

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

[0101] The RAN area may be used to track the UE at the RAN level. For a UE in the RRC inactive 606 state, a RAN notification area may be assigned to the UE. The RAN notification area may include one or more cell identities, a list of RAIs, or a list of TAIs. In an example, a base station may belong to one or more RAN notification areas. In an example, a cell may belong to one or more RAN notification areas. If the UE moves to a cell not included in the RAN notification area assigned to the UE through cell reselection, the UE may perform a notification area update on the RAN to update the RAN notification area of ​​the UE.

[0102] The base station storing the RRC context for the UE or the last serving base station of the UE 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 of time that the UE remains in the RAN notification area of ​​the anchor base station and / or during the period of time that the UE remains in RRC inactivity 606.

[0103] gNBs, such as Figure 1B The gNB 160 in the embodiment of the present invention 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 the F1 interface. The gNB-CU may include RRC, PDCP, and SDAP. The gNB-DU may include RLC, MAC, and PHY.

[0104] In NR, physical signals and physical channels (about Figure 5A and Figure 5BDiscussed) can be mapped onto orthogonal frequency division multiplexing (OFDM) symbols. OFDM is a multi-carrier communication scheme that transmits data through F orthogonal subcarriers (or tones). Before transmission, the data can be mapped to a series of complex symbols called source symbols (e.g., M-quadrature amplitude modulation (M-QAM) symbols or M-phase shift keying (M-PSK) symbols) and divided into F parallel symbol streams. The F parallel symbol streams can be treated as if they are in the frequency domain and used as input to the inverse fast Fourier transform (IFFT) block that transforms them into the time domain. The IFFT block can take F source symbols at a time (one source symbol from each of the F parallel symbol streams), and use each source symbol to modulate the amplitude and phase of one of the F sinusoidal basis functions corresponding to the F orthogonal subcarriers. The output of the IFFT block can be F time domain samples representing the sum of the F orthogonal subcarriers. The F time domain samples can form a single OFDM symbol. After some processing (e.g., addition of a cyclic prefix) and up-conversion, the OFDM symbols provided by the IFFT block can be transmitted over the air interface at the carrier frequency. The F parallel symbol streams can be mixed using the FFT block before being processed by the IFFT block. This operation produces a discrete Fourier transform (DFT) precoded OFDM symbol and can be used by the UE in the uplink to reduce the peak to average power ratio (PAPR). The FFT block can be used to perform inverse processing on the OFDM symbol at the receiver to restore the data mapped to the source symbol.

[0105] Figure 7 An exemplary configuration of an NR frame into which OFDM symbols are grouped is shown. An NR frame may be identified by a system frame number (SFN). The SFN may be repeated with a period of 1024 frames. As shown, a NR frame may have a duration of 10 milliseconds (ms) and may include 10 subframes of duration 1 ms. A subframe may be divided into time slots that include, for example, 14 OFDM symbols per time slot.

[0106] The duration of a time slot may depend on the parameter set of the OFDM symbol used for the 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 mm-wave range). Parameter sets may be defined in terms of subcarrier spacing and cyclic prefix duration. For parameter sets in NR, the subcarrier spacing may be scaled up by powers of two from a baseline subcarrier spacing of 15 kHz, and the cyclic prefix duration may be scaled down by powers of two from a baseline cyclic prefix duration of 4.7 μs. For example, NR defines parameter sets with the following subcarrier spacing / cyclic prefix duration combinations: 15 kHz / 4.7 μs; 30 kHz / 2.3 μs; 60 kHz / 1.2 μs; 120 kHz / 0.59 μs; and 240 kHz / 0.29 μs.

[0107] A slot may have a fixed number of OFDM symbols (eg, 14 OFDM symbols). Parameter sets with higher subcarrier spacing have shorter slot durations and correspondingly more slots per subframe. Figure 7 The transmission structure of the time slot duration and each subframe time slot associated with the parameter set is shown (for ease of explanation, Figure 7 Parameter sets with subcarrier spacing of 240kHz are not shown in Figure 1). Subframes in NR can be used as a time reference independent of the parameter set, while slots can be used as the unit for scheduling uplink and downlink transmissions. To support low latency, scheduling in NR can be decoupled from the slot duration and start at any OFDM symbol and continue to transmit as many symbols as needed. These partial slot transmissions can be called mini-slots or sub-slot transmissions.

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

[0109] Figure 8A single parameter set is shown used across the entire bandwidth of the NR carrier. In other example configurations, multiple parameter sets may be supported on the same carrier.

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

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

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

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

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

[0115] One or more BWP indicator fields may be provided in downlink control information (DCI). The value of the BWP indicator field may indicate which BWP in a 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 may indicate the active uplink BWP for one or more uplink transmissions.

[0116] The base station may semi-statically configure a default downlink BWP for the UE within the 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 may be the initial active downlink BWP. The UE may determine which BWP is the initial active downlink BWP based on the CORESET configuration obtained using the PBCH.

[0117] The base station may configure the BWP inactivity timer value for the PCell for the UE. The UE may start or restart the BWP inactivity timer at any appropriate time. For example, the UE may start or restart the BWP inactivity timer in 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 indicating an active downlink BWP or an active uplink BWP other than the default downlink BWP or uplink BWP for unpaired spectrum operation. If the UE does not detect the DCI within a time interval (e.g., 1 ms or 0.5 ms), the UE may run the BWP inactivity timer towards expiration (e.g., an increment from zero to the BWP inactivity timer value, or a decrement from the BWP inactivity timer value to zero). When the BWP inactivity timer expires, the UE may switch from the active downlink BWP to the default downlink BWP.

[0118] In an example, the base station may semi-statically configure the UE with one or more BWPs. The UE may 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 expiration of a BWP inactivity timer (e.g., when the second BWP is the default BWP).

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

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

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

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

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

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

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

[0126] The configured SCell for a 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 transmission on the SCell. Figure 4B The MAC CE may be used to activate and deactivate the configured SCells. For example, the MAC CE may use a bitmap (e.g., one bit per SCell) to indicate which SCells (e.g., in a subset of configured SCells) are activated or deactivated for the UE. The configured SCells may be deactivated in response to the expiration of an SCell deactivation timer (e.g., one SCell deactivation timer per SCell).

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

[0128] Fig. 10B An example of how aggregated cells can be configured into one or more PUCCH groups is shown. PUCCH group 1010 and PUCCH group 1050 may include one or more downlink CCs, respectively. Fig. 10B, PUCCH group 1010 includes three downlink CCs: PCell 1011, SCell 1012, and SCell 1013. PUCCH group 1050 includes three downlink CCs: PCell 1051, SCell 1052, and SCell 1053 in this example. One or more uplink CCs may be configured as PCell 1021, SCell 1022, and SCell 1023. One or more other uplink CCs may 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) may be transmitted in the uplink of PCell 1021. Uplink control information (UCI) related to the downlink CCs of PUCCH group 1050 (shown as UCI 1071, UCI 1072, and UCI 1073) may be transmitted in the uplink of PSCell 1061. In the example, if Fig. 10B If the aggregated cell depicted in FIG. 1 is not divided into PUCCH group 1010 and PUCCH group 1050 , a single uplink PCell transmits UCI associated with a downlink CC, and the PCell may become overloaded. By dividing the transmission of UCI between PCell 1021 and PSCell 1061 , overload can be prevented.

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

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

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

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

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

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

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

[0136] The PBCH may use QPSK modulation and may use forward error correction (FEC). FEC may use polarity coding. One or more symbols spanned by the PBCH may carry one or more DMRS for demodulating the PBCH. The PBCH may include an indication of the current system frame number (SFN) of the cell and / or an SS / PBCH block timing index. These parameters may contribute to the time synchronization of the UE with the base station. The PBCH may include a master information block (MIB) for providing one or more parameters to the UE. The MIB may be used by the UE to locate the remaining minimum system information (RMSI) associated with the cell. The RMSI may include a system information block type 1 (SIB1). SIB1 may contain information required for the UE to access the cell. The UE may use one or more parameters of the MIB to monitor the PDCCH that may be used to schedule the PDSCH. The PDSCH may include SIB1. SIB1 may be decoded using the parameters provided in the MIB. The PBCH may indicate that SIB1 does not exist. Based on the PBCH indicating that SIB1 does not exist, the UE may point to a frequency. The UE may search for SS / PBCH blocks at the frequency to which the UE is pointing.

[0137] 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 block transmissions with different SS / PBCH block indices.

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

[0139] In an example, within a frequency range of a carrier, a base station may transmit multiple SS / PBCH blocks. In an example, a first PCI of a first SS / PBCH block in the multiple SS / PBCH blocks may be different from a second PCI of a second SS / PBCH block in the multiple SS / PBCH blocks. PCIs of SS / PBCH blocks transmitted in different frequency positions may be different or the same.

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

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

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

[0143] The CSI-RS configuration may include one or more parameters indicating, for example, up to 32 antenna ports. The UE may be configured to employ the same OFDM symbol for downlink CSI-RS and 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 blocks (PRBs) configured for the CORESET. The UE may be configured to employ the same OFDM symbol for downlink CSI-RS and SS / PBCH blocks when the downlink CSI-RS and SS / PBCH blocks are spatially QCLed and the resource elements associated with the downlink CSI-RS are outside the PRBs configured for the SS / PBCH blocks.

[0144] Downlink DMRS can be transmitted by the base station and used by the UE for channel estimation. For example, the 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. The frontload DMRS can be mapped on one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). The base station can semi-statically configure the UE with the number (e.g., maximum number) of frontload DMRS symbols for PDSCH. The DMRS configuration can support one or more DMRS ports. For example, for single-user MIMO, the DMRS configuration can support up to eight orthogonal downlink DMRS ports per UE. For multi-user MIMO, the DMRS configuration can support up to 4 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, in which the DMRS position, DMRS pattern and / or scrambling sequence can be the same or different. The base station may use the same precoding matrix to transmit the downlink DMRS and the corresponding PDSCH. The UE may use the one or more downlink DMRS to perform consistent demodulation / channel estimation on the PDSCH.

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

[0146] The PDSCH may include one or more layers. The UE may assume that at least one symbol with DMRS is present on a layer in the one or more layers of the PDSCH. The higher layers may configure up to 3 DMRS for the PDSCH.

[0147] The downlink PT-RS may be transmitted by a base station and used by a UE for phase noise compensation. Whether a downlink PT-RS exists may depend on an RRC configuration. The presence and / or type of a downlink PT-RS may be configured based on a UE-specific configuration using a combination of RRC signaling and / or an association with one or more parameters for other purposes (e.g., a modulation and coding scheme (MCS)) that may be indicated by a DCI. When configured, the dynamic presence of a downlink PT-RS may be associated with one or more DCI parameters including at least an MCS. The NR network may support multiple PT-RS densities defined in the time / frequency domain. When present, the frequency domain density may be associated with at least one configuration of the scheduled bandwidth. The UE may use the same precoding for DMRS ports and PT-RS ports. The number of PT-RS ports may be less than the number of DMRS ports in the scheduled resources. The downlink PT-RS may be limited to the scheduled time / frequency duration of the UE. The downlink PT-RS may be transmitted on a symbol to facilitate phase tracking at the receiver.

[0148] The UE may transmit an uplink DMRS to a base station for channel estimation. For example, the base station may use the uplink DMRS to consistently demodulate one or more uplink physical channels. For example, the UE may transmit an uplink DMRS with a PUSCH and / or a PUCCH. The uplink DM-RS may span a frequency range similar to the frequency range associated with the corresponding physical channel. The base station may configure the UE with one or more uplink DMRS configurations. At least one DMRS configuration may support a front-loaded DMRS mode. The front-loaded DMRS may be mapped on one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). One or more uplink DMRS may be configured to be transmitted at one or more symbols of the PUSCH and / or PUCCH. The base station may semi-statically configure the UE with the number (e.g., maximum number) of front-loaded DMRS symbols for the PUSCH and / or PUCCH, and the UE may use the front-loaded DMRS symbol to schedule single-symbol DMRS and / or dual-symbol DMRS. NR networks may support a common DMRS structure for downlink and uplink (e.g., for cyclic prefix orthogonal frequency division multiplexing (CP-OFDM)), where the DMRS positions, DMRS patterns, and / or scrambling sequences of the DMRS may be the same or different.

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

[0150] Depending on the RRC configuration of the UE, an uplink PT-RS (which can be used by the base station for phase tracking and / or phase noise compensation) may or may not exist. The presence and / or type of the uplink PT-RS can be configured based on UE-specific configuration through a combination of RRC signaling and / or one or more parameters for other purposes (e.g., modulation and coding scheme (MCS)) indicated by the DCI. When configured, the dynamic presence of the uplink PT-RS can be associated with one or more DCI parameters including at least the 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 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 scheduled time / frequency duration of the UE.

[0151] The UE may transmit an SRS to a base station for channel state estimation to support uplink channel-dependent scheduling and / or link adaptation. The SRS transmitted by the UE may allow the base station to estimate the uplink channel state at one or more frequencies. The scheduler at the base station may use the estimated uplink channel state to assign one or more resource blocks for uplink PUSCH transmission from the UE. The base station may semi-statically configure the UE with one or more SRS resource sets. For an SRS resource set, the base station may configure the UE with one or more SRS resources. The applicability of the SRS resource set may be configured by a higher layer (e.g., RRC) parameter. For example, when a higher layer parameter indicates beam management, the SRS resources in the SRS resource set in the one or more SRS resource sets (e.g., having the same / similar time domain behavior, periodic, aperiodic, etc.) may be transmitted at a certain time (e.g., at the same time). The UE may transmit one or more SRS resources in the SRS resource set. The NR network may support aperiodic, periodic, and / or semi-persistent SRS transmission. The UE may 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 an 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 an example, when PUSCH and SRS are transmitted in the same time slot, the UE may be configured to transmit SRS after transmission of PUSCH and corresponding uplink DMRS.

[0152] The base station can semi-statically configure the UE using one or more SRS configuration parameters indicating at least one of the following: an SRS resource configuration identifier; the number of SRS ports; the time domain behavior of the SRS resource configuration (e.g., an indication of periodic, semi-persistent, or non-periodic SRS); time slot, mini-slot, and / or subframe level periodicity; time slots of periodic and / or non-periodic SRS resources; the number of OFDM symbols in the SRS resources; the start OFDM symbol of the SRS resources; SRS bandwidth; frequency hopping bandwidth; cyclic shift; and / or SRS sequence ID.

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

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

[0155] Fig. 11B An example of a channel state information reference signal (CSI-RS) mapped in the time and frequency domain is shown. Fig. 11BThe squares shown in the figure may represent resource blocks (RBs) within the bandwidth of the cell. The base station may transmit one or more RRC messages including CSI-RS resource configuration parameters indicating one or more CSI-RS. One or more of the following parameters may be configured for the CSI-RS resource configuration through higher layer signaling (e.g., RRC and / or MAC signaling): CSI-RS resource configuration identity, number of CSI-RS ports, CSI-RS configuration (e.g., symbol and resource element (RE) positions in a subframe), CSI-RS subframe configuration (e.g., subframe position, offset and periodicity in a radio frame), CSI-RS power parameters, CSI-RS sequence parameters, code division multiplexing (CDM) type parameters, frequency density, transmission comb, quasi co-location (QCL) parameters (e.g., QCL-scramblingidentity, crs-portscount, mbsfn-subframeconfiglist, csi-rs-configZPid, qcl-csi-rs-configNZPid) and / or other radio resource parameters.

[0156] Fig. 11B The three beams shown may be configured for a UE in a UE-specific configuration. Fig. 11B Three beams (beam #1, beam #2, and beam #3) are shown in the figure, and more or fewer beams can be configured. CSI-RS1101 can be allocated to beam #1, which can be transmitted in one or more subcarriers in the RB of the first symbol. CSI-RS1102 can be allocated to beam #2, which can be transmitted in one or more subcarriers in the RB of the second symbol. CSI-RS1103 can be allocated to beam #3, which can be transmitted in 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 (for example, those subcarriers not used to transmit CSI-RS1101) to transmit another CSI-RS associated with the beam of another UE. By using time domain multiplexing (TDM), the beam for the UE can be configured so that the beam for the UE uses symbols from the beams of other UEs.

[0157] CSI-RS, such as Fig. 11BThose shown in (e.g., CSI-RS1101, 1102, 1103) can be transmitted by a base station and used by a UE for one or more measurement values. For example, the UE can measure the reference signal received power (RSRP) of the configured CSI-RS resource. The base station can configure the UE with a reporting configuration, and the UE can report the RSRP measurement value 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 a downlink transmission 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 of the transmission (Tx) beam based on the spatial domain filter of the corresponding Rx beam. If the UE does not have beam-corresponding capability, the UE may perform an uplink beam selection procedure to determine the spatial domain filter of the Tx beam. The UE may perform an uplink beam selection procedure based on one or more sounding reference signal (SRS) resources configured to the UE by the base station. The base station may select and indicate the uplink beam of the UE based on measurements of one or more SRS resources transmitted by the UE.

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

[0159] Fig. 12AExamples of three downlink beam management procedures are shown: P1, P2, and P3. Procedure P1 may enable UE measurements of transmit (Tx) beams of a transmit reception point (TRP) (or multiple TRPs), for example to support selection of one or more base station Tx beams and / or UE Rx beams (shown as ovals in the top and bottom rows of P1, respectively). Beamforming at the TRP may include Tx beam sweeping for a set of beams (shown as ovals rotating in a counterclockwise direction indicated by dashed arrows in the top rows of P1 and P2). Beamforming at the UE may include Rx beam sweeping for a set of beams (shown as ovals rotating in a clockwise direction indicated by dashed arrows in the bottom rows of P1 and P3). Procedure P2 may be used to enable UE measurements of Tx beams of a TRP (shown as ovals rotating in a counterclockwise direction indicated by dashed arrows in the top row of P2). The UE and / or the base station may perform procedure P2 using a smaller beam set than the beam set used in procedure P1, or using a narrower beam than the beam 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.

[0160] Fig. 12B Examples of three uplink beam management procedures are shown: U1, U2, and U3. Procedure U1 can be used to enable the base station to perform measurements on the UE's Tx beam, for example, to support selection of one or more UE Tx beams and / or base station Rx beams (shown as ovals in the top and bottom rows of U1, respectively). Beamforming at the UE can include, for example, Rx beam sweeping from a set of beams (shown as ovals rotating in a clockwise direction indicated by dashed arrows in the bottom rows of U1 and U3). Beamforming at the base station can include, for example, Rx beam sweeping from a set of beams (shown as ovals rotating in a counterclockwise direction indicated by dashed arrows in the top rows of U1 and U2). 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 the base station may perform procedure U2 using a smaller beam set than the beam set used in procedure P1, or using a narrower beam than the beam used in procedure P1. This may be referred to as beam refinement. The UE may perform procedure U3 to adjust its Tx beam when the base station uses a fixed Rx beam.

[0161] The UE may initiate a beam failure recovery (BFR) procedure based on detecting a beam failure. The UE may transmit a BFR request (e.g., preamble, UCI, SR, MAC CE, etc.) based on the initiation of the BFR procedure. The UE may detect a beam failure based on a determination that the quality of the beam-pair link of the associated control channel is unsatisfactory (e.g., having an error rate above an error rate threshold, a received signal power below a received signal power threshold, expiration of a timer, etc.).

[0162] The UE may measure the quality of a beam-to-link using one or more reference signals (RS), the one or more reference signals 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 a beam-to-link may be based on one or more of the following: a block error rate (BLER), an RSRP value, a signal-to-interference-plus-noise ratio (SINR) value, a reference signal received quality (RSRQ) value and / or a CSI value measured on an RS resource. The base station may indicate that the RS resource is quasi-co-located (QCLed) with one or more DM-RS of a channel (e.g., a control channel, a shared data channel, etc.). When the channel characteristics (e.g., Doppler shift, Doppler spread, average delay, delay spread, spatial Rx parameters, fading, etc.) from the transmission to the UE via the RS resource are similar or identical to the channel characteristics from the transmission to the UE via the channel, the RS resource and the one or more DMRS of the channel may be QCLed.

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

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

[0165] The configuration message 1310 may be transmitted, for example, using one or more RRC messages. The one or more RRC messages may indicate one or more random access channel (RACH) parameters to the UE. The one or more RACH parameters may include at least one of the following: general parameters for one or more random access procedures (e.g., RACH-configGeneral); cell-specific parameters (e.g., RACH-ConfigCommon); and / or dedicated parameters (e.g., RACH-configDedicated). The base station may broadcast or multicast 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 the RRC_INACTIVE state). The UE may determine the time-frequency resources and / or uplink transmission power for transmitting Msg 1 1311 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 reception timing and downlink channel for receiving Msg 2 1312 and Msg 4 1314.

[0166] The one or more RACH parameters provided in the configuration message 1310 may indicate one or more physical RACH (PRACH) opportunities that can be used to transmit Msg 11311. The one or more PRACH opportunities may be predefined. The one or more RACH parameters may indicate one or more available sets of one or more PRACH opportunities (e.g., prach-ConfigIndex). The one or more RACH parameters may indicate an association between: (a) one or more PRACH opportunities, and (b) one or more reference signals. The one or more RACH parameters may indicate an association between: (a) one or more preambles, and (b) one or more reference signals. The one or more reference signals may be SS / PBCH blocks and / or CSI-RS. For example, the one or more RACH parameters may indicate the number of SS / PBCH blocks mapped to the PRACH opportunity and / or the number of preambles mapped to the SS / PBCH block.

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

[0168] Msg 1 1311 may include one or more preamble transmissions (e.g., a preamble transmission and one or more preamble retransmissions). The RRC message may be used to configure one or more preamble groups (e.g., group A and / or group B). The preamble group may include one or more preambles. The UE may determine the preamble group based on the path loss measurement value and / or the size 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 having an RSRP above an RSRP threshold (e.g., rsrp-ThresholdSSB and / or rsrp-ThresholdCSI-RS). For example, if the association between the one or more preambles and the at least one reference signal is configured by an RRC message, the UE may select at least one preamble associated with the one or more reference signals and / or the selected preamble group.

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

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

[0171] 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 is received by the base station. Msg 2 1312 may include a time alignment command that may be used by the UE to adjust the transmission timing of the UE, a scheduling grant for transmitting Msg 3 1313, and / or a temporary cell RNTI (TC-RNTI). After transmitting the preamble, the UE may start a time window (e.g., ra-ResponseWindow) to monitor the PDCCH of Msg 2 1312. The UE may determine when to start the time window based on the PRACH opportunity used by the UE to transmit the preamble. For example, the UE may start a time window of one or more symbols after the last symbol of the preamble (e.g., at the first PDCCH opportunity starting from the end of the preamble transmission). The one or more symbols may be determined based on a parameter set. The PDCCH may be in a common search space (e.g., Type1-PDCCH common search space) configured by an RRC message. The UE may identify the RAR based on a radio network temporary identifier (RNTI). The RNTI may be used depending on one or more events that initiate a random access procedure. The UE may use a random access RNTI (RA-RNTI). The RA-RNTI may be associated with the PRACH opportunity in which the UE transmits the preamble. For example, the UE may determine the RA-RNTI based on: an OFDM symbol index; a time slot index; a frequency domain index; and / or a UL carrier indicator of a PRACH opportunity. Examples of RA-RNTIs may be as follows:

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

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

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

[0175] Msg 4 1314 may be received after or in response to the transmission of Msg 3 1313. If a C-RNTI is included in Msg 3 1313, the base station will address the UE on the PDCCH using the C-RNTI. If a unique C-RNTI for the UE is detected on the PDCCH, it is determined that the random access procedure is successfully completed. If a TC-RNTI is included in Msg 3 1313 (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 identity MAC CE that matches or otherwise corresponds to the CCCH SDU sent (e.g., transmitted) in Msg 3 1313, the UE may determine that contention resolution is successful and / or the UE may determine that the random access procedure is successfully completed.

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

[0177] Fig. 13B A two-step contention-free random access procedure is shown. Fig.13A Similar to the four-step contention-based random access procedure shown, the base station may transmit a configuration message 1320 to the UE before the procedure is initiated. The configuration message 1320 may be similar to the configuration message 1310 in some aspects. Fig. 13B The illustrated procedure includes the transmission of two messages: Msg 1 1321 and Msg 2 1322. Msg 1 1321 and Msg 2 1322 may be similar in some respects to Fig.13A As shown in Msg 1 1311 and Msg 2 1312. Fig.13A and Fig. 13B It will be appreciated that the contention-free random access procedure may not include messages similar to Msg 3 1313 and / or Msg 4 1314 .

[0178] Can be initiated for beam failure recovery, other SI requests, SCell addition and / or handover Fig. 13B For example, the base station may indicate or assign a preamble to be used for Msg 1 1321 to the UE. The UE may receive an indication of the preamble (eg, ra-PreambleIndex) from the base station via PDCCH and / or RRC.

[0179] After transmitting the preamble, the UE may start a time window (e.g., ra-ResponseWindow) to monitor the PDCCH for the RAR. In the case of a beam failure recovery request, the base station may configure the UE with a separate time window and / or a separate PDCCH in the search space indicated by the RRC message (e.g., recoverySearchSpaceId). The UE may monitor PDCCH transmissions addressed to the Cell RNTI (C-RNTI) on the search space. Fig. 13B In the contention-free random access procedure shown, the UE may determine that the random access procedure is 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 is addressed to the C-RNTI, the UE may determine that the random access procedure is 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 the preamble identifier, the UE may determine that the random access procedure is successfully completed. The UE may determine that the response is an indication of a confirmation of the SI request.

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

[0181] Msg A 1331 may be transmitted by the UE in an uplink transmission. Msg A 1331 may include one or more transmissions of a preamble 1341 and / or one or more transmissions of a transport block 1342. Transport block 1342 may include Fig.13A The transmission block 1342 may include UCI (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 the same content as the content of Msg 3 1313 shown in FIG. Fig.13A and Fig. 13B Msg 2 1312 (eg, RAR) and / or Fig.13A The content of Msg 4 1314 shown is similar and / or identical.

[0182] The UE can initiate a call for licensed spectrum and / or unlicensed spectrum. Fig. 13C 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; the cell size; the RRC state of the UE; the type of spectrum (e.g., licensed vs. unlicensed); and / or any other suitable factors.

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

[0184] The transmission block 1342 may include data (e.g., delay-sensitive data), an identifier of the UE, security information, and / or device information (e.g., an International Mobile Subscriber Identity (IMSI)). The base station may transmit 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 high-level command; a power control command; an uplink grant (e.g., a radio resource assignment and / or MCS); a UE identifier for contention resolution; and / or an RNTI (e.g., a C-RNTI or a TC-RNTI). The UE may determine that the two-step random access procedure is successfully completed if the following conditions exist: the preamble identifier in Msg B 1332 matches the preamble transmitted by the UE; and / or the identifier of the UE in Msg B 1332 matches the identifier of the UE in Msg A 1331 (e.g., transmission block 1342).

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

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

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

[0188] DCI can be used for different 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 with a paging RNTI (P-RNTI) can indicate paging information and / or system information change notification. The P-RNTI can be predefined as hexadecimal "FFFE". A DCI with CRC parity bits scrambled with a system information RNTI (SI-RNTI) can indicate a broadcast transmission of system information. The SI-RNTI can be predefined as hexadecimal "FFFF". A DCI with CRC parity bits scrambled with a random access RNTI (RA-RNTI) can indicate a random access response (RAR). A DCI with CRC parity bits scrambled with a cell RNTI (C-RNTI) can indicate a dynamically scheduled unicast transmission and / or the triggering of a PDCCH ordered random access. A DCI with CRC parity bits scrambled with a temporary cell RNTI (TC-RNTI) can indicate contention resolution (e.g., similar to Fig.13AThe other RNTIs configured by the base station to the UE may include: a configured scheduling RNTI (CS-RNTI), a transmission power control PUCCH RNTI (TPC-PUCCH-RNTI), a transmission power control PUSCH RNTI (TPC-PUSCH-RNTI), a transmission power control SRS RNTI (TPC-SRS-RNTI), an interruption RNTI (INT-RNTI), a slot format indication RNTI (SFI-RNTI), a semi-persistent CSI RNTI (SP-CSI-RNTI), a modulation and coding scheme cell RNTI (MCS-C-RNTI), etc.

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

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

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

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

[0193] The base station may transmit an RRC message including configuration parameters of one or more CORESETs and one or more search space sets to the UE. The configuration parameters may indicate an association between a search space set and a CORESET. The search space set may include a set of PDCCH candidates formed by CCEs at a given aggregation level. The configuration parameters may indicate: the number of PDCCH candidates to be monitored for each aggregation level; the PDCCH monitoring period and the 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 may be predefined and known to the UE. The set of CCEs in the UE-specific search space set may be configured based on the UE's identity (e.g., C-RNTI).

[0194] like Fig. 14B As shown, the UE may determine the time-frequency resources of the CORESET based on the RRC message. The UE may determine the CCE to REG mapping of the CORESET based on the configuration parameters of the CORESET (e.g., interlaced or non-interlaced and / or mapping parameters). The UE may determine the number of search space sets configured on the CORESET based on the RRC message (e.g., up to 10). The UE may monitor a set of PDCCH candidates according to the configuration parameters of the search space set. The UE may monitor a set of PDCCH candidates in one or more CORESETs for detecting one or more DCIs. Monitoring may 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 positions, 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 may determine that the DCI is valid for the UE in response to a CRC check (e.g., scrambled bits of the CRC parity bits of the DCI matching the RNTI value). The UE may process the information contained in the DCI (e.g., scheduling assignments, uplink grants, power control, time slot format indications, downlink preemption, etc.).

[0195] The UE may transmit uplink control signaling (e.g., uplink control information (UCI)) to the base station. The uplink control signaling transmission may include a hybrid automatic repeat request (HARQ) confirmation for the received DL-SCH transport block. The UE may transmit the HARQ confirmation after receiving the DL-SCH transport block. The 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 may determine the transmission format parameters (e.g., including multiple antennas and beamforming schemes) for downlink transmission. The 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 confirmation (HARQ-ACK), CSI report, SR, etc.) via a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH). The UE may transmit uplink control signaling via PUCCH using one of several PUCCH formats.

[0196] There may be five PUCCH formats, and the UE may determine the PUCCH format based on the size of the UCI (e.g., the number of uplink symbols for UCI transmission and the number of UCI bits). PUCCH format 0 may have a length of one or two OFDM symbols and may include two or fewer bits. If the transmission exceeds one or two symbols and the number of HARQ-ACK information bits (HARQ-ACK / SR bits) with positive or negative SR is one or two, the UE may use PUCCH format 0 to transmit the UCI in the PUCCH resource. PUCCH format 1 may occupy between four and fourteen OFDM symbols and may 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 may use PUCCH format 1. PUCCH format 2 may occupy one or two OFDM symbols and may include more than two bits. If the transmission exceeds one or two symbols and the number of UCI bits is two or more, the UE may use PUCCH format 2. PUCCH format 3 may occupy between four and fourteen OFDM symbols and may include more than two bits. If four or more symbols are transmitted, the number of UCI bits is two or more, and the PUCCH resources do not include orthogonal cover codes, the UE may use PUCCH format 3. PUCCH format 4 may occupy between four and fourteen OFDM symbols and may include more than two bits. If four or more symbols are transmitted, the number of UCI bits is two or more, and the PUCCH resources include orthogonal cover codes, the UE may use PUCCH format 4.

[0197] The base station may transmit configuration parameters of multiple PUCCH resource sets to the UE using, for example, an RRC message. The multiple PUCCH resource sets (e.g., up to four sets) may be configured on the uplink BWP of the cell. The PUCCH resource set may be configured with: a PUCCH resource set index; multiple PUCCH resources having PUCCH resources identified by a PUCCH resource identifier (e.g., pucch-Resourceid); and / or multiple (e.g., maximum number) UCI ​​information bits that the UE may transmit using one of the multiple PUCCH resources in the PUCCH resource set. When multiple PUCCH resource sets are configured, the UE may 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 may select the 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 may select a second PUCCH resource set having 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 may select a third PUCCH resource set having 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 a third value (e.g., 1406), the UE may select a fourth PUCCH resource set having a PUCCH resource set index equal to "3".

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

[0199] Fig.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. Fig.15 Only one wireless device 1502 and one base station 1504 are shown in FIG. 1 , but it should be understood that the mobile communication network may include more than one UE and / or more than one base station, which have the same Fig.15 Configurations the same or similar to those shown.

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

[0201] In the downlink, data to be sent from base station 1504 to wireless device 1502 may be provided to processing system 1508 of base station 1504. The data may be provided to processing system 1508 via, for example, a core network. In the uplink, data to be sent from wireless device 1502 to base station 1504 may be provided to processing system 1518 of wireless device 1502. Processing system 1508 and processing system 1518 may implement layer 3 and layer 2 OSI functions to process data for transmission. Layer 2 may include, for example, information about Figure 2A , Figure 2B , Figure 3 and Figure 4A Layer 3 may include the following: Figure 2B RRC layer.

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

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

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

[0205] Processing system 1508 and processing system 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 codes that may be executed by processing system 1508 and / or processing system 1518 to perform one or more of the functions discussed herein. Fig.15 Not shown, transmit processing system 1510, transmit processing system 1520, receive processing system 1512, and / or receive 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 may be executed to perform one or more of their respective functions.

[0206] The processing system 1508 and / or the 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 device, discrete gate and / or transistor logic, discrete hardware components, on-board units, or any combination thereof. The processing system 1508 and / or the 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 functions that may enable the wireless device 1502 and the base station 1504 to operate in a wireless environment.

[0207] The processing system 1508 and / or the 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 the one or more peripheral devices 1526 may include software and / or hardware that provides features and / or functionality, such as a speaker, a microphone, a keyboard, a display, a touch pad, a power supply, a satellite transceiver, a universal serial bus (USB) port, a hands-free headset, a frequency modulation (FM) radio unit, a media player, an Internet browser, an electronic control unit (e.g., for a motor vehicle), and / or one or more sensors (e.g., an accelerometer, a gyroscope, a temperature sensor, a radar sensor, a lidar sensor, an ultrasonic sensor, a light sensor, a camera, etc.). The processing system 1508 and / or the 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 one or more peripheral devices. The processing system 1518 in the wireless device 1502 can receive power from the power source and / or can be configured to distribute power to other components in the wireless device 1502. The power source can include one or more power sources, such as batteries, solar cells, fuel cells, or any combination thereof. The processing system 1508 and / or the processing system 1518 can be connected to the GPS chipset 1517 and the GPS chipset 1527, respectively. The GPS chipset 1517 and the GPS chipset 1527 can be configured to provide the geographical location information of the wireless device 1502 and the base station 1504, respectively.

[0208] Fig.16AAn exemplary structure for uplink transmission is shown. The baseband signal representing the physical uplink shared channel can perform one or more functions. The one or more functions may include at least one of the following: scrambling; modulating scrambled bits to generate complex-valued symbols; mapping complex-valued modulated symbols to one or several transmission layers; transform precoding to generate complex-valued symbols; precoding of complex-valued symbols; mapping of precoded complex-valued symbols to resource elements; generating a complex-valued time-domain single carrier frequency division multiple access (SC-FDMA) or CP-OFDM signal for an antenna port; and the like. 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, the uplink transmission can be performed by Fig.16A Generate a CP-OFDM signal for uplink transmission. These functions are shown as examples, and it is contemplated that other mechanisms may be implemented in various embodiments.

[0209] Fig. 16B An exemplary structure for modulation and up-conversion of a baseband signal to a carrier frequency is shown. The baseband signal may be a complex-valued SC-FDMA or CP-OFDM baseband signal and / or a complex-valued physical random access channel (PRACH) baseband signal for an antenna port. Filtering may be employed prior to transmission.

[0210] Fig. 16C An exemplary structure for downlink transmission is shown. A baseband signal representing a physical downlink channel may perform one or more functions. The one or more functions may include: scrambling coded bits in a codeword to be transmitted on a physical channel; modulating the scrambled bits to generate complex-valued modulation symbols; mapping the complex-valued modulation symbols onto one or several transmission layers; precoding of complex-valued modulation symbols on layers for transmission on antenna ports; mapping complex-valued modulation symbols for antenna ports to resource elements; generating complex-valued time-domain OFDM signals for antenna ports; and the like. These functions are shown as examples, and it is contemplated that other mechanisms may be implemented in various embodiments.

[0211] Fig.16D Another exemplary structure for modulation and up-conversion of a baseband signal to a carrier frequency is shown. The baseband signal may be a complex valued OFDM baseband signal at an antenna port. Filtering may be employed prior to transmission.

[0212] The wireless device may receive one or more messages (e.g., RRC messages) including configuration parameters of multiple cells (e.g., primary cells, secondary cells) from a base station. The wireless device may communicate with at least one base station (e.g., two or more base stations in dual connectivity) via the 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, the configuration parameters may include parameters for configuring physical layer and MAC layer channels, bearers, and the like. For example, the configuration parameters may include parameters indicating values ​​of timers for the physical layer, MAC layer, RLC layer, PCDP layer, SDAP layer, RRC layer, and / or communication channels.

[0213] Once started, a timer can start running and continue running until it stops or until it expires. If the timer is not running, it can be started, or if it is running, it can be restarted. A timer can be associated with a value (e.g., a timer can start or restart from a certain value, or can start from zero and expire once it reaches the 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 for the time period / window of the measurement process. When the specification refers to implementations and procedures related to one or more timers, it should be understood that there are multiple ways to implement the one or more timers. For example, it should be understood that one or more of the multiple ways of implementing the timer can be used for the time period / window of the measurement procedure. For example, a random access response window timer can be used to measure the time window for receiving a random access response. In an example, instead of the start and expiration of the random access response window timer, the time difference between two timestamps can be used. When the timer is restarted, the measurement process of the time window can be restarted. Other exemplary embodiments can be provided to restart the measurement of the time window.

[0214] For example, the wireless device may receive one or more messages from a base station including one or more configuration parameters for a cell.

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

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

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

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

[0219] The one or more configuration parameters may indicate at least two TAGs for the cell. The at least two TAGs may include a first TAG and a second TAG.

[0220] In the prior art, one or more configuration parameters may indicate at least two TAGs for a cell, for example, for multi-TRP operation (e.g., inter-cell multi-TRP operation, intra-cell multi-TRP operation, etc.). Each of the at least two TAGs may be used for (or associated with) a corresponding TRP in a plurality of TRPs. For example, a first TAG of the at least two TAGs may be associated with a first TRP. A second TAG of the at least two TAGs may be associated with a second TRP.

[0221] For example, in an embodiment of the prior art, when the first time alignment timer of the first TAG of at least two TAGs of the cell expires / stops, the wireless device may not perform any uplink transmission via the cell based on the first time alignment timer of the first TAG including the cell expiring / stopping (or not running). This may be invalid when the cell is associated with at least two TAGs and the second time alignment timer of the second TAG of the at least two TAGs may be running. Stopping (or not performing) uplink transmission may reduce the data rate and increase the latency of communication. The wireless device may transmit an uplink signal based on the second TAG (or to / towards the second TRP) regardless of the expiration / stop of the first time alignment timer of the first TAG associated with the first TRP. The wireless device may transmit to the second TRP without increasing interference (e.g., inter-symbol interference and / or wireless devices in other cells).

[0222] The exemplary embodiment enhances uplink transmission when the cell is associated with at least two TAGs including a first TAG and a second TAG.

[0223] In an exemplary embodiment, the first time alignment timer of the first TAG may be running. When the second time alignment timer of the second TAG expires / stops, the wireless device may i) continue to transmit the first uplink signal associated with the first TAG via the cell, and ii) stop / suspend (or do not perform) the transmission of the second uplink signal associated with the second TAG via the cell.

[0224] In an exemplary embodiment, the second time alignment timer of the second TAG may be running. When the first time alignment timer of the first TAG expires / stops, the wireless device may i) continue to transmit the second uplink signal associated with the second TAG via the cell, and ii) stop / suspend (or do not perform) the transmission of the first uplink signal associated with the first TAG via the cell.

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

[0226] Exemplary embodiments may increase data rates and reduce latency of communications.

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

[0228] The exemplary embodiments enhance uplink transmission (eg, HARQ-ACK information feedback / bits) when the cell is associated with at least two TAGs including a first TAG and a second TAG.

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

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

[0231] Example embodiments may reduce latency for communications and reduce power consumption at wireless devices and / or base stations.

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

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

[0234] For a subcarrier spacing configuration μ (e.g., μ=0, 1, 2, 3, ...), the time slots may be numbered in ascending order within a subframe as and are numbered in ascending order within the frame In the time slot there can be consecutive OFDM symbols, where The time slot in a subframe may be based on / depends on a cyclic prefix (e.g., a normal cyclic prefix or an extended cyclic prefix). The start time can be the same as the OFDM symbol in the same subframe Startup alignment.

[0235] Transmissions (eg, downlink transmissions, uplink transmissions, and sidelink transmissions) may be organized into f =(Δf max N f / 100)·T c = 10ms duration frame. A frame can include T sf =(Δf max N f / 1000)·T c = ten subframes of 1 ms duration (or consisting of them). The number of consecutive OFDM symbols per subframe can be Each frame may be divided into two equally sized half-frames of five subframes each, where half-frame 0 consists of subframes 0-4 and half-frame 1 consists of subframes 5-9.

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

[0237] An uplink frame number i for transmission from a wireless device may be initiated before the corresponding downlink frame is initiated at the wireless device. in

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

[0239] - may be derived / determined by the wireless device from (or indicated to the wireless device by) higher layer (or RRC or configuration(s)) parameters TACommon, TACommonDrift and TACommonDriftVariation (if configured), otherwise It can be a timing correction controlled by the network.

[0240] - Can be calculated / determined by the wireless device based on higher layer (e.g., RRC or one or more configuration) parameters related to satellite ephemeris (if configured), otherwise It can be a UE derived timing correction.

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

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

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

[0244] The wireless device may 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., a TAG ID). The wireless device may receive the timing advance command, for example, via a cell associated with the TAG. The TAG may include at least one cell having the cell. The one or more cells may include at least one cell having the cell. The wireless device may, for example, based on the timing advance command, adjust / determine uplink timing for uplink transmission (e.g., PUCCH / PUSCH / SRS transmission) on / via each of the at least one cell in the TAG for uplink transmission. The wireless device may, for example, based on the timing advance command, adjust / determine uplink timing for uplink transmission (e.g., PUCCH / PUSCH / SRS transmission) on each of the at least one cell in the TAG for uplink transmission. The wireless device may, for example, based on the timing advance offset (e.g., N TA,offset ) to adjust / determine the uplink timing for uplink transmission on / via each of the at least one cell in the TAG based on the value (or default value) of the timing advance offset. In an example, the value (or default value) of the timing advance offset may be the same for each of the at least one cell in the TAG. In an example, the uplink timing may be the same for each of the at least one cell in the TAG. In an example, the uplink timing of uplink transmissions (e.g., PUCCH / PUSCH / SRS transmissions) may be the same for each of the at least one cell.

[0245] For 2 μ .15kHz subcarrier spacing (SCS), a timing advance command received by a wireless device for a TAG in one or more TAGs may be received at 16.64.T c / 2 μ The multiple of indicates the change in uplink timing relative to the current uplink timing for the TAG.

[0246] The wireless device may receive a timing advance command (eg, T A ).

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

[0248] In an example, the timing advance command MAC CE may indicate / include a timing advance command. The wireless device may receive the timing advance command in the timing advance command MAC CE. The timing advance command may be indicated by an index value (e.g., T A =0, 1, 2, ..., 63) indicates the current timing advance value N TA_old To the new timing advance value N TA_new Adjustment. For 2 μ ·15kHz SCS, the wireless device can determine the new timing advance value as N TA_new =N TA_old +(T A -31)·16·64 / 2 μ .

[0249] Each cell of at least one cell in 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 of at least one cell may include a first uplink carrier (e.g., NUL). A second cell of at least one cell may include a second uplink carrier (e.g., SUL). A third cell of at least one cell may include a first uplink carrier (e.g., NUL) and a second uplink carrier (e.g., SUL). The wireless device may be active in a plurality of uplink BWPs of / for one or more uplink carriers of at least one cell in the TAG (or may activate a plurality of uplink BWPs of / for one or more uplink carriers of at least one cell in the TAG). The wireless device may be active in a corresponding uplink BWP of a plurality of uplink BWPs of one or more uplink carriers of each cell in the at least one cell (or may activate a corresponding uplink BWP of a plurality of uplink BWPs of one or more uplink carriers of each cell in the at least one cell). The 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 maximum SCS among the multiple uplink BWPs / the maximum SCS among them. The new timing advance value (e.g., N ... TA_new ) can be rounded by the wireless device to align with the timing advance granularity for uplink BWP with lower SCS.

[0250] Set the timing advance value (for example, N TA ) A positive or negative adjustment may indicate that the uplink transmission timing to be used for the TAG is advanced or delayed by a corresponding amount, respectively.

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

[0252] The wireless device may change an active uplink BWP of a cell in at least one of the cells in the TAG. The wireless device may activate (or switch to a new uplink BWP for the cell) based on changing the active uplink BWP. The wireless device may change the active uplink BWP between a first time of receiving a timing advance command and a second time of applying the adjustment of the uplink transmission timing. Based on changing the active uplink BWP between the first time and the second time, the wireless device may determine a value of the timing advance command (or a timing advance value) based on an SCS of the new active ULBWP. The wireless device may change the active uplink BWP after the second time. The wireless device may determine / assume the same absolute value for the timing advance command (or the same absolute timing advance value) before and after the change of the active uplink BWP.

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

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

[0255] The wireless device may, for example, receive one or more messages including one or more configuration parameters (e.g., RRC configuration parameters, RRC reconfiguration parameters) from a base station. 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 a TAG configuration (e.g., tag-Config). The TAG configuration may be used by the wireless device and / or the base station to configure parameters for the time alignment group. The TAG configuration 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.).

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

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

[0258] One or more configuration parameters may indicate a TAG index in one or more TAG indexes for a cell. A TAG index may indicate / identify a TAG in one or more TAGs. One or more configuration parameters may include one or more serving cell configuration parameters (e.g., ServingCellConfig) of a cell. One or more serving cell configuration parameters of a cell may include / indicate a TAG index, which TAG index indicates / identifies a TAG index of a TAG. For example, based on one or more configuration parameters indicating a TAG index for a cell (TAG index indicating / identifying 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 a cell (TAG index indicating / identifying TAG), a TAG may include (or may be associated with or may correspond to) a cell.

[0259] The wireless device may be able to handle the relative transmission timing difference between the subframe timing boundary of the E-UTRA PCell and the closest slot timing boundary of the PSCell to be aggregated for EN-DC operation.

[0260] The wireless device may be able to handle relative transmission timing differences between the closest slot timing boundaries of different carriers to be aggregated in the NR carrier aggregation.

[0261] The wireless device may be able to handle the relative transmission timing difference between the slot timing boundary of the PCell and the subframe timing boundary of the E-UTRA PSCell to be aggregated for NE-DC operation.

[0262] The wireless device may be able to handle the relative transmission timing difference between the slot timing boundary of the PCell and the closest slot timing boundary of the PSCell to be aggregated in NR DC operation.

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

[0264] The one or more TAGs may include a first TAG and a second TAG.

[0265] The first TAG may be / operate in FR1. The second TAG may be / operate in FR1. The maximum uplink transmission time difference between the first TAG and the second TAG may be 34.6 microseconds ( / mu).

[0266] The first TAG may be / operate in FR2. The second TAG may be / operate in FR2. The maximum uplink transmission time difference between the first TAG and the second TAG may be 8.5 microseconds ( / mu). The wireless device may be capable of independent beam management for FR2 inter-band carrier aggregation.

[0267] In an example, the first TAG may be / operating in FR1 and the second TAG may be / operating in FR2. In an example, the first TAG may be / operating in FR2 and the second TAG may be / operating in FR1. The maximum uplink transmission time difference between the first TAG and the second TAG may be 26.1 microseconds ( / mu).

[0268] In RRC_CONNECTED, the base station may maintain timing advance to keep the layer 1 (L1) of the wireless device synchronized. Serving cells having / with the same timing advance applied to the uplink and using the same timing reference cell may be grouped by the base station in a TAG in one or more TAGs. Each TAG in the one or more TAGs may contain / include at least one serving cell configured with an uplink. The mapping of each serving cell to the (corresponding) TAG may be configured / indicated by an RRC configuration parameter (e.g., tag-Id).

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

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

[0271] The wireless device may transmit / report a user equipment (UE) capability message (e.g., UE capability information) to the base station. The wireless device may transmit / report the UE capability message to the base station, for example, based on receiving a UE capability query / request from the base station. The base station may request the wireless device to send / transmit the UE capability message via / through the UE capability query / request. The UE capability message (or UE capability information) may be an RRC message that the wireless device transmits / sends / reports to the base station. The wireless device may transmit the UE capability message, for example, during an initial registration procedure.

[0272] The UE capability message may indicate the supported number of TAGs (supportedNumberTAG). The UE capability message may include a carrier aggregation (CA) parameter indicating / including the supported number of TAGs by the wireless device. The supported number of TAGs may be applied by the wireless device and / or the base station for NR CA, NR-DC, (NG) EN-DC / NE-DC and DAPS switching.

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

[0274] For inter-frequency DAPS, the supported number of TAGs may be two. The wireless device may be forced to support 2 TAGs for inter-frequency DAPS. For mixed inter-band and intra-band NR CA / NR-DC band combinations, if the base station configures more non-contiguous uplink serving cells than the supported number of TAGs, for example, through one or more configuration parameters, then the one or more configuration parameters indicate the same TAG (or the same TAG Id / index) for one or more uplink serving cells of the same band.

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

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

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

[0278] The TAG of the SpCell including / containing the MAC entity of the wireless device may be referred to as a Primary Timing Advance Group (PTAG). The TAG of the SpCell not including / containing the MAC entity of the wireless device may be referred to as a Secondary Timing Advance Group (STAG).

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

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

[0281] One or more TAGs may include a PTAG. A PTAG may include a SpCell (eg, a PCell).

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

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

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

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

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

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

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

[0289] The wireless device may stop the time alignment timer associated with the TAG including the cell. For example, if contention resolution of a random access procedure (or a contention-based random access procedure) is unsuccessful (or not successful), the wireless device may stop the time alignment timer.

[0290] The wireless device may stop a time alignment timer associated with a TAG including a cell. For example, based on HARQ feedback for a MAC PDU transmission containing / including a UE contention resolution identity MAC CE, the wireless device may stop the time alignment timer. Contention resolution for a random access procedure (or contention-based random access procedure) may be successful. The wireless device may initiate a random access procedure (or transmit a random access preamble) for a system information (SI) request.

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

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

[0293] The one or more configuration parameters may indicate a time alignment timer in one or more time alignment timers for a TAG in one or more TAGs. The time alignment timer may expire.

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

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

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

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

[0298] clearing any configured downlink assignments and configured uplink grants;

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

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

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

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

[0303] Flush all HARQ buffers;

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

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

[0306] clearing any configured downlink assignments and configured uplink grants;

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

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

[0309] In an example, the maximum uplink transmission time difference between the first TAG and the second TAG may be exceeded. One or more TAGs may include a first TAG and a second TAG. The wireless device (or a MAC entity of the wireless device) may stop / suspend uplink transmission via / for a cell (e.g., SCell). For example, based on the maximum uplink transmission time difference between the first TAG and the second TAG being exceeded, the wireless device (or the MAC entity of the wireless device) may stop / suspend uplink transmission via / for a cell. The TAG in one or more TAGs may include the cell. For example, the TAG may be different from the first TAG. The TAG may be different from the second TAG. For example, the TAG may be the first TAG. For example, the TAG may be the second TAG. One or more configuration parameters may indicate a time alignment timer in one or more time alignment timers for a TAG in one or more TAGs. The wireless device may determine / assume / consider the time alignment timer of the TAG associated with the cell to be expired. For example, based on the maximum uplink transmission timing difference between the first TAG and the second TAG being exceeded, the wireless device may determine / assume / consider the time alignment timer of the TAG associated with the cell to be expired.

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

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

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

[0313] The Timing Advance Command MAC CE may be identified by a MAC subheader with an LCID (eg, 61). The Timing Advance Command MAC CE may have a fixed size. The Timing Advance Command MAC CE may include a single octet.

[0314] The timing advance command MAC CE may include one or more fields.

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

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

[0317] The Absolute Timing Advance Command MAC CE may be identified by a MAC subheader with an LCID. The Absolute Timing Advance Command MAC CE may have a fixed size. The Absolute Timing Advance Command MAC CE may include two octets.

[0318] The Absolute Timing Advance Command MAC CE may include one or more fields.

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

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

[0321] The wireless device may receive the DCI. The wireless device may receive the DCI in / via a PDCCH monitoring opportunity (or PDCCH opportunity). The wireless device may monitor the downlink control channel in the PDCCH monitoring opportunity for the DCI.

[0322] For example, the DCI may include / indicate a downlink assignment.

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

[0324] The one or more configuration parameters may indicate a configured downlink assignment (eg, an SPS PDSCH configuration). The wireless device may receive one or more SPS PDSCHs (or one or more SPS PDSCH receptions) for the configured downlink assignment.

[0325] In an example, the DCI may indicate SPS deactivation / release. The DCI may include a new data indicator (NDI) field. The value of the NDI field may be, for example, equal to zero. The DCI may include one or more fields (e.g., RV, HARQ, TDRA, FDRA) set to predefined values ​​indicating SPS deactivation. For example, based on receiving a DCI indicating SPS deactivation, the wireless device may clear the configured downlink assignment. For example, based on clearing the configured downlink assignment, the wireless device may not receive one or more SPS PDSCHs (or one or more SPS PDSCH receptions) for the configured downlink assignment. The DCI may or may not schedule PDSCH reception.

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

[0327] In an example, the DCI may schedule PDSCH reception (or transport block).The wireless device may transmit (or determine to transmit) HARQ-ACK information feedback / bits for PDSCH reception (or for reception of a transport block).

[0328] In an example, the DCI may indicate SCell dormancy for one or more cells. The wireless device may transmit (or determine to transmit) HARQ-ACK information feedback / bit for SCell dormancy. The wireless device may transmit HARQ-ACK information feedback / bit, for example, to confirm receipt of the DCI indicating SCell dormancy. The DCI may or may not schedule PDSCH reception.

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

[0330] The wireless device may transmit HARQ-ACK information feedback / bit via the cell. One or more configuration parameters may indicate a TAG in one or more TAGs for the cell. The TAG may include a cell. The cell may belong to a TAG. One or more configuration parameters may indicate a time alignment timer in one or more time alignment timers for the TAG including the cell.

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

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

[0333] A positive acknowledgement may be, for example, for SPS deactivation. A positive acknowledgement may be, for example, for PDSCH reception scheduled by DCI. A positive acknowledgement may be, for example, for SCell dormancy. A positive acknowledgement may be, for example, for TCI status update.

[0334] In an example, the time alignment timer may not be running (or may be stopped or may expire).

[0335] The wireless device (or the MAC layer of the wireless device) may not command the physical layer of the wireless device to generate an acknowledgement (e.g., a positive acknowledgement or a negative acknowledgement). For example, based on the time alignment timer not running, the wireless device (or the MAC layer of the wireless device) may not command the physical layer of the wireless device to generate an acknowledgement. For example, based on the time alignment timer being running, the wireless device (or the physical layer of the wireless device) may not transmit an acknowledgement via the cell. For example, based on the time alignment timer being running, the wireless device (or the physical layer of the wireless device) may not transmit HARQ-ACK information feedback / bits via the cell.

[0336] For example, based on the time alignment timer not running (or being stopped or expired), the wireless device (or the MAC layer of the wireless device) may not command the physical layer of the wireless device to generate a confirmation for SPS deactivation. For example, based on the time alignment timer not running (or being stopped or expired), the wireless device (or the MAC layer of the wireless device) may not command the physical layer of the wireless device to generate a confirmation for PDSCH reception scheduled by DCI. For example, based on the time alignment timer not running (or being stopped or expired), the wireless device (or the MAC layer of the wireless device) may not command the physical layer of the wireless device to generate a confirmation for SCell dormancy. For example, based on the time alignment timer not running (or being stopped or expired), the wireless device (or the MAC layer of the wireless device) may not command the physical layer of the wireless device to generate a confirmation for TCI status update.

[0337] HARQ-ACK information feedback / bit may be, for example, for SPS deactivation. HARQ-ACK information feedback / bit may be, for example, for PDSCH reception scheduled by DCI. HARQ-ACK information feedback / bit may be, for example, for SCell dormancy. HARQ-ACK information feedback / bit may be, for example, for TCI status update.

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

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

[0340] In an example, the wireless device may receive one or more messages. In an example, the wireless device may receive one or more messages from a base station. In an example, the wireless device may receive one or more messages from a relay node. In an example, the wireless device may receive one or more messages from another wireless device (e.g., a TRP, a vehicle, a remote radio head, etc.). The one or more messages may include one or more configuration parameters (e.g., Fig.17In an example, the one or more configuration parameters may be RRC configuration parameters. In an example, the one or more configuration parameters may be RRC reconfiguration parameters.

[0341] In an example, one or more configuration parameters may be for one or more cells.

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

[0343] In an example, the wireless device may perform uplink transmission (e.g., PUSCH, PUCCH, PUCCH) of / via a cell at a first time and at a first frequency. The wireless device may perform downlink reception (e.g., PDCCH, PDSCH) of / via a cell at a second time and at a second frequency. In an example, the cell may operate in a time division duplex (TDD) mode. In the TDD mode, the first frequency and the second frequency may be the same. In the TDD mode, the first time and the second time may be different. In an example, the cell may operate in a frequency division duplex (FDD) mode. In the FDD mode, the first frequency and the second frequency may be different. In the FDD mode, the first time and the second time may be the same.

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

[0345] In an example, a cell may include multiple BWPs. The multiple BWPs may include one or more uplink BWPs, the one or more uplink BWPs including the uplink BWP of the cell. The multiple BWPs may include one or more downlink BWPs, the one or more downlink BWPs including the downlink BWP of the cell.

[0346] In an example, a BWP in the plurality of BWPs may be in one of an active state and an inactive state. In an example, in the active state of a downlink BWP in the one or more downlink BWPs, the wireless device may monitor downlink channels / signals (e.g., PDCCH, DCI, CSI-RS, PDSCH) on / for / via the downlink BWP. In an example, in the active state of a downlink BWP in the one or more downlink BWPs, the wireless device may receive PDSCH on / via / for the downlink BWP. In an example, in the inactive state of a downlink BWP in the one or more downlink BWPs, the wireless device may not monitor downlink channels / signals (e.g., PDCCH, DCI, CSI-RS, PDSCH) on / via / for the downlink BWP. In the inactive state of a downlink BWP in the one or more downlink BWPs, the wireless device may stop monitoring (or receiving) downlink channels / signals (e.g., PDCCH, DCI, CSI-RS, PDSCH) on / via / for the downlink BWP. In an example, in an inactive state of a downlink BWP in one or more downlink BWPs, the wireless device cannot receive PDSCH on / via / for the downlink BWP. In an inactive state of a downlink BWP in one or more downlink BWPs, the wireless device may stop receiving PDSCH on / via / for the downlink BWP.

[0347] In an example, in an active state of an uplink BWP among the one or more uplink BWPs, the wireless device may transmit uplink signals / channels (e.g., PUCCH, preamble, PUSCH, PRACH, PUCCH, etc.) on / via the uplink BWP. In an example, in an inactive state of an uplink BWP among the one or more uplink BWPs, the wireless device may not transmit uplink signals / channels (e.g., PUCCH, preamble, PUSCH, PRACH, PUCCH, etc.) on / via the uplink BWP.

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

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

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

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

[0352] One or more configuration parameters may indicate the subcarrier spacing (or parameter set) for the downlink BWP.

[0353] One or more configuration parameters may indicate the subcarrier spacing (or parameter set) for uplink BWP.

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

[0355] In an example, one or more configuration parameters may indicate a plurality of control resource sets (coresets). One or more configuration parameters may indicate a plurality of coresets for an (active) downlink BWP of a cell. An (active) downlink BWP may include a plurality of coresets.

[0356] In an example, one or more configuration parameters may indicate multiple coreset indexes / identifiers / indicators for multiple coresets (e.g., provided by a higher layer parameter ControlResourceSetId). In an example, each coreset in the multiple coresets may be identified / indicated by a corresponding coreset index in the multiple coreset indexes. In an example, a first coreset in the multiple coresets may be identified by a first coreset index in the multiple coreset indexes. A second coreset in the multiple coresets may be identified by a second coreset index in the multiple coreset indexes.

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

[0358] In an example, one or more configuration parameters may not indicate a coreset pool index for a coreset in a plurality of coresets. A higher-layer parameter CoresetPoolIndex may not be in the configuration parameters of a coreset. The wireless device may determine the value (or default value) of the coreset pool index of / for a coreset as a first coreset pool index (CoresetPoolIndex=0). For example, based on one or more configuration parameters not indicating a coreset pool index for a coreset, the wireless device may determine the value (or default value) of the coreset pool index of / for a coreset as a first coreset pool index. For example, based on one or more configuration parameters not indicating a coreset pool index for a coreset, the first coreset pool index (CoresetPoolIndex=0) may be the coreset pool index of a coreset.

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

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

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

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

[0363] In an example, the first coreset pool index of the first coreset and the second coreset pool index of the second coreset may be different. Multiple coresets may include the first coreset and the second coreset. One or more coreset pool indexes may include the first coreset pool index and the second coreset pool index. Based on the first coreset pool index of the first coreset and the second coreset pool index of the second coreset being different, the wireless device may group the first coreset and the second coreset into different coreset pools. In an example, the wireless device may group the first coreset in a first coreset pool (e.g., CoresetPoolIndex=0). Based on the first coreset pool index and the second coreset pool index being different, the wireless device may group the second coreset in a second coreset pool (e.g., CoresetPoolIndex=1) that is different from the first coreset pool. Based on the first coreset pool index of the first coreset and the second coreset pool index being different, the first coreset pool and the second coreset pool may be different.

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

[0365] In one example, a cell may include multiple transmission and reception points (TRPs). Multiple TRPs may serve the cell (or may serve wireless devices in / via the cell / serve wireless devices of the cell). Multiple TRPs may include a first TRP and a second TRP.

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

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

[0368] In an example, one or more configuration parameters may indicate a plurality of uplink resources (e.g., PUCCH-Resource, SRS-Resource, etc.). One or more configuration parameters may indicate a plurality of uplink resources for an (active) uplink BWP of a cell. An (active) uplink BWP may include a plurality of uplink resources. An (active) uplink BWP of an uplink carrier (e.g., NUL, SUL) of a cell may include a plurality of uplink resources.

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

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

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

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

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

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

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

[0376] In one example, a cell may include multiple transmission and reception points (TRPs). Multiple TRPs may serve the cell (or may serve wireless devices in / via the cell / serve wireless devices of the cell). Multiple TRPs may include a first TRP and a second TRP.

[0377] The first TRP may receive an uplink signal / transmission (e.g., PUSCH, PUCCH, SRS, UCI, PRACH) via a first uplink resource having (e.g., configured with or associated with) a first coreset pool index among multiple uplink resources. The first TRP may not receive an uplink signal / transmission (e.g., PUSCH, PUCCH, SRS, UCI, PRACH) via a second uplink resource having (e.g., configured with or associated with) a second coreset pool index among multiple uplink resources.

[0378] The second TRP may receive an uplink signal / transmission (e.g., PUSCH, PUCCH, SRS, UCI, PRACH) via a second uplink resource having (e.g., configured with or associated with) a second coreset pool index among the multiple uplink resources. The second TRP may not receive an uplink signal / transmission (e.g., PUSCH, PUCCH, SRS, UCI, PRACH) via a first uplink resource having (e.g., configured with or associated with) a first coreset pool index among the multiple uplink resources.

[0379] In an example, one or more configuration parameters may indicate one or more uplink resource indexes for one or more uplink resource groups / sets (e.g., provided by a higher layer parameter CoresetPoolIndex). In an example, each uplink resource group / set in one or more uplink resource groups / sets may include (or be configured / indicated by one or more configuration parameters) a corresponding coreset pool index in one or more coreset pool indexes (e.g., 0, 1). One or more configuration parameters may indicate a corresponding coreset pool index in one or more coreset pool indexes for each uplink resource group / set in one or more uplink resource groups / sets. For example, one or more configuration parameters may indicate a first coreset pool index (CoresetPoolIndex=0) for a first uplink resource group / set in one or more multiple uplink resource groups / sets. One or more configuration parameters may indicate a second coreset pool index (CoresetPoolIndex=1) for a second uplink resource group / set in one or more uplink resource groups / sets. One or more coreset pool indexes may include a first coreset pool index and a second coreset pool index.

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

[0381] In an example, one or more configuration parameters may indicate at least two coreset pool indexes (e.g., 0 and 1) for a higher layer parameter CORESETPoolIndex. One or more configuration parameters may include a higher layer parameter CORESETPoolIndex having (or set to) at least two coreset pool indexes. In an example, at least two coreset pool indexes may include a first coreset pool index (e.g., 0) for / for one or more first uplink resource groups / sets in one or more uplink resource groups / sets. At least two coreset pool indexes may include a second coreset pool index (e.g., 1) different from the first coreset pool index for / for one or more second uplink resource groups / sets in one or more uplink resource groups / sets. One or more first uplink resource groups / sets may include one or more third uplink resource groups / sets in one or more uplink resource groups / sets without a value for the higher layer parameter CORESETPoolIndex. The one or more configuration parameters may not include a higher layer parameter CORESETPoolIndex for the one or more third uplink resource groups / sets.

[0382] In one example, a cell may include multiple transmission and reception points (TRPs). Multiple TRPs may serve the cell (or may serve wireless devices in / via the cell / serve wireless devices of the cell). Multiple TRPs may include a first TRP and a second TRP.

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

[0384] The second TRP may receive uplink signals / transmissions (e.g., PUSCH, PUCCH, SRS, UCI, PRACH) via a second uplink resource group / set / uplink resources therein having (e.g., configured with or associated with) a second coreset pool index in one or more uplink resource groups / sets. The second TRP may not receive uplink signals / transmissions (e.g., PUSCH, PUCCH, SRS, UCI, PRACH) via a first uplink resource group / set / uplink resources therein having (e.g., configured with or associated with) a first coreset pool index in one or more uplink resource groups / sets.

[0385] The wireless device may transmit an uplink signal / transmission (eg, a PUSCH / PUCCH / SRS transmission) via the uplink resources. The plurality of uplink resources may include an uplink resource. An uplink resource group / set in one or more uplink resource groups / sets may include an uplink resource.

[0386] The wireless device may receive downlink control information (DCI) that schedules / trigger / indicates the transmission of an uplink signal / transmission via a coreset in a plurality of coresets. The DCI may schedule / trigger / indicate the transmission of an uplink signal / transmission via uplink resources. The DCI may indicate uplink resources. The DCI may include a field indicating uplink resources.

[0387] For example, the uplink signal / transmission may be a PUSCH transmission (eg, a transport block). The uplink resources may be PUCCH resources. The DCI may schedule the transmission of a PUSCH transmission.

[0388] For example, the uplink signal / transmission may be a PUCCH transmission (e.g., HARQ-ACK information feedback). The uplink resource may be a PUCCH resource. The DCI may schedule the reception of a transport block (or PDSCH reception). The uplink signal / transmission may be HARQ-ACK information feedback for a transport block.

[0389] For example, the uplink signal / transmission may be an SRS. The uplink resource may be an SRS resource. The DCI may schedule the transmission of the SRS. The SRS may be, for example, an aperiodic SRS.

[0390] The coreset for receiving DCI by the wireless device may be associated with a coreset pool index. One or more coreset pool indexes may include a coreset pool index. For example, one or more configuration parameters may indicate a coreset pool index for a coreset. For example, one or more configuration parameters may not indicate a coreset pool index for a coreset (CoresetPoolIndex=0 or CoresetPoolIndex=1). For example, based on one or more configuration parameters not indicating a coreset pool index for a coreset, the value (or default value) of the coreset pool index of the coreset may be equal to the first coreset pool index (CoresetPoolIndex=0).

[0391] The uplink resources may be associated with a coreset pool index. For example, the uplink resources may be associated with a coreset pool index based on receiving a DCI scheduling / triggering / indicating transmission of an uplink signal / transmission via the uplink resources via a coreset associated with the coreset pool index.

[0392] An uplink resource group / set including uplink resources may be associated with a coreset pool index. For example, based on receiving a DCI for scheduling / triggering / indicating the transmission of an uplink signal / transmission via uplink resources in an uplink resource group / set (belonging to the uplink resource group / set) via a coreset associated with the coreset pool index, the uplink resource group / set may be associated with the coreset pool index. An uplink resource group / set may include one or more uplink resources having uplink resources. For example, based on an uplink resource group / set including one or more uplink resources being associated with a coreset pool index, one or more uplink resources may be associated with the coreset pool index. For example, based on an uplink resource group / set being associated with a coreset pool index, each of the one or more uplink resources may be associated with a coreset pool index.

[0393] The uplink signal / transmission may be associated with a coreset pool index. For example, the uplink signal / transmission may be associated with a coreset pool index based on receiving a DCI scheduling / triggering / indicating transmission of the uplink signal / transmission via a coreset associated with the coreset pool index.

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

[0395] The one or more configuration parameters may include corresponding usage parameters for each of the at least two SRS resource sets.

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

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

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

[0399] In an example, the first SRS resource set index of the first SRS resource set may be lower / smaller than the second SRS resource set index of the second SRS resource set.

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

[0401] The DCI that schedules / activates the transmission of repetitions of an uplink signal / transmission may include an SRS resource set indicator field. The length / size of the SRS resource set indicator field may be 2 bits.

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

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

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

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

[0406] In response to the SRS resource set indicator field being equal to / set to a second value (e.g., 00), the wireless device may transmit a repetition of an uplink signal / transmission based on the first SRS resource set. In response to the SRS resource set indicator field being equal to / set to a second value (e.g., 00), the wireless device may not transmit a repetition of the repetition of an uplink signal / transmission based on the second SRS resource set.

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

[0408] In response to the SRS resource set indicator field being equal to / set to a third value (e.g., 01), the wireless device may transmit a repetition of an uplink signal / transmission based on a second SRS resource set. In response to the SRS resource set indicator field being equal to / set to a third value (e.g., 01), the wireless device may not transmit a repetition of the repetition of an uplink signal / transmission based on a first SRS resource set.

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

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

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

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

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

[0414] An uplink signal / transmission may include one or more data layers / streams.

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

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

[0417] The wireless device may transmit an uplink signal / transmission based on a first SRS resource set. The wireless device may transmit an uplink signal / transmission based on a first SRS resource in a second SRS resource set. One or more configuration parameters may indicate a first SRS port number (e.g., nrofSRS-Ports) for a first SRS resource. The wireless device may, for example, transmit an uplink signal / transmission based on a first SRS port number of a first SRS resource in a first SRS resource set. For example, the wireless device may transmit an uplink signal / transmission using a first transmission precoder determined based on the first SRS port number. For example, the wireless device may transmit an uplink signal / transmission using a first spatial domain transmission filter / beam determined based on the first SRS resource.

[0418] In response to the SRS resource set indicator field being equal to / set to the second value (eg, 00), the wireless device may transmit an uplink signal / transmission based on the first SRS resource set.

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

[0420] In response to the SRS resource set indicator field being equal to / set to a third value (eg, 01), the wireless device may transmit an uplink signal / transmission based on the second SRS resource set.

[0421] The one or more configuration parameters may indicate multiple TCI states (eg, DL-orJoint-TCIState). The one or more configuration parameters may include, for example, one or more PDSCH configuration parameters indicating multiple TCI states.

[0422] The one or more configuration parameters may include, for example, one or more PDSCH configuration parameters for a downlink BWP of a cell. The one or more configuration parameters indicate a plurality of TCI states for a downlink BWP of a cell.

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

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

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

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

[0427] The one or more configuration parameters may indicate a second plurality of TCI states (eg, UL-TCIState). The one or more configuration parameters may include, for example, one or more uplink BWP configuration parameters indicating a second plurality of TCI states.

[0428] The one or more configuration parameters may include, for example, one or more uplink BWP configuration parameters for an uplink BWP of the cell. The one or more configuration parameters indicate a second plurality of TCI states for an uplink BWP of the cell.

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

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

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

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

[0433] In an example, for example, based on a reference unified TCI state list parameter indicating a second downlink BWP of a second cell for a downlink BWP of a cell, the wireless device may receive multiple TCI states using the second downlink BWP of the second cell for a downlink via the downlink BWP of the cell.

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

[0435] In an example, the wireless device may use the second plurality of TCI states for uplink transmission reception via the uplink BWP of the cell, eg, based on one or more configuration parameters indicating a second plurality of TCI states for the uplink BWP of the cell.

[0436] In an example, for example, based on a reference unified TCI state list parameter indicating a second uplink BWP for a cell, the wireless device may receive a second plurality of TCI states using the second uplink BWP of the second cell for uplink transmissions via the uplink BWP of the cell.

[0437] The one or more configuration parameters may indicate a physical cell index / identity / identifier (PCI) for a cell.

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

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

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

[0441] The at least one cell may be, for example, at least one non-serving cell. The at least one cell may be, for example, at least one neighboring cell. The at least one cell may be, for example, at least one candidate / secondary cell.

[0442] The maximum size / length of the list of PCI sets may be equal to a value (eg, 7).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0458] In an example, the wireless device may receive a control command (eg, MAC-CE, DCI, downlink control command, unified TCI state activate / deactivate MAC CE, etc.).

[0459] For example, the control command may indicate activation of a subset of TCI states among multiple TCI states (eg, DLorJoint-TCIState).

[0460] For example, the control command may indicate activation of a subset of TCI states among multiple TCI states (eg, UL-TCIState).

[0461] The wireless device may map a subset of TCI states to one or more TCI code points. The wireless device may 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 may indicate a subset of TCI states. Each TCI code point in the one or more TCI code points may indicate a corresponding TCI state in a subset of TCI states. Each TCI code point in the one or more TCI code points may indicate / include one or more TCI code points. For example, a subset of TCI states may be / include TCI state 1, TCI state 5, TCI state 8, TCI state 23, TCI state 34, and TCI state 48. One or more TCI code points may be / include a first TCI code point, a second TCI code point, a third TCI code point, and a fourth TCI code point. The first TCI code point may include / indicate TCI state 5. The second TCI code point may include / indicate TCI state 8 and TCI state 48. The third TCI code point may include / indicate TCI state 1 and TCI state 23. The fourth TCI code point may include / indicate TCI state 34.

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

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

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

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

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

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

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

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

[0470] The control command may indicate a list / set / vector of at least two TCI states in a TCI code point / map the list / set / vector of at least two TCI states to a TCI code point / activate a list / set / vector of at least two TCI states for a TCI code point. The control command may indicate a mapping / association / activation of a list / set / vector of at least two TCI states to / for a TCI code point. The at least two TCI states may include a first TCI state and a second TCI state. The first TCI state may be the first to appear in the list / set / vector of at least two TCI states. The first TCI state may be the first / starting / earliest / initial TCI state in the list / set / vector of at least two TCI states. The second TCI state may be the second to appear in the list / set / vector of at least two TCI states. The second TCI state may be the last / latest / ending TCI state in the list / set / vector of at least two TCI states.

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

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

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

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

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

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

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

[0478] The wireless device may transmit a second uplink signal / transmission (eg, PUSCH / PUCCH / SRS transmission, transport block, UCI, etc.) based on the second TCI state.

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

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

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

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

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

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

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

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

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

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

[0489] For example, in Fig.18 In the example, the multiple TAGs include TAG 0, TAG 1, and TAG 2. The one or more cells (or a subset of cells) include cell 1, cell 2, cell 3, cell 4, and cell 5. For example, in Fig.17, TAG-ID 0 may indicate / identify TAG0, TAG-ID 1 may indicate / identify TAG 1, and TAG-ID 2 may indicate / identify TAG 2. One or more configuration parameters indicate TAG 0 for cell 1 (or TAG-ID 0 indicating / identifying TAG 0). One or more configuration parameters indicate TAG 0 and TAG 2 for cell 2 (or TAG-ID 0 indicating / identifying TAG 0 and TAG-ID 2 indicating / identifying TAG 2). One or more configuration parameters indicate TAG 1 for cell 3 (or TAG-ID 1 indicating / identifying TAG 1). One or more configuration parameters indicate TAG 1 for cell 4 (or TAG-ID 1 indicating / identifying TAG 1). One or more configuration parameters indicate TAG 1 and TAG 2 for cell 5 (or TAG-ID 1 indicating / identifying TAG 1 and TAG-ID 2 indicating / identifying TAG 2).

[0490] The one or more configuration parameters may indicate at least two TAGs of the plurality of TAGs for the cell. The at least two TAGs may include a first TAG and a second TAG.

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

[0492] For example, in Fig.18 In the example, the cell may be cell 2. The at least two TAGs are TAG 0 and TAG 2. Fig.17 In , the list / set / vector of at least two TAG indexes for cell 2 is {TAG-ID 0, TAG-ID 2}.

[0493] For example, in Fig.18 In the example, the cell may be cell 5. The at least two TAGs are TAG 1 and TAG 2. Fig.17In , the list / set / vector of at least two TAG indexes for cell 5 is {TAG-ID 1, TAG-ID 2}.

[0494] In an example, the first TAG index of the first TAG of the at least two TAGs may be lower / smaller than the second TAG index of the second TAG of the at least two TAGs. The second TAG index of the second TAG of the at least two TAGs may be greater / higher than the first TAG index of the first TAG of the at least two TAGs.

[0495] For example, in Fig.18 , the cell may be cell 2. The at least two TAGs are TAG 0 and TAG 2. TAG 0 may be indicated / identified by TAG-ID 0. TAG 2 may be indicated / identified by TAG-ID 2. For example, based on TAG-ID 0 of TAG 0 being lower / smaller than TAG-ID 2 of TAG 2, the first TAG of the at least two TAGs may be TAG 0. For example, based on TAG-ID 0 of TAG 0 being lower / smaller than TAG-ID 2 of TAG 2, the second TAG of the at least two TAGs may be TAG 2. For example, based on TAG-ID 2 of TAG 2 being greater / higher than TAG-ID 0 of TAG 0, the second TAG of the at least two TAGs may be TAG 2.

[0496] For example, in Fig.18 , the cell may be cell 5. The at least two TAGs are TAG 1 and TAG 2. TAG 1 may be indicated / identified by TAG-ID 1. TAG 2 may be indicated / identified by TAG-ID 2. For example, based on TAG-ID 1 of TAG 1 being lower / smaller than TAG-ID 2 of TAG 2, the first TAG of the at least two TAGs may be TAG 1. For example, based on TAG-ID 1 of TAG 1 being lower / smaller than TAG-ID 2 of TAG 2, the second TAG of the at least two TAGs may be TAG 2. For example, based on TAG-ID 2 of TAG 2 being greater / higher than TAG-ID 1 of TAG 1, the second TAG of the at least two TAGs may be TAG 2.

[0497] In an example, the first TAG index may be the first / starting / earliest TAG index in a list / set / vector of at least two TAG indexes. The first TAG index may first appear in a list / set / vector of at least two TAG indexes. The position / location of the first TAG index may be the starting / first / earliest position / location / entry / element in a list / set / vector of at least two TAG indexes.

[0498] In an example, the second TAG index may be the last / latest / end / second start / second earliest / second TAG index in a list / set / vector of at least two TAG indexes. The second TAG index may appear second in the list / set / vector of at least two TAG indexes. The position / location of the second TAG index may be the last / latest / end / second start / second earliest / second position / position / entry / element in the list / set / vector of at least two TAG indexes. In the list / set / vector of at least two TAG indexes, the position / location of the first TAG index may be before (or earlier than or prior to) the position / position of the second TAG index.

[0499] For example, in Fig.18 In the example, the cell may be cell 2. The at least two TAGs are TAG 0 and TAG 2. Fig.17, the list / set / vector of at least two TAG indexes for cell 2 is {TAG-ID 0, TAG-ID 2}. TAG 0 may be indicated / identified by TAG-ID 0. TAG 2 may be indicated / identified by TAG-ID 2. For example, based on TAG-ID 0 being the first / starting / earliest TAG index in the list / set / vector of at least two TAG indexes (or the list / set / vector of TAG-ID 0 and TAG-ID 2), the first TAG index may be TAG-ID 0. For example, based on TAG-ID 0 being the first / starting / earliest TAG index in the list / set / vector of at least two TAG indexes (or the list / set / vector of TAG-ID 0 and TAG-ID 2), the second TAG index may be TAG-ID 2. For example, based on TAG-ID 2 being the last / latest / ending / second starting / second earliest / second TAG index in the list / set / vector of at least two TAG indexes (or the list / set / vector of TAG-ID0 and / TAG-ID 2), the second TAG index may be TAG-ID 2. For example, based on TAG-ID 0 indicating / identifying TAG 0 being the first / starting / earliest TAG index in the list / set / vector of at least two TAG indexes, the first TAG of the at least two TAGs may be TAG 0. For example, based on TAG-ID 0 indicating / identifying TAG 0 being the first to appear in the list / set / vector of at least two TAG indexes, the first TAG of the at least two TAGs may be TAG 0. For example, based on TAG-ID 0 indicating / identifying TAG 0 being the first / starting / earliest TAG index in the list / set / vector of at least two TAG indexes, the second TAG of the at least two TAGs may be TAG 2. For example, based on the indication / identification that TAG-ID 2 of TAG 2 is the last / latest / ending / second starting / second earliest / second TAG index in the list / set / vector of at least two TAG indexes, the second TAG of the at least two TAGs may be TAG 2. For example, based on the indication / identification that TAG-ID 2 of TAG 2 appears second in the list / set / vector of at least two TAG indexes, the second TAG of the at least two TAGs may be TAG 2.

[0500] For example, in Fig.18 In the example, the cell may be cell 5. The at least two TAGs are TAG 1 and TAG 2. Fig.17, the list / set / vector of at least two TAG indexes for cell 5 is {TAG-ID 1, TAG-ID 2}. TAG 1 can be indicated / identified by TAG-ID 1. TAG 2 can be indicated / identified by TAG-ID 2. For example, based on TAG-ID 1 being the first / starting / earliest TAG index in the list / set / vector of at least two TAG indexes (or the list / set / vector of TAG-ID 1 and TAG-ID 2), the first TAG index can be TAG-ID 1. For example, based on TAG-ID 1 being the first / starting / earliest TAG index in the list / set / vector of at least two TAG indexes (or the list / set / vector of TAG-ID 1 and TAG-ID 2), the second TAG index can be TAG-ID 2. For example, based on TAG-ID 2 being the last / latest / ending / second starting / second earliest / second TAG index in the list / set / vector of at least two TAG indexes (or the list / set / vector of TAG-ID1 and / TAG-ID 2), the second TAG index may be TAG-ID 2. For example, based on TAG-ID 1 indicating / identifying TAG 1 being the first / starting / earliest TAG index in the list / set / vector of at least two TAG indexes, the first TAG of the at least two TAGs may be TAG 1. For example, based on TAG-ID 1 indicating / identifying TAG 1 being the first to appear in the list / set / vector of at least two TAG indexes, the first TAG of the at least two TAGs may be TAG 1. For example, based on TAG-ID 1 indicating / identifying TAG 1 being the first / starting / earliest TAG index in the list / set / vector of at least two TAG indexes, the second TAG of the at least two TAGs may be TAG 2. For example, based on the indication / identification that TAG-ID 2 of TAG 2 is the last / latest / ending / second starting / second earliest / second TAG index in the list / set / vector of at least two TAG indexes, the second TAG of the at least two TAGs may be TAG 2. For example, based on the indication / identification that TAG-ID 2 of TAG 2 appears second in the list / set / vector of at least two TAG indexes, the second TAG of the at least two TAGs may be TAG 2.

[0501] For example, the list / set / vector of at least two TAG indexes of / for the cell may be {TAG-ID 3, TAG-ID 2}. TAG 3 may be indicated / identified by TAG-ID 3. TAG 2 may be indicated / identified by TAG-ID 2. For example, based on TAG-ID 3 being the first / starting / earliest TAG index in the list / set / vector of at least two TAG indexes (or the list / set / vector of TAG-ID 3 and TAG-ID 2), the first TAG index may be TAG-ID 3. For example, based on TAG-ID 1 being the first / starting / earliest TAG index in the list / set / vector of at least two TAG indexes (or the list / set / vector of TAG-ID 3 and TAG-ID 2), the second TAG index may be TAG-ID 2. For example, based on TAG-ID 2 being the last / la...

Claims

1. A method, comprising: receiving, by a wireless device, one or more radio resource control (RRC) messages, the one or more radio resource control messages including one or more configuration parameters for cells associated with at least two timing advance groups (TAGs), wherein the one or more configuration parameters indicate a plurality of transmission configuration indicator (TCI) states; receiving a medium access control (MAC) control element (CE) indicating activation of at least two of the plurality of TCI states for the cell; and Receiving Downlink Control Information (DCI): Scheduling downlink transport blocks or indicating semi-persistent scheduling (SPS) deactivation; as well as indicating uplink resources of the cell for hybrid automatic repeat request acknowledgement (HARQ-ACK) feedback for the downlink transport block or the SPS deactivation, wherein the uplink resources are associated with a TCI state of the at least two active TCI states of the cell; Based on the time alignment timer of the TAG in the at least two TAGs of the cell associated with the TCI state being running, the MAC layer of the wireless device commands the physical layer of the wireless device to generate an acknowledgement for the downlink transport block or the SPS deactivation; as well as The HARQ-ACK feedback is transmitted by the wireless device via a cell having a timing advance value associated with the TAG and based on a spatial domain transmission filter determined according to a reference signal of the TCI state, the HARQ-ACK feedback including the acknowledgment.

2. A method comprising: Receiving, by a wireless device, a downlink message via a cell associated with at least two timing advance groups (TAGs), the downlink message indicating uplink resources for hybrid automatic repeat request acknowledgement (HARQ-ACK) feedback, wherein the uplink resources are associated with a transmission configuration indicator (TCI) state of at least two active TCI states of the cell; commanding a physical layer of the wireless device to generate an acknowledgement based on a time alignment timer of a TAG in the at least two TAGs of the cell associated with the TCI state being running; as well as The HARQ-ACK feedback including the acknowledgment is transmitted via the cell and based on the TCI state.

3. The method of claim 2, wherein the command is commanded by a medium access control (MAC) layer of the wireless device.

4. The method of any one of claims 2 to 3, wherein the downlink message is downlink control information (DCI).

5. The method of any one of claims 2 to 4, wherein the acknowledgment is for a downlink transport block scheduled by the downlink message.

6. The method of any one of claims 2 to 5, wherein HARQ-ACK feedback is transmitted with a timing advance value associated with the TAG.

7. The method of any one of claims 2 to 6, wherein the transmission is based on a spatial domain transmission filter determined according to the TCI state.

8. The method of claim 7, wherein the spatial domain transmission filter is determined based on a reference signal indicated by the TCI state.

9. The method of any one of claims 2 to 8, wherein the downlink message schedules a downlink transport block.

10. The method of claim 9, further comprising receiving the downlink transport block scheduled by the downlink message.

11. The method of claim 10, wherein the acknowledgement is a positive acknowledgement (ACK) or a negative acknowledgement (NACK) based on whether the downlink transport block was successfully decoded or not successfully decoded, respectively.

12. The method of any one of claims 4 to 8, wherein the DCI indicates semi-persistent scheduling (SPS) deactivation.

13. The method of claim 12, wherein the DCI includes one or more fields set to predefined values ​​indicating deactivation of the SPS.

14. The method of any one of claims 12 to 13, wherein the acknowledgement is based on a positive acknowledgement (ACK) or a negative acknowledgement (NACK) of whether the DCI indicating the SPS deactivation is successfully detected or unsuccessfully detected, respectively.

15. The method of any one of claims 12 to 14, further comprising clearing one or more configured downlink assignments for the cell based on the DCI indicating the SPS deactivation.

16. The method according to any one of claims 2 to 15, further comprising receiving one or more radio resource control (RRC) messages including one or more configuration parameters of the cell, wherein the one or more configuration parameters indicate a plurality of transmission configuration indicator (TCI) states including the at least two TCI states.

17. The method of any one of claims 2 to 16, further comprising receiving a medium access control (MAC) control element (CE), the medium access control control element indicating activation of the at least two TCI states among a plurality of TCI states for the cell.

18. The method of any one of claims 2 to 17, wherein when the time alignment timer is running, a second time alignment timer of a second TAG of the at least two TAGs of the cell associated with a second TCI state of the at least two active TCI states stops or expires.

19. The method of claim 18, wherein the command: based on whether the time alignment timer is running; and Not based on whether the second time alignment timer is running, stopped or expired.

20. The method of any one of claims 2 to 17, further comprising: receiving, via the cell associated with the at least two TAGs, a second downlink message indicating the uplink resources for second HARQ-ACK feedback, wherein the second uplink resources are associated with the TCI state of the at least two active TCI states of the cell; as well as Based on the time alignment timer of the TAG in the at least two TAGs of the cell associated with the TCI state being stopped or expired, the physical layer of the wireless device is not commanded to generate a second acknowledgement.

21. The method of claim 20, wherein a second time alignment timer of a second TAG of the at least two TAGs of the cell associated with a second TCI state of the at least two active TCI states is running, and the time alignment timer is stopped or expires.

22. The method of claim 21, wherein the no command is: Based on whether the time alignment timer is stopped or expired; and Not based on whether the second time alignment timer is running, stopped or expired.

23. The method of any one of claims 20 to 22, further comprising not transmitting the second acknowledgement based on the time alignment of the TAG being stopped or expired.

24. The method of any one of claims 2 to 23, wherein the at least two active TCI states are associated with a physical cell identifier (PCI) of the cell.

25. The method of any one of claims 16 to 24, wherein the one or more configuration parameters indicate one or more physical cell identifiers (PCIs) for one or more of the plurality of TCI states.

26. The method of claim 25, wherein the at least two active TCIs are associated with the PCI of the cell based on the one or more configuration parameters not indicating a PCI for each of the at least two TCI states.

27. The method of any one of claims 2 to 26, further comprising determining whether to command the physical layer of the wireless device to generate the acknowledgement based on the time alignment timer of the TAG associated with the TCI state being running.

28. A method comprising: Receiving, by a wireless device, one or more messages including one or more configuration parameters indicating at least two timing advance groups (TAGs) for a cell, wherein each TAG of the at least two TAGs is associated with a corresponding control resource set (coreset) pool index; Receiving downlink control information (DCI) scheduling a transport block via a coreset having a coreset pool index; determining whether a time alignment timer for a TAG in the at least two TAGs of the cell associated with the coreset pool index of the coreset is running; commanding a physical layer of the wireless device to generate an acknowledgment for the transport block based on the time alignment timer of the TAG being running; as well as A hybrid automatic repeat request acknowledgement (HARQ-ACK) feedback including the acknowledgement of the transport block is transmitted via the cell.

29. A method comprising: Receiving, by a wireless device, downlink control information (DCI) triggering transmission of a hybrid automatic repeat request acknowledgement (HARQ-ACK) feedback via cells associated with at least two timing advance groups (TAGs), wherein the HARQ-ACK feedback is associated with a control resource set (coreset) pool index; commanding a physical layer of the wireless device to generate an acknowledgment based on a time alignment timer of a TAG in the at least two TAGs of the cell associated with the coreset pool index of the HARQ-ACK feedback being running; as well as The HARQ-ACK feedback including the acknowledgment is transmitted via the cell.

30. The method of claim 29, further comprising receiving one or more messages comprising one or more configuration parameters.

31. The method of claim 30, wherein the one or more configuration parameters indicate the at least two TAGs, wherein A first TAG of the at least two TAGs is associated with a first coreset pool index; and A second TAG of the at least two TAGs is associated with a second coreset pool index.

32. The method of claim 31 , wherein the one or more configuration parameters indicate: a first TAG index for the first TAG; and A second TAG index for the second TAG.

33. The method of claim 32, wherein the first TAG index is lower than the second TAG index.

34. The method of any one of claims 31 to 33, wherein the one or more configuration parameters indicate: a first time alignment timer for the first TAG of the at least two TAGs; and A second time alignment timer for the second TAG of the at least two TAGs.

35. The method of any one of claims 31 to 34, wherein the coreset pool index is the first coreset pool index.

36. The method of any one of claims 31 to 35, wherein the TAG is a first TAG based on a coreset pool index that is the first coreset pool index.

37. The method of any one of claims 34 to 36, wherein the time alignment timer is the first time alignment timer of the first TAG.

38. The method according to any one of claims 34 to 37, wherein the second time alignment timer of the second TAG: is in operation; or maturity.

39. The method of any one of claims 34 to 38, wherein the command is based on the first time alignment timer of the first TAG being running.

40. The method of any one of claims 34 to 39, wherein the command is not based on whether the second time alignment timer of the second TAG is running or expired.

41. The method of any one of claims 29 to 40, wherein the transmission is via uplink resources of the cell.

42. The method of claim 41 , wherein the uplink resource is at least one of: Physical uplink control channel (PUCCH) resources; Physical uplink shared channel (PUSCH) resources; Sounding Reference Signal (SRS) resources.

43. The method of any one of claims 41 to 42, wherein the HARQ-ACK feedback is associated with the coreset pool index based on one or more configuration parameters indicating the coreset pool index for the uplink resources.

44. The method of any one of claims 29 to 43, wherein the receiving the DCI is via a coreset of the cell, the coreset having the coreset pool index.

45. The method of claim 44, wherein the HARQ-ACK feedback is triggered based on the receiving the DCI via the coreset having the coreset pool index, the HARQ-ACK feedback being associated with the coreset pool index.

46. ​​The method of any one of claims 29 to 45, wherein a medium access control (MAC) layer of the wireless device commands the physical layer of the wireless device.

47. The method of any one of claims 29 to 46, wherein the confirmation is: positive confirmation; or Negative confirmation.

48. The method of any one of claims 29-47, wherein the transmission is based on a timing advance value of a TAG.

49. The method of any one of claims 29 to 48, wherein the DCI: scheduling reception of a transport block for a second cell; Instructing a secondary cell (SCell) for the second cell to sleep; indicating deactivation of semi-persistent scheduling (SPS) for the second cell; or Indicates a transmission configuration indicator (TCI) status update for the second cell.

50. The method of claim 49, wherein the HARQ-ACK feedback is used to: successful decoding or unsuccessful decoding of the transport block; or confirmation of successful detection or unsuccessful detection of said DCI indicating: The SCell is dormant; or The SPS is deactivated; or The TCI status is updated.

51. The method of any one of claims 49 to 50, wherein the second cell and the cell are: different; or Same.

52. The method of any one of claims 49 to 51, wherein the transport block is: New transmission; or retransmission of the transport block.

53. The method of any one of claims 49 to 51 , further comprising attempting to decode data comprising the transport block.

54. The method of claim 53, wherein the decoding of the transport block is successful or unsuccessful.

55. The method of any one of claims 29 to 54, wherein the DCI includes a New Data Indicator (NDI) field having a value equal to zero.

56. The method of any one of claims 29 to 55, wherein the DCI comprises one or more fields set to a predefined value indicating deactivation of semi-persistent scheduling (SPS).

57. The method of claim 56, further comprising clearing one or more configured downlink assignments based on the DCI indicating deactivation of the SPS.

58. The method of any one of claims 56 to 57, wherein the confirmation is a positive confirmation for the SPS deactivation.

59. The method of any one of claims 29 to 58, further comprising: receiving a second DCI triggering transmission of a second HARQ-ACK feedback via the cell, wherein the second HARQ-ACK feedback is associated with a coreset pool index; as well as Based on the expiration of the time alignment timer of the TAG in the at least two TAGs of the cell associated with the coreset pool index of the second HARQ-ACK feedback, the physical layer of the wireless device is not commanded to generate a second acknowledgement.

60. The method of claim 59, wherein a MAC layer of the wireless device does not command the physical layer of the wireless device to generate the second acknowledgment for a second transport block.

61. The method of any one of claims 29 to 60, wherein the acknowledgement is a HARQ-ACK information bit.

62. A system comprising: Base station; as well as A wireless device comprising: one or more processors and a memory storing instructions, wherein the instructions, when executed by the one or more processors, cause the wireless device to perform the method as claimed in any one of claims 1 to 61.

63. An apparatus comprising: one or more processors; as well as A memory storing instructions which, when executed by the one or more processors, cause the apparatus to perform a method as claimed in any one of claims 1 to 61.

64. A non-transitory computer-readable medium comprising instructions which, when executed by one or more processors of a device, cause the device to perform the method of any one of claims 1-61.

Images