Configuring uplink transmission configuration indicator list

Abstract

Aspects of the disclosure include methods and devices, including apparatuses, such as a UE, for wireless communication. The UE can be configured to receive an RRC configuration that configures UL TCI states for one or more serving cells. The UL TCI states can be configured by an IE for configuring PUSCH, PUCCH, SRS, PDSCH, and / or dedicated uplink BWP transmissions. The UE can also be configured to receive a DCI that indicates a UL TCI state of the configured UL TCI states for at least one UL transmission to at least one of the one or more serving cells. The UE can also be configured to transmit the at least one UL transmission based on the indicated UL TCI state. The UL transmission based on the indicated UL TCI state can include at least one of a PUSCH transmission, a configured grant PUSCH transmission, a PUCCH transmission, and a SRS transmission.

Description

Technical Field

[0001] In general, this disclosure relates to communication systems, and more specifically, to configuring an uplink (UL) transmission configuration indicator (TCI) list at a user equipment (UE). Background Technology

[0002] Wireless communication systems are widely deployed to provide a variety of telecommunications services such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems can use multiple access technologies that support communication with multiple users by sharing available system resources. Examples of these multiple access technologies include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single Carrier Frequency Division Multiple Access (SC-FDMA) systems, and Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems.

[0003] These multiple access technologies have been adopted in various telecommunications standards to provide a common protocol enabling different wireless devices to communicate at the city, national, regional, and even global levels. One example of a telecommunications standard is 5G New Radio (NR). 5G NR is part of the Continuous Mobile Broadband Evolution (CMB) initiative released by the 3rd Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the Internet of Things (IoT)), and other requirements. 5G NR includes services related to enhanced mobile broadband (eMBB), massive machine-type communications (mMTC), and ultra-reliable low-latency communications (URLLC). Some aspects of 5G NR can be based on the 4G Long Term Evolution (LTE) standard. There is a need to further enhance 5G NR technology. These improvements can also be applied to other multiple access technologies and telecommunications standards that use these technologies. Summary of the Invention

[0004] The following is a simplified summary of one or more aspects to provide a basic understanding of these aspects. This invention is not an exhaustive overview of all anticipated aspects, nor is it intended to identify key or essential elements of all aspects, nor to describe the scope of any or all aspects. Its sole purpose is to present some ideas of one or more aspects in a simplified form as a prelude to the more detailed description given later.

[0005] In some aspects of wireless communication, such as 5G NR, downlink (DL), and UL, separate TCI states can be used. For example, a first set of reference signals associated with M TCI states can provide quasi-co-location (QCL) information for UE-dedicated reception on at least the Physical Downlink Shared Channel (PDSCH) and on all control resource sets (CORESET) or subsets of CORESETs in the component carriers (CC). The QCL information can identify common characteristics between antenna ports. For example, the QCL information may indicate similar Doppler shift; Doppler spread; average delay; and delay spread (Type A), similar Doppler shift and Doppler spread (Type B), similar average delay and delay spread (Type C), or similar spatial receiver parameters for supporting beamforming (Type D). A second set of reference signals associated with N TCI states can provide a reference for determining at least all or a subset of common UL transmission filters (or filters) for all or a subset of the Physical Uplink Shared Channel (PUSCH) and Dedicated Physical Uplink Control Channel (PUCCH) resources in the CC based on dynamically granted / configured granted Physical Uplink Shared Channel (PUSCH). In some configurations, a common UL transmission filter can also be applied to probe reference signal (SRS) resources in one or more resource sets configured for antenna switching, codebook-based or non-codebook-based UL transmission.

[0006] In some configurations using carrier aggregation (CA), where the UE communicates with a set of one or more serving cells using multiple CCs, the DL TCI state (e.g., a DL TCI state list) for each specific CC (or each serving cell) can be configured in a PDSCH configuration (PDSCH-Config) information element (IE) (as an example of a DL config IE) and reused to identify the TCI state of the physical downlink control channel (PDCCH) and / or the channel state information reference signal (CSI-RS) for a specific CC. However, for CA UL transmissions on different CCs and / or with different serving cells, different UL transmission configurations can exist for different CCs or serving cells. For example, a specific CC (or serving cell) can have only one of the PUCCH, PUSCH, or SRS transmissions in its UL transmission, or any combination of PUCCH, PUSCH, configured to allow PUSCH and SRS transmissions. Given the different UL transmission configurations for different CCs and / or different serving cells, and the different types of UL transmissions that can be exchanged on different CCs associated with different serving cells, it may be beneficial to introduce a set of one or more UL TCI state configuration locations (e.g., in one or more information elements in Radio Resource Control (RRC)) where each of the set of one or more locations can be used to configure the UL TCI state (e.g., a UL TCI state list) for at least one type of UL transmission (e.g., PUCCH, PUSCH, configured permitted PUSCH, and SRS transmissions).

[0007] In this disclosure, methods, computer-readable media, and apparatus are provided. The apparatus may be a device at a UE. The device may be a processor and / or modem at the UE, or the UE itself. The UE may be configured to receive RRC configuration for configuring UL TCI states for one or more serving cells. The UE may also be configured to receive downlink control information (DCI) indicating a UL TCI state in a configured UL TCI state for at least one UL transmission to at least one of the one or more serving cells. The UE may also be configured to transmit the at least one UL transmission based on the indicated UL TCI state. UL transmissions based on the indicated UL TCI state may include at least one of PUSCH transmissions, configured permitted PUSCH transmissions, PUCCH transmissions, and SRS transmissions.

[0008] RRC configuration can be used to configure UL TCI status for one or more serving cells using any of the following configurations: (1) PUSCH configuration, (2) PUCCH configuration, (3) SRS configuration, (4) Dedicated Bandwidth Part (BWP) configuration, or (5) PDSCH configuration. The PUSCH configuration, PUCCH configuration, SRS configuration, BWP configuration, or PDSCH configuration can be included in the PUSCH configuration (PUSCH-Config)IE, PUCCH configuration (PUCCH-Config)IE, SRS configuration (SRS-Config)IE, Dedicated Uplink BWP (BWP-UplinkDedicated)IE, or PDSCH-Config IE, respectively. In some embodiments, the PUSCH configuration for configuring UL TCI status can exclude other PUSCH-related configuration information (e.g., a dummy PUSCH configuration sent to configure UL TCI status without configuring other aspects of PUSCH).

[0009] To achieve the foregoing and related objectives, one or more aspects include the features fully described below and specifically pointed out in the claims. The following description and drawings set forth certain illustrative features of one or more aspects in detail. However, these features indicate various methods in which the principles of the various aspects can be used, and this description is intended to include all such aspects and their equivalents. Attached Figure Description

[0010] Figure 1 This is a diagram illustrating an example of a wireless communication system and access network.

[0011] Figure 2A This is a diagram illustrating an example of the first frame of various aspects according to this disclosure.

[0012] Figure 2B This is a diagram illustrating an example of a DL channel within a subframe according to various aspects of this disclosure.

[0013] Figure 2C This is a diagram illustrating an example of the second frame according to various aspects of this disclosure.

[0014] Figure 2D This is a diagram illustrating an example of a UL channel within a subframe according to various aspects of this disclosure.

[0015] Figure 3 This is a diagram illustrating examples of base stations and user equipment (UEs) in an access network.

[0016] Figure 4 This is a call flow diagram illustrating the UL TCI status configuration and indication.

[0017] Figure 5 This is a call flow diagram illustrating the UL TCI status configuration via the PUSCH-Config IE in the RRC IE set.

[0018] Figure 6 This is a call flow diagram illustrating the UL TCI status configuration via the "dummy" PUSCH-ConfigIE in the RRC IE set.

[0019] Figure 7 This is a call flow diagram illustrating the UL TCI status configuration via the PUSCH-Config IE in the RRC IE set.

[0020] Figure 8 This is a call flow diagram illustrating the UL TCI status configuration via SRS-Config IE 800 in the RRC IE set.

[0021] Figure 9 This is a call flow diagram illustrating the UL TCI status configuration via the BWP-UplinkDedicated IE in the RRC IE set.

[0022] Figure 10 This is a call flow diagram illustrating the UL TCI status configuration via the PDSCH-Config IE in the RRC IE set.

[0023] Figure 11 This is a call flow diagram showing the UL TCI state configuration via PUSCH in the RRC IE set through the ConfiguredGrantConfig IE.

[0024] Figure 12 This is a flowchart of a wireless communication method.

[0025] Figure 13 This is a diagram illustrating an example of the hardware implementation used for the device. Detailed Implementation

[0026] The specific embodiments described below, in conjunction with the accompanying drawings, are intended as descriptions of various configurations and not as representations of the only configuration in which the concepts described herein are practiced. Specific details are included in the specific embodiments for the purpose of providing a comprehensive understanding of the various concepts. However, it will be apparent to those skilled in the art that these concepts can be implemented without using these specific details. In some cases, well-known structures and components are shown in block diagram form to avoid obscuring these concepts.

[0027] Several aspects of a telecommunications system will now be presented with reference to various apparatuses and methods. These apparatuses and methods will be described in detail below and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively, “elements”). These elements can be implemented using electronic hardware, computer software, or any combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0028] For example, an element, any part of an element, or any combination of elements can be implemented as a "processing system" including one or more processors. Examples of processors include: microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, system-on-a-chip (SoCs), baseband processors, field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functions described throughout this disclosure. One or more processors in a processing system can execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other names, software should be interpreted broadly as meaning instructions, instruction sets, code, code segments, program code, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc.

[0029] Accordingly, in one or more example embodiments, the described functionality can be implemented using hardware, software, or any combination thereof. If implemented in software, the functionality can be stored on or encoded as one or more instructions or code on a computer-readable medium. A computer-readable medium includes a computer storage medium. The storage medium can be any available medium accessible by a computer. By way of example, and not limitation, such a computer-readable medium can include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disc storage, magnetic disk storage, other magnetic storage devices, combinations of computer-readable media of the types described above, or any other medium that can be used to store computer-executable code in the form of instructions or data structures accessible by a computer.

[0030] Figure 1This diagram illustrates an example of a wireless communication system and access network 100. The wireless communication system (also referred to as a wireless wide area network (WWAN)) includes base station 102, UE 104, and evolved packet core (EPC) 160, as well as another core network 190 (e.g., a 5G core (5GC)). Base station 102 may include macro cells (high-power cellular base stations) and / or small cells (low-power cellular base stations). Macro cells include base stations. Small cells include femtocells, picocells, and microcells.

[0031] Base station 102 configured for 4G LTE (collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) and Terrestrial Radio Access Network (E-UTRAN)) can interface with EPC 160 via a first backhaul link 132 (e.g., S1 interface). Base station 102 configured for 5G / NR (collectively referred to as Next Generation RAN (NG-RAN)) can interface with core network 190 via a second backhaul link 184. Among other functions, base station 102 can perform one or more of the following functions: transmission of user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution of non-access stratum (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS), user and equipment tracking, RAN information management (RIM), paging, location, and delivery of warning messages. Base station 102 can communicate with each other directly or indirectly (e.g., via EPC 160 or core network 190) on third backhaul link 134 (e.g., X2 interface). First backhaul link 132, second backhaul link 184 and third backhaul link 134 can be wired or wireless.

[0032] Base station 102 can wirelessly communicate with UE 104. Each base station in base station 102 can provide communication coverage to a corresponding geographic coverage area 110. Overlapping geographic coverage areas 110 may exist. For example, small cell 102' may have a coverage area 110' that overlaps with the coverage areas 110 of one or more macro base stations 102. A network that includes both small cells and macro cells can be referred to as a heterogeneous network. The heterogeneous network may also include evolved home node B (eNB) (HeNB), which can provide services to a restricted group referred to as a closed subscriber group (CSG). The communication link between base station 102 and UE 104 may include: uplink (UL) (also referred to as reverse link) transmission from UE 104 to base station 102 and / or downlink (DL) (also referred to as forward link) transmission from base station 102 to UE 104. Communication link 120 may use multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link may use one or more carriers. Base station 102 / UE 104 may use up to Y MHz (e.g., 5, 10, 15, 20, 100, 400, etc.) of bandwidth allocated per carrier in carrier aggregation for transmission in each direction, up to a total of Yx MHz (x component carriers). Carriers may or may not be adjacent to each other. Carrier allocation may be asymmetric for DL ​​and UL (e.g., more or fewer carriers may be allocated to DL compared to UL). Component carriers may include primary component carriers and one or more secondary component carriers. The primary component carrier may be referred to as the primary cell (P cell) and the secondary component carrier may be referred to as the secondary cell (S cell).

[0033] Some UEs 104 can communicate with each other using device-to-device (D2D) communication link 158. D2D communication link 158 can use DL / UL WWAN spectrum. D2D communication link 158 can use one or more sidelink channels, such as the Physical Sidelink Broadcast Channel (PSBCH), Physical Sidelink Discovery Channel (PSDCH), Physical Sidelink Shared Channel (PSSCH), and Physical Sidelink Control Channel (PSCCH). D2D communication can be achieved through various wireless D2D communication systems, such as WiMedia, Bluetooth, ZigBee, Wi-Fi based on the IEEE 802.11 standard, LTE, or NR.

[0034] The wireless communication system may also include a Wi-Fi access point (AP) 150 that communicates with a Wi-Fi station (STA) 152 via a communication link 154 in, for example, a 5 GHz unlicensed spectrum. When communicating in the unlicensed spectrum, the STA 152 / AP 150 may perform a free channel assessment (CCA) before communication to determine whether the channel is available.

[0035] Small cell 102' can operate in licensed and / or unlicensed spectrum. When operating in unlicensed spectrum, small cell 102' can utilize NR and can use the same unlicensed spectrum (e.g., 5 GHz, etc.) used by Wi-Fi AP 150. Small cell 102' utilizing NR in unlicensed spectrum can improve coverage of the access network and / or increase the capacity of the access network.

[0036] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc., based on frequency / wavelength. In 5G NR, two initial operating frequency bands have been identified as the frequency range names FR1 (410MHz–7.125GHz) and FR2 (24.25GHz–52.6GHz). The frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Although a portion of FR1 is greater than 6GHz, in various documents and articles, FR1 is often referred to as the (interchangeable) "sub-6GHz" band. Similar naming issues sometimes arise for FR2, which in documents and articles is often (interchangeably) referred to as the "millimeter wave" band, although this is different from the Extremely High Frequency (EHF) band (30GHz–300GHz) band designated as "millimeter wave" by the International Telecommunication Union (ITU).

[0037] In light of the foregoing, unless otherwise expressly stated, it should be understood that the term "below 6 GHz" as used herein can broadly mean frequencies less than 6 GHz, within FR1, or including intermediate frequency band frequencies. Furthermore, unless otherwise expressly stated, it should be understood that the term "millimeter wave," as used herein, can broadly mean frequencies that can include intermediate frequency band frequencies, within FR2, or within the EHF band.

[0038] Whether it is a small cell 102' or a large cell (e.g., a macro base station), base station 102 may include and / or be referred to as an eNB, gNodeB (gNB), or another type of base station. Some base stations (e.g., gNB 180) may operate in the conventional sub-6 GHz spectrum at millimeter wave frequencies and / or near-millimeter wave frequencies to communicate with UE 104. When gNB 180 operates at millimeter wave or near-millimeter wave frequencies, gNB 180 may be referred to as a millimeter wave base station. Millimeter wave base station 180 may use beamforming 182 with UE 104 to compensate for this path loss and short distance. Base station 180 and UE 104 may each include multiple antennas, such as antenna elements, antenna panels, and / or antenna arrays, to facilitate beamforming.

[0039] Base station 180 may transmit beamformed signals to UE 104 in one or more transmit directions 182'. UE 104 may receive beamformed signals from base station 180 in one or more receive directions 182'. UE 104 may transmit beamformed signals to base station 180 in one or more transmit directions. Base station 180 may receive beamformed signals from UE 104 in one or more receive directions. Base station 180 / UE 104 may perform beam training to determine the optimal receive and transmit directions for each of base station 180 / UE 104. The transmit and receive directions of base station 180 may be the same or different. The transmit and receive directions of UE 104 may be the same or different.

[0040] EPC 160 may include: Mobility Management Entity (MME) 162, other MMEs 164, Serving Gateway 166, Multimedia Broadcast Multicast Service (MBMS) Gateway 168, Broadcast Multicast Service Center (BM-SC) 170, and Packet Data Network (PDN) Gateway 172. MME 162 can communicate with Home Subscriber Server (HSS) 174. MME 162 is the control node that handles signaling between UE 104 and EPC 160. Typically, MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are transmitted through Serving Gateway 166, which itself is connected to PDN Gateway 172. PDN Gateway 172 provides UE IP address allocation and other functions. PDN Gateway 172 and BM-SC 170 are connected to IP Service 176. IP Service 176 may include the Internet, intranet, IP Multimedia Subsystem (IMS), PS streaming service, and / or other IP services. The BM-SC 170 provides functions for MBMS user service provisioning and delivery. The BM-SC 170 can serve as an entry point for content provider MBMS transmissions, authorize and initiate MBMS bearer services in the Public Land Mobile Network (PLMN), and schedule MBMS transmissions. The MBMS gateway 168 can allocate MBMS services to base stations 102 belonging to the Multicast-Broadcast Single Frequency Network (MBSFN) area belonging to the Broadcast-Specific Service, and can be responsible for session management (start / end) and collecting billing information related to eMBMS.

[0041] The core network 190 may include Access and Mobility Management Functions (AMF) 192, other AMFs 193, Session Management Functions (SMF) 194, and User Plane Functions (UPF) 195. AMF 192 may communicate with Unified Data Management (UDM) 196. AMF 192 is the control node that handles signaling between UE 104 and the core network 190. Typically, AMF 192 provides QoS flow and session management. All user Internet Protocol (IP) packets are transmitted through UPF 195. UPF 195 provides UE IP address allocation and other functions. UPF 195 connects to IP services 197. IP services 197 may include the Internet, intranets, IP Multimedia Subsystem (IMS), Packet Switched (PS) Streaming (PSS) services, and / or other IP services.

[0042] Base stations may include and / or be referred to as gNB, Node B, eNB, access point, base transceiver, wireless base station, wireless transceiver, transceiver function, Basic Services Set (BSS), Extended Services Set (ESS), Transmitter Receiver Point (TRP), or some other suitable term. Base station 102 provides UE 104 with access to EPC 160 or core network 190. Examples of UE 104 include cellular phones, smartphones, Session Initiation Protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, GPS devices, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablets, smart devices, wearable devices, motor vehicles, electricity meters, air pumps, large or small kitchen appliances, medical devices, implants, sensors / actuators, displays, or any other similarly functional devices. Some UE 104s may be referred to as IoT devices (e.g., parking meters, air pumps, toasters, vehicles, heart monitors, etc.). UE 104 may also be referred to as mobile station, subscriber station, mobile unit, subscriber unit, radio unit, remote unit, mobile device, radio device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, radio terminal, remote terminal, handheld device, user agent, mobile client, client, or some other appropriate terminology.

[0043] Refer again Figure 1In some aspects, UE 104 may include a UL TCI state identification component 198, which can be configured to: receive an RRC configuration configuring a UL TCI state for one or more serving cells; receive a DCI indicating a ULTCI state in the configured UL TCI state for at least one UL transmission to at least one of the one or more serving cells; and transmit at least one UL transmission based on the indicated UL TCI state. Although the following description focuses on 5G NR, the concepts described herein can be applied to other similar areas, such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

[0044] Figure 2A Figure 200 shows an example of the first subframe within a 5G NR frame structure. Figure 2B Figure 230 shows an example of a DL channel within a 5G NR subframe. Figure 2C Figure 250 shows an example of a second subframe within a 5G NR frame structure. Figure 2D Figure 280 illustrates an example of a UL channel within a 5G NR subframe. The 5G / NR frame structure can be Frequency Division Duplex (FDD), in which subframes within a specific set of subcarriers (carrier system bandwidth) are dedicated to either DL or UL; or it can be Time Division Duplex (TDD), in which subframes within a specific set of subcarriers (carrier system bandwidth) are dedicated to both DL and UL. Figure 2A , 2C In the provided example, assuming the 5G NR frame structure is TDD, subframe 4 is configured with slot format 28 (primarily DL), where D is DL, U is UL, and F is flexible between DL / UL, and subframe 3 is configured with slot format 1 (for all UL). Although subframes 3 and 4 are shown with slot formats 1 and 28 respectively, any particular subframe can be configured with any of the various available slot formats 0-61. Slot formats 0 and 1 are both DL and UL, respectively. Other slot formats 2-61 include a mixture of DL, UL, and flexible symbols. The UE configures the slot format via the received Slot Format Indicator (SFI) (dynamically via DL Control Information (DCI) or semi-statically / statically via Radio Resource Control (RRC) signaling). Note that the following description also applies to 5G NR frame structures that are TDD.

[0045] Other wireless communication technologies may have different frame structures and / or different channels. A frame (10 ms) can be divided into 10 equal-sized subframes (1 ms). Each subframe may include one or more time slots. Subframes may also include micro-time slots, which may include 7, 4, or 2 symbols. Each time slot may include 7 or 14 symbols, depending on the time slot configuration. For time slot configuration 0, each time slot may include 14 symbols, while for time slot configuration 1, each time slot may include 7 symbols. These symbols on the DL can be Cyclic Prefix (CP) Orthogonal Frequency Division Multiplexing (OFDM) (CP-OFDM) symbols. The symbols on the UL can be CP-OFDM symbols (for high-throughput scenarios) or Discrete Fourier Transform (DFT) Extended OFDM (DFT-s-OFDM) symbols (also known as Single Carrier Frequency Division Multiple Access (SC-FDMA)) symbols (for power-constrained scenarios; limited to single-stream transmission). The number of time slots within a subframe is based on the time slot configuration and digital labeling. For slot configuration 0, different numerical designations μ0 to 4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For slot configuration 1, different numerical designations 0 to 2 allow 2, 4, and 8 slots per subframe, respectively. Therefore, for slot configuration 0 and numerical parameter μ, each slot has 14 symbols, and each subframe has 2 μ Each time slot. Subcarrier spacing and symbol length / duration are functions of the digital label. Subcarrier spacing can be equal to 2. μ *15kHz, where μ is a digital label from 0 to 4. Therefore, a digital parameter μ = 0 has a subcarrier spacing of 15kHz, and a digital parameter μ = 4 has a subcarrier spacing of 240kHz. The symbol length / duration is inversely proportional to the subcarrier spacing. Figures 2A-2D An example of slot configuration 0 is provided, where each slot has 14 symbols, and the digital label μ=2 has 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs. Within the frame set, there may be one or more different bandwidth portions (BWPs) of frequency division multiplexing (see [reference]). Figure 2B Each BWP can have specific numerical parameters.

[0046] A resource grid can be used to represent frame structure. Each time slot includes a resource block (RB) (also known as a physical RB (PRB)) extending for 12 consecutive subcarriers. The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0047] like Figure 2AAs shown, some of these REs carry reference (pilot) signals (RS) for the UE. RSs may include demodulation RS (DM-RS) (indicated as R for a specific configuration, but other DM-RS configurations are also possible) and CSI-RS for the UE. RSs may also include beam measurement RS (BRS), beam refinement RS (BRRS), and phase tracking RS (PT-RS).

[0048] Figure 2B Examples of individual DL channels within a subframe of a frame are shown. The Physical Downlink Control Channel (PDCCH) carries the DCI in one or more Control Channel Elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE comprising six RE Groups (REGs), each REG comprising 12 consecutive REs in the OFDM symbols of an RB. A PDCCH within a BWP can be referred to as a Control Resource Set (CORESET). The UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., a common search space, a UE-specific search space) during PDCCH monitoring on the CORESET, where the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs can be located at higher and / or lower frequencies on the channel bandwidth. The Primary Synchronization Signal (PSS) can be within symbol 2 of a specific subframe within the frame. The PSS is used by the UE 104 to determine subframe / symbol timing and physical layer identification. The Secondary Synchronization Signal (SSS) can be within symbol 4 of a specific subframe within the frame. The SSS is used by the UE to determine the Physical Layer Cell Identifier Group Number and radio frame timing. Based on the Physical Layer Identifier and the Physical Layer Cell Identifier Group Number, the UE can determine the Physical Cell Identifier (PCI). Based on the PCI, the UE can determine the location of the aforementioned DM-RS. The Physical Broadcast Channel (PBCH), carrying the Master Information Block (MIB), can be logically grouped with the PSS and SSS to form a Synchronization Signal (SS) / PBCH block (also known as an SS block (SSB)). The MIB provides multiple RBs in the system bandwidth and the System Frame Number (SFN). The Physical Downlink Shared Channel (PDSCH) carries user data, broadcast system information not transmitted via the PBCH (such as the System Information Block (SIB)), and paging messages.

[0049] like Figure 2CAs shown, some of these REs carry DM-RS for channel estimation at the base station (indicated as R for a specific configuration, but other DM-RS configurations are also possible). The UE can transmit DM-RS for PUCCH and DM-RS for PUSCH. PUSCH DM-RS can be transmitted in the first one or two symbols of the PUSCH. PUCCH DM-RS can be transmitted in different configurations depending on whether a short or long PUCCH is transmitted and depending on the specific PUCCH format used. The UE can transmit SRS. SRS can be transmitted in the last symbol of a subframe. SRS can have a comb structure, and the UE can transmit SRS on one of these combs. SRS can be used by the base station for channel quality estimation to enable frequency-dependent scheduling on the UL.

[0050] Figure 2D Examples of individual UL channels within a subframe of a frame are shown. The PUCCH can be positioned as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), precoding matrix indicators (PMI), rank indicators (RI), and hybrid automatic repeat request (HARQ) acknowledgment (ACK) (HARQ-ACK) information (ACK / NACK (NACK)) feedback. The PUCCH carries data and can also be used to carry buffer status reports (BSR), power headroom reports (PHR), and / or UCI.

[0051] Figure 3This is a block diagram of base station 310 communicating with UE 350 in the access network. In the DL, IP packets from EPC 160 can be provided to controller / processor 375. Controller / processor 375 implements Layer 3 and Layer 2 functions. Layer 3 includes the Radio Resource Control (RRC) layer, while Layer 2 includes the Serving Data Adaptation Protocol (SDAP) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, and Media Access Control (MAC) layer. The controller / processor 375 provides RRC layer functions associated with broadcasting system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-Radio Access Technology (RAT) mobility, and measurement configuration for UE measurement reports; PDCP layer functions associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functions associated with upper-layer packet data unit (PDU) transmission, error correction via ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs), resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functions associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs to transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority handling, and priority determination for logical channels.

[0052] Transmit (TX) processor 316 and receive (RX) processor 370 implement Layer 1 functions associated with various signal processing functions. Layer 1 (which includes the physical (PHY) layer) may include: error detection on the transport channel, forward error correction (FEC) encoding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. TX processor 316 processes the mapping to the signal constellation diagram based on various modulation schemes (e.g., binary phase shift keying / binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase shift keying / M-phase phase shift keying (M-PSK), M-order quadrature amplitude modulation (M-QAM)). The encoded and modulated symbols can then be divided into parallel streams. Each stream can then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., a pilot) in the time and / or frequency domains, and then combined using an inverse fast Fourier transform (IFFT) to generate a physical channel carrying a stream of time-domain OFDM symbols. The OFDM streams are spatially precoded to generate multiple spatial streams. Channel estimates from channel estimator 374 can be used to determine coding and modulation schemes and for spatial processing. The channel estimates can be obtained from the reference signal and / or channel condition feedback transmitted by UE 350. Each spatial stream can then be provided to a different antenna 320 via a corresponding transmitter 318TX. Each transmitter 318TX can use the corresponding spatial stream to modulate an RF carrier for transmission.

[0053] At UE 350, each receiver 354RX receives signals through its respective antenna 352. Each receiver 354RX recovers the information modulated onto the RF carrier and provides that information to the receive (RX) processor 356. The TX processor 368 and RX processor 356 implement Layer 1 functions associated with various signal processing functions. The RX processor 356 can perform spatial processing on the information to recover any spatial stream destined for UE 350. If multiple spatial streams are destined for UE 350, the RX processor 356 can combine them into a single OFDM symbol stream. The RX processor 356 then uses a Fast Fourier Transform (FFT) to transform the OFDM symbol stream from the time domain to the frequency domain. The frequency domain signal consists of a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, along with a reference signal, are recovered and demodulated by determining the most probable signal constellation points transmitted by base station 310. These soft decisions can be based on the channel estimate calculated by channel estimator 358. Then, the soft decision is decoded and deinterleaved to recover the data and control signals originally transmitted by base station 310 on the physical channel. The data and control signals are then provided to controller / processor 359, which implements layer 3 and layer 2 functions.

[0054] The controller / processor 359 may be associated with a memory 360 that stores program code and data. The memory 360 may be referred to as a computer-readable medium. In the UL, the controller / processor 359 provides demultiplexing, packet reassembly, decryption, header decompression, and control signal processing between transport and logical channels to recover IP packets from the UE 160. The controller / processor 359 is also responsible for error detection, supporting HARQ operation using ACK and / or NACK protocols.

[0055] Similar to the functions described in conjunction with DL transmissions performed by base station 310, controller / processor 359 provides: RRC layer functions associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functions associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functions associated with upper-layer PDU transmission, error correction via ARQ, concatenation, segmentation and assembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functions associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs to TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority processing, and priority determination of logical channels.

[0056] The TX processor 368 can use the channel estimate obtained by the channel estimator 358 from the reference signal or feedback sent by the base station 310 to select a suitable coding and modulation scheme, and to facilitate spatial processing. The spatial stream generated by the TX processor 368 can be provided to different antennas 352 via corresponding transmitters 354TX. Each transmitter 354TX can use the corresponding spatial stream to modulate the RF carrier for transmission.

[0057] At base station 310, UL transmissions are processed in a manner similar to that described in conjunction with the receiver function at UE 350. Each receiver 318RX receives signals through its respective antenna 320. Each receiver 318RX recovers the information modulated onto the RF carrier and provides that information to the RX processor 370.

[0058] The controller / processor 375 may be associated with a memory 376 that stores program code and data. The memory 376 may be referred to as a computer-readable medium. In the UL, the controller / processor 375 provides demultiplexing, packet reassembly, decryption, header decompression, and control signal processing between transport and logical channels to recover IP packets from the UE 350. IP packets from the controller / processor 375 can be provided to the EPC 160. The controller / processor 375 is also responsible for error detection, supporting HARQ operation using ACK and / or NACK protocols.

[0059] At least one of the TX processor 368, RX processor 356, and controller / processor 359 can be configured to perform coupling. Figure 1 198 aspects.

[0060] In some aspects of wireless communication, such as 5G NR, DL, and UL, separate TCI states can be used. For example, a first set of reference signals associated with M TCI states can provide QCL information for at least UE-dedicated reception on the PDSCH and on all CORESETs or subsets thereof in the CC. The QCL information can identify common characteristics between antenna ports. For example, the QCL information may indicate similar Doppler shift; Doppler spread; average delay; and delay spread (Type A), similar Doppler shift and Doppler spread (Type B), similar average delay and delay spread (Type C), or similar spatial receiver parameters for supporting beamforming (Type D). A second set of reference signals associated with N TCI states can provide a reference for determining a common UL transmission filter (or multiple filters) for at least all or a subset of dedicated PUCCH resources in the CC, based on dynamically granted / configured PUSCH. In some configurations, the common UL transmission filter can also be applied to SRS resources in one or more resource sets configured for antenna switching, codebook-based, or non-codebook-based UL transmission.

[0061] In some CA-based configurations, where the UE communicates with a set of one or more serving cells using multiple CCs, the DL TCI state (e.g., a DL TCI state list) for each specific CC (or each serving cell) can be configured in a PDSCH-Config IE (as an example of a DL config IE) and reused to identify the TCI state of the PDCCH and / or the CSI-RS of a specific CC. However, for CA UL transmissions on different CCs and / or with different serving cells, different UL transmission configurations can exist for different CCs or serving cells. For example, a specific CC (or serving cell) can have only one of the PUCCH, PUSCH, or SRS transmissions, or any combination of PUCCH, PUSCH, configured to allow PUSCH and SRS transmissions. Given the different UL transmission configurations for different CCs and / or different serving cells, and the different types of UL transmissions that can be exchanged on different CCs associated with different serving cells, it may be beneficial to introduce a set of one or more UL TCI state configuration locations (e.g., in one or more information elements in Radio Resource Control (RRC)) where each location in the set of one or more locations can be used to configure the UL TCI state (e.g., a list of UL TCI states) for at least one type of UL transmission (e.g., PUCCH, PUSCH, configured permitted PUSCH and SRS transmissions).

[0062] Figure 4 This is a call flowchart 400 illustrating the UL TCI status configuration and indication. (Example) Figure 4 As shown, base station (BS) 404 can communicate with UE 402. BS 404 may include one or more serving cells (e.g., a primary serving cell and a set of secondary serving cells). In other configurations (e.g., dual connectivity), the one or more serving cells may belong to multiple base stations. Figure 4 It is shown that UE 402 can receive RRC configuration 406 sent by BS 404, wherein RRC configuration 406 includes information for configuring UL TCI status for one or more serving cells of BS 404 (e.g., configuration from which a list of TCI statuses can indicate TCI statuses).

[0063] Upon receiving RRC configuration 406 for configuring UL TCI states, UE 402 may receive DCI 408, which may be transmitted by BS 404. DCI 408 may include (1) UL permission for at least one UL transmission and (2) an indication of one or more UL TCI states among the configured UL TCI states for at least one UL transmission. Alternatively, DCI 408 may include an indication of one or more UL TCI states among the configured UL TCI states for at least one UL transmission, and another DCI may include UL permission for at least one UL transmission to which the UL TCI state indicated by DCI 408 applies. Alternatively, DCI 408 may include an indication of one or more UL TCI states among the configured UL TCI states for at least one UL transmission, and other signaling, such as RRC or MAC-CE, may indicate UL permission for at least one UL transmission to which the UL TCI state indicated by DCI 408 applies. UE 402 can then transmit at least one UL transmission at 410 based on the indicated UL TCI state (e.g., the UL TCI state indicated in DCI 408). In the case of using CA, at least one UL transmission can be sent to the serving cell set of BS 404 via CC 412. BS 404 can then receive at least one UL transmission 410 via the serving cell.

[0064] As shown in the figure, UE 402 can interact with multiple serving cells indicated by the dashed lines (e.g., Figure 4The dashed line depicts a serving cell within BS 404 (or communicating with multiple BSs). It indicates a set of component transmissions of at least one UL transmission 410 that can be sent to the corresponding set of serving cells of BS 404. UE 402 can use at least one CC 412 to communicate with each serving cell. Each CC 412 can be configured with a UL TCI state (e.g., a list of TCI states from which TCI states can be indicated) or the UE can be configured with a UL TCI state that can be indicated for any CC 412 in the set of CC 412s used for communication with the set of serving cells (e.g., via RRC configuration 406). Each CC 412 can carry one or more UL transmissions (e.g., PUCCH, PUSCH, configured permitted PUSCH, or SRS transmissions). A set of UL TCI states can be indicated for each CC 412 (e.g., in a DCI associated with the CC 412, such as DCI 408 received from BS 404), and the set of UL TCI states can be applied to each type of UL transmission via CC 412. For example, the indicated UL TCI status can be applied to any or all of a PUSCH transmitted via a specific CC 412, a configured permitted PUSCH, PUCCH, and / or SRS transmission.

[0065] In some configurations, the UE (e.g., UE 402) may communicate with additional serving cells in an additional base station (e.g., a base station other than BS 404). For example, if dual connectivity is enabled, the UE may communicate with the additional base station (e.g., connect to the additional base station) to improve wireless communication. Each base station may be used to transmit a set of UL or DL ​​channels (e.g., PUSCH, PUCCH, PDSCH, PDCCH, or a combination of channels). In some configurations where the UE is connected to multiple base stations, RRC configuration 406 may be an RRC reconfiguration message sent to configure the UL TCI state of at least one additional serving cell of at least one additional BS. DCI 408 or additional DCI transmissions may be sent to indicate a set of UL TCI states associated with at least one additional serving cell. For example, the first and second DCIs received at UE 402 and associated with the first reference and the second base station, respectively, may include different TCI state indicators. Different TCI indicators may identify different TCI states, and different TCI states in turn identify different reference signals and QCL types. For example, two TCI states can identify QCL type D information to support beamforming, but one TCI state can indicate the QCL with a specific SSB, while the other TCI state can indicate the QCL with CSI-RS or a different SSB. UE 402 can then use the QCL information about the different reference signals to perform beamforming to reach the first and second base stations.

[0066] Figures 5-11 The diagram illustrates the set of operations for configuring UL TCI status using different RRC configuration information elements (IEs). Figure 5 This is a call flowchart 550 illustrating the UL TCI status configuration of PUSCH-Config IE 500 in the RRC configuration IE set. Call flowchart 550 includes... Figure 4 The elements of Figure 400. Figure 5 It is shown that UE 402 can receive RRC configuration 406 / 506 sent by BS 404. RRC configuration 406 / 506 may include PUSCH-Config IE 500, which includes UL TCI state configuration (e.g., TCI state configuration defined by ul-tci-StatesToAddModList and / or ul-tci-StatesToReleaseList 520). After configuring the UL TCI state based on PUSCH-Config IE 500 included in RRC configuration 406 / 506, UE 402 may receive DCI 408 sent by BS 404. DCI 408 may include (1) UL permission for at least one UL transmission and (2) an indication of one or more UL TCI states among the configured UL TCI states for at least one UL transmission. In another aspect, DCI 408 may include indications of one or more UL TCI states among configured UL TCI states for at least one UL transmission, and another DCI may include UL permission for at least one UL transmission to which the UL TCI state indicated by DCI 408 applies. Alternatively, DCI 408 may include indications of one or more UL TCI states among configured UL TCI states for at least one UL transmission, and other signaling, such as RRC or MAC-CE, may indicate UL permission for at least one UL transmission to which the UL TCI state indicated by DCI 408 applies.

[0067] Figure 5It is also shown that UE 402 can send at least one UL transmission 410, which includes one of the following: a PUSCH transmission; a configured permitted PUSCH transmission; a PUSCH and PUCCH transmission; a PUSCH and SRS transmission; or a PUSCH, PUCCH, and SRS transmission. At least one transmission 410 can be sent by UE 402 to a specific serving cell or a group of serving cells in BS 404 based on an indicated UL TCI state. The UL TCI state configured in the PUSCH-Config IE 500 for PUSCH transmission in the downlink bandwidth portion of the serving cell can also be applied to other uplink transmissions (if configured) in the same bandwidth portion of the same serving cell, such as configured permitted PUSCH transmissions, PUSCH transmissions, and / or SRS transmissions.

[0068] The PUSCH-Config IE 500 may include a set of fields 520, which may include the ul-tci-StatesToAddModList field and the ul-tci-StatesToReleaseList field. These fields may identify the TCI state used to provide a QCL relationship between an RS (e.g., CSI-RS, SSB, SRS) in a set of RSs (e.g., a set of CSI-RS, SSB, or SRS associated with an indicated UL TCI state) and the PUSCH, PUCCH, and / or SRS DMRS ports. The PUSCH-Config IE 500 may include additional fields for configuring other aspects of the PUSCH, such as data scrambling (dataScramblingIdentityPUSCH), whether the UE uses codebook-based or non-codebook-based transmission (txConfig), DMRS configuration (dmrs-UplinkForPUSCH-MappingTypeA and / or dmrs-UplinkForPUSCH-MappingTypeB), frequency hopping, resource allocation, and power control, etc. PUSCH-Config IE 500 is provided as a non-restrictive example of an uplink channel configuration IE in the currently defined standard, which may be renamed or replaced with an equivalent IE or other data structure in future versions.

[0069] Figure 6 This is a call flowchart 650 illustrating the UL TCI status configuration of a "dummy" PUSCH-Config IE 600 in the RRC configuration IE set. Call flowchart 650 includes... Figure 4 The elements of Figure 400. Figure 6It is shown that UE 402 can receive RRC configuration 406 / 606 sent by BS 404. RRC configuration 406 / 506 may include PUSCH-Config IE 600, which includes ULTCI state configuration (e.g., TCI state configuration defined by ul-tci-StatesToAddModList and / or ul-tci-StatesToReleaseList 620). After configuring the ULTCI state based on PUSCH-Config 600 included in RRC configuration 406 / 606, UE 402 may receive DCI 408 sent by BS 404. DCI 408 may include (1) UL permission for at least one UL transmission and (2) indication of one or more UL TCI states among the configured UL TCI states for at least one UL transmission. In one aspect, DCI 408 may include indications of one or more UL TCI states among configured UL TCI states for at least one UL transmission, and another DCI may include UL permission for at least one UL transmission to which the UL TCI state indicated by DCI 408 applies. In another aspect, DCI 408 may include indications of one or more UL TCI states among configured UL TCI states for at least one UL transmission, and other signaling, such as RRC or MAC-CE, may indicate UL permission for at least one UL transmission to which the UL TCI state indicated by DCI 408 applies.

[0070] Figure 6 It is also shown that UE 402 can send at least one UL transmission 410, which includes a PUCCH transmission and / or an SRS transmission. At least one UL transmission 410 can be sent by UE 402 to a specific serving cell or a group of serving cells in BS 404 based on an indicated UL TCI state. The UL TCI state configured in PUSCH-Config IE 600 in the bandwidth portion of the serving cell can be applied to other UL transmissions in the same bandwidth portion of the same serving cell (if configured), such as configured permitted PUSCH transmissions, PUCCH transmissions, and / or SRS transmissions.

[0071] The PUSCH-Config IE 600 can be used to configure UL TCI states for one or more serving cells. The "dummy" PUSCH-Config IE 600 can be used to configure UL TCI states for a specific CC that sends PUCCH and / or SRS transmissions without PUSCH transmissions. The PUSCH-Config IE 600 may include a set of fields 620, which may include the ul-tci-StatesToAddModList field and the ul-tci-StatesToReleaseList field. These fields can identify the TCI states used to provide a QCL relationship between an RS (e.g., a CSI-RS, SSB, or SRS) in a set of RSs (e.g., a set of CSI-RS, SSB, or SRS associated with the indicated UL TCI state) and the PUCCH and / or SRS DMRS ports. Additional fields for configuring other aspects of PUSCH transmissions can be excluded from the "dummy" PUSCH-Config IE 600. PUSCH-Config IE 600 is provided as a non-restrictive example of an uplink channel configuration IE in the currently defined standard, which may be renamed or replaced with an equivalent IE or other data structure in future versions.

[0072] Figure 7 This is a call flowchart 750 illustrating the UL TCI status configuration of PUCCH-Config IE 700 in the RRC configuration IE set. Call flowchart 750 includes... Figure 4 The elements of Figure 400. Figure 7It is shown that UE 402 can receive RRC configuration 406 / 706 sent by BS 404. RRC configuration 406 / 706 may include PUCCH-Config IE 700, which includes UL TCI state configuration (e.g., TCI state configuration defined by ul-tci-StatesToAddModList and / or ul-tci-StatesToReleaseList 720). After configuring the UL TCI state based on PUCCH-Config IE 700 included in RRC configuration 406 / 706, UE 402 may receive DCI 408 sent by BS 404. DCI 408 may include (1) UL permission for at least one UL transmission and (2) an indication of one or more ULTCI states among the configured UL TCI states for at least one UL transmission. In another aspect, DCI 408 may include indications of one or more UL TCI states among configured UL TCI states for at least one UL transmission, and another DCI may include UL permission for at least one UL transmission to which the UL TCI state indicated by DCI 408 applies. Alternatively, DCI 408 may include indications of one or more UL TCI states among configured UL TCI states for at least one UL transmission, and other signaling, such as RRC or MAC-CE, may indicate UL permission for at least one UL transmission to which the UL TCI state indicated by DCI 408 applies.

[0073] Figure 7 It is also shown that UE 402 can send at least one UL transmission 410, which includes one of the following: a PUCCH transmission; a PUCCH and a configured permitted PUSCH transmission; a PUCCH and a PUSCH transmission; a PUCCH and an SRS transmission; or a PUSCH, PUCCH, and SRS transmission. At least one UL transmission 410 can be sent by UE 402 to a specific serving cell or a group of serving cells in BS 404 based on an indicated UL TCI state. The UL TCI state configured in the PUCCH-Config IE 700 for PUCCH transmissions in the bandwidth portion of the serving cell can also be applied to other uplink transmissions in the same bandwidth portion of the same serving cell (if configured), such as configured permitted PUSCH transmissions, PUSCH transmissions, and / or SRS transmissions.

[0074] The PUCCH-Config IE 700 can be used to configure UL TCI states for one or more serving cells. The PUCCH-Config IE 700 can also be used to configure UL TCI states for a specific CC through which PUCCH transmissions are sent, with or without other UL channel transmissions. The PUCCH-Config IE 700 may include a set of fields 720, which may include the ul-tci-StatesToAddModList field and the ul-tci-StatesToReleaseList field. These fields can identify the TCI states for the QCL relationships between RSs (e.g., CSI-RS, SSB, SRS) in a set of RSs (e.g., a set of CSI-RS, SSB, or SRS associated with the indicated UL TCI state) and PUSCH, PUCCH, and / or SRS DMRS ports. The PUCCH-Config IE 700 may include additional fields for configuring other aspects of PUCCH transmissions. PUCCH-Config IE 700 is provided as a non-restrictive example of an uplink channel configuration IE in the currently defined standard, which may be renamed or replaced with an equivalent IE or other data structure in future versions.

[0075] Figure 8 This is a call flowchart 850 illustrating the UL TCI status configuration via SRS-Config IE 800 in the RRC IE set. Call flowchart 850 includes... Figure 4 The elements of Figure 400. Figure 8It is shown that UE 402 can receive RRC configuration 406 / 806 sent by BS 404. RRC configuration 406 / 806 may include SRS-Config IE 800, which includes UL TCI state configuration (e.g., TCI state configuration defined by ul-tci-StatesToAddModList and / or ul-tci-StatesToReleaseList 820). After configuring the UL TCI state based on SRS-Config IE 800 included in RRC configuration 406 / 806, UE 402 may receive DCI 408 sent by BS 404. DCI 408 may include (1) UL permission for at least one UL transmission and (2) an indication of one or more UL TCI states in the UL TCI state configuration for at least one UL transmission. In another aspect, DCI 408 may include indications of one or more UL TCI states among configured UL TCI states for at least one UL transmission, and another DCI may include UL permission for at least one UL transmission to which the UL TCI state indicated by DCI 408 applies. Alternatively, DCI 408 may include indications of one or more UL TCI states among configured UL TCI states for at least one UL transmission, and other signaling, such as RRC or MAC-CE, may indicate UL permission for at least one UL transmission to which the UL TCI state indicated by DCI 408 applies.

[0076] Figure 8 It is also shown that UE 402 can send at least one UL transmission 410, which includes one of the following: SRS transmission; SRS and PUSCH transmission; SRS and configured permitted PUSCH transmission; SRS and PUCCH transmission; or PUSCH, PUCCH and SRS transmission. At least one UL transmission 410 can be sent by UE 402 to a specific serving cell or a group of serving cells in BS 404 based on an indicated UL TCI state. The UL TCI state configured in the SRS-configIE 800 for SRS transmission in the bandwidth portion of the serving cell can also be applied to other uplink transmissions in the same bandwidth portion of the same serving cell (if configured), such as configured permitted PUSCH transmission, PUCCH transmission, and PUSCH transmission.

[0077] The SRS-Config IE 800 can be used to configure UL TCI states for one or more serving cells. The SRS-Config IE 800 can also be used to configure UL TCI states for a specific CC through which SRS transmissions are sent, with or without other UL channel transmissions. The SRS-Config IE 800 may include a set of fields 820, which may include the ul-tci-StatesToAddModList field and the ul-tci-StatesToReleaseList field. These fields may identify the TCI states used to provide a QCL relationship between an RS (e.g., CSI-RS, SSB, SRS) in a set of RSs (e.g., a set of CSI-RS, SSB, or SRS associated with the indicated UL TCI state) and the PUSCH, PUCCH, and / or SRS DMRS ports. Additional fields may be included in the SRS-Config IE 800 for configuring other aspects of SRS transmissions. SRS-Config IE 800 is provided as a non-restrictive example of an uplink channel configuration IE in the currently defined standard, which may be renamed or replaced with an equivalent IE or other data structure in future versions.

[0078] Figure 9 This is a call flowchart 950 illustrating the UL TCI status configuration of a BWP-UplinkDedicated IE 900 in the IE set via RRC configuration. Call flowchart 950 includes... Figure 4 The elements of Figure 400. Figure 9It is shown that UE 402 can receive RRC configuration 406 / 906 sent by BS 404. RRC configuration 406 / 906 may include BWP-UplinkDedicated IE 900, which includes UL TCI state configuration (e.g., TCI state configuration defined by ul-tci-StatesToAddModList and / or ul-tci-StatesToReleaseList 920). After configuring the UL TCI state based on BWP-UplinkDedicated IE 900 included in RRC configuration 406 / 906, UE 402 can receive DCI 408 sent by BS 404. DCI 408 may include (1) UL permission for at least one UL transmission and (2) an indication of one or more UL TCI states among the configured UL TCI states for at least one UL transmission. In another aspect, DCI 408 may include an indication of one or more UL TCI states among configured UL TCI states for at least one UL transmission, and another DCI may include UL permission for at least one UL transmission to which the UL TCI state indicated by DCI 408 applies. Alternatively, DCI 408 may include an indication of one or more ULTCI states among configured UL TCI states for at least one UL transmission, and other signaling, such as RRC or MAC-CE, may indicate UL permission for at least one UL transmission to which the UL TCI state indicated by DCI 408 applies.

[0079] Figure 9 It is also shown that UE 402 can send at least one UL transmission 410, which includes one of the following: a PUSCH transmission, a configured permitted PUSCH transmission, a PUCCH transmission, and an SRS transmission. At least one UL transmission 410 can be sent by UE 402 to a specific serving cell or a group of serving cells in BS 404 based on an indicated UL TCI state. The UL TCI state configured in the bandwidth portion of the serving cell (e.g., in BWP-UplinkDedicated IE 900) can be applied to all uplink transmissions (if configured) in the same bandwidth portion of the same serving cell, such as configured permitted PUSCH transmissions, PUCCH transmissions, PUSCH transmissions, and SRS transmissions.

[0080] Figure 900 illustrates a BWP-UplinkDedicated IE 900 that can be used to configure UL TCI states for one or more serving cells. The BWP-UplinkDedicated IE 900 may include a set of fields 920, which may include the ul-tci-StatesToAddModList field and the ul-tci-StatesToReleaseList field. These fields may identify the TCI states used to provide a QCL relationship between an RS (e.g., CSI-RS, SSB, SRS) in a set of RSs (e.g., a set of CSI-RS, SSB, or SRS associated with the indicated UL TCI state) and the PUSCH, PUCCH, and / or SRS DMRS ports. Additional fields may be included in the BWP-UplinkDedicated IE 900 for configuring other aspects of UL transport. The BWP-UplinkDedicated IE 900 is provided as a non-limiting example of configuring an IE for uplink channels in the currently defined standard, and may be renamed or replaced with an equivalent IE or other data structure in future versions.

[0081] Figure 10 This is a call flowchart 1050 illustrating the UL TCI status configuration of the PDSCH-Config IE 1000 in the RRC configuration IE set. Call flowchart 1050 includes... Figure 4 The elements of Figure 400. Figure 10It is shown that UE 402 can receive RRC configuration 406 / 1006 sent by BS 404. RRC configuration 406 / 1006 may include PDSCH-Config IE 1000, which includes UL TCI state configuration (e.g., TCI state configuration defined by ul-tci-StatesToAddModList and / or ul-tci-StatesToReleaseList 1020). After configuring the UL TCI state based on PDSCH-Config IE 1000 included in RRC configuration 406 / 1006, UE 402 may receive DCI 408 sent by BS 404. DCI 408 may include (1) UL permission for at least one UL transmission and (2) an indication of one or more UL TCI states among the configured UL TCI states for at least one UL transmission. In another aspect, DCI 408 may include an indication of one or more UL TCI states among configured UL TCI states for at least one UL transmission, and another DCI may include UL permission for at least one UL transmission to which the UL TCI state indicated by DCI 408 applies. Alternatively, DCI 408 may include an indication of one or more UL TCI states among configured UL TCI states for at least one UL transmission, and other signaling, such as RRC or MAC-CE, may indicate UL permission for at least one UL transmission to which the UL TCI state indicated by DCI 408 applies.

[0082] Figure 10 It is also shown that UE 402 can send at least one UL transmission 410, which includes at least one of the following: a PUSCH transmission; a configured permitted PUSCH transmission; a PUCCH transmission; and an SRS transmission. The UL TCI state configured in the PDSCH-config IE in the downlink bandwidth portion of the serving cell can be applied to uplink transmissions in the corresponding uplink bandwidth portion of the same serving cell (if configured), such as configured permitted PUSCH transmissions, PUSCH transmissions, PUCCH transmissions, and SRS transmissions. At least one UL transmission 410 can be sent by UE 402 to a specific serving cell or a group of serving cells of BS404 based on the indicated UL TCI state.

[0083] The PDSCH-Config IE 1000 can be used to configure UL TCI states for one or more serving cells. The PDSCH-Config IE 1000 may include a set of fields 1020, which may include the ul-tci-StatesToAddModList field and the ul-tci-StatesToReleaseList field. These fields identify the TCI states used to provide a QCL relationship between an RS (e.g., CSI-RS, SSB, SRS) in a set of RSs (e.g., a set of CSI-RS, SSB, or SRS associated with the indicated UL TCI state) and the PUSCH, PUCCH, and / or SRS DMRS ports. The PDSCH-Config IE 1000 may also include a set of fields 1030, which may include the tci-StatesToAddModList field and the tci-StatesToReleaseList field. These fields may identify the TCI states used to provide a QCL relationship between a DL RS (e.g., a CSI-RS or SSB) in a set of RSs (e.g., a CSI-RS or SSB associated with a TCI state) and the PDCCH DMRS port. The PDSCH-Config IE 1000 may include additional fields for configuring other aspects of PDSCH transmission. The PDSCH-Config IE 1000 is provided as a non-limiting example of configuring an IE for a downlink channel in the currently defined standard, and may be renamed or replaced with an equivalent IE or other data structure in future versions.

[0084] Figure 11 This is call flowchart 1150 illustrating the ULTCI status configuration via PUSCH ConfiguredGrantConfig IE 1100 in the RRC IE set. Call flowchart 1150 includes... Figure 4 The elements of Figure 400. Figure 11It is shown that UE402 can receive RRC configuration 406 / 1106 sent by BS 404. RRC configuration 406 / 1106 may include ConfiguredGrantConfig IE 1100, which includes UL TCI state configuration (e.g., TCI state configuration defined by ul-tci-StatesToAddModList and / or ul-tci-StatesToReleaseList 1120). After configuring the UL TCI state based on ConfiguredGrantConfig IE 1100 included in RRC configuration 406 / 1106, UE402 may receive DCI 408 sent by BS 404. DCI 408 may include (1) UL permission for at least one UL transmission and (2) an indication of one or more UL TCI states in the UL TCI state configuration for at least one UL transmission. On the other hand, DCI 408 may include indications of one or more UL TCI states among configured UL TCI states for at least one UL transmission, and another DCI may include UL permission for at least one UL transmission to which the UL TCI state indicated by DCI 408 applies. Alternatively, DCI 408 may include indications of one or more UL TCI states among configured UL TCI states for at least one UL transmission, and other signaling, such as RRC or MAC-CE, may indicate UL permission for at least one UL transmission to which the UL TCI state indicated by DCI 408 applies.

[0085] Figure 11 It is also shown that UE 402 can transmit at least one UL transmission 410, which includes at least one of the following: a configured permitted PUSCH transmission; a configured permitted PUSCH and PUCCH transmission; a configured permitted PUSCH and SRS transmission; and a configured permitted PUSCH, PUCCH, and SRS transmission. At least one UL transmission 410 can be transmitted by UE 402 to a specific serving cell or a group of serving cells in BS 404 based on an indicated UL TCI state. The UL TCI state configured in ConfiguredGrantConfig IE 1100 in the bandwidth portion of the serving cell can be applied to other UL transmissions (if configured) in the same bandwidth portion of the same serving cell, such as PUSCH transmissions, PUCCH transmissions, and / or SRS transmissions.

[0086] ConfiguredGrantConfig IE 1100 can be used to configure UL TCI states for one or more serving cells. ConfiguredGrantConfig IE 1100 may include a set of fields 1120, which may include the ul-tci-StatesToAddModList field and the ul-tci-StatesToReleaseList field. These fields may identify the TCI states used to provide a QCL relationship between an RS (e.g., CSI-RS, SSB, SRS) in a set of RSs (e.g., a set of CSI-RS, SSB, or SRS associated with the indicated UL TCI state) and the PUSCH, PUCCH, and / or SRS DMRS ports. ConfiguredGrantConfig IE 1100 may include additional fields for configuring other aspects of PUSCH transport. ConfiguredGrantConfig IE 1100 is provided as a non-limiting example of configuring an IE for uplink channels in the currently defined standard, and may be renamed or replaced with an equivalent IE or other data structure in future versions.

[0087] As mentioned above, regarding Figures 5-11 The RRC configuration for configuring the UL TCI status can include UL TCI information from any of the following: PUSCH-config IE 500, dummy PUSCH-config IE 600, PUCCH-Config IE 700, SRS-Config IE 800, BWP-UplinkDedicated IE 900, PDSCH-Config IE 1000, or ConfiguredGrantConfig IE 1100. These specific IEs are provided as examples only and can be generalized to IEs, or subsequent structures defined in later standards, for configuring uplink or downlink characteristics.

[0088] Figure 12 This is a flowchart 1200 of a wireless communication method. This method can be performed by a UE (e.g., UE 104; device 1302). At 1202, the UE can receive RRC configuration configuring the UL TCI state for one or more serving cells. For example, refer to... Figure 4-11 UE 402 can receive RRC configurations 406, 506, 606, 706, 806, 906, 1006, or 1106 for configuring the UL TCI state for one or more serving cells of BS 404. For example, 1202 can be... Figure 13 The UL TCI status recognition component 1340 is used for this purpose.

[0089] At 1204, the UE may receive DCI (or other control information) indicating the UL TCI state in the configured UL TCI state for at least one UL transmission to at least one of the one or more serving cells. For example, refer to Figures 4-11 UE 402 can receive DCI 408 indicating at least one UL TCI status (derived from UL TCI status configured by RRC configurations 406, 506, 606, 706, 806, 906, 1006, or 1106). For example, 1204 can be... Figure 13 The UL TCI status recognition component 1340 is used for this purpose.

[0090] Finally, at 1206, the UE can send at least one UL transmission based on the indicated UL TCI status. For example, refer to Figures 4-11 UE 402 can transmit at least one UL transmission 410 based on the UL TCI indicated in DCI 408. For example, 1206 can be transmitted by... Figure 13 The UL TCI status recognition component 1340 is used for this purpose.

[0091] In one configuration, the RRC configuration at 1202 may include a PUSCH configuration that configures the UL TCI status for one or more serving cells. Furthermore, at least one transmission at 1206 may include one of the following: a PUSCH transmission, a configured permitted PUSCH transmission, a PUCCH transmission, or an SRS transmission based on the indicated UL TCI status. For example, refer to... Figure 5 The RRC configuration 506 at 1202 may include a PUSCH configuration 500, which configures the UL TCI status for one or more serving cells of BS 404. Furthermore, at least one UL transmission 410 at 1206 may include one of the following: a PUSCH transmission based on the indicated UL TCI status, a configured permitted PUSCH transmission, a PUCCH transmission, or an SRS transmission.

[0092] In one configuration, at least one UL transmission at 1206 may include one of the following: a PUSCH transmission; a configured permitted PUSCH transmission; a PUSCH and PUCCH transmission; a PUSCH and SRS transmission; or a PUSCH, PUCCH, and SRS transmission based on an indicated UL TCI status. For example, refer to Figure 5At least one UL transmission 410 at 1206 may include one of the following: a PUSCH transmission; a configured permitted PUSCH transmission; a PUSCH and PUCCH transmission; a PUSCH and SRS transmission; or a PUSCH, PUCCH, and SRS transmission based on the indicated UL TCI status. In one configuration, such as Figure 5 As shown, the PUSCH configuration 500 in the RRC configuration 506 received by UE 402 at 1202 can be PUSCH-Config IE 500.

[0093] In one configuration, the RRC configuration received at 1202 may include a PUSCH configuration that configures the ULTCI state for one or more serving cells and excludes other PUSCH-related configuration information. Furthermore, at least one UL transmission at 1206 may include one of the following: an SRS transmission; a PUCCH transmission; or a PUCCH and SRS transmission based on the indicated UL TCI state. For example, refer to... Figure 6 The PUSCH configuration 600 in the RRC configuration 606 received by UE 402 at 1202 can be a "dummy" PUSCH-Config IE 600 that excludes other PUSCH-related configuration information. Furthermore, Figure 6 The illustration shows that transmission 410 at 1206 may include SRS transmission; PUCCH transmission; or PUCCH and SRS transmission based on the indicated UL TCI status.

[0094] In one configuration, the RRC configuration at 1202 may include a PUCCH configuration that configures the UL TCI state for one or more serving cells. Furthermore, at least one transmission at 1206 may include one of the following: a PUSCH transmission, a configured permitted PUSCH transmission, a PUCCH transmission, or an SRS transmission based on the indicated UL TCI state. For example, refer to... Figure 7 The RRC configuration 706 at 1202 may include a PUCCH configuration 700, which configures the UL TCI status for one or more serving cells of BS 404. Furthermore, at least one UL transmission 410 at 1206 may include one of the following: a PUSCH transmission based on the indicated UL TCI status, a configured permitted PUSCH transmission, a PUCCH transmission, or an SRS transmission.

[0095] In one configuration, at least one UL transmission at 1206 may include one of the following: a PUCCH transmission; a PUCCH and a configured permitted PUSCH transmission; a PUSCH and a PUCCH transmission; a PUSCH and an SRS transmission; or a PUSCH, PUCCH, and SRS transmission based on the indicated UL TCI status. For example, refer to Figure 7 At least one UL transmission 410 at 1206 may include one of the following: a PUCCH transmission; a PUCCH and a configured permitted PUSCH transmission; a PUSCH and a PUCCH transmission; a PUSCH and an SRS transmission; or a PUSCH, PUCCH, and SRS transmission based on the indicated UL TCI status. In one configuration, such as Figure 7 As shown, the PUCCH configuration 700 in the RRC configuration 706 received by UE402 at 1202 can be PUCCH-Config IE 700.

[0096] In one configuration, the RRC configuration at 1202 may include an SRS configuration that configures the UL TCI status for one or more serving cells. Furthermore, at least one transmission at 1206 may include one of the following: a PUSCH transmission, a configured permitted PUSCH transmission, a PUCCH transmission, or an SRS transmission based on the indicated UL TCI status. For example, refer to... Figure 8 The RRC configuration 806 at 1202 may include SRS configuration 800, which configures the UL TCI status for one or more serving cells of BS 404. Furthermore, at least one UL transmission 410 at 1206 may include one of the following: a PUSCH transmission based on the indicated UL TCI status, a configured permitted PUSCH transmission, a PUCCH transmission, or an SRS transmission.

[0097] In one configuration, at least one UL transmission at 1206 may include one of the following: an SRS transmission; an SRS and PUSCH transmission; an SRS and configured permitted PUSCH transmission; an SRS and PUCCH transmission; or a PUSCH, PUCCH, and SRS transmission based on the indicated UL TCI status. For example, refer to Figure 8 At least one UL transmission 410 at 1206 may include one of the following: an SRS transmission; an SRS and PUSCH transmission; an SRS and configured permitted PUSCH transmission; an SRS and PUCCH transmission; or a PUSCH, PUCCH, and SRS transmission based on an indicated UL TCI status. In one configuration, such as Figure 8 As shown, the SRS configuration 800 in the RRC configuration 806 received by UE 402 at 1202 can be SRS-Config IE 800.

[0098] In one configuration, the RRC configuration at 1202 may include a dedicated BWP configuration for configuring the UL TCI status for one or more serving cells. Furthermore, at least one transmission at 1206 may include one of the following: a PUSCH transmission based on the indicated UL TCI status, a configured permitted PUSCH transmission, a PUCCH transmission, or an SRS transmission. For example, refer to... Figure 9 The RRC configuration 906 at 1202 may include a dedicated BWP configuration 900, which configures the UL TCI status for one or more serving cells of BS 404. In one configuration, such as Figure 9 As shown, the dedicated BWP configuration 900 in the RRC configuration 906 received by UE 402 at 1202 can be a dedicated BWP-UplinkDedicated IE 900.

[0099] In one configuration, the RRC configuration at 1202 may include a PDSCH configuration that configures the UL TCI status for one or more serving cells. Furthermore, at least one transmission at 1206 may include one of the following: a PUSCH transmission, a configured permitted PUSCH transmission, a PUCCH transmission, or an SRS transmission based on the indicated UL TCI status. For example, refer to... Figure 10 The RRC configuration 1006 at 1202 may include PDSCH configuration 1000, which configures the UL TCI status for one or more serving cells of BS 404. In one configuration, such as Figure 10 As shown, the PDSCH configuration 1000 in the RRC configuration 1006 received by UE 402 at 1202 can be a dedicated PDSCH-Config IE 1000.

[0100] In one configuration, the RRC configuration at 1202 may include a configured permitted PUSCH configuration that configures the UL TCI state for one or more serving cells. Furthermore, at least one transmission at 1206 may include one of the following: a PUSCH transmission based on the indicated UL TCI state, a configured permitted PUSCH transmission, a PUCCH transmission, or an SRS transmission. For example, refer to... Figure 11 The RRC configuration 1106 at 1202 may include a configured permitted PUSCH configuration 1100, which configures the UL TCI status for one or more serving cells. Furthermore, at least one UL transmission 410 at 1206 may include one of the following: a PUSCH transmission based on the indicated UL TCI status, a configured permitted PUSCH transmission, a PUCCH transmission, or an SRS transmission.

[0101] In one configuration, at least one UL transmission at 1206 may include one of the following: a configured permitted PUSCH transmission; a configured permitted PUSCH and PUCCH transmission; a configured permitted PUSCH and SRS transmission; or a configured permitted PUSCH, PUCCH, and SRS transmission based on an indicated ULTCI status. For example, refer to Figure 11 At least one UL transmission 410 at 1206 may include one of the following: a configured permitted PUSCH transmission; a configured permitted PUSCH and PUCCH transmission; a configured permitted PUSCH and SRS transmission; or a configured permitted PUSCH, PUCCH, and SRS transmission based on an indicated UL TCI status. In one configuration, such as Figure 11 As shown, the PUSCH configuration 1100 in the RRC configuration 1106 received by UE 402 at 1202 can be ConfiguredGrantConfig IE 1100.

[0102] Figure 13Figure 1300 illustrates an example of a hardware implementation of device 1302. Device 1302 is a UE and includes a cellular baseband processor 1304 (also referred to as a modem) coupled to a cellular RF transceiver 1322 and one or more Subscriber Identity Module (SIM) cards 1320, an application processor 1306 coupled to a Secure Digital Card (SD) card 1308 and a screen 1310, a Bluetooth module 1312, a Wireless Local Area Network (WLAN) module 1314, a Global Positioning System (GPS) module 1316, and a power supply 1318. The cellular baseband processor 1304 communicates with UE 104 and / or BS 102 / 180 via the cellular RF transceiver 1322. The cellular baseband processor 1304 may include computer-readable media / memory. The computer-readable media / memory may be non-transitory. The cellular baseband processor 1304 is responsible for general processing, including executing software stored on the computer-readable media / memory. When executed by the cellular baseband processor 1304, the software causes the cellular baseband processor 1304 to perform the various functions described above. A computer-readable medium / memory may also be used to store data operated by the cellular baseband processor 1304 during software execution. The cellular baseband processor 1304 also includes a receiving component 1330, a communication manager 1332, and a transmitting component 1334. The communication manager 1332 includes one or more illustrated components. Components within the communication manager 1332 may be stored in a computer-readable medium / memory and / or configured as hardware within the cellular baseband processor 1304. The cellular baseband processor 1304 may be a component of the UE 350 and may include a memory 360 and / or at least one of a TX processor 368, an RX processor 356, and a controller / processor 359. In one configuration, the device 1302 may be a modem chip and include only the baseband processor 1304, and in another configuration, the device 1302 may be the entire UE (e.g., see...). Figure 3 (350) and includes additional modules of the device 1302 discussed above.

[0103] Communication manager 1332 includes UL TCI status identification component 1340, which is configured to: receive RRC configuration configuring UL TCI status for one or more serving cells; receive DCI indicating the UL TCI status in the configured UL TCI status for at least one UL transmission to at least one of the one or more serving cells; and transmit the at least one UL transmission based on the indicated UL TCI status, for example, as in combination with... Figure 12 As described in 1202, 1204, and 1206. The apparatus may include the functions described above. Figure 12 The flowchart shows the additional components of each block in the algorithm's block diagram. Therefore, the above... Figure 12Each block in the flowchart can be executed by a component and a device that may include one or more of those components. A component can be one or more hardware components specifically configured to execute the described process / algorithm, implemented by a processor configured to execute the process / algorithm, which is stored within a computer-readable medium and implemented by a processor or some combination thereof.

[0104] In one configuration, apparatus 1302, specifically cellular baseband processor 1304, includes a unit for receiving an RRC configuration that configures a UL TCI state for one or more serving cells. Apparatus 1302, specifically cellular baseband processor 1304, may further include a unit for receiving a DCI indicating a UL TCI state in the configured UL TCI state for at least one UL transmission to at least one of the one or more serving cells. Apparatus 1302, specifically cellular baseband processor 1304, may further include a unit for transmitting the at least one UL transmission based on the indicated UL TCI state. The aforementioned units may be one or more of the aforementioned components of apparatus 1302 configured to perform the functions described by the aforementioned units. As described above, apparatus 1302 may include a TX processor 368, an RX processor 356, and a controller / processor 359. Therefore, in one configuration, the aforementioned units may be the TX processor 368, the RX processor 356, and the controller / processor 359 configured to perform the functions described by the aforementioned units.

[0105] In some aspects of wireless communication, such as 5G NR, DL, and UL, separate TCI states can be used. For example, a first set of reference signals associated with M TCI states can provide QCL information for at least UE-dedicated reception on the PDSCH and on all CORESETs or subsets thereof in the CC. The QCL information can identify common characteristics between antenna ports. For example, the QCL information may indicate similar Doppler shift; Doppler spread; average delay; and delay spread (Type A), similar Doppler shift and Doppler spread (Type B), similar average delay and delay spread (Type C), or similar spatial receiver parameters for supporting beamforming (Type D). A second set of reference signals associated with N TCI states can provide a reference for determining a common UL transmission filter (or multiple filters) for at least all or a subset of dedicated PUCCH resources in the CC, based on dynamically granted / configured PUSCH. In some configurations, the common UL transmission filter can also be applied to SRS resources in one or more resource sets configured for antenna switching, codebook-based, or non-codebook-based UL transmission.

[0106] In some CA-based configurations, where the UE communicates with a set of one or more serving cells using multiple CCs, the DL TCI state (e.g., a DL TCI state list) for each specific CC (or each serving cell) can be configured in a PDSCH-Config IE (as an example of a DL config IE) and reused to identify the TCI state of the PDCCH and / or the CSI-RS of a specific CC. However, for CA UL transmissions on different CCs and / or with different serving cells, different UL transmission configurations can exist for different CCs or serving cells. For example, a specific CC (or serving cell) can have only one of the PUCCH, PUSCH, or SRS transmissions, or any combination of PUCCH, PUSCH, configured to allow PUSCH and SRS transmissions. Given the different UL transport configurations for different CCs and / or different serving cells, and the different types of UL transports that can be exchanged on different CCs associated with different serving cells, it may be beneficial to introduce a set of one or more UL TCI state configuration locations (e.g., in one or more information elements in Radio Resource Control (RRC)), wherein each of the set of one or more locations can be used to configure the UL TCI state (e.g., a UL TCI state list) for at least one type of UL transport (e.g., PUCCH, PUSCH, configured permitted PUSCH, and SRS transport). Multiple locations in which the UL TCI state configuration can be set (e.g., RRC IEs) may be beneficial for allowing case-specific signaling (i.e., using a specific RRC IE to configure the UL TCI state on a CC that only carries one of the PUSCH, PUCCH, or SRS transports).

[0107] It should be understood that the specific order or hierarchy of the blocks in the disclosed process / flowcharts is illustrative of the exemplary methods. It should be understood that the specific order or hierarchy of the blocks in these process / flowcharts can be rearranged according to design preferences. Furthermore, some blocks can be combined or omitted. The appended method claims present the elements of the various blocks in an exemplary order, and are not intended to limit one to the specific order or hierarchy presented.

[0108] The above description is provided to enable any person skilled in the art to implement the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Therefore, the claims are not intended to be limited to the aspects shown herein, but should be accorded the full scope consistent with the expression of the claims, wherein, unless expressly stated, an element referred to in the singular is not intended to mean “one and only one,” but rather “one or more.” Terms such as “if,” “when,” and “simultaneously” should be interpreted as meaning “under this condition,” rather than implying a direct temporal relationship or reaction. That is, these phrases, such as “when,” do not imply a response or immediate action during the occurrence of the action, but simply that the action will occur if the condition is met, but no specific or immediate time limit is required for the action to occur. The term “exemplary” as used herein means “serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” is not necessarily to be construed as preferred or superior to other aspects. Unless otherwise specifically stated, the term “some” refers to one or more. Combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" include any combination of A, B, and / or C, and may include multiple A, multiple B, or multiple C. Specifically, combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" may be only A, only A, only C, A and B, A and C, B and C, or A and B and C, wherein any such combination may include one or more members or some members of A, B, or C. All structures and functions known or to be known by one of ordinary skill in the art that are equivalent to the elements described throughout the various aspects of this disclosure are expressly incorporated herein by reference and are intended to be included by the claims. Furthermore, the disclosure herein is not intended to be offered to the public, whether or not it is expressly recited in the claims. The terms “module,” “mechanism,” “element,” “device,” etc., are not necessarily substitutes for the term “unit.” Therefore, unless the element is explicitly described using the phrase “unit for…”, it should not be interpreted as a unit plus a function.

[0109] The following aspects are illustrative only and may be combined with other aspects or teachings described herein without limitation.

[0110] Aspect 1 is a UE wireless communication method, comprising: receiving an RRC configuration configuring UL TCI states for one or more serving cells; receiving a DCI indicating a UL TCI state in a configured UL TCI state for at least one UL transmission to at least one of the one or more serving cells; and transmitting the at least one UL transmission based on the indicated UL TCI state.

[0111] Aspect 2 is the method according to aspect 1, wherein the RRC configuration includes configuring a PUSCH configuration for the UL TCI state of the one or more serving cells, and the transmission includes at least one of the following: a PUSCH transmission based on the indicated ULTCI state, a configured permitted PUSCH transmission, a PUCCH transmission, or an SRS transmission.

[0112] Aspect 3 is the method according to aspect 2, wherein the transmission includes one of the following: PUSCH transmission; configured permitted PUSCH transmission; PUSCH and PUCCH transmission; PUSCH and SRS transmission; or PUSCH, PUCCH and SRS transmission based on the indicated UL TCI status.

[0113] Aspect 4 is the method according to any one of Aspect 2 or 3, wherein the PUSCH configuration for configuring the UL TCI state of the one or more serving cells is received in a PUSCH-Config IE.

[0114] Aspect 5 is the method according to either aspect 2 or 4, wherein the RRC configuration, which includes configuring the PUSCH configuration for the UL TCI state of the one or more serving cells, does not include other PUSCH-related configuration information.

[0115] Aspect 6 is the method according to aspect 5, wherein the transmission includes one of the following: SRS transmission; PUCCH transmission; or PUCCH and SRS transmission based on the indicated UL TCI status.

[0116] Aspect 7 is the method according to aspect 1, wherein the RRC configuration includes configuring a PUCCH configuration for the UL TCI state of the one or more serving cells, and the transmission includes at least one of the following: a PUSCH transmission based on the indicated ULTCI state, a configured permitted PUSCH transmission, a PUCCH transmission, or an SRS transmission.

[0117] Aspect 8 is the method according to aspect 7, wherein the transmission includes one of the following: PUCCH transmission; PUCCH and configured permitted PUSCH transmission; PUSCH and PUCCH transmission; PUSCH and SRS transmission; or PUSCH, PUCCH and SRS transmission based on the configured UL TCI status.

[0118] Aspect 9 is the method according to any aspect of aspect 7 or 8, wherein the PUCCH configuration for configuring the UL TCI state of the one or more serving cells is received in a PUCCH-Config IE.

[0119] Aspect 10 is the method according to aspect 1, wherein the RRC configuration includes configuring SRS configuration of the UL TCI state for the one or more serving cells, and the transmission includes at least one of the following: PUSCH transmission based on the indicated ULTCI state, configured permitted PUSCH transmission, PUCCH transmission, or SRS transmission.

[0120] Aspect 11 is the method according to aspect 10, wherein the transmission includes one of the following: SRS transmission; SRS and PUSCH transmission; SRS and configured permitted PUSCH transmission; SRS and PUCCH transmission; or PUSCH, PUCCH and SRS transmission based on the indicated UL TCI status.

[0121] Aspect 12 is the method according to any aspect of aspect 10 or 11, wherein the SRS configuration for configuring the UL TCI state of the one or more serving cells is received in an SRS-Config IE.

[0122] Aspect 13 is the method according to aspect 1, wherein the RRC configuration includes a dedicated BWP configuration that configures the UL TCI state of the BWP for the one or more serving cells, and the transmission includes at least one of the following: PUSCH transmission on the BWP based on the indicated UL TCI state, configured permitted PUSCH transmission, PUCCH transmission, or SRS transmission.

[0123] Aspect 14 is the method according to aspect 13, wherein the dedicated BWP configuration for configuring the UL TCI state of the one or more serving cells is received in a BWP-UplinkDedicated IE.

[0124] Aspect 15 is the method according to aspect 1, wherein the RRC configuration includes configuring a PDSCH configuration of the UL TCI state for the one or more serving cells, and the transmission includes at least one of the following: a PUSCH transmission based on the indicated ULTCI state, a configured permitted PUSCH transmission, a PUCCH transmission, or an SRS transmission.

[0125] Aspect 16 is the method according to aspect 15, wherein the PDSCH configuration for configuring the UL TCI state of the one or more serving cells is received in a PDSCH-Config IE.

[0126] Aspect 17 is an apparatus for wireless communication, comprising at least one processor coupled to a memory and configured to implement the method described in any one of aspects 1 to 16.

[0127] Aspect 18 is an apparatus for wireless communication, including units for implementing the method described in any one of aspects 1 to 16.

[0128] Aspect 19 is a computer-readable medium storing computer-executable code, wherein the code, when executed by a processor, causes the processor to implement the methods described in any one of aspects 1 to 16.

Claims

1. A method for wireless communication of a user equipment (UE), comprising: Receive Radio Resource Control (RRC) configuration, which is used to configure the uplink (UL) Transport Configuration Indicator (TCI) state for one or more serving cells; Receive first downlink control information (DCI), the first DCI indicating the UL TCI state in the configured UL TCI state for at least one UL transmission to at least one of the one or more serving cells; and The at least one UL transmission is transmitted based on the indicated UL TCI state, wherein the at least one UL transmission includes at least one of a Physical Uplink Shared Channel (PUSCH) transmission, a configured permitted PUSCH transmission, a Physical Uplink Control Channel (PUCCH) transmission, or a Sounding Reference Signal (SRS) transmission based on the indicated UL TCI state, and wherein the RRC configuration includes a Dedicated Bandwidth Part (BWP) configuration for configuring the UL TCI state of the BWP of the one or more serving cells on which the at least one UL transmission is transmitted.

2. The method according to claim 1, wherein, The dedicated BWP configuration for configuring the ULTCI state for the one or more serving cells is received in the BWP-UplinkDedicated information element (IE).

3. The method according to claim 1 or 2, wherein, The DCI also includes UL permission for the at least one UL transmission.

4. The method of claim 1 or 2, further comprising receiving a second DCI, RRC signaling or media access control element (MAC-CE) authorized by the UL for the at least one UL transmission.

5. The method according to claim 1 or 2, wherein, The configured UL TCI status applies to all uplink transmissions on the BWP.

6. An apparatus for wireless communication, the apparatus being a first user equipment (UE), comprising: Memory; as well as At least one processor, coupled to the memory, is configured to: Receive Radio Resource Control (RRC) configuration, which is used to configure the uplink (UL) Transport Configuration Indicator (TCI) state for one or more serving cells; Receive first downlink control information (DCI), the first DCI indicating the UL TCI state in the configured UL TCI state for at least one UL transmission to at least one of the one or more serving cells; and The at least one UL transmission is transmitted based on the indicated UL TCI state, wherein the at least one UL transmission includes at least one of a Physical Uplink Shared Channel (PUSCH) transmission, a configured permitted PUSCH transmission, a Physical Uplink Control Channel (PUCCH) transmission, or a Sounding Reference Signal (SRS) transmission based on the indicated UL TCI state, and wherein the RRC configuration includes a Dedicated Bandwidth Part (BWP) configuration for configuring the UL TCI state of the BWP of the one or more serving cells on which the at least one UL transmission is transmitted.

7. The apparatus according to claim 6, wherein, The dedicated BWP configuration for configuring the ULTCI state for the one or more serving cells is received in the BWP-UplinkDedicated information element (IE).

8. The apparatus according to claim 6 or 7, wherein, The DCI also includes UL permission for the at least one UL transmission.

9. The apparatus of claim 6 or 7, further comprising receiving a second DCI, RRC signaling, or media access control element (MAC-CE) that includes UL permission for the at least one UL transmission.

10. An apparatus for wireless communication, comprising: A unit for receiving Radio Resource Control (RRC) configuration, the RRC configuration being used to configure the uplink (UL) Transport Configuration Indicator (TCI) state for one or more serving cells; A unit for receiving first downlink control information (DCI), the first DCI indicating the UL TCI state in a configured UL TCI state for at least one UL transmission to at least one of the one or more serving cells; and A unit for transmitting the at least one UL transmission based on an indicated UL TCI state, wherein the at least one UL transmission includes at least one of a Physical Uplink Shared Channel (PUSCH) transmission, a configured permitted PUSCH transmission, a Physical Uplink Control Channel (PUCCH) transmission, or a Sounding Reference Signal (SRS) transmission based on the indicated UL TCI state, and wherein the RRC configuration includes a Dedicated Bandwidth Part (BWP) configuration for configuring the UL TCI state of the BWP of the one or more serving cells on which the at least one UL transmission is transmitted.

11. A computer-readable medium storing computer-executable code, said code, when executed by a processor of a device at a user equipment (UE), causing the processor to: Receive Radio Resource Control (RRC) configuration, which is used to configure the uplink (UL) Transport Configuration Indicator (TCI) state for one or more serving cells; Receive first downlink control information (DCI), the first DCI indicating the UL TCI state in the configured UL TCI state for at least one UL transmission to at least one of the one or more serving cells; and The at least one UL transmission is sent based on the indicated UL TCI status, wherein, The at least one UL transmission includes at least one of a Physical Uplink Shared Channel (PUSCH) transmission based on the indicated UL TCI state, a configured permitted PUSCH transmission, a Physical Uplink Control Channel (PUCCH) transmission, or a Sounding Reference Signal (SRS) transmission, and wherein the RRC configuration includes a Dedicated Bandwidth Part (BWP) configuration for configuring the UL TCI state of the BWP of the one or more serving cells on which the at least one UL transmission is transmitted.

Images