Handover for single frequency network (SFN) physical uplink shared channel (PUSCH) communication scheme

Abstract

Various aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) can receive downlink control information (DCI) including an indication for transmitting a physical uplink shared channel (PUSCH) communication associated with the DCI using a single frequency network (SFN) communication scheme in which each layer of the PUSCH communication is simultaneously transmitted from multiple antenna modules of the UE. The UE can transmit the PUSCH communication according to the DCI. Numerous other aspects are described.

Description

Background Art

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to U.S. non-provisional patent application No. 17 / 813,770, filed on July 20, 2022, entitled "SWITCHING FOR SINGLE-FREQUENCY NETWORK (SFN) PHYSICAL UPLINK SHARED CHANNEL (PUSCH) COMMUNICATION SCHEME," which is hereby expressly incorporated herein by reference. Technical Field

[0003] Aspects of the present disclosure relate to wireless communications, and more particularly to techniques for switching for a single frequency network (SFN) physical uplink shared channel (PUSCH) communication scheme.

[0004] Related technologies

[0005] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, broadcasts or other similar types of services. These wireless communication systems may employ multiple-access technologies capable of supporting communication with multiple users by sharing available wireless communication system resources with those users.

[0006] Although wireless communication systems have made tremendous technical progress over the years, challenges still exist. For example, complex and dynamic environments can still attenuate or block signals between wireless transmitters and wireless receivers. Accordingly, there is a continued desire to improve the technical performance of wireless communication systems, including, for example: improving the speed and data carrying capacity of communications, improving the efficiency of using shared communication media, reducing the power used by transmitters and receivers when performing communications, improving the reliability of wireless communications, avoiding redundant transmission and / or reception and related processing, improving the coverage area of ​​wireless communications, increasing the number and types of devices that can access wireless communication systems, increasing the ability of different types of devices to communicate with each other, increasing the number and types of wireless communication media available for use, etc. Therefore, there is a need to further improve wireless communication systems to overcome the above-mentioned technical challenges and other challenges. Summary of the invention

[0007] One aspect provides a method for wireless communication by a user equipment (UE). The method includes receiving downlink control information (DCI), the DCI including an indication for sending a physical uplink shared channel (PUSCH) communication associated with the DCI using a single frequency network (SFN) communication scheme, in which each layer of the PUSCH communication is sent simultaneously using multiple antenna modules of the UE. The method also includes sending the PUSCH communication according to the DCI.

[0008] Another aspect provides a method for wireless communication by a network entity. The method includes sending a DCI, the DCI including an indication for sending a PUSCH communication associated with the DCI using an SFN communication scheme, in which each layer of the PUSCH communication is sent simultaneously using multiple antenna modules of the UE. The method also includes receiving the PUSCH communication according to the DCI.

[0009] Other aspects provide: an apparatus operable to, configured to, or otherwise adapted to perform any one or more of the foregoing methods and / or those described elsewhere herein; a non-transitory computer-readable medium comprising instructions that, when executed by a processor of the apparatus, cause the apparatus to perform the foregoing methods and those described elsewhere herein; a computer program product embodied on a computer-readable storage medium, comprising code for performing the foregoing methods and those described elsewhere herein; and / or an apparatus comprising components for performing the foregoing methods and those described elsewhere herein. By way of example, an apparatus may include a processing system, a device having a processing system, or a processing system cooperating through one or more networks.

[0010] For purposes of illustration, the following description and drawings set forth certain features. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] The accompanying drawings depict certain features of the various aspects described herein and should not be considered to limit the scope of the disclosure.

[0012] Figure 1 An example wireless communication network is depicted.

[0013] Figure 2 An example disaggregated base station architecture is depicted.

[0014] Figure 3 Aspects of an example base station and example user equipment are depicted.

[0015] Figure 4A , Figure 4B , Figure 4C and Figure 4DVarious example aspects of data structures for a wireless communication network are described.

[0016] Figure 5 An example logical architecture of a distributed radio access network (RAN) is illustrated.

[0017] Figure 6 is a diagram illustrating an example of multiple transmit-receive point (TRP) communications.

[0018] Figure 7 is a diagram illustrating an example associated with single frequency network (SFN) communications.

[0019] Figure 8 is a diagram illustrating an example of a SFN communication scheme for transmission.

[0020] Fig. 9 is a diagram illustrating an example of signaling associated with switching for a SFN communication scheme.

[0021] Fig.10 A method for wireless communication is described.

[0022] Fig.11 A method for wireless communication is described.

[0023] Fig.12 Aspects of an example communications device are depicted.

[0024] Fig.13 Aspects of an example communications device are depicted. DETAILED DESCRIPTION

[0025] Aspects of the present disclosure provide apparatus, methods, processing systems, and computer-readable media for switching for a single frequency network (SFN) physical uplink shared channel (PUSCH) communication scheme.

[0026] The UE may be able to use various communication schemes to send PUSCH. The communication scheme may indicate the configuration for sending PUSCH, such as the number of sounding reference signal (SRS) resource sets for sending PUSCH, the distribution of time, frequency or space resources for sending PUSCH, the number of transmit reception points (TRPs) to which PUSCH is to be sent, etc. Examples of communication schemes include space division multiplexing (SDM) communication schemes, frequency division multiplexing (FDM) communication schemes, time division multiplexing (TDM) communication schemes, single TRP communication schemes, and SFN communication schemes. PUSCH transmission is usually scheduled by downlink control information (DCI). User equipment (UE) that supports multiple communication schemes for PUSCH transmission can benefit from switching between different communication schemes, such as based on channel conditions, available resources, UE capabilities, etc. However, semi-static configuration of active communication schemes (such as via radio resource control (RRC) signaling) may not provide sufficient flexibility and adaptability for communication scheme switching, and may involve significant delays.

[0027] Some techniques described herein provide signaling associated with indicating a communication scheme for PUSCH transmission. For example, a UE may receive an indication (e.g., a DCI from a network entity) indicating a selected communication scheme. In some aspects, the indication may indicate whether an SFN communication scheme is used. If the indication indicates whether an SFN communication scheme is used, overhead may be reduced relative to indicating a selected communication scheme (e.g., in an FDM communication scheme, a TDM communication scheme, and / or an SDM communication scheme) because the UE may not need to indicate an order associated with an FDM communication scheme, a TDM communication scheme, or an SDM communication scheme, as described elsewhere herein. In some aspects, the indication may indicate a selected communication scheme (e.g., in an FDM communication scheme, a TDM communication scheme, an SDM communication scheme, a single TRP communication scheme, or an SFN communication scheme) that increases the flexibility of communication scheme switching.

[0028] In this manner, the delay associated with switching communication schemes is reduced relative to a semi-static configuration of the communication schemes.

[0029] Introduction to wireless communication networks

[0030] The techniques and methods described herein can be used in various wireless communication networks. Although various aspects may be described herein using terms commonly associated with 3G, 4G and / or 5G wireless technologies, various aspects of the present disclosure may also be applicable to other communication systems and standards not explicitly mentioned herein.

[0031] Figure 1 An example of a wireless communication network 100 is depicted in which various aspects described herein may be implemented.

[0032] In general, the wireless communication network 100 includes various network entities (alternatively, network elements or network nodes). A network entity is typically a communication device and / or a communication function performed by a communication device (e.g., a UE, a base station (BS), a component of a BS, a server, etc.). For example, various functions of a network and various devices associated with and interacting with the network may be considered network entities. In addition, the wireless communication network 100 includes ground aspects, such as ground-based network entities (e.g., BS 110), and non-ground aspects, such as satellites 140 and aircraft 145, which may include airborne network entities (e.g., one or more BSs) that can communicate with other network elements (e.g., ground BSs) and UEs.

[0033] In the depicted example, the wireless communication network 100 includes a BS 110, a UE 120, and one or more core networks (such as an evolved packet core (EPC) 160 and a 5G core (5GC) 190) that interoperate to provide communication services over various communication links (including wired and wireless links).

[0034] Figure 1 Various example UEs 120 are depicted, which may more generally include: a cellular phone, a smart phone, a Session Initiation Protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player, a camera, a game console, a tablet computer, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a healthcare device, an implant, a sensor / actuator, a display, an Internet of Things (IoT) device, an Always-On (AON) device, an edge processing device, or another similar device. UE 120 may also be more generally referred to as a mobile device, a wireless device, a wireless communication device, a station, a mobile station, a subscriber station, a mobile subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a remote device, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, or a handset, among others.

[0035] BS 110 may communicate wirelessly with (e.g., send signals to or receive signals from) UE 120 via communication link 170. Communication link 170 between BS 110 and UE 120 may carry uplink (UL) (also referred to as a reverse link) transmissions from UE 120 to BS 110 and / or downlink (DL) (also referred to as a forward link) transmissions from BS 110 to UE 120. In various aspects, communication link 170 may employ multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity.

[0036] BS 110 may generally include: NodeB, enhanced NodeB (eNB), next generation enhanced NodeB (ng-eNB), next generation NodeB (gNB or gNodeB), access point, base transceiver station, radio base station, radio transceiver, transceiver function, transmission and reception point, and / or other. BS 110 may provide communication coverage for corresponding geographic coverage areas 112, which may sometimes be referred to as cells and may overlap in some cases (e.g., a small cell provided by BS 110a may have a coverage area 112' that overlaps with the coverage area 112 of a macro cell). For example, the BS may provide communication coverage for macro cells (covering a relatively large geographic area), pico cells (covering a relatively small geographic area, such as a stadium), femto cells (covering a relatively small geographic area (e.g., a home)), and / or other types of cells.

[0037] Although BS110 is depicted as a single communication device in various aspects, BS110 can be implemented in various configurations. For example, one or more components of the base station may be decomposed, including a central unit (CU), one or more distributed units (DU), one or more radio units (RU), a near real-time (near RT) RAN intelligent controller (RIC) or a non-real-time (non-RT) RIC, to name a few examples. In another example, various aspects of the base station may be virtualized. More generally, a base station (e.g., BS110) may include components located at a single physical location or components located at various physical locations. In an example in which the base station includes components located at various physical locations, the various components may each perform a function so that the various components together implement functions similar to those of a base station located at a single physical location. In some aspects, a base station including components located at various physical locations may be referred to as a decomposed radio access network architecture (such as an open RAN (O-RAN) or virtualized RAN (VRAN) architecture). Figure 2 An example decomposed base station architecture is depicted and described.

[0038] Different BSs 110 within the wireless communication network 100 may also be configured to support different radio access technologies (such as 3G, 4G, and / or 5G). For example, a BS 110 configured for 4G LTE (collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) may interface with the EPC 160 via a first backhaul link 132 (e.g., an S1 interface). A BS 110 configured for 5G (e.g., 5G NR or Next Generation RAN (NG-RAN)) may interface with the 5GC 190 via a second backhaul link 184. The BSs 110 may communicate with each other directly or indirectly (e.g., via the EPC 160 or the 5GC 190) over a third backhaul link 134 (e.g., an X2 interface), which may be wired or wireless.

[0039] The wireless communication network 100 may subdivide the electromagnetic spectrum into various categories, frequency bands, channels, or other characteristics. In some aspects, the subdivision is provided based on wavelength and frequency, where frequency may also be referred to as a carrier, subcarrier, channel, tone, or subband. For example, 3GPP currently defines frequency range 1 (FR1) as including 410 MHz-7125 MHz, which is often (interchangeably) referred to as "below 6 GHz". Similarly, 3GPP currently defines frequency range 2 (FR2) as including 24,250 MHz-52,600 MHz, which is sometimes (interchangeably) referred to as "millimeter wave" ("mmW" or "mmWave"). A base station (e.g., a mmWave base station such as BS 110b) configured to communicate using mmWave or near mmWave radio bands may utilize beamforming (e.g., as shown by 182) with a UE (e.g., 120) to improve path loss and distance.

[0040] The communication link 170 between BS 110 and, for example, UE 120 may be through one or more carriers, which may have different bandwidths (e.g., 5 MHz, 10 MHz, 15 MHz, 20 MHz, 100 MHz, 400 MHz, and / or other bandwidths) and may be aggregated in various aspects. The carriers may or may not be adjacent to each other. In some examples, the allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL ​​compared to UL).

[0041] Communications using higher frequency bands may have higher path loss and shorter range than communications at lower frequencies. Accordingly, some base stations (e.g., Figure 1182 ′. BS 110b and UE 120 may each include multiple antennas, such as antenna elements, antenna panels, and / or antenna arrays, to facilitate beamforming. In some cases, BS 110b may transmit beamformed signals to UE 120 in one or more transmit directions 182 ′. UE 120 may receive beamformed signals from BS 110b in one or more receive directions 182 ″. UE 120 may also transmit beamformed signals to BS 110b in one or more transmit directions 182 ″. BS 110b may also receive beamformed signals from UE 120 in one or more receive directions 182 ′. BS 110b and UE 120 may then perform beam training to determine optimal receive and transmit directions for each of BS 110b and UE 120. It is worth noting that the transmission direction and the reception direction of BS 110b may be the same or different. Similarly, the transmission direction and the reception direction of UE 120 may be the same or different.

[0042] Wireless communication network 100 also includes Wi-Fi AP 150 that communicates with Wi-Fi station (STA) 152 via communication link 154 in, for example, the 2.4 GHz and / or 5 GHz unlicensed spectrum.

[0043] Certain UEs 120 may communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), a physical sidelink control channel (PSCCH), and / or a physical sidelink feedback channel (PSFCH).

[0044] The EPC 160 may include various functional components, including: a mobility management entity (MME) 161, other MMEs 162, a serving gateway 163, a multimedia broadcast multicast service (MBMS) gateway 164, a broadcast multicast service center (BM-SC) 165, and / or a packet data network (PDN) gateway 166, such as in the depicted example. The MME 161 may communicate with a home subscriber server (HSS) 167. The MME 161 is a control node that handles signaling between the UE 120 and the EPC 160. In general, the MME 161 provides bearer and connection management.

[0045] Generally, user Internet Protocol (IP) packets are delivered through a Serving Gateway 163, which itself is connected to a PDN Gateway 166. The PDN Gateway 166 provides UE IP address allocation and other functions. The PDN Gateway 166 and the BM-SC 165 are connected to IP Services 168, which may include, for example, the Internet, an Intranet, an IP Multimedia Subsystem (IMS), a Packet Switched (PS) streaming media service, and / or other IP services.

[0046] The BM-SC 165 may provide functionality for MBMS user service provisioning and delivery. The BM-SC 165 may serve as an entry point for content provider MBMS transmissions, may be used to authorize and initiate MBMS bearer services within a public land mobile network (PLMN), and / or may be used to schedule MBMS transmissions. The MBMS Gateway 164 may be used to distribute MBMS services to BSs 110 belonging to a multicast broadcast single frequency network (MBSFN) area that broadcasts a particular service, and / or may be responsible for session management (start / stop) and for collecting eMBMS-related billing information.

[0047] 5GC 190 may include various functional components, including: access and mobility management function (AMF) 191, other AMFs 192, session management functions (SMF) 193, and user plane functions (UPF) 194. AMF 191 may communicate with unified data management (UDM) 195.

[0048] AMF 191 is a control node that processes signaling between UE 120 and 5GC 190. AMF 191 provides, for example, Quality of Service (QoS) flow and session management.

[0049] IP packets are delivered through UPF 194, which is connected to IP services 196 and provides UE IP address allocation and other functions for 5GC 190. IP services 196 may include, for example, the Internet, intranet, IMS, PS streaming services, and / or other IP services.

[0050] In various aspects, a network entity or network node may be implemented as a converged base station, a decomposed base station, a component of a base station, an integrated access and backhaul (IAB) node, a relay node, a sidelink node, or a transmit receive point (TRP), to name a few examples.

[0051] Figure 2An example disaggregated base station 200 architecture is depicted. The disaggregated base station 200 architecture may include one or more central units (CUs) 210 that may communicate directly with a core network 220 via a backhaul link, or indirectly with the core network 220 through one or more disaggregated base station units, such as a near real-time (near-RT) RAN intelligent controller (RIC) 225 via an E2 link, or a non-real-time (non-RT) RIC 215 associated with a service management and orchestration (SMO) framework 205, or both. The CU 210 may communicate with one or more distributed units (DUs) 230 via respective midhaul links, such as an F1 interface. The DU 230 may communicate with one or more radio units (RUs) 240 via respective fronthaul links. The RU 240 may communicate with respective UEs 120 via one or more radio frequency (RF) access links. In some implementations, a UE 120 may be served simultaneously by multiple RUs 240.

[0052] Each of these units (e.g., CU 210, DU 230, RU 240, and near-RT RIC 225, non-RT RIC 215, and SMO framework 205) may include or be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to the communication interface of the unit may be configured to communicate with one or more of the other units via a transmission medium. For example, these units may include a wired interface configured to receive or send signals to one or more of the other units via a wired transmission medium. Additionally or alternatively, the unit may include a wireless interface that may include a receiver, transmitter, or transceiver (such as an RF transceiver) configured to receive or send signals or both to one or more of the other units on a wireless transmission medium.

[0053] In some aspects, CU 210 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may be implemented using an interface configured to communicate signals with other control functions hosted by CU 210. CU 210 may be configured to handle user plane functions (e.g., central unit-user plane (CU-UP)), control plane functions (e.g., central unit-control plane (CU-CP)), or a combination thereof. In some specific implementations, CU 210 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, CU 210 may be implemented to communicate with DU 230 for network control and signaling.

[0054] DU 230 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 240. In some aspects, DU 230 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) at least in part according to functional divisions such as those defined by the 3rd Generation Partnership Project (3GPP). In some aspects, DU 230 may also host one or more low PHY layers. Each layer (or module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by DU 230 or with control functions hosted by CU 210.

[0055] The lower layer functions may be implemented by one or more RUs 240. In some deployments, the RU 240 controlled by the DU 230 may correspond to a logical node that hosts RF processing functions or low PHY layer functions (such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, based at least in part on a functional split (such as a lower layer functional split). In such an architecture, the RU 240 may be implemented to handle over-the-air (OTA) communications with one or more UEs 120. In some implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 240 may be controlled by the corresponding DU 230. In some scenarios, this configuration may enable the DU 230 and CU 210 to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).

[0056] The SMO framework 205 may be configured to support RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 205 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 205 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 290) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 210, DU 230, RU 240, and near-RT RIC 225. In some specific implementations, the SMO framework 205 may communicate with hardware aspects of the 4G RAN (such as an open eNB (O-eNB) 211) via the O1 interface. Additionally, in some specific implementations, the SMO framework 205 may communicate directly with one or more RU240 via the O1 interface. The SMO framework 205 may also include a non-RT RIC 215 configured to support the functionality of the SMO framework 205 .

[0057] The non-RT RIC 215 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 225. The non-RT RIC 215 may be coupled to or in communication with the near-RT RIC 225 (such as via an A1 interface). The near-RT RIC 225 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 210, one or more DUs 230, or both, and the O-eNB with the near-RT RIC 225.

[0058] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 225, the non-RT RIC 215 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 225 and may be received from a non-network data source or from a network function at the SMO framework 205 or the non-RT RIC 215. In some examples, the non-RT RIC 215 or the near-RT RIC 225 may be configured to adjust RAN behavior or performance. For example, the non-RT RIC 215 may monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions through the SMO framework 205 (such as via reconfiguration of O1) or via the creation of RAN management policies (such as A1 policies).

[0059] Figure 3 Aspects of an example BS 110 and UE 120 are depicted.

[0060] In general, BS 110 includes various processors (e.g., 320, 330, 338, and 340), antennas 334a-334t (collectively 334), transceivers 332a-332t (collectively 332) including modulators and demodulators, and other aspects that enable wireless transmission of data (e.g., data source 312) and wireless reception of data (e.g., data sink 339). For example, BS 110 can transmit and receive data between BS 110 and UE 120. BS 110 includes a controller / processor 340 that can be configured to implement various functions described herein related to wireless communications.

[0061] Generally speaking, the UE 120 includes various processors (e.g., 358, 364, 366, and 380), antennas 352a-352r (collectively 352), transceivers 354a-354r (collectively 354) including modulators and demodulators, and other aspects that enable wireless transmission of data (e.g., retrieved from a data source 362) and wireless reception of data (e.g., provided to a data sink 360). The UE 120 includes a controller / processor 380 that may be configured to implement various functions described herein related to wireless communications.

[0062] Regarding example downlink transmissions, BS 110 includes a transmit processor 320 that can receive data from a data source 312 and control information from a controller / processor 340. The control information can be for a physical broadcast channel (PBCH), a physical control format indicator channel (PCFICH), a physical hybrid automatic repeat request (HARQ) indicator channel (PHICH), a physical downlink control channel (PDCCH), a group common PDCCH (GC PDCCH), and / or others. In some examples, the data can be for a physical downlink shared channel (PDSCH).

[0063] The transmit processor 320 may process (e.g., encode and symbol map) data and control information to obtain data symbols and control symbols, respectively. The transmit processor 320 may also generate reference symbols (such as for a primary synchronization signal (PSS), a secondary synchronization signal (SSS), a PBCH demodulation reference signal (DMRS), and a channel state information reference signal (CSI-RS)).

[0064] The transmit (TX) multiple-input multiple-output (MIMO) processor 330 may perform spatial processing (e.g., pre-decoding) on ​​data symbols, control symbols, and / or reference symbols, where applicable, and may provide an output symbol stream to a modulator (MOD) in a transceiver 332a-332t. Each modulator in the transceiver 332a-332t may process a corresponding output symbol stream to obtain an output sample stream. Each modulator may further process (e.g., convert to analog, amplify, filter, and up-convert) the output sample stream to obtain a downlink signal. The downlink signals from the modulators in the transceivers 332a-332t may be transmitted via antennas 334a-334t, respectively.

[0065] To receive downlink transmissions, UE 120 includes antennas 352a-352r that can receive downlink signals from BS 110 and can provide received signals to demodulators (DEMODs) in transceivers 354a-354r, respectively. Each demodulator in transceivers 354a-354r can condition (e.g., filter, amplify, downconvert, and digitize) a corresponding received signal to obtain input samples. Each demodulator can further process the input samples to obtain received symbols.

[0066] A MIMO detector 356 may obtain received symbols from all demodulators in transceivers 354a-354r, perform MIMO detection on the received symbols if applicable, and provide detected symbols. A receive processor 358 may process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide decoded data for UE 120 to a data sink 360, and provide decoded control information to a controller / processor 380.

[0067] With respect to example uplink transmissions, the UE 120 also includes a transmit processor 364 that may receive and process data from a data source 362 (e.g., for a PUSCH) and control information from a controller / processor 380 (e.g., for a physical uplink control channel (PUCCH)). The transmit processor 364 may also generate reference symbols for reference signals (e.g., for a sounding reference signal (SRS)). The symbols from the transmit processor 364 may be pre-decoded by a TX MIMO processor 366, if applicable, further processed by a modulator in the transceivers 354a-354r (e.g., for SC-FDM), and transmitted to the BS 110.

[0068] At BS 110, uplink signals from UE 120 may be received by antennas 334a-334t, processed by demodulators in transceivers 332a-332t, detected by MIMO detector 336 where applicable, and further processed by receive processor 338 to obtain decoded data and control information transmitted by UE 120. Receive processor 338 may provide decoded data to data sink 339 and decoded control information to controller / processor 340. Memory 342 and memory 382 may store data and program codes for BS 110 and UE 120, respectively. Scheduler 344 may schedule UEs for data transmission on the downlink and / or uplink.

[0069] In various aspects, BS 110 may be described as sending and receiving various types of data associated with the methods described herein. In these contexts, "sending" may refer to various mechanisms for outputting data, such as outputting data from a data source 312, a scheduler 344, a memory 342, a transmit processor 320, a controller / processor 340, a TX MIMO processor 330, a transceiver 332a-332t, an antenna 334a-334t, and / or other aspects described herein. Similarly, "receiving" may refer to various mechanisms for obtaining data, such as obtaining data from an antenna 334a-334t, a transceiver 332a-332t, a RX MIMO detector 336, a controller / processor 340, a receive processor 338, a scheduler 344, a memory 342, and / or other aspects described herein.

[0070] In various aspects, the UE 120 may also be described as sending and receiving various types of data associated with the methods described herein. In these contexts, "sending" may refer to various mechanisms for outputting data, such as outputting data from a data source 362, a memory 382, ​​a transmit processor 364, a controller / processor 380, a TX MIMO processor 366, a transceiver 354a-354t, an antenna 352a-352t, and / or other aspects described herein. Similarly, "receiving" may refer to various mechanisms for obtaining data, such as obtaining data from an antenna 352a-352t, a transceiver 354a-354t, a RX MIMO detector 356, a controller / processor 380, a receive processor 358, a memory 382, ​​and / or other aspects described herein.

[0071] In some aspects, the processor may be configured to perform various operations (such as those associated with the methods described herein) and send (output) data to or receive (obtain) data from another interface configured to send or receive data, respectively.

[0072] Figure 4A , Figure 4B , Figure 4C and Figure 4D Describes a method for use in a wireless communication network such as Figure 1 Various aspects of the data structure of the wireless communication network 100).

[0073] Specifically, Figure 4A is a diagram 400 illustrating an example of a first subframe within a 5G (e.g., 5G NR) frame structure, Figure 4B is a diagram 430 illustrating an example of a DL channel within a 5G subframe, Figure 4C is a diagram 450 illustrating an example of a second subframe within a 5G frame structure, and Figure 4D FIG480 is a diagram illustrating an example of UL channels within a 5G subframe.

[0074] Wireless communication systems may utilize orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) on both the uplink and downlink. Such systems may also support half-duplex operation using time division duplex (TDD). OFDM and single carrier frequency division multiplexing (SC-FDM) will (for example, Figure 4B and Figure 4D The system bandwidth (as depicted in FIG. 1 ) is divided into multiple orthogonal subcarriers. Each subcarrier can be modulated with data. Modulation symbols can be transmitted in the frequency domain using OFDM and / or in the time domain using SC-FDM.

[0075] The wireless communication frame structure may be frequency division duplex (FDD), where for a particular set of subcarriers, subframes within the set of subcarriers are dedicated to either DL or UL. The wireless communication frame structure may also be time division duplex (TDD), where for a particular set of subcarriers, subframes within the set of subcarriers are dedicated to both DL and UL.

[0076] exist Figure 4A and Figure 4C In the wireless communication frame structure, TDD is used, where D is DL, U is UL, and F is used flexibly between DL / UL. The UE can be configured with a slot format (dynamically configured by DL control information (DCI) or semi-statically / statically configured by RRC signaling) through a received slot format indicator (SFI). In the depicted example, a 10ms frame is divided into 10 1ms subframes of equal size. Each subframe may include one or more slots. In some examples, each slot may include 7 or 14 symbols, depending on the slot format. A subframe may also include a microslot, which typically has fewer symbols than a whole slot. Other wireless communication technologies may have different frame structures and / or different channels.

[0077] In certain aspects, the number of slots within a subframe is based on the slot configuration and parameter set. For example, for slot configuration 0, different parameter sets (μ) 0 to 5 allow for 1, 2, 4, 8, 16, and 32 slots per subframe, respectively. For slot configuration 1, different parameter sets 0 to 2 allow for 2, 4, and 8 slots per subframe, respectively. Accordingly, for slot configuration 0 and parameter set μ, there are 14 symbols per slot and 2 per subframe. μ time slots. The subcarrier spacing and symbol length / duration are functions of the parameter set. The subcarrier spacing can be equal to 2 μ × 15kHz, where μ is parameter set 0 to 5. Accordingly, parameter set μ=0 has a subcarrier spacing of 15kHz, and parameter set μ=5 has a subcarrier spacing of 480kHz. The symbol length / duration is inversely related to the subcarrier spacing. Figure 4A , Figure 4B , Figure 4C and Figure 4D An example is provided for slot configuration 0 with 14 symbols per slot and parameter set μ=2 with 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.

[0078] like Figure 4A , Figure 4B , Figure 4C and Figure 4DAs depicted in FIG. 1 , a resource grid may be used to represent a frame structure. Each time slot includes a resource block (RB) (also referred to as a physical RB (PRB)) extending, for example, over 12 consecutive subcarriers. The resource grid is divided into a plurality of resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0079] like Figure 4A As illustrated, some of the REs carry data for UEs (eg, Figure 1 and Figure 3 The RS may include a demodulation RS (DMRS) and / or a channel state information reference signal (CSI-RS) for channel estimation at the UE. The RS may also include a beam measurement RS (BRS), a beam refinement RS (BRRS), and / or a phase tracking RS (PT-RS).

[0080] Figure 4B Examples of various DL channels within a subframe of a frame are illustrated.The Physical Downlink Control Channel (PDCCH) carries DCI within one or more Control Channel Elements (CCEs), each CCE comprising, for example, nine RE Groups (REGs), each REG comprising, for example, four consecutive REs in an OFDM symbol.

[0081] The primary synchronization signal (PSS) may be in symbol 2 of a particular subframe of a frame. The PSS is transmitted by a UE (e.g., Figure 1 and Figure 3 104) is used to determine subframe / symbol timing and physical layer identification.

[0082] A Secondary Synchronization Signal (SSS) may be within symbol 4 of a particular subframe of a frame. The SSS is used by the UE to determine the physical layer cell identity group number and radio frame timing.

[0083] 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 DMRS. 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. The MIB provides the system frame number (SFN) and the number of RBs in the system bandwidth. The physical downlink shared channel (PDSCH) carries user data, broadcast system information (such as system information blocks (SIBs)) that is not sent via the PBCH, and / or paging messages.

[0084] like Figure 4CAs illustrated, some REs carry DMRS for channel estimation at the base station (indicated as R for one particular configuration, but other DMRS configurations are possible). The UE may send DMRS for PUCCH and DMRS for PUSCH. The PUSCH DMRS may be sent, for example, in the first one or two symbols of the PUSCH. The PUCCH DMRS may be sent in different configurations depending on whether a short PUCCH or a long PUCCH is sent and depending on the specific PUCCH format used. UE 120 may send a sounding reference signal (SRS). The SRS may be sent, for example, in the last symbol of a subframe. The SRS may have a comb structure, and the UE may send the SRS on one of the teeth of the comb. The SRS may be used by the base station for channel quality estimation to achieve frequency-dependent scheduling of the UL.

[0085] Figure 4D Examples of various UL channels within a subframe of a frame are illustrated. The PUCCH may be located at a position as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicator (CQI), precoding matrix indicator (PMI), rank indicator (RI), and HARQ ACK / NACK feedback. The PUSCH carries data and may additionally be used to carry a buffer status report (BSR), a power headroom report (PHR), and / or UCI.

[0086] Aspects related to switching single frequency network (SFN) physical uplink shared channel (PUSCH) communication schemes

[0087] Figure 5 An example logical architecture of a distributed RAN 500 is illustrated.

[0088] The 5G access node 505 may include an access node controller 510. The access node controller 510 may be a central unit (CU) of the distributed RAN 500. In some aspects, a backhaul interface to the 5G core network 515 may terminate at the access node controller 510. The 5G core network 515 may include a 5G control plane component 520 and a 5G user plane component 525 (e.g., a 5G gateway), and a backhaul interface for one or both of the 5G control plane and the 5G user plane may terminate at the access node controller 510. Additionally or alternatively, a backhaul interface to one or more neighbor access nodes 530 (e.g., another 5G access node 505 and / or an LTE access node) may terminate at the access node controller 510.

[0089] The access node controller 510 may include one or more TRPs 535 and / or may communicate with one or more TRPs (e.g., via an F1 control (F1-C) interface and / or an F1 user (F1-U) interface). The TRP 535 may be a distributed unit (DU) of the distributed RAN 500. In some aspects, the TRP 535 may correspond to the above combined Figure 1 The base station 110 described herein. For example, different TRPs 535 may be included in different base stations 110. Additionally or alternatively, multiple TRPs 535 may be included in a single base station 110. In some aspects, a base station 110 may include a CU (e.g., an access node controller 510) and / or one or more DUs (e.g., one or more TRPs 535). In some cases, a TRP 535 may be referred to as a cell, a panel, an antenna array, or an array.

[0090] The TRP 535 may be connected to a single access node controller 510 or to multiple access node controllers 510. In some aspects, there may be a dynamic configuration of split logical functions within the architecture of the distributed RAN 500. For example, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and / or a medium access control (MAC) layer may be configured to terminate at an access node controller 510 or a TRP 535.

[0091] In some aspects, multiple TRPs 535 may transmit communications (e.g., the same communication or different communications) in the same transmit time interval (TTI) (e.g., time slot, mini-slot, subframe, or symbol) or in different TTIs using different quasi-co-location (QCL) relationships (e.g., different spatial parameters, different transmit configuration indicator (TCI) states, different pre-coding parameters, and / or different beamforming parameters). In some aspects, the TCI state may be used to indicate one or more QCL relationships. A TRP 535 may be configured to provide services to a UE 120 individually (e.g., using dynamic selection) or jointly (e.g., using joint transmission with one or more other TRPs 535).

[0092] As indicated above, Figure 5 are provided as examples. Other examples can be found in the Figure 5 The examples described are different.

[0093] Figure 6 6 is a diagram illustrating an example 600 of multi-TRP communication (sometimes referred to as multi-panel communication). Figure 6 As shown, multiple TRPs 605 can communicate with the same UE 120. TRP 605 can correspond to the above combination Figure 5 TRP 535 as described.

[0094] Multiple TRPs 605 (shown as TRP A and TRP B) may communicate with the same UE 120 in a coordinated manner (e.g., using coordinated multipoint transmission) to improve reliability and / or increase throughput. The TRPs 605 may coordinate such communications via an interface between the TRPs 605 (e.g., a backhaul interface and / or an access node controller 510). When the TRPs 605 are co-located at the same base station 110 (e.g., when the TRPs 605 are different antenna arrays or panels of the same base station 110), the interface may have less latency and / or higher capacity, and when the TRPs 605 are located at different base stations 110, the interface may have greater latency and / or lower capacity (compared to co-location). Different TRPs 605 may communicate with the UE 120 using different QCL relationships (e.g., different TCI states), different demodulation reference signal (DMRS) ports, and / or different layers (e.g., different layers in multi-layer communications).

[0095] In a first multi-TRP transmission mode (e.g., Mode 1), a single physical downlink control channel (PDCCH) may be used to schedule downlink data communications of a single physical downlink shared channel (PDSCH). In this case, multiple TRPs 605 (e.g., TRP A and TRP B) may transmit communications to UE 120 on the same PDSCH. For example, communications may be transmitted using a single codeword with different spatial layers for different TRPs 605 (e.g., one of the codewords is mapped to a first set of layers transmitted by a first TRP 605 and is mapped to a second set of layers transmitted by a second TRP 605). As another example, communications may be transmitted using multiple codewords, with different codewords being transmitted by different TRPs 605 (e.g., using different sets of layers). In either case, different TRPs 605 may use different QCL relationships (e.g., different TCI states) for different DMRS ports corresponding to different layers. For example, the first TRP 605 may use a first QCL relationship or a first TCI state for a first DMRS port set corresponding to a first layer set, and the second TRP 605 may use a second (different) QCL relationship or a second (different) TCI state for a second (different) DMRS port set corresponding to a second (different) layer set. In some aspects, the TCI state in the downlink control information (DCI) (e.g., sent on the PDCCH, such as DCI format 1_0 or DCI format 1_1) may indicate a first QCL relationship (e.g., by indicating a first TCI state) and a second QCL relationship (e.g., by indicating a second TCI state). The first TCI state and the second TCI state may be indicated using a TCI field in the DCI. Typically, in this multi-TRP transmission mode (e.g., mode 1), the TCI field may indicate a single TCI state (for single TRP transmission) or multiple TCI states (for multi-TRP transmission as discussed herein).

[0096] In a second multi-TRP transmission mode (e.g., Mode 2), multiple PDCCHs may be used to schedule downlink data communications for multiple corresponding PDSCHs (e.g., one PDCCH for each PDSCH). In this case, the first PDCCH may schedule a first codeword to be sent by the first TRP 605, and the second PDCCH may schedule a second codeword to be sent by the second TRP 605. In addition, a first DCI (e.g., sent by the first TRP 605) may schedule a first PDSCH communication associated with a first DMRS port set having a first QCL relationship (e.g., indicated by a first TCI state) for the first TRP 605, and a second DCI (e.g., sent by the second TRP 605) may schedule a second PDSCH communication associated with a second DMRS port set having a second QCL relationship (e.g., indicated by a second TCI state) for the second TRP 605. In this case, the DCI (e.g., having DCI format 1_0 or DCI format 1_1) may indicate a corresponding TCI state corresponding to the DCI of the TRP 605. The TCI field of the DCI indicates the corresponding TCI state (e.g., the TCI field of the first DCI indicates a first TCI state and the TCI field of the second DCI indicates a second TCI state).

[0097] A single PDCCH may be used to schedule uplink communications for a PUSCH. For example, a single PDCCH may carry DCI that schedules PUSCH communications involving the transmission of multiple PUSCHs (carrying transport blocks (TBs) or sets of TBs) using a communication scheme such as a TDM communication scheme, an FDM communication scheme, an SDM communication scheme, or an SFN communication scheme, among other communication schemes. The techniques described herein provide for switching (or indicating) a communication scheme for a UE via a DCI, such as in conjunction with Fig. 9 described.

[0098] As indicated above, Figure 6 are provided as examples. Other examples can be found in the Figure 6 The examples described are different.

[0099] Figure 7 is a diagram illustrating an example 700 associated with SFN communications.

[0100] In some cases, the UE may operate in an SFN. An SFN may be a network with a configuration in which multiple cells (e.g., multiple network entities or multiple cells associated with a single network entity) simultaneously transmit the same signal on the same frequency channel. As used herein, "SFN transmission" may refer to two or more transmissions that are transmitted using the same (or substantially the same) time domain resources and frequency domain resources. For example, an SFN may be a broadcast network. An SFN may achieve an extended coverage area without using additional frequencies. For example, an SFN configuration may include multiple network entities in an SFN area that use the same frequency to transmit one or more identical signals at the same or substantially the same time. In some aspects, an SFN configuration may include other network devices, such as multiple TRPs corresponding to the same network entity. Multiple TRPs may provide coverage for an SFN area. Multiple TRPs may use the same frequency to transmit one or more identical signals at the same or substantially the same time. In some examples, the same signal sent simultaneously by multiple network entities (and / or multiple TRPs) may include a PDSCH signal, a control resource set (CORESET) that schedules the PDSCH, and / or a reference signal (e.g., a synchronization signal block, CSI-RS, a tracking reference signal (TRS) or other reference signal), among others.

[0101] As indicated by reference numeral 705, an example of communications that do not use a SFN configuration is depicted. TRP 710 may use a transmit (Tx) beam to transmit communications to UE 120. The transmit beam may be associated with a TCI state. UE 120 may use a receive (Rx) beam to receive communications (e.g., transmitted by TRP 710). For example, UE 120 may identify a TCI state associated with the transmit beam and may use information provided by the TCI state to receive communications.

[0102] As shown by reference numeral 715, an example of a first SFN pattern is depicted. Figure 7As shown, the first TRP 720 (or the first base station 110) and the second TRP 725 (or the second base station 110) can send SFN communications 730 to the UE 120. For example, the first TRP 720 and the second TRP 725 can use the same frequency domain resources and the same time domain resources to send substantially the same information (e.g., SFN communications 730) to the UE 120. The first TRP 720 can use a first transmit beam to send the SFN communications 730. The second TRP 725 can use a second transmit beam to send the SFN communications 730. In the first SFN mode, the UE 120 may not be aware that the SFN communications 730 are sent on separate transmit beams (e.g., from different TRPs and / or different base stations 110). Accordingly, when multiple network entities (and / or multiple TRPs) simultaneously transmit the same signal to UE 120, the SFN configuration may be transparent to UE 120, and UE 120 may aggregate or accumulate simultaneous signal transmissions from multiple TRPs (and / or multiple base stations 110), which may provide higher signal quality or higher tolerance to multipath fading, among other benefits. For example, UE 120 may receive SFN communications 730 using a single receive beam (e.g., SFN communications 730 may be received using a single spatial receive direction, etc.). In other words, the TCI states of different transmit beams used to transmit SFN communications 730 may not be signaled to UE 120.

[0103] As shown by reference numeral 735, an example of a second SFN pattern is depicted. Figure 7As shown, the first TRP 740 (or the first base station 110) and the second TRP 745 (or the second base station 110) can send SFN communication 750 to the UE 120. For example, the first TRP 740 and the second TRP 745 can use the same frequency domain resources and the same time domain resources to send substantially the same information (e.g., SFN communication 750) to the UE 120. The first TRP 740 can use a first transmit beam to send SFN communication 750. The second TRP 745 can use a second transmit beam to send SFN communication 750. In the second SFN mode, the UE 120 can know that the SFN communication 750 is sent on a separate transmit beam (e.g., from a different TRP and / or a different base station 110). For example, a first TCI state of a first transmit beam (e.g., associated with the first TRP 740) and a second TCI state of a second transmit beam (e.g., associated with the second TRP 745) can be signaled to the UE 120. For example, base station 110 may send configuration information (e.g., directly to UE 120 or via one or more network entities) indicating that SFN communication 750 may be a combination of transmissions from different TRPs and / or different transmit beams. UE 120 may use information associated with different TRPs and / or different transmit beams (e.g., the first TCI state and the second TCI state) to improve reception performance of SFN communication 750. For example, Figure 7 As shown, UE 120 may receive SFN communications 750 using different spatial directions (e.g., different receive beams) based at least in part on the TCI state of the transmit beam associated with SFN communications 750. This may improve performance of UE 120 because UE 120 may receive SFN communications 750 with improved signal strength and / or signal quality, etc., from different transmit beams and / or different TRPs.

[0104] As indicated above, Figure 7 are provided as examples. Other examples can be found in the Figure 7 The examples described are different.

[0105] Figure 8 is a diagram of example 800 illustrating an SFN communication scheme for PUSCH transmission. Example 800 shows a transmission component of a wireless communication device (e.g., UE 120), a first TRP (e.g., base station 110, TRP 605, TRP 535, TRP 720, TRP 725), and a second TRP (e.g., base station 110, TRP 535, TRP 605, TRP 720, TRP 725). In some aspects, the first TRP and the second TRP may be associated with a gNB (e.g., base station 110).

[0106] Example 800 relates to PUSCH transmission. In some examples, Example 800 may be implemented in a SFN, but the techniques described herein are not limited to those involving SFN. PUSCH is a physical channel used, for example, to convey end-user application data and signaling radio bearer (SRB) messages. Using PUSCH to send data is referred to herein as PUSCH communication. For example, a UE may use PUSCH to send PUSCH communication.

[0107] PUSCH transmission can be codebook-based (CB) transmission or non-CB (NCB) transmission, etc. In CB transmission, the UE may be configured with only one SRS resource set, and the "use" parameter of the SRS resource set may be set to "codebook". Up to 4 SRS resources within the SRS resource set may be configured for the UE. The SRS resource indicator (SRI) field in the uplink DCI (i.e., the DCI that schedules PUSCH transmission) may indicate one SRS resource. The number of layers (i.e., rank) and the transmitted precoding matrix indicator (TPMI) (sometimes referred to as a predecoder) for the scheduled PUSCH may be determined based on a separate DCI field indicating the number of precoding information and layers. For NCB transmission, the UE may be configured with only one SRS resource set with the "use" parameter set to "codebook". The UE may be configured with up to 4 SRS resources within the SRS resource set. Each SRS resource may have one port. The SRI field in the uplink DCI that schedules PUSCH transmission may indicate one or more SRS resources. The number of indicated SRS resources determines the rank (ie, the number of layers) used for the scheduled PUSCH. The PUSCH is transmitted using the same precoder as the indicated SRS resources.

[0108] In some examples, PUSCH transmissions may use repetitions. For example, a single DCI message may schedule multiple PUSCH repetition sets in a TDM manner (referred to herein as a TDM communication scheme). PUSCH repetitions may be sent on PUSCH transmission occasions. Therefore, in the context of PUSCH repetitions, references to PUSCH transmission occasions may refer to PUSCH repetition transmissions on PUSCH transmission occasions. A PUSCH repetition set may include one or more PUSCH repetitions. Each PUSCH repetition set scheduled by a single DCI message may have different transmission parameters (such as beam, spatial relationship, or transmission configuration indicator (TCI) state; power control parameters; or pre-decoders). For example, a first set of PUSCH repetitions scheduled by a single DCI message may belong to a first set associated with a first transmission parameter, and a second set of PUSCH repetitions scheduled by a single DCI message may belong to a second set associated with a second transmission parameter. Each PUSCH repetition set may be associated with the same transport block (e.g., may carry the same transport block). The first set may correspond to a first SRS resource set, and the second set may correspond to a second SRS resource set. The DCI message may indicate two sets of transmission parameters (e.g., indicating two beams, two sets of power control parameters, etc.) using a first SRI field for a first set of transmission parameters and a second SRI field for a second set of transmission parameters. For example, the DCI message may indicate two sets of transmission parameters using two SRI fields for both CB transmission and NCB transmission. For CB transmission, the DCI message may include two TPMI fields indicating two precoders for two PUSCH repetition sets.

[0109] In a TDM communication scheme, a UE may dynamically switch between a multi-TRP (mTRP) mode in which the UE communicates with multiple TRPs and a single TRP (sTRP) mode in which the UE communicates with a single TRP. Dynamic switching may be achieved using DCI signaling. This may be based on a field in a DCI format (e.g., DCI formats 0_1 and 0_2), which is referred to herein as an SRS resource set indicator. The presence of an SRS resource set indicator field in a DCI format may be based on whether two SRS resource sets are configured corresponding to the DCI format. In this context, the SRS resource set indicator field may have 2 bits. The 2-bit value (referred to herein as a code point) may indicate whether a PUSCH will be sent in mTRP mode, the SRS resource set to be used for the PUSCH, and the order of PUSCH repetitions scheduled by a DCI message using a DCI format. For example, a first value of the SRS resource set indicator field may indicate that the first repetition will be directed to the first TRP and the second repetition will be directed to the second TRP, and a second value of the SRS resource set indicator field may indicate that the first repetition will be directed to the second TRP and the second repetition will be directed to the first TRP. An example set of code points and corresponding transmission parameters is provided in Table 1 below:

[0110]

[0111] Table 1

[0112] In some aspects, a FDM communication scheme may be used to transmit PUSCH communications. In one example of an FDM communication scheme, two PUSCH transmission opportunities with the same or different redundancy versions (RVs) of the same TB are transmitted from different UE antenna groups on non-overlapping frequency domain resources and the same time domain resources. In another example of an FDM communication scheme, different portions of the frequency domain resources of one PUSCH transmission opportunity are transmitted from different UE antenna groups.

[0113] In some aspects, PUSCH communications may be transmitted using an SDM scheme. In an SDM scheme, different layers (eg, different demodulation reference signal (DMRS) ports) of the PUSCH are separately precoded and transmitted simultaneously from different antenna groups of a UE.

[0114] In some aspects, PUSCH communications may be transmitted using an SDM repetition scheme (referred to herein as an SDM communication scheme).In the SDM communication scheme, two PUSCH transmission opportunities with different RVs for the same TB are transmitted simultaneously from two different UE antenna groups.

[0115] Example 800 is an example of an SFN communication scheme using a single DCI-based SFN PUSCH. The SFN communication scheme may provide SFN-based transmissions for PUSCH communications. In the SFN communication scheme, multiple antenna modules of the UE are used simultaneously to transmit all layers (e.g., DMRS ports) of PUSCH transmissions. An antenna module (sometimes referred to as an antenna panel) may include a set of one or more antennas that may be configured to transmit communications using beams. Transmissions using antenna modules may be transmitted via a set of one or more antennas of the antenna module. A single DCI may schedule PUSCH communications. Multiple antenna modules are used to transmit each layer of PUSCH communications. Each of the multiple antenna modules may use a different set of transmit parameters (e.g., transmit beams, pre-decoders, power control parameters, combinations thereof, or another transmit parameter) to transmit PUSCH communications.

[0116] For example, the UE may receive a DCI that schedules the transmission of a PUSCH communication. The DCI may include an SRS resource set indicator field, two SRI fields, and two TPMI fields. The PUSCH communication may include a first layer (layer 0, shown by reference numeral 805) corresponding to a first DMRS port and a second layer (layer 1, shown by reference numeral 810) corresponding to a second DMRS port. Each layer (e.g., DMRS port) of the PUSCH communication may be associated with two SRS resource sets. As shown, each layer of the PUSCH communication is mapped to the first antenna module 825 by (e.g., using) a first TPMI and SRI (shown by reference numeral 815), and is mapped to the second antenna module 830 by (e.g., using) a second TPMI and SRI (shown by reference numeral 820).

[0117] As indicated by reference numeral 835, the first antenna module 825 may transmit (e.g., to a first TRP) a PUSCH communication including a first layer and a second layer. As indicated by reference numeral 840, the second antenna module 830 may transmit a PUSCH communication including a first layer and a second layer. For example, the first antenna module 825 and the second antenna module 830 may transmit all layers of the PUSCH communication simultaneously. The first antenna module 825 may generate a first transmit beam associated with a first TCI state and a first SRS resource set, and the second antenna module 830 may generate a second transmit beam associated with a second TCI state and a second SRS resource set. Thus, the UE may use a SFN transmission scheme to transmit PUSCH communications using multiple antenna modules including the first antenna module 825 and the second antenna module 830.

[0118] As described above, PUSCH repetitions sent using an FDM communication scheme, an SDM communication scheme, and a TDM communication scheme may be associated with an order. The order may indicate whether the communication on the first PUSCH transmission opportunity (or a set of PUSCH transmission opportunities) will be sent to the first TRP or the second TRP. Therefore, when switching between communication schemes associated with an order, the signaling indicating the switching of the communication scheme may indicate the order. For the TDM communication scheme, the order may indicate whether the first PUSCH transmission opportunity is associated with the first SRS resource set or the second SRS resource set in time. For the SDM communication scheme, the order may indicate whether the first set of layers of the PUSCH communication is associated with the first SRS resource set or the second SRS resource set. For the FDM communication scheme, the order may indicate whether the first set of RBs for the PUSCH communication is associated with the first SRS resource set or the second SRS resource set.

[0119] However, the SFN communication scheme may not be associated with an order (e.g., order switching may not make sense for the SFN communication scheme). This is because each DMRS port (e.g., layer) of PUSCH communication across all time resources and frequency resources transmitted by the PUSCH is associated with two SRS resource sets and two TCI states, and therefore the order of the first SRS resource set and the second SRS resource set and the TCI state does not matter (because each layer is transmitted simultaneously using two SRS resource sets and two TCI states). Therefore, a DCI format for switching the SDM communication scheme, the TDM communication scheme, and the FDM communication scheme (the DCI format may include a bit indicating the order for the communication scheme) may involve unnecessary overhead for the SFN communication scheme.

[0120] Some techniques and apparatus described herein provide an indication of whether a PUSCH communication is sent using an SFN communication scheme. In some aspects, the indication may include a single code point indicating the SFN communication scheme, as opposed to two code points corresponding to different orders of communication schemes. Thus, overhead is reduced relative to indications of other communication schemes.

[0121] As indicated above, Figure 8 are provided as examples. Other examples can be found in the Figure 8 The examples described are different.

[0122] Fig. 9 1 is a diagram illustrating an example 900 of signaling associated with a handover for a SFN communication scheme. As shown, example 900 includes a network entity and a UE (e.g., UE 120). The network entity may include, for example, base station 110 or one or more decomposed network entities. In some aspects, the network entity may communicate with multiple TRPs (e.g., TRP 535, TRP 605, TRP 720, or TRP 725). Fig. 9 not shown).

[0123] like Fig. 9 And as shown by reference numeral 910, the UE may optionally send capability signaling. For example, the UE may send capability information. The capability signaling may indicate whether the UE supports the SFN communication scheme. For example, the capability signaling may include a first value indicating that the UE supports the SFN communication scheme (e.g., the UE may use the SFN communication scheme to send PUSCH communications) or a second value indicating that the UE does not support the SFN communication scheme.

[0124] In some aspects, the capability signaling may be specific to a frequency band. For example, the capability signaling may indicate whether the UE supports the SFN communication scheme for PUSCH communication on a specific frequency band. For another example, the capability signaling may identify multiple frequency bands and may indicate, for each of the multiple frequency bands, whether the UE supports the SFN communication scheme on each frequency band.

[0125] In some aspects, the capability signaling may be specific to the UE. For example, the capability signaling may identify the UE and may indicate whether the UE supports the SFN communication scheme.

[0126] In some aspects, the capability signaling may be specific to a frequency band combination. For example, the capability signaling may indicate whether the UE supports the SFN communication scheme for a frequency band combination (e.g., a dual connectivity frequency band combination including at least a first frequency band and a second frequency band). For another example, the capability signaling may identify a plurality of frequency band combinations, and may indicate, for each of the plurality of frequency band combinations, whether the UE supports the SFN communication scheme on each frequency band combination.

[0127] In some aspects, capability signaling may be specific to a feature set. A feature set stores a collection of UE capabilities and features. A feature set may be linked to one or more frequency bands within a frequency band combination, or to one or more frequency band combinations. For example, capability signaling may identify a feature set that indicates whether the UE supports a SFN communication scheme, and the feature set may be linked to each frequency band and frequency band combination that the UE supports the SFN communication scheme. Thus, capability signaling may identify whether the UE supports the SFN communication scheme by frequency band and by frequency band combination.

[0128] As indicated by reference numeral 920, the network entity may optionally output configuration information. For example, the network entity may output configuration information (such as RRC configuration information) for transmission by a TRP or the like. As another example, the network entity may send configuration information. In some aspects, the network entity may output configuration information based on capability signaling described with respect to reference numeral 910. In some aspects, the configuration information may be based at least in part on capability signaling. For example, the network entity may determine configuration information based on whether the capability signaling indicates that the UE supports the SFN communication scheme. As another example, the network entity may output configuration information configuring the SFN communication scheme (e.g., for a specific frequency band, frequency band combination, UE, or frequency band and frequency band combination) based on capability signaling indicating that the UE supports the SFN communication scheme.

[0129] In some aspects, the configuration information may configure multiple SRS resource sets. For example, the configuration information may configure two SRS resource sets with a usage parameter set to "codebook" or "non-codebook". Additionally, the configuration information may configure the SFN communication scheme. For example, the configuration information may indicate activation or switching to the SFN communication scheme via DCI (as described in conjunction with reference numeral 930). As another example, the configuration information may indicate a parameter set for the SFN communication scheme. For example, the configuration information may indicate (such as in Table 2, Table 3, and / or Table 4 below) how the value of the indication provided via the DCI should be interpreted.

[0130] In some aspects, the configuration information may be specific to a bandwidth part (BWP) or a component carrier (CC). For example, the configuration information may be specific to a BWP and / or CC for a dynamic grant of a PUSCH (i.e., a PUSCH whose resources are scheduled via a dynamic grant). A CC is a bandwidth over which a UE can communicate with a network entity. A BWP is a configured set of frequency resources within a CC that can be used by a UE for communication. A BWP may be configured with a set of configuration parameters and may be activated or deactivated for a UE via network signaling. A UE may send and receive communications for the UE within an active BWP. The configuration information may configure multiple SRS resource sets and / or SFN communication schemes for a specific BWP or group of BWPs.

[0131] In some aspects, the capability information may be specific to a configuration grant. For example, the configuration information may be included in the configuration of a configuration grant (CG) associated with a PUSCH (e.g., CG-PUSCH). The configuration information may configure multiple SRS resource sets and / or SFN communication schemes for a particular CG or CG group.

[0132] In some aspects, the capability information may be specific to a DCI format. For example, the configuration may be configured separately for DCI format 0_1 ​​and for DCI format 0_2 (such as for DG-PUSCH) (eg, via different RRC messages or different RRC information elements).

[0133] In some aspects, the configuration information may configure multiple communication schemes. For example, the configuration information may configure two or more of a SFN communication scheme, a TDM communication scheme, an SDM communication scheme, an FDM communication scheme, or an sTRP communication scheme. If more than one communication scheme is configured by the configuration information, the indication described below in conjunction with reference numeral 940 may indicate which communication scheme is to be used for the PUSCH scheduled by the DCI described below in conjunction with reference numeral 930.

[0134] like Fig. 9 And as shown by reference numeral 930, the network entity may output the DCI. The UE may receive the DCI. In some aspects, the network entity may send the DCI. In some other aspects, the network entity may provide the DCI for sending (e.g., via a first TRP and / or a second TRP associated with the network entity).

[0135] As shown by reference numeral 940, the DCI may include an indication. In some aspects, the indication indicates a communication scheme used to send PUSCH communications. For example, the communication scheme may be one of a TDM communication scheme, an FDM communication scheme, an SDM communication scheme, an SFN communication scheme, or an sTRP communication scheme. In some aspects, the indication may include a field of the DCI. For example, the indication may be a value (e.g., a code point) of a field of the DCI.

[0136] In some aspects, the indication may indicate whether the scheduled PUSCH communication (scheduled by the DCI) should be sent using the SFN communication scheme. In some aspects, the DCI may not provide for dynamic switching between the SFN communication scheme and other communication schemes (e.g., TDM communication schemes, SDM communication schemes, or FDM communication schemes) in which the scheduled PUSCH transmission is associated with two SRS resource sets, which reduces the size of the indication relative to an indication indicating a switching arrangement for a communication scheme in which the scheduled PUSCH transmission is associated with two SRS resource sets. In this case, the indication may indicate whether the PUSCH communication will be sent using a first antenna module among a plurality of antenna modules of the UE using a first SRS resource set, using a second antenna module among the plurality of antenna modules using a second SRS resource set, or using both the first antenna module and the second module using the first SRS resource set and the second SRS resource set (i.e., the SFN communication scheme).

[0137] In some aspects, the indication (e.g., SRS resource set indicator field) may include 2 bits. Thus, the indication may indicate 4 values ​​(e.g., 4 code points): 00, 01, 10, and 11. In some aspects, a first value of the indication may indicate that a PUSCH communication will be sent using a first SRS resource set using a first antenna module, a second value may indicate that a PUSCH communication will be sent using a second SRS resource set using a second antenna module, and a third value may indicate that a PUSCH communication will be sent using both the first SRS resource set and the second SRS resource set using the first antenna module and the second module.

[0138] In some aspects, the fourth value of the indication may be retained. For example, the UE may not expect the indication to be set to (e.g., include) the fourth value. In some aspects, the fourth value of the indication may indicate the same behavior as the third value of the indication. For example, the fourth value may indicate that the PUSCH communication will be sent using both the first SRS resource set and the second SRS resource set using the same transmission parameters as the third value using the first antenna module and the second module (e.g., the fourth value may also indicate the use of an SFN communication scheme). In some aspects, the fourth value of the indication may indicate the use of an SFN communication scheme with a different set of transmission parameters than the third value. For example, the third value may indicate that the first set of transmission parameters will be used to simultaneously transmit PUSCH communications using multiple antenna modules, or the fourth value may indicate that the second set of transmission parameters will be used to simultaneously transmit PUSCH communications using multiple antenna modules. In such examples, the fourth value may indicate that one or more DCI fields (such as a transmit power control (TPC) field, a phase tracking reference signal (PTRS)-DMRS association field, or an open-loop power control parameter set indication field) of the DCI are interpreted differently from the third value. For example, if the DCI includes one TPC field, the third value (e.g., 10) may indicate that the TPC command indicated by the TPC field is applied to two closed-loop adjustment states (e.g., two antenna modules in a plurality of antenna modules), and the fourth value (e.g., 11) may indicate that the TPC command is applied only to the first closed-loop adjustment state. For another example, if the DCI includes one TPC field, the third value may indicate that the TPC command is applied only to the first closed-loop adjustment state, and the fourth value may indicate that the TPC command is applied only to the second closed-loop adjustment state. Examples of indicated values, SRS resource sets indicated by these values, and communication schemes indicated by these values ​​are provided in Table 2 below:

[0139]

[0140] Table 2

[0141] In some aspects, the indication (e.g., the SRS resource set indicator field) may include 1 bit. Thus, the indication may indicate 2 values ​​(e.g., 2 code points): 0 and 1. In some aspects, the first value of the indication indicates that the PUSCH communication will be sent using the first SRS resource set using the first antenna module (e.g., a single antenna module), or the second value of the indication indicates that the PUSCH communication will be sent using the first SRS resource set and the second SRS resource set (e.g., using an SFN communication scheme) using multiple antenna modules of the UE. For example, the second value may indicate an SFN communication scheme, and the first value may indicate a fixed one of the two SRS resource sets. An example is provided in Table 3 below:

[0142]

[0143] Table 3

[0144] In some aspects, the indication (e.g., the SRS resource set indicator field) may provide a switch of the communication scheme between an SFN communication scheme and one or more communication schemes in which the PUSCH is associated with two SRS resource sets (such as a TDM communication scheme, an SDM communication scheme, or an FDM communication scheme). For example, the indication may indicate a specific communication scheme for sending PUSCH communications, wherein the specific communication scheme is one of an SFN communication scheme, a TDM communication scheme, an SDM communication scheme, an FDM communication scheme, or an sTRP communication scheme. In some aspects, the indication may indicate a switching arrangement associated with the specific communication scheme. For example, if the specific communication scheme may be associated with a first switching arrangement or a second switching arrangement (such as a TDM communication scheme, an SDM communication scheme, or an FDM communication scheme), the indication may indicate whether the specific communication scheme is associated with the first switching arrangement or the second switching arrangement. For example, the indication may select between PUSCH communication associated with the first SRS resource set, PUSCH communication associated with the second SRS resource set, one or more of a TDM communication scheme, an SDM communication scheme, or an FDM communication scheme associated with two SRS resource sets and with the first SRS resource set applied first (i.e., the first switching arrangement), one or more of a TDM communication scheme, an SDM communication scheme, or an FDM communication scheme associated with two SRS resource sets and with the second SRS resource set applied first (i.e., the second switching arrangement), or an SFN communication scheme associated with two SRS resource sets.

[0145] In some aspects, the SFN communication scheme is associated with a single value (e.g., a code point) of the indication. If there are additional values ​​(in addition to the value used to indicate a TDM communication scheme, an FDM communication scheme, an SDM communication scheme, or another communication scheme other than the SFN communication scheme), these additional values ​​may be retained. In some aspects, a single value may be assigned to the sTRP communication scheme, which may reduce the size of the indication. In some aspects, a single value may be assigned to a communication scheme in which the PUSCH is associated with two SRS resource sets (such as a TDM communication scheme, an SDM communication scheme, or an FDM communication scheme), which may reduce the size of the indication. In such examples, a single value may correspond to a single switching arrangement for a communication scheme (e.g., switching of the switching arrangement may not be enabled for a communication scheme associated with a single value).

[0146] In some aspects, the SFN communication scheme is associated with multiple values ​​(e.g., code points) of the indication. The multiple values ​​may each indicate a SFN communication scheme and the same transmission parameters for the SFN communication scheme. In some other aspects, a first value associated with the SFN communication scheme may indicate a first set of transmission parameters for the SFN communication scheme, and a second value associated with the SFN communication scheme may indicate a second set of transmission parameters for the SFN communication scheme (different from the first set of transmission parameters). For example, the second value may indicate a different interpretation of one or more DCI fields (e.g., a transmit power control field, a PTRS-DMRS association field, or an open-loop power control parameter set indication field of the DCI of reference numeral 930).

[0147] Example values ​​for providing an indication of switching of a communication scheme between a SFN communication scheme and one or more communication schemes in which a PUSCH is associated with two SRS resource sets are provided in Table 4 below:

[0148]

[0149] Table 4

[0150] As shown by reference numeral 950, the UE may send PUSCH communications according to the DCI. For example, the UE may send PUSCH communications using a specific communication scheme indicated by the indication shown by reference numeral 940. In some aspects, the UE may send PUSCH communications using an SFN communication scheme. For example, the UE may send PUSCH communications, and all layers of the PUSCH communications (e.g., DMRS ports) are sent using each of the multiple antenna modules of the UE. In this way, the UE can use the DCI to dynamically switch to the SFN communication scheme. In some examples, the indication of the DCI does not include an indication of a switching arrangement for the communication scheme, which reduces the size of the indication. In some examples, the DCI may indicate a communication scheme associated with multiple SRS resource sets in addition to the SFN communication scheme, which increases the flexibility of the UE's PUSCH transmission.

[0151] Example Operation of User Equipment

[0152] Fig.10 The method for use by a UE such as Figure 1 and Figure 3 A method 1000 for wireless communication with a UE 120 of the present invention. The UE may be configured for wireless communication.

[0153] Method 1000 begins at 1010 by receiving (e.g., using controller / processor 380, antenna 352, receive processor 358, receive MIMO detector 356, transceiver 354, or memory 382) a DCI that includes an indication to send a PUSCH communication associated with the DCI using a SFN communication scheme in which each layer of the PUSCH communication is sent simultaneously using multiple antenna modules of the UE.

[0154] The method 1000 then proceeds to step 1020 where a PUSCH communication is transmitted in accordance with the DCI (eg, using the controller / processor 380, antenna 352, transmit processor 364, transmit MIMO processor 366, or transceiver 354).

[0155] In a first aspect, the indication indicates whether the PUSCH communication will be sent using a first sounding reference signal (SRS) resource set using a first antenna module among the multiple antenna modules, using a second SRS resource set using a second antenna module among the multiple antenna modules, or using both the first SRS resource set and the second SRS resource set using the first antenna module and the second module.

[0156] In a second aspect, alone or in combination with the first aspect, the first value of the indication indicates that a first set of transmission parameters will be used to simultaneously send the PUSCH communication using the multiple antenna modules, or the second value of the indication indicates that a second set of transmission parameters will be used to simultaneously send the PUSCH communication using the multiple antenna modules.

[0157] In a third aspect, alone or in combination with one or more of the first and second aspects, the first value of the indication indicates that the PUSCH communication will be sent using the first antenna module using the first SRS resource set, or the second value of the indication indicates that the PUSCH communication will be sent using the multiple antenna modules using the first SRS resource set and the second SRS resource set.

[0158] In a fourth aspect, either alone or in combination with one or more of the first to third aspects, the indication indicates a specific communication scheme used to send the PUSCH communication, wherein the specific communication scheme is one of the following: the SFN communication scheme, the time division multiplexing (TDM) communication scheme, the space division multiplexing (SDM) communication scheme, the frequency division multiplexing (FDM) communication scheme or the single transmit receive point (TRP) communication scheme.

[0159] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the indication indicates a switching arrangement associated with the particular communication scheme.

[0160] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the indication is based at least in part on a configuration of at least one of the SFN communication scheme, the first SRS resource set, or the second SRS resource set.

[0161] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, the configuration is specific to a bandwidth portion, a carrier, or a configuration grant.

[0162] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, the configuration is specific to a DCI format.

[0163] In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, the configuration indicates a plurality of communication schemes including the SFN communication scheme, and the indication indicates a selected communication scheme among the plurality of communication schemes.

[0164] In a tenth aspect, alone or in combination with one or more of the first to ninth aspects, method 1000 includes sending capability information indicating that the UE supports the SFN communication scheme.

[0165] In an eleventh aspect, alone or in combination with one or more of the first to tenth aspects, the capability information is specific to a frequency band, a UE, a frequency band combination, or a feature set.

[0166] In one aspect, method 1000 or any aspect related thereto may be performed by an apparatus such as Fig.12 The method 1000 is performed by a communication device 1200 that includes various components that are operable, configured, or adapted to perform the method 1000. The communication device 1200 is described in more detail below.

[0167] It should be noted that Fig.10 This is merely one example of a method, and other methods including fewer, additional, or alternative steps are possible consistent with the present disclosure.

[0168] Example Operations of Network Entities

[0169] Fig.11 A method for transmitting data to a network entity such as Figure 1 and Figure 3 BS110 or such Figure 2 A method 1100 for wireless communication using a decomposed base station as discussed above. A network entity may be configured for wireless communication.

[0170] Method 1100 begins at 1110 by sending (e.g., using antenna 334, transceiver 332, transmit processor 320, transmit MIMO processor 330, and / or controller / processor 340) a DCI that includes an indication for sending PUSCH communications associated with the DCI using a SFN communication scheme in which each layer of the PUSCH communication is simultaneously sent using multiple antenna modules of the UE.

[0171] The method 1100 then proceeds to step 1120 where a PUSCH communication is received in accordance with the DCI (eg, using the antenna 334, the transceiver 332, the receive MIMO detector 336, the receive processor 338, and / or the controller / processor 340).

[0172] In a first aspect, the indication indicates whether the PUSCH communication will be sent using a first SRS resource set using a first antenna module among the multiple antenna modules, using a second SRS resource set using a second antenna module among the multiple antenna modules, or using both the first SRS resource set and the second SRS resource set using the first antenna module and the second module.

[0173] In a second aspect, alone or in combination with the first aspect, the first value of the indication indicates that a first set of transmission parameters will be used to simultaneously send the PUSCH communication using the multiple antenna modules, or the second value of the indication indicates that a second set of transmission parameters will be used to simultaneously send the PUSCH communication using the multiple antenna modules.

[0174] In a third aspect, alone or in combination with one or more of the first and second aspects, the first value of the indication indicates that the PUSCH communication will be sent using the first antenna module using the first SRS resource set, or the second value of the indication indicates that the PUSCH communication will be sent using the multiple antenna modules using the first SRS resource set and the second SRS resource set.

[0175] In a fourth aspect, either alone or in combination with one or more of the first to third aspects, the indication indicates a specific communication scheme used to send the PUSCH communication, wherein the specific communication scheme is one of the following: the SFN communication scheme, the TDM communication scheme, the SDM communication scheme, the FDM communication scheme or the single TRP communication scheme.

[0176] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the indication indicates a switching arrangement associated with the particular communication scheme.

[0177] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the indication is based at least in part on a configuration of at least one of the SFN communication scheme, the first SRS resource set, or the second SRS resource set.

[0178] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, the configuration is specific to a bandwidth portion, a carrier, or a configuration grant.

[0179] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, the configuration is specific to a DCI format.

[0180] In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, the configuration indicates a plurality of communication schemes including the SFN communication scheme, and the indication indicates a selected communication scheme among the plurality of communication schemes.

[0181] In a tenth aspect, alone or in combination with one or more of the first to ninth aspects, method 1100 includes receiving capability information indicating that the UE supports the SFN communication scheme, wherein the DCI is based at least in part on the capability information.

[0182] In an eleventh aspect, alone or in combination with one or more of the first to tenth aspects, the capability information is specific to a frequency band, a UE, a frequency band combination, or a feature set.

[0183] In one aspect, method 1100 or any aspect related thereto may be performed by an apparatus such as Fig.13 The method 1100 is performed by a communication device 1300 that includes various components that are operable, configured, or adapted to perform the method 1100. The communication device 1300 is described in more detail below.

[0184] It should be noted that Fig.11 This is merely one example of a method, and other methods including fewer, additional, or alternative steps are possible consistent with the present disclosure.

[0185] Example Communication Device

[0186] Fig.12 Depicted are aspects of an example communications device 1200. In some examples, the communications device 1200 is a UE, such as described above with respect to Figure 1 and Figure 3 UE 120 is described.

[0187] The communication device 1200 includes a processing system 1202 coupled to a transceiver 1208 (e.g., a transmitter and / or a receiver). The transceiver 1208 is configured to transmit and receive signals for the communication device 1200, such as various signals as described herein, via an antenna 1210. The processing system 1202 may be configured to perform processing functions for the communication device 1200, including processing signals received and / or to be transmitted by the communication device 1200.

[0188] The processing system 1202 includes one or more processors 1220. In various aspects, the one or more processors 1220 may represent one or more of the receive processor 358, the transmit processor 364, the TX MIMO processor 366, and / or the controller / processor 380, as described with respect to FIG. Figure 3 The one or more processors 1220 are coupled to the computer readable medium / memory 1230 via the bus 1206. In some aspects, the computer readable medium / memory 1230 is configured to store instructions (e.g., computer executable code) that, when executed by the one or more processors 1220, cause the one or more processors 1220 to perform operations related to the computer readable medium / memory 1230. Fig.10 The described method 1000 or any aspect related thereto. It should be noted that reference to a processor performing a function of the communication device 1200 may include one or more processors performing that function of the communication device 1200.

[0189] In the depicted example, the computer-readable medium / memory 1230 stores code (e.g., processor-executable instructions) 1231 for receiving a DCI including an indication for sending a PUSCH communication, code 1232 for sending a PUSCH communication in accordance with the DCI, and code 1233 for sending capability information indicating that the UE supports the SFN communication scheme. Processing of the codes 1231-1233 may cause the communication device 1200 to perform operations related to Fig.10 The described method 1000 or any aspect related thereto.

[0190] The one or more processors 1220 include circuits configured to implement (e.g., execute) code stored in the computer-readable medium / memory 1230, including circuits 1221 for receiving a DCI including an indication for sending a PUSCH communication, circuits 1222 for sending a PUSCH communication according to the DCI, and circuits 1223 for sending capability information indicating that the UE supports the SFN communication scheme. Processing using circuits 1221-1223 may cause the communication device 1200 to perform operations related to Fig.10 The described method 1000 or any aspect related thereto.

[0191] The various components of the communication device 1200 may provide for performing Fig.10 The components of the described method 1000 or any aspect related thereto. For example, the components for sending, transmitting, or outputting for sending may include Figure 3 The illustrated transceiver 354 and / or antenna 352 of the UE 120, and / or Fig.12 The transceiver 1208 and antenna 1210 of the communication device 1200 in FIG. 1 may include Figure 3 The illustrated transceiver 354 and / or antenna 352 of the UE 120, and / or Fig.12 The transceiver 1208 and antenna 1210 of the communication device 1200 in FIG.

[0192] Fig.13 Depicted are aspects of an example communication device. In some aspects, the communication device 1300 is a network entity such as Figure 1 and Figure 3 BS110 or such Figure 2 The decomposed base station in question.

[0193] The communication device 1300 includes a processing system 1302 coupled to a transceiver 1308 (e.g., a transmitter and / or a receiver) and / or a network interface 1312. The transceiver 1308 is configured to transmit and receive signals for the communication device 1300 via an antenna 1310, such as various signals as described herein. The network interface 1312 is configured to transmit and receive signals for the communication device 1300 via a communication link (such as, for example, as described herein with respect to Figure 2 The processing system 1302 may be configured to perform processing functions of the communication device 1300, including processing signals received and / or to be transmitted by the communication device 1300.

[0194] The processing system 1302 includes one or more processors 1320. In various aspects, the one or more processors 1320 may represent one or more of the receive processor 338, the transmit processor 320, the TX MIMO processor 330, and / or the controller / processor 340, as described with respect to FIG. Figure 3 The one or more processors 1320 are coupled to the computer readable medium / memory 1330 via the bus 1306. In some aspects, the computer readable medium / memory 1330 is configured to store instructions (e.g., computer executable code) that, when executed by the one or more processors 1320, cause the one or more processors 1320 to perform operations related to the computer readable medium / memory 1330. Fig.11 The described method 1100 or any aspect related thereto. It should be noted that reference to a processor of the communication device 1300 performing a function may include one or more processors of the communication device 1300 performing the function.

[0195] In the depicted example, the computer-readable medium / memory 1330 stores code (e.g., processor-executable instructions) 1331 for sending a DCI including an indication for sending a PUSCH communication, code 1332 for receiving a PUSCH communication according to the DCI, and / or code 1333 for receiving capability information indicating that the UE supports the SFN communication scheme. Processing of the codes 1331-1333 may cause the communication device 1300 to perform operations related to Fig.11 The described method 1100 or any aspect related thereto.

[0196] The one or more processors 1320 include circuits configured to implement (e.g., execute) code stored in the computer-readable medium / memory 1330, including circuits 1321 for sending a DCI including an indication for sending a PUSCH communication, circuits 1322 for receiving a PUSCH communication according to the DCI, and circuits 1323 for receiving capability information indicating that the UE supports the SFN communication scheme. Processing using circuits 1321-1323 may cause the communication device 1300 to perform as described above. Fig.11 The described method 1100 or any aspect related thereto.

[0197] The various components of the communication device 1300 may be provided for performing the following operations: Fig.11 The components of the described method 1100 or any aspect thereof. The components for sending, transmitting, or outputting for sending may include Figure 3 The illustrated transceiver 332 and / or antenna 334 of the BS 110, and / or Fig.13 The transceiver 1308 and antenna 1310 of the communication device 1300 in FIG. 1304 may include Figure 3 The illustrated transceiver 332 and / or antenna 334 of the BS 110, and / or Fig.13 The transceiver 1308 and antenna 1310 of the communication device 1300 in FIG.

[0198] Sample Clauses

[0199] Specific implementation examples are described in the following numbered clauses:

[0200] Clause 1: A method of wireless communications performed by a user equipment (UE), the method comprising: receiving downlink control information (DCI), the DCI comprising an indication for sending a physical uplink shared channel (PUSCH) communication associated with the DCI using a single frequency network (SFN) communication scheme, in which each layer of the PUSCH communication is simultaneously sent using multiple antenna modules of the UE; and sending the PUSCH communication in accordance with the DCI.

[0201] Clause 2: A method according to clause 1, wherein the indication indicates whether the PUSCH communication will be sent using a first sounding reference signal (SRS) resource set using a first antenna module among the multiple antenna modules, using a second SRS resource set using a second antenna module among the multiple antenna modules, or using both the first SRS resource set and the second SRS resource set using the first antenna module and the second module.

[0202] Clause 3: A method according to any one of clauses 1 to 2, wherein the first value of the indication indicates that a first set of transmission parameters will be used to simultaneously transmit the PUSCH communication using the multiple antenna modules, or the second value of the indication indicates that a second set of transmission parameters will be used to simultaneously transmit the PUSCH communication using the multiple antenna modules.

[0203] Clause 4: A method according to any one of clauses 1 to 3, wherein the first value of the indication indicates that the PUSCH communication will be sent using the first antenna module using the first sounding reference signal (SRS) resource set, or the second value of the indication indicates that the PUSCH communication will be sent using the multiple antenna modules using the first SRS resource set and the second SRS resource set.

[0204] Clause 5: A method according to any one of clauses 1 to 4, wherein the indication indicates a specific communication scheme used to send the PUSCH communication, wherein the specific communication scheme is one of the following: the SFN communication scheme, the time division multiplexing (TDM) communication scheme, the space division multiplexing (SDM) communication scheme, the frequency division multiplexing (FDM) communication scheme or the single transmit receive point (TRP) communication scheme.

[0205] Clause 6: The method of clause 5, wherein the indication indicates a switching arrangement associated with the particular communication scheme.

[0206] Clause 7: A method as described in any of clauses 1 to 6, wherein the indication is based at least in part on a configuration of at least one of the SFN communication scheme, a first sounding reference signal (SRS) resource set, or a second SRS resource set.

[0207] Clause 8: The method of clause 7, wherein the configuration is specific to a bandwidth portion, a carrier, or a configuration grant.

[0208] Clause 9: The method of clause 7, wherein the configuration is specific to a DCI format.

[0209] Clause 10: The method of clause 7, wherein the configuration indication includes a plurality of communication schemes of the SFN communication scheme, and wherein the indication indicates a selected communication scheme of the plurality of communication schemes.

[0210] Clause 11: A method as described in any of clauses 1 to 10, the method further comprising sending capability information indicating that the UE supports the SFN communication scheme.

[0211] Clause 12: The method of clause 11, wherein the capability information is specific to a frequency band, a UE, a frequency band combination, or a feature set.

[0212] Clause 13: A method of wireless communication performed by a network entity, the method comprising: sending downlink control information (DCI), the DCI comprising an indication for sending a physical uplink shared channel (PUSCH) communication associated with the DCI using a single frequency network (SFN) communication scheme, in which each layer of the PUSCH communication is simultaneously sent using multiple antenna modules of a user equipment (UE); and receiving the PUSCH communication based on the DCI.

[0213] Clause 14: A method according to clause 13, wherein the indication indicates whether the PUSCH communication will be sent using a first sounding reference signal (SRS) resource set using a first antenna module among the multiple antenna modules, using a second SRS resource set using a second antenna module among the multiple antenna modules, or using both the first SRS resource set and the second SRS resource set from the first antenna module and the second module.

[0214] Clause 15: A method according to any one of clauses 13 to 14, wherein the first value of the indication indicates that a first set of transmission parameters will be used to simultaneously transmit the PUSCH communications using the multiple antenna modules, or the second value of the indication indicates that a second set of transmission parameters will be used to simultaneously transmit the PUSCH communications using the multiple antenna modules.

[0215] Clause 16: A method according to any one of clauses 13 to 15, wherein the first value of the indication indicates that the PUSCH communication will be sent using the first antenna module using the first sounding reference signal (SRS) resource set, or the second value of the indication indicates that the PUSCH communication will be sent using the multiple antenna modules using the first SRS resource set and the second SRS resource set.

[0216] Clause 17: A method according to any one of clauses 13 to 16, wherein the indication indicates a specific communication scheme used to send the PUSCH communication, wherein the specific communication scheme is one of the following: the SFN communication scheme, the time division multiplexing (TDM) communication scheme, the space division multiplexing (SDM) communication scheme, the frequency division multiplexing (FDM) communication scheme or the single transmit receive point (TRP) communication scheme.

[0217] Clause 18: The method of clause 17, wherein the indication indicates a switching arrangement associated with the particular communication scheme.

[0218] Clause 19: A method as set forth in any of clauses 13 to 18, wherein the indication is based at least in part on a configuration of at least one of the SFN communication scheme, a first sounding reference signal (SRS) resource set, or a second SRS resource set.

[0219] Clause 20: The method of clause 19, wherein the configuration is specific to a bandwidth portion, a carrier, or a configuration grant.

[0220] Clause 21: The method of clause 19, wherein the configuration is specific to a DCI format.

[0221] Clause 22: The method of clause 19, wherein the configuration indication includes a plurality of communication schemes of the SFN communication scheme, and wherein the indication indicates a selected communication scheme of the plurality of communication schemes.

[0222] Clause 23: A method as described in any of clauses 13 to 22, the method further comprising receiving capability information indicating that the UE supports the SFN communication scheme, wherein the DCI is based at least in part on the capability information.

[0223] Clause 24: A method as described in clause 23, wherein the capability information is specific to a frequency band, a UE, a frequency band combination, or a feature set.

[0224] Clause 25: An apparatus comprising: a memory including processor-executable instructions; and a processor configured to execute the processor-executable instructions and cause the apparatus to perform the method of any one of clauses 1 to 23.

[0225] Clause 26: An apparatus comprising means for performing the method according to any one of clauses 1 to 23.

[0226] Clause 27: A non-transitory computer readable medium comprising executable instructions which, when executed by a processor of an apparatus, cause the apparatus to perform the method of any one of clauses 1 to 23.

[0227] Clause 28: A computer program product embodied on a computer readable storage medium, the computer program product comprising code for performing the method according to any one of clauses 1 to 23.

[0228] Additional considerations

[0229] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. The examples discussed herein are not limited to the scope, applicability or aspects set forth in the claims. 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. For example, without departing from the scope of the present disclosure, the functions and arrangements of the elements discussed may be changed. Various examples may ignore, replace or add various procedures or components as appropriate. For example, the described method may be performed in an order different from the order described, and various actions may be added, omitted or combined. In addition, features equivalent to some example descriptions may be combined in some other examples. For example, any number of aspects set forth herein may be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such devices or methods practiced using other structures, functions, or structures and functions that are supplementary or alternative to the various aspects of the present disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of the present invention.

[0230] The various illustrative logical blocks, modules, and circuits described in conjunction with the present disclosure may be implemented or performed using a general purpose processor, a digital signal processor (DSP), an ASIC, a field programmable gate array (FPGA) or other programmable logic device (PLD), discrete gate or transistor logic, discrete hardware components, or any combination thereof, designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in an alternative, the processor may be any commercially available processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, a system on a chip (SoC), or any other such configuration).

[0231] As used herein, a phrase referring to "at least one of" a list of items refers to any combination of those items (including single members). As an example, "at least one of a, b, or c" is intended to cover: a, b, c, ab, ac, bc, and abc, as well as any combination with multiple of the same elements (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbc, cc, and ccc, or any other ordering of a, b, and c).

[0232] As used herein, the term "determine" encompasses a wide variety of actions. For example, "determine" may include calculating, computing, processing, deriving, investigating, searching (e.g., searching in a table, a database, or another data structure), ascertaining, etc. In addition, "determine" may include receiving (e.g., receiving information), accessing (e.g., accessing data in a memory), etc. In addition, "determine" may include resolving, selecting, choosing, establishing, etc.

[0233] The method disclosed herein includes one or more actions for implementing the method. The method actions are interchangeable with each other without departing from the scope of the claims. In other words, unless a specific order of actions is specified, the order and / or use of specific actions may be modified without departing from the scope of the claims. In addition, the various operations of the method described above may be performed by any appropriate component capable of performing the corresponding function. The component may include various hardware and / or software components and / or modules, including but not limited to circuits, application specific integrated circuits (ASICs) or processors.

[0234] The following claims are not intended to be limited to the various aspects shown herein, but should be given the full scope consistent with the language of the claims. Within the claims, unless otherwise specified, reference to an element in the singular form is not intended to mean "one and only one", but "one or more". Unless otherwise specified, the term "some" refers to one or more. Any claim element is not interpreted according to the provisions of 35 U.S.C. § 112 (f) unless the element is explicitly stated using the phrase "parts for...". All structural and functional equivalents of the elements of the various aspects described throughout the present disclosure that are known or will be known later to a person of ordinary skill in the art are expressly incorporated herein by reference and are intended to be covered by the claims. In addition, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is explicitly stated in the claims.

Claims

1. A method of wireless communication performed by a user equipment (UE), the method comprising: receiving downlink control information (DCI), the DCI including an indication to transmit a physical uplink shared channel (PUSCH) communication associated with the DCI using a single frequency network (SFN) communication scheme in which each layer of the PUSCH communication is transmitted simultaneously using multiple antenna modules of the UE; and The PUSCH communication is sent according to the DCI.

2. The method of claim 1 , wherein the indication indicates whether the PUSCH communication will be sent using a first sounding reference signal (SRS) resource set using a first antenna module among the multiple antenna modules, using a second SRS resource set using a second antenna module among the multiple antenna modules, or using both the first SRS resource set and the second SRS resource set using the first antenna module and the second antenna module.

3. The method of claim 1 , wherein the first value of the indication indicates that a first set of transmission parameters is to be used for simultaneously transmitting the PUSCH communications using the multiple antenna modules, or the second value of the indication indicates that a second set of transmission parameters is to be used for simultaneously transmitting the PUSCH communications using the multiple antenna modules.

4. The method of claim 1 , wherein a first value of the indication indicates that the PUSCH communication will be sent using a first sounding reference signal (SRS) resource set using a first antenna module, or a second value of the indication indicates that the PUSCH communication will be sent using the first and second SRS resource sets using the multiple antenna modules.

5. The method of claim 1, wherein the indication indicates a specific communication scheme for sending the PUSCH communication, wherein the specific communication scheme is one of: The SFN communication scheme, Time Division Multiplexing (TDM) communication scheme, Space Division Multiplexing (SDM) communication scheme, Frequency Division Multiplexing (FDM) communication scheme, or Single Transmit Receive Point (TRP) communication scheme. The method of claim 5 , wherein the indication indicates a switching arrangement associated with the particular communication scheme.

7. The method of claim 1, wherein the indication is based at least in part on a configuration of at least one of the SFN communication scheme, a first sounding reference signal (SRS) resource set, or a second SRS resource set.

8. The method of claim 7, wherein the configuration is specific to a bandwidth portion, a carrier, or a configuration grant.

9. The method of claim 7, wherein the configuration is specific to a DCI format.

10. The method of claim 7, wherein the configuration indication includes a plurality of communication schemes of the SFN communication scheme, and wherein the indication indicates a selected communication scheme of the plurality of communication schemes.

11. The method according to claim 1, further comprising sending capability information indicating that the UE supports the SFN communication scheme.

12. The method of claim 11, wherein the capability information is specific to a frequency band, a UE, a frequency band combination, or a feature set.

13. A method of wireless communication performed by a network entity, the method comprising: transmitting downlink control information (DCI), the DCI including an indication to transmit a physical uplink shared channel (PUSCH) communication associated with the DCI using a single frequency network (SFN) communication scheme in which each layer of the PUSCH communication is transmitted simultaneously using multiple antenna modules of a user equipment (UE); and The PUSCH communication is received according to the DCI.

14. The method of claim 13, wherein the indication indicates whether the PUSCH communication will be sent using a first sounding reference signal (SRS) resource set using a first antenna module among the multiple antenna modules, using a second SRS resource set using a second antenna module among the multiple antenna modules, or using both the first SRS resource set and the second SRS resource set using the first antenna module and the second antenna module.

15. The method of claim 13, wherein the first value of the indication indicates that a first set of transmission parameters is to be used for simultaneously transmitting the PUSCH communications using the multiple antenna modules, or the second value of the indication indicates that a second set of transmission parameters is to be used for simultaneously transmitting the PUSCH communications using the multiple antenna modules.

16. A method according to claim 13, wherein the first value of the indication indicates that the PUSCH communication will be sent using the first antenna module using the first sounding reference signal (SRS) resource set, or the second value of the indication indicates that the PUSCH communication will be sent using the multiple antenna modules using the first SRS resource set and the second SRS resource set.

17. The method of claim 13, wherein the indication indicates a specific communication scheme for sending the PUSCH communication, wherein the specific communication scheme is one of: The SFN communication scheme, Time Division Multiplexing (TDM) communication scheme, Space Division Multiplexing (SDM) communication scheme, Frequency Division Multiplexing (FDM) communication scheme, or Single Transmit Receive Point (TRP) communication scheme.

18. The method of claim 17, wherein the indication indicates a switching arrangement associated with the particular communication scheme.

19. The method of claim 13, wherein the indication is based at least in part on a configuration of at least one of the SFN communication scheme, a first sounding reference signal (SRS) resource set, or a second SRS resource set.

20. The method of claim 19, wherein the configuration is specific to a bandwidth portion, a carrier, or a configuration grant.

21. The method of claim 19, wherein the configuration is specific to a DCI format.

22. The method of claim 19, wherein the configuration indication includes a plurality of communication schemes of the SFN communication scheme, and wherein the indication indicates a selected communication scheme of the plurality of communication schemes.

23. The method of claim 13, further comprising receiving capability information indicating that the UE supports the SFN communication scheme, wherein the DCI is based at least in part on the capability information.

24. The method of claim 23, wherein the capability information is specific to a frequency band, a UE, a frequency band combination, or a feature set.

25. A user equipment (UE) configured for wireless communication, the user equipment (UE) comprising: a memory including processor-executable instructions; and a processor configured to execute the processor-executable instructions and cause the UE to: receiving downlink control information (DCI), the DCI including an indication to transmit a physical uplink shared channel (PUSCH) communication associated with the DCI using a single frequency network (SFN) communication scheme in which each layer of the PUSCH communication is transmitted simultaneously using multiple antenna modules of the UE; and The PUSCH communication is sent according to the DCI.

26. A network entity configured for wireless communication, the network entity comprising: a memory including processor-executable instructions; and a processor configured to execute the processor-executable instructions and cause the network entity to: transmitting downlink control information (DCI), the DCI including an indication to transmit a physical uplink shared channel (PUSCH) communication associated with the DCI using a single frequency network (SFN) communication scheme in which each layer of the PUSCH communication is transmitted simultaneously using multiple antenna modules of a user equipment (UE); and The PUSCH communication is received according to the DCI.

Images