PTRS design for single DCI simultaneous PUSCH transmission with SDM or SFN

Abstract

In one aspect, a base station includes a transceiver configured to communicate with a user equipment (UE). The base station also includes a processor communicatively coupled to the transceiver and configured to perform operations including: transmitting, by the network, a downlink control information (DCI) signal to the UE, the DCI including an indication associated with UE operation with simultaneous transmission (STxMP) across multiple panels using a single frequency network (SFN) or using space division multiplexing (SDM); and communicating with the UE based on a maximum number of layers associated with the indication.

Description

Technical Field

[0001] This disclosure relates generally to wireless technology, and more specifically to the design of a phase tracking reference signal (PTRS) for transmitting a single downlink control information (DCI) while simultaneously transmitting a physical uplink shared channel (PUSCH) using spatial division multiplexing (SDM) or a single-frequency network (SFN). Background Technology

[0002] Fifth-generation mobile networks (5G) are wireless standards designed to improve data transmission speed, reliability, availability, and other aspects. Wireless standards include numerous processes that can be implemented by transmitting or receiving devices to improve the latency, speed, and reliability of uplink and downlink transmissions. Summary of the Invention

[0003] Various aspects of this disclosure relate to 5G new radios (NR) that operate in licensed spectrum or in shared and unlicensed spectrum (NR-U).

[0004] In one aspect of this disclosure, a method performed by a network coupled to a user equipment (UE) includes sending downlink control information (DCI) signals from the network to the UE, the DCI including an indication associated with UE operation under simultaneous transmission across multiple panels using spatial multiplexing (SDM) (STxMP); and communicating with the UE based on a maximum number of layers associated with the indication.

[0005] In one aspect, a method performed by a user equipment (UE) coupled to a network includes the UE receiving downlink control information (DCI) signals from the network, the DCI including an indication associated with UE operation under simultaneous transmission across multiple panels using spatial multiplexing (SDM) (STxMP); and communicating with the network based on the maximum number of layers associated with the indication.

[0006] In one aspect, a method performed by a network coupled to a user equipment (UE) includes the network sending downlink control information (DCI) signals to the UE, the DCI including an indication associated with UE operation under simultaneous transmission across multiple panels using a single-frequency network (SFN) (STxMP); and communicating with the UE based on the maximum number of layers associated with the indication.

[0007] In one aspect, a method performed by a user equipment (UE) coupled to a network includes the UE receiving downlink control information (DCI) signals from the network, the DCI including an indication associated with UE operation under simultaneous transmission across multiple panels using a single-frequency network (SFN) (STxMP); and communicating with the network based on a maximum number of layers associated with the indication.

[0008] In one aspect, a base station includes a transceiver configured to communicate with a user equipment (UE); and a processor communicatively coupled to the transceiver and configured to perform the methods described herein from a network perspective.

[0009] In one respect, the UE's processor (e.g., the baseband processor) is configured to execute the methods described herein from the UE's perspective.

[0010] Other technical features will be apparent to those skilled in the art from the following figures, description and claims. Attached Figure Description

[0011] The above and other objects, features and advantages of this disclosure will become more apparent from a more detailed description of some embodiments thereof in the accompanying drawings, wherein:

[0012] Figure 1 An example wireless communication system is illustrated based on some aspects.

[0013] Figure 2 Examples of uplink and downlink communication based on some aspects are given.

[0014] Figure 3 Example block diagrams of a UE based on some aspects are shown.

[0015] Figure 4 Example block diagrams of BS based on some aspects are shown.

[0016] Figure 5 An example block diagram of a cellular communication circuit is shown, based on some aspects.

[0017] Figure 6 An example of a UE that transmits simultaneously using a PUSCH with multiple panels is shown.

[0018] Figure 7 An example of a configuration for an uplink phase tracking reference signal (UL PTRS) is shown.

[0019] Figure 8 An example diagram illustrating the dynamic switching between SDM STxMP and sTRP according to some implementation schemes is shown.

[0020] Figure 9 An example diagram illustrating the dynamic switching between SFN STxMP and sTRP according to some implementation schemes is shown. Detailed Implementation

[0021] A method and apparatus for performing operations between user equipment (UE) and a network are described. Numerous specific details are set forth in the following description to provide a thorough explanation of aspects of the invention. However, it will be apparent to those skilled in the art that aspects of the invention may be practiced without these specific details. In other instances, well-known components, structures, and techniques have not been shown in detail so as not to obscure the understanding of this description.

[0022] In this specification, the phrase "some aspects" or "aspect" means that a particular feature, structure, or characteristic described in connection with that aspect may be included in at least one aspect of the invention. The phrase "some aspects" appearing in various places throughout this specification does not necessarily refer to the same aspect.

[0023] In the following description and claims, the terms “coupled” and “connected” and their derivatives may be used. “Coupled” is used to mean that two or more elements may or may not be in direct physical or electrical contact with each other, cooperating or interacting with each other. “Connected” is used to mean the establishment of communication between two or more coupled elements.

[0024] The processes illustrated in the following figures are executed by processing logic, which includes hardware (e.g., circuitry, special-purpose logic, etc.), software (such as software running on a general-purpose computer system or a special-purpose machine), or a combination of both. While these processes are described below in a certain order, it should be understood that some of the described operations may be performed in a different order. Furthermore, some operations may be performed in parallel rather than sequentially.

[0025] The terms “server,” “client,” and “device” are intended to refer generally to a data processing system, rather than to specific constituent elements of a server, client, and / or device.

[0026] Figure 1 A simplified example of a wireless communication system is illustrated based on some aspects. It should be noted that... Figure 1 The system described is merely one example of a possible system, and the features of this disclosure can be implemented in any of a variety of systems as needed.

[0027] As shown in the figure, the example wireless communication system includes a base station 102A, which communicates with one or more user equipments 106A, 106B to 106N, etc., via a transmission medium. Each user equipment may be referred to as a "user equipment" (UE).

[0028] Base station (BS) 102A may be a transceiver base station (BTS) or a cell site (“cellular base station”), and may include hardware that enables wireless communication with UE 106A to UE 106N.

[0029] The communication area (or coverage area) of a base station may be referred to as a "cell". Base station 102A and UE 106 can be configured to communicate via a transmission medium using any of a variety of Radio Access Technologies (RATs), also known as wireless communication technologies or telecommunications standards, such as GSM, UMTS (associated with air interfaces such as WCDMA or TD-SCDMA), LTE, LTE-Advanced (LTE-A), 5G New Radio (5G NR), HSPA, 3GPP2 CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), etc. Note that if base station 102A is implemented in an LTE environment, it may alternatively be referred to as an "eNodeB" or "eNB". Note that if base station 102A is implemented in a 5G NR context, it may alternatively be referred to as a "gNodeB" or "gNB".

[0030] As shown in the figure, base station 102A can also be configured to communicate with network 100 (e.g., in various possibilities, the core network of a cellular service provider, telecommunications networks such as the Public Switched Telephone Network (PSTN), and / or the Internet). Therefore, base station 102A facilitates communication between user equipments and / or between user equipments and network 100. Specifically, cellular base station 102A can provide UE 106 with various telecommunications capabilities, such as voice, SMS, and / or data services.

[0031] Base station 102A and other similar base stations (such as base station 102B...102N) operating under the same or different cellular communication standards can thus provide a network as a cell that can provide continuous or near-continuous overlapping services to UE 106A to 106N and similar devices over a geographical area via one or more cellular communication standards.

[0032] Therefore, although base station 102A can act as such Figure 1 The example illustrates the "serving cells" of UEs 106A to 106N, but each UE 106 may also be able to receive signals (and possibly within its communication range) from one or more other cells (which may be provided by base stations 102B to 102N and / or any other base stations), which may be referred to as "neighboring cells." Such cells may also facilitate communication between user equipments and / or between user equipments and network 100. These cells may include "macro" cells, "micro" cells, "pecimen" cells, and / or any other cells of various other granularities providing service area size. For example, in... Figure 1 Base stations 102A to 102B illustrated can be macro cells, while base station 102N can be a micro cell. Other configurations are also possible.

[0033] In some respects, base station 102A may be a next-generation base station, such as a 5G New Radio (5G NR) base station or a “gNB”. In some respects, the gNB may connect to a legacy evolved packet core (EPC) network and / or to an NR core (NRC) network. Furthermore, a gNB cell may include one or more transition and receive points (TRPs). Additionally, a UE capable of operating according to 5G NR may be connected to one or more TRPs within one or more gNBs.

[0034] It should be noted that UE 106 may be able to communicate using multiple wireless communication standards. For example, in addition to at least one cellular communication protocol (e.g., GSM, UMTS (associated with, for example, WCDMA or TD-SCDMA air interfaces), LTE, LTE-A, 5G NR, HSPA, 3GPP2 CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD, etc.), UE 106 may be configured to communicate using wireless networking (e.g., Wi-Fi) and / or peer-to-peer wireless communication protocols (e.g., Bluetooth, Wi-Fi peer-to-peer, etc.). If desired, UE 106 may also be configured, or alternatively, to communicate using one or more Global Navigation Satellite Systems (GNSS, such as GPS or GLONASS), one or more mobile television broadcasting standards (e.g., ATSC-M / H or DVB-H), and / or any other wireless communication protocol. Other combinations of wireless communication standards (including more than two wireless communication standards) are also possible.

[0035] Figure 2 An example is shown of a UE 106A that can communicate with base station 102 via uplink and downlink communication, according to some aspects. The UE can be a cellular communication-capable device, such as a mobile phone, handheld device, computer, tablet computer, or virtually any type of wireless device.

[0036] The UE may include a processor configured to execute program instructions stored in memory. The UE may perform any of the method aspects described herein by executing such stored instructions. Alternatively or additionally, the UE may include programmable hardware elements, such as an FPGA (Field Programmable Gate Array) configured to perform any of the method aspects described herein or any portion thereof.

[0037] The UE may include one or more antennas for communicating using one or more wireless communication protocols or technologies. In some aspects, the UE may be configured to communicate using, for example, CDMA2000 (1xRTT / 1xEV-DO / HRPD / eHRPD) or LTE using a single shared radio component and / or GSM or LTE using a single shared radio component. The shared radio component may be coupled to a single antenna or to multiple antennas (e.g., for MIMO) for performing wireless communication. Generally, the radio component may include any combination of baseband processors, analog RF signal processing circuitry (e.g., including filters, mixers, oscillators, amplifiers, etc.) or digital processing circuitry (e.g., for digital modulation and other digital processing). Similarly, the radio component may use the aforementioned hardware to implement one or more receive chains and transmit chains. For example, UE 106 may share one or more portions of the receive chain and / or transmit chain among various wireless communication technologies (such as those discussed above).

[0038] In some aspects, the UE may include separate transmit and / or receive chains (e.g., including separate antennas and other radio components) for each wireless communication protocol configured to communicate with it. As another possibility, the UE may include one or more radio components shared among multiple wireless communication protocols, as well as one or more radio components used uniquely by a single wireless communication protocol. For example, the UE may include shared radio components for communicating using either LTE or 5G NR (or LTE or 1xRTT, or LTE or GSM), and separate radio components for communicating using each of Wi-Fi and Bluetooth. Other configurations are also possible.

[0039] Figure 3 A simplified block diagram illustrating a communication device 106 according to some aspects is shown. Note that... Figure 3 The block diagram of the communication device is merely one example of possible communication devices. Depending on the aspects, among other devices, the communication device 106 may be a UE device, a mobile device or mobile station, a wireless device or wireless station, a desktop computer or computing device, a mobile computing device (e.g., a laptop, notebook, or portable computing device), a tablet computer, and / or a combination of devices. As shown, the communication device 106 may include a set of components 300 configured to perform core functions. For example, this set of components may be implemented as a system-on-a-chip (SOC), which may include portions for various purposes. Alternatively, the set of components 300 may be implemented as individual components or groups of components for various purposes. The set of components 300 may be (e.g., communicatively; directly or indirectly) coupled to various other circuitry of the communication device 106.

[0040] For example, communication device 106 may include various types of memory (e.g., including NAND flash memory 310), input / output interfaces such as connector I / F 320 (e.g., for connection to a computer system; docking station; charging station; input devices such as microphone, camera, keyboard; output devices such as speaker; etc.), a display 360 that can be integrated with or external to the communication device 106, and cellular communication circuitry 330 such as for 5G NR, LTE, GSM, etc., and short- to medium-range wireless communication circuitry 329 (e.g., Bluetooth). ™ (And WLAN circuitry). In some aspects, communication device 106 may include wired communication circuitry (not shown), such as, for example, a network interface card for Ethernet.

[0041] Cellular communication circuitry 330 may be coupled (e.g., communicatively; directly or indirectly) to one or more antennas, such as antennas 335 and 336 shown. Short-to-medium-range wireless communication circuitry 329 may also be coupled (e.g., communicatively; directly or indirectly) to one or more antennas, such as antennas 337 and 338 shown. Alternatively, short-to-medium-range wireless communication circuitry 329 may be coupled (e.g., communicatively; directly or indirectly) to antennas 335 and 336 in addition to or instead of being coupled to antennas 337 and 338. Short-to-medium-range wireless communication circuitry 329 and / or cellular communication circuitry 330 may include multiple receive chains and / or multiple transmit chains for receiving and / or transmitting multiple spatial streams, such as in a multiple-input multiple-output (MIMO) configuration.

[0042] In some aspects, as further described below, the cellular communication circuit 330 may include dedicated receive chains for multiple radio access technologies (RATs) (including and / or coupled to (e.g., a communication ground; directly or indirectly) a dedicated processor and / or radio components) (e.g., a first receive chain for LTE and a second receive chain for 5G-NR). Furthermore, in some aspects, the cellular communication circuit 330 may include a single transmit chain that can be switched between radio components dedicated to a particular RAT. For example, a first radio component may be dedicated to a first RAT, such as LTE, and may communicate with a dedicated receive chain and a transmit chain shared with additional radio components, such as a second radio component that may be dedicated to a second RAT (e.g., 5G NR) and may communicate with a dedicated receive chain and a shared transmit chain.

[0043] The communication device 106 may also include one or more user interface elements and / or be configured to be used with one or more user interface elements. The user interface elements may include any of a variety of elements such as a display 360 (which may be a touch screen display), a keyboard (which may be a separate keyboard or may be implemented as part of a touch screen display), a mouse, a microphone and / or a speaker, one or more cameras, one or more buttons, and / or any of a variety of other elements capable of providing information to the user and / or receiving or interpreting user input.

[0044] The communication device 106 may also include one or more smart cards 345 with SIM (Subscriber Identity Module) functionality, such as one or more UICC (Universal Integrated Circuit Card) 345.

[0045] As shown in the figure, the SOC 300 may include a processor 302 and a display circuit 304. The processor executes program instructions of the communication device 106, and the display circuit performs graphics processing and provides display signals to the display 360. The processor 302 may also be coupled to a memory management unit (MMU) 340 (which may be configured to receive addresses from the processor 302 and translate those addresses into locations in memory (e.g., memory 306, read-only memory (ROM) 350, NAND flash memory 310)) and / or coupled to other circuitry or devices (such as the display circuit 304, short-range wireless communication circuitry 229, cellular communication circuitry 330, connector I / F 320, and / or display 360). The MMU 340 may be configured to perform memory protection and page table translation or setup. In some aspects, the MMU 340 may be included as part of the processor 302.

[0046] As noted above, communication device 106 can be configured to communicate using wireless and / or wired communication circuits. Communication device 106 can also be configured to determine physical downlink shared channel scheduling resources for user equipment and base stations. Furthermore, communication device 106 can be configured to select and group CCs from the wireless link, and determine virtual CCs from the selected CC groups. The wireless device can also be configured to perform physical downlink resource mapping based on an aggregation resource matching mode for CC groups.

[0047] As described herein, communication device 106 may include hardware and software components for implementing the aforementioned features for determining physical downlink shared channel scheduling resources for communication device 106 and a base station. For example, by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium), processor 302 of communication device 106 may be configured to implement some or all of the features described herein. Alternatively (or in addition), processor 302 may be configured as a programmable hardware element such as a FPGA (Field-Programmable Gate Array) or as an ASIC (Application-Specific Integrated Circuit). Alternatively (or in addition), in conjunction with one or more of other components 300, 304, 306, 310, 320, 329, 330, 340, 345, 350, 360, processor 302 of communication device 106 may be configured to implement some or all of the features described herein.

[0048] Furthermore, as described herein, processor 302 may include one or more processing elements. Therefore, processor 302 may include one or more integrated circuits (ICs) configured to perform the functions of processor 302. Additionally, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of one or more processors 302.

[0049] Furthermore, as described herein, both the cellular communication circuit 330 and the short-range wireless communication circuit 329 may include one or more processing elements. In other words, one or more processing elements may be included in the cellular communication circuit 330, and similarly, one or more processing elements may be included in the short-range wireless communication circuit 329. Therefore, the cellular communication circuit 330 may include one or more integrated circuits (ICs) configured to perform the functions of the cellular communication circuit 330. Furthermore, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of the wireless communication circuit 330. Similarly, the short-range wireless communication circuit 329 may include one or more ICs configured to perform the functions of the short-range wireless communication circuit 329. Furthermore, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of the short-range wireless communication circuit 329.

[0050] Figure 4 An example block diagram of base station 102 is shown, illustrating some aspects. It should be noted that... Figure 4The base station shown is merely one example of a possible base station. As illustrated, base station 102 may include processor 404, which executes program instructions for base station 102. Processor 404 may also be coupled to memory management unit (MMU) 440, which may be configured to receive addresses from processor 404 and translate these addresses into locations in memory (e.g., memory 460 and read-only memory (ROM) 450), or to other circuitry or devices.

[0051] Base station 102 may include at least one network port 470. Network port 470 may be configured to couple to a telephone network and provide access rights as described above. Figure 1 and Figure 2 The telephone network described herein includes multiple devices such as UE device 106.

[0052] Network port 470 (or an additional network port) may also be configured, or alternatively configured, to couple to a cellular network, such as the core network of a cellular service provider. The core network may provide mobility-related services and / or other services to multiple devices, such as UE device 106. In some cases, network port 470 may be coupled to a telephone network via the core network, and / or the core network may provide a telephone network (e.g., in other UE devices served by a cellular service provider).

[0053] In some respects, base station 102 may be a next-generation base station, such as a 5G New Radio (5G NR) base station or a “gNB”. In such respects, base station 102 may connect to a legacy evolved packet core (EPC) network and / or to an NR core (NRC) network. Furthermore, base station 102 may be considered a 5G NR cell and may include one or more transition and receive points (TRPs). Additionally, UEs capable of operating according to 5G NR may be connected to one or more TRPs within one or more gNBs. In some respects, the base station may operate in 5G NR-U mode.

[0054] Base station 102 may include at least one antenna 434, and may include multiple antennas. At least one antenna 434 may be configured to operate as a wireless transceiver and may be further configured to communicate with UE device 106 via radio component 430. Antenna 434 communicates with radio component 430 via communication link 432. Communication link 432 may be a receive link, a transmit link, or both. Radio component 430 may be configured to communicate via various wireless communication standards, including but not limited to 5G NR, 5G NR-U, LTE, LTE-A, GSM, UMTS, CDMA2000, Wi-Fi, etc.

[0055] Base station 102 can be configured to perform wireless communication using multiple wireless communication standards. In some instances, base station 102 may include multiple radio components that enable base station 102 to communicate according to multiple wireless communication technologies. For example, as one possibility, base station 102 may include an LTE radio component for performing communication according to LTE and a 5G NR radio component for performing communication according to 5G NR and 5G NR-U. In this case, base station 102 may be able to operate as both an LTE base station and a 5G NR base station. As another possibility, base station 102 may include a multimode radio component capable of performing communication according to any of multiple wireless communication technologies (e.g., 5G NR and Wi-Fi, LTE and Wi-Fi, LTE and UMTS, LTE and CDMA2000, UMTS and GSM, etc.).

[0056] As further described herein, BS 102 may include hardware and software components for implementing or supporting specific implementations of the features described herein. The processor 404 of base station 102 may be configured, for example, to implement or support some or all of the methods described herein by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively, processor 404 may be configured as a programmable hardware element such as a FPGA (Field-Programmable Gate Array), or as an ASIC (Application-Specific Integrated Circuit), or a combination thereof. Alternatively (or in addition), in conjunction with one or more of other components 430, 432, 434, 440, 450, 460, 470, the processor 404 of BS 102 may be configured to implement or support implementations of some or all of the features described herein.

[0057] Furthermore, as described herein, processor 404 may comprise one or more processing elements. In other words, one or more processing elements may be included in processor 404. Therefore, processor 404 may include one or more integrated circuits (ICs) configured to perform the functions of processor 404. Additionally, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of one or more processors 404.

[0058] Furthermore, as described herein, radio component 430 may comprise one or more processing elements. In other words, radio component 430 may include one or more processing elements. Therefore, radio component 430 may include one or more integrated circuits (ICs) configured to perform the functions of radio component 430. Additionally, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of radio component 430.

[0059] Figure 5 A simplified block diagram illustrating an example of a cellular communication circuit based on some aspects is shown. Note that... Figure 5 The block diagram of the cellular communication circuit is merely one example of a possible cellular communication circuit. Depending on the aspects, the cellular communication circuit 330 may be included in a communication device such as the communication device 106 described above. As noted above, among other devices, the communication device 106 may be a user equipment (UE) device, a mobile device or mobile station, a wireless device or wireless station, a desktop computer or computing device, a mobile computing device (e.g., a laptop computer, notebook computer, or portable computing device), a tablet computer, and / or a combination of devices.

[0060] Cellular communication circuit 330 may (e.g., communicatively; directly or indirectly) be coupled to one or more antennas, such as ( Figure 3 Antennas 335 ab and 336 are shown in the diagram. In some aspects, the cellular communication circuitry 330 may include dedicated receive chains for multiple RATs (including and / or coupled to (e.g., communication ground; directly or indirectly) dedicated processors and / or radio components) (e.g., a first receive chain for LTE and a second receive chain for 5G NR). For example, as... Figure 5 As shown, the cellular communication circuit 330 may include a modem 510 and a modem 520. The modem 510 may be configured for communication according to a first RAT (e.g., such as LTE or LTE-A), and the modem 520 may be configured for communication according to a second RAT (e.g., such as 5G NR).

[0061] As shown, modem 510 may include one or more processors 512 and memory 516 communicating with processors 512. Modem 510 may communicate with radio frequency (RF) front end 530. RF front end 530 may include circuitry for transmitting and receiving radio signals. For example, RF front end 530 may include receiver circuitry (RX) 532 and transmitter circuitry (TX) 534. In some aspects, receiver circuitry 532 may communicate with downlink (DL) front end 550, which may include circuitry for receiving radio signals via antenna 335a.

[0062] Similarly, modem 520 may include one or more processors 522 and memory 526 communicating with processor 522. Modem 520 may communicate with RF front end 540. RF front end 540 may include circuitry for transmitting and receiving radio signals. For example, RF front end 540 may include receiving circuitry 542 and transmitting circuitry 544. In some aspects, receiving circuitry 542 may communicate with DL front end 560, which may include circuitry for receiving radio signals via antenna 335b.

[0063] In some aspects, switch 570 may couple transmitting circuitry 534 to uplink (UL) front-end 572. Additionally, switch 570 may couple transmitting circuitry 544 to UL front-end 572. UL front-end 572 may include circuitry for transmitting radio signals via antenna 336. Therefore, when cellular communication circuitry 330 receives an instruction to transmit according to a first RAT (e.g., supported by modem 510), switch 570 may be switched to a first state allowing modem 510 to transmit signals according to the first RAT (e.g., via a transmission chain including transmitting circuitry 534 and UL front-end 572). Similarly, when cellular communication circuitry 330 receives an instruction to transmit according to a second RAT (e.g., supported by modem 520), switch 570 may be switched to a second state allowing modem 520 to transmit signals according to the second RAT (e.g., via a transmission chain including transmitting circuitry 544 and UL front-end 572).

[0064] As described herein, modem 510 may include hardware and software components for implementing the features described above or for determining a physical downlink shared channel for user equipment and base stations, as well as for various other technologies described herein. For example, processor 512 may be configured to implement some or all of the features described herein by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively (or otherwise), processor 512 may be configured as a programmable hardware element such as a FPGA (Field-Programmable Gate Array) or as an ASIC (Application-Specific Integrated Circuit). Alternatively (or otherwise), processor 512 may be configured to implement some or all of the features described herein in conjunction with one or more of other components 530, 532, 534, 550, 570, 572, 335, and 336.

[0065] Furthermore, as described herein, processor 512 may include one or more processing elements. Therefore, processor 512 may include one or more integrated circuits (ICs) configured to perform the functions of processor 512. Additionally, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of processor 512.

[0066] As described herein, modem 520 may include hardware and software components for implementing the features described above to determine physical downlink shared channel scheduling resources for user equipment equipment and base stations, as well as for various other technologies described herein. For example, processor 522 may be configured to implement some or all of the features described herein by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable storage medium). Alternatively (or otherwise), processor 522 may be configured as a programmable hardware element such as a FPGA (Field-Programmable Gate Array) or as an ASIC (Application-Specific Integrated Circuit). Alternatively (or otherwise), processor 522 may be configured to implement some or all of the features described herein in conjunction with one or more of other components 540, 542, 544, 550, 570, 572, 335, and 336.

[0067] Furthermore, as described herein, processor 522 may include one or more processing elements. Therefore, processor 522 may include one or more integrated circuits (ICs) configured to perform the functions of processor 522. Additionally, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of processor 522.

[0068] 5G supports multi-antenna transmission, beamforming, and simultaneous transmission from multiple geographically separated sites. The channels associated with different antenna ports of the UE can differ, for example, in terms of radio channel attributes. QCL antenna ports can be geographically separated.

[0069] 5G physical channels provide flexible communication between 5G base stations and UEs. 5G NR has specified physical channels for 5G networks that can be used for downlink or uplink communication. 5G NR physical channels for uplink communication include the Physical Uplink Shared Channel (PUSCH), Physical Uplink Control Channel (PUCCH), and Physical Random Access Channel (PRACH). Uplink signals such as demodulation reference signals (DMRS), phase tracking reference signals (PTRS), and sounding reference signals (SRS) are also supported. 5G NR supports simultaneous transmission on both PUSCH and PUCCH. PUSCH is typically used to carry user data and may optionally carry uplink control information (UCI).

[0070] PDSCH stands for Physical Downlink Shared Channel, and it is a channel used to deliver data from a base station (e.g., eNodeB) to a User Equipment (UE) in the downlink direction. PDSCH supports high data rates and low latency for a wide range of applications and services. It uses advanced modulation and decoding schemes and multi-antenna techniques such as MIMO (Multiple-Input Multiple-Output) to maximize spectral efficiency and improve overall network performance. PDSCH is also used in conjunction with other channels such as the Physical Downlink Control Channel (PDCCH) and the Physical Hybrid ARQ Indicator Channel (PHICH) to support features such as channel state information reporting, data packet scheduling and retransmission, and HARQ (Hybrid Automatic Repeat Request) feedback. PDSCH enables high-speed data and low-latency services to be delivered to users in the downlink direction and supports a range of advanced features and capabilities that promote efficient and reliable network operation.

[0071] Multiple-input multiple-output (MIMO) can be used in 5G networks to increase data rates, improve spectral efficiency, and enhance the reliability of wireless communication. In MIMO operation, multiple antennas are used at both the transmitter (e.g., a base station) and the receiver (user equipment or UE) to simultaneously transmit and receive multiple data streams. MIMO can be used in both uplink and downlink directions and can support a range of antenna configurations, including 2×2, 4×4, 8×8, or higher. The number of antennas used in a MIMO configuration can be represented by two numbers, where the first number represents the number of antennas at the transmitter (e.g., the base station) and the second number represents the number of antennas at the receiver (e.g., the UE). MIMO supports high data rates and low latency by allowing the simultaneous transmission and reception of multiple data streams, even in environments with high levels of interference or signal attenuation. Each data stream can be referred to as a layer.

[0072] The demodulation reference signal (DMRS) is specific to each UE and can be used to estimate the radio channel. The network or UE can beamform the DMRS, keeping it within scheduled resources, and transmit it only in the DL or UL when needed. Additionally, multiple orthogonal DMRSs can be allocated to support MIMO transmission.

[0073] Phase tracking reference signal (PTRS) is useful because transmitter phase noise tends to increase with increasing operating frequency. PTRS can minimize the impact of oscillator phase noise on system performance. Phase noise can introduce subcarrier phase rotation (which can be referred to as common phase error (CPE)) into OFDM symbols. PTRS can be used to track the phase of the local oscillator at both the transmitter and receiver, and to suppress phase noise and CPE, especially at higher millimeter-wave frequencies. PTRS exists in both the uplink (in NR-PUSCH) and downlink (in NR-PDSCH) channels. PTRS can be associated with a DMRS port during transmission.

[0074] The Sounding Reference Signal (SRS) is a UL signal transmitted by the UE to help the network obtain the Channel State Information (CSI) for each UE. The CSI describes how the NR signal propagates from the UE to the gNB and represents the combined effects of scattering, fading, and power attenuation with distance. The UE transmits the SRS at specific times and frequencies; this SRS is a predefined signal with known characteristics. The SRS configuration is provided to the UE by the gNB and can vary depending on cell conditions and service requirements. The UE transmits the SRS periodically or aperiodically on the uplink (UL) channel, as indicated by the gNB. For example, the network can configure one or more SRS resource sets for the UE via a higher-layer parameter that may be called an SRS-ResourceSet. Each SRS resource set can contain up to 16 SRS resources. The UE can be configured to transmit the SRS on 1 / 2 / 4 antenna ports. The SRS can be configured to use 1 / 2 / 4 symbols in the time domain, located in the last 6 symbols of the time slot. The antenna ports can be identified as 1000, 1001, 1002, and 1003.

[0075] The New Radio (NR) uplink (UL) supports two multiple-input multiple-output (MIMO) operating modes: codebook and non-codebook. Furthermore, the NR UL can support up to four layers, but no more. A layer can be understood as a separate data stream.

[0076] A codebook is a predefined set of beamforming vectors used by a base station to orient antenna radiation patterns toward a specific user or user group. The codebook may include a lookup table that the base station uses to select the optimal beamforming vector for a given user or user group based on channel conditions and other factors. The codebook may include multiple sets of beamforming vectors optimized for different scenarios, such as indoor vs. outdoor environments, line-of-sight vs. non-line-of-sight conditions, etc. The codebook may include a matrix with complex-valued elements that transforms data bits (e.g., in a PDSCH) into another dataset mapped to each antenna port. By selecting the optimal beamforming vector for each user or user group, the base station can minimize interference and maximize signal strength, resulting in faster and more reliable connections.

[0077] In codebook-based UL, such as when the Sound Reference Signal (SRS) resource set purpose is set to "codebook", the UE can utilize multiple ports to transmit SRS resources. The network (NW) can schedule PUSCH by indicating TPMI (Transmit Pre-decoded Matrix) and SRS Rank Indicator (SRI).

[0078] In a non-codebook-based UL, such as when the SRS resource set purpose = "non-codebook", the UE can send multiple SRS signals, each with a single port. The NW can schedule the PUSCH by indicating the SRS resource / port selection and SRI.

[0079] Figure 6 An example of a UE with simultaneous transmission of PUSCH utilizing multiple panels is shown, according to one aspect. 5G and MIMO evolution can support two modes of simultaneous transmission of PUSCH from multiple panels based on a single DCI. UE 602 can have two panels 604 and 606. Each panel 604 and 606 can be pointed in a corresponding direction different from the other panel. A panel can also be referred to as a panel antenna, which is a directional antenna configured to transmit and receive radio signals from a single direction rather than other directions. Panel antennas have a wider beam compared to other directional antennas, which allows each panel antenna to cover a larger area.

[0080] When UE 602 transmits two PUSCHs (608 and 610) simultaneously, this can be referred to as simultaneous transmission across multiple panels (STxMP). STxMP can operate in two modes. The first mode can be referred to as SDM (Space Division Multiplexing) mode 616 (or SDM STxMP). The second mode can be referred to as SFN (Single Frequency Network) mode 614 (or SFN STxMP). In each mode, UE 602 can perform mode-specific operations, as described in further detail in other sections, to operate each panel 604 and panel 606 to transmit the corresponding PUSCH.

[0081] For example, panel 604 can be operated to transmit data via uplink channel PUSCH 608, and panel 606 can be operated to transmit data to base station 612 via uplink channel PUSCH 610. PUSCHs can be transmitted to base station 612 individually and simultaneously by the UE. UE 602 can also operate in non-STxMP modes, such as single transmit and receive point (sTRP) mode, where the UE uses only one of panels 604 or 606 to transmit a single PUSCH.

[0082] For simultaneous PUSCH transmission via a single DCI, 5G can support dynamic handover between STxMP (simultaneous transmission across multiple panels) PUSCH based on a single DCI and SDM (or SFN) schemes transmitted via sTRP. However, it is unclear or unconsensus how the network can provide indication of dynamic handover between sTRP and SDM STxMP (or SFN STxMP), and it is also unclear or unconsensus regarding the maximum number of layers that should be when switching to sTRP transmission. Dynamic handover may include downlink signaling (e.g., DCI) from the network to the UE to signal the change in behavior.

[0083] For simultaneous PUSCH transmission of a single DCI, 5G can support independent configuration of the maximum number of layers for sTRP and SDM STxMP modes (or SFNSTxMP), but details are yet to be determined.

[0084] This disclosure addresses various aspects of PTRS design for simultaneous PUSCH transmission of a single DCI using SDM or SFN. Various PTRS design problems can be addressed within this context. Some aspects relate to PTRS port configuration. Some aspects relate to PTRS-DMRS association indication. Some aspects relate to shared ports between SDM / SFN and sTRP.

[0085] Figure 7 An example of configuration for Uplink Phase Tracking Reference Signal (UL PTRS) is shown. PTRS port configuration can be performed through the configuration of the Uplink Phase Tracking Reference Signal (UL PTRS). The network can configure the UE's UL PTRS via signaling (e.g., RRC signaling). The network can send signaling to the UE containing PTRS-Uplink configuration 700, which may include various fields. For example, PTRS-Uplink configuration 700 may include a field 702 indicating the maximum number of ports, "maxNrofPorts". This field may include enumerated values ​​"n1" or "n2".

[0086] It should be understood that, as those skilled in the art would understand, the aspects described in this disclosure are not mutually exclusive and can be combined with each other unless logically incompatible.

[0087] Figure 8 An example diagram illustrating the dynamic switching between SDM STxMP and sTRP according to some implementation schemes is shown.

[0088] At operation 806, network (NW) 804 may send a DCI signal to the UE. The DCI may include an indication associated with UE operation under simultaneous transmission across multiple panels using spatial multiplexing (SDM) (STxMP), which may be referred to as SDMSTxMP. For example, the DCI signal may include a field indicating to UE 802 a change from STRP to SDM STxMP operation or a change from SDM STxMP to STRP operation.

[0089] At operation 810, in response to an instruction received from the network, UE 802 can dynamically activate or deactivate SDM STxMP based on the field value of the instruction received via operation 806.

[0090] At operation 808, network 804 may communicate with UE 802 based on the maximum number of tiers associated with the indication. For example, if UE 802 is switched to operate in sTRP mode, network 804 and UE 802 may assume the maximum number under one or more first rules, and if UE 802 is switched to operate in SDM STxMP mode, UE 802 and network 804 may assume the maximum number of tiers under one or more second rules. This will be explained in detail below. The maximum number of tiers can be understood as the maximum number of data streams that can be transmitted over MIMO communication between the UE and the network (e.g., during uplink communication). Communication at operation 808 may include UE 802 using two panels (e.g., when SDM STxMP is activated) and using a single panel (e.g., when SDM STxMP is deactivated).

[0091] Configuration operation 812 may include one or more signals from NW 804 to UE 802 to configure one or more settings of the UE (e.g., UL PTRS or other settings). Configuration operation 812 may include RRC signaling, higher-layer signaling, or other signaling. Configuration operation 812 may occur promptly as shown in the example, but may also be provided to the UE from the NW at other times.

[0092] On one hand, when the NW configures the UE using SDM STxMP operations based on a single DCI, the following restrictions can be applied regarding the maximum number of PUSCH layers configured: In the first option, the maximum number of layers L_(max,sTRP) = 2 * L_(max,SDM). In the second option, the maximum number of layers L_(max,sTRP) = L_(max,SDM). In the third option, the maximum number of layers L_(max,sTRP) ≤ 2 * L_(max,SDM). In the fourth option, the maximum number of layers L_(max,sTRP) ≥ L_(max,SDM).

[0093] L_(max,sTRP) can refer to the maximum number of layers used for sTRP transmission. L_(max,SDM) can refer to the maximum number of layers applied to each SRS resource set (panel / TRP). These can be configured via operation 912, or assumed by UE 902 and NW904 as described.

[0094] For example, an indication received in the DCI (via operation 806) may include instructions for transitioning from STxMP (e.g., SDMSTxMP) to a Single Transmit and Receive Point (sTRP). The maximum number of layers associated with the indication includes the maximum number of layers associated with the sTRP, which is equal to or less than twice the maximum number of layers associated with each individual panel used for STxMP. In this embodiment, and in other embodiments, the maximum number of layers may be set via signaling that can be executed at operation 812 (e.g., via field 702 of PTRS-UplinkConfig 700). Thus, at operation 810, the UE transitions from SDM STxMP to sTRP and operates with a maximum number of layers equal to or less than twice the maximum number of layers associated with each individual panel used for STxMP.

[0095] In another example, the indication includes instructions for transitioning from STxMP (e.g., SDM STxMP) to a single transmit and receive point (sTRP). The maximum number of layers associated with the indication includes the maximum number of layers associated with the sTRP, which is equal to the maximum number of layers associated with each individual panel used for STxMP.

[0096] On the one hand, when NW 804 configures UE 802 using SDM STxMP operation based on a single DCI (e.g., at operation 806), NW is free to configure the UE using the number of ports used for UL PTRS, such as, for example, maxNrofPorts in PTRS-UplinkConfig being “n1” or “n2”. For example, the network can (e.g., at operation 812) configure the UE using the maximum number of ports used for uplink phase tracking reference signal (PTRS), which is set to n1 or n2 in PTRS-Uplink configuration without limitation.

[0097] On one hand, when NW 802 configures UE 804 using SDM STxMP operations based on a single DCI (e.g., at operation 806), NW can configure two-port PTRS, such as setting maxNrofPorts in PTRS-UplinkConfig to “n2”. The configuration of two-port PTRS can be accomplished via signaling operation 812.

[0098] On one hand, when NW 804 configures UE 802 using SDM STxMP operation based on a single DCI (e.g., at operation 806) and NW configures two-port UL PTRS (e.g., at operation 812), when dynamic handover between SDM and sTRP is configured, and when gNB schedules sTRP, regarding the number of ports used for UL PTRS, one option is that UE 802 and NW 804 assume only a single port. For example, when dynamic handover between SDM and a single transmit and receive point (sTRP) is configured, and when the network schedules sTRP, the network operates under the assumption of only a single port (or single layer) for uplink (UL) PTRS. Another option is to assume two-port PTRS. For example, when dynamic handover between SDM and a single transmit and receive point (sTRP) is configured, and when the network schedules sTRP, the network operates under the assumption of two ports (or layers) for uplink (UL) PTRS.

[0099] In one aspect (1.5), when the network uses a two-port uplink (UL) PTRS to configure the UE (e.g., via operation 812), and when dynamic switching between SDM and single transmit and receive point (sTRP) is configured (e.g., via operation 812), and when the network schedules sTRP (e.g., at operation 814), the network assumes a port (or layer) UL PTRS in response to at least one of the following: i) the network (e.g., gNB) configures fully coherent physical uplink shared channel (PUSCH) operation for sTRP, or ii) the network configures non-coherent PUSCH operation for sTRP with a single port, wherein for codebook operation, the number of ports (or layers) to be used by the UE is the number of probe reference signal (SRS) ports of the SRS-Resource in the SRS-ResourceSet whose purpose is set to the codebook. For non-codebook, the number of ports (or layers) to be used by the UE is equal to the number of SRS-Resources in the SRS-ResourceSet whose purpose is set to "non-codebook" (e.g., via operation 812). The number of ports to be used by the UE can also be referred to as the maximum number of ports to be used by the UE during the corresponding mode (e.g., SDM STxMP or sTRP).

[0100] On one hand, when NW 804 uses two-port uplink (UL) PTRS to configure UE 802 (e.g., via operation 812), and when dynamic handover between SDM and single transmit and receive point (sTRP) is configured, and when the network schedules sTRP, the network assumes two-port UL PTRS in response to at least one of the following: i) the network configures partially coherent physical uplink shared channel (PUSCH) operation for sTRP; or ii) the network configures incoherent PUSCH operation for sTRP with more than one port, wherein for codebook operation, the number of ports (or layers) to be used by the UE is equal to the number of sounding reference signal (SRS) ports of the SRS-Resource in the SRS-ResourceSet whose purpose is set to "codebook". For non-codebook operation, the number of ports (or layers) to be used by the UE is equal to the number of SRS-Resources in the SRS-ResourceSet whose purpose is set to "non-codebook".

[0101] The PTRS-DMRS association can be a field in DCI signaling (e.g., via operation 806). This field can be 0 or 2 bits, depending on other factors such as whether UL PTRS and / or PUSCH are configured via RRC (e.g., via operation 812). Network 804 and UE 802 can agree on the conditions defining the bit width. NW 804 can transmit the PTRS-DMRS association to UE 802 via DCI operation 806.

[0102] On one hand, NW 804 uses SDM STxMP operation based on a single DCI to configure UE 802 (e.g., at operation 806), in DCI formats 0_1 and 0_2, the bit width of "PTRS-DMRS association" is 0 under any of the following conditions: PTRS-UplinkConfig is not configured and the transform predecoder is disabled; the transform predecoder is enabled; L_(max,SDM)=1 and dynamic switching between SDM STxMP and sTRP is not configured; L_(max,SDM)=1 and L_(max,sTRP)=1 and dynamic switching between SDM STxMP and sTRP is configured.

[0103] For example, when the DCI format is 0_1 or 0_2, the network responds to one or more of the following first conditions to set the bit width of the Phase Tracking Reference Signal Demodulation Reference Signal Association (PTRS-DMRS Association) to zero: PTRS-uplink configuration is not configured and the transform pre-decoder is disabled; the transform pre-decoder is enabled; the maximum number of layers for SDM is one and dynamic switching between SDM STxMP and sTRP is not configured; or the maximum number of layers for SDM and sTRP is equal to one and dynamic switching between SDM STxMP and sTRP is configured. This can be referred to as the first scenario.

[0104] Tables 7.3.1.1.2-25 and 7.3.1.1.2-26 of 3GPP TS 38.212 Release 15.3.0 (shown below) are used to indicate the association between PTRS ports and DMRS ports for transmission on one PTRS port and two PTRS ports respectively, with the DMRS port indicated by the antenna port field. It has been agreed that for the PTRS-DMRS association field, the number of bits (e.g., zero or two) is determined as follows: 0 bits if PTRS-UplinkConfig is not configured and the transform pre-decoder is disabled, or if the transform pre-decoder is enabled, or if maxRank=1; otherwise, 2 bits.

[0105] Table 1 below is an example of 7.3.1.1.2-25 from 3GPP TS 38.212 version 15.3.0.

[0106]

[0107] Table 2 below is an example of 7.3.1.1.2-26 from 3GPP TS 38.212 version 15.3.0, which allows four configurations. A PTRS-DMRS association of “00” can mean that the first DMRS port shares PTRS port 0, and the second DMRS port shares PTRS port 1. Similarly, a PTRS-DMRS association of “01” can mean that the first DMRS port shares PTRS port 0, and the second DMRS port shares PTRS port 1, and so on.

[0108]

[0109] On the one hand, when NW 804 uses SDM STxMP operation based on a single DCI to configure UE 802 (at operation 806), in DCI formats 0_1 and 0_2, when PTRS-UplinkConfig is configured and the transform predecoder is disabled, and under any of the following conditions, the bit width of "PTRS-DMRS association" is 1: L_(max,SDM)=1 and L_(max,sTRP)=2, and coherent operation is configured for sTRP, and dynamic switching between SDM STxMP and sTRP is configured.

[0110] For example, when the DCI format is 0_1 or 0_2, and when the PTRS-uplink configuration is configured and the transform pre-decoder is disabled, and in response to a second condition, network 804 sets the bit width of the PTRS-DMRS association to one. This second condition includes a maximum number of layers for SDM equal to one, a maximum number of layers for sTRP equal to two, coherent operation being configured for sTRP, and dynamic switching between SDM STxMP and sTRP being configured. This can be referred to as the second scenario.

[0111] On the one hand, when NW 804 uses SDM STxMP operation based on a single DCI to configure UE 802 (e.g., at operation 806), in DCI formats 0_1 and 0_2, the bit width of "PTRS-DMRS association" is two under the following conditions: the condition in scenario 1 does not exist, or the condition under both scenario 1 and scenario 2 does not exist.

[0112] For example, when the DCI format of the DCI is 0_1 or 0_2, in response to either of the first conditions (e.g., in scenario 1) being unsatisfied, or either of the first and second conditions (in scenario 2) being unsatisfied, the network sets the bit width associated with PTRS-DMRS to two.

[0113] On one hand, when NW 804 configures UE 802 using SDM STxMP operation based on a single DCI (e.g., at operation 806), in DCI formats 0_1 and 0_2, the bit width of "PTRS-DMRS association" is 2 and 2-port PTRS is configured. When SDM STxMP is scheduled, the interpretation of the "PTRS-DMRS association" field is as follows: i) PTRS port 0 is associated with a DMRS port associated with a first SRS resource set, in which case the DMRS port may be associated with a first TPMI or SRI; and / or ii) PTRS port 1 is associated with a DMRS port associated with a second SRS resource set, in which case the DMRS port may be associated with a second TPMI or SRI.

[0114] For example, when the DCI format is 0_1 or 0_2 (at operation 806), and when the bit width of the PTRS-DMRS association is two, and when a two-port PTRS is configured, and when SDM STxMP is scheduled, the network associates PTRS port zero with a first DMRS port associated with a first SRS resource set; and the network associates PTRS port one with a second DMRS port associated with a second SRS resource set. For further reference, Table 2 (above) includes the mapping of PTRS-DMRS associations.

[0115] On one hand, when NW 804 configures UE 802 using SDM STxMP operation based on a single DCI (e.g., at operation 806), in DCI formats 0_1 and 0_2, if L_(max,SDM)=1, when SDM STxMP is scheduled, the bit width of "PTRS-DMRS association" is 2 and a 2-port PTRS is configured. Under the first option, no indication of "PTRS-DMRS association" other than "00" is expected to be given to the UE. Under the second option, the UE always assumes "00" regardless of what "PTRS-DMRS association" indicates. For example, when the DCI format is 0_1 or 0_2, and the bit width of PTRS-DMRS association is two, and a 2-port PTRS is configured, and when SDM STxMP is scheduled, in response to the maximum number of SDM layers being equal to one, the network indicates PTRS-DMRS association as "00", or the UE operates under the assumption that PTRS-DMRS association equals "00".

[0116] On one hand, when NW 804 configures 802 using SDM STxMP operation based on a single DCI (e.g., at operation 806), in DCI formats 0_1 and 0_2, the bit width of "PTRS-DMRS association" is 2 and 2-port PTRS is configured. When sTRP is scheduled, the "PTRS-DMRS association" field is interpreted as follows: PTRS port 0 is associated with a DMRS port associated with a UL layer that is transmitted using PUSCH antenna ports 1000 and 1002; PTRS port 1 is associated with a DMRS port associated with a UL layer that is transmitted using PUSCH antenna ports 1001 and 1003. For example, when the DCI format is 0_1 or 0_2, and when the bit width of the PTRS-DMRS association is two, and when two-port PTRS is configured, and when sTRP is scheduled, the network associates PTRS port 0 with a first DMRS port, which is associated with uplink (UL) layer transmissions using Physical Uplink Shared Channel (PUSCH) antenna port numbers 1000 and 1002, and the network associates PTRS port 1 with a second DMRS port, which is associated with UL layer transmissions using PUSCH antenna port numbers 1001 and 1003. The PTRS-DMRS associations can be referenced in the table provided above.

[0117] On the one hand, when NW 804 uses SDM STxMP operation based on a single DCI to configure 802 (e.g., at operation 806), in DCI formats 0_1 and 0_2, the bit width of “PTRS-DMRS association” is 2 and 2-port PTRS is configured when sTRP is scheduled and when coherent transmission is configured for sTRP: only single-port PTRS is assumed; and / or the interpretation of “PTRS-DMRS association” follows Table 1 above. For example, when the DCI format of the DCI is 0_1 or 0_2, and when the bit width of the PTRS-DMRS association is two, and when two-port PTRS is configured, and when sTRP is scheduled, and when coherent transmission is configured for sTRP, the network operates under the assumption of single-port PTRS operation, and the PTRS-DMRS association for UL PTRS port zero is: zero for the first scheduled DMRS port, one for the second scheduled DMRS port, two for the third scheduled DMRS port, and three for the fourth scheduled DMRS port.

[0118] When UE 802 changes between SDM operation and sTRP operation (e.g., at operation 810), UE 802 can share the port used between SDM operation and sTRP operation.

[0119] On one hand, when NW 804 is configured to use SDM STxMP operation based on a single DCI to configure 802 (e.g., at operation 806) and dynamic switching between SDM STxMP and SDM is configured (e.g., via RRC signaling 812), in order to allow shared ports between SDM and sTRP, i.e., the total number of PUSCH antenna ports used for SDM and sTRP is the same, for codebook operation: two SRS-ResourceSets are configured; the SRS-Resource in each SRS-ResourceSet is configured using N ports, e.g., N=2, 4; when gNB schedules SDM STxMP, only N / 2 SRS ports in each SRS-Resource are used for PUSCH scheduling, and / or when gNB schedules sTRP, all N SRS ports in each SRS-Resource are used for PUSCH scheduling. For example, when dynamic scheduling between SDM STxMP and sTRP is configured and two probe reference signal (SRS)-ResourceSets are configured, under codebook operation: when STxMP is scheduled, half of all SRS ports in each SRS-Resource in the SRS-ResourceSet are used for PUSCH scheduling, and when sTRP is scheduled, all SRS ports in each SRS-Resource in the SRS-ResourceSet are used for PUSCH scheduling.

[0120] On the one hand, when NW 804 configures UE 802 using SDM STxMP operation based on a single DCI (e.g., at operation 806) and dynamic handover between SDM STxMP and SDM is configured, in order to allow shared ports between SDM and sTRP, i.e., the total number of PUSCH antenna ports used for SDM and sTRP is the same, for non-codebook operations, the following can be understood between NW 804 and UE 802: two SRS-ResourceSets are configured; N SRS-Resources are configured in each SRS-ResourceSet, e.g., N=2, 4; when gNB schedules SDM STxMP, only N / 2 SRS-Resources in each SRS-ResourceSet are used for PUSCH scheduling; and / or when gNB schedules sTRP, all N SRS-Resources in each SRS-ResourceSet are used for PUSCH scheduling. For example, when dynamic scheduling between SDM STxMP and sTRP is configured and two probe reference signal (SRS)-ResourceSets are configured, under codebook operation: when STxMP is scheduled, half of all SRS-Resources in each SRS-ResourceSet are used for PUSCH scheduling, and when sTRP is scheduled, all SRS-Resources in each SRS-ResourceSet are used for PUSCH scheduling.

[0121] On one hand, for SDM STxMP operation, UE 802 can indicate to NW 804 whether the UE supports dynamic handover between SDM STxMP and sTRP. This can be performed by signaling the UE's capability to NW 804 at operation 816. The network receives the indication from UE 802 regarding whether the UE supports dynamic handover between SDM STxMP and sTRP. In response, at operation 814, NW 804 can schedule uplink and downlink communication accordingly.

[0122] On one hand, for SDM STxMP operation, if the UE supports both SDM STxMP and sTRP, the UE 802 can indicate to the NW 804 whether the UE shares ports between SDM and sTRP. The NW 804 receives this indication from the UE 804. If the UE shares ports between SDM and sTRP, for codebook operation, the total number of SRS ports expected to be configured for PUSCH scheduling by the UE is the same on both panels (two SRS-ResourceSets) used for SDM STxMP scheduling and on a single panel (single SRS-ResourceSet) used for sTRP scheduling. For non-codebook operation, the total number of SRS resources expected to be configured for PUSCH scheduling by the UE is the same on both panels (two SRS-ResourceSets) used for SDM STxMP scheduling and on a single panel (single SRS-ResourceSet) used for sTRP scheduling.

[0123] For example, at operation 816, UE 802 can provide NW 804 with an indication of whether the UE shares ports between SDM and sTRP. At operations 814 and 810, NW 804 and UE 802 can operate under the following assumptions: i) the total number of SRS ports configured for PUSCH scheduling is the same on both panels (two SRS-ResourceSets) used for SDM STxMP scheduling and on a single panel (single SRS-ResourceSet) used for sTRP scheduling; and ii) for non-codebook operations, the total number of SRS resources configured for PUSCH scheduling is the same on both panels (two SRS-ResourceSets) used for SDM STxMP scheduling and on a single panel (single SRS-ResourceSet) used for sTRP scheduling.

[0124] Figure 9 An example diagram illustrating the dynamic switching between SFN STxMP and sTRP according to some implementation schemes is shown.

[0125] Network (NW) 904 may include one or more base stations. UE 902 may be associated with or communicate with NW 904. At operation 906, NW 904 may send downlink control information (DCI) signals to UE 902. DCI may include various fields for information or instructions that the UE can use to perform various operations. Specifically, DCI may include indications associated with UE operations under Single Frequency Network (SFN) Simultaneous Transmission Across Multiple Panels (STxMP). For example, the indication may include fields that, based on their values, indicate whether the UE is transitioning from SFN STxMP mode to sTRP mode, or from sTRP mode to SFN STxMP mode.

[0126] At operation 910, UE 902 can respond to an indication to transition from SFN STxMP mode to sTRP mode, or from sTRP mode to SFN STxMP mode. NW 904 can dynamically provide this signaling to UE 902 at operation 906. Similarly, the UE can dynamically activate or deactivate SFN STxMP mode.

[0127] At operation 908, NW 904 and UE 902 can communicate based on a maximum number of layers associated with the indication provided to UE 902 via operation 906. For example, UE 902 can perform uplink communication with NW 904 using a single panel or two panels (as described) and a maximum number of layers (which may be determined based on one or more other factors), as described below. Each layer can refer to an independent data stream.

[0128] Configuration operation 912 may include one or more signals from NW 904 to UE 902 to configure one or more settings of the UE (e.g., UL PTRS or other settings). Configuration operation 912 may include RRC signaling, higher-layer signaling, or other signaling. Configuration operation 912 may occur promptly as shown in the example, but may also be provided to the UE from the NW at other times.

[0129] On the one hand, when NW 904 configures UE 902 using SFN STxMP operation based on a single DCI (e.g., at operation 906), for the maximum number of PUSCH layer configurations, UE 902 and NW 904 can operate under one or more of the following restrictive options regarding the number of layers used in communication. In option 1, Lmax,sTRP ≤ 2*Lmax,SFN. In option 2, SFN Lmax,sTRP ≥ Lmax,SFN. In option 3, Lmax,sTRP = 2*Lmax,SFN. In option 4, Lmax,sTRP = Lmax,SFN.

[0130] Lmax, sTRP refers to the maximum number of layers that can be configured (e.g., at operation 912) for sTRP transmission. Lmax, SFN refers to the maximum number of layers that can be configured (e.g., at operation 912), which is applied individually to each SRS resource set (panel / TRP) during SFN STxMP operation.

[0131] For example, the instruction provided to UE 902 (e.g., operation 906) may include instructions for the UE to transition from STxMP (e.g., SFNSTxMP) to a single transmit and receive point (sTRP) (e.g., at operation 910). The maximum number of layers associated with the instruction includes the maximum number of layers associated with sTRP (Lmax, sTRP), which is equal to or less than twice the maximum number of layers associated with each individual panel used for STxMP (Lmax, SFN).

[0132] In another example, the indication includes instructions for transitioning from STxMP (e.g., SFN STxMP) to a single transmit and receive point (sTRP). The maximum number of layers associated with the indication includes the maximum number of layers associated with the sTRP (Lmax, sTRP), which is equal to or greater than the maximum number of layers associated with each individual panel used for STxMP (Lmax, SFN).

[0133] On one hand, regarding SFN PTRS port configuration, when NW 904 configures UE 902 (e.g., at operation 906) using SFN STxMP operation based on a single DCI, for codebook-based PUSCH operation, NW 904 configures the same coherence mode for each panel (which may correspond to the corresponding SRS-ResourceSet). For example, NW 904 may configure the coherence mode of each panel as "fullyAndPartialAndNonCoherent" in the first case, "partialAndNonCoherent" in the second case, or "nonCoherent" in the third case. This aspect also extends to SDM STxMP operation.

[0134] On one hand, for SFN PTRS port configuration, when NW 904 configures UE 902 using a single DCI-based SFN STxMP operation (e.g., operation 906) and dynamic handover between SFN STxMP and sTRP is configured, for codebook-based PUSCH operations, both SFN STxMP and sTRP can be configured using the same coherence mode, i.e., “fullyAndPartialAndNonCoherent”, “partialAndNonCoherent”, or “nonCoherent”. At operation 912, SFN PTRS port configuration can be performed via signaling from NW 904 to UE 902 (e.g., RRC signaling).

[0135] On the one hand, when NW 904 configures UE 902 using SFN STxMP operation based on a single DCI, NW 904 can freely configure the number of PTRS ports, i.e., maxNrofPorts in PTRS-UplinkConfig is set to "n1" or "n2" (e.g., via operation 912). For example, the network can configure the UE using the maximum number of ports for the uplink phase tracking reference signal (PTRS), which is set to n1 or n2 in the PTRS-uplink configuration without limitation. (As relative to...) Figure 7 As described, n1 and n2 can be enumerated values ​​that specify the corresponding maximum values. In this example and in other examples, n1 can represent the maximum number of "one port" and n2 can represent the maximum number of "two ports".

[0136] On one hand, when NW 904 configures UE 902 using SFN STxMP operation based on a single DCI (e.g., operation 906), NW will configure two-port PTRS, such as setting maxNrofPorts in PTRS-UplinkConfig to “n2” (e.g., at operation 912). For example, the network configures the UE using the maximum number of ports used for uplink phase tracking reference signals (PTRS), which is set to n2 in PTRS-Uplink Configuration instead of n1.

[0137] On one hand, when NW 904 configures UE 902 using SFN STxMP operation based on a single DCI (e.g., at operation 906) and NW configures 2-port UL PTRS (e.g., at operation 912), several options can be implemented regarding the number of ports used for UL PTRS when dynamic handover between SFN and sTRP is configured and when gNB schedules sTRP. In the first option, UE 902 and NW 904 use only a single port. In the second option, UE 902 and NW 904 assume two-port PTRS. When the network configures the UE using two-port uplink (UL) PTRS, and when dynamic handover between SFN and single transmit and receive point (sTRP) is configured, and when the network schedules sTRP, the network assumes one or two ports for UL PTRS. This aspect can also be extended to SDM STxMP.

[0138] On one hand, when NW 904 configures UE 902 using SFN STxMP operation based on a single DCI (e.g., at operation 906) and NW configures two-port UL PTRS (e.g., at operation 912), when dynamic handover between SFN and sTRP is configured, and when gNB schedules sTRP, one-port UL PTRS is assumed under one or more of the following assumptions: i) the network (gNB) configures fully coherent PUSCH operation for sTRP, i.e., “fullyAndPartialAndNonCoherent”; and ii) the network configures noncoherent PUSCH operation for sTRP, i.e., “nonCoherent” with only a single port. For codebook, the maximum number of ports is the number of SRS ports of SRS-Resource in SRS-ResourceSet, where purpose = “codebook”. For noncodebook, the maximum number of ports is the number of SRS-Resource in SRS-ResourceSet, where purpose = “nonCodebook”.

[0139] For example, when the network uses two-port uplink (UL) PTRS to configure the UE, and when dynamic handover between SFN and single transmit and receive point (sTRP) is configured, and when the network schedules sTRP, the network assumes a port for UL PTRS in response to at least one of the following: i) the network configures fully coherent physical uplink shared channel (PUSCH) operation for sTRP, or ii) the network configures single-port noncoherent PUSCH operation for sTRP, wherein for codebook operation, the number of ports is the number of probe reference signal (SRS) ports of SRS-Resource in the SRS-ResourceSet whose purpose is set to codebook, and for non-codebook operation, the number of ports is the number of SRS-Resources in the SRS-ResourceSet whose purpose is set to non-codebook.

[0140] On one hand, when NW 904 configures UE 902 using a single DCI-based SFN STxMP operation (e.g., at operation 906) and NW 904 configures two-port UL PTRS (e.g., via operation 912), when dynamic handover between SFN and sTRP is configured, and when gNB schedules sTRP (e.g., via operation 906), two-port UL PTRS is assumed under one or more of the following conditions: the network (e.g., gNB) configures partially coherent PUSCH operations for sTRP, i.e., “partialAndNonCoherent”; the network configures noncoherent PUSCH operations (i.e., “nonCoherent”) for TRP with more than one port. For codebook, the number of ports is equal to the number of SRS ports of SRS-Resource in SRS-ResourceSet, where purpose = “codebook”. For noncodebook, the number of ports is equal to the number of SRS-Resource in SRS-ResourceSet, where purpose = “nonCodebook”. Regarding the PTRS-DMRS association indication, this signaling field can be used for PUSCH scheduling to indicate which DMRS port should be used for PTS transmission.

[0141] For example, when the network uses two-port uplink (UL) PTRS to configure the UE, and when dynamic handover between SDM and single transmit and receive point (sTRP) is configured, and when the network schedules sTRP, the network assumes two-port UL PTRS in response to at least one of the following: i) the network configures partially coherent physical uplink shared channel (PUSCH) operation for sTRP, or ii) the network configures non-coherent PUSCH operation for sTRP with more than one port, wherein for codebook operation, the number of ports (or layers) is equal to the number of probe reference signal (SRS) ports of the SRS-Resource in the SRS-ResourceSet whose purpose is set to codebook, and for non-codebook operation, the number of ports (or layers) is equal to the number of SRS-Resources in the SRS-ResourceSet whose purpose is set to non-codebook.

[0142] On one hand, when NW 904 configures UE 902 using SFN STxMP operation based on a single DCI (e.g., at operation 906), in DCI formats 0_1 and 0_2, the bit width of "PTRS-DMRS association" is 0 under any of the following conditions: PTRS-UplinkConfig is not configured and the transform predecoder is disabled; the transform predecoder is enabled; Lmax,SFN=1 and dynamic handover between SFN STxMP and sTRP is not configured; and / or Lmax,SFN=1 and Lmax,sTRP=1 and dynamic handover between SFN STxMP and sTRP is configured. For example, when the DCI format is 0_1 or 0_2, the network responds to one or more of the following first conditions to set the bit width of the Phase Tracking Reference Signal Demodulation Reference Signal Association (PTRS-DMRS Association) to zero: PTRS-Uplink configuration is not configured and the transform pre-decoder is disabled; the transform pre-decoder is enabled; the maximum number of layers for the SFN is one and dynamic switching between the SFN STxMP and sTRP is not configured; or the maximum number of layers for the SFN and sTRP is equal to one and dynamic switching between the SFN STxMP and sTRP is configured. This can be referred to as the first scenario.

[0143] On one hand, when NW 904 configures UE 902 using SFN STxMP operation based on a single DCI (e.g., at operation 906), in DCI formats 0_1 and 0_2, when PTRS-UplinkConfig is configured and the transform pre-decoder is disabled (e.g., via operation 912), and under any of the following conditions, the bit width of "PTRS-DMRS association" is 1: Lmax, SFN=1 and Lmax, sTRP=2, and fully coherent operation is configured for sTRP, and dynamic switching between SFN STxMP and sTRP is configured. For example, when the DCI format is 0_1 or 0_2, and when the PTRS-uplink configuration is configured and the transform pre-decoder is disabled, and in response to a second condition, the network sets the bit width of the PTRS-DMRS association to one. This second condition includes the maximum number of layers for SFN being equal to one, the maximum number of layers for sTRP being equal to two, coherent operation being configured for sTRP, and dynamic switching between SFN STxMP and sTRP being configured. This can be referred to as the second scenario.

[0144] On one hand, when NW 904 configures UE 902 using SFN STxMP operation based on a single DCI (e.g., at operation 906), in DCI formats 0_1 and 0_2, the bit width of "PTRS-DMRS association" is 2 under either of the following conditions: the condition under the first scenario is not met, or the conditions under both the first and second scenarios are not met. For example, when the DCI format is 0_1 or 0_2, in response to neither the first nor the second condition being met, the network sets the bit width of PTRS-DMRS association to two.

[0145] On one hand, when NW 904 configures UE 902 using SFN STxMP operation based on a single DCI (e.g., operation 906), in DCI formats 0_1 and 0_2, the bit width of "PTRS-DMRS association" is 2 and 2-port PTRS is configured (e.g., operation 912). When SFN STxMP is scheduled, the UE's interpretation of the "PTRS-DMRS association" field can be defined as follows: i) PTRS port 0 is associated with a DMRS port associated with the first SRS resource set (a DMRS port associated with the first TPMI or SRI); and / or ii) PTRS port 1 is associated with a DMRS port associated with the second SRS resource set (a DMRS port associated with the second TPMI or SRI). For example, when the DCI format of the DCI is 0_1 or 0_2, and when the bit width associated with the PTRS-DMRS is two, and when the two-port PTRS is configured, and when the SFN STxMP is scheduled, the network associates PTRS port zero with the first DMRS port associated with the first SRS resource set; and the network associates PTRS port one with the second DMRS port associated with the second SRS resource set.

[0146] On one hand, when NW 904 configures UE 902 using SFN STxMP operation based on a single DCI (e.g., operation 906), in DCI formats 0_1 and 0_2, the bit width of "PTRS-DMRS association" is 2 and 2-port PTRS is configured. If Lmax, SFN=1, then when SFN STxMP is scheduled, one option is that the UE is not expected to indicate a "PTRS-DMRS association" other than "00", and a second option is that regardless of what value "PTRS-DMRS association" indicates, UE 902 will always assume "00" for the association. For example, when the DCI format is 0_1 or 0_2, and the bit width of PTRS-DMRS association is two, and when 2-port PTRS is configured, and when SFN STxMP is scheduled, in response to the maximum number of layers of SFN being equal to one, the network indicates PTRS-DMRS association as "00", or the UE operates under the assumption that PTRS-DMRS association is equal to "00". For the PTRS-DMRS association mapping, see Table 1 and Table 2 above.

[0147] On one hand, when NW 904 configures UE 902 using SFN STxMP operation based on a single DCI (e.g., at operation 906), in DCI formats 0_1 and 0_2, the bit width of "PTRS-DMRS association" is two and two-port PTRS is configured. When sTRP is scheduled, the UE and NW interpret the "PTRS-DMRS association" field as follows: i) PTRS port 0 is associated with a DMRS port associated with a UL layer that is transmitted using PUSCH antenna ports 1000 and 1002 (same as SDM); and / or ii) PTRS port 1 is associated with a DMRS port associated with a UL layer that is transmitted using PUSCH antenna ports 1001 and 1003. For example, when the DCI format of the DCI is 0_1 or 0_2, and when the bit width associated with PTRS-DMRS is two, and when two-port PTRS is configured, and when sTRP is scheduled, the network associates PTRS port 0 with a first DMRS port, which is associated with the uplink (UL) layer transmitted using Physical Uplink Shared Channel (PUSCH) antenna ports 1000 and 1002, and the network associates PTRS port 1 with a second DMRS port, which is associated with the UL layer transmitted using PUSCH antenna ports 1001 and 1003.

[0148] On the one hand, when NW 904 configures UE 902 using SFN STxMP operation based on a single DCI, in DCI formats 0_1 and 0_2, the bit width of "PTRS-DMRS association" is two and two-port PTRS is configured. When sTRP is scheduled and when coherent transmission is configured for sTRP: UE 902 and NW 904 can operate as if configured for single-port PTRS, regardless of how PTRS is configured (e.g., via operation 912). The interpretation of "PTRS-DMRS association" follows Table 1 provided above.

[0149] On one hand, when NW 904 configures UE 902 using SFN STxMP operations based on a single DCI (e.g., operation 906), NW 904 supports two “PTRS-DMRS association” fields in DCI formats 0_1 and 0_2 and includes them in the DCI (e.g., at operation 906). Additionally, when SFN STxMP is scheduled (e.g., via operations 906 and 910), both “PTRS-DMRS association” fields are used. Alternatively or additionally, when sTRP is scheduled (e.g., via operations 906 and 910), only the first “PTRS-DMRS association” field is used by the UE, and the second “PTRS-DMRS association” field is ignored by the UE. For example, when the DCI format is 0_1 or 0_2, the network includes two PTRS-DMRS association fields in the DCI. When the network schedules SFN STxMP, both PTRS-DMRS association fields are used, and when the network schedules sTRP, the first PTRS-DMRS association field is used instead of the second. This aspect can also be applied to the SDM STxMP case.

[0150] On one hand, when NW 904 configures UE 902 using SFN STxMP operations based on a single DCI (e.g., operation 906), in DCI formats 0_1 and 0_2, when both “PTRS-DMRS association” fields are supported and included in the DCI, for SFN STxMP scheduling, the UE can consider the first “PTRS-DMRS association” field as associated with a first panel (e.g., SRS resource set) or a first transcoder predecoder matrix indicator (TPMI) or SRS resource indicator (SRI); and / or the second “PTRS-DMRS association” field as associated with a second panel, i.e., an SRS resource set, in other words, a second TPMI or SRI. This aspect can also be applied to the case of SDM STxMP.

[0151] For example, when the DCI format is 0_1 or 0_2, and when the DCI includes two PTRS-DMRS association fields, the first PTRS-DMRS association field is associated with the first panel, and the second PTRS-DMRS association field is associated with the second panel. These panels can be the panels that the UE 904 uses to communicate with the NW 904 at operation 908. The panels can correspond to... Figure 7 The panel described in the text.

[0152] On one hand, (SFN 2.10), when NW 904 uses SFN STxMP operation based on a single DCI to configure UE902 (e.g., at operation 906), for non-codebook PUSCH of the SFN scheme, the UE ignores the configuration of “ptrs-PortIndex”, for example, as defined in the SRS resource or SRS resource set.

[0153] It should be understood that, as those skilled in the art would understand, the aspects described in this disclosure are not mutually exclusive and can be combined with each other unless logically incompatible.

[0154] Parts of the content described above can be implemented using logic circuits such as dedicated logic circuits or using microcontrollers or other forms of processing cores that execute program code instructions. Thus, the processes taught in the above discussion can be executed using program code such as machine-executable instructions, which cause the machine to execute these instructions to perform certain functions. In this context, "machine" can be a machine that translates intermediate (or "abstract") instructions into processor-specific instructions (e.g., abstract execution environments such as "virtual machines" (e.g., Java Virtual Machines), interpreters, Common Language Runtimes, high-level language virtual machines, etc.), and / or electronic circuits disposed on semiconductor chips (e.g., "logic circuits" implemented using transistors) designed to execute instructions, such as general-purpose processors and / or dedicated processors. The processes taught in the above discussion can also be executed (as an alternative to or in conjunction with a machine) by electronic circuits designed to execute processes (or parts thereof) without executing program code.

[0155] The present invention also relates to an apparatus for performing the operations described herein. This apparatus may be specifically configured for a desired purpose, or may comprise a general-purpose computer selectively activated or reconfigured by a computer program stored in a computer. Such a computer program may be stored in a computer-readable storage medium, such as, but not limited to, any type of disk, including floppy disks, optical disks, CD-ROMs and magneto-optical disks, read-only memory (ROM), RAM, EPROM, EEPROM, magnetic cards or optical cards, or any type of medium suitable for storing electronic instructions, and each of which is coupled to a computer system bus.

[0156] Machine-readable media include any means by which information is stored or transmitted in a machine-readable (e.g., computer) form. For example, machine-readable media include read-only memory (“ROM”); random access memory (“RAM”); magnetic disk storage media; optical storage media; flash memory devices; and so on.

[0157] A baseband processor (also known as a baseband radio processor, BP, or BBP) is a device (a chip or part of a chip) in a network interface that manages radio functions, such as communication over the antenna (e.g., TX and RX).

[0158] The article of manufacture may be used to store program code. The article of manufacture storing program code may be implemented as, but is not limited to, one or more memories (e.g., one or more flash memories, random access memory (static, dynamic, or other)), optical discs, CD-ROMs, DVD-ROMs, EPROMs, EEPROMs, magnetic cards or optical cards, or other types of machine-readable media suitable for storing electronic instructions. Program code may also be downloaded from a remote computer (e.g., a server) to a requesting computer (e.g., a client) by means of data signals contained in a transmission medium (e.g., via a communication link (e.g., a network connection)).

[0159] The foregoing detailed description has been presented according to the algorithms and symbolic representations used to manipulate data bits within computer memory. These algorithmic descriptions and representations are tools used by those skilled in the art of data processing, and these tools are also the most effective means of communicating the essence of their work to others skilled in the art. An algorithm here and generally refers to a self-consistent sequence of operations that leads to a desired result. These operations are those that require physical manipulation of physical quantities. Often, but not necessarily, these quantities take the form of electrical or magnetic signals that can be stored, transmitted, combined, compared, and otherwise manipulated. It has proven convenient to refer to these signals as bits, values, elements, symbols, characters, terms, numbers, etc., primarily for general reasons.

[0160] However, it should be remembered that all these and similar terms are associated with appropriate physical quantities and are merely convenient labels applied to those quantities. Unless otherwise specifically stated, it is evident from the foregoing discussion that, throughout this specification, the use of terms such as “send,” “transmit,” “select,” “determine,” “receive,” “form,” “group,” “aggregate,” “generate,” “remove,” etc., refers to the actions and processing of computer systems or similar electronic computing devices that can manipulate data represented as physical (electronic) quantities in the registers and memories of the computer system and convert them into other data similarly represented as physical quantities in the computer system’s memory or registers or other such information storage, transmission, or display devices.

[0161] The processes and displays presented herein are not inherently related to any particular computer or other device. Various general-purpose systems can be used with programs based on the teachings herein, or can prove convenient for constructing more specialized devices to perform the operations described herein. The necessary structures for various such systems will be apparent from the description below. Furthermore, the invention is not described with reference to any particular programming language. It should be understood that various programming languages ​​can be used to implement the teachings of the invention as described herein.

[0162] As is widely recognized, the use of personally identifiable information should comply with privacy policies and practices that are generally accepted to meet or exceed industry or governmental requirements for protecting user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of authorized use should be clearly explained to users.

[0163] The foregoing discussion has described only some exemplary aspects of the invention. Those skilled in the art will readily recognize from these discussions, drawings, and claims that various modifications can be made without departing from the spirit and scope of the invention.

Claims

1. A method performed by a network communicating with a user equipment (UE), the method comprising: The network sends downlink control information (DCI) signals to the UE, the DCI signals including indications associated with UE operation under spatial division multiplexing (SDM) across multiple panels simultaneously (STxMP); and The communication with the UE is based on the maximum layer number associated with the indication.

2. The method of claim 1, wherein the indication includes instructions for transitioning from STxMP to a single transmit and receive point (sTRP); and wherein the maximum number of layers associated with the indication includes a maximum number of layers associated with the sTRP, the maximum number of layers being equal to or less than twice the maximum number of layers associated with each individual panel used for STxMP.

3. The method of claim 1, wherein the indication includes instructions for transitioning from STxMP to a single transmit and receive point (sTRP); and wherein the maximum number of layers associated with the indication includes a maximum number of layers associated with the sTRP, the maximum number of layers being equal to the maximum number of layers associated with each individual panel used for STxMP.

4. The method of claim 1, wherein the indication includes instructions for transitioning from a single transmit and receive point (sTRP) to STxMP; and wherein the maximum number of layers associated with the indication includes a maximum number of layers associated with the sTRP, the maximum number of layers being less than or equal to a maximum number of layers used with the sTRP.

5. The method of claim 1, wherein the network configures the UE using a maximum number of ports for uplink phase tracking reference signals (PTRS), the maximum number of ports being set to n1 or n2 in the PTRS-uplink configuration.

6. The method of claim 5, wherein the maximum number of ports used for the PTRS is set to n2.

7. The method of claim 6, wherein when dynamic switching between SDM and Single Transmit and Receive Point (sTRP) is configured, and when the network schedules the sTRP, the network operates under the assumption that only a single port is used for uplink (UL) PTRS.

8. The method of claim 6, wherein when dynamic switching between SDM and single transmit and receive point (sTRP) is configured, and when the network schedules the sTRP, the network operates under the assumption of two ports for uplink (UL) PTRS.

9. The method of claim 1, wherein when the UE is configured using a two-port uplink (UL) PTRS, and when dynamic handover between SDM and single transmit and receive point (sTRP) is configured, and when the network schedules the sTRP, the network assumes a one-port UL PTRS in response to at least one of the following: i) the network configures fully coherent physical uplink shared channel (PUSCH) operation for the sTRP, or ii) the network configures incoherent PUSCH operation for the sTRP with a single port, wherein for codebook operation, the number of ports is the number of probe reference signal (SRS) ports of the SRS-Resource in the SRS-ResourceSet whose purpose is set to codebook, and for non-codebook operation, the number of ports is equal to the number of SRS-Resources in the SRS-ResourceSet whose purpose is set to non-codebook.

10. The method of claim 1, wherein when the UE is configured using a two-port uplink (UL) PTRS, and when dynamic handover between SDM and single transmit and receive point (sTRP) is configured, and when the network schedules the sTRP, the network assumes two-port UL PTRS in response to at least one of the following: i) the network configures partially coherent physical uplink shared channel (PUSCH) operation for the sTRP; or ii) the network configures noncoherent PUSCH operation for the sTRP with more than one port, wherein for codebook operation, the number of ports is equal to the number of probe reference signal (SRS) ports of the SRS-Resource in the SRS-ResourceSet whose purpose is set to codebook, and for non-codebook operation, the number of ports is equal to the number of SRS-Resources in the SRS-ResourceSet whose purpose is set to non-codebook.

11. The method of claim 1, wherein when the DCI format of the DCI is 0_1 or 0_2, the network responds to one or more of the following first conditions to set the bit width of the Phase Tracking Reference Signal Demodulation Reference Signal Association (PTRS-DMRS Association) to zero: PTRS-uplink configuration is not configured and the transform pre-decoder is disabled, the transform pre-decoder is enabled, the maximum number of layers for SDM is one and dynamic switching between SDM STxMP and sTRP is not configured, or the maximum number of layers for SDM and sTRP is equal to one and dynamic switching between SDM STxMP and sTRP is configured.

12. The method of claim 11, wherein when the DCI format of the DCI is 0_1 or 0_2, and when the PTRS-uplink configuration is configured and the transform pre-decoder is disabled, and in response to a second condition, the network sets the bit width associated with the PTRS-DMRS to one, the second condition including the maximum number of layers for SDM being equal to one, and the maximum number of layers for sTRP being equal to two, and coherent operation being configured for sTRP, and the dynamic handover between SDM STxMP and sTRP being configured.

13. The method of claim 12, wherein when the DCI format of the DCI is 0_1 or 0_2, in response to the first condition and the second condition not being met, the network sets the bit width associated with the PTRS-DMRS to two.

14. The method of claim 1, wherein when the DCI format of the DCI is 0_1 or 0_2, and when the bit width of the PTRS-DMRS association is two, and when a two-port PTRS is configured, and when SDM STxMP is scheduled, the network associates PTRS port zero with a first DMRS port associated with a first SRS resource set; and the network associates PTRS port one with a second DMRS port associated with a second SRS resource set.

15. The method of claim 1, wherein when the DCI format of the DCI is 0_1 or 0_2, and when the bit width of the PTRS-DMRS association is two, and when a two-port PTRS is configured, and when the SDM STxMP is scheduled, in response to the maximum number of SDM layers being equal to one, the network indicates the PTRS-DMRS association as "00", or the UE operates under the assumption that the PTRS-DMRS association is equal to "00".

16. The method of claim 1, wherein when the DCI format of the DCI is 0_1 or 0_2, and when the bit width associated with PTRS-DMRS is two, and when a two-port PTRS is configured, and when sTRP is scheduled, the network associates PTRS port 0 with a first DMRS port, the first DMRS port being associated with uplink (UL) layers transmitted using Physical Uplink Shared Channel (PUSCH) antenna ports 1000 and 1002, and the network associates PTRS port 1 with a second DMRS port, the second DMRS port being associated with UL layers transmitted using PUSCH antenna ports 1001 and 1003.

17. The method of claim 1, wherein when the DCI format of the DCI is 0_1 or 0_2, and when the bit width of the PTRS-DMRS association is two, and when two-port PTRS is configured, and when sTRP is scheduled, and when coherent transmission is configured for sTRP, the network operates under the assumption of single-port PTRS operation, and the PTRS-DMRS association for UL PTRS port zero is: zero for the first scheduled DMRS port, one for the second scheduled DMRS port, two for the third scheduled DMRS port, and three for the fourth scheduled DMRS port.

18. The method of claim 1, wherein when dynamic scheduling between SDM STxMP and sTRP is configured and two probe reference signals (SRS)-ResourceSets are configured, under codebook operation: when STxMP is scheduled, half of all SRS ports in each SRS-Resource in the SRS-ResourceSet are used for PUSCH scheduling, and when sTRP is scheduled, all of the SRS ports in each SRS-Resource in the SRS-ResourceSet are used for PUSCH scheduling.

19. The method of claim 1, wherein when dynamic scheduling between SDM STxMP and sTRP is configured and two probe reference signals (SRS)-ResourceSets are configured, under codebook operation: when the STxMP is scheduled, half of all SRS-Resources in each SRS-ResourceSet are used for PUSCH scheduling, and when the sTRP is scheduled, all SRS-Resources in each SRS-ResourceSet are used for PUSCH scheduling.

20. The method of claim 1, wherein the network receives from the UE an indication of whether the UE supports dynamic switching between the SDM STxMP and the sTRP.

21. The method of claim 1, further comprising receiving from the UE an indication of whether the UE shares a port between SDM and sTRP.

22. A method performed by a user equipment (UE) communicating with a network, the method comprising: The UE receives downlink control information (DCI) signals from the network, the DCI including indications associated with UE operation under spatial division multiplexing (SDM) simultaneous transmission across multiple panels (STxMP); and Communicating with the network is based on the maximum number of layers associated with the indication.

23. The method of claim 22, wherein the indication includes instructions for transitioning from STxMP to a single transmit and receive point (sTRP); and wherein the maximum number of layers associated with the indication includes a maximum number of layers associated with the sTRP, the maximum number of layers being equal to or less than twice the maximum number of layers associated with each individual panel for STxMP.

24. The method of claim 22, wherein the indication includes instructions for transitioning from STxMP to a single transmit and receive point (sTRP); and wherein the maximum number of layers associated with the indication includes a maximum number of layers associated with the sTRP, the maximum number of layers being equal to the maximum number of layers associated with each individual panel used for STxMP.

25. The method of claim 22, wherein the indication includes instructions for transitioning from a single transmit and receive point (sTRP) to STxMP; and wherein the maximum number of layers associated with the indication includes a maximum number of layers associated with the sTRP, the maximum number of layers being less than or equal to a maximum number of layers used with the sTRP.

26. The method of claim 22, wherein the network configures the UE using a maximum number of ports for uplink phase tracking reference signals (PTRS), the maximum number of ports being set to n1 or n2 in the PTRS-uplink configuration.

27. The method of claim 26, wherein the maximum number of ports used for the PTRS is set to n2.

28. The method of claim 27, wherein when dynamic switching between SDM and Single Transmit and Receive Point (sTRP) is configured, and when the network schedules the sTRP, the network operates under the assumption that only a single port is used for uplink (UL) PTRS.

29. The method of claim 27, wherein when dynamic switching between SDM and single transmit and receive point (sTRP) is configured, and when the network schedules the sTRP, the network operates under the assumption of two ports for uplink (UL) PTRS.

30. The method of claim 22, wherein when the UE is configured using a two-port uplink (UL) PTRS, and when dynamic handover between SDM and single transmit and receive point (sTRP) is configured, and when the network schedules the sTRP, the network assumes a one-port UL PTRS in response to at least one of the following: i) the network configures fully coherent physical uplink shared channel (PUSCH) operation for the sTRP, or ii) the network configures non-coherent PUSCH operation for the sTRP with a single port, wherein for codebook operation, the number of ports is the number of probe reference signal (SRS) ports of the SRS-Resource in the SRS-ResourceSet whose purpose is set to codebook, and for non-codebook operation, the number of ports is equal to the number of SRS-Resources in the SRS-ResourceSet whose purpose is set to non-codebook.

31. The method of claim 22, wherein when the UE is configured using a two-port uplink (UL) PTRS, and when dynamic handover between SDM and single transmit and receive point (sTRP) is configured, and when the network schedules the sTRP, the network assumes two-port UL PTRS in response to at least one of the following: i) the network configures partially coherent physical uplink shared channel (PUSCH) operation for the sTRP; or ii) the network configures non-coherent PUSCH operation for the sTRP with more than one port, wherein for codebook operation, the number of ports is equal to the number of probe reference signal (SRS) ports of the SRS-Resource in the SRS-ResourceSet whose purpose is set to codebook, and for non-codebook operation, the number of ports is equal to the number of SRS-Resources in the SRS-ResourceSet whose purpose is set to non-codebook.

32. The method of claim 22, wherein when the DCI format of the DCI is 0_1 or 0_2, the network responds to one or more of the following first conditions to set the bit width of the Phase Tracking Reference Signal Demodulation Reference Signal Association (PTRS-DMRS Association) to zero: PTRS-uplink configuration is not configured and the transform pre-decoder is disabled, the transform pre-decoder is enabled, the maximum number of layers for SDM is one and dynamic switching between SDM STxMP and sTRP is not configured, or the maximum number of layers for SDM and sTRP is equal to one and dynamic switching between SDM STxMP and sTRP is configured.

33. The method of claim 32, wherein when the DCI format of the DCI is 0_1 or 0_2, and when the PTRS-uplink configuration is configured and the transform pre-decoder is disabled, and in response to a second condition, the network sets the bit width associated with the PTRS-DMRS to one, the second condition including the maximum number of layers for SDM being equal to one, and the maximum number of layers for sTRP being equal to two, and coherent operation being configured for sTRP, and the dynamic handover between SDM STxMP and sTRP being configured.

34. The method of claim 33, wherein when the DCI format of the DCI is 0_1 or 0_2, in response to the first condition and the second condition not being met, the network sets the bit width associated with the PTRS-DMRS to two.

35. The method of claim 22, wherein when the DCI format of the DCI is 0_1 or 0_2, and when the bit width of the PTRS-DMRS association is two, and when a two-port PTRS is configured, and when an SDM STxMP is scheduled, the network associates PTRS port zero with a first DMRS port associated with a first SRS resource set; and the network associates PTRS port one with a second DMRS port associated with a second SRS resource set.

36. The method of claim 22, wherein when the DCI format of the DCI is 0_1 or 0_2, and when the bit width of the PTRS-DMRS association is two, and when a two-port PTRS is configured, and when the SDM STxMP is scheduled, in response to the maximum number of SDM layers being equal to one, the network indicates the PTRS-DMRS association as "00", or the UE operates under the assumption that the PTRS-DMRS association is equal to "00".

37. The method of claim 22, wherein when the DCI format of the DCI is 0_1 or 0_2, and when the bit width associated with the PTRS-DMRS is two, and when a two-port PTRS is configured, and when sTRP is scheduled, the network associates PTRS port 0 with a first DMRS port, the first DMRS port being associated with uplink (UL) layers transmitted using Physical Uplink Shared Channel (PUSCH) antenna ports 1000 and 1002, and the network associates PTRS port 1 with a second DMRS port, the second DMRS port being associated with UL layers transmitted using PUSCH antenna ports 1001 and 1003.

38. The method of claim 22, wherein when the DCI format of the DCI is 0_1 or 0_2, and when the bit width of the PTRS-DMRS association is two, and when two-port PTRS is configured, and when sTRP is scheduled, and when coherent transmission is configured for sTRP, the network operates under the assumption of single-port PTRS operation, and the PTRS-DMRS association for UL PTRS port zero is: zero for the first scheduled DMRS port, one for the second scheduled DMRS port, two for the third scheduled DMRS port, and three for the fourth scheduled DMRS port.

39. The method of claim 22, wherein when dynamic scheduling between SDM STxMP and sTRP is configured and two probe reference signals (SRS)-ResourceSets are configured, under codebook operation: when STxMP is scheduled, half of all SRS ports in each SRS-Resource in the SRS-ResourceSet are used for PUSCH scheduling, and when sTRP is scheduled, all of the SRS ports in each SRS-Resource in the SRS-ResourceSet are used for PUSCH scheduling.

40. The method of claim 22, wherein when dynamic scheduling between SDM STxMP and sTRP is configured and two probe reference signals (SRS)-ResourceSets are configured, under codebook operation: when the STxMP is scheduled, half of all SRS-Resources in each SRS-ResourceSet are used for PUSCH scheduling, and when the sTRP is scheduled, all SRS-Resources in each SRS-ResourceSet are used for PUSCH scheduling.

41. The method of claim 22, wherein the network receives from the UE an indication of whether the UE supports dynamic switching between the SDM STxMP and the sTRP.

42. The method of claim 22, further comprising receiving from the UE an indication of whether the UE shares a port between SDM and sTRP.

43. A method performed by a network communicating with a user equipment (UE), the method comprising: The network sends downlink control information (DCI) signals to the UE, the DCI including indications associated with UE operation under Single Frequency Network (SFN) simultaneous transmission across multiple panels (STxMP); and The communication with the UE is based on the maximum layer number associated with the indication.

44. The method of claim 43, wherein the indication includes instructions for transitioning from STxMP to a single transmit and receive point (sTRP); and wherein the maximum number of layers associated with the indication includes a maximum number of layers associated with the sTRP, the maximum number of layers being equal to or less than twice the maximum number of layers associated with each individual panel for STxMP.

45. The method of claim 43, wherein the indication includes instructions for transitioning from STxMP to a single transmit and receive point (sTRP); and wherein the maximum number of layers associated with the indication includes a maximum number of layers associated with the sTRP, the maximum number of layers being equal to or greater than the maximum number of layers associated with each individual panel used for STxMP.

46. ​​The method of claim 43, wherein for codebook-based Physical Uplink Shared Channel (PUSCH) operation, the network configures the same coherence mode for each panel.

47. The method of claim 43, wherein when dynamically switching between SFN STxMPs, both SFN STxMPs and sTRPs are configured using the same coherent mode for codebook-based Physical Uplink Shared Channel (PUSCH) operation.

48. The method of claim 43, wherein the network further configures the UE using a maximum number of ports for uplink phase tracking reference signals (PTRS), the maximum number of ports being set to n1 or n2 in the PTRS-uplink configuration.

49. The method of claim 43, wherein the network further configures the UE using a maximum number of ports for uplink phase tracking reference signals (PTRS), the maximum number of ports being set to n2 in the PTRS-uplink configuration.

50. The method of claim 43, wherein when the UE is configured using a two-port uplink (UL) PTRS, and when dynamic handover between the SFN and a single transmit and receive point (sTRP) is configured, and when the network schedules the sTRP, the network assumes one or two ports are used for UL PTRS.

51. The method of claim 43, wherein when the UE is configured using a two-port uplink (UL) PTRS, and when dynamic handover between the SFN and a single transmit and receive point (sTRP) is configured, and when the network schedules the sTRP, the network assumes a port for UL PTRS in response to at least one of the following: i) the network configures fully coherent physical uplink shared channel (PUSCH) operation for the sTRP, or ii) the network configures single-port incoherent PUSCH operation for the sTRP, wherein for codebook operation, the number of ports is the number of probe reference signal (SRS) ports of the SRS-Resource in the SRS-ResourceSet whose purpose is set to codebook, and for non-codebook operation, the number of ports is the number of the SRS-Resources in the SRS-ResourceSet whose purpose is set to non-codebook.

52. The method of claim 43, wherein when the UE is configured using a two-port uplink (UL) PTRS, and when dynamic handover between SDM and single transmit and receive point (sTRP) is configured, and when the network schedules the sTRP, the network assumes two-port UL PTRS in response to at least one of the following: i) the network configures partially coherent physical uplink shared channel (PUSCH) operation for the sTRP, or ii) the network configures noncoherent PUSCH operation for the sTRP with more than one port, wherein for codebook operation, the number of ports is equal to the number of probe reference signal (SRS) ports of the SRS-Resource in the SRS-ResourceSet whose purpose is set to codebook, and for non-codebook operation, the number of ports is equal to the number of SRS-Resources in the SRS-ResourceSet whose purpose is set to non-codebook.

53. The method of claim 43, wherein when the DCI format of the DCI is 0_1 or 0_2, the network responds to one or more of the following first conditions to set the bit width of the Phase Tracking Reference Signal Demodulation Reference Signal Association (PTRS-DMRS Association) to zero: PTRS-uplink configuration is not configured and the transform pre-decoder is disabled, the transform pre-decoder is enabled, the maximum number of layers for the SFN is one and dynamic switching between the SFN STxMP and sTRP is not configured, or the maximum number of layers for the SFN and sTRP is equal to one and dynamic switching between the SFN STxMP and sTRP is configured.

54. The method of claim 53, wherein when the DCI format of the DCI is 0_1 or 0_2, and when the PTRS-uplink configuration is configured and the transform pre-decoder is disabled, and in response to a second condition, the network sets the bit width associated with the PTRS-DMRS to one, the second condition including the maximum number of layers for SFN being equal to one, the maximum number of layers for sTRP being equal to two, coherent operation being configured for sTRP, and the dynamic handover between SFN STxMP and sTRP being configured.

55. The method of claim 54, wherein when the DCI format of the DCI is 0_1 or 0_2, in response to the first condition and the second condition not being met, the network sets the bit width associated with the PTRS-DMRS to two.

56. The method of claim 43, wherein when the DCI format of the DCI is 0_1 or 0_2, and when the bit width of the PTRS-DMRS association is two, and when a two-port PTRS is configured, and when SFN STxMP is scheduled, the network associates PTRS port zero with a first DMRS port associated with a first SRS resource set; and the network associates PTRS port one with a second DMRS port associated with a second SRS resource set.

57. The method of claim 43, wherein when the DCI format of the DCI is 0_1 or 0_2, and when the bit width of the PTRS-DMRS association is two, and when a two-port PTRS is configured, and when the SFN STxMP is scheduled, in response to the maximum number of layers of the SFN being equal to one, the network indicates the PTRS-DMRS association as "00", or the UE operates under the assumption that the PTRS-DMRS association is equal to "00".

58. The method of claim 43, wherein when the DCI format of the DCI is 0_1 or 0_2, and when the bit width associated with PTRS-DMRS is two, and when a two-port PTRS is configured, and when sTRP is scheduled, the network associates PTRS port 0 with a first DMRS port, the first DMRS port being associated with uplink (UL) layers transmitted using Physical Uplink Shared Channel (PUSCH) antenna ports 1000 and 1002, and the network associates PTRS port 1 with a second DMRS port, the second DMRS port being associated with UL layers transmitted using PUSCH antenna ports 1001 and 1003.

59. The method of claim 43, wherein when the DCI format of the DCI is 0_1 or 0_2, and when the bit width of the PTRS-DMRS association is two, and when two-port PTRS is configured, and when sTRP is scheduled, and when coherent transmission is configured for sTRP, the network operates under the assumption of single-port PTRS operation, and the PTRS-DMRS association for UL PTRS port zero is: zero for the first scheduled DMRS port, one for the second scheduled DMRS port, two for the third scheduled DMRS port, and three for the fourth scheduled DMRS port.

60. The method of claim 43, wherein when the DCI format of the DCI is 0_1 or 0_2, the network includes two PTRS-DMRS association fields in the DCI, wherein when the network schedules SFN STxMP, the two PTRS-DMRS association fields are used, and when the network schedules sTRP, the first PTRS-DMRS association field is used instead of the second PTRS-DMRS association field.

61. The method of claim 43, wherein when the DCI format of the DCI is 0_1 or 0_2, and when the DCI includes the two PTRS-DMRS association fields, the first PTRS-DMRS association field is associated with the first panel, and the second PTRS-DMRS association field is associated with the second panel.

62. The method of claim 43, wherein for a non-codebook physical uplink shared channel (PUSCH) with an SFN, the UE ignores the PTRS port index.

63. A method performed by a user equipment (UE) connected to a network, the method comprising: The UE receives downlink control information (DCI) signals from the network, the DCI including indications associated with UE operation under Single Frequency Network (SFN) simultaneous transmission across multiple panels (STxMP); and Communicating with the network is based on the maximum number of layers associated with the indication.

64. The method of claim 63, wherein the indication includes instructions for transitioning from STxMP to a single transmit and receive point (sTRP); and wherein the maximum number of layers associated with the indication includes a maximum number of layers associated with the sTRP, the maximum number of layers being equal to or less than twice the maximum number of layers associated with each individual panel used for STxMP.

65. The method of claim 63, wherein the indication includes instructions for transitioning from STxMP to a single transmit and receive point (sTRP); and wherein the maximum number of layers associated with the indication includes a maximum number of layers associated with the sTRP, the maximum number of layers being equal to or greater than the maximum number of layers associated with each individual panel used for STxMP.

66. The method of claim 63, wherein for codebook-based Physical Uplink Shared Channel (PUSCH) operation, the network configures the same coherence mode for each panel.

67. The method of claim 63, wherein when dynamically switching between SFN STxMPs, the same coherent mode is used to configure both SFN STxMPs and sTRPs for codebook-based Physical Uplink Shared Channel (PUSCH) operation.

68. The method of claim 63, wherein the network further configures the UE using a maximum number of ports for uplink phase tracking reference signals (PTRS), the maximum number of ports being set to n1 or n2 in the PTRS-uplink configuration.

69. The method of claim 63, wherein the network further configures the UE using a maximum number of ports for uplink phase tracking reference signals (PTRS), the maximum number of ports being set to n2 in the PTRS-uplink configuration.

70. The method of claim 63, wherein when the UE is configured using a two-port uplink (UL) PTRS, and when dynamic handover between the SFN and a single transmit and receive point (sTRP) is configured, and when the network schedules the sTRP, the network assumes one or two ports are used for UL PTRS.

71. The method of claim 63, wherein when the UE is configured using a two-port uplink (UL) PTRS, and when dynamic handover between the SFN and a single transmit and receive point (sTRP) is configured, and when the network schedules the sTRP, the network assumes a port for UL PTRS in response to at least one of the following: i) the network configures fully coherent physical uplink shared channel (PUSCH) operation for the sTRP, or ii) the network configures single-port incoherent PUSCH operation for the sTRP, wherein for codebook operation, the number of ports is the number of probe reference signal (SRS) ports of the SRS-Resource in the SRS-ResourceSet whose purpose is set to codebook, and for non-codebook operation, the number of ports is the number of SRS-Resources in the SRS-ResourceSet whose purpose is set to non-codebook.

72. The method of claim 63, wherein when the UE is configured using a two-port uplink (UL) PTRS, and when dynamic handover between SDM and single transmit and receive point (sTRP) is configured, and when the network schedules the sTRP, the network assumes two-port UL PTRS in response to at least one of the following: i) the network configures partially coherent physical uplink shared channel (PUSCH) operation for the sTRP, or ii) the network configures non-coherent PUSCH operation for the sTRP with more than one port, wherein for codebook operation, the number of ports is equal to the number of probe reference signal (SRS) ports of the SRS-Resource in the SRS-ResourceSet whose purpose is set to codebook, and for non-codebook operation, the number of ports is equal to the number of SRS-Resources in the SRS-ResourceSet whose purpose is set to non-codebook.

73. The method of claim 63, wherein when the DCI format of the DCI is 0_1 or 0_2, the network responds to one or more of the following first conditions to set the bit width of the Phase Tracking Reference Signal Demodulation Reference Signal Association (PTRS-DMRS Association) to zero: PTRS-uplink configuration is not configured and the transform pre-decoder is disabled, the transform pre-decoder is enabled, the maximum number of layers for the SFN is one and dynamic switching between the SFN STxMP and sTRP is not configured, or the maximum number of layers for the SFN and sTRP is equal to one and dynamic switching between the SFN STxMP and sTRP is configured.

74. The method of claim 73, wherein when the DCI format of the DCI is 0_1 or 0_2, and when the PTRS-uplink configuration is configured and the transform pre-decoder is disabled, and in response to a second condition, the network sets the bit width associated with the PTRS-DMRS to one, the second condition including the maximum number of layers for SFN being equal to one, the maximum number of layers for sTRP being equal to two, coherent operation being configured for sTRP, and the dynamic handover between SFN STxMP and sTRP being configured.

75. The method of claim 74, wherein when the DCI format of the DCI is 0_1 or 0_2, in response to the first condition and the second condition not being met, the network sets the bit width associated with the PTRS-DMRS to two.

76. The method of claim 63, wherein when the DCI format of the DCI is 0_1 or 0_2, and when the bit width of the PTRS-DMRS association is two, and when a two-port PTRS is configured, and when SFN STxMP is scheduled, the network associates PTRS port zero with a first DMRS port associated with a first SRS resource set; and the network associates PTRS port one with a second DMRS port associated with a second SRS resource set.

77. The method of claim 63, wherein when the DCI format of the DCI is 0_1 or 0_2, and when the bit width of the PTRS-DMRS association is two, and when a two-port PTRS is configured, and when the SFN STxMP is scheduled, in response to the maximum number of layers of the SFN being equal to one, the network indicates the PTRS-DMRS association as "00", or the UE operates under the assumption that the PTRS-DMRS association is equal to "00".

78. The method of claim 63, wherein when the DCI format of the DCI is 0_1 or 0_2, and when the bit width associated with the PTRS-DMRS is two, and when a two-port PTRS is configured, and when sTRP is scheduled, the network associates PTRS port 0 with a first DMRS port, the first DMRS port being associated with uplink (UL) layers transmitted using Physical Uplink Shared Channel (PUSCH) antenna ports 1000 and 1002, and the network associates PTRS port 1 with a second DMRS port, the second DMRS port being associated with UL layers transmitted using PUSCH antenna ports 1001 and 1003.

79. The method of claim 63, wherein when the DCI format of the DCI is 0_1 or 0_2, and when the bit width of the PTRS-DMRS association is two, and when two-port PTRS is configured, and when sTRP is scheduled, and when coherent transmission is configured for sTRP, the network operates under the assumption of single-port PTRS operation, and the PTRS-DMRS association for UL PTRS port zero is: zero for the first scheduled DMRS port, one for the second scheduled DMRS port, two for the third scheduled DMRS port, and three for the fourth scheduled DMRS port.

80. The method of claim 63, wherein when the DCI format of the DCI is 0_1 or 0_2, the network includes two PTRS-DMRS association fields in the DCI, wherein when the network schedules SFN STxMP, the two PTRS-DMRS association fields are used, and when the network schedules sTRP, the first PTRS-DMRS association field is used instead of the second PTRS-DMRS association field.

81. The method of claim 63, wherein when the DCI format of the DCI is 0_1 or 0_2, and when the DCI includes the two PTRS-DMRS association fields, the first PTRS-DMRS association field is associated with the first panel, and the second PTRS-DMRS association field is associated with the second panel.

82. The method of claim 63, wherein for a non-codebook physical uplink shared channel (PUSCH) with an SFN, the UE ignores the PTRS port index.

Images