TCI switching time handling with low-band carrier aggregation with switching
Optimizing TCI state switching time during low-band carrier aggregation addresses inefficiencies in wireless networks, enhancing communication efficiency and reducing latency.
Patent Information
- Application Number
- PCT/US2026/027123
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2025-05-07
- Filing Date
- 2026-05-07
- Publication Date
- 2026-11-12
AI Technical Summary
Existing technologies face challenges in efficiently handling TCI switching time during low-band carrier aggregation, leading to suboptimal performance in wireless communication networks.
Implementing mechanisms to manage TCI state switching time during low-band carrier aggregation by optimizing the configuration and timing of TCI states, ensuring seamless transitions and reduced latency.
Enhances communication efficiency and reduces latency in wireless networks by optimizing TCI state switching, thereby improving overall network performance.
Smart Images

Figure US2026027123_12112026_PF_FP_ABST
Abstract
Description
Docket No.25-1081 PCTTITLE TCI Switching Time Handling with Low-band Carrier Aggregation with SwitchingCROSS-REFERENCE TO RELATED APPLICATIONS
[0001] This application claims the benefit of U. S. Provisional Application No. 63 / 801,513, filed May 7, 2025, which is hereby incorporated by reference in its entirety.BRIEF DESCRIPTION OF THE DRAWINGS
[0002] Examples of several of the various embodiments of the present disclosure are described herein with reference to the drawings.
[0003] FIG. 1A and FIG. 1B illustrate example mobile communication networks in which embodiments of the present disclosure may be implemented.
[0004] FIG. 2A and FIG. 2B respectively illustrate a New Radio (NR) user plane and control plane protocol stack.
[0005] FIG. 3 illustrates an example of services provided between protocol layers of the NR user plane protocol stack of FIG.2A.
[0006] FIG. 4A illustrates an example downlink data flow through the NR user plane protocol stack of FIG. 2A.
[0007] FIG. 4B illustrates an example format of a MAC subheader in a MAC PDU.
[0008] FIG. 5A and FIG. 5B respectively illustrate a mapping between logical channels, transport channels, and physical channels for the downlink and uplink.
[0009] FIG. 6 is an example diagram showing RRC state transitions of a UE.
[0010] FIG. 7 illustrates an example configuration of an NR frame into which OFDM symbols are grouped.
[0011] FIG. 8 illustrates an example configuration of a slot in the time and frequency domain for an NR carrier.
[0012] FIG. 9 illustrates an example of bandwidth adaptation using three configured BWPs for an NR carrier.
[0013] FIG. 10A illustrates three carrier aggregation configurations with two component carriers.
[0014] FIG. 10B illustrates an example of how aggregated cells may be configured into one or more PUCCH groups.
[0015] FIG. 11A illustrates an example of an SS / PBCH block structure and location.
[0016] FIG. 11 B illustrates an example of CSI-RSs that are mapped in the time and frequency domains.
[0017] FIG. 12A and FIG. 12B respectively illustrate examples of three downlink and uplink beam management procedures.
[0018] FIG. 13A, FIG. 13B, and FIG. 13C respectively illustrate a four-step contention-based random access procedure, a two-step contention-free random access procedure, and another two-step random access procedure.
[0019] FIG. 14A illustrates an example of CORESET configurations fora bandwidth part.
[0020] FIG. 14B illustrates an example of a CCE-to-REG mapping for DCI transmission on a CORESET and PDCCH processing.
[0021] FIG. 15 illustrates an example of a wireless device in communication with a base station.
[0022] FIG. 16A, FIG. 16B, FIG. 16C, and FIG. 16D illustrate example structures for uplink and downlink transmission.Docket No.25-1081 PCT
[0023] FIG. 17 illustrates an aspect of an example embodiment according to the present disclosure.
[0024] FIG. 18 illustrates an aspect of an example embodiment according to the present disclosure.
[0025] FIG. 19 illustrates an aspect of an example embodiment according to the present disclosure.
[0026] FIG. 20 illustrates an aspect of an example embodiment according to the present disclosure.
[0027] FIG. 21 illustrates an aspect of an example embodiment according to the present disclosure.
[0028] FIG. 22 illustrates an aspect of an example embodiment according to the present disclosure.
[0029] FIG. 23 illustrates an aspect of an example embodiment according to the present disclosure.
[0030] FIG. 24 illustrates an aspect of an example embodiment according to the present disclosure.
[0031] FIG. 25 illustrates an aspect of an example embodiment according to the present disclosure.
[0032] FIG. 26 illustrates an aspect of an example embodiment according to the present disclosure.
[0033] FIG. 27 illustrates an aspect of an example embodiment according to the present disclosure.DETAILED DESCRIPTION
[0034] In the present disclosure, various embodiments are presented as examples of how the disclosed techniques may be implemented and / or how the disclosed techniques may be practiced in environments and scenarios. It will be apparent to persons skilled in the relevant art that various changes in form and detail can be made therein without departing from the scope. In fact, after reading the description, it will be apparent to one skilled in the relevant art how to implement alternative embodiments. The present embodiments should not be limited by any of the described exemplary embodiments. The embodiments of the present disclosure will be described with reference to the accompanying drawings. Limitations, features, and / or elements from the disclosed example embodiments may be combined to create further embodiments within the scope of the disclosure. Any figures which highlight the functionality and advantages, are presented for example purposes only. The disclosed architecture is sufficiently flexible and configurable, such that it may be utilized in ways other than that shown. For example, the actions listed in any flowchart may be re-ordered or only optionally used in some embodiments.
[0035] Embodiments may be configured to operate as needed. The disclosed mechanism may be performed when certain criteria are met, for example, in a wireless device, a base station, a radio environment, a network, a combination of the above, and / or the like. Example criteria may be based, at least in part, on for example, wireless device or network node configurations, traffic load, initial system set up, packet sizes, traffic characteristics, a combination of the above, and / or the like. When the one or more criteria are met, various example embodiments may be applied.Therefore, it may be possible to implement example embodiments that selectively implement disclosed protocols.
[0036] A base station may communicate with a mix of wireless devices. Wireless devices and / or base stations may support multiple technologies, and / or multiple releases of the same technology. Wireless devices may have some specific capability(ies) depending on wireless device category and / or capabil ity(ies). When this disclosure refers to a base station communicating with a plurality of wireless devices, this disclosure may refer to a subset of the total wireless devices in a coverage area. This disclosure may refer to, for example, a plurality of wireless devices of a given LTE or 5G release with a given capability and in a given sector of the base station. The plurality of wireless devices inDocket No.25-1081 PCTthis disclosure may refer to a selected plurality of wireless devices, and / or a subset of total wireless devices in a coverage area which perform according to disclosed methods, and / or the like. There may be a plurality of base stations or a plurality of wireless devices in a coverage area that may not comply with the disclosed methods, for example, those wireless devices or base stations may perform based on older releases of LTE or 5G technology.
[0037] In this disclosure, "a” and “an” and similar phrases are to be interpreted as “at least one” and “one or more.” Similarly, any term that ends with the suffix “(s)” is to be interpreted as “at least one” and “one or more.” In this disclosure, the term “may” is to be interpreted as “may, for example.” In other words, the term “may” is indicative that the phrase following the term “may” is an example of one of a multitude of suitable possibilities that may, or may not, be employed by one or more of the various embodiments. The terms “comprises” and “consists of", as used herein, enumerate one or more components of the element being described. The term “comprises” is interchangeable with “includes" and does not exclude unenumerated components from being included in the element being described. By contrast, “consists of' provides a complete enumeration of the one or more components of the element being described. The term “based on”, as used herein, should be interpreted as “based at least in part on” rather than, for example, “based solely on”. The term “and / or” as used herein represents any possible combination of enumerated elements. For example, “A, B, and / or 0” may represent A; B; C; A and B; A and C; B and C; or A, B, and C.
[0038] If A and B are sets and every element of A is an element of B, A is called a subset of B. In this specification, only non-empty sets and subsets are considered. For example, possible subsets of B = {celH, cell2} are: {celH }, {cell2}, and {celH, cell2}. The phrase “based on" (or equally “based at least on”) is indicative that the phrase following the term “based on” is an example of one of a multitude of suitable possibilities that may, or may not, be employed to one or more of the various embodiments. The phrase “in response to” (or equally “in response at least to”) is indicative that the phrase following the phrase “in response to” is an example of one of a multitude of suitable possibilities that may, or may not, be employed to one or more of the various embodiments. The phrase “depending on” (or equally “depending at least to”) is indicative that the phrase following the phrase “depending on" is an example of one of a multitude of suitable possibilities that may, or may not, be employed to one or more of the various embodiments. The phrase “employing / using” (or equally “employing / using at least’) is indicative that the phrase following the phrase “employing / using” is an example of one of a multitude of suitable possibilities that may, or may not, be employed to one or more of the various embodiments.
[0039] The term configured may relate to the capacity of a device whether the device is in an operational or non-operational state. Configured may refer to specific settings in a device that affect or implement the operational characteristics of the device whether the device is in an operational or non-operational state. In other words, the hardware, software, firmware, registers, memory values, and / or the like may be “configured” within a device, whether the device is in an operational or nonoperational state, to provide the device with specific characteristics. Terms such as “a control message to cause in a device” may mean that a control message has parameters that may be used to configure specific characteristics or may be used to implement certain actions in the device, whether the device is in an operational or non-operational state.Docket No.25-1081 PCT
[0040] In this disclosure, parameters (or equally called, fields, or Information elements: lEs) may comprise one or more information objects, and an information object may comprise one or more other objects. For example, if parameter (IE) N comprises parameter (IE) M, and parameter (IE) M comprises parameter (IE) K, and parameter (IE) K comprises parameter (information element) J. Then, for example, N comprises K, and N comprises J. In an example embodiment, when one or more messages comprise a plurality of parameters, it implies that a parameter in the plurality of parameters is in at least one of the one or more messages, but does not have to be in each of the one or more messages.
[0041] Many features presented are described as being optional through the use of “may” or the use of parentheses. For the sake of brevity and legibility, the present disclosure does not explicitly recite each and every permutation that may be obtained by choosing from the set of optional features. The present disclosure is to be interpreted as explicitly disclosing all such permutations. For example, a system described as having three optional features may be embodied in seven ways, namely with just one of the three possible features, with any two of the three possible features or with three of the three possible features.
[0042] Many of the elements described in the disclosed embodiments may be implemented as modules. A module is defined here as an element that performs a defined function and has a defined interface to other elements. The modules described in this disclosure may be implemented in hardware, software in combination with hardware, firmware, wetware (e.g., hardware with a biological element), or a combination thereof, which may be behaviora lly equivalent. For example, modules may be implemented as a software routine written in a computer language configured to be executed by a hardware machine (such as C, C++, Fortran, Java, Basic, MATLAB or the like) or a modeling / simulation program such as Simulink, Stateflow, GNU Octave, or LabVI E WMathScript. It may be possible to implement modules using physical hardware that incorporates discrete or programmable analog, digital and / or quantum hardware. Examples of programmable hardware comprise: computers, microcontrollers, microprocessors, applicationspecific integrated circuits (ASICs); field programmable gate arrays (FPGAs); and complex programmable logic devices (CPLDs). Computers, microcontrollers and microprocessors are programmed using languages such as assembly, C, C++ or the like. FPGAs, ASICs and CPLDs are often programmed using hardware description languages (HDL) such as VHSIC hardware description language (VHDL) or Verilog that configure connections between internal hardware modules with lesser functionality on a programmable device. The mentioned technologies are often used in combination to achieve the result of a functional module.
[0043] FIG. 1A illustrates 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) run by a network operator. As illustrated in FIG. 1A, the mobile communication network 100 includes a core network (CN) 102, a radio access network (RAN) 104, and a wireless device 106.
[0044] The CN 102 may provide the wireless device 106 with an interface to one or more data networks (DNs), such as public DNs (e.g., the Internet), private DNs, and / or intra-operator DNs. As part of the interface functionality, the CNDocket No.25-1081 PCT102 may set up end-to-end connections between the wireless device 106 and the one or more DNs, authenticate the wireless device 106, and provide charging functionality.
[0045] The RAN 104 may connect the CN 102 to the wireless device 106 through 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 communication direction from the RAN 104 to the wireless device 106 over the air interface is known as the downlink and the communication direction from the wireless device 106 to the RAN 104 over the air interface is known as the uplink. Downlink transmissions may be separated from uplink transmissions using frequency division duplexing (FDD), time-division duplexing (TDD), and / or some combination of the two duplexing techniques.
[0046] The term wireless device may be used throughout this disclosure to refer to and encompass any mobile device or fixed (non-mobile) device for which wireless communication is needed or usable. For example, a wireless device maybe a telephone, smartphone, tablet, computer, laptop, sensor, meter, wearable device, Internet of Things (loT) device, vehicle roadside unit (RSU), relay node, automobile, and / or any combination thereof. The term wireless device encompasses other terminology, including user equipment (UE), user terminal (UT), access terminal (AT), mobile station, handset, wireless transmit and receive unit (WTRU), and / or wireless communication device.
[0047] The RAN 104 may include one or more base stations (not shown). The term base station may be used throughout this disclosure to refer to 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, Wi-Fi or any other suitable wireless communication standard), and / or any combination thereof. A base station may comprise at least one gNB Central Unit (gNB-CU) and at least one a gNB Distributed Unit (gNB-DU).
[0048] A base station included in the RAN 104 may include one or more sets of antennas for communicating with the wireless device 106 over the air interface. For example, one or more of the base stations may include three sets of antennas to respectively control three cells (or sectors). The size of a cell may be determined by a range at which a receiver (e.g., a base station receiver) can successfully receive the transmissions from a transmitter (e.g., a wireless device transmitter) operating in the cell. Together, the cells of the base stations may provide radio coverage to the wireless device 106 over a wide geographic area to support wireless device mobility.
[0049] In addition to three-sector sites, other implementations of base stations are possible. For example, one or more of the base stations in the RAN 104 may be implemented as a sectored 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, as a baseband processing unit coupled to several remote radio heads (RRHs), and / or as a repeater or relay node used to extend the coverage area of a donor node. A baseband processing unit coupled to RRHs may be part of a centralized or cloud RAN architecture, where the baseband processing unit may be either centralized in a pool of baseband processing units orDocket No.25-1081 PCTvirtualized. A repeater node may amplify and rebroadcast a radio signal received from a donor node. A relay node may perform the same / similar functions as a repeater node but may decode the radio signal received from the donor node to remove noise before amplifying and rebroadcasting the radio signal.
[0050] The RAN 104 may be deployed as a homogenous network of macrocell base stations that have similar antenna patterns and similar high-level transmit powers. The RAN 104 may be deployed as a heterogeneous network. In heterogeneous networks, small cell base stations may be used to provide small coverage areas, for example, coverage areas that overlap with the comparatively larger coverage areas provided by macrocell base stations. The small coverage areas may be provided in areas with high data traffic (or so-called "hotspots”) or in areas with weak macrocell coverage. Examples of small cell base stations include, in order of decreasing coverage area, microcell base stations, picocell base stations, and femtocell base stations or home base stations.
[0051] The Third-Generation Partnership Project (3GPP) was formed in 1998 to provide global standardization of specifications for mobile communication networks similar to the mobile communication network 100 in FIG. 1A. To date, 3GPP has produced specifications for three generations of mobile networks: a third generation (3G) network known as Universal Mobile Telecommunications System (UMTS), a fourth generation (4G) network known as Long-Term Evolution (LTE), and a fifth generation (5G) network known as 5G System (5GS). Embodiments of the present disclosure are described with reference to the RAN of a 3GPP 5G network, referred to as next-generation RAN (NG-RAN). Embodiments may be applicable to RANs of other mobile communication networks, such as the RAN 104 in FIG. 1 A, the RANs of earlier 3G and 4G networks, and those of future networks yet to be specified (e.g., a 3GPP 6G network). NG-RAN implements 5G radio access technology known as New Radio (NR) and may be provisioned to implement 4G radio access technology or other radio access technologies, including non-3GPP radio access technologies.
[0052] FIG. 1B illustrates another example mobile communication network 150 in which embodiments of the present disclosure may be implemented. Mobile communication network 150 may be, for example, a PLMN run by a network operator. As illustrated in FIG. 1B, mobile communication network 150 includes a 5G core network (5G-CN) 152, an NG-RAN 154, and UEs 156A and 156B (collectively UEs 156). These components may be implemented and operate in the same or similar manner as corresponding components described with respect to FIG. 1A
[0053] The 5G-CN 152 provides the UEs 156 with an interface to one or more DNs, such as public DNs (e.g., the Internet), private DNs, and / or intra-operator DNs. As part of the interface functionality, the 5G-CN 152 may set up end-to-end connections between the UEs 156 and the one or more DNs, authenticate the UEs 156, and provide charging functionality. Compared to the CN of a 3GPP 4G network, the basis of the 5G-CN 152 may be a service-based architecture. This means that the architecture of the nodes making up the 5G-CN 152 may be defined as network functions that offer services via interfaces to other network functions. The network functions of the 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).Docket No.25-1081 PCT
[0054] As illustrated in FIG. 1 B, the 5G-CN 152 includes an Access and Mobility Management Function (AMF) 158A and a User Plane Function (UPF) 158B, which are shown as one component AMF / UPF 158 in FIG. 1B for ease of illustration. The UPF 158B may serve as a gateway between the NG-RAN 154 and the one or more DNs. The UPF 158B may perform functions such as packet routing and forwarding, packet inspection and user plane policy rule enforcement, traffic usage reporting, uplink classification to support routing of traffic flows to the one or more DNs, quality of service (QoS) handling for the user plane (e.g., packet filtering, gating, uplink / downlink rate enforcement, and uplink traffic verification), downlink packet buffering, and downlink data notification triggering. The UPF 158B may serve as an anchor point for intra- / i nter-Radio Access Technology (RAT) mobility, an external protocol (or packet) data unit (PDU) session point of interconnect to the one or more DNs, and / or a branching point to support a multi-homed PDU session. The UEs 156 may be configured to receive services through a PDU session, which is a logical connection between a UEandaDN.
[0055] 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 retransmission), registration area management, intra-system and inter-system mobility support, access authentication, access authorization including checking of roaming rights, mobility management control (subscription and policies), network slicing support, and / or session management function (SMF) selection. NAS may refer to the functionality operating between a CN and a UE, and AS may refer to the functionality operating between the UE and a RAN.
[0056] The 5G-CN 152 may include one or more additional network functions that are not shown in FIG. 1 B for the sake of clarity. For example, the 5G-CN 152 may include one or more of a Session Management Function (SMF), an NR Repository Function (NRF), a Policy Control Function (PCF), a Network Exposure Function (NEF), a Unified Data Management (UDM), an Application Function (AF), and / or an Authentication Server Function (AUSF).
[0057] The NG-RAN 154 may connect the 5G-CN 152 to the UEs 156 through radio communications over the air interface. The NG-RAN 154 may include one or more g NBs, illustrated as g NB 160A and g NB 160B (collectively gNBs 160) and / or one or more ng-eNBs, illustrated as ng-eNB 162A and ng-eNB 162B (collectively ng-eNBs 162). The gNBs 160 and ng-eNBs 162 may be more generically referred to as base stations. The gNBs 160 and ng-eNBs 162 may include one or more sets of antennas for communicating with the UEs 156 over an air interface. For example, one or more of the gNBs 160 and / or one or more of the ng-eNBs 162 may include three sets of antennas to respectively control three cells (or sectors). Together, the cells of the gNBs 160 and the ng-eNBs 162 may provide radio coverage to the UEs 156 over a wide geographic area to support UE mobility.
[0058] As shown in FIG. 1B, the gNBs 160 and / or the ng-eNBs 162 may be connected to the 5G-CN 152 by means of an NG interface and to other base stations by an Xn interface. The NG and Xn interfaces may be established using direct physical connections and / or indirect connections over an underlying transport network, such as an internet protocol (IP) transport network. The gNBs 160 and / or the ng-eNBs 162 may be connected to the UEs 156 by means of a Uu interface. For example, as illustrated in FIG. 1B, gNB 160A maybe connected to the UE 156A by meansofa UuDocket No.25-1081 PCTinterface. The NG, Xn, and Uu interfaces are associated with a protocol stack. The protocol stacks associated with the interfaces may be used by the network elements in FIG. 1 B to exchange data and signaling messages and may include two planes: a user plane and a control plane. The user plane may handle data of interest to a user. The control plane may handle signaling messages of interest to the network elements.
[0059] The gNBs 160 and / or the ng-eNBs 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 maybe connected to the UPF 158B of the AMF / UPF 158 by means of an NG-User plane (NG-U) interface. The NG-U interface may provide delivery (e.g., non-guaranteed delivery) of user plane PDUs between the gNB 160A and the UPF 158B. The gNB 160A may be connected to the AMF 158A by means of an NG-Control plane (NG-C) interface. The NG-C interface may provide, for example, NG interface management, UE context management, UE mobility management, transport of NAS messages, paging, PDU session management, and configuration transfer and / or warning message transmission.
[0060] The gNBs 160 may provide NR user plane and control plane protocol terminations towards the UEs 156 over the Uu interface. For example, the gNB 160A may provide NR user plane and control plane protocol terminations toward the UE 156A over a Uu interface associated with a first protocol stack. The ng-eNBs 162 may provide Evolved UMTS Terrestrial Radio Access (E-UTRA) user plane and control plane protocol terminations towards the UEs 156 over a Uu interface, where E-UTRA refers to the 3GPP 4G radio-access technology. For example, the ng-eNB 162B may provide E-UTRA user plane and control plane protocol terminations towards the UE 156B over a Uu interface associated with a second protocol stack.
[0061] The 5G-CN 152 was described as being configured to handle NR and 4G radio accesses. It will be appreciated by one of ordinary skill in the art that it may be possible for NR to connect to a 4G core network in a mode known as "non-standalone operation.” In non-standalone operation, a 4G core network is used to provide (or at least support) control-plane functionality (e.g., initial access, mobility, and paging). Although only one AMF / UPF 158 is shown in FIG. 1 B, one gNB or ng-eNB may be connected to multiple AMF / UPF nodes to provide redundancy and / or to load share across the multiple AMF / UPF nodes.
[0062] As discussed, an interface (e.g., Uu, Xn, and NG interfaces) between the network elements in FIG. 1 B may be associated with a protocol stack that the network elements use to exchange data and signaling messages. A protocol stack may include two planes: a user plane and a control plane. The user plane may handle data of interest to a user, and the control plane may handle signaling messages of interest to the network elements.
[0063] FIG. 2A and FIG. 2B respectively illustrate examples of NR user plane and NR control plane protocol stacks for the Uu interface that lies between a UE 210 and a gNB 220. The protocol stacks illustrated in FIG. 2A and FIG.2B may be the same or similar to those used for the Uu interface between, for example, the UE 156A and the gNB 160A shown in FIG. 1B.
[0064] FIG. 2A illustrates a NR user plane protocol stack comprising five layers implemented in the UE 210 and the gNB 220. At the bottom of the protocol stack, physical layers (PHYs) 211 and 221 may provide transport services to theDocket No.25-1081 PCThigher layers of the protocol stack and may correspond to layer 1 of the Open Systems Interconnection (OSI) model. The next four protocols above PHYs 211 and 221 comprise medium access control (MAC) layers (MACs) 212 and 222 (also referred to as media access control layers), radio link control (RLC) layers (RLCs) 213 and 223, packet data convergence protocol (PDCP) layers (PDCPs) 214 and 224, and service data application protocol (SOAP) layers (SDAPs) 215 and 225. Together, these four protocols may make up layer 2, or the data link layer, of the OSI model.
[0065] FIG. 3 illustrates an example of services provided between protocol layers of the NR user plane protocol stack. Starting from the top of FIG. 2A and FIG.3, the SDAPs 215 and 225 may perform QoS flow handling. The UE 210 may receive services through a PDU session, which may be a logical connection between the UE 210 and a DN. The PDU session may have one or more QoS flows. A UPF of a CN (e.g., the UPF 158B) may 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). The SDAPs 215 and 225 may perform mapping / de-mapping between the one or more QoS flows and one or more data radio bearers. The mapping / de-mapping between the QoS flows and the data radio bearers may be determined by the SDAP 225 at the g NB 220. The SDAP 215 at the UE 210 may be informed of 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 the downlink packets with a QoS flow indicator (QFI), which may be observed by the SDAP 215 at the UE 210 to determine the mapping / de-mapping between the QoS flows and the data radio bearers.
[0066] The PDCPs 214 and 224 may perform header compression / decompression to reduce the amount of data that needs to be transmitted over the air interface, ciphering / deciphering to prevent unauthorized decoding of data transmitted over the air interface, and integrity protection (to ensure control messages originate from intended sources. The PDCPs 214 and 224 may perform retransmissions of undelivered packets, in-sequence delivery and reordering of packets, and removal of packets received in duplicate due to, for example, an intra-g NB handover. The PDCPs 214 and 224 may perform packet duplication to improve the likelihood of the packet being received and, at the receiver, remove any duplicate packets. Packet duplication may be useful for services that require high reliability.
[0067] Although not shown in FIG. 3, PDCPs 214 and 224 may perform mapping / de-mapping between a split radio bearer and RLC channels in a dual connectivity scenario. Dual connectivity is a technique that allows a UE to connect to two cells or, more generally, two cell groups: a master cell group (MCG) and a secondary cell group (SCG). A split bearer is when a single radio bearer, such as one of the radio bearers provided by the PDCPs 214 and 224 as a service to the SDAPs 215 and 225, is handled by cell groups in dual connectivity. The PDCPs 214 and 224 may map / de-map the split radio bearer between RLC channels belonging to cell groups.
[0068] The RLCs 213 and 223 may perform segmentation, retransmission through Automatic Repeat Request (ARQ), and removal of duplicate data units received from MACs 212 and 222, respectively. The RLCs 213 and 223 may support three transmission modes: transparent mode (TM); unacknowledged mode (UM); and acknowledged mode (AM). Based on the transmission mode an RLC is operating, the RLC may perform one or more of the noted functions The RLC configuration may be per logical channel with no dependency on numerologies and / orDocket No.25-1081 PCTTransmission Time Interval (TTI) durations. As shown in FIG.3, the RLCs 213 and 223 may provide RLC channels as a service to PDCPs 214 and 224, respectively.
[0069] The MACs 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 of data units, belonging to the one or more logical channels, into / from Transport Blocks (TBs) delivered to / from the PHYs 211 and 221. The MAC 222 may be configured to perform scheduling, scheduling information reporting, and priority handling between UEs by means of dynamic scheduling. Scheduling may be performed in the g NB 220 (at the MAC 222) for downlink and uplink The MACs 212 and 222 may be configured to perform error correction through Hybrid Automatic Repeat Request (HARQ) (e.g., one HARQ entity per carrier in case of Carrier Aggregation (CA)), priority handling between logical channels of the UE 210 by means of logical channel prioritization, and / or padding. The MACs 212 and 222 may support one or more numerologies and / or transmission timings. In an example, mapping restrictions in a logical channel prioritization may control which numerology and / or transmission timing a logical channel may use. As shown in FIG. 3, the MACs 212 and 222 may provide logical channels as a service to the RLCs 213 and 223.
[0070] The PHYs 211 and 221 may 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, coding / decoding and modulation / demodulation. The PHYs 211 and 221 may perform multi-antenna mapping. As shown in FIG.3, the PHYs 211 and 221 may provide one or more transport channels as a service to the MACs 212 and 222.
[0071] FIG. 4A illustrates an example downlink data flow through the NR user plane protocol stack. FIG. 4A illustrates a downlink data flow of three IP packets (n, n+1, and m) through the NR user plane protocol stack to generate two TBs at the gNB 220. An uplink data flow through the NR user plane protocol stack may be similar to the downlink data flow depicted in FIG. 4A.
[0072] The downlink data flow of FIG. 4A begins when SDAP 225 receives the three IP packets from one or more QoS flows and maps the three packets to radio bearers. In FIG.4A, the SDAP 225 maps IP packets n and n+1 to a first radio bearer 402 and maps IP packet m to a second radio bearer 404. An SDAP header (labeled with an “H" in FIG. 4A) is added to an IP packet. The data unit from / to a higher protocol layer is referred to as a service data unit (SDU) of the lower protocol layer and the data unit to / from a lower protocol layer is referred to as a protocol data unit (PDU) of the higher protocol layer. As shown in FIG. 4A, the data unit from the SDAP 225 is an SDU of lower protocol layer PDCP 224 and is a PDU of the SDAP 225.
[0073] The remaining protocol layers in FIG. 4A may perform their associated functionality (e.g., with respect to FIG.3), add corresponding headers, and forward their respective outputs to the next lower layer. For example, the PDCP 224 may perform IP-header compression and ciphering and forward its output to the RLC 223. The RLC 223 may optionally perform segmentation (e.g., as shown for IP packet m in FIG.4A) and forward its output to the MAC 222. The MAC 222 may multiplex a number of RLC PDUs and may attach a MAC subheader to an RLC PDU to form a transport block. In NR, the MAC subheaders may be distributed across the MAC PDU, as illustrated in FIG.4A. In LTE, the MACDocket No.25-1081 PCTsubheaders may be entirely located at the beginning of the MAC PDU. The NR MAC PDU structure may reduce processing time and associated latency because the MAC PDU subheaders may be computed before the full MAC PDU is assembled.
[0074] FIG. 4B illustrates an example format of a MAC subheader in a MAC PDU. 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 originated to aid 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.
[0075] FIG. 4B further illustrates MAC control elements (CEs) inserted into the MAC PDU by a MAC, such as MAC 223 or MAC 222. For example, FIG. 4B illustrates two MAC CEs inserted into the MAC PDU. MAC CEs may be inserted at the beginning of a MAC PDU for downlink transmissions (as shown in FIG. 4B) and at the end of a MAC PDU for uplink transmissions. MAC CEs 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 for activation / deactivation of PDCP duplication detection, channel state information (CSI) reporting, sounding reference signal (SRS) transmission, and prior configured components; discontinuous reception (DRX) related MAC CEs; timing advance MAC CEs; and random access related MAC CEs. A MAC CE may be preceded by a MAC subheader with a similar format as described for MAC SDUs and may be identified with a reserved value in the LCID field that indicates the type of control information included in the MAC CE.
[0076] Before describing the NR control plane protocol stack, logical channels, transport channels, and physical channels are first described as well as a mapping between the channel types. One or more of the channels may be used to carry out functions associated with the NR control plane protocol stack described later below.
[0077] FIG. 5A and FIG. 5B illustrate, for downlink and uplink respectively, a mapping between logical channels, transport channels, and physical channels. Information is passed through channels between the RLC, the MAC, and the PHY of the NR protocol stack. A logical channel may be used between the RLC and the MAC and may be classified as a control channel that carries control and configuration information in the NR control plane or as a traffic channel that carries data in the NR user plane. A logical channel may be classified as a dedicated logical channel that is dedicated to a specific UE or as a common logical channel that may be used by more than one UE. A logical channel may also be defined by the type of information it carries. The set of logical channels defined by NR include, for example:
[0078] - a paging control channel (PCCH) for carrying paging messages used to page a UE whose location is not known to the network on a cell level;
[0079] - a broadcast control channel (BCCH) for carrying system information messages in the form of a master information block (MIB) and several system information blocks (SIBs), wherein the system information messages may be used by the UEs to obtain information about how a cell is configured and how to operate within the cell;
[0080] - a common control channel (CCCH) for carrying control messages together with random access;Docket No.25-1081 PCT
[0081] - a dedicated control channel (DCCH) for carrying control messages to / from a specific the UE to configure the UE; and
[0082] - a dedicated traffic channel (DTCH) for carrying user data to / from a specific the UE.
[0083] T ransport channels are used between the MAC and PHY layers and may 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:
[0084] - a paging channel (PCH) for carrying paging messages that originated from the PCCH;
[0085] - a broadcast channel (BCH) for carrying the MIB from the BCCH;
[0086] - a downlink shared channel (DL-SCH) for carrying downlink data and signaling messages, including the SIBs from the BCCH;
[0087] - an uplink shared channel (UL-SCH) for carrying uplink data and signaling messages; and
[0088] - a random access channel (RACH) for allowing a UE to contact the network without any prior scheduling.
[0089] The PHY may use physical channels to pass information between processing levels of the PHY. A physical channel may have an associated set of time-frequency resources for carrying the information of one or more transport channels. The PHY may generate control information to support the low-level operation of the PHY and provide the control information to the lower levels of the PHY via physical control channels, known as L1 / L2 control channels. The set of physical channels and physical control channels defined by NR include, for example:
[0090] - a physical broadcast channel (PBCH) for carrying the MIB from the BCH;
[0091] - a physical downlink shared channel (PDSCH) for carrying downlink data and signaling messages from the DL-SCH, as well as paging messages from the PCH;
[0092] - a physical downlink control channel (PDCCH) for carrying downlink control information (DCI), which may include downlink scheduling commands, uplink scheduling grants, and uplink power control commands;
[0093] - a physical uplink shared channel (PUSCH) for carrying uplink data and signaling messages from the UL-SCH and in some instances uplink control information (UCI) as described below;
[0094] - a physical uplink control channel (PUCCH) for carrying UCI, which may include HARQ acknowledgments, channel quality indicators (CQI), pre-coding matrix indicators (PMI), rank indicators (Rl), and scheduling requests (SR); and
[0095] - a physical random access channel (PRACH) for random access.
[0096] Similar to the physical control channels, the physical layer generates physical signals to support the low-level operation of the physical layer. As shown in FIG. 5A and FIG. 5B, the physical layer signals defined by NR include: primary synchronization signals (PSS), secondary synchronization signals (SSS), channel state information reference signals (CSI-RS), demodulation reference signals (DMRS), sounding reference signals (SRS), and phase-tracking reference signals (PT-RS). These physical layer signals will be described in greater detail below.
[0097] FIG. 2B illustrates an example NR control plane protocol stack. As shown in FIG. 2B, the NR control plane protocol stack may use the same / similar first four protocol layers as the example NR user plane protocol stack. These four protocol layers include the PHYs 211 and 221, the MACs 212 and 222, the RLCs 213 and 223, and the PDCPsDocket No.25-1081 PCT214 and 224. Instead of having the SDAPs 215 and 225 at the top of the stack as in the NR user plane protocol stack, the NR control plane stack has radio resource controls (RRCs) 216 and 226 and NAS protocols 217 and 237 at the top of the NR control plane protocol stack.
[0098] The NAS protocols 217 and 237 may provide control plane functionality between the UE 210 and the AMF 230 (e.g., the AMF 158A) or, more generally, between the UE 210 and the CN. The NAS protocols 217 and 237 may provide control plane functionality 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 the NAS messages can be transported The NAS messages may be transported using the AS of the Uu and NG interfaces. NAS protocols 217 and 237 may provide control plane functionality such as authentication, security, connection setup, mobility management, and session management.
[0099] The RRCs 216 and 226 may provide control plane functionality 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 functionality between the UE 210 and the gNB 220 via signaling messages, referred to as RRC messages. RRC messages may be transmitted 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 RRCs 216 and 226 may provide control plane functionality such as: broadcast of system information related to AS and NAS; paging initiated by the CN or the RAN; establishment, maintenance and release of an RRC connection between the UE 210 and the RAN; security functions including key management; establishment, configuration, maintenance and release of signaling radio bearers and data radio bearers; mobility functions; QoS management functions; the UE measurement reporting and control of the reporting; detection of and recovery from radio link failure (RLF); and / or NAS message transfer. As part of establishing an RRC connection, RRCs 216 and 226 may establish an RRC context, which may involve configuring parameters for communication between the UE 210 and the RAN.
[0100] FIG. 6 is an example diagram showing RRC state transitions of a UE. The UE may be the same or similar to the wireless device 106 depicted in FIG. 1A, the UE 210 depicted in FIG. 2Aand FIG.2B, or any other wireless device described in the present disclosure. As illustrated in FIG. 6, a UE may be in at least one of three RRC states: RRC connected 602 (e.g., RRC_CONNECTED), RRC idle 604 (e.g., RRCJDLE), and RRC inactive 606 (e.g., RRCJNACTIVE).
[0101] In RRC connected 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 one or more base stations included in the RAN 104 depicted in FIG. 1A, one of the gNBs 160 or ng-eNBs 162 depicted in FIG. 1B, the gNB 220 depicted in FIG. 2Aand FIG. 2B, or any other base station described in the present disclosure. The base station with which the UE is connected may have the RRC context for the UE. The RRC context, referred to as the UE context, may comprise parameters for communication between the UE and the base station. These parameters may include, for example: one or more AS contexts; one or more radio link configuration parameters; bearer configuration information (e.g., relating to a data radio bearer, signaling radio bearer, logical channel, QoS flow, and / or PDU session); security information; and / or PHY, MAC,Docket No.25-1081 PCTRLC, PDCP, and / or SDAP layer configuration information. While in RRC connected 602, mobility of the UE may be managed by the RAN (e.g., the RAN 104 or the NG-RAN 154). The UE may measure the 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 a 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 through a connection release procedure 608 or to RRC inactive 606 through a connection inactivation procedure 610.
[0102] 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 the base station. While in RRC idle 604, the UE may be in a sleep state for the majority of the time (e.g., to conserve battery power). The UE may wake up periodically (e.g., once in every discontinuous reception cycle) to monitor for paging messages from the RAN. 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 greater detail below.
[0103] In RRC inactive 606, the RRC context previously established is maintained in the UE and the base station. This allows for a fast transition to RRC connected 602 with reduced signaling overhead as compared to the transition from RRC idle 604 to RRC connected 602. While in RRC inactive 606, the UE may be in a sleep state and 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 resume procedure 614 or to RRC idle 604 though a connection release procedure 616 that may be the same as or similar to connection release procedure 608.
[0104] An 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 be able to notify the UE of an event via a paging message without having to broadcast the paging message over the entire mobile communications network. The mobility management mechanism used in RRC idle 604 and RRC inactive 606 may allow the network to track the UE on a cell-group level so that the paging message may be broadcast over the cells of the cell group that the UE currently resides within instead of the entire mobile communication network. The mobility management mechanisms for RRC idle 604 and RRC inactive 606 track the UE on a cell-group level. They may do so using different granularities of grouping. For example, there may be three levels of cell-grouping granularity: individual cells; cells within a RAN area identified by a RAN area identifier (RAI); and cells within a group of RAN areas, referred to as a tracking area and identified by a tracking area identifier (TAI).
[0105] Tracking areas may be used to track the UE at the CN level. The CN (e.g., the CN 102 or the 5G-CN 152) may provide the UE with a list of TAIs associated with a UE registration area. If the UE moves, through cell reselection, to a cell associated with a TAI not included in the list of TAIs associated with the 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 the UE registration area.Docket No.25-1081 PCT
[0106] RAN areas may be used to track the UE at the RAN level. For a UE in RRC inactive 606 state, the UE may be assigned a RAN notification area. A RAN notification area may comprise 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, through cell reselection, to a cell not included in the RAN notification area assigned to the UE, the UE may perform a notification area update with the RAN to update the UE's RAN notification area.
[0107] A base station storing an RRC context for a UE or a last serving base station of the UE may be referred to as an anchor base station. An anchor base station may maintain an RRC context for the UE at least during a period of time that the UE stays in a RAN notification area of the anchor base station and / or during a period of time that the UE stays in RRC inactive 606.
[0108] A gNB, such as gNBs 160 in FIG. 1B, may be split into two parts: a central unit (gNB-CU), and one or more distributed units (gNB-DU). A gNB-CU may be coupled to one or more gNB-DUs using an F1 interface. The gNB-CU may comprise the RRC, the PDCP, and the SOAP. A gNB-DU may comprise the RLC, the MAC, and the PHY.
[0109] In NR, the physical signals and physical channels (discussed with respect to FIG.5A and FIG. 5B) may be mapped onto orthogonal frequency divisional multiplexing (OFDM) symbols. OFDM is a multicarrier communication scheme that transmits data over F orthogonal subcarriers (or tones). Before transmission, the data may be mapped to a series of complex symbols (e.g., M-quadrature amplitude modulation (M-QAM) or M-phase shift keying (M-PSK) symbols), referred to as source symbols, and divided into F parallel symbol streams. The F parallel symbol streams may be treated as though they are in the frequency domain and used as inputs to an Inverse Fast Fourier Transform (IFFT) block that transforms them into the time domain. The IFFT block may take in F source symbols at a time, one from each of the F parallel symbol streams, and use each source symbol to modulate the amplitude and phase of one of F sinusoidal basis functions that correspond to the F orthogonal subcarriers. The output of the IFFT block may be F time-domain samples that represent the summation of the F orthogonal subcarriers. The F time-domain samples may form a single OFDM symbol. After some processing (e.g., addition of a cyclic prefix) and up-conversion, an OFDM symbol provided by the IFFT block may be transmitted over the air interface on a carrier frequency. The F parallel symbol streams may be mixed using an FFT block before being processed by the IFFT block. This operation produces Discrete Fourier Transform (DFT)-precoded OFDM symbols and may be used by UEs in the uplink to reduce the peak to average power ratio (PAPR). Inverse processing may be performed on the OFDM symbol at a receiver using an FFT block to recover the data mapped to the source symbols.
[0110] FIG. 7 illustrates an example configuration of an NR frame into which OFDM symbols are grouped. An NR frame may be identified by a system frame number (SFN). The SFN may repeat with a period of 1024 frames. As illustrated, one NRframe may be 10 milliseconds (ms) in duration and may include 10 subframes that are 1 ms in duration. A subframe may be divided into slots that include, for example, 14 OFDM symbols per slot.
[0111] The duration of a slot may depend on the numerology used for the OFDM symbols of the slot. In NR, a flexible numerology is supported to accommodate different cell deployments (e.g., cells with carrier frequencies below 1 GHzDocket No.25-1081 PCTup to cells with carrier frequencies in the mm-wave range). A numerology may be defined in terms of subcarrier spacing and cyclic prefix duration. For a numerology in NR, subcarrier spacings may be scaled up by powers of two from a baseline subcarrier spacing of 15 kHz, and cyclic prefix durations may be scaled down by powers of two from a baseline cyclic prefix duration of 4.7 ps. For example, NR defines numerologies with the following subcarrier spacing / cyclic prefix duration combinations: 15 kHz / 4.7 ps; 30 kHz / 2.3 ps; 60 kHz / 1.2 ps; 120 kHz / 0.59 ps; and 240 kHz / 0.29 ps.
[0112] A slot may have a fixed number of OFDM symbols (e.g., 14 OFDM symbols). A numerology with a higher subcarrier spacing has a shorter slot duration and, correspondingly, more slots per subframe. FIG. 7 illustrates this numerology-dependent slot duration and slots-per-subframe transmission structure (the numerology with a subcarrier spacing of 240 kHz is not shown in FIG.7 for ease of illustration). A subframe in NR may be used as a numerologyindependent time reference, while a slot may be used as the unit upon which uplink and downlink transmissions are scheduled. To support low latency, scheduling in NR may be decoupled from the slot duration and start at any OFDM symbol and last for as many symbols as needed for a transmission. These partial slot transmissions may be referred to as mini-slot or subslot transmissions.
[0113] FIG. 8 illustrates an example configuration of a slot in the time and frequency domain for an NR carrier. The slot includes resource elements (REs) and resource blocks (RBs). An RE is the smallest physical resource in NR. An RE spans one OFDM symbol in the time domain by one subcarrier in the frequency domain as shown in FIG. 8. An RB spans twelve consecutive REs in the frequency domain as shown in FIG. 8. An NR carrier may be limited to a width of 275 RBs or 275*12 = 3300 subcarriers. Such a limitation, if used, may limit the NR carrier to 50, 100, 200, and 400 MHz for subcarrier spacings of 15, 30, 60, and 120 kHz, respectively, where the 400 MHz bandwidth may be set based on a 400 MHz per carrier bandwidth limit.
[0114] FIG. 8 illustrates a single numerology being used across the entire bandwidth of the NR carrier. In other example configurations, multiple numerologies may be supported on the same carrier.
[0115] 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). Also, 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, a UE may adapt the size of the UE’s receive bandwidth based on the amount of traffic the UE is scheduled to receive. This is referred to as bandwidth adaptation.
[0116] NR defines bandwidth parts (BWPs) to support UEs not capable of receiving the full carrier bandwidth and to support bandwidth adaptation. In an example, a BWP may be defined by a subset of contiguous RBs on a carrier. A UE may be configured (e.g., via 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 a serving cell may be active. These one or more BWPs may be referred to as active BWPs 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.Docket No.25-1081 PCT
[0117] For unpaired spectra, 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 a downlink BWP index of the downlink BWP and an uplink BWP index of the uplink BWP are the same. For unpaired spectra, a UE may expect that a center frequency for a downlink BWP is the same as a center frequency for an uplink BWP.
[0118] For a downlink BWP in a set of configured downlink BWPs on a primary cell (PCell), a 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 domains where the UE may find control information. The search space may be a UE-specific search space or a common search space (potentially usable by a plurality of UEs). For example, a base station may configure a UE with a common search space, on a PCell or on a primary secondary cell (PSCell), in an active downlink BWP.
[0119] For an uplink BWP in a set of configured uplink BWPs, a BS may configure a UE with one or more resource sets for one or more PUCCH transmissions. A UE may receive downlink receptions (e.g., PDCCH or PDSCH) in a downlink BWP according to a configured numerology (e.g., subcarrier spacing and cyclic prefix duration) for the downlink BWP. The UE may transmit uplink transmissions (e.g., PUCCH or PUSCH) in an uplink BWP according to a configured numerology (e.g., subcarrier spacing and cyclic prefix length for the uplink BWP).
[0120] One or more BWP indicator fields may be provided in Downlink Control Information (DCI). A value of a BWP indicator field may indicate which BWP in a set of configured BWPs is an active downlink BWP for one or more downlink receptions. The value of the one or more BWP indicator fields may indicate an active uplink BWP for one or more uplink transmissions.
[0121] A base station may semi-statical ly configure a UE with a default downlink BWP within a set of configured downlink BWPs associated with a PCell. If the base station does not provide the default downlink BWP to the UE, the default downlink BWP may be an initial active downlink BWP. The UE may determine which BWP is the initial active downlink BWP based on a CORESET configuration obtained using the PBCH.
[0122] A base station may configure a UE with a BWP inactivity timer value for a PCell. The UE may start or restart a BWP inactivity timer at any appropriate time. For example, the UE may start or restart the BWP inactivity timer (a) when the UE detects a DCI indicating an active downlink BWP other than a default downlink BWP for a paired spectra operation; or (b) when a UE detects a DCI indicating an active downlink BWP or active uplink BWP other than a default downlink BWP or uplink BWP for an unpaired spectra operation. If the UE does not detect DCI during an interval of time (e.g., 1 ms or 0.5 ms), the UE may run the BWP inactivity timer toward expiration (for example, increment from zero to the BWP inactivity timer value, or 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.
[0123] In an example, a base station may semi-statically configure a UE with one or more BWPs. A UE may switch an active BWP from a first BWP to a second BWP in response to receiving a DCI indicating the second BWP as an active BWP and / or in response to an expiry of the BWP inactivity timer (e.g., if the second BWP is the default BWP).Docket No.25-1081 PCT
[0124] Downlink and uplink BWP switching (where BWP switching refers to switching from a currently active BWP to a not currently active BWP) may be performed independently in paired spectra. In unpaired spectra, downlink and uplink BWP switching may be performed simultaneously. Switching between configured BWPs may occur based on RRC signaling, DCI, expiration of a BWP inactivity timer, and / or an initiation of random access.
[0125] FIG. 9 illustrates an example of bandwidth adaptation using three configured BWPs for an NR carrier. A UE configured with the three BWPs may switch from one BWP to another BWP ata switching point. In the example illustrated in FIG. 9, the BWPs include: a BWP 902 with a bandwidth of 40 MHz and a subcarrier spacing of 15 kHz; a BWP 904 with a bandwidth of 10 MHz and a subcarrier spacing of 15 kHz; and a BWP 906 with a bandwidth of 20 MHz and a subcarrier spacing of 60 kHz. The BWP 902 may be an initial active BWP, and the BWP 904 may be a default BWP. The UE may switch between BWPs at switching points. In the example of FIG. 9, the UE may switch from the BWP 902 to the BWP 904 at a switching point 908. The switching at the switching point 908 may occur for any suitable reason, for example, in response to an expiry of a BWP inactivity timer (indicating switching to the default BWP) and / or in response to receiving a DCI indicating BWP 904 as the active BWP. The UE may switch at a switching point 910 from active BWP 904 to BWP 906 in response to receiving a DCI indicating BWP 906 as the active BWP. The UE may switch at a switching point 912 from active BWP 906 to BWP 904 in response to an expiry of a BWP inactivity timer and / or in response to receiving a DCI indicating BWP 904 as the active BWP. The UE may switch at a switching point 914 from active BWP 904 to BWP 902 in response to receiving a DCI indicating BWP 902 as the active BWP.
[0126] If a UE is configured for a secondary cell with a default downlink BWP in a set of configured downlink BWPs and a timer value, UE procedures for switching BWPs on a secondary cell maybe the same / similar as those on a primary cell. For example, the UE may use the timer value and the default downlink BWP for the secondary cell in the same / similar manner as the UE would use these values for a primary cell.
[0127] To provide for greater data rates, two or more carriers can be aggregated and simultaneously transmitted to / from the same UE using carrier aggregation (CA). The aggregated carriers in CA may be referred to as component carriers (CCs). When CA is used, there are a number of serving cells for the UE, one for a CC. The CCs may have three configurations in the frequency domain.
[0128] FIG. 10A illustrates the three CA configurations with two CCs. In the intraband, contiguous configuration 1002, the two CCs are aggregated in the same frequency band (frequency band A) and are located directly adjacent to each other within the frequency band. In the intraband, non-contiguous configuration 1004, the two CCs are aggregated in the same frequency band (frequency band A) and are separated in the frequency band by a gap. In the interband configuration 1006, the two CCs are located in frequency bands (frequency band A and frequency band B).
[0129] In an example, up to 32 CCs may be aggregated. The aggregated CCs may have the same or different bandwidths, subcarrier spacing, and / or duplexing 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 be optionally configured for a serving cell. The ability to aggregate more downlink carriers than uplink carriers may be useful, for example, when the UE has more data traffic in the downlink than in the uplink.Docket No.25-1081 PCT
[0130] When CA is used, one of the aggregated cells for a UE may be referred to as a primary cell (PCell). The PCell may be the serving cell that the UE initially connects to at RRC connection establishment, reestablishment, and / or handover. The PCell may provide the UE with NAS mobility information and the security input. UEs may have different PCells. In the downlink, the carrier corresponding to the PCell may be referred to as the downlink primary CC (PCC). In the uplink, the carrier corresponding to the PCell may be referred to as the uplink PCC. The other aggregated cells for the UE may be referred to as secondary cells (SCells). In an example, the SCells may be configured after the PCell is configured for the UE. For example, an SCell may be configured through an RRC Connection Reconfiguration procedure. In the downlink, the carrier corresponding to an SCell may be referred to as a downlink secondary CC (SCC). In the uplink, the carrier corresponding to the SCell may be referred to as the uplink SCC.
[0131] Configured SCells for a UE may be activated and deactivated based on, for example, traffic and channel conditions. Deactivation of an SCell may mean that PDCCH and PDSCH reception on the SCell is stopped and PUSCH, SRS, and CQI transmissions on the SCell are stopped. Configured SCells maybe activated and deactivated using a MAC CE with respect to FIG. 4B. For example, a MAC CE may use a bitmap (e.g., one bit per SCell) to indicate which SCells (e.g., in a subset of configured SCells) for the UE are activated or deactivated. Configured SCells may be deactivated in response to an expiration of an SCell deactivation timer (e.g., one SCell deactivation timer per SCell).
[0132] Downlink control information, such as scheduling assignments and scheduling grants, for a cell may be transmitted on the cell corresponding to the assignments and grants, which is known as self-scheduling. The DCI for the cell may be transmitted on another cell, which is known as cross-carrier scheduling. Uplink control information (e.g., HARQ acknowledgments and channel state feedback, such as CQI, PMI, and / or Rl) for aggregated cells may be transmitted on the PUCCH of the PCell. For a larger number of aggregated downlink CCs, the PUCCH of the PCell may become overloaded. Cells may be divided into multiple PUCCH groups.
[0133] FIG. 10B illustrates an example of how aggregated cells may be configured into one or more PUCCH groups. A PUCCH group 1010 and a PUCCH group 1050 may include one or more downlink CCs, respectively. In the example of FIG. 10B, the PUCCH group 1010 includes three downlink CCs: a PCell 1011, an SCell 1012, and an SCell 1013. The PUCCH group 1050 includes three downlink CCs in the present example: a PCell 1051, an SCell 1052, and an SCell 1053. One or more uplink CCs may be configured as a PCell 1021, an SCell 1022, and an SCell 1023. One or more other uplink CCs may be configured as a primary SCell (PSCell) 1061, an SCell 1062, and an SCell 1063. Uplink control information (UCI) related to the downlink CCs of the PUCCH group 1010, shown as UCI 1031, UCI 1032, and UCI 1033, may be transmitted in the uplink of the PCell 1021. Uplink control information (UCI) related to the downlink CCsof the PUCCH group 1050, shown as UCI 1071, UCI 1072, and UCI 1073, maybe transmitted in the uplink of the PSCell 1061. In an example, if the aggregated cells depicted in FIG. 10B were not divided into the PUCCH group 1010 and the PUCCH group 1050, a single uplink PCell to transmit UCI relating to the downlink CCs, and the PCell may become overloaded. By dividing transmissions of UCI between the PCell 1021 and the PSCell 1061, overloading may be prevented.Docket No.25-1081 PCT
[0134] A cell, comprising a downlink carrier and optionally an uplink carrier, may be assigned with a physical cell ID and a cell index. The physical cell ID or the cell index may identify a downlink carrier and / or an uplink carrier of the cell, for example, depending on the context in which the physical cell ID is used. A physical cell ID may be determined using a synchronization signal transmitted on a downlink component carrier. A cell index may be determined using RRC messages. In the disclosure, a physical cell ID may be referred to as a carrier ID, and a cell index may be referred to as a carrier index. For example, when the disclosure refers to a first physical cell ID for a first downlink carrier, the disclosure may mean the first physical cell ID is for a cell comprising the first downlink carrier. The same / similar concept may apply to, for example, a carrier activation When the disclosure indicates that a first carrier is activated, the specification may mean that a cell comprising the first carrier is activated.
[0135] In CA, a multi-carrier nature of a PHY may be exposed to a MAC. In an example, a HARQ entity may operate on a serving cell. A transport block may be generated per assignment / grant per serving cell. A transport block and potential HARQ retransmissions of the transport block may be mapped to a serving cell.
[0136] In the downlink, a base station may transmit (e.g., unicast, multicast, and / or broadcast) one or more Reference Signals (RSs) to a UE (e.g., PSS, SSS, CSI-RS, DMRS, and / or PT-RS, as shown in FIG.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. 5B). The PSS and the SSS may be transmitted by the base station and used by the UE to synchronize the UE to the base station The PSS and the SSS may be provided in a synchronization signal (SS) I physical broadcast channel (PBCH) block that includes the PSS, the SSS, and the PBCH. The base station may periodically transmit a burst of SS / PBCH blocks.
[0137] FIG. 11A illustrates an example of an SS / PBCH block's structure and location. A burst of SS / PBCH blocks may include one or more SS / PBCH blocks (e.g., 4 SS / PBCH blocks, as shown in FIG. 11 A). Bursts maybe transmitted periodically (e.g., every 2 frames or 20 ms). A burst may be restricted to a half-frame (e.g., a first half-frame having a duration of 5 ms). It will be understood that FIG. 11 A is an example, and that these parameters (number of SS / PBCH blocks per burst, periodicity of bursts, position of burst within the frame) may be configured based on, for example: a carrier frequency of a cell in which the SS / PBCH block is transmitted; a numerology or subcarrier spacing of the cell; a configuration by the network (e.g, using RRC signaling); or any other suitable factor. In an example, the UE may assume a subcarrier spacing for the SS / PBCH block based on the carrier frequency being monitored, unless the radio network configured the UE to assume a different subcarrier spacing.
[0138] The SS / PBCH block may span one or more OFDM symbols in the time domain (e.g., 4 OFDM symbols, as shown in the example of FIG. 11A) and may span one or more subcarriers in the frequency domain (e.g., 240 contiguous subcarriers). The PSS, the SSS, and the 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., across the next 3 OFDM symbols) and may span 240 subcarriers.Docket No.25-1081 PCT
[0139] The location of the SS / PBCH block in the time and frequency domains may not be known to the UE (e.g., if the UE is searching for the cell). To find and select the cell, the UE may monitor a carrier for the PSS. For example, the UE may monitor a frequency location within the carrier. If the PSS is not found after a certain duration (e.g., 20 ms), the UE may search for the PSS at a different frequency location within the carrier, as indicated by a synchronization raster. If the PSS is found at a location in the time and frequency domains, the UE may determine, based on a known structure of the SS / PBCH block, the locations of the SSS and the PBCH, respectively. The SS / PBCH block may be a celldefining 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, a cell selection / search and / or reselection may be based on the CD-SSB.
[0140] 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 a physical cell identifier (PCI) of the cell based on the sequences of the PSS and the SSS, respectively. The UE may determine a location of a 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 in accordance with a transmission pattern, wherein a SS / PBCH block in the transmission pattern is a known distance from the frame boundary.
[0141] The PBCH may use a QPSK modulation and may use forward error correction (FEC). The FEC may use polar coding. One or more symbols spanned by the PBCH may carry one or more DMRSs for demodulation of the PBCH. The PBCH may include an indication of a current system frame number (SFN) of the cell and / or a SS / PBCH block timing index. These parameters may facilitate time synchronization of the UE to the base station. The PBCH may include a master information block (MIB) used to provide the UE with one or more parameters. The MIB may be used by the UE to locate remaining minimum system information (RMSI) associated with the cell. The RMSI may include a System Information Block Type 1 (SIB1). The SIB1 may contain information needed by the UE to access the cell. The UE may use one or more parameters of the MIB to monitor PDCCH, which may be used to schedule PDSCH. The PDSCH may include the SIB1. The SIB1 may be decoded using parameters provided in the MIB. The PBCH may indicate an absence of SIB1. Based on the PBCH indicating the absence of SIB1, the UE maybe pointed to a frequency. The UE may search for an SS / PBCH block at the frequency to which the UE is pointed.
[0142] The UE may assume that one or more SS / PBCH blocks transmitted with a 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 having different SS / PBCH block indices.
[0143] SS / PBCH blocks (e.g., those within a half-frame) may be transmitted in spatial directions (e.g., using different beams that span a coverage area of the 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.
[0144] In an example, within a frequency span of a carrier, a base station may transmit a plurality of SS / PBCH blocks. In an example, a first PCI of a first SS / PBCH block of the plurality of SS / PBCH blocks may be different from aDocket No.25-1081 PCTsecond PCI of a second SS / PBCH block of the plurality of SS / PBCH blocks. The PCIs of SS / PBCH blocks transmitted in different frequency locations may be different or the same.
[0145] The CSI-RS may be transmitted by the base station and used by the UE to acquire channel state information (CSI). The base station may configure the UE with one or more CSI-RSs for channel estimation or any other suitable purpose. The base station may configure a UE with one or more of the same / similar CSI-RSs. The UE may measure the one or more CSI-RSs. The UE may estimate a downlink channel state and / or generate a CSI report based on the measuring of the one or more downlink CSI-RSs. The UE may provide the CSI report to the base station. The base station may use feedback provided by the UE (e.g., the estimated downlink channel state) to perform link adaptation.
[0146] The base station may semi-statically configure the UE with one or more CSI-RS resource sets. A CSI-RS resource may be associated with a location in the time and frequency domains and a periodicity. The base station may selectively activate and / or deactivate a CSI-RS resource. The base station may indicate to the UE that a CSI-RS resource in the CSI-RS resource set is activated and / or deactivated.
[0147] The base station may configure the UE to report CSI measurements. The base station may configure the UE to provide CSI reports periodically, aperiodically, or semi-persistently. For periodic CSI reporting, the UE maybe configured with a timing and / or periodicity of a plurality of CSI reports. For aperiodic CSI reporting, the base station may request a CSI report. For example, the base station may command the UE to measure a configured CSI-RS resource and provide a CSI report relating to the measurements. For semi-persistent CSI reporting, the base station may configure the UE to transmit periodically, and selectively activate or deactivate the periodic reporting. The base station may configure the UE with a CSI-RS resource set and CSI reports using RRC signaling.
[0148] The CSI-RS configuration may comprise one or more parameters indicating, for example, up to 32 antenna ports. The UE may be configured to employ the same OFDM symbols for a downlink CSI-RS and a control resource set (CORESET) when the downlink CSI-RS and CORESET are spatially QCLed and resource elements associated with the downlink CSI-RS are outside of the physical resource blocks (PRBs) configured for the CORESET. The UE may be configured to employ the same OFDM symbols for downlink CSI-RS and SS / PBCH blocks when the downlink CSI-RS and SS / PBCH blocks are spatially QCLed and resource elements associated with the downlink CSI-RS are outside of PRBs configured for the SS / PBCH blocks.
[0149] Downlink DMRSs may be transmitted by a base station and used by a UE for channel estimation. For example, the downlink DMRS may be used for coherent demodulation of one or more downlink physical channels (e.g., PDSCH). An NR network may support one or more variable and / or configurable DMRS patterns for data demodulation. At least one downlink DMRS configuration may support a front-loaded DMRS pattern. A front-loaded DMRS may be mapped over one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). A base station may semi-statically configure the UE with a number (e.g., a maximum number) of front-loaded DMRS symbols for PDSCH. A DMRS configuration may support one or more DMRS ports. For example, for single user-MIMO, a DMRS configuration may support up to eight orthogonal downlink DMRS ports per UE. For multiuser-MIMO, a DMRS configuration may support up to 4 orthogonal downlink DMRS ports per UE. A radio network may support (e.g., at least for CP-OFDM) aDocket No.25-1081 PCTcommon DMRS structure for downlink and uplink, wherein a DMRS location, a DMRS pattern, and / or a scrambling sequence may be the same or different. The base station may transmit a downlink DMRS and a corresponding PDSCH using the same precoding matrix. The UE may use the one or more downlink DMRSs for coherent demodulation / channel estimation of the PDSCH.
[0150] In an example, a transmitter (e.g., a base station) may use a precoder matrices for a part of a transmission bandwidth. For example, the 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 a same precoding matrix is used across a set of PRBs. The set of PRBs may be denoted as a precoding resource block group (PRG).
[0151] A PDSCH may comprise one or more layers. The UE may assume that at least one symbol with DMRS is present on a layer of the one or more layers of the PDSCH. A higher layer may configure up to 3 DMRSs for the PDSCH.
[0152] Downlink PT-RS may be transmitted by a base station and used by a UE for phase-noise compensation. Whether a downlink PT-RS is present or not may depend on an RRC configuration. The presence and / or pattern of the downlink PT-RS may be configured on a UE-specific basis using a combination of RRC signaling and / or an association with one or more parameters employed for other purposes (e.g., modulation and coding scheme (MCS)), which may be indicated by DCI. When configured, a dynamic presence of a downlink PT-RS may be associated with one or more DCI parameters comprising at least MCS. An NR network may support a plurality of PT-RS densities defined in the time and / or frequency domains. When present, a frequency domain density may be associated with at least one configuration of a scheduled bandwidth. The UE may assume a same precoding for a DMRS port and a PT-RS port. A number of PT-RS ports may be fewer than a number of DMRS ports in a scheduled resource. Downlink PT-RS may be confined in the scheduled time / frequency duration for the UE. Downlink PT-RS may be transmitted on symbols to facilitate phase tracking at the receiver.
[0153] The UE may transmit an uplink DMRS to a base station for channel estimation. For example, the base station may use the uplink DMRS for coherent demodulation of 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 range of frequencies that is similar to a range of frequencies 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 pattern. The front-loaded DMRS maybe mapped over one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). One or more uplink DMRSs may be configured to transmit at one or more symbols of a PUSCH and / or a PUCCH. The base station may semi-statically configure the UE with a number (e.g., maximum number) of front-loaded DMRS symbols for the PUSCH and / or the PUCCH, which the UE may use to schedule a single-symbol DMRS and / or a double-symbol DMRS. An NR network may support (e.g., for cyclic prefix orthogonal frequency division multiplexing (CP-OFDM)) a common DMRS structure for downlink and uplink, wherein a DMRS location, a DMRS pattern, and / or a scrambling sequence for the DMRS may be the same or different.Docket No.25-1081 PCT
[0154] A PUSCH may comprise one or more layers, and the UE may transmit at least one symbol with DMRS present on a layer of the one or more layers of the PUSCH. In an example, a higher layer may configure up to three DMRSs for the PUSCH.
[0155] Uplink PT-RS (which may be used by a base station for phase tracking and / or phase-noise compensation) may or may not be present depending on an RRC configuration of the UE. The presence and / or pattern of uplink PT-RS may be configured on a UE-specific basis by a combination of RRC signaling and / or one or more parameters employed for other purposes (e.g., Modulation and Coding Scheme (MCS)), which may be indicated by DCI. When configured, a dynamic presence of uplink PT-RS may be associated with one or more DCI parameters comprising at least MCS. A radio network may support a plurality of uplink PT-RS densities defined in time / frequency domain. When present, a frequency domain density may be associated with at least one configuration of a scheduled bandwidth. The UE may assume a same precoding for a DMRS port and a PT-RS port. A number of PT-RS ports may be fewer than a number of DMRS ports in a scheduled resource. For example, uplink PT-RS may be confined in the scheduled time / frequency duration for the UE.
[0156] SRS may be transmitted by a UE to a base station for channel state estimation to support uplink channel dependent scheduling and / or link adaptation. SRS transmitted by the UE may allow a base station to estimate an uplink channel state at one or more frequencies. A scheduler at the base station may employ the estimated uplink channel state to assign one or more resource blocks for an uplink PUSCH transmission from the UE. The base station may semi-statically configure the UE with one or more SRS resource sets. Foran SRS resource set, the base station may configure the UE with one or more SRS resources. An SRS resource set applicability may be configured by a higher layer (e.g., RRC) parameter. For example, when a higher layer parameter indicates beam management, an SRS resource in an SRS resource set of the one or more SRS resource sets (e.g., with the same / similar time domain behavior, periodic, aperiodic, and / or the like) may be transmitted at a time instant (e.g., simultaneously). The UE may transmit one or more SRS resources in SRS resource sets. An NR network may support aperiodic, periodic and / or semi-persistent SRS transmissions. The UE may transmit SRS resources based on one or more trigger types, wherein the one or more trigger types may comprise higher layer signaling (e.g., RRC) and / or one or more DCI formats. In an example, at least one DCI format may be employed for the UE to select at least one of one or more configured SRS resource sets. An SRS trigger type 0 may refer to an SRS triggered based on a higher layer signaling. An SRS trigger type 1 may refer to an SRS triggered based on one or more DCI formats. In an example, when PUSCH and SRS are transmitted in a same slot, the UE may be configured to transmit SRS after a transmission of a PUSCH and a corresponding uplink DMRS.
[0157] The base station may semi-statically configure the UE with one or more SRS configuration parameters indicating at least one of following: a SRS resource configuration identifier; a number of SRS ports; time domain behavior of an SRS resource configuration (e.g., an indication of periodic, semi-persistent, or aperiodic SRS); slot, minislot, and / or subframe level periodicity; offset for a periodic and / or an aperiodic SRS resource; a number of OFDMDocket No.25-1081 PCTsymbols in an SRS resource; a starting OFDM symbol of an SRS resource; an SRS bandwidth; a frequency hopping bandwidth; a cyclic shift; and / or an SRS sequence ID.
[0158] An antenna port is defined such that the channel over which a symbol on the antenna port is conveyed can be inferred from the channel over which another symbol on the same antenna port is conveyed. If a first symbol and a second symbol are transmitted on the same antenna port, the receiver may infer the channel (e.g., fading gain, multipath delay, and / or the like) for conveying the second symbol on the antenna port, from the channel for conveying the first symbol on the antenna port. A first antenna port and a second antenna port may be referred to as quasi colocated (QCLed) if one or more large-scale properties of the channel over which a first symbol on the first antenna port is conveyed may be inferred from the channel over which a second symbol on a second antenna port is conveyed. The one or more large-scale properties may comprise at least one of: a delay spread; a Doppler spread; a Doppler shift; an average gain; an average delay; and / or spatial Receiving (Rx) parameters.
[0159] Channels that use beamforming require beam management. Beam management may comprise 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 measurement based on downlink reference signals (e.g., a channel state information reference signal (CSI-RS)) and generate a beam measurement report. The UE may perform the downlink beam measurement procedure after an RRC connection is set up with a base station
[0160] FIG. 11B illustrates an example of channel state information reference signals (CSI-RSs) that are mapped in the time and frequency domains. A square shown in FIG. 11 B may span a resource block (RB) within a bandwidth of a cell. A base station may transmit one or more RRC messages comprising CSI-RS resource configuration parameters indicating one or more CSI-RSs. One or more of the following parameters may be configured by higher layer signaling (e.g., RRC and / or MAC signaling) for a CSI-RS resource configuration: a CSI-RS resource configuration identity, a number of CSI-RS ports, a CSI-RS configuration (e.g., symbol and resource element (RE) locations in a subframe), a CSI-RS subframe configuration (e.g., subframe location, offset, and periodicity in a radio frame), a CSI-RS power parameter, a CSI-RS sequence parameter, a code division multiplexing (CDM) type parameter, a frequency density, a 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.
[0161] The three beams illustrated in FIG. 11 B may be configured for a UE in a UE-specific configuration. Three beams are illustrated in FIG. 11 B (beam #1, beam #2, and beam #3), more or fewer beams may be configured. Beam #1 may be allocated with CSI-RS 1101 that may be transmitted in one or more subcarriers in an RB of a first symbol. Beam #2 may be allocated with CSI-RS 1102 that may be transmitted in one or more subcarriers in an RB of a second symbol. Beam #3 may be allocated with CSI-RS 1103 that may be transmitted in one or more subcarriers in an RB of a third symbol. By using frequency division multiplexing (FDM), a base station may use other subcarriers in a same RB (for example, those that are not used to transmit CSI-RS 1101) to transmit another CSI-RS associated with a beam forDocket No.25-1081 PCTanother U E. By using time domain multiplexing (TDM), beams used for the UE may be configured such that beams for the UE use symbols from beams of other UEs.
[0162] CSI-RSs such as those illustrated in FIG. 11B (e.g., CSI-RS 1101, 1102, 1103) may be transmitted by the base station and used by the UE for one or more measurements. For example, the UE may measure a reference signal received power (RSRP) of configured CSI-RS resources. The base station may configure the UE with a reporting configuration and the UE may report the RSRP measurements to a network (for example, via one or more base stations) based on the reporting configuration. In an example, the base station may determine, based on the reported measurement results, one or more transmission configuration indication (TCI) states comprising a number of reference signals. In an example, the base station may indicate one or more TCI states to the UE (e.g., via RRC signaling, a MAC CE, and / or a DCI). The UE may receive a downlink transmission with a receive (Rx) beam determined based on the one or more TCI states. In an example, the UE may or may not have a capability of beam correspondence. If the UE has the capability of beam correspondence, the UE may determine a spatial domain filter of a transmit (Tx) beam based on a spatial domain filter of the corresponding Rx beam. If the UE does not have the capability of beam correspondence, the UE may perform an uplink beam selection procedure to determine the spatial domain filter of the Tx beam. The UE may perform the 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 uplink beams for the UE based on measurements of the one or more SRS resources transmitted by the UE.
[0163] In a beam management procedure, a UE may assess (e.g., measure) a channel quality of one or more beam pair links, a beam pair link comprising a transmitting beam transmitted by a base station and a receiving 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 comprising, e.g., one or more beam identifications (e.g., a beam index, a reference signal index, or the like), RSRP, a precoding matrix indicator (PMI), a channel quality indicator (CQI), and / or a rank indicator (Rl).
[0164] FIG. 12A illustrates examples of three downlink beam management procedures: P1, P2, and P3. Procedure P1 may enable a UE measurement on transmit (Tx) beamsofa transmission reception point (TRP) (or multiple TRPs), e.g., to support a selection of one or more base station Tx beams and / or UE Rx beams (shown as ovals in the top row and bottom row, respectively, of P1 ). Beamforming at a TRP may comprise a Tx beam sweep for a set of beams (shown, in the top rows of P1 and P2, as ovals rotated in a counterclockwise direction indicated by the dashed arrow). Beamforming at a UE may comprise an Rx beam sweep for a set of beams (shown, in the bottom rows of P1 and P3, as ovals rotated in a clockwise direction indicated by the dashed arrow). Procedure P2 may be used to enable a UE measurement on Tx beams of a TRP (shown, in the top row of P2, as ovals rotated in a counterclockwise direction indicated by the dashed arrow). The UE and / or the base station may perform procedure P2 using a smaller set of beams than is used in procedure P1, or using narrower beams than the beams 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 an Rx beam at the UE.Docket No.25-1081 PCT
[0165] FIG. 12B illustrates examples of three uplink beam management procedures: U 1, U2, and U3. Procedure U1 may be used to enable a base station to perform a measurement on Tx beams of a UE, e.g., to support a selection of one or more UE Tx beams and / or base station Rx beams (shown as ovals in the top row and bottom row, respectively, of U1). Beamforming at the UE may include, e.g., a Tx beam sweep from a set of beams (shown in the bottom rows of U1 and U3 as ovals rotated in a clockwise direction indicated by the dashed arrow). Beamforming at the base station may include, e.g., an Rx beam sweep from a set of beams (shown, in the top rows of U1 and U2, as ovals rotated in a counterclockwise direction indicated by the dashed arrow). Procedure U2 may be used to enable the base station to adjust its Rx beam when the UE uses a fixed Tx beam The UE and / or the base station may perform procedure U2 using a smaller set of beams than is used in procedure P1, or using narrower beams than the beams 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.
[0166] A UE may initiate a beam failure recovery (BFR) procedure based on detecting a beam failure. The UE may transmit a BFR request (e.g., a preamble, a UCI, an SR, a MAC CE, and / or the like) based on the initiating of the BFR procedure. The UE may detect the beam failure based on a determination that a quality of beam pair link(s) of an associated control channel is unsatisfactory (e.g., having an error rate higher than an error rate threshold, a received signal power lower than a received signal power threshold, an expiration of a timer, and / or the like).
[0167] The UE may measure a quality of a beam pair link using one or more reference signals (RSs) comprising one or more SS / PBCH blocks, one or more CSI-RS resources, and / or one or more demodulation reference signals (DMRSs). A quality of the beam pair link may be based on one or more of 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 RS resources. The base station may indicate that an RS resource is quasi co-located (QCLed) with one or more DM-RSs of a channel (e.g., a control channel, a shared data channel, and / or the like). The RS resource and the one or more DMRSs of the channel may be QCLed when the channel characteristics (e.g., Doppler shift, Doppler spread, average delay, delay spread, spatial Rx parameter, fading, and / or the like) from a transmission via the RS resource to the UE are similar or the same as the channel characteristics from a transmission via the channel to the UE.
[0168] A network (e.g., a gNB and / or an ng-eNB of a network) and / or the UE may initiate a random access procedure. A UE in an RRCJ DLE state and / or an RRCJNACTIVE state may initiate the random access procedure to request a connection setup to a network. The UE may initiate the random access procedure from an RRC_CONNECTED state. The UE may initiate the random access procedure to request uplink resources (e.g., for uplink transmission of an SR when there is no PUCCH resource available) and / or acquire uplink timing (e.g., when uplink synchronization status is non-synchronized). The UE may initiate the random access procedure to request one or more system information blocks (SIBs) (e.g., other system information such as SIB2, SIB3, and / or the like). The UE may initiate the random access procedure for a beam failure recovery request. A network may initiate a random access procedure fora handover and / or for establishing time alignment for an SCell addition.Docket No.25-1081 PCT
[0169] FIG. 13A illustrates a four-step contention-based random access procedure. Prior to initiation of the procedure, a base station may transmit a configuration message 1310 to the UE. The procedure illustrated in FIG. 13A comprises transmission of four messages: a Msg 1 1311, a Msg 21312, a Msg 31313, and a Msg 41314. The Msg 1 1311 may include and / or be referred to as a preamble (or a random access preamble). The Msg 21312 may include and / or be referred to as a random access response (RAR).
[0170] 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 comprise at least one of following: general parameters for one or more random access procedures (e.g., RACH-configGeneral); cell-specific parameters (e.g., RACH-Con figCommon) and / or dedicated parameters (e.g., RACH-configDedicated). The base station may broadcastor 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 a UE in an RRC_CONNECTED state and / or in an RRC J NACTIVE state). The UE may determine, based on the one or more RACH parameters, a time-frequency resource and / or an uplink transmit power for transmission of the Msg 1 1311 and / or the Msg 31313. Based on the one or more RACH parameters, the UE may determine a reception timing and a downlink channel for receiving the Msg 21312 and the Msg 41314.
[0171] The one or more RACH parameters provided in the configuration message 1310 may indicate one or more Physical RACH (PRACH) occasions available for transmission of the Msg 1 1311. The one or more PRACH occasions may be predefined. The one or more RACH parameters may indicate one or more available sets of one or more PRACH occasions (e.g., prach-Configlndex). The one or more RACH parameters may indicate an association between (a) one or more PRACH occasions 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-RSs. For example, the one or more RACH parameters may indicate a number of SS / PBCH blocks mapped to a PRACH occasion and / or a number of preambles mapped to a SS / PBCH blocks.
[0172] The one or more RACH parameters provided in the configuration message 1310 may be used to determine an uplink transmit power of Msg 1 1311 and / or Msg 31313. For example, the one or more RACH parameters may indicate a reference power for a preamble transmission (e.g., a received target power and / or an initial power of the 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 ramping step; a power offset between SSB and CSI-RS; a power offset between transmissions of the Msg 1 1311 and the Msg 31313; 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., an SSB and / or CSI-RS) and / or an uplink carrier (e.g., a normal uplink (NUL) carrier and / or a supplemental uplink (SUL) carrier).
[0173] The Msg 1 1311 may include one or more preamble transmissions (e.g., a preamble transmission and one or more preamble retransmissions). An RRC message may be used to configure one or more preamble groups (e.g.,Docket No.25-1081 PCTgroup A and / or group B). A preamble group may comprise one or more preambles. The UE may determine the preamble group based on a pathloss measurement and / or a size of the Msg 31313. The UE may measure an RSRP of one or more reference signals (e.g., SSBs and / or CSI-RSs) and determine at least one reference signal having an RSRP above an RSRP threshold (e.g., rsrp-ThresholdSSB and / or rsrp-ThresholdCSI-RS). The UE may select at least one preamble associated with the one or more reference signals and / or a selected preamble group, for example, if the association between the one or more preambles and the at least one reference signal is configured by an RRC message.
[0174] 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 pathloss measurement, an RSRP measurement, and / or a size of the Msg 31313. 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). A base station may use the one or more RACH parameters to configure the UE with an association between one or more preambles and one or more reference signals (e.g., SSBs and / or CSI-RSs). If the association is configured, the UE may determine the preamble to include in Msg 1 1311 based on the association. The Msg 1 1311 may be transmitted to the base station via one or more PRACH occasions. The UE may use one or more reference signals (e.g., SSBs and / or CSI-RSs) for selection of the preamble and for determining of the PRACH occasion. One or more RACH parameters (e.g., ra-ssb-OccasionMsklndex and / or ra-OccasionList) may indicate an association between the PRACH occasions and the one or more reference signals.
[0175] The UE may perform a preamble retransmission if no response is received following a preamble transmission. The UE may increase an uplink transmit power for the preamble retransmission. The UE may select an initial preamble transmit power based on a pathloss measurement and / or a target received preamble power configured by the network. The UE may determine to retransmit a preamble and may ramp up the uplink transmit power. The UE may receive one or more RACH parameters (e.g., PREAMBLE_POWER_RAMP! NG_STEP) indicating a ramping step for the preamble retransmission. The ramping step may be an amount of incremental increase in uplink transmit power for a retransmission. The UE may ramp up the uplink transmit power if the UE determines a reference signal (e.g., SSB and / or CSI-RS) that is the same as a previous preamble transmission. The UE may count a number of preamble transmissions and / or retransmissions (e.g., PREAMBLE_TRANSMISSION_COUNTER). The UE may determine that a random access procedure completed unsuccessfully, for example, if the number of preamble transmissions exceeds a threshold configured by the one or more RACH parameters (e.g., preambleTransMax).
[0176] The Msg 21312 received by the UE may include an RAR. In some scenarios, the Msg 21312 may include multiple RARs corresponding to multiple UEs. The Msg 21312 may be received after or in response to the transmitting of the Msg 1 1311. The Msg 21312 maybe scheduled on the DL-SCH and indicated on a PDCCH using a random access RNTI (RA-RNTI). The Msg 21312 may indicate that the Msg 1 1311 was received by the base station. The Msg 21312 may include a time-alignment command that may be used by the UE to adjust the UE’s transmission timing, a scheduling grant for transmission of the Msg 31313, and / ora Temporary Cell RNTI (TC-RNTI). AfterDocket No. 25-1081 PCTtransmitting a preamble, the UE may start a time window (e.g., ra-ResponseWindow) to monitor a PDCCH for the Msg 21312. The UE may determine when to start the time window based on a PRACH occasion that the UE uses to transmit the preamble. For example, the UE may start the time window one or more symbols after a last symbol of the preamble (e.g., at a first PDCCH occasion from an end of a preamble transmission). The one or more symbols may be determined based on a numerology. The PDCCH may be in a common search space (e.g., a Typel -PDCCH common search space) configured by an RRC message. The UE may identify the RAR based on a Radio Network Temporary Identifier (RNTI). RNTIs may be used depending on one or more events initiating the random access procedure. The UE may use random access RNTI (RA-RNTI). The RA-RNTI may be associated with PRACH occasions in which the UE transmits a preamble. For example, the UE may determine the RA-RNTI based on: an OFDM symbol index; a slot index; a frequency domain index; and / or a UL carrier indicator of the PRACH occasions. An example of RA-RNTI may be as follows:
[0177] RA-RNTI= 1 + sjd + 14 x tjd + 14 x 80 x fjd + 14 x 80 x 8 x ul_carrier_id, where sjd may be an index of a first OFDM symbol of the PRACH occasion (e.g., 0 < sjd < 14), tjd may be an index of a first slot of the PRACH occasion in a system frame (e.g., 0 ≤ tjd < 80), fjd may be an index of the PRACH occasion in the frequency domain (e.g., 0 ≤ fjd < 8), and ul_carrier_id may be a UL carrier used for a preamble transmission (e.g., 0 for an NUL carrier, and 1 for an SUL carrier).
[0178] The UE may transmit the Msg 31313 in response to a successful reception of the Msg 2 1312 (e.g., using resources identified in the Msg 21312). The Msg 31313 maybe used for contention resolution in, for example, the contention-based random access procedure illustrated in FIG. 13A. In some scenarios, a plurality of UEs may transmit a same preamble to a base station and the base station may provide an RAR that corresponds to a UE. Collisions may occur if the plurality of UEs interpret the RAR as corresponding to themselves. Contention resolution (e.g., using the Msg 31313 and the Msg 41314) may be used to increase the likelihood that the UE does not incorrectly use an identity of another the UE. To perform contention resolution, the UE may include a device identifier in the Msg 31313 (e.g., a C-RNTI if assigned, a TC-RNTI included in the Msg 21312, and / or any other suitable identifier).
[0179] The Msg 41314 may be received after or in response to the transmitting of the Msg 31313. If a C-RNTI was included in the Msg 31313, the base station will address the UE on the PDCCH using the C-RNTI. If the UE's unique C-RNTI is detected on the PDCCH, the random access procedure is determined to be successfully completed. If a TC-RNTI is included in the Msg 31313 (e.g., if the UE is in an RRC_IDLE state or not otherwise connected to the base station), Msg 4 1314 will be received using a DL-SCH associated with the TC-RNTI. If a MAC PDU is successfully decoded and a MAC PDU comprises the UE contention resolution identity MAC CE that matches or otherwise corresponds with the CCCH SDU sent (e.g., transmitted) in Msg 31313, the UE may determine that the contention resolution is successful and / or the UE may determine that the random access procedure is successfully completed.
[0180] The UE may be configured with a supplementary uplink (SUL) carrier and a normal uplink (NUL) carrier. An initial access (e.g., random access procedure) may be supported in an uplink carrier. For example, a base station may configure the UE with two separate RACH configurations: one for an SUL carrier and the other for an NUL carrier. ForDocket No. 25-1081 PCTrandom access in a cell configured with an SUL carrier, the network may indicate which carrier to use (NUL or SUL). The UE may determine the SUL carrier, for example, if a measured quality of one or more reference signals is lower than a broadcast threshold. Uplink transmissions of the random access procedure (e.g., the Msg 1 1311 and / or the Msg 31313) may remain on the selected carrier. The UE may switch an uplink carrier during the random access procedure (e.g., between the Msg 1 1311 and the Msg 3 1313) in one or more cases. For example, the UE may determine and / or switch an uplink carrier for the Msg 1 1311 and / or the Msg 31313 based on a channel clear assessment (e.g., a listen-before-talk).
[0181] FIG. 13B illustrates a two-step contention-free random access procedure. Similar to the four-step contentionbased random access procedure illustrated in FIG. 13A, a base station may, prior to initiation of the procedure, transmit a configuration message 1320 to the UE. The configuration message 1320 may be analogous in some respects to the configuration message 1310. The procedure illustrated in FIG. 13B comprises transmission of two messages: a Msg 1 1321 and a Msg 21322. The Msg 1 1321 and the Msg 21322 may be analogous in some respects to the Msg 1 1311 and a Msg 2 1312 illustrated in FIG. 13A, respectively. As will be understood from FIGS. 13A and 13B, the contention-free random access procedure may not include messages analogous to the Msg 31313 and / or the Msg 41314.
[0182] The contention-free random access procedure illustrated in FIG. 13B may be initiated for a beam failure recovery, other SI request, SCell addition, and / or handover. For example, a base station may indicate or assign to the UE the preamble to be used for the Msg 1 1321. The UE may receive, from the base station via PDCCH and / or RRC, an indication of a preamble (e.g., ra-Preamblelndex).
[0183] After transmitting a preamble, the UE may start a time window (e.g., ra-ResponseWindow) to monitor a PDCCH for the RAR. In the event of a beam failure recovery request, the base station may configure the UE with a separate time window and / or a separate PDCCH in a search space indicated by an RRC message (e.g., recoverySearchSpaceld). The UE may monitor for a PDCCH transmission addressed to a Cell RNTI (C-RNTI) on the search space. In the contention-free random access procedure illustrated in FIG. 13B, the UE may determine that a random access procedure successfully completes after or in response to transmission of Msg 1 1321 and reception of a corresponding Msg 21322. The UE may determine that a random access procedure successfully completes, for example, if a PDCCH transmission is addressed to a C-RNTI. The UE may determine that a random access procedure successfully completes, for example, if the UE receives an RAR comprising a preamble identifier corresponding to a preamble transmitted by the UE and / or the RAR comprises a MAC sub-PDU with the preamble identifier. The UE may determine the response as an indication of an acknowledgement for an SI request.
[0184] FIG. 13C illustrates another two-step random access procedure. Similar to the random access procedures illustrated in FIGS. 13Aand 13B, a base station may, prior to initiation of the procedure, transmit a configuration message 1330 to the UE. The configuration message 1330 maybe analogous in some respects to the configuration message 1310 and / or the configuration message 1320. The procedure illustrated in FIG. 13C comprises transmission of two messages: a Msg A 1331 and a Msg B 1332.Docket No. 25-1081 PCT
[0185] Msg A 1331 may be transmitted in an uplink transmission by the UE. Msg A 1331 may comprise one or more transmissions of a preamble 1341 and / or one or more transmissions of a transport block 1342. The transport block 1342 may comprise contents that are similar and / or equivalent to the contents of the Msg 31313 illustrated in FIG. 13A. The transport block 1342 may comprise UCI (e.g., an SR, a HARQ ACK / NACK, and / or the like). The UE may receive the Msg B 1332 after or in response to transmitting the Msg A 1331. The Msg B 1332 may comprise contents that are similar and / or equivalent to the contents of the Msg 2 1312 (e.g., an RAR) illustrated in FIGS. 13Aand 13B and / or the Msg 41314 illustrated in FIG. 13A.
[0186] The UE may initiate the two-step random access procedure in FIG. 13C for licensed spectrum and / or unlicensed spectrum. The UE may determine, based on one or more factors, whether to initiate the two-step random access procedure. The one or more factors may be: a radio access technology in use (e.g., LTE, NR, and / or the like); whether the UE has valid TA or not; a cell size; the UE’s RRC state; a type of spectrum (e.g., licensed vs. unlicensed); and / or any other suitable factors.
[0187] The UE may determine, based on two-step RACH parameters included in the configuration message 1330, a radio resource and / or an uplink transmit power for the preamble 1341 and / or the transport block 1342 included in the Msg A 1331. The RACH parameters may indicate a modulation and coding schemes (MCS), a time-frequency resource, and / or a power control for the preamble 1341 and / or the transport block 1342. A time-frequency resource for transmission of the preamble 1341 (e.g., a PRACH) and a time-frequency resource for transmission of the transport block 1342 (e.g., a PUSCH) maybe multiplexed using FDM, TDM, and / or CDM. The RACH parameters may enable the UE to determine a reception timing and a downlink channel for monitoring for and / or receiving Msg B 1332.
[0188] The transport block 1342 may comprise 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 the Msg B 1332 as a response to the Msg A 1331. The Msg B 1332 may comprise at least one of following: a preamble identifier; a timing advance command; a power control command; an uplink grant (e.g., a radio resource assignment and / or an 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: a preamble identifier in the Msg B 1332 is matched to a preamble transmitted by the UE; and / or the identifier of the UE in Msg B 1332 is matched to the identifier of the UE in the Msg A 1331 (e.g., the transport block 1342).
[0189] A UE and a 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 comprise downlink control signaling transmitted from the base station to the UE and / or uplink control signaling transmitted from the UE to the base station.
[0190] The downlink control signaling may comprise: a downlink scheduling assignment; an uplink scheduling grant indicating uplink radio resources and / or a transport format; a slot format information; a preemption indication; a power control command; and / or any other suitable signaling. The UE may receive the downlink control signaling in a payload transmitted by the base station on a physical downlink control channel (PDCCH). The payload transmitted on theDocket No.25-1081 PCTPDCCH may be referred to as downlink control information (DC I). In some scenarios, the PDCCH may be a group common PDCCH (GC-PDCCH) that is common to a group of UEs.
[0191] A base station may attach one or more cyclic redundancy check (CRC) parity bits to a DCI in order to facilitate detection of transmission errors. When the DCI is intended for a UE (or a group of the UEs), the base station may scramble the CRC parity bits with an identifier of the UE (or an identifier of the group of the UEs). Scrambling the CRC parity bits with the identifier may comprise Modulo-2 addition (or an exclusive OR operation) of the identifier value and the CRC parity bits. The identifier may comprise a 16-bit value of a radio network temporary identifier (RNTI).
[0192] DCIs may be used for different purposes. A purpose may be indicated by the type of RNTI used to scramble the CRC parity bits. For example, a DCI having CRC parity bits scrambled with a paging RNTI (P-RNTI) may indicate paging information and / or a system information change notification. The P-RNTI may be predefined as " FFFE" in hexadecimal. A DCI having CRC parity bits scrambled with a system information RNTI (SI-RNTI) may indicate a broadcast transmission of the system information. The SI-RNTI may be predefined as “FFFF” in hexadecimal. A DCI having CRC parity bits scrambled with a random access RNTI (RA-RNTI) may indicate a random access response (RAR). A DCI having CRC parity bits scrambled with a cell RNTI (C-RNTI) may indicate a dynamically scheduled unicast transmission and / or a triggering of PDCCH-ordered random access. A DCI having CRC parity bits scrambled with a temporary cell RNTI (TC-RNTI) may indicate a contention resolution (e.g., a Msg 3 analogous to the Msg 31313 illustrated in FIG. 13A). Other RNTIs configured to the UE by a base station may comprise a Configured Scheduling RNTI (CS-RNTI), a Transmit Power Control-PUCCH RNTI (TPC-PUCCH-RNTI), a Transmit Power Control-PUSCH RNTI (TPC-PUSCH-RNTI), a Transmit 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), and / or the like.
[0193] Depending on the purpose and / or content of a DCI, the base station may transmit the DCIs 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 compact DCI payloads). DCI format 0_1 may be used for scheduling of PUSCH in a cell (e.g., with more DCI payloads 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 compact DCI payloads). DCI format 1 J may be used for scheduling of PDSCH in a cell (e.g., with more DCI payloads than DCI format 1_0). DCI format 2_0 may be used for providing a slot format indication to a group of UEs. DCI format 2 J may be used for notifying a group of UEs of a physical resource block and / or OFDM symbol where the UE may assume no transmission is intended to the UE. DCI format 2_2 may be used for transmission of a transmit power control (TPC) command for PUCCH or PUSCH. DCI format 2_3 may be used for transmission of a group of TPC commands for SRS transmissions by one or more UEs. DCI format(s) for new functions may be defined in future releases. DCI formats may have different DCI sizes, or may share the same DCI size.
[0194] After scrambling a DCI with a RNTI, the base station may process the DCI with channel coding (e.g., polar coding), rate matching, scrambling and / or QPSK modulation. A base station may map the coded and modulated DCI onDocket No.25-1081 PCTresource elements used and / or configured for a PDCCH. Based on a payload size of the DCI and / or a coverage of the base station, the base station may transmit the DCI via a PDCCH occupying a number of contiguous control channel elements (CCEs). The number of the contiguous CCEs (referred to as aggregation level) may be 1, 2, 4, 8, 16, and / or any other suitable number. A CCE may comprise a number (e.g., 6) of resource-element groups (REGs). A REG may comprise a resource block in an OFDM symbol. The mapping of the coded and modulated DCI on the resource elements may be based on mapping of CCEs and REGs (e.g., CCE-to-REG mapping).
[0195] FIG. 14A illustrates an example of CORESET configurations for a bandwidth part. The base station may transmit a DCI via a PDCCH on one or more control resource sets (CORESETs). A CORESET may comprise a timefrequency resource in which the UE tries to decode a DCI using one or more search spaces. The base station may configure a CORESET in the time-frequency domain. In the example of FIG. 14A, a first CORESET 1401 and a second CORESET 1402 occur at the first symbol in a slot. The first CORESET 1401 overlaps with the second CORESET 1402 in the frequency domain. A third CORESET 1403 occurs ata third symbol in the slot. A fourth CORESET 1404 occurs at the seventh symbol in the slot. CORESETs may have a different number of resource blocks in frequency domain.
[0196] FIG. 14B illustrates an example of a CCE-to-REG mapping for DCI transmission on a CORESET and PDCCH processing. The CCE-to-REG mapping may be an interleaved mapping (e.g., for the purpose of providing frequency diversity) or a non-interleaved mapping (e.g., for the purposes of facilitating interference coordination and / or frequency-selective transmission of control channels). The base station may perform different or same CCE-to-REG mapping on different CORESETs. A CORESET maybe associated with a CCE-to-REG mapping by RRC configuration. A CORESET may be configured with an antenna port quasi co-location (QCL) parameter. The antenna port QCL parameter may indicate QCL information of a demodulation reference signal (DMRS) for PDCCH reception in the CORESET.
[0197] The base station may transmit, to the UE, RRC messages comprising configuration parameters of one or more CORESETs and one or more search space sets. The configuration parameters may indicate an association between a search space set and a CORESET. A search space set may comprise a set of PDCCH candidates formed by CCEs ata given aggregation level. The configuration parameters may indicate: a number of PDCCH candidates to be monitored per aggregation level; a PDCCH monitoring periodicity and a PDCCH monitoring pattern; one or more DCI formats to be monitored by the UE; and / or whether a search space set is a common search space set or a UE-specific search space set. A set of CCEs in the common search space set may be predefined and known to the UE. A set of CCEs in the UE-specific search space set may be configured based on the UE’s identity (e.g., C-RNTI).
[0198] As shown in FIG. 14B, the UE may determine a time-frequency resource fora CORESET based on RRC messages. The UE may determine a CCE-to-REG mapping (e.g., interleaved or non-interleaved, and / or mapping parameters) for the CORESET based on configuration parameters of the CORESET. The UE may determine a number (e.g., at most 10) of search space sets configured on the CORESET based on the RRC messages. The UE may monitor a set of PDCCH candidates according to configuration parameters of a 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 compriseDocket No.25-1081 PCTdecoding one or more PDCCH candidates of the set of the PDCCH candidates according to the monitored DCI formats. Monitoring may comprise decoding a DCI content of one or more PDCCH candidates with possible (or configured) PDCCH locations, possible (or configured) PDCCH formats (e.g., number of CCEs, number of PDCCH candidates in common search spaces, and / or number of PDCCH candidates in the UE-specific search spaces) and possible (or configured) DCI formats. The decoding may be referred to as blind decoding. The UE may determine a DCI as valid for the UE, in response to CRC checking (e.g., scrambled bits for CRC parity bits of the DCI matching a RNTI value). The UE may process information contained in the DCI (e.g., a scheduling assignment, an uplink grant, power control, a slot format indication, a downlink preemption, and / or the like)
[0199] The UE may transmit uplink control signaling (e.g., uplink control information (UCI)) to a base station. The uplink control signaling may comprise hybrid automatic repeat request (HARQ) acknowledgements for received DL-SCH transport blocks. The UE may transmit the HARQ acknowledgements after receiving a DL-SCH transport block. Uplink control signaling may comprise channel state information (CSI) indicating channel quality of a physical downlink channel. The UE may transmit the CSI to the base station. The base station, based on the received CSI, may determine transmission format parameters (e.g., comprising multi-antenna and beamforming schemes) for a downlink transmission. Uplink control signaling may comprise scheduling requests (SR). The UE may transmit an SR indicating that uplink data is available for transmission to the base station. The UE may transmit a UCI (e.g., HARQ acknowledgements (HARQ-ACK), CSI report, SR, and the like) via a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH). The UE may transmit the uplink control signaling via a PUCCH using one of several PUCCH formats.
[0200] There may be five PUCCH formats and the UE may determine a PUCCH format based on a size of the UCI (e.g., a number of uplink symbols of UCI transmission and a number of UCI bits). PUCCH format 0 may have a length of one or two OFDM symbols and may include two or fewer bits. The UE may transmit UCI in a PUCCH resource using PUCCH format 0 if the transmission is over one or two symbols and the number of HARQ-ACK information bits with positive or negative SR (HARQ-ACK / SR bits) is one or two. PUCCH format 1 may occupy a number between four and fourteen OFDM symbols and may include two or fewer bits. The UE may use PUCCH format 1 if the transmission is four or more symbols and the number of HARQ-ACK / SR bits is one or two. PUCCH format 2 may occupy one or two OFDM symbols and may include more than two bits. The UE may use PUCCH format 2 if the transmission is over one or two symbols and the number of UCI bits is two or more. PUCCH format 3 may occupy a number between four and fourteen OFDM symbols and may include more than two bits. The UE may use PUCCH format 3 if the transmission is four or more symbols, the number of UCI bits is two or more and PUCCH resource does not include an orthogonal cover code. PUCCH format 4 may occupy a number between four and fourteen OFDM symbols and may include more than two bits. The UE may use PUCCH format 4 if the transmission is four or more symbols, the number of UCI bits is two or more and the PUCCH resource includes an orthogonal cover code.
[0201] The base station may transmit configuration parameters to the UE for a plurality of PUCCH resource sets using, for example, an RRC message The plurality of PUCCH resource sets (e.g., up to four sets) may be configuredDocket No. 25-1081 PCTon an uplink BWP of a cell. A PUCCH resource set may be configured with a PUCCH resource set index, a plurality of PUCCH resources with a PUCCH resource being identified by a PUCCH resource identifier (e.g., pucch-Resourceid), and / or a number (e.g., a maximum number) of UCI information bits the UE may transmit using one of the plurality of PUCCH resources in the PUCCH resource set. When configured with a plurality of PUCCH resource sets, the UE may select one of the plurality of PUCCH resource sets based on a total bit length of the UCI information bits (e.g., HARQ-ACK, SR, and / or CSI). If the total bit length of UCI information bits is two or fewer, the UE may select a first PUCCH resource set having a PUCCH resource set index equal to “0”. If the total bit length of UCI information bits is greater than two and less than or equal to a 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 UCI information bits is greater than the first configured value and less than or equal to a 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 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”.
[0202] After determining a PUCCH resource set from a plurality of PUCCH resource sets, the UE may determine a PUCCH resource from the PUCCH resource set for UCI (HARQ-ACK, CSI, and / or SR) transmission. The UE may determine the PUCCH resource based on a PUCCH resource indicator in a DCI (e.g., with a DCI format 1_0 or DCI format 1_1) received on a PDCCH. A three-bit PUCCH resource indicator in the DCI may indicate one of eight PUCCH resources in the PUCCH resource set. Based on the PUCCH resource indicator, the UE may transmit the UCI (HARQ-ACK, CSI and / or SR) using a PUCCH resource indicated by the PUCCH resource indicator in the DCI.
[0203] FIG. 15 illustrates an example of a wireless device 1502 in communication with a base station 1504 in accordance with embodiments of the present disclosure. The wireless device 1502 and base station 1504 may be part of a mobile communication network, such as the mobile communication network 100 illustrated in FIG. 1A, the mobile communication network 150 illustrated in FIG. 1B, or any other communication network. Only one wireless device 1502 and one base station 1504 are illustrated in FIG. 15, but it will be understood that a mobile communication network may include more than one UE and / or more than one base station, with the same or similar configuration as those shown in FIG. 15.
[0204] The base station 1504 may connect the wireless device 1502 to a core network (not shown) through radio communications over the air interface (or radio interface) 1506. The communication direction from the base station 1504 to the wireless device 1502 over the air interface 1506 is known as the downlink, and the communication direction from the wireless device 1502 to the base station 1504 over the air interface is known as the uplink. Downlink transmissions may be separated from uplink transmissions using FDD, TDD, and / or some combination of the two duplexing techniques.
[0205] In the downlink, data to be sent to the wireless device 1502 from the base station 1504 may be provided to the processing system 1508 of the base station 1504. The data may be provided to the processing system 1508 by, for example, a core network. In the uplink, data to be sent to the base station 1504 from the wireless device 1502 maybeDocket No.25-1081 PCTprovided to the processing system 1518 of the wireless device 1502. The processing system 1508 and the processing system 1518 may implement layer 3 and layer 2 OSI functionality to process the data for transmission. Layer 2 may include an SDAP layer, a PDCP layer, an RLC layer, and a MAC layer, for example, with respect to FIG.2A, FIG. 2B, FIG. 3, and FIG.4A. Layer 3 may include an RRC layer as with respect to FIG. 2B.
[0206] After being processed by processing system 1508, the data to be sent to the wireless device 1502 may be provided to a transmission processing system 1510 of base station 1504. Similarly, after being processed by the processing system 1518, the data to be sent to base station 1504 may be provided to a transmission processing system 1520 of the wireless device 1502. The transmission processing system 1510 and the transmission processing system 1520 may implement layer 1 OSI functionality. Layer 1 may include a PHY layer with respect to FIG. 2A, FIG.2B, FIG.3, and FIG. 4A. For transmit 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 channel, multiple-input multiple-output (Ml MO) or multi-antenna processing, and / or the like.
[0207] At the base station 1504, a reception processing system 1512 may receive the uplink transmission from the wireless device 1502. At the wireless device 1502, a reception processing system 1522 may receive the downlink transmission from base station 1504. The reception processing system 1512 and the reception processing system 1522 may implement layer 1 OSI functionality. Layer 1 may include a PHY layer with respect to FIG.2A, FIG. 2B, FIG. 3, and FIG. 4A. For receive 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, and / or the like.
[0208] As shown in FIG. 15, a 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.
[0209] The processing system 1508 and the processing system 1518 may be associated with a memory 1514 and a memory 1524, respectively. Memory 1514 and memory 1524 (e.g., one or more non-transitory computer readable mediums) may store computer program instructions or code that may be executed by the processing system 1508 and / or the processing system 1518 to carry out one or more of the functionalities discussed in the present application. Although not shown in FIG. 15, the transmission processing system 1510, the transmission processing system 1520, the reception processing system 1512, and / or the reception processing system 1522 may be coupled to a memory (e.g., one or more non-transitory computer readable mediums) storing computer program instructions or code that may be executed to carry out one or more of their respective functionalities.
[0210] The processing system 1508 and / or the processing system 1518 may comprise one or more controllers and / or one or more processors. The one or more controllers and / or one or more processors may comprise, 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 / orDocket No.25-1081 PCTtransistor logic, discrete hardware components, an on-board unit, or any combination thereof. The processing system 1508 and / or the processing system 1518 may perform at least one of signal coding / processing, data processing, power control, input / output processing, and / or any other functionality that may enable the wireless device 1502 and the base station 1504 to operate in a wireless environment.
[0211] The processing system 1508 and / or the processing system 1518 may be connected to one or more peripherals 1516 and one or more peripherals 1526, respectively. The one or more peripherals 1516 and the one or more peripherals 1526 may include software and / or hardware that provide features and / or functionalities, for example, a speaker, a microphone, a keypad, a display, a touchpad, a power source, a satellite transceiver, a universal serial bus (USB) port, a hands-free headset, a frequency modulated (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, and / or the like). The processing system 1508 and / or the processing system 1518 may receive user input data from and / or provide user output data to the one or more peripherals 1516 and / or the one or more peripherals 1526. The processing system 1518 in the wireless device 1502 may receive power from a power source and / or may be configured to distribute the power to the other components in the wireless device 1502. The power source may comprise one or more sources of power, for example, a battery, a solar cell, a fuel cell, or any combination thereof. The processing system 1508 and / or the processing system 1518 may be connected to a GPS chipset 1517 and a GPS chipset 1527, respectively. The GPS chipset 1517 and the GPS chipset 1527 may be configured to provide geographic location information of the wireless device 1502 and the base station 1504, respectively.
[0212] FIG. 16A illustrates an example structure for uplink transmission. A baseband signal representing a physical uplink shared channel may perform one or more functions. The one or more functions may comprise at least one of: scrambling; modulation of scrambled bits to generate complex-valued symbols; mapping of the complex-valued modulation symbols onto one or several transmission layers; transform precoding to generate complex-valued symbols; precoding of the complex-valued symbols; mapping of precoded complex-valued symbols to resource elements; generation of complex-valued time-domain Single Carrier-Frequency Division Multiple Access (SC-FDMA) or CP-OFDM signal for an antenna port; and / or the like. In an example, when transform precoding is enabled, a SC-FDMA signal for uplink transmission may be generated. In an example, when transform precoding is not enabled, a CP-OFDM signal for uplink transmission may be generated by FIG. 16A. These functions are illustrated as examples and it is anticipated that other mechanisms may be implemented in various embodiments.
[0213] FIG. 16B illustrates an example structure for modulation and up-conversion of a baseband signal to a carrier frequency. The baseband signal may be a complex-valued SC-FDMA or CP-OFDM baseband signal for an antenna port and / or a complex-valued Physical Random Access Channel (PRACH) baseband signal. Filtering may be employed prior to transmission.
[0214] FIG. 16C illustrates an example structure for downlink transmissions. A baseband signal representing a physical downlink channel may perform one or more functions. The one or more functions may comprise: scrambling ofDocket No.25-1081 PCTcoded bits in a codeword to be transmitted on a physical channel; modulation of scrambled bits to generate complexvalued modulation symbols; mapping of the complex-valued modulation symbols onto one or several transmission layers; precoding of the complex-valued modulation symbols on a layer for transmission on the antenna ports; mapping of complex-valued modulation symbols for an antenna port to resource elements; generation of complex-valued timedomain OFDM signal for an antenna port; and / or the like. These functions are illustrated as examples and it is anticipated that other mechanisms may be implemented in various embodiments.
[0215] FIG. 16D illustrates another example structure for modulation and up-conversion of a baseband signal to a carrier frequency. The baseband signal may be a complex-valued OFDM baseband signal for an antenna port. Filtering may be employed prior to transmission.
[0216] A wireless device may receive from a base station one or more messages (e.g., RRC messages) comprising configuration parameters of a plurality of cells (e.g., primary cell, secondary cell). The wireless device may communicate with at least one base station (e.g., two or more base stations in dual connectivity) via the plurality of cells. The one or more messages (e.g., as a part of the configuration parameters) may comprise parameters of physical, MAC, RLC, PCDP, SDAP, RRC layers for configuring the wireless device. For example, the configuration parameters may comprise parameters for configuring physical and MAC layer channels, bearers, etc. For example, the configuration parameters may comprise parameters indicating values of timers for physical, MAC, RLC, PCDP, SDAP, RRC layers, and / or communication channels
[0217] A timer may begin running once it is started and continue running until it is stopped or until it expires. A timer may be started if it is not running or restarted if it is running. A timer may be associated with a value (e.g., the timer may be started or restarted from a value or may be started from zero and expire once it reaches the value). The duration of a timer may not be updated until the timer is stopped or expires (e.g., due to BWP switching). A timer may be used to measure a time period / window for a process. When the specification refers to an implementation and procedure related to one or more timers, it will be understood that there are multiple ways to implement the one or more timers. For example, it will be understood that one or more of the multiple ways to implement a timer may be used to measure a time period / window for the procedure. For example, a random access response window timer may be used for measuring a window of time for receiving a random access response. In an example, instead of starting and expiry (or expiration) of a random access response window timer, the time difference between two time stamps may be used. When a timer is restarted, a process for measurement of time window may be restarted. Other example implementations may be provided to restart a measurement of a time window.
[0218] In an example, a wireless device may be configured with a list of TCI states (e.g., TCI-State) within / by a higher layer parameter PDSCH-Config to decode PDSCH according to a detected PDCCH with DCI intended for the wireless device and a given cell (e.g., a given serving cell, a given non-serving / candidate / target cell). A subset of the list of TCI states (e.g., tci-StatesPDCCH-ToAddList) may be configured for monitoring PDCCHs via the given cell. The wireless device may determine QCL relationship between one or more RS(s) on a TCI state associated with aDocket No.25-1081 PCTCORESET and DM-RS port(s) of a PDCCH via the CORESET. The base station may configure up to maxNrofTCI-StatesPDCCH for the tci-StatesPDCCH-ToAddList.
[0219] A number of TCI states in the list may depend on a UE capability parameter maxNumberConfiguredTCIstatesPerCC. Each TCI state (e.g., TCI-State) may contain / comprise / include / indicate / have respective parameters for configuring a quasi co-location relationship / assumption / information between one or two downlink reference signals and DM-RS port(s) of a PDSCH, a DM-RS port of a PDCCH, or CSI-RS port(s) of a CSI-RS resource.
[0220] The quasi co-location (QCL) relationship may be configured by a higher layer parameter qcl-Type1 for a first downlink reference signal of the one or more downlink reference signals. The quasi co-location relationship may be, optionally, configured by a higher layer parameter qcl-Type2 for a second downlink reference signal of the one or more downlink reference signals. When two downlink reference signals comprising a first downlink reference signal and a second downlink reference signal are indicated by a TCI state, QCL types of the two downlink reference signals may not be the same, regardless of whether the first downlink reference signal and the second downlink reference signal are the same or different. A quasi co-location type corresponding to a downlink reference signal of the one or more downlink reference signals may be given by a higher layer parameter qcl-Type in a higher layer parameter QCL-Info and may take one of the following values: 'typeA': {Doppler shift, Doppler spread, average delay, delay spread}, 'typeB': {Doppler shift, Doppler spread}, 'typeC: {Doppler shift, average delay}, or 'typeD': {Spatial Rx parameter}.
[0221] A TCI state may be configured via information element of TCI-State. One or more configuration parameters of a TCI state may be referred as a TCI state configuration, a TCI state ora TCI in the specification.
[0222] A wireless device may be configured with a list of TCI states (e.g., up to 128 TCI-State configurations) within / by a higher layer parameter dl-OrJointTCI-StateList in PDSCH-Config. A PDSCH-Config may be configured for each / a bandwidth part of a cell. A TCI state in the list of TCI states may provide / indicate a reference signal for a quasi co-location for i) DM-RS of a PDSCH, ii) DM-RS of a PDCCH in a BWP / cell, and / or iii) a CSI-RS. A TCI state in the list of TCI states may provide / indicate one or more reference signals for determining uplink transmission spatial filter for i) a dynamic-grant PUSCH, ii) a configured-grant based PUSCH, iii) a PUCCH resource in a BWP / cell, and / or, iv) an SRS.
[0223] The TCI state may comprise an index of the TCI state (e.g., tci-State / d) and parameter(s) to indicate a first reference signal for determining QCL with a first QCL type (e.g., qcl-TypeT). Additionally, the TCI state may comprise parameter(s) to indicate a second reference signal for determining QCL with a second QCL type (e.g., qcl-Type2), where the second QCL type is different from the first QCL type. The TCI state may indicate an additional PCI (e.g., additionalPCI). The additional PCI may indicate a physical cell index (PCI) of SSB(s) when the first reference signal of the qcl-Type 1 and the second signal of the qcl-Type2 are SSB(s). In such a case, if the additional PCI is present in the TCI state, this may refer to a PCI value configured in a list of additional PCI (e.g., PCI-ToAddModList) in serving cell configurations of a second cell. The wireless device may determine the second cell from the qcl-Type 1 and / or the qcl-Type2 configurations. If qcl-Type 1 and / or qcl-Type2 do not have parameter(s) of the second cell, the wireless device may determine the list of additional PCI from serving cell configurations of the cell (e.g., the serving cell).Docket No. 25-1081 PCT
[0224] The TCI state may comprise an index of a pathloss reference signal (PL-RS) (e.g., pathlossReferenceSignal-Id). The index of the PL-RS indicates a reference signal (one of a CSI-RS or an SSB) that would be used for determining pathloss for uplink transmissions (e.g., PUSCH, PUCCH and SRS). This field may refer to an element in a list of pathloss-ReferenceRSToAddModList of an active UL BWP of the cell. The TCI state may comprise parameter(s) of uplink power control (e.g., ul-PowerControl). The parameter(s) of uplink power control may configure power control parameters for the uplink transmissions (PUCCH, PUSCH, and SRS) for the TCI state. The TCI state may comprise a tag id pointer (e.g., tag-ld-ptr). The tag id pointer may indicate a TAG that is associated with the TCI state. A first value (eg., nO) may indicate a first TAG with a tag-id parameter. A second value (e.g., n 1 ) may indicate a second TAG with a tag-id2 parameter.
[0225] In the specification, a QCL-info maybe referred as one or more QCL parameters, QCL information, QCL parameters, QCL relations, QCL property, QCL, QCL assumption, QCL relationship, and / or the like.
[0226] The one or more QCL parameters (e.g., QCL-info) may comprise a cell index of a second cell (e.g., a cell). The second cell may transmit a reference signal for the qcl-Type 1 or the qcl-Type2. In an example, if the cell index of the second cell is not present in the one or more QCL parameters, the wireless device may use a cell index of the cell (i.e., the serving cell where the TCI state is applied). The one or more QCL parameters may comprise an index of a bandwidth part. The index of the bandwidth part may indicate the bandwidth part of the second cell (if the cell is present) or the cell (i.e., the serving cell).
[0227] The one or more QCL parameters may indicate the reference signal for the qcl-Type1 or the qcl-Type2. The reference signal may be one of a CSI-RS or an SSB. The one or more QCL parameters may comprise an index to the CSI or the SSB. The one or more QCL parameters may indicate a QCL type using the reference signal. The QCL type may indicate one of {'typeA', ‘typeB’, ‘typeC, ‘typeD’}.
[0228] In an example, the PL-RS of the TCI may comprise an index of a SSB or a CSI-RS that is used for pathloss computation. Configuration parameters of the PL-RS may comprise a cell index of a third cell (e.g., additiona / PCI) that is an index of the third cell transmitting the PL-RS.
[0229] A wireless device may receive an activation command (e.g., MAC-CE, DCI) used to map up to a number TCI states and / or pairs of TCI states (e.g., up to 8 TCI states and / or pairs of TCI states), with one TCI state for downlink channels / signals and / or one TCI state for uplink channels / signals, to codepoint(s) of a DCI field 'Transmission Configuration Indication' for one cell or for a set of cells / downlink BWPs, and / or up to a number of sets of TCI states (e.g., up to 8 sets of TCI states). Each set of the number of sets may be comprised of up to a number of TCI state(s) for downlink and uplink signals / channels (e.g., up to two TCI state(s)), or up to a number of TCI state(s) (e.g., up to two TCI state(s)) for downlink channels / signals and up to a number of TCI state(s) (e.g., up to two TCI state(s)) for uplink channels / signals to codepoint(s) of a DCI field 'Transmission Configuration Indication' for one cell or for a set of cells / downlink BWPs, and if applicable, for one cell or for a set of cells / uplink BWPs. When a set of TCI state IDs are activated, by the activation command, for a set of cells / downlink BWPs and if applicable, for a set of cells / uplink BWPs, where the applicable list of cells may be determined, by the wireless device, by an indicated cell in the activationDocket No.25-1081 PCTcommand, the (same) set of TCI state IDs may be applied by the wireless device to / for all downlink and / or uplink BWPs in the indicated cells (or the applicable list of cells). If the activation command maps TCI-State(s) and / or TCI-UL-State(s) to only one (or to a single) TCI codepoint, the wireless device may apply the (indicated) TCI-State(s) and / or TCI-UL-State(s) to one cell or to a set of cells / downlink BWPs, and if applicable, to one cell or to a set of cells / uplink BWPs once the indicated mapping for the one single TCI codepoint is applied by the wireless device.
[0230] When a wireless device configured with dl-OrJointTCI-StateList by one or more configuration parameters (e.g., RRC messages / parameters) transmits an uplink transmission (e.g., a PUCCH transmission, a PUSCH transmission) with a positive HARQ-ACK corresponding to the DCI format indicating the indicated TCI state(s) (e.g., TCI-State(s) and / or TCI-UL-State(s)), and if the indicated TCI State(s) is / are different from the previously indicated TCI state(s), the indicated TCI-State(s) may be applied, by the wireless device, starting from a first / starting / earliest slot that is at least a number of symbols (e.g., symbols) after the last symbol of the uplink transmission. The first / starting / earliest slot and the number of symbols may be both determined, by the wireless device, based on an active BWP with the smallest subcarrier spacing among BWP(s) of the cells applying the indicated TCI-State(s) that are active at the end of the uplink transmission carrying / with the positive HARQ-ACK. The number of symbols may be indicated / provided to the wireless device by RRC messages (e.g., one or more configuration parameters).
[0231] When a wireless device supports two TCI states in a codepoint of a DCI field 'Transmission Configuration Indication', the wireless device may receive an activation command (e.g., MAC-CE, DCI) used to map up to 8 combinations of one or two TCI states to codepoint(s) of the DCI field 'Transmission Configuration Indication'. The wireless device may not expect to receive more than 8 TCI states in the activation command.
[0232] In an example, if the TCI-State or TCI-UL-State configurations are absent in a BWP of the CC, the wireless device may apply the TCI-State or TCI-UL-State configurations from a reference BWP of a reference CC configured by unifiedTCI-StateRef
[0233] When the bwp-id or cell for QCL-TypeA / D source RS in a QCL-Info of the TCI state is not configured, the wireless device may assume that QCL-TypeA / D source RS is configured in the CC / DL BWP where TCI state applies.
[0234] When tci-PresentlnDCI is set as 'enabled' or tci-PresentDCI-1-2 is configured for the CORESET, a wireless device that is configured with dl-OrJointTCI-State List with activated TCI-State or u / -TC / -StateList with activated TCI-UL-State receives DCI format 1_1 / 1_2 / 1_3 providing indicated TCI-State(s) and / or TCI-UL-State(s) for a CC or all CCs in the same CC list configured by simultaneousU-TCI-UpdateList1-r17, simultaneousU-TCI-UpdateList2-r17, simultaneousU-TCI-UpdateList3-r17, simultaneousU-TCI-UpdateList4-r17. The DCI format 1_1 / 1 _2 may be with or without, if applicable, DL assignment (e.g., the DCI format 1_1 / 1_2 may schedule a PDSCH or may not schedule a PDSCH). If the DCI format 1_1 / 1_2 / is without DL assignment (e.g., the DCI format 1_1 / 1_2 may not schedule a PDSCH), the wireless device may asusme the following for the DCI format 1_1 / 1_2.
[0235] A) CS-RNTI is used to scramble the CRC for the DCI
[0236] B) The value of a DCI field of redundancy version (RV) set to all ‘1’s; the value of a DCI field of modulation and coding scheme (MCS) set to all ‘Ts; and a DCI field of a new data indicator (NDI) set to 0.Docket No.25-1081 PCT
[0237] C) A DCI field of a frequency domain resource allocation (FDRA) with a resource allocation type 0 set to all ‘0’s, or the FDRA with a resource allocation type 1 set to all ‘Ts, or the FDRA with a dynamicSwitch set to all ‘0’s.
[0238] After a wireless device receives an initial higher layer configuration of dl-OrJointTCI-StateList with more than one TCI-State and before application of an indicated TCI state from the configured TCI states, the wireless device may assume that DM-RS of PDSCH and DM-RS of PDCCH and the CSI-RS applying the indicated TCI state are quasi colocated with the SS / PBCH block the wireless device identified during the initial access procedure.
[0239] After a wireless device receives an initial higher layer configuration of dl-OrJointTCI-StateList with more than one TCI-State or ul-TCI-StaieList with more than one TCI-UL-State and before application of an indicated TCI state from the configured TCI states, the wireless device may assume that the UL TX spatial filter, if applicable, for dynamicgrant and configured-grant based PUSCH and PUCCH, and for SRS applying the indicated TCI state, is the same as that for a PUSCH transmission scheduled by a RAR UL grant or a MsgA PUSCH transmission during the initial access procedure
[0240] After a UE receives a higher layer configuration of dl-OrJointTCI-StateList with more than one TCI-State as part of a Reconfiguration with sync procedure (e.g., a handover procedure) and before applying an indicated TCI state from the configured TCI states, the wireless device may assume that DM-RS of PDSCH and DM-RS of PDCCH, and the CSI-RS applying the indicated TCI state are quasi co-located with the SS / PBCH block or the CSI-RS resource the wireless device identified during the random access procedure initiated by the Reconfiguration with sync procedure.
[0241] Aftera wireless device receives a higher layer configuration of dl-OrJointTCI-StateList with more than one TCI-State or more than one TCI-UL-State as part of a Reconfiguration with sync procedure (e.g., a handover procedure) and before applying an indicated TCI state from the configured TCI states, the wireless device may assume that the UL TX spatial filter, if applicable, for dynamic-grant and configured-grant based PUSCH and PUCCH, and for SRS applying the indicated TCI state, is the same as that for a PUSCH transmission scheduled by a RAR UL grant ora MsgA PUSCH transmission during random access procedure initiated by the Reconfiguration with sync procedure.
[0242] If a wireless device receives a higher layer configuration of dl-OrJointTCI-StateList with a single TCI-State, that may be used as an indicated TCI state, the wireless device may obtain the QCL assumptions from the configured TCI state for DM-RS of PDSCH and DM-RS of PDCCH, and the CSI -RS applying the indicated TCI state.
[0243] If a wireless device receives a higher layer configuration of dl-OrJointTCI-StateList with a single TCI-State or ul-TCI-StateList with a single TCI-UL-State, that may be used as an indicated TCI state, the wireless device may determine an UL TX spatial filter, if applicable, from the configured TCI state for dynamic-grant and configured-grant based PUSCH and PUCCH, and SRS applying the indicated TCI state.
[0244] When a wireless device that is configured with dl-OrJointTCI-StateList would transmit a PUCCH with positive HARQ-ACK or a PUSCH with positive HARQ-ACK corresponding to the DCI carrying the TCI State indication and without DL assignment, or corresponding to the PDSCH scheduled by the DCI carrying the TCI State indication, and if the indicated TCI State(s) is / are different from the previously indicated one(s), the indicated TCI-State(s) and / or TCI-UL-State(s) may be applied starting from the first slot that is at least beamAppT ime symbols after the last symbol ofDocket No.25-1081 PCTthe PUCCH or the PUSCH. If the wireless device receives more than one indicated TCI state for a CC / BWP to be applied starting from the first slot that is at least beamAppT ime symbols after the last symbol of the PUCCH or the PUSCH, the indicated TCI state carried in the latest DCI in time corresponding to positive HARQ-ACK value is applied. The first slot and the beamAppT ime symbols are both determined on the active BWP with the smallest SCS among the BWP(s) from the CCs applying the indicated TCI-State(s) or TCI-UL-State(s) that are active at the end of the PUCCH or the PUSCH carrying the positive HARQ-ACK.
[0245] When a wireless device is configured with dl-OrJointTCI-StateList, and if the wireless device is configured with unifiedTCI-StateType is set as 'separate', and if the wireless device receives a TCI codepoint mapped with either of {TCI-State, TCI-UL-State}, the wireless device may update the one indicated {TCI-State, TCI-UL-State} and maintain the other {TCI-State, TCI-UL-State} that is not updated by the received TCI codepoint.
[0246] When a wireless device is configured with dl-OrJointTCI-StateList and is having two indicated TCI-states, if the wireless device receives a TCI codepoint mapped with a sub-set of first and second TCI-State(s) and / or a sub-set of first and second TCI-UL-State(s), the wireless device may update the first / second TCI-State(s) and / or first / second TCI-UL-State(s) mapped to the TCI codepoint, when applicable, and keep the previously indicated first / second TCI-State(s) and / or first / second TCI-UL-State(s) that is / are not updated by the TCI codepoint.
[0247] If a wireless device is configured with pdsch-TimeDomainAllocationListForMultiPDSCH in which one or more rows contain multiple SLIVs for PDSCH on a DL BWP of a serving cell, and the wireless device is receiving a DCI carrying the TCI-State indication and without DL assignment, the wireless device does not expect that the number of indicated SLIVs in the row of the pdsch-TimeDomainAllocationListForMultiPDSCH by the DCI is more than one.
[0248] When the DCI field 'Transmission Configuration Indication' is present in DCI format 1_2 and when the number of codepoints S in the DCI field 'Transmission Configuration Indication' of DCI format 1_2 is smaller than the number of TCI codepoints that are activated by the activation command, only the first S activated codepoints are applied for DCI format 1_2.
[0249] When the wireless device would transmit a PUCCH with HARQ-ACK information in slot n corresponding to the PDSCH carrying the activation command, the indicated mapping between TCI states and codepoints of the DCI field 'Transmission Configuration Indication' should be applied starting from the first slot that is after slot n + 3N^obtframe’'1+ g^gc. ■ fcmac where u is the SCS configuration for the PUCCH and pKmacis the subcarrier spacing configuration for kmacwith a value of 0 for frequency range 1, and kmacis provided by K-Mac or kmac= 0 if K-Mac is not provided. If tci-PresentlnDCI is set to 'enabled' or tci-PresentDCI-1 -2 is configured for the CORESET scheduling the PDSCH, and the time offset between the reception of the DL DCI and the corresponding PDSCH is equal to or greater than timeDurationForQCL if applicable, after a wireless device receives an initial higher layer configuration of TCI states and before reception of the activation command, the wireless device may assume that the DM-RS ports of PDSCH of a serving cell are quasi co-located with the SS / PBCH block determined in the initial access procedure with respect to qcl-Type set to 'typeA', and when applicable, also with respect to qcl-Type set to 'typeD'.Docket No.25-1081 PCT
[0250] If a wireless device is not provided dl-OrJointTCI-StateList-r17, and if a PDSCH is scheduled by a DCI format having the TCI field present, the TCI field in DCI in the scheduling component carrier points to the activated TCI states in the scheduled component carrier or DL BWP, the wireless device may use the TCI-State according to the value of the 'Transmission Configuration Indication' field in the detected PDCCH with DCI for determining PDSCH antenna port quasi co-location. The wireless device may assume that the DM-RS ports of PDSCH of a serving cell are quasi colocated with the RS(s) in the TCI state with respect to the QCL type parameter(s) given by the indicated TCI state if the time offset between the reception of the DL DCI and the corresponding PDSCH is equal to or greater than a threshold timeDurationForQCL, where the threshold is based on reported UE capability. For a single slot PDSCH, the indicated TCI state(s) may be based on the activated TCI states in the slot with the scheduled PDSCH. For a multi-slot PDSCH or the wireless device is configured with higher layer parameter pdsch-TimeDomainAllocationListForMultiPDSCH, the indicated TCI state(s) may be based on the activated TCI states in the first slot with the scheduled PDSCH(s), and wireless device may expect the activated TCI states are the same across the slots with the scheduled PDSCH(s). Independent of the configuration of tci-Presentl n DC I and tci-PresentDCI - 1 -2 in RRC connected mode, if the UE is not provided dl-OrJointTCI-StateList-r17, and if the offset between the reception of the DL DCI and the corresponding PDSCH is less than the threshold timeDurationForQCL and at least one configured TCI state for the serving cell of scheduled PDSCH contains qcl-Type set to 'typeD', the wireless device may assume that the DM-RS ports of PDSCH(s) of a serving cell are quasi co-located with the RS(s) with respect to the QCL parameter(s) used for PDCCH quasi co-location indication of the CORESET associated with a monitored search space with the lowest controlResourceSetld in the latest slot in which one or more CORESETs within the active BWP of the serving cell are monitored by the wireless device. In this case, if the qcl-Type is set to 'typeD' of the PDSCH DM-RS is different from that of the PDCCH DM-RS with which they overlap in at least one symbol, the wireless device is expected to prioritize the reception of PDCCH associated with that CORESET. This also applies to the intra-band CA case (when PDSCH and the CORESET are in different component carriers).
[0251] Wireless communication systems may encounter certain challenges, particularly when user equipment (UE) is configured to communicate via two cells configured with low band carrier aggregation (LB-CA), which involves dynamic switching between the two cells— e.g., a primary cell (PCell) and a secondary cell (SCell). In LB-CA, the UE transmits and / or receives data on the two cells during their respective time allocations. In such scenarios, the UE may receive downlink control information (DCI) indicating a new transmission configuration indicator (TCI) state for one cell. Upon receiving the DCI, the UE typically transmits a positive hybrid automatic repeat request acknowledgment (HARQ-ACK) to confirm receipt, and then applies the new TCI state after a predefined time duration from the HARQ-ACK transmission.
[0252] A conflict may arise if this predefined time duration for applying the new TCI state for one cell overlaps with a switching gap for transitioning between the two cells in LB-CA. Due to hardware constraints, the UE may be unable to perform the necessary switch during this period. Consequently, such an overlap may prevent the UE from properlyDocket No.25-1081 PCTapplying the new TCI state or performing the necessary switch for LB-CA, potentially leading to degraded performance or communication failures.
[0253] In order to solve this problem, according to an example of an embodiment of this disclosure, there is provided a method comprising receiving, by a wireless device, one or more configuration parameters indicating a value of beam application time (beamAppTime), indicating when the wireless device is to apply a transmission configuration indicator (TCI) state, for a first cell, indicated by downlink control information (DCI), and a low-band carrier aggregation (LB-CA) switching latency value indicating a latency for switching, for LB-CA, between the first cell and a second cell (e.g., the latency value indicates how long it takes for the wireless device to switch, for LB-CA, between the first cell and the second cell). The method further comprises receiving DCI indicating a TCI state for the first cell (e.g., the DCI carrying an indication of the TCI state). The TCI state is different from a current TCI state of the first cell. The method further comprises transmitting an uplink channel (e.g., PUCCH or PUSCH) with a positive feedback (e.g., positive HARQ-ACK) corresponding to the DCI (e.g., the positive feedback acknowledging the receipt of the DCI), and applying the indicated TCI state, starting from a slot which is after at least a sum, of the value of the BeamAppTime and the LB-CA switching latency value, from the last symbol of the uplink channel (e.g., if the value of the BeamAppTime is X msec / symbols and the LB-CA switching latency value is Y msec / symbols, the slot is at least after X + Y msec / symbols from the last symbol of the uplink channel. More specifically, the beginning of the slot is at a timing which is X+Y msec / symbols from the last symbol of the uplink channel).
[0254] In an example of the embodiment of this disclosure, there is provided a method comprising transmitting, by a wireless device, an uplink channel corresponding to downlink control information (DCI) indicating a transmission configuration information (TCI) state for a first cell. The TCI state is different from a current TCI state of the first cell. The method further comprises applying the indicated TCI state, based on a carrier aggregation (CA) switching latency value for switching, for CA, between the first cell and a second cell, or a fixed offset value (e.g., 2 symbols).
[0255] In an example of the embodiment of this disclosure, there is provided a method comprising receiving, by a wireless device, one or more configuration parameters indicating that a first cell is configured with a low-band carrier aggregation (LB-CA) switching. A switching pattern of the LB-CA switching indicates a first plurality of time slots allocated to the first cell, during which the wireless device is configured to communicate in the first cell and a second plurality of time slots allocated to a second cell, during which the wireless device is configured to communicate in the second cell. The configuration parameter(s) indicate beam application time (beamAppTime) symbols indicating when the wireless device is to apply a transmission configuration indicator (TCI) state, for the first cell, indicated by downlink control information (DCI). The method further comprises, based on whether the beamAppTime symbols overlap with a (or any) of the second plurality of time slots allocated to the second cell, either dropping data scheduled to be received or transmitted, during the beamAppTime symbols, in the second cell.
[0256] In an example of the embodiment of this disclosure, there is provided a method comprising receiving, by a wireless device, one or more configuration parameters indicating that a first cell is configured with a carrier aggregation (CA) (e.g., a low-band CA (" LB-CA”)) switching. A switching pattern of the LB-CA switching indicates a first plurality ofDocket No.25-1081 PCTtime slots allocated to the first cell and a second plurality of time slots allocated to a second cell. The method further comprises, based on whether beam application time (beamAppTime) symbols overlap with a (or any) of the second plurality of time slots allocated to the second cell, either: transmitting or receiving data scheduled in the second cell, during the beamAppTime symbols, or dropping data scheduled to be received or transmitted, during the beamAppTime symbols, in the second cell.
[0257] In an example of the embodiment of this disclosure, there is provided a method comprising receiving, by a wireless device, one or more configuration parameters indicating that a first cell is configured with a low-band carrier aggregation (LB-CA) switching. A switching pattern of the LB-CA switching indicates a plurality of switching gaps for switching between the first cell and a second cell. The configuration parameters further indicate beam application time (beamAppTime) symbols indicating when the wireless device is to apply a transmission configuration indicator (TCI) state, for the first cell, indicated by downlink control information (DCI). The method further comprises, based on the beamAppTime symbols overlapping with a (or any) of the plurality of switching gaps, skipping switching (not switching) to the second cell during the beamAppTime symbols (and / or the switching gap)
[0258] In an example of the embodiment of this disclosure, there is provided a method comprising receiving, by a wireless device, one or more configuration parameters indicating that a first cell is configured with a carrier aggregation (CA) (e.g., a low-band CA (“LB-CA’’)) switching. A switching pattern of the CA switching indicates a plurality of switching gaps for switching between the first cell and a second cell. The method further comprises, based on beam application time (beamAppTime) symbols overlapping with a (or any) of the plurality of switching gaps, skipping switching (not switching) to the second cell during the beamAppTime symbols (and / or during the switching gap).
[0259] In an example of the embodiment of this disclosure, there is provided a method comprising receiving, by a wireless device, one or more configuration parameters indicating that a first cell is configured with a low-band carrier aggregation (LB-CA) switching. A switching pattern of the LB-CA switching indicates a plurality of switching gaps for switching between the first cell and a second cell. The configuration parameters further indicate a value of beam application time (beamAppTime), indicating when the wireless device is to apply a transmission configuration indicator (TCI) state, for the first cell, indicated by downlink control information (DCI) The value of the beamAppTime is larger than a sum of: a switching gap in the plurality of switching gaps, for switching from the first cell to the second cell, and a value of a minimum beamAppTime. The method further comprises receiving DCI indicating a TCI for the first cell (e.g., the DCI carrying an indication of the TCI state). The TCI state is different from a current TCI state of the first cell. The method further comprises transmitting an uplink channel (e.g., PUCCH or PUSCH) with a positive feedback (e.g., positive HARQ-ACK) corresponding to the DCI (e.g., the positive feedback acknowledging the receipt of the DCI), applying the indicated TCI state, starting from a slot indicated by the BeamAppTime (e.g., indicated by the value of the BeamAppTime), and receiving downlink data, based on the indicated TCI sate.
[0260] In an example of the embodiment of this disclosure, there is provided a method comprising receiving, by a wireless device, one or more configuration parameters indicating a value of beam application time (beamAppTime). The value of the beamAppTime is larger than a switching gap of a carrier aggregation (CA) (e.g., a low-band CA (“LB-Docket No.25-1081 PCTCA”)) switching (e.g., a time duration indicated by the value of the beamAppTime is greater than a time length of the switching gap), and the switching gap is for switching between a first cell and a second cell. The method further comprises, based on the beamAppTime, applying a TCI state, for the first cell, indicated by downlink control information (DCI).
[0261] As described above, according to one example of the embodiment of this disclosure, a time duration for applying the new TCI state for the first cell may be configured based on a carrier aggregation (CA) (e.g., LB-CA) switching latency value— indicating the length of the switching gap for switching between the two cells— or based on an additional offset value. This configuration allows the UE sufficient time to perform the CA switching while preparing to apply the new TCI state for the other cell. Asa result, the overlap between the TCI application window for one cell and the switching gap does not prevent the UE from properly applying the new TCI state and from successfully communicating via the respective cell during LB-CA operations.
[0262] Alternatively, in another example of the embodiment of this disclosure, in case there is an overlap between the TCI application window for one cell and the switching gap, the UE may skip the switching and drop data that is scheduled to be received or transmitted during the T Cl application window via the other cell.
[0263] FIG. 17 shows an exemplary scenario 1700 where the embodiment of this disclosure can be applied. In scenario 1700, UE 1710 is configured to communicate with a base station (BS) 1720 in / via a first cell (“1stCell”) and a second cell ("2ndCell”). In one example, the first cell is a primary cell (PCell) of UE 1710, and the second cell is a secondary cell (SCell) of UE 1710. In another example, the first cell is an SCell of UE 1710, and the second cell Isa PCell of UE 1710. In this disclosure, the expression “A / B” is used to mean " A and / or B.” For example, “communicating in / via the first cell” refers to communicating in, via, or both in and via the first cell. Accordingly, any instance of “communicating in" may be replaced with “communicating via,” and vice versa. Also, in this disclosure, the expression “communicating in / via a cell” means transmitting data and / or receiving data, in / via a cell. Accordingly, any instance of “communicating” may be replaced with “transmitting and / or receiving,” and vice versa.
[0264] Each of the first cell and the second cell may be configured with a carrier aggregation (CA) (e.g., a low-band carrier aggregation, also referred to as “LB-CA”) switching that is based on a CA switching pattern of switching between the first cell and the second cell. FIG. 17 shows an example of a CA switching pattern 1730. In this disclosure, the CA switching pattern may also be referred to as a time division multiplexing (TDM) pattern, a time domain multiplexing (TDM) pattern, a carrier switching (CS) pattern, or simply a CS.
[0265] As shown in FIG. 17, according to CA switching pattern 1730, UE 1710 may communicate with BS 1720 via the first cell (but not via the second cell) during a first set of time slots 1722, 1726, and 1730, and via the second cell (but not via the first cell) during a second set of time slots 1724, 1728, and 1732. In other words, UE 1710 may communicate with BS 1720 in either the first or second cell in a time division manner.
[0266] CA switching pattern 1730 may indicate a plurality of switching gaps 1742a-f. Each switching gap represents a time duration (e.g., required or needed by UE 1710) for switching from the first cell to the second cell or from the second cell to the first cell. For instance, switching gap 1742a represents a time duration for UE 1710 to switch fromDocket No.25-1081 PCTcommunicating via the first cell to communicating via the second cell while switching gap 1742b represents a time duration for UE 1710 to switch from communicating via the second cell to communicating via the first cell.
[0267] Even though FIG. 17 shows that the length of a time interval allocated to either the first cell or the second cell in CS switching pattern 1730 is same as the length of a slot (a.k.a., "a time slot'), the length of the time interval may be different from the length of a slot. As illustrated in FIG. 17, each slot consists of a certain number (e.g., 14) symbols 1706 (e.g., orthogonal frequency-division multiplexing (OFDM) symbols).
[0268] In scenario 1700 shown in FIG. 17, UE 1710 may receive configuration parameter(s) 1702. Note that, in this disclosure, the expression "element(s)” means one or more elements. Thus, "configuration parameter(s)” means one or more configuration parameters. In one example, configuration parameter(s) 1702 are included in radio resource control (RRC) message(s).
[0269] Configuration parameter(s) 1702 may indicate a carrier aggregation (CA) (e.g., LB-CA) switching between the first cell and the second cell. More specifically, configuration parameter(s) 1702 may indicate CA switching pattern 1730 of the CA switching. In indicating CA switching pattern 1730, configuration parameter(s) 1702 may indicate the first set of time slots 1722, 1726, and 1730 allocated to the first cell, and the second set of time slots 1724, 1728, and 1732 allocated to the second cell.
[0270] Additionally, configuration parameter(s) 1702 may indicate a CA switching latency value indicating a length of each of switching gaps 1742a-f (in case all switching gaps have the same length) or may indicate two CA switching latency values— one indicating a length of each of switching gaps 1742a, 1742c, and 1742e, for switching from the first cell to the second cell and another one indicating a length of each of switching gaps 1742b, 1742d, and 1742f, for switching from the second cell to the first cell.
[0271] In one example, configuration parameter(s) 1702 may indicate the CA switching in a configuration of UE 1710's serving cell (e.g., within the “servingcellConfig” IE). For instance, configuration parameter(s) 1702 may include a configuration of the first / second cell, and the configuration of the first / second cell may indicate that the first / second cell is configured with the CA switching. In one example, the configuration of the first / second cell may be included in a configuration of a cell group which comprises the first and second cells.
[0272] After receiving configuration parameter(s) 1702, UE 1710 may receive downlink control information (DCI) 1704 indicating a new transmission configuration information (TCI) state for the first cell, which is different from the current TCI state of the first cell. Note that even though, for simple illustration purpose, FIG. 17 shows that UE 1710 receives DC11704 within a certain symbol, UE 1710 may receive DC11704 at any symbol within slot 1724 and / or may receive DC11704 across multiple symbols. In one example, UE 1710 may receive DC11704 by receiving a physical downlink control channel (PDCCH) that contains DC11704. In the examples provided in this disclosure, DC11704 indicates a new TCI state for the first cell.
[0273] In response to receiving DC11704, UE 1710 may transmit an uplink (UL) channel 1708 (e.g., physical uplink shared channel (PUSCH) or physical uplink control channel (PUC CH)) with (e.g., containing) a positive feedback to DCI 1704. In one example, uplink channel 1708 is transmitted via a PCell. The positive feedback may indicate anDocket No.25-1081 PCTacknowledgement that UE 1710 successfully received DC11704 or the PDCCH containing DC11704. One example of such positive feedback is a positive hybrid automatic repeat request acknowledgement (HARQ-ACK) feedback.
[0274] Note that even though, for simple illustration purpose, FIG. 17 shows that UE 1710 transmits UL channel 1708 at symbol 1706a, UE 1710 may transmit UL channel 1708 at any symbol within slot 1726 and / or may transmit UL channel 1708 across multiple symbols. Also note that, in this disclosure, the expression of transmitting an uplink channel means transmitting uplink data / signal / control via the uplink channel. Similarly, the expression of receiving a downlink channel means receiving downlink data / signal / control via the downlink channel. In FIG. 17, symbol 1706a is the last symbol of UL channel 1708
[0275] Even though FIG. 17 shows that slot 1724 during which UE 1710 receives DC11704 and slot 1726 during which UE 1710 transmits UL channel 1708 are adjacent to each other, they do not need to be adjacent. Also, in a different example, slots 1724 and 1726 may be the same slot.
[0276] After transmitting UL channel 1708, after a time duration 1712, UE 1710 may apply, during slot 1728, the new TCI state indicated by DC1 1704. In one example, time duration 1712 may correspond to beam application time (beamAppTime) for / of the first cell. For instance, time duration 1722 may be same as the beamAppTime.
[0277] Applying the new TCI state may comprise receiving DL data / signal / channel (e.g., PDCCH, PDSCH, or CSI-RS) and / or transmitting UL data / signal / channel (e.g., PUCCH, PUSCH, SRS), based on the new TCI state. More specifically, in one example, applying the new TCI state comprises receiving DL data / signal / channel, based on spatial domain filter parameter(s) of the new TCI state and / or QCL assumption based on the new TCI state and / or transmitting UL data / signal / channel, based on spatial domain filter parameter(s) of the new TCI state and / or QCL assumption based on the new TCI state. In an example, the new TCI state may update an indicated TCI state of the first cell. In an example, DC11704 updates the indicated TCI of the first cell based on an unified TCI operation / framework. For example, configuration parameter(s) 1702 may indicate dl-OrJointTCI-StateList for the first cell. The DCI may indicate the new TCI state of / from the dl-OrJointTCI-StateList.
[0278] In one example, configuration parameter(s) 1702 may indicate a value of the beamAppTime for the first cell, and the value of the beamAppTime may indicate when UE 1710 is to apply the new TCI state, indicated by DC11704, for the first cell. More specifically, in one example, the value of the beamAppTime may indicate an earliest slot to apply the TCI state indicated by the DCI (e.g., when the first cell is not configured with the CA switching).
[0279] In one example, the value of the beamAppTime may indicate a number of symbols (a.k.a., “beamAppTime symbols’’), and the new TCI state for the first cell may be applied after an elapse of time corresponding to the symbols, from a timing of transmitting UL channel 1708 (e.g., the last symbol of transmission of UL channel 1708).
[0280] In one example, the value of the beamAppTime may indicate the minimum time duration required / needed for UE 1710 to apply the new TCI state. For instance, applying the new TCI state for the first cell may require some tuning in radio frequency (RF) circuitries of UE 1710 and the beamAppTime may indicate the time duration for performing the required tuning. Thus, in one example, the beamAppTime corresponding to (e.g., same as) time duration 1712 may also be called “initial beamAppTime” or “minimum beamAppTime” or “minBeamApplicationTime.”Docket No. 25-1081 PCT
[0281] As explained above, time duration 1712 may represent how long it takes before UE 1710 applies the new TCI state, for the first cell, indicated by DC1 1704. However, in case time duration 1712 (or the initial / minimum beamAppTime), for applying the new TCI state for the first cell, overlaps with any of switching gaps 1742a- 1742f, there is a conflict in the operation of UE 1710, because UE 1710 may be unable to perform the CA switching (e.g., the CA switching from the first cell to the second cell) during any of the switching gaps, while preparing to apply the new TCI state for the first cell.
[0282] To address the problem described above, in one example of the embodiment of this disclosure, the application of a new TCI state for the first cell, indicated by DC1 1704, is delayed based on either a CA switching latency value or a fixed offset value (e.g., two symbols). Either one of these values may be used to determine the appropriate starting slot for applying the new TCI state to the first cell.
[0283] As previously noted, the CA switching latency value may represent the duration of one of the switching gaps 1742a-f. In one example, this value reflects the time required for UE 1710 to switch from the first cell to the second cell for the CA switching operation. In another example, it may indicate the time needed for switching from the second cell back to the first cell. In other words, the CA switching latency value represents the latency associated with a cell switching in either direction.
[0284] FIG. 18 illustrates an exemplary scenario 1800 demonstrating how the CA switching latency value or the fixed offset value may be applied to determine the timing for applying a new TCI state. In scenario 1800, a time period 1814 corresponds to the CA switching latency value or the fixed offset value. In other words, either the CA switching latency value or the fixed offset value may indicate a length of time period 1814.
[0285] Compared to scenario 1700 shown in FIG. 17, scenario 1800 in FIG. 18 introduces an extended duration between the transmission timing of UL channel 1708 (e.g., the last symbol of UL channel 1708) and the application slot of the new TCI state, increased by either the CA switching latency value or the fixed offset. Specifically, in scenario 1700, time period 1712 (e.g., beamAppTime) represents the time it takes for UE 1710 to apply the new TCI state for the first cell after transmitting the UL channel 1708 with a positive acknowledgment. In contrast, in scenario 1800, time period 1812—which includes both time period 1712 and an additional time period 1814 (corresponding to the CA switching latency value or fixed offset)—represents the total delay before the new TCI state is applied. In case time duration 1712 corresponds to the beamAppTime for the first cell, the earliest time slot for applying the new TCI state is determined by the sum of beamAppTime and either the CA switching latency or the additional offset.
[0286] This increase in delay provides a practical benefit. For instance, if time period 1712 represents the minimum time required for UE 1710 to apply the new TCI state, the UE cannot switch to the second cell, for the CA switching, during this interval, as it may be busy for preparing the application of the new TCI state. Consequently, an overlap between time period 1712 and a switching gap (e.g., 1742c) may result in communication conflicts or failures.
[0287] By contrast, time period 1812 includes not only the minimum required time for applying the new TCI state but also additional time for the UE to switch cells (e.g., from the first cell to the second cell via switching gap 1742c). This extended period helps prevent timing conflicts and supports more reliable CA switching operations.Docket No.25-1081 PCT
[0288] One exemplary approach to achieving this is for UE 1710 to prepare for applying the new TCI state during time period 1812, excluding the switching gap 1742c, during which the UE performs CA switching from the first cell to the second cell. Once the CA switching is complete, the UE may resume preparation for applying the new TCI state. Alternatively, UE 1710 may perform the preparation during time period 1712 and then carry out the CA switching during the subsequent time period 1814. After the switching is completed, the UE may apply the new TCI state for the first cell and begin communication via the second cell.
[0289] As mentioned above, in one example of the embodiment, the new TCI state for the first cell indicated by DCI 1704 is applied during a slot which is after at least a sum of the CA switching latency value / the fixed offset value and the beamAppTime from the timing of transmitting UL channel 1708 (e.g., the last symbol of UL channel 1708) (e.g., which is after a sum of a time duration indicated by the CA switching latency value / the fixed offset value and a time duration indicated by the beamAppTime, from the last symbol of UL channel 1708).
[0290] However, in a different example of the embodiment, the slot during which the new TCI state for the first cell is applied, may be determined based on a maximum or a minimum value from among the CA switching latency value and the beamAppTime. More specifically, in one example, the slot during which the new TCI state is applied is a slot occurring after a greater one or a smaller one from among the CA switching latency value and the beamAppTime from the last symbol of UL channel 1708.
[0291] The following paragraph discloses an example of implementation of the embodiment of this disclosure.with any of switching gaps 1742a—f, UE 1710 may delay the TCI state application. The amount of delay may be based on, or equal to, the switching latency value or a predefined offset. This ensures that UE 1710 applies the new TCI state only after completing the necessary CA switching.
[0294] In an alternative example, rather than delaying the application of the new TCI state, UE 1710 may skip CA switching altogether during the overlapping time interval. This approach is illustrated in scenario 1900 in FIG. 19.Docket No.25-1081 PCT
[0295] Similar to scenario 1700 in FIG. 17, scenario 1900 shows a case where time duration 1712 overlaps with switching gap 1742c. As previously explained, this overlap may prevent UE 1710 from performing both the CA switching and the preparation for applying the new TCI state during that time. Therefore, in one example, UE 1710 may skip the CA switching— i.e., it may remain in communication with the first cell and ignore the scheduled switching to the second cell during switching gap 1742c. By staying in the first cell, UE 1710 avoids the conflict and can utilize the entire time duration 1712 to complete preparation for applying the new TCI state.
[0296] The following paragraph discloses an example of implementation of the embodiment of this disclosure.application of the new TCI state for the first cell at least by an amount (i.e., a time delay) corresponding to the CA switching latency value or the predefined slot offset value. For instance, UE 1710 may delay the application of the new TCI state for the first cell such that the new TCI state is applied at least after an elapse of a time period, corresponding to a sum of the beamAppTime and the CA switching latency value / the predefined slot offset value, from the transmitting time of UL channel 1708.
[0299] However, in a different example of the embodiment, BS 1720 may adjust / update / increase the beamAppTime (a.k.a., “initial beamAppTime” or “minimum beamAppTime”) such that the increased beamAppTime (e.g., corresponding to time period 1812 in FIG. 18) corresponds to (eg., is same as) the sum of the beamAppTime and the CA switching latency value / the predefined slot offset value.
[0300] In order for BS 1720 to adjust / update / increase the minimum beamAppTime, BS 1720 needs to obtain the minimum beamAppTime supported by UE 1710. Thus, in one example, UE 1710 may transmit to BS 1720 UE radio access capability parameter(s) such that BS 1720 respects the signalled UE radio access capability parameter(s) when configuring and / or scheduling UE 1710. The UE access capability parameter(s) may indicate (e.g., may comprise aDocket No.25-1081 PCTfield indicating) the minimum beamAppTime (e.g., indicated in a number of symbols per SCS). In one example, the minimum beamAppTime may be indicated in an information element indicating TCI state indication for update and activation (e.g., "unifiedSeperateTCI-multiMac-CE-r17").
[0301] After obtaining the minimum beamAppTime, BS 1720 may determine whether the minimum beamAppTime overlaps or may possibly overlap with any of switching gaps 1742a-f, and if there is an actual / potential overlap, BS 1720 may increase / adjust / change / update the minimum beamAppTime such that the increased beamAppTime includes at least one switching gap (e.g., 1742c). Alternatively, without determining whether the minimum beamAppTime overlaps or may possibly overlap with any of the switching gaps, if BS 1720 configures a low band carrier aggregation (LB-CA), which involves dynamic switching between first cell and the second cell, BS 1720 may increase / adjust / change / update the minimum beamAppTime such that the increased beamAppTime includes at least one switching gap (e.g., 1742c).
[0302] The following paragraph discloses an example of implementation of the embodiment of this disclosure.period for applying a new or updated TCI state for the first cell— indicated by a DCI (Downlink Control Information)— and the switching gap of the CA switching, such as a transition from the first cell to the second cell. A similar issue can also occur when the UE 1710 receives a DCI indicating a new or updated TCI state for the second cell. In this case, the problem arises if there is an overlap between the application period of the TCI state for the second cell and the CA switching gap, for example, during a transition from the second cell back to the first cell.
[0306] To address this issue, an example embodiment allows the new or updated TCI state for the first cell to be used as the TCI state for the second cell. Specifically, consider a scenario in which distinct TCI states are configured for the first and second cells. In this case, when UE 1710 is configured for CA switching between the two cells, it may be set up to apply the new or updated TCI state for the first cell over two consecutive slots For instance, as illustrated in FIG. 18, UE 1710 could apply the new TCI state to the first cell during slot 1730 and reuse the same TCI state for the second cell in slot 1732. Alternatively, the UE may be configured with a shared TCI state for both cells, such that any new or updated TCI state for the first cell is automatically applied to the second cell as well.
[0307] For example, configuration parameters 1702 may indicate dl-OrJointTCI-StateList that is applied to both the first cell and the second cell.Docket No.25-1081 PCT
[0308] Alternatively, a reference cell index indicating an index of the first cell may be configured for the second cell. Based on the reference cell index, UE 1710 uses the first cell’s TCI state for the second cell.
[0309] Alternatively, BS 1720 may configure a first dl-OrJointTCI-StateList for the first cell, and configure a second dl-OrJointTCI-StateList for the second cell. A first indicated TCI state may be updated and used for the first cell, and a second indicated TCI state may be updated and used for the second cell. BS 1720 may update the first indicated TCI state during one or more consecutive time slots, that are assigned to the first cell, such that the update is completed within the one or more consecutive time slots. BS 1720 may transmit a DCI indicating a new TCI state for the first cell such that a beamAppTime of the new TCI state overlaps with one or more time slots assigned to the first cell. In this case, the first cell is the primary cell. In this case, when BS 1720 transmits a second DCI indicating a new TCI state for the second cell, UE 1710 transmits an uplink transmission comprising / indicating a positive HARQ-ACK feedback corresponding to the second DCI via the first cell. Thus, to avoid overlapping with a carrier switching time, BS 1720 may transmit the second DCI such that a second beamAppTime of the new TCI state overlaps with one or more time slots assigned to the first cell. BS 1720 may transmit a DCI updating a TCI state for / of the first cell or the second cell such that there is no switching time overlapping with a beamAppTime for the TCI state.
[0310] FIG. 20 shows a method 2000 according to an example of the embodiment of this disclosure. Method 2000 may begin with step 2002. Step 2002 comprises transmitting, by a wireless device (e.g., UE 1710), an uplink channel (1708) corresponding to downlink control information (DCI) (eg., 1704) indicating a transmission configuration information (TCI) state for a first cell (e.g., the first cell in FIG. 17). The TCI state maybe different from a current TCI state of the first cell. Step 2004 comprises applying the indicated TCI state, based on: a carrier aggregation (CA) switching latency value for switching, for CA, between the first cell and a second cell; or a fixed offset value (e.g., 2 symbols).
[0311] In one example, the indicated TCI state is applied based on the CA switching latency value.
[0312] In one example, the CA switching latency value indicates a latency for switching, for the CA, between the first cell and the second cell.
[0313] One example of the CA is a low-band CA (“LB-CA”) that is based on switching between the first cell and the second cell. In one example, the CA switching latency value may indicate a time length of the latency. More specifically, the CA switching latency may indicate a time duration of how long it takes for the wireless device to switch, for the CA, from the first cell to the second cell or to switch, for the CA, from the second cell to the first cell.
[0314] In one example, the indicated TCI state is applied, starting from a slot which is based on the CA switching latency value.
[0315] In one example, the slot is at least after the CA switching latency value, from a timing of transmitting the uplink channel.
[0316] As mentioned above, in one example, the CA switching latency indicates a time duration of how long it takes for the wireless device to switch, for the CA, from the first cell to the second cell or to switch, for the CA, from the second cell to the first cell. In this example, a starting timing of applying the indicated TCI state may be at or within aDocket No.25-1081 PCTslot that is after an elapse of the time duration corresponding to the CA switching latency value from the timing of transmitting the uplink channel.
[0317] In one example, the slot is further based on beam application time (beamAppTime) symbols.
[0318] In one example, the slot is based on a combination of: the beamAppTime symbols and the CA switching latency value.
[0319] In one example, the slot is after at least a sum of the beamAppTime symbols and the CA switching latency value, from the timing of the transmitting the uplink channel.
[0320] In one example, the beamAppTime symbols takes up X msec / symbols and the CA switching latency value indicates Y msec / symbols. In this example, the transmitting the uplink channel occurs at least X+Y msec / symbols, after the slot.
[0321] In one example, the slot is after at least a maximum (or greater) value from among the beamAppTime symbols and the CA switching latency value, from the timing of the transmitting the uplink channel.
[0322] In one example, the slot may be after at least a maximum value from among a time duration of the beamAppTime symbols and a time duration of the CA switching latency value, from the timing of the transmitting the uplink channel. For instance, let's assume that the beamAppTime symbols takes up X msec and the CA switching latency value indicates Y msec which is greater than X msec. In this case, the transmitting the uplink channel may occur at least Y msec after the slot. Conversely, if X msec is greater than Y msec, the transmitting the uplink channel may occur at least X msec after the slot.
[0323] In one example, the slot is after at least a minimum (or smaller) value from among the beamAppTime symbols and the CA switching latency value, from the timing of the transmitting the uplink channel.
[0324] More specifically, the slot may be after at least a minimum value from among a time duration of the beamAppTime symbols and a time duration of the CA switching latency value, from the timing of the transmitting the uplink channel. For instance, let's assume that the beamAppTime symbols takes up X msec / symbols and the CA switching latency value indicates Y msec / symbols which is greater than X msec / symbols. In this case, the transmitting the uplink channel may occur at least X msec / s after the slot. Conversely, if X msec / symbols is greater than Y msec / symbols, the transmitting the uplink channel may occur at least Y msec / symbols after the slot.
[0325] In one example, the indicated TCI state is applied based on the fixed offset value.
[0326] In one example, the indicated TCI state is applied, starting from a slot which is based on the fixed offset value.
[0327] In one example, the slot is at least after the fixed offset value, from a timing of transmitting the uplink channel.
[0328] In one example, the slot is based on a combination of: beam application time (beamAppTime) symbols and the fixed offset value.
[0329] In one example, the slot is based on a sum of the beamAppTime symbols and the fixed offset value, from the timing of the transmitting the uplink channel.
[0330] In one example, the beamAppTime symbols takes up X msec / symbols and the fixed offset value indicates Y msec / symbols. In this example, the transmitting the uplink channel occurs at least X+Y msec / symbols, before the slot.Docket No.25-1081 PCT
[0331] In one example, the timing of the transmitting the uplink channel corresponds to the last symbol of the uplink channel.
[0332] For instance, the timing of the transmitting the uplink channel is within or at the last symbol of the uplink channel.
[0333] In one example, the method comprises receiving the DCI indicating the TCI state for the first cell. In other words, the DCI may carry an indication of the TCI state. In one example, the DCI may carry the TCI state indication with any downlink assignment.
[0334] In one example, the uplink channel is with a positive feedback corresponding to the DCI.
[0335] In one example, uplink channel may comprise the positive feedback, and the positive feedback may correspond to the DCI carrying the TCI state indication without any downlink assignment or may correspond to a physical downlink shared channel (PDSCH) scheduled by the DCI carrying the TCI state indication.
[0336] More specifically, for instance, the positive feedback may be an acknowledgement of the receipt of the DCI or the PDSCH. One example of the positive feedback is a positive HARQ-ACK.
[0337] In one example, the method further comprises receiving, by the wireless device one or more configuration parameters indicating: the beamAppTime symbols and the CA switching latency value and / or the fixed offset value.
[0338] In one example, the uplink channel is either: a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH).
[0339] In one example, the positive feedback is a positive hybrid automatic repeat request acknowledgement (HARQ-ACK) feedback.
[0340] In one example, the beamAppTime symbols indicate when the wireless device is to apply a TCI state, for the first cell, indicated by DCI.
[0341] In one example, the beamAppTime symbols indicate an earliest slot to apply the TCI state indicated by the DCI.
[0342] In one example, the beamAppTime symbols indicate an earliest slot to apply the TCI state, of the first cell, indicated by the DCI when the first cell is not configured with CA which is based on switching between the first cell and the second cell.
[0343] In one example, the uplink channel is transmitted during a first time duration, the indicated TCI state is applied during a second time duration, the second time duration is after a third time duration, and the third time duration is after the first time duration.
[0344] In one example, the third time duration starts at an end of the first time duration.
[0345] In one example, the third time duration is greater than or equal to the sum of the beamAppTime symbols and the CA switching latency value.
[0346] More specifically, in one example, the third time duration is greater than or equal to a length of a time interval corresponding to the sum of the beamAppTime symbols and the CA switching latency value.Docket No.25-1081 PCT
[0347] In one example, the first cell is a primary cell (PCell), the uplink channel is transmitted in the PCell and the CA switching latency value indicates a length of a switching latency for switching from the first cell to the second cell.
[0348] In one example, the second cell is a secondary cell (SCell).
[0349] In one example, the CA switching latency value is set to a first value if the first cell is the PCell and is set to a second value if the first cell is the SCell. Conversely, in this example, the CA switching latency value is set to the first value if the second cell is the SCell and is set to the second value if the second cell is the PCell. Here, the CA switching latency value of the first value may indicate that it is a switching latency value from the PCell to the SCell while the CA switching latency value of the second value may indicate that it is a switching latency value from the SCell to the PCell.
[0350] In one example, the second cell is a primary cell (PCell), the uplink channel is transmitted in the PCell, and the CA switching latency value indicates a length of a switching latency for switching from the second cell to the first cell.
[0351] In one example, the first cell is a secondary cell (SCell).
[0352] In one example, the applying the TCI state comprises: receiving downlink data, based on the TCI state and / or transmitting uplink data, based on the TCI state.
[0353] In one example, the downlink data is one of a PDCCH, a PDSCH, or a CSI-RS.
[0354] In one example, receiving the downlink data based on the TCI state comprises receiving the downlink data, based on: spatial domain filter parameters of the TCI state or QCL assumption based on the TCI state.
[0355] In one example, the uplink data is one of a PUCCH, a PUSCH or a SRS.
[0356] FIG. 21 shows a method 2100 according to the embodiment of this disclosure. Method 2100 may begin with step 2102. Step 2102 comprises receiving, by a wireless device (e.g., UE 1710), one or more configuration parameters (e.g., 1702) indicating that a first cell (e.g., the first cell in FIG. 17) is configured with a carrier aggregation (CA) (e.g., a low-band CA (“LB-CA”)) switching. A switching pattern of the LB-CA switching may indicate a first plurality of time slots allocated to the first cell and a second plurality of time slots allocated to a second cell. Step 2104 comprises, based on whether beam application time (beamAppTime) symbols overlap with one (or any) of the second plurality of time slots allocated to the second cell, either: transmitting or receiving data scheduled in the second cell, during the one of the second plurality of time slots or dropping data scheduled to be received or transmitted, during the one of the second plurality of time slots, in the second cell.
[0357] In one example, the wireless device is configured to communicate: in the first cell during the first plurality of time slots and in the second cell during the second plurality of time slots.
[0358] In one example, the one or more configuration parameters indicate the beamAppTime symbols and the beamAppTime symbols indicate when the wireless device is to apply a transmission configuration information (TCI) state, for the first cell, indicated by downlink control information (DCI).
[0359] In one example, based on the beamAppTime symbols overlapping with a (or any) of the second plurality of time slots allocated to the second cell, the data scheduled to be received or transmitted, during the beamAppTime symbols, in the second cell is dropped.Docket No.25-1081 PCT
[0360] In other words, based on the beamAppTime symbols overlapping with a (or any) of the second plurality of time slots allocated to the second cell, the wireless device may skip communicating in the second cell. In one example, the skipping the communicating in the second cell may mean that the wireless device skips switching to the second cell, that the wireless device ignores the switching pattern of the LB-CA, and / or that the wireless device stays in the first cell.
[0361] In one example, based on the beamAppTime symbols not overlapping with a (or any) of the second plurality of time slots allocated to the second cell, the data scheduled in the second cell is received or transmitted, during the second plurality of time slots symbols.
[0362] In other words, based on the beamAppTime symbols not overlapping with a (or any) of the second plurality of time slots allocated to the second cell, the wireless device may communicate in the second cell. In one example, the communicating in the second cell may mean that the wireless device follows the switching pattern of the LB-CA.
[0363] In one example, the method further comprises receiving DCI indicating a TCI state for the first cell (e.g., the DCI carrying an indication of the TCI state). The TCI state is different from a current TCI state of the first cell. The method further comprises transmitting an uplink channel (e.g., PUCCH or PUSCH) with a positive feedback (e.g., positive HARQ-ACK) corresponding to the DCI (e.g., the positive feedback acknowledging the receipt of the DCI). The method further comprises applying the indicated TCI state, starting from a slot which is after at least the BeamAppTime symbols, from a timing of transmitting the uplink channel.
[0364] In one example, when the beamAppTime symbols takes up X msec, the transmitting the uplink channel may occur at least X msec, after the timing of transmitting the uplink channel.
[0365] In one example, the method further comprises, after applying the indicated TCI state, transmitting or receiving data, in the second cell, during one or more of the second plurality of time slots allocated to the second cell.
[0366] In one example, the uplink channel is either: a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH).
[0367] In one example, the positive feedback is a positive hybrid automatic repeat request acknowledgement (HARQ-ACK) feedback.
[0368] In one example, the beamAppTime symbols indicate when the wireless device is to apply a TCI state, for the first cell, indicated by DCI.
[0369] In one example, the beamAppTime symbols indicate an earliest slot to apply the TCI state indicated by the DCI.
[0370] In one example, the applying the TCI state comprises receiving downlink data based on the TCI state.
[0371] In one example, the applying the TCI state comprises transmitting uplink data based on the TCI state.
[0372] In one example, the downlink data is one of a PDCCH, a PDSCH, or a CSI-RS. The uplink data is one of a PUCCH, a PUSCH or a SRS.
[0373] In one example, receiving the downlink data based on the TCI state comprises receiving the downlink data, based on: spatial domain filter parameters of the TCI state or QCL assumption based on the TCI state.Docket No.25-1081 PCT
[0374] In one example, transmitting the uplink data based on the TCI state comprises transmitting the uplink data, based on: spatial domain filter parameters of the TCI state, determining spatial domain filter parameters of the transmission based on the TCI state, QCL assumption based on the TCI state, or determining spatial domain filter parameters of the transmission based on QCL assumption indicated by the TCI state.
[0375] FIG. 22 shows a method 2200 according to the embodiment of this disclosure. Method 2200 may begin with step 2202. Step 2202 comprises receiving, by a wireless device (e.g., UE 1710), one or more configuration parameters (e.g., 1702) indicating that a first cell (e.g., the first cell in FIG. 17) is configured with a carrier aggregation (CA) (e.g., a low-band CA (“LB-CA")) switching. A switching pattern of the CA switching indicates a plurality of switching gaps for switching between the first cell and a second cell. Step 2204 comprises, based on beam application time (beamAppTime) symbols overlapping with a (or any) of the plurality of switching gaps, skipping switching (not switching) to the second cell during the beamAppTime symbols (and / or during the switching gap).
[0376] In one example, the beamAppTime symbols indicate when the wireless device is to apply a transmission configuration indicator (TCI) state, for the first cell, indicated by downlink control information (DCI).
[0377] In one example, the one or more configuration parameters indicate the beamAppTime symbols.
[0378] In one example, the method comprises, based on the beamAppTime symbols overlapping with a (or any) of the plurality of switching gaps, skipping communicating via the second cell (i.e., staying in the first cell, dropping scheduled data to be transmitted or received via the second cell, etc.).
[0379] In one example, the method comprises, based on the skipping the switching to the second cell during the beamAppTime symbols, skipping communicating via the second cell (i.e., staying in the first cell, dropping scheduled data to be transmitted or received via the second cell, etc.).
[0380] In one example, the method further comprises receiving DCI indicating a TCI state for the first cell (e.g., the DCI carrying an indication of the TCI state). The TCI state is different from a current TCI state of the first cell. The method further comprises transmitting an uplink channel (e.g., PUCCH or PUSCH) with a positive feedback (e.g., positive HARQ-ACK) corresponding to the DCI (e.g., the positive feedback acknowledging the receipt of the DCI), and applying the indicated TCI state, starting from a slot which is after at least the BeamAppTime symbols, from a timing of transmitting the uplink channel
[0381] In one example, when the beamAppTime symbols takes up X msec / symbols, the applying the indicated TCI state may occur at least X msec / symbols, after the timing of transmitting the uplink channel (e.g., the last symbol of the uplink channel).
[0382] In one example, the switching pattern of the LB-CA switching indicates: a first plurality of time slots allocated to the first cell and a second plurality of time slots allocated to a second cell.
[0383] In one example, the method further comprises, after applying the indicated TCI state, transmitting or receiving data, in the second cell, during one or more of the second plurality of time slots allocated to the second cell.
[0384] In one example, the uplink channel is either: a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH).Docket No.25-1081 PCT
[0385] In one example, the positive feedback is a positive hybrid automatic repeat request acknowledgement (HARQ-ACK) feedback.
[0386] In one example, the beamAppTime symbols indicate an earliest slot to apply the TCI state indicated by the DCI.
[0387] In one example, the applying the TCI state comprises: receiving downlink data based on the TCI state and / or transmitting uplink data based on the TCI state.
[0388] In one example, the downlink data is one of a PDCCH, a PDSCH, or a CSI-RS.
[0389] In one example, receiving the downlink data based on the TCI state comprises receiving the downlink data, based on: spatial domain filter parameters of the TCI state or QCL assumption based on the TCI state.
[0390] In one example, the uplink data is one of a PUCCH, a PUSCH or a SRS.
[0391] In one example, transmitting the uplink data based on the TCI state comprises transmitting the uplink data, based on one or more of: spatial domain filter parameters of the TCI state, determining spatial domain filter parameters of the transmission of the uplink data, based on the TCI state (e.g., based on the QCP assumption indicated by the TCI state), and QCL assumption based on the TCI state.
[0392] FIG. 23 shows a method 2300 according to the embodiment of this disclosure. Method 2300 may begin with step 2302. Step 2302 comprises receiving, by a wireless device (e.g., UE 1710), one or more configuration parameters (eg., 1702) indicating a value of beam application time (beamAppTime). The value of the beamAppTime is larger than a switching gap of a carrier aggregation (CA) (e.g., a low-band CA (“LB-CA")) switching (e.g., a time duration indicated by the value of the beamAppTime is greater than a time length of the switching gap). The switching gap is for switching between a first cell and a second cell. Step 2304 comprises, based on the beamAppTime, applying a TCI state, for the first cell, indicated by downlink control information (DCI).
[0393] In one example, the switching gap is for switching from the first cell to the second cell.
[0394] In one example, the TCI state indicated by the DCI is applied starting from a slot indicated by the beamAppTime (e.g., indicated by the value of the beamAppTime).
[0395] In one example, the method comprises receiving the DCI indicating the TCI state for the first cell (e.g., the DCI carrying an indication of the TCI state). The indicated TCI state is different from a current TCI state of the first cell. The method further comprises transmitting an uplink channel (e.g., PUCCH or PUSCH) with a positive feedback (e.g., positive HARQ-ACK) corresponding to the DCI (e.g., the positive feedback acknowledging the receipt of the DCI).
[0396] In one example, the method comprises receiving downlink data, based on the indicated TCI state.
[0397] In one example, the value of the beamAppTime indicates when the wireless device is to apply a TCI state, for the first cell, indicated by DCI.
[0398] In one example, the one or more configuration parameters indicate that the first cell is configured with the CA switching, a switching pattern of the CA switching indicates a plurality of switching gaps for switching between the first cell and the second cell, and the switching gap is one of the plurality of switching gaps.Docket No.25-1081 PCT
[0399] In one example, the value of the beamAppTime is larger than a sum of the switching gap and a value of a minimum beamAppTime (e.g., a time duration indicated by the value of the beamAppTime is longer than a sum of a time length of the switching gap and a time duration of the minimum beamAppTime or a number of symbols indicated by the value of the beamAppTime is greater than a sum of a number of symbols within the switching gap and a number of symbols indicated by the value of the minimum beamAppTime).
[0400] In one example, the value of the minimum beamAppTime indicates a number of symbols per subcarrier spacing (SCS).
[0401] In one example, the method comprises transmitting a message indicating a capability of the wireless device, wherein the message indicates (e.g., comprises a field indicating) the value of the minimum beamAppTime.
[0402] In one example, the message comprises an information element (IE) indicating whether the wireless device supports unified TCI state operation, and the IE comprises an IE indicating the value of the minimum beamAppTime.
[0403] In one example, the IE indicating whether the wireless device supports unified TCI state operation is "unifiedJointTCI-multiMAC-CE-r17, urifiedJointTCI-multiMAC-CE-\ / 17b(J' which indicates the support of unified TCI state operation with joint DL / UL TCI update for intra- and inter-cell beam management with more than one MAC-CE activated joint TCI state per CC with MAC CE and DCI based TCI state indication in DCI formats 1 J and 1_2 with and without DL assignment.
[0404] In one example, the one or more configuration parameters are received by the wireless device, based on transmitting the message.
[0405] In one example, the message is transmitted to a base station. Based on receiving the message, the base station may determine whether the minimum beamAppTime overlaps with the switching gap (e.g., determining whether symbols in the minimum beamAppTime overlap with symbols within the switching gap). Based on determining that the minimum beamAppTime overlaps with the switching gap, the base station may increment / revise / change the value of the minimum beamAppTime, thereby generating the value of the beamAppTime. The incremented / revised / changed amount may depend on (e.g., may be same as) the switching gap (e.g., may based on a number of symbols within the switching gap).
[0406] In one example, the uplink channel is either: a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH).
[0407] In one example, the positive feedback is a positive hybrid automatic repeat request acknowledgement (HARQ-ACK) feedback (acknowledging the receipt of the DCI).
[0408] In one example, the beamAppTime (or the value of the beamAppTime) indicate an earliest slot to apply the TCI state indicated by the DCI.
[0409] In one example, the beamAppTime (or the value of the beamAppTime) indicate the earliest slot to apply the TCI state indicated by the DCI, from / after a timing of transmitting the uplink channel.
[0410] In one example, the beamAppTime (or the value of the beamAppTime) indicate the earliest slot to apply the TCI state indicated by the DCI, from / after the last symbol of the uplink channel.Docket No.25-1081 PCT
[0411] In one example, the beamAppTime (or the value of the beamAppTime) indicates a number of symbols, and the earliest slot is at least the number of symbols, after the last symbol of the uplink channel.
[0412] In one example, the uplink channel is transmitted during a first time duration, the indicated TCI state is applied during a second time duration, the second time duration is after a third time duration, and the third time duration is after the first time duration.
[0413] In one example, the third time duration starts at an end of the first time duration.
[0414] In one example, the third time duration is greater than or equal to the value of the beamAppTime.
[0415] More specifically, in one example, the third time duration is greater than or equal to a length of a time interval or a number of symbols, indicated by the value of the beamAppTime.
[0416] In one example, the first cell is a primary cell (PCell) and the uplink channel is transmitted in the PCell.
[0417] In one example, the second cell is a primary cell (PCell), and the uplink channel is transmitted in the PCell.
[0418] In one example, the first cell is a secondary cell (SCell).
[0419] In one example, the applying the TCI state comprises: receiving downlink data, based on the TCI state and / or transmitting uplink data, based on the TCI state.
[0420] In one example, the downlink data is one of a PDCCH, a PDSCH, or a CSI-RS.
[0421] In one example, receiving the downlink data based on the TCI state comprises receiving the downlink data, based on: spatial domain filter parameters of the TCI state or QCL assumption based on the TCI state
[0422] In one example, the uplink data is one of a PUCCH, a PUSCH or a SRS.
[0423] In one example, transmitting the uplink data based on the TCI state comprises transmitting the uplink data, based on one or more of: spatial domain filter parameters of the TCI state, determining spatial domain filter parameters of the transmission of the uplink data, based on the TCI state (e.g., based on the QCP assumption indicated by the TCI state), and QCL assumption based on the TCI state.
[0424] Wireless communication systems may face additional challenges when a UE communicates via two cells configured with LB-CA. During a beam failure recovery (BFR) procedure in such configurations, the UE may receive DCI indicating a new beam to be used for communication via the first cell. The UE is expected to apply this new beam after a predefined time interval from when the DCI is received
[0425] A conflict may occur if this predefined time interval overlaps with a switching gap required for transitioning between the two cells in LB-CA. Due to hardware limitations, the UE may be unable to perform the necessary LB-CA switch and simultaneously prepare for applying the new beam. As a result, the UE might fail to either apply the new beam or complete the switch, potentially leading to degraded performance or communication failure.
[0426] Additionally, a conflict may arise if the beam application timing overlaps with time slot(s) allocated to the second cell in the LB-CA configuration. As with the previous scenario, hardware constraints may prevent the UE from performing the necessary LB-CA switch and simultaneously prepare for applying the new beam. As a result, this overlap can disrupt either the beam application or communication with the second cell using LB-CA, potentially resulting in reduced performance or connection issuesDocket No.25-1081 PCT
[0427] In order to solve the problems described above, according to an embodiment of this disclosure, a method 2400 shown in FIG. 24 is provided. Method 2400 may begin with step 2402. Step 2402 comprises receiving, by a wireless device (e.g., UE 1710), one or more configuration parameters (e.g., 1702) indicating that a first cell (e.g., the first cell in FIG. 17) is configured with a CA switching (e.g., an LB-CA switching). A switching pattern of the CA switching may indicate a plurality of switching gaps (e.g., 1742a-f) for switching between the first cell and the second cell. Step 2404 comprises skipping switching, from the first cell to the second cell, for the CA switching, during a switching gap in the plurality of switching gaps. The switching gap may overlap with a time duration for applying a first beam, for the first cell, indicated by downlink control information (DCI) (e.g., DC11704). The first beam indicated by the DCI may be different from a current beam of the first cell.
[0428] In one example, the switching from the first cell to the second cell for the CA switching may be skipped during the switching gap, based on the switching gap overlapping with the time duration.
[0429] In one example, the one or more configuration parameters may indicate a number of symbols (e.g., 28), indicating when the wireless device is to apply a beam, for the first cell, indicated by DCI (e.g., indicating when to apply the first beam indicated by the DCI).
[0430] In one example, the time duration is a time duration of the number of symbols.
[0431] For instance, the time duration may begin at the timing of receiving the DCI (e.g., the last symbol of a downlink channel carrying the DCI) and end at the timing of applying the first beam.
[0432] In one example, method 2400 may further comprise receiving, during a beam failure recovery (BFR) procedure, a physical downlink control channel (PDCCH) with the DCI indicating the first beam for the first cell.
[0433] In one example, method 2400 may further comprise applying, after the number of symbols from a last symbol of the PDCCH, the first beam indicated by the DCI, for the BFR procedure.
[0434] By skipping the switching duration the time duration, the wireless device can successfully apply the beam indicated by the DCI without interruption.
[0435] In another example of the embodiment, a method 2500 shown in FIG. 25 is provided. Method 2500 may begin with step 2502. Step 2502 comprises receiving, by a wireless device (e.g., UE 1710), one or more configuration parameters (e.g., 1702) indicating that a first cell (e.g., the first cell in FIG. 17) is configured with a CA switching (e.g., an LB-CA switching). A switching pattern of the LB-CA switching may indicate a first plurality of time slots allocated to the first cell, and a second plurality of time slots allocated to a second cell (e.g., the second cell in FIG. 17). Step 2504 comprises dropping data scheduled to be received or transmitted, in the second cell, during one or more of the second plurality of time slots, in the switching pattern, based on the one or more of the second plurality of time slots overlapping with a time duration for applying a first beam, for the first cell, indicated by downlink control information (DCI). The first beam is different from a current beam of the first cell.
[0436] In one example, the one or more configuration parameters indicate a number of symbols (e.g., 28), indicating when the wireless device is to apply a beam, for the first cell, indicated by DCI. The time duration for applying the first beam may be a time duration of the number of symbols.Docket No. 25-1081 PCT
[0437] In one example, method 2500 further comprises receiving, during a beam failure recovery (BFR) procedure, a physical downlink control channel (PDCCH) with the DCI indicating the first beam for the first cell.
[0438] In one example, method 2500 further comprises applying, after the number of symbols from a last symbol of the PDCCH, the first beam indicated by the DCI, for the BFR procedure.
[0439] In a different example of the embodiment, a method 2600 shown in FIG. 26 is provided. Method 2600 may begin with step 2602. Step 2602 comprises receiving, by a wireless device (e.g., UE 1710), one or more configuration parameters (e.g., 1702) indicating that a first cell (e.g., the first cell in FIG. 17) is configured with a CA switching (e.g., an LB-CA switching). A switching pattern of the LB-CA switching indicates a plurality of switching gaps for switching between the first cell and a second cell (e.g., the second cell in FIG. 17). Step 2604 comprises, after a time duration, applying the first beam, for the first cell, indicated by downlink control information (DCI). The time duration does not overlap with any of the plurality of switching gaps.
[0440] In one example, a base station serving the wireless device may determine (e.g., set) the time duration such that the time duration does not overlap with any of the plurality of switching gaps.
[0441] In one example, the one or more configuration parameters indicate a number of symbols (e.g., 28), indicating when the wireless device is to apply a beam, for the first cell, indicated by DCI.
[0442] In one example, the time duration is a time duration of the number of symbols.
[0443] In one example, method 2600 further comprises receiving, during a beam failure recovery (BFR) procedure, a physical downlink control channel (PDCCH) with the DCI (e.g., including the DCI) indicating the first beam for the first cell.
[0444] In one example, the time duration is the time duration of the number of symbols from a last symbol of the PDCCH.
[0445] In a different example of the embodiment, a method 2700 shown in FIG. 27 is provided. Method 2700 may begin with step 2702. Step 2702 comprises receiving, by a wireless device (e.g., UE 1710), one or more configuration parameters (e.g., 1702) indicating that a first cell (e.g., the first cell in FIG. 17) with a CA switching (e.g., an LB-CA switching). A switching pattern of the LB-CA switching may indicate a first plurality of time slots allocated to the first cell and a second plurality of time slots allocated to a second cell. Step 2704 comprises, after a time duration, applying the first beam, for the first cell, indicated by downlink control information (DCI). The time duration does not overlap with any of the second plurality of time slots.
[0446] In one example, a base station serving the wireless device may determine (e.g., set) the time duration such that the time duration does not overlap with any of the second plurality of time slots.
[0447] In one example, the one or more configuration parameters indicate a number of symbols (e.g., 28), indicating when the wireless device is to apply a beam, for the first cell, indicated by DCI.
[0448] In one example, the time duration is a time duration of the number of symbols.
[0449] In one example, method 2700 further comprises receiving, during a beam failure recovery (BFR) procedure, a physical downlink control channel (PDCCH) with the DCI indicating the first beam for the first cell.Docket No.25-1081 PCT
[0450] In one example, the time duration is the time duration of the number of symbols from a last symbol of the PDCCH.
[0451] In one example, there is provided a method comprising receiving, by a wireless device, one or more configuration parameters indicating a switching pattern indicating a first cell is configured with a low-band carrier aggregation (LB-CA) based on switching between the first cell and a second cell. The switching pattern indicates first time slots are assigned to the first cell and second time slots are assigned to the second cell. The method comprises transmitting a preamble via a random access resource and the first cell, and receiving an uplink grant comprised in a random access response corresponding to the preamble. The uplink grant indicates a repetition of an uplink data transmission. The method further comprises transmitting the uplink data transmission during one or more slots. At least one of the one or more slots overlaps with the second time slots.
[0452] In one example, the method further comprises receiving a downlink control information (DCI) indicating a second uplink grant indicating a second repetition of a second uplink data transmission.
[0453] In one example, the second uplink data transmission overlaps with one or more second slots, wherein a second slot, of the one or more second slots, overlaps with the second time slots.
[0454] In one example, the method further comprises dropping an uplink channel during the second slot, based on the DCI being scrambled with a C-RNTI or a MCS-C-RNTI (or not with a TC-RNTI), and transmitting the uplink channel during the second slot, based on the DCI being scrambled with a temporary C-RNTI (TC-RNTI).
[0455] In one example, there is provided a method comprising receiving, by a wireless device, one or more configuration parameters indicating a switching pattern indicating a first cell is configured with a low-band carrier aggregation (LB-CA) based on switching between the first cell and a second cell. The switching pattern indicates first time durations are assigned to the first cell and second time durations are assigned to the second cell. The method further comprises receiving a downlink control information (DCI) indicating: resourcesofa downlink data reception, via the second cell, overlapping with a first slot of the second time durations, and a timing offset for a hybrid automatic repeat request (HARQ) feedback (PDSCH-to-HARQ_feedback timing indicator), corresponding to the downlink data. An uplink transmission comprising the HARQ feedback overlaps with a second slot of the first time durations. The timing offset is less than or equal to X, where X is a maximum number of consecutive slots in a time slot of the second time durations. Alternatively the timing offset is applied at an end slot of a first time duration of the second time durations, wherein the first time duration is a time duration comprises consecutive one or more slots comprising the second slot and each of the one or more slots is assigned to the second cell. The method further comprises transmitting an uplink transmission comprising the HARQ feedback of the downlink data based on the timing offset.
[0456] In one example, each time duration of the second time durations comprises a plurality of slots.
[0457] In one example, the one or more configuration parameters further indicate a list of timing offset values (e.g., DL-DataToUL-ACK ), wherein one value of the list of timing offset values is indicaed in the DCI for the timing offset.Docket No.25-1081 PCT
[0458] In one example, a maximum value of each value of the timing offset values (e.g., DL-DataToUL-ACK) is X based on the timing offset being less than or equal to X, wherein is is the maximum number of consecutive slots in a time slot of the second time durations.
[0459] In one example, a maximum value of each value of the timing offset values (e.g., DL-DataToUL-ACK) is 15 based on the timing offset being applied at the end slot of the first time duration of the second time durations.
[0460] In one example, there is provided a method comprising receiving, by a wireless device, one or more configuration parameters indicating: a switching pattern indicating a primary cell is configured with a low-band carrier aggregation (LB-CA) based on switching between a first cell (e.g., the primary cell) and a second cell (e.g., a secondary cell). The switching pattern indicates first time durations are assigned to the first cell and second time durations are assigned to the second cell. The method further comprises receiving a downlink control command indicating an activation of the second cell, and measuring one or more channel state information (CSI) resources. The one or more CSI resources overlaps with the first time durations and / or the second time durations, while the secondary cell being activated based on the receiving. The method further comprises transmitting a CSI report, comprising a valid CSI report (i.e., not indicating out of range) during a first slot, while the secondary cell being activated, and starting communicating via the second cell, based on the switching pattern at least one or more slots after the first slot.
[0461] In one example, a number of the one or more slots is 1.
[0462] In one example, a number of the one or more slots is determined based on one or more of: an earliest switching gap from the first cell to the second cell based on switching pattern after the first slot; an earliest frame after the first slot; an earliest frame with a frame number index being multiple of M (e.g., M = 4) after the first slot; and an earliest switching gap from the first cell to the second cell based on switching pattern after an end of the transmissions of the CSI report.
[0463] In one example, the communicating via the second cell comprising measuring one or more second CSI resources, wherein the one or more second CSI resources overlaps with the second time durations and does not overlap with the first time durations.
[0464] In one example, the valid CSI feedback comprises a channel quality indicator that is not an out of range value.
[0465] In one example, the method further comprises receiving a second downlink control command indicating deactivation of the second cell while the wireless device commutates via the second cell.
[0466] In one example, the method further comprises skipping communicating via the second cell at deactivating the second cell.
[0467] In one example, the method further comprises switching to the first cell before an end of a slot (or at a next slot of the slot), wherein the wireless device deactivates the second cell at the slot.
[0468] In one example, the downlink control command is a RRC signaling, MAC CE or DCI.
[0469] In one example, the wireless device completes the activation of the second cell based on the transmitting the CSI report.Docket No.25-1081 PCT
[0470] In one example, there is provided a method comprising receiving, by a wireless device, one or more configuration parameters indicating: a switching pattern indicating a primary cell is configured with a low-band carrier aggregation (LB-CA) based on a switching between the primary cell and a secondary cell. The switching pattern indicates first time durations are assigned to the primary cell and second time durations are assigned to the secondary cell. The configuration parameters) further indicate a medium access control (MAC) entity of the wireless device. The method further comprises, during second time durations, skip, for the primary cell, one or more of: instructing a physical layer entity of the wireless device to transmit a scheduling request (SR) on a physical uplink control channel (PUCCH) resource; incrementing a SR counter; starting a prohibit timer for the SR; delivering a configured uplink grant and an associated HARQ to a HARQ entity; instructing a HARQ process to trigger a new transmission or retransmission of the configured uplink grant; and reporting CSI on a PUCCH and semi-persistent CSI on a configured PUSCH.
[0471] In one example, the method further comprises, by the HARQ entity of the wireless device, generating a transmission for a transport block, during a time slot, based on one or more of: the time slot not overlapping with a measurement gap; the time slot not overlapping with the first time durations in response to the HARQ entity is for the secondary cell; and the time slot not overlapping with the second time durations in response to the HARQ entity is for the primary cell.
[0472] In one example, the MAC entity of the wireless device skips further one or more of: monitoring PDCCH for the MAC entity's RNTIs, in response to the monitoring PDCCH is via the primary cell; instructing the physical layer to receive transport block on the DL-SCH of the primary cell; indicating the presence of a configured downlink assignment via the primary cell and deliver the stored HARQ information to the HARQ entity for the primary cell; setting the HARQ Process ID to the HARQ Process ID associated with the PDSCH duration of a configured downlink assignment for the primary cell; and considering the NDI bit for the HARQ process corresponding to the PDSCH duration of a configured downlink assignment to have been toggled for the configured downlink assignment for the primary cell.
[0473] In one example, the method further comprises determining the PUCCH resource as invalid based on the PUCCH resource overlapping with the second time durations.
[0474] In one example, the method further comprises comparing determining a first PUCCH resource of the primary cell being valid based on the first PUCCH resource overlapping, in time, with the first time durations.
[0475] In one example, the wireless device drops a first SR transmission based on the first PUCCH resource being invalid, and the first SR transmission is on the first PUCCH resource.
[0476] In an example, a wireless device may transmit a first capability (e.g., unifiedJointTCI-multiMAC-CE, or unifiedSeparateTCI-multiMAC-CE) indicating that the wireless device supports unified TCI state operation with joint / separate DL / UL TCI update for intra- and inter-cell beam management with more than one MAC-CE activated joint / separate TCI states per CC with MAC CE and DCI based TCI state indication in DCI formats 1_1 and 1_2 with and without DL assignment. The first capability may indicate one or more of the following parameters.
[0477] A) a minimum beam application time (e.g., minBeamApplicationTime) indicates a minimum beam application time in Y symbols per subcarrier spacing.Docket No.25-1081 PCT
[0478] B) a maximum number of MAC CE activated joint TCI states per CC in a band (e.g., maxNumMAC-CE-PerCC): indicates a number of TCI states activated per CC in a band (e.g., a number of codepoints or a number of active TCI states by MAC CE).
[0479] C) a maximum number of MAC CE activated DL TCI state per CC (e.g., maxActivatedDL-TCIPerCC): indicates a number of DL TCI states activated per CC in a band (e.g., a number of codepoints or a number of active DL TCI states by MAC CE
[0480] C) a maximum number of MAC CE activated UL TCI state per CC (e.g., maxActivatedUL-TCIPerCC): indicates a number of UL TCI states activated perCC in a band (eg., a number of codepoints or a number of active UL TCI states by MAC CE.
[0481] In an example, the wireless device may indicate a second capability (e.g., unifiedJointTCI) indicating a support of a unified TCI state operation with joint DL / UL TCI update for intra-cell beam management. The second capability may indicate that the wireless device supports a) one MAC-CE activated joint TCI state per CC in a band; and b) TCI state indication for update and activation of MAC CE based TCI state indication for one active TCI state. The second capability may indicate a maximum number of configured joint TCI states per BWP per CC in a band (e.g., maxCon figured JointTC I) and / or a maximum number of MAC-CE activated joint TCI states across all CC(s) in a band (e.g., maxActivatedTCIAcrossCC). The wireless device may indicate the first capability conditioned to reporting the second capability (e.g., the second capability is a pre-requisite of the first capability).
[0482] In an example, the wireless device may indicate a third capability (e.g., unifiedJointTCI-ListSharingCA) indicating that the wireless device supports a reference BWP and / or serving cell index to indicate a reference TCI state list shared by multiple BWPs and / or multiple serving cells. The third capability may indicate a value (e.g., a maximum number) indicating a maximum number of configured joint TCI state lists across all BWPs and all serving cells in a band. The wireless device may support the second capability based on the wireless device supports the third capability. In the example, the wireless device may report the third capability for a band and / or for a band combination. In particular, if the. wireless device supports a low-band CA that is based on a switching (e.g., LB-CA with a switching) for a band combination comprising a first band and a second band, the wireless device may indicate the third capability for the band combination and / or for the firsthand and / or the second band. Alternatively, the wireless device may indicate / transmit a fourth capability indicating that the wireless device supports a serving cell index to indicate a reference TCI state list shared by multiple serving cells configured with the LB-CA with the switching. The fourth capability may be indicated for a band combination and / or per serving cell.
[0483] In an example, for the wireless device that indicates support the second capability and / or the first capability and / or the capability of a LB-CA with the switching, the wireless device may transmit a fifth capability (e.g., simultaneous beam application and a LB-CA switching) that indicates the wireless device is able to perform a beam application while the wireless device performs a carrier switching between serving cells configured with a LB-CA with a switching. The wireless device indicates the fifth capability, the second capability (and / or the first capability) and the capability of the LB-CA with the switching. The second capability (and / or the first capability) and the capability of theDocket No. 25-1081 PCTLB-CA with the switching may be pre-requisite capabilities of the fifth capability. The fifth capability may be transmitted for a band combination or for a serving cell or a band.
[0484] In an example, for the wireless device that indicates the capability of a LB-CA with the switching, the wireless device may transmit a sixth capability to a base station. The sixth capability may indicate that the wireless device supports a unified TCI framework independently for each serving cell when the serving cell is configured with a LB-CA with a switching. Alternatively, the sixth capability may indicate among one or more options for an unified TCI operation across a first cell and a second cell configured with the LB-CA with the switching.
[0485] A) Support unified TCI state operation with joint DL / UL TCI update for the first cell and the second cell respectively;
[0486] B) Support unified TCI state operation with joint DL / UL TCI state for the first cell and the second cell follows the unified TCI state of the first cell, where the first cell is a primary cell;
[0487] C) Not support a unified TCI state, where the wireless device is configured with a single TCI state for both the first cell and the second cell.
[0488] In an example, a wireless device maybe configured with a multi-PDSCH scheduling ora multi-PUSCH scheduling for a cell. For example, the wireless device may receive one or more configuration parameters comprising pusch-TimeDomainAllocationListForMulb'PUSCHIE for the multi-PUSCH scheduling of the cell, and / or pdsch-TimeDomainAllocationListForMultiPUSCH IE for the multi-PDSCH scheduling. An entry of the pusch-TimeDomainAllocationListForMultiPUSCH IE orpdsch-TimeDomainAllocationListForMultiPUSCH IE may indicate one or more time domain allocations where each of the one or more time domain allocations may indicate a starting symbol and a duration in a slot. The one or more time domain allocations may allocate contiguous and / or non-contiguous slots for the multi-PDSCH or the multi-PUSCH scheduling. A PUSCH-Config IE of an uplink BWP of the cell may comprise a parameter of availableSlotCounting for the multi-PUSCH scheduling. For example, the availableSlotCounting may indicate whether a PUSCH repetitions may be counted based on available slots or based on absolute slots (e.g., availableSlotCounting is disabled). If the availableSlotCounting is enabled (or set to ‘enabled’), the wireless device may determine PUSCH repetitions of the multi-PUSCH based on available slots. Otherwise, (e.g., availableSlotCounting is absent), the wireless device may determine PUSCH repetitions based on absolute slots regardless of whether slots are available for PUSCH transmission or not.
[0489] For example, when the wireless device is scheduled to transmit a transport block and no CSI report by a DCI or by a RAR UL grant or fallbackRAR UL grant, or the UE is scheduled to transmit a transport block and a CSI report(s) on PUSCH by a DCI, the 'Time domain resource assignment' field value m for the scheduled PUSCH on the serving cell of the DCI or the PUSCH time resource allocation field value m of the RAR UL grant or of the fallbackRAR UL grant provides a row index m + 1 to a resource allocation table. The wireless device may determine the resource allocation table based on a time domain resource allocation rule. The indexed row defines the slot offset K2, the start and length indicator SLIV, or directly the start symbol S and the allocation length L, the PUSCH mapping type, the number of slots used for TBS determination (if numberOfSIotsTBoMS is present in the resource allocation table), and the number ofDocket No.25-1081 PCTrepetitions (if numberOfRepetitions is present in the resource allocation table) to be applied in the PUSCH transmission. For example, when pusch-TimeDomainAllocationListForMultiPUSCH and / or pdsch-TimeDomainAllocationListForMultiPUSCH is configured (e.g., multi-PUSCH and / or multi-PDSCH are used), the numberOfRepetitions in a TDRA (TimeDomainAllocationList) list for the multi-PDSCH / PUSCH may indicate a repetition number for each PUSCH / PDSCH.
[0490] In an example, a wireless device may be configured with a transport block over multiple slot (TBoMS) (e.g., configured with numberOfSIotsTBoMS, N), the wireless device may be configured with a number of repetitions (e.g., numberOfRepetitions, K). The numberOfSIotsTBoMS may indicate a number of slots allocated for TB processing over multi-slot PUSCH (TBoMS) for DCI format 0_1 / 0_2. If a number of repetitions K is configured by numberOfRepetitions or numberOf RepetitionsExt, the base station may configure numberOfSIotsTBoMS (N) and K such that N*K 32. The base station may not configure the numberOfSlotsTBoMS-r17 simultaneously with the pusch-TimeDomainAllocationListForMuitiPUSCH-r16. In other words, the base station may not configure a multi-PUSCH with a TBoMS simultaneously. The base station may not configure numberOfSlotsTBoMS-r17 together with enhancedSkipUplinkTxDynamic or enbancedSkipUplinkTxCon figured with value true. The base station may not configure numberOfSIotsTBoMS with a LB-CA that is based on a switching or with a CS switching pattern. In other words, the wireless device may not be configured with a TBoMS and / or multi-PUSC H / multi-PDSC H for a cell if the cell is configured with a LB-CA with a switching or configured with a CS pattern for the cell.
[0491] In case, the base station may configure a TBoMS for the cell, that is configured with a LB-CA with a switching (e.g., based on a CS pattern) with a second cell, the wireless device may determine N * K consecutive slots, for a PUSCH transmission of a PUSCH repetition type A scheduled by DCI format 0_1 or 0_2, or 0_3 for paired spectrum, or for a PUSCH transmission of TB processing over multiple slots scheduled by DCI format 0_1 or 0_2, or 0_3 for paired spectrum, based on the TDRA information field value in the DCI format 0_1, 0_2 or 0_3, as follows:
[0492] A) Fora normal PUSCH transmission not scheduled by a RAR UL grant nor based on a TC-RNTI,
[0493] A-1) For a case when a first cell (e.g., PCell) and a second cell (e.g., SCell) is configured with a LB-CA switching pattern (or a CS pattern), the wireless device may determine N ■ K slots for a PUSCH transmission, of the first cell (e.g., PCell) (or the second cell (e.g., SCell)), of a PUSCH repetition type A scheduled by DCI format 0_1, 0_2 or 0_3 when AvailableSlotCounting is enabled and K>1, or for a PUSCH transmission of TB processing over multiple slots scheduled by DCI format 0_1, 0_2 or 0_3, based on the TDRA information field value in the DCI format 0_1, 0_2 or 0_3. A slot would not be counted in the number of N ■ K slots if at least one of the symbols indicated by the indexed row of the used resource allocation table in the slot overlaps with a slot assigned to the second cell (or the first cell) or overlaps with a switching latency / gap (e.g., LB-CA switching gap). For example, a N*K slots may start from slot n, and slots between slot [n, n + N*K] are all allocated to the first cell (or the second cell), each slot between slot [n, n+ N*K] are used for the PUSCH transmission. If one or more slots between slot [n, n + N*K] are allocated to the second cell (or the first cell), the transmission of the PUSCH may occur between [n, n + N*K + X] where X is determined by skipping the one or more slots (e.g, X is a number of the one or more slots). For example, if there is one or more second slotsDocket No.25-1081 PCTbetween slot [n, n+ N*K+X], where the one or more second slots are allocated to the first cell (or the second cell) but a resource scheduled for the PUSCH transmission in each slot, of the one or more second slots, overlaps with the LB-CA switching gap, the transmission of the PUSCH may occur between [n, n + N*K + X + Y] where Y is determined by skipping the one or more second slots (or Y is a number of the one or more second slots).
[0494] A-2) Otherwise (e.g., the first cell (or the second cell) is not configured with a LB-CA with a switching, the wireless device may determine consecutive N * K slots for the PUSCH transmission.
[0495] B) For a PUSCH transmission, via a first cell, scheduled by a RAR UL grant,
[0496] B-1) For a case when the first cell (e.g., PCell) and a second cell (e.g., SCell) is not configured with a LB-CA switching pattern (or a CS pattern) or a TC-RNTI is provided by higher layers (e.g., the DCI is CRC-scrambled with the TC-RNTI), the wireless device may determine N ■ K consecutive slots for a PUSCH transmission of a PUSCH repetition Type A scheduled by RAR UL grant, based on the TDRA information field value in the RAR UL grant.
[0497] B-2) For the case when a first cell (e.g., PCell) and a second cell (e.g., SCell) is configured with a LB-CA switching pattern (or a CS pattern) and a C-RNTI is provided by higher layers, the wireless device may determine based on one of the following options:
[0498] B-2- 1 ) the wireless device may determine N * K consecutive slots, and the wireless device may drop a PUSCH transmission on a slot if the slot is allocated to the second cell or the PUSCH transmission overlaps with a LB-CA switching gap.
[0499] B-2-2) the wireless device may determine M consecutive slots for N * K valid uplink slots, where M is determined as N * K + X + Y where X is determined based on a number of slots allocated to the second cell during the transmission of the PUSCH and Y is determined based on a number of overlapping with the LB-CA switching delay. A similar rule in A-1). Please refer the details in A-1). Additionally, availableSlotCounting may be configured for the PUSCH transmission scheduled by the RAR UL grant.
[0500] B-2-3) the wireless device may determine N * K consecutive slots, based on the TDRA field value in the RAR UL grant. The wireless device may ignore or may skip switching to the second cell during N * K consecutive slots or during the transmission of the PUSCH.
[0501] In an example, a wireless device may be configured with a list of DL-DataToUL-ACK, where each of the DL-DataToUL-ACK may indicate a value between [M 1, M2], For example, M1 may be 0, and M2 may be 15. For example, M1 may be -1 and M2 may be 14. For example, M1 may be 16 and M2 may be 32. Each value of the DL-DataToUL-ACK may indicate a timing I slot offset between a first slot indicating a last / latest slot of a PDSCH reception for a HARQ-ACK feedback and a second slot indicating a first / earliest slot of a PUCCH I PUSCH transmission comprising the HARQ-ACK feedback.
[0502] For example, if a value of the DL-DataToUL-ACK indicates an integer value between [0, 15], a gap between the first slot and the second cell ranges from 0 to 15 (e.g., a same slot or a gap between two slots is 15). For example, if the gap is k, the first slot is a slot index n, the second slot has a slot index n+k. In this case, a subcarrier spacing of a downlink BWP receiving the PDSCH is same as a subcarrier spacing an uplink BWP transmitting the PUSCH / PUSCH.Docket No. 25-1081 PCT
[0503] In an example, a wireless device may receive one or more configuration parameters indicating a LB-CA with a switching between a first cell (e.g., a primary cell) and a second cell (e.g., a secondary cell). The configuration parameters may indicate a semi-static switching pattern (e.g., a CS pattern, a LB-CA CS pattern, a TDM pattern, a CA switching pattern, etc.). The configuration parameters may indicate a list of timing offset values (e.g., DL-DataToUL-ACK) for HARQ-ACK feedbacks of PDSCH receptions via the second cell. In the example, the wireless device may transmit a PUCCH, comprising a HARQ-ACK feedback of the HARQ-ACK feedbacks of the PDSCH receptions via the second cell, via the first cell. In the example, a subcarrier spacing of the first cell and a subcarrier spacing of the second cell may be same.
[0504] The semi-static switching pattern may indicate a first plurality of time durations, wherein each time duration of the first plurality of time durations may comprise one or more consecutive slots and each of the one or more consecutive slots is assigned to the first cell. The switching pattern may indicate a second plurality of time durations, wherein each time duration of the second plurality of time durations may comprise one or more consecutive slots and each of the one or more consecutive slots is assigned to the second cell. In the specification, a time duration refers a time interval of the switching pattern. A time duration in some cases may refer a time slot. The time slot may comprise one or more slots. A slot may be determined based on a subcarrier spacing of the first cell or the second cell.
[0505] The wireless device may receive a DCI indicating / scheduling a downlink data (e.g., PDSCH) reception via the second cell, where an end of the downlink data reception is during a first slot. The first slot overlaps with the second plurality of time durations. The DCI may further indicate a timing offset for a HARQ-ACK feedback for the downlink data reception (e.g., PDSCH), wherein an uplink transmission, of the HARQ-ACK feedback, overlaps, in time, with a second slot. The second slot overlaps with the first plurality of time durations.
[0506] In the example, a number of slots of a time duration of the second plurality of time durations may be larger than M2 (e.g., a largest / maximum value configurable for the timing offset). Alternatively, the wireless device may determine M2 based on the number of slots. For example, the time duration (i.e., any time duration) of the second plurality of time durations is M3 (e.g., M3 > 16), the wireless device may determine M2 as M3-1. This may allow the timing offset (e.g., HARQ-ACK timing, PDSCH-to-HARQ-ACK_feedback timing indicator), starting after / from the first slot, to indicate the second slot overlapping with the first plurality of time durations. When the wireless device is configured with the LB-CA with the switching or the semi-static switching pattern (e.g., the CS pattern), the wireless device may have a range of [M1, M2] such that M2 is determined based on a maximum / largest number of slots in a time duration of the second plurality of time durations. M1 may be determined based on M2 (e.g., M2 - 16). M2 may be M3 -1 or M3.
[0507] Alternatively, if the maximum / largest number of slots in a time duration of the second plurality of time durations is larger than 16, the wireless device may apply the timing offset at / after end of a time duration of the second plurality of time durations, instead of starting after / at the first slot. For example, the time duration comprises the first slot. In this case, the range of the timing offset may be [0, 15],Docket No. 25-1081 PCT
[0508] The first slot may indicate a last / latest slot of one or more slots of the downlink data reception. The second slot may indicate a first / earliest slot of one or more slots of the uplink transmission comprising the HARQ-ACK feedback.
[0509] In an example, a minimum number of slots in a time duration of the second plurality of time durations may be 2 or M (e.g., M > 2). Each of the second plurality of time durations may comprise a plurality of slots.
[0510] Example embodiments allow HARQ-ACK feedback timing is determined regardless of a maximum number of consecutive slots assigned to a secondary cell.
[0511] In an example, a wireless device may receive one or more configuration parameters indicating a LB-CA with a switching between a first cell (e.g., a primary cell) and a second cell (e.g., a secondary cell). The configuration parameters may indicate a semi-static switching pattern (e.g., a CS pattern, a LB-CA CS pattern, a TDM pattern, a CA switching pattern, etc.). The configuration parameters may indicate a CSI report configuration for the second cell, where the CSI report may be performed while the second cell is deactivated or before the second cell is activated.
[0512] The semi-static switching pattern may indicate a first plurality of time durations, wherein each time duration of the first plurality of time durations may comprise one or more consecutive slots and each of the one or more consecutive slots is assigned to the first cell. The switching pattern may indicate a second plurality of time durations, wherein each time duration of the second plurality of time durations may comprise one or more consecutive slots and each of the one or more consecutive slots is assigned to the second cell. In the specification, a time duration refers a time interval of the switching pattern. A time duration in some cases may refer a time slot. The time slot may comprise one or more slots. A slot may be determined based on a subcarrier spacing of the first cell or the second cell.
[0513] The wireless device may receive a downlink control command (e.g., RRC message(s), a MAC CE activating / deactivating secondary cell(s), a DCI activating / deactivating the second cell). The downlink control command may indicate an activation of the second cell. Based on the receiving the downlink control command, the wireless device may measure one or more channel state information (CSI) resources. The one or more CSI resources may overlap, in time, with the first plurality of time durations and / or the second plurality of time durations, during the secondary cell being activated based on the receiving the downlink control command. The wireless device may measure the one or more CSI resources during measurement occasions of the second cell. The measurement occasions may overlap with the first plurality of time durations and / or the second plurality of time durations. During the second cell is deactivated or during the second cell being activated or before the second cell is activated, the wireless device may not apply the semi-static switching pattern.
[0514] Based on the measuring, the wireless device may transmit a CSI report while the second cell is deactivated. The CSI report may comprise a valid CSI report. For example, the valid CSI report may comprise a CQI (channel quality indicator) that indicates non-OoR (out of range) value. In the example, the wireless device may transmit the CSI report during a first slot. The first slot may overlap with the first plurality of time durations and / or the second plurality of time durations. Based on the transmitting, the wireless device may complete the activation of the second cell.Docket No. 25-1081 PCT
[0515] The wireless device may start communicating via the second cell based on the semi-static switching pattern, at least one or more slots after the first slot. For example, the one or more slots may be determined based on an earliest available slot, of a time duration of the second plurality of time durations after one slot of the first slot. For example, the one or more slots may be determined one slot of the first slot, the one or more slots may be determined based on an earliest available slot, of a time duration of the second plurality of time durations after the first slot. In an example, a number of the one or more slots is one slot.
[0516] For example, the one or more slots may be determined one slot of the first slot, the one or more slots may be determined based on an earliest available slot, of a time duration of the second plurality of time durations si nce / at / starti ng from the first slot. For example, the one or more slots may be determined based on an earliest / next switching gap from the first cell to the second cell. For example, the wireless device transmits a PUCCH comprising the CSI report at a slot n, and a first / earliest switching gap occurs is slot n+k, the one or more slots may comprise slot(s) between slot n+1 and slot n+k-1. After performing the switching to the second cell at the slot n+k, the wireless device starts to apply the semi-static pattern (the CS pattern, the TDM pattern, the CA switching pattern). For example, after the wireless device completes the activation of the second cell, at an earliest I first switching gap from the first cell to the second cell, the wireless device starts switching to the first cell. A time of the completion of the activation of the second cell may be determined as
[0517] 1) an end of a slot where the wireless device transmits the PUCCH (ora PUSCH) comprising the valid CSI report;
[0518] 2) an end symbol of the transmission of the PUCCH or the PUSCH;
[0519] 3) X symbols / slots after the 1 ) or 2)
[0520] 4) A first slot of a next frame after 1) or 2) or 3): for example, a slot index = 0 in a next frame may be used to start to apply the CS pattern. The next frame (e.g., a frame is 10msec) occurs after the 1) or 2) or 3).
[0521] 5) A first slot of a next frame, after 1) or 2) or 3), with a SFN % 4 = 0: for example, based on the semi-static pattern has 40 msec periodicity, a SFN index is multiple of 4 may be used to start the semi-static pattern. For example, if a current frame is 22, a next frame becomes SFN = 24. When SFN of the next frame is 24, the first / earliest slot of the SFN = 24 will be used to start to apply the semi-static pattern (e.g., the CS pattern)
[0522] The communicating via the second cell may comprise measuring one or more second CSI resources. In the example, the one or more second CSI resources may overlap, in time, with the second time durations and does not overlap with the first time durations
[0523] The wireless device may receive a second downlink control command indicating deactivation of the second cell while the wireless device commutates via the second cell.
[0524] The wireless device may stop communicating via the second cell and / or may start skipping switching to the second cell upon deactivating the second cell.
[0525] For example, the wireless device may switch to the first cell before an end of a slot (or at a next slot of the slot), wherein the wireless device deactivates the second cell at the slot. The wireless device may stay on the first cellDocket No.25-1081 PCT(e.g., continue communicating via the first cell during slots overlapping with the first plurality of time durations and / or the second plurality of time durations after the switching).
[0526] This will enable the wireless device to switch between cells based on (pre-)configured switching gaps without performing additional switching gaps when the CS pattern is dynamically disabled or enabled (or applied or not applied).
[0527] In an example, a base station may configure a LB-CA with a switching for a cell. The base station may configure a cross-carrier scheduling for the cell, wherein a scheduling cell may be a second cell that is configured with the LB-CA with the switching between the cell and the second cell. The base station may not configure a UE processing capability 2 (e.g., fast processing capability) for PDSCH or PUSCH for the cell based on the base station configuring the cross-carrier scheduling, for the cell, via the second cell. In an example, the base station may not configure a cross-carrier scheduling for the cell or the second cell based on the LB-CA with the switching being configured for the cell or the second cell.
[0528] In the example, a wireless device may support a minimum processing time of a PDSCH or a PUSCH where the minimum processing time comprising a LB-CA switching gap.
[0529] In an example, a wireless device may receive one or more configuration parameters via a downlink control command (e.g., RRC, MAC CE, DCI). The configuration parameters may indicate a switching pattern indicating a primary cell is configured with a low-band carrier aggregation (LB-CA) based on a switching between the primary cell and a secondary cell. The switching pattern may indicate first time durations are assigned to the primary cell and second time durations are assigned to the secondary cell. A medium access control (MAC) entity of the wireless device, during second time durations, may skip, for the primary cell, one or more of the followings:
[0530] A) instruct a physical layer entity of the wireless device to transmit a scheduling request (SR) on a physical uplink control channel (PUCCH) resource;
[0531] B) increment a SR counter;
[0532] C) start a prohibit timer for the SR;
[0533] D) deliver a configured uplink grant and an associated HARQ to a HARQ entity;
[0534] E) instruct a HARQ process to trigger a new transmission or retransmission of the configured uplink grant; and
[0535] F) report CSI on a PUCCH and semi-persistent CSI on a configured PUSCH.
[0536] In the example, the HARQ entity of the wireless device may generate a transmission for a transport block, during a time slot, based on one or more of:
[0537] 1) the time slot not overlapping with a measurement gap;
[0538] 2) the time slot not overlapping with the first time durations in response to the HARQ entity is for the secondary cell; and
[0539] 3) the time slot not overlapping with the second time durations in response to the HARQ entity is for the first cell(e.g., the primary cell).
[0540] In the example, the MAC entity of the wireless device may skip further one or more of the followings:Docket No.25-1081 PCT
[0541] A) monitor PDCCH for the MAC entity's RNTIs, in response to the monitoring PDCCH is via the primary cell;
[0542] B) instruct the physical layer to receive transport block on the DL-SCH of the primary cell;
[0543] C) indicate the presence of a configured downlink assignment via the primary cell and deliver the stored HARQ information to the HARQ entity for the primary cell;
[0544] D) set the HARQ Process ID to the HARQ Process ID associated with the PDSCH duration of a configured downlink assignment for the primary cell; and
[0545] E) consider the NDI bit for the HARQ process corresponding to the PDSCH duration of a configured downlink assignment to have been toggled for the configured downlink assignment for the primary cell
[0546] In the example, the wireless device may determine the PUCCH resource as invalid based on the PUCCH resource overlapping with the second time durations. For example, the wireless device may determining a first PUCCH resource of the first / pri mary cell being valid based on the first PUCCH resource overlapping, in time, with the first time durations. The wireless device may drop a first SR transmission based on the first PUCCH resource being invalid, where the first SR transmission is on the first PUCCH resource.
[0547] Docket No.25-1081 PCTDocket No.25-1081 PCTDocket No.25-1081 PCTDocket No.25-1081 PCT
Claims
Docket No.25-1081 PCTCLAIMS1. A method comprising:receiving, by a wireless device, one or more configuration parameters indicating:a value, of beam application time, indicating when the wireless device is to apply a transmission configuration indicator (TCI) state, for a first cell, indicated by a downlink control command; anda carrier aggregation (CA) switching latency value indicating a latency for switching, for CA, between the first cell and a second cell;receiving the downlink control command indicating the TCI state for the first cell, wherein the TCI state is different from a current TCI state of the first cell;transmitting an uplink channel transmission with a positive feedback for the downlink control command; and starting to apply the indicated TCI state at a slot which is after at least a sum, of the value of beam application time and the CA switching latency value, from a last symbol from among symbols during which the uplink channel transmission is transmitted.
2. A method comprising:transmitting, by a wireless device, an uplink channel transmission corresponding to a downlink control command indicating a transmission configuration information (TCI) state for a first cell, wherein the TCI state is different from a current TCI state of the first cell; andapplying the indicated TCI state, based on a carrier aggregation (CA) switching pattern, for CA, between the first cell and a second cell.
3. The method of claim 2, further comprising receiving, by the wireless device, one or more configuration parameters indicating:a value, of beam application time, indicating when the wireless device is to the TCI, fora first cell, indicated by the downlink control command; and / ora CA switching latency value indicating a latency for switching, for the CA, between the first cell and the second cell.
4. The method of claim 3, wherein the indicated TCI state is applied during a slot which is based on the value of the beam application time and / or the CA switching latency value.
5. The method of claim 4, wherein the slot is after a last symbol from among symbols during which the uplink transmission is transmitted.
6. The method of claim 5, wherein the slot is after at least a sum, of the value of beam application time and the CA switching latency value, from the last symbol.
7. The method of any one of claims 4-6, further comprising starting to apply the indicated TCI state during the slot.
8. The method of any one of claims 2-7, further comprising receiving the downlink control command indicating the TCI state for the first cell, wherein the uplink channel transmission is transmitted with a positive feedback for the downlink control command.Docket No.25-1081 PCT9. The method of claim 8, wherein the positive feedback is for acknowledging the downlink control command.
10. The method of any one of claims 3-9, wherein the one or more configuration parameters indicate that the first cell is configured with a CA switching of the CA switching pattern, wherein the CA switching pattern indicates:a first plurality of time slots allocated to the first cell, during which the wireless device is configured to communicate in the first cell; anda second plurality of time slots allocated to a second cell, during which the wireless device is configured to communicate in the second cell.
11. The method of any one of claims 3-10, wherein the CA switching latency value indicates a latency for switching, for the CA and based on the CS switching pattern, between the first cell and the second cell.
12. The method of any one of claims 2-11, wherein the uplink channel transmission is either:a physical uplink control channel (PUCCH) transmission; ora physical uplink shared channel (PUSCH) transmission.
13. The method of any one of claims 8-11, wherein the positive feedback is a positive hybrid automatic repeat request acknowledgement (HARQ-ACK) feedback.
14. The method of any one of claims 2-13, wherein the applying the indicated TCI state comprises:receiving downlink data, based on the indicated TCI state; and / ortransmitting uplink data, based on the indicated TCI state.
15. The method of claim 14, wherein the downlink data is one of a PDCCH transmission, a PDSCH transmission, ora CSI-RS.
16. The method of claim 14 or 15, wherein the receiving the downlink data based on the indicated TCI state comprises receiving the downlink data, based on:spatial domain filter parameters of the indicated TCI state; orQCL assumption based on the indicated TCI state.
17. The method of any one of claims 14-16, wherein the uplink data is oneof a PUCCH transmission, a PUSCH transmission, or a SRS.
18. The method of any one of claims 2-17, wherein:the first cell is a primary cell (PCell);the second cell is a secondary cell (SCell);the uplink channel transmission is transmitted in the PCell; andthe CA switching latency value indicates a length of a switching latency for switching from the PCell to the SCell.
19. The method of any one of claims 10-18, further comprising, based on the beam application time overlapping with at least one slot in the second plurality of time slots allocated to the second cell:transmitting or receiving data scheduled in the second cell, during the beam application time; or dropping data scheduled to be received or transmitted, during the beam application time, in the second cell.Docket No.25-1081 PCT20. The method of claim 19, wherein, based on the beam application time overlapping with the at least one time slot in the second plurality of time slots allocated to the second cell, the data scheduled to be received or transmitted, during the beam application time, in the second cell is dropped.
21. The method of claim 19, wherein, based on the beam application time not overlapping with any of the second plurality of time slots allocated to the second cell, the data scheduled to be received or transmitted in the second cell is received or transmitted, during one or more time slots in the second plurality of time slots.
22. The method of any one of claims 3-21, wherein the value of the beam application time is larger than a sum of: a switching gap, in the CA switching pattern, for switching from the first cell to the second cell; and a value of a minimum beam application time that the wireless device supports.
23. The method of claim 22, further comprising transmitting a message indicating a capability of the wireless device, wherein the message indicates the value of the minimum beam application time that the wireless device supports.
24. A method comprising:receiving, by a wireless device, one or more configuration parameters indicating:that a first cell is configured with a carrier aggregation (CA) switching, wherein a switching pattern of the CA switching indicates a plurality of switching gaps for switching between the first cell and a second cell; anda number of symbols during which the wireless device is to apply a first beam, for the first cell, indicated by a downlink control information (DCI); andreceiving, during a beam failure recovery (BFR) procedure and via a physical downlink control channel (PDCCH), the DCI indicating the first beam for the first cell, wherein the first beam is different from a current beam of the first cell;skipping switching, from the first cell to the second cell, for the CA switching, during a switching gap in the plurality of switching gaps, based on the switching gap overlapping with a time duration of the number of symbols; andapplying, after the number of symbols from a last symbol of the PDCCH, the first beam indicated by the DCI, for the BFR procedure.
25. A method comprising:receiving, by a wireless device, one or more configuration parameters indicating that a first cell is configured with a carrier aggregation (CA) switching, wherein a switching pattern of the CA switching indicates a plurality of switching gaps for switching between the first cell and a second cell; andskipping switching, from the first cell to the second cell, for the CA switching, during a switching gap in the plurality of switching gaps, wherein:the switching gap overlaps with a time duration for applying a first beam, for the first cell, indicated by a downlink control information (DCI); andthe first beam is different from a current beam of the first cell.Docket No.25-1081 PCT26. The method of claim 25, wherein the switching is skipped during the switching gap, based on the switching gap overlapping with the time duration for applying the first beam.
27. The method of claim 25 or 26, wherein:the one or more configuration parameter indicate a number of symbols during which the wireless device is to apply the first beam, for the first cell, indicated by the DCI; andthe time duration for applying the first beam is a time duration of the number of symbols.
28. The method of any one of claims 25-27, further comprising receiving, during a beam failure recovery (BFR) procedure and via a physical downlink control channel (PDCCH), the DCI indicating the first beam for the first cell.
29. The method of claim 28, further comprising applying, after the time duration from a last symbol of the PDCCH, the first beam indicated by the DCI, for the BFR procedure.
30. A method comprising:receiving, by a wireless device, one or more configuration parameters comprising:a bitmap indicating a switching pattern for switching between a first cell and a second cell, wherein:a first bit value, for a first slot, in the bitmap indicates that the wireless device is configured to transmit and / or receive via the first cell in the first slot; anda second bit value, for a second slot, in the bitmap indicates that the wireless device is configured to receive via the second cell in the second slota first parameter indicating a first number of slots allocated for a transport block over a multi-slot physical uplink shared channel (PUSCH) fora DCI format; anda second parameter indicating a number of repetitions of the multi-slot PUSCH scheduled by the DCI format;receiving a DCI, in the DCI format, scheduling a first PUSCH transmission via the first cell; and transmitting repetitions of the first PUSCH transmission during a second number of slots, wherein the second number of slots is a product of the first number of slots and the number of repetitions.
31. The method of claim 30, wherein the bitmap indicates the first bit value for each of the first number of slots.
32. The method of claim 30 or 31, wherein:the first cell is a primary cell; andthe second cell is a secondary cell.
33. The method of any one of claims 30-32, wherein the first parameter indicates one of 1, 2, 4, and 8.
34. The method of any one of claims 30-33, wherein the second parameter indicates:the number of repetitions of the multi-slot PUSCH; and / orone of 1, 2, 3, 4, 7, 8, 12, and 16.
35. The method of any one of claims 31-34, wherein the one or more configuration parameters do not comprise a time domain allocation list for multiple PUSCH for a serving cell.Docket No.25-1081 PCT36. The method of any one of claims 31-35, comprising receiving one or more radio resource control (RRC) messages comprising the one or more configuration parameters.
37. The method of any one of claims 31-36, wherein the one or more configuration parameters comprises a parameter enabling available slot counting based on the one or more configuration parameter indicating the bitmap indicating the switching pattern.
38. The method of any one of claims 31-37, further comprising receiving a random access response (RAR) uplink grant scheduling a second PUSCH transmission.
39. The method of claim 38, wherein the switching pattern is ignored by the wireless device for the second PUSCH transmission.
40. The method of claim 38 or 39, wherein the wireless device does not switch to the second cell during the second PUSCH transmission based on ignoring the switching pattern.
41. An apparatus comprising:one or more processors; andmemory storing instructions that, when executed by the one or more processors, cause the apparatus to perform the method of any one of claims 1 -40.
42. A non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to perform the method of any one of claims 1 -40.
