Demodulation reference signal configuration and resource mapping method

Abstract

This disclosure provides systems, apparatus, apparatus, and methods, including computer programs encoded on a storage medium, for DMRS configuration. The UE receives (904) control signaling that causes the UE to enable at least one of: a number of eType1 or eType2 DMRS antenna ports, a minimum FD-OCC dispreading length, or at least one isolated RE handling scheme. The UE receives (306) a DCI that schedules a physical shared channel for at least one of: at least one indicated eType1 / eType2 DMRS antenna port, an indicated FD-OCC dispreading length, or an indicated isolated RE handling scheme. The UE communicates with the network entity on the physical shared channel based on at least one of: the at least one indicated eType1 / eType2 DMRS antenna port, the indicated FD-OCC dispreading length, or the indicated isolated RE handling scheme (911).

Description

Technical Field

[0001] The present disclosure relates generally to wireless communications, and more particularly to demodulation reference signal (DMRS) configurations. Background Art

[0002] The 3rd Generation Partnership Project (3GPP) specifies a radio interface called fifth generation (5G) New Radio (NR) (5G NR). The architecture of a 5G NR wireless communication system may include a 5G core (5GC) network, a 5G radio access network (5G-RAN), user equipment (UE), etc. Compared to other types of wireless communication systems, the 5G NR architecture may provide increased data rates, reduced latency, and / or increased capacity.

[0003] Wireless communication systems can generally be configured to provide various telecommunication services (e.g., telephone, video, data, messaging, broadcast, etc.) based on multiple access technologies (such as orthogonal frequency division multiple access (OFDMA) technologies) that support communication with multiple UEs. With the development of mobile broadband technology, the improvement of mobile broadband helps to continue the advancement of such technology. For example, 3GPP recently introduced support for more antenna ports with higher-order frequency domain orthogonal cover codes (FD-OCC) to support higher-order multi-purpose multiple input multiple output (MU-MIMO) configurations, but some configurations may result in degradation of system performance. Summary of the invention

[0004] The following presents a simplified overview of one or more aspects in order to provide a basic understanding of such aspects. This overview is not an extensive review of all contemplated aspects. This overview neither identifies the key or important elements of all aspects, nor describes the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to a more detailed description presented later.

[0005] The present disclosure describes methods and systems for configuring uplink and downlink enhanced Type 1 (eType 1) and eType 2 demodulation reference signals (DMRS). A wireless receiver (e.g., a user equipment (UE) in some cases, or a base station (BS) or a network entity of the BS in other cases) estimates a radio channel using a downlink DMRS provided by the network entity of the BS and an uplink DMRS provided by the UE. After the receiver estimates the radio channel, the receiver decodes a data channel based on the radio channel estimate.

[0006] A resource block (RB) as defined by the 3GPP standard includes 144 resource elements (REs) that can provide communication resources for a UE. In previous 3GPP releases, such as Release 15, Type 1 DMRS supports two code domain orthogonal groups (e.g., code division multiplexing (CDM) group 0 and CDM group 1), and Type 2 DMRS supports three groups (CDM groups 0, 1, and 2). In order to distinguish antenna ports, DMRS has two frequency domain orthogonal cover codes (FD-OCC) (e.g., antenna port 0 = 1, antenna port 1 = -1). In summary, in Release 15, Type 1 DMRS supports 8 antenna ports, which corresponds to two CDM groups × two symbols associated with a time domain orthogonal cover code (TD-OCC) × two FD-OCCs. Release 15 Type 2 DMRS supports 12 antenna ports, which corresponds to three CDM groups × two TD-OCCs × two FD-OCCs.

[0007] As the demand for wireless data traffic continues to increase, Release 18 introduces more antenna ports with higher-order FD-OCC to support higher-order multi-purpose multiple-input multiple-output (MU-MIMO) configurations. On the basis of Release 15 Type 1 DMRS (e.g., 2 CDM groups and 2 TD-OCCs), eType1 DMRS adds two FD-OCCs to provide FD-OCC-4. In short, eType1 DMRS supports 16 antenna ports. Similarly, eType2 defines 3 CDM groups with FD-OCC-4 and TD-OCC-2. In short, eType2 DMRS supports 24 antenna ports.

[0008] However, some technical problems may arise with eType1 and eType2 DMRS. First, because eType1 and eType2 DMRS support higher-order antenna ports, the overhead used to indicate the antenna ports of eType1 and eType2 DMRS increases. Second, because the UE receiver may not have information about co-scheduled UEs when the base station transmitter uses MU-MIMO, the UE may apply the maximum FD-OCC-4 despreading. As a result, the UE may become inefficient, which may degrade the performance of the wireless system. Third, applying FD-OCC-4 to each RE set within a CDM group may result in remaining REs, which may be referred to as "orphan REs" that include DMRS signals that do not support antenna ports. Therefore, orphan REs result in a waste of resources and potential confusion when identifying antenna ports.

[0009] In order to overcome the above technical problems, the method and system configure the UE to handle eType1 and eType2 DMRS, which includes the maximum number of DMRS antenna ports, FD-OCC despreading length and / or control signaling of the type of isolated RE handling. For example, the UE of the present disclosure may send a capability report to the serving BS, which capability report indicates that the UE can support eType1 and eType2 DMRS. In addition, the capability report may include the maximum total number of antenna ports supported by the UE and / or the isolated RE handling scheme supported by the UE. After the UE sends the capability report, the UE receives control signaling from the network entity. The UE may receive control signaling via a radio resource control (RRC) message or downlink control information (DCI). The control signaling enables the UE to enable eType1 and eType2 DMRS. Then, the UE communicates with the network entity on a physical shared channel according to the control signaling. The physical shared channel may be a physical uplink shared channel (PUSCH) or a physical downlink shared channel (PDSCH). When decoding the PDSCH, the UE determines which antenna ports are being used, which despreading length is used, and how to handle isolated REs.

[0010] On the network side, in response to receiving the UE capability report, the serving BS configures the UE to enable eType1 and eType2 DMRS. In these implementations, the network entity and the UE may communicate on the PUSCH or the PDSCH (or both).

[0011] Therefore, the method and system overcome the technical problems faced by eType 1 and eType 2 DMRS.The method and system handles the problems of higher order FD-OCC overhead and orphaned REs which may lead to degraded system performance.

[0012] To accomplish the foregoing and related purposes, one or more aspects correspond to the features described below and particularly pointed out in the claims. One or more aspects can be implemented by any of an apparatus, a method, a component for executing the method, and / or a non-transitory computer-readable medium. The following description and the accompanying drawings set forth in detail certain illustrative features of one or more aspects. However, these features indicate only a few of the various ways in which the principles of the various aspects can be employed. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] Figure 1 A diagram of a wireless communication system including multiple network entities communicating over multiple cells is shown.

[0014] Figure 2A A diagram showing an example of DMRS symbol positions for Type 1 DMRS according to some embodiments.

[0015] Figure 2B A diagram showing an example of DMRS symbol positions for Type 2 DMRS according to some embodiments.

[0016] Figure 2C A diagram showing an example of DMRS symbol positions for an eType 1 DMRS according to some embodiments.

[0017] Figure 2D A diagram showing an example of DMRS symbol locations for an eType 2 DMRS according to some embodiments.

[0018] Figure 3 A signaling diagram illustrating an example scenario in which a user equipment (UE) and a network entity exchange messages and implement procedures for downlink eType 1 and eType 2 DMRS configuration and resource mapping according to some embodiments.

[0019] Figure 4 is a flow chart illustrating an example method of downlink eType1 and eType2 DMRS configuration and resource mapping implemented in a UE according to some embodiments.

[0020] Figure 5 is a flow chart illustrating an example method of downlink eType 1 and eType 2 DMRS configuration and resource mapping implemented in a network entity according to some embodiments.

[0021] Figure 6 A signaling diagram illustrating an example scenario in which a UE and a network entity exchange messages and implement procedures for uplink eType1 and eType2 DMRS configuration and resource mapping according to some embodiments.

[0022] Figure 7 is a flow chart illustrating an example method of uplink eType1 and eType2 DMRS configuration and resource mapping implemented in a UE according to some embodiments.

[0023] Figure 8 is a flow chart illustrating an example method of uplink eType 1 and eType 2 DMRS configuration and resource mapping implemented in a network entity according to some embodiments.

[0024] Fig. 9 A signaling diagram illustrating an example scenario in which a UE and a network entity exchange messages and implement procedures for uplink and downlink eType 1 and eType 2 DMRS configuration and resource mapping according to some embodiments.

[0025] Fig.10is a flow chart illustrating an example method of downlink and uplink eType1 and eType2 DMRS configuration and resource mapping implemented in a UE according to some embodiments.

[0026] Fig.11 is a flow chart illustrating an example method of downlink and uplink eType1 and eType2 DMRS configuration and resource mapping implemented in a network entity according to some embodiments.

[0027] Fig. 12A A diagram showing an example of DMRS symbol locations within isolated REs according to some embodiments.

[0028] Fig. 12B A diagram showing examples of DMRS symbol positions for overlapping despreading windows according to some embodiments.

[0029] FIG. 12C to FIG. 12D An example table showing PT-RS RE offset configuration for eType1 / eType2 DMRS according to some embodiments.

[0030] Fig.12E Table showing an example of a joint indication of DMRS port and minimum FD-OCC despreading length according to some embodiments.

[0031] Fig.12F A table showing an example of eType 1 DMRS port indication with a single frontloading symbol according to some embodiments, and the maximum number of ports indicated is {1}.

[0032] Figure 12G A table showing an example of eType 1 DMRS port indication with a single front-loading symbol according to some embodiments, and the candidate number of the indicated ports is {1, 2, 4}.

[0033] Fig.13 is a diagram illustrating an example of a hardware implementation of an example UE equipment.

[0034] Fig.14 are diagrams illustrating examples of hardware implementations of one or more example network entities. DETAILED DESCRIPTION

[0035] Figure 1A diagram 100 of a wireless communication system associated with a plurality of cells 190 is shown. The wireless communication system includes a user equipment (UE) 102 and base stations 104, some of which 104a include an aggregated base station architecture and other base stations 104b include a decomposed base station architecture. The aggregated base station architecture includes a radio unit (RU) 106, a distributed unit (DU) 108, and a centralized unit (CU) 110, which are configured to utilize a radio protocol stack physically or logically integrated within a single radio access network (RAN) node. The decomposed base station architecture utilizes a protocol stack physically or logically distributed between two or more units (e.g., RU 106, DU 108, CU 110). For example, CU 110 is implemented within a RAN node, and one or more DUs 108 may be co-located with CU 110, or alternatively, may be geographically or virtually distributed in one or more other RAN nodes. DU 108 may be implemented to communicate with one or more RU 106. Each of the RU 106, DU 108, and CU 110 may be implemented as a virtual unit, such as a virtual radio unit (VRU), a virtual distributed unit (VDU), or a virtual central unit (VCU).

[0036] The operation and / or network design of the base station 104 can be based on the aggregated nature of the base station functions. For example, a decomposed base station architecture is utilized in an integrated access backhaul (IAB) network, an open radio access network (O-RAN) network, or a virtualized radio access network (vRAN), which may also be referred to as a cloud radio access network (C-RAN). Decomposition may include distributing functions between two or more units located at various physical locations, and virtually distributing the functions of at least one unit, which enables flexibility in network design. Various units of the decomposed base station architecture or decomposed RAN architecture may be configured to communicate with at least one other unit in wired or wireless communication. For example, CU 110a communicates with DU108a-108b via corresponding midhaul links based on the F1 interface. DU 108a-108b may communicate with RU 106a and RU 106b-106c, respectively, via corresponding fronthaul links. RU 106a-106c can communicate with corresponding UE 102a-102c and 102s via one or more radio frequency (RF) access links based on Uu interface. In an example, multiple RU 106 and / or base station 104 can provide services for UE 102 at the same time, such as the access link of RU 106a of cell 190a and the UE 102a of cell 190e served by base station 104a of cell 190e at the same time.

[0037] One or more CUs 110, such as CU 110a or CU 110d, may communicate directly with the core network 120 via a backhaul link 164. For example, CU 110d communicates with the core network 120 via a backhaul link 164 based on a next generation (NG) interface. One or more CUs 110 may also communicate indirectly with the core network 120 via one or more decomposed base station units, such as a near real-time RAN intelligent controller (RIC) 128 via an E2 link and a service management and orchestration (SMO) framework 116 that may be associated with a non-real-time RIC 118. The near real-time RIC 128 may communicate with the SMO framework 116 and / or the non-real-time RIC 118 via an A1 link. The SMO framework 116 and / or the non-real-time RIC 118 may also communicate with an open cloud (O-cloud) 130 via an O2 link. One or more CUs 110 may further communicate with each other via a backhaul link 164 based on an Xn interface. For example, the CU 110d of the base station 104a communicates with the CU 110a of the base station 104b via the backhaul link 164 based on the Xn interface. Similarly, the base station 104a of the cell 190e can communicate with the CU 110a of the base station 104b via the backhaul link 164 based on the Xn interface.

[0038] The RU 106, DU 108, and CU 110, as well as the near real-time RIC 128, the non-real-time RIC 118, and / or the SMO framework 116, may include (or may be coupled to) one or more interfaces configured to send or receive information / signals via a wired or wireless transmission medium. The base station 104 or any of the one or more decomposed base station units may be configured to communicate with one or more other base stations 104 or one or more other decomposed base station units via a wired or wireless transmission medium. In an example, a processor, memory, and / or controller associated with executable instructions of the interface may be configured to provide communication between the base station 104 and / or one or more decomposed base station units via a wired or wireless transmission medium. For example, the wired interface may be configured to send or receive information / signals through a wired transmission medium, such as a fronthaul link 160 between the RU 106d and the baseband unit (BBU) 112 for the cell 190d, or more specifically, a fronthaul link 160 between the RU 106d and the DU 108d. The BBU 112 includes the DU 108d and the CU 110d, which may also have a wired interface configured between the DU 108d and the CU 110d to send or receive information / signals between the DU 108d and the CU 110d based on the midhaul link 162. In a further example, a wireless interface, which may include a receiver, transmitter, or transceiver (such as an RF transceiver), may be configured to send or receive information / signals via a wireless transmission medium, such as information for transmission between RU 106a of cell 190a and base station 104a of cell 190e via a cross-cell communication beam between RU 106a and base station 104a.

[0039] One or more high-level control functions (such as functions related to radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc.) can be hosted at CU 110. Each control function can be associated with an interface for transmitting signals based on one or more other control functions hosted at CU 110. User plane functions (such as central unit-user plane (CU-UP) functions), control plane functions (such as central unit-control plane (CU-CP) functions), or a combination thereof can be implemented based on CU 110. For example, CU 110 may include one or more CU-UP processes and / or one or more CU-CP processes. When implemented in an O-RAN configuration, the CU-UP function can be based on bidirectional communication with the CU-CP function via an interface (such as an E1 interface (not shown)).

[0040] The CU 110 may communicate with the DU 108 for network control and signaling. The DU 108 is a logical unit of the base station 104 that is configured to perform one or more base station functions. For example, the DU 108 may control the operation of one or more RUs 106. One or more of the following may be hosted at the DU 108: a radio link control (RLC) layer, a media access control (MAC) layer, or one or more higher physical (PHY) layers, such as forward error correction (FEC) modules for encoding / decoding, scrambling, modulation / demodulation, etc. The DU 108 may host such functions based on the functional division of the DU 108. The DU 108 may similarly host one or more lower PHY layers, where each lower layer or module may be implemented based on an interface for communicating with other layers and modules hosted at the DU 108, or based on a control function hosted at the CU 110.

[0041] The RU 106 may be configured to implement low-level functions. For example, the RU 106 is controlled by the DU 108 and may correspond to a logical node that hosts RF processing functions or low-level PHY functions, such as performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc. The functions of the RU 106 may be based on functional partitioning, such as low-level functional partitioning.

[0042] The RU 106 may send or receive over-the-air (OTA) communications with one or more UEs 102. For example, the RU 106b of the cell 190b communicates with the UE 102b of the cell 190b via the first communication beam set 132 of the RU 106b and the second communication beam set 134 of the UE 102b, which may correspond to inter-cell communication beams or cross-cell communication beams. Both real-time and non-real-time features of the control plane and user plane communications of the RU 106 may be controlled by the associated DU 108. Thus, the DU 108 and the CU 110 may be used in a cloud-based RAN architecture (such as a vRAN architecture), and the SMO framework 116 may be used to support non-virtualized and virtualized RAN network elements. For non-virtualized network elements, the SMO framework 116 may support the deployment of dedicated physical resources for RAN coverage, where the dedicated physical resources may be managed through an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 116 can interact with a cloud computing platform (such as O-cloud 130) via an O2 link (e.g., a cloud computing platform interface) to manage the network elements. The virtualized network elements may include, but are not limited to, RU 106, DU 108, CU 110, near real-time RIC 128, etc.

[0043] The SMO framework 116 may be configured to communicate directly with one or more RUs 106 using an O1 link. The non-real-time RIC 118 of the SMO framework 116 may also be configured to support the functionality of the SMO framework 116. For example, the non-real-time RIC 118 implements logic functions that are capable of controlling non-real-time RAN features and resources, features / applications of the near real-time RIC 128, and / or artificial intelligence / machine learning (AI / ML) processes. The non-real-time RIC 118 may communicate (or couple) with the near real-time RIC 128, such as through an A1 interface. The near real-time RIC 128 may implement logic functions that are capable of controlling near real-time RAN features and resources based on data collection and interaction through an E2 interface (such as an E2 interface between the near real-time RIC 128 and the CU 110a and the DU 108b).

[0044] The non-real-time RIC 118 may receive parameters or other information from an external server to generate an AI / ML model for deployment in the near-real-time RIC 128. For example, the non-real-time RIC 118 receives parameters or other information from the O-cloud 130 via the O2 link to deploy the AI / ML model to the real-time RIC 128 via the A1 link. The near-real-time RIC 128 may utilize the parameters and / or other information received from the non-real-time RIC 118 or the SMO framework 116 via the A1 link to perform near-real-time functions. The near-real-time RIC 128 and the non-real-time RIC 115 may be configured to adjust the performance of the RAN. For example, the non-real-time RIC 116 monitors patterns and long-term trends to improve the performance of the RAN. The non-real-time RIC 116 may also deploy the AI / ML model through the SMO framework 116 for implementing corrective actions, such as initiating reconfiguration of the O1 link or instructing the management process of the A1 link.

[0045] Any combination of RU 106, DU 108, and CU 110 or any reference thereto individually may correspond to base station 104. Therefore, base station 104 may include at least one of RU 106, DU 108, or CU 110. Base station 104 provides UE 102 with access to core network 120. That is, base station 104 may relay communications between UE 102 and core network 120. Base station 104 may be associated with a macro cell of a high-power cellular base station and / or a small cell of a low-power cellular base station. For example, cell 190e corresponds to a macro cell, and cells 190a-190d may correspond to a small cell. Small cells include femto cells, pico cells, micro cells, etc. A cell structure including at least one macro cell and at least one small cell may be referred to as a "heterogeneous network."

[0046] Transmissions from the UE 102 to the base station 104 / RU 106 are referred to as uplink (UL) transmissions, while transmissions from the base station 104 / RU 106 to the UE 102 are referred to as downlink (DL) transmissions. Uplink transmissions may also be referred to as reverse link transmissions, while downlink transmissions may also be referred to as forward link transmissions. For example, the RU 106 d utilizes the antenna of the base station 104 a of the cell 190 d to send downlink / forward link communications to the UE 102 d, or receive uplink / reverse link communications from the UE 102 d, based on the Uu interface associated with the access link between the UE 102 d and the base station 104 a / RU 106 d.

[0047] The communication link between UE 102 and base station 104 / RU 106 can be based on multiple input multiple output (MIMO) antenna technology, including spatial multiplexing, beamforming and / or transmit diversity. The communication link can be associated with one or more carriers. UE 102 and base station 104 / RU 106 can utilize Y MHz (e.g., 5 MHz, 10 MHz, 15 MHz, 20 MHz, 100 MHz, 400 MHz, etc.) spectrum bandwidth allocated per carrier in up to a total of Yx MHz carrier aggregation, where x component carriers (CCs) are used for communication in each direction of the uplink direction and the downlink direction. The carriers may be adjacent to each other along the spectrum, or may not be adjacent to each other. In an example, uplink carriers and downlink carriers may be allocated in an asymmetric manner, and more or fewer carriers may be allocated for uplink or downlink. A component carrier may include a primary component carrier and one or more secondary component carriers. The primary component carrier may be associated with a primary cell (PCell), and the secondary component carrier may be associated with a secondary cell (SCell).

[0048] Some UEs 102 (such as UEs 102a and 102s) can perform device-to-device (D2D) communication via a side link. For example, a side link communication / D2D link utilizes a spectrum of a wireless wide area network (WWAN) associated with uplink communication and downlink communication. The side link communication / D2D link can also use one or more side link channels, such as a physical side link broadcast channel (PSBCH), a physical side link discovery channel (PSDCH), a physical side link shared channel (PSSCH), and / or a physical side link control channel (PSCCH) to transmit information between UEs 102a and 102s. Such side link / D2D communication can be performed via various wireless communication systems, such as wireless fidelity (Wi-Fi) systems, Bluetooth systems, long term evolution (LTE) systems, new radio (NR) systems, etc.

[0049] The electromagnetic spectrum is typically subdivided into different categories, bands, channels, etc. based on different frequencies / wavelengths associated with the electromagnetic spectrum. Fifth generation (5G) NR is typically associated with two operating bands referred to as frequency range 1 (FR1) and frequency range 2 (FR2). FR1 ranges from 410 MHz - 7.125 GHz, and FR2 ranges from 24.25 GHz - 52.6 GHz. Although a portion of FR1 is actually greater than 6 GHz, FR1 is often referred to as the "sub-6 GHz" band. In contrast, FR2 is often referred to as the "millimeter wave" (mmW) band. FR2 is different from the "extremely high frequency" (EHF) band, but is an approximate subset of that band, the EHF band ranges from 30 GHz - 300 GHz, and is sometimes also referred to as the "millimeter wave" band. The frequencies between FR1 and FR2 are often referred to as "mid-band" frequencies. The operating frequency band of mid-band frequencies may be referred to as frequency range 3 (FR3), which ranges from 7.125 GHz to 24.25 GHz. The frequency band within FR3 may include the characteristics of FR1 and / or FR2. Therefore, the characteristics of FR1 and / or FR2 may be extended to mid-band frequencies. Higher operating frequency bands have been identified as extending 5G NR communications to above 52.6 GHz associated with the upper limit of FR2. Three of these higher operating frequency bands include FR2-2 (ranging from 52.6 GHz to 71 GHz), FR4 (ranging from 71 GHz to 114.25 GHz), and FR5 (ranging from 114.25 GHz to 300 GHz). The upper limit of FR5 corresponds to the upper limit of the EHF frequency band. Therefore, unless otherwise expressly stated herein, the term "below 6 GHz" may refer to frequencies less than 6 GHz, frequencies within FR1, or frequencies that may include mid-band frequencies. Further, unless otherwise expressly stated herein, the term "millimeter wave" or mmW refers to frequencies that may include mid-band frequencies, frequencies that may be within FR2, FR4, FR2-2 and / or FR5, or frequencies that may be within the EHF band.

[0050] UE 102 and base station 104 / RU 106 may each include multiple antennas. Multiple antennas may correspond to antenna elements, antenna panels, and / or antenna arrays that may facilitate beamforming operations. For example, RU 106b transmits a downlink beamformed signal to UE 102b based on a first beam set 132 in one or more transmit directions of RU 106b. UE 102b may receive a downlink beamformed signal from RU 106b based on a second beam set 134 in one or more receive directions of UE 102b. In a further example, UE 102b may also transmit an uplink beamformed signal to RU 106b based on a second beam set 134 in one or more transmit directions of UE 102b. RU 106b may receive an uplink beamformed signal from UE 102b in one or more receive directions of RU 106b. UE 102b may perform beam training to determine the optimal receive and transmit directions for the beamformed signal. The transmit and receive directions of the UE 102 and the base station 104 / RU 106 may be the same, or may be different. In a further example, a beamformed signal may be transmitted between the first base station 104a and the second base station 104b. For example, the RU 106a of the cell 190a may send a beamformed signal to the base station 104a of the cell 190e based on the RU beam set 136 in one or more transmit directions of the RU 106a. The base station 104a of the cell 190e may receive a beamformed signal from the RU 106a based on the base station beam set 138 in one or more receive directions of the base station 104a. Similarly, the base station 104a of the cell 190e may send a beamformed signal to the RU 106a based on the base station beam set 138 in one or more transmit directions of the base station 104a. The RU 106a may receive a beamformed signal from the base station 104a of the cell 190e based on the RU beam set 136 in one or more receive directions of the RU 106a.

[0051] The base station 104 may include and / or be referred to as a next generation evolved Node B (ng-eNB), a generation NB (gNB), an evolved NB (eNB), an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a transmit receive point (TRP), a network node, a network entity, a network device, or other related terms. The base station 104 or an entity at the base station 104 may be implemented as an IAB node, a relay node, a side link node, a converged (monolithic) base station having a RU 106 and a BBU including a DU 108 and a CU 110, or as a decomposed base station 104b including one or more of the RU 106, the DU 108, and / or the CU 110. The set of converged or decomposed base stations 104a-104b may be referred to as a next generation radio access network (NG-RAN).

[0052] The core network 120 may include an access and mobility management function (AMF) 121, a session management function (SMF) 122, a user plane function (UPF) 123, a unified data management (UDM) 124, a gateway mobile location center (GMLC) 125, and / or a location management function (LMF) 126. The core network 120 may also include one or more location servers, which may include the GMLC 125 and the LMF 126, as well as other functional entities. For example, the one or more location servers include one or more location / positioning servers, which may include the GMLC 125 and the LMF 126 in addition to one or more of the positioning determination entity (PDE), the serving mobile location center (SMLC), the mobile positioning center (MPC), etc.

[0053] AMF 121 is a control node that handles signaling between UE 102 and core network 120. AMF 121 supports registration management, connection management, mobility management, and other functions. SMF 122 supports session management and other functions. UPF 123 supports packet routing, packet forwarding, and other functions. UDM 124 supports the generation of authentication and key agreement (AKA) credentials, user identity handling, access authorization, and subscription management. GMLC 125 provides an interface for clients / applications (e.g., emergency services) to access UE positioning information. LMF 126 receives measurement and assistance information from NG-RAN and UE 102 via AMF 121 to calculate the positioning of UE 102. NG-RAN can use one or more positioning methods to determine the location of UE 102. Positioning UE 102 can involve signal measurement, position estimation, and optional speed calculation based on measurement. Signal measurement can be performed by UE 102 and / or serving base station 104 / RU 106.

[0054] The transmitted signal may also be based on one or more of a satellite positioning system (SPS) 114, such as a signal measured for positioning. In an example, the SPS 114 of the cell 190c may communicate with one or more UEs 102, such as UE 102c, and one or more base stations 104 / RU 106, such as RU 106c. The SPS 114 may correspond to one or more of a global navigation satellite system (GNSS), a global positioning system (GPS), a non-terrestrial network (NTN), or other satellite positioning / positioning systems. The SPS 114 may be associated with LTE signals, NR signals (e.g., based on round trip time (RTT) and / or multiple RTT), wireless local area network (WLAN) signals, terrestrial beacon systems (TBS), sensor-based information, NR enhanced cell ID (NR E-CID) technology, downlink departure angle (DL-AoD), downlink arrival time difference (DL-TDOA), uplink arrival time difference (UL-TDOA), uplink arrival angle (UL-AoA), and / or other systems, signals, or sensors.

[0055] UE 102 may be configured as a cellular phone, a smart phone, a Session Initiation Protocol (SIP) phone, a laptop computer, a personal digital assistant (PDA), a satellite radio, a GPS, a multimedia device, a video device, a digital audio player (e.g., a Moving Picture Experts Group (MPEG) Audio Layer 3 (MP3) player), a camera, a game console, a tablet computer, a smart device, a wearable device, a vehicle, a utility meter, a gas pump, a home appliance, a healthcare device, a sensor / actuator, a display, or any other device with similar functionality. Some of UE 102 may be referred to as Internet of Things (IoT) devices, such as parking meters, gas pumps, home appliances, vehicles, healthcare equipment, etc. UE 102 may also be referred to as a station (STA), a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handheld device, a mobile client, a client, or other similar terms. The term UE may also apply to a roadside unit (RSU), which may communicate with other RSU UEs, non-RSU UEs, the base station 104, and / or entities at the base station 104, such as the RU 106.

[0056] Still reference Figure 1In certain aspects, the UE 102 may include a UE orphan resource element (RE) handling component 140 configured to receive control signaling from a network entity that causes the UE to enable at least one of: a number of enhanced Type 1 (eType 1) or eType 2 demodulation reference signal (DMRS) antenna ports, a minimum frequency domain orthogonal cover code (FD-OCC) despreading length, or at least one orphan RE handling scheme; receive downlink control information (DCI) from the network entity that schedules a physical shared channel for at least one of: at least one indicated eType 1 / eType 2 DMRS antenna port, an indicated FD-OCC despreading length, or an indicated orphan RE handling scheme; and communicate with the network entity on the physical shared channel based on at least one of: the at least one indicated eType 1 / eType 2 DMRS antenna port, the indicated FD-OCC despreading length, or the indicated orphan RE handling scheme.

[0057] In certain aspects, the base station 104 or a network entity of the base station 104 may include a BS isolated RE handling component 150, which is configured to send control signaling to the UE, which causes the UE to enable at least one of the following: the number of eType1 or eType2 DMRS antenna ports, the minimum FD-OCC despreading length, or at least one isolated RE handling scheme; send DCI to the UE, which schedules a physical shared channel for at least one of the following: eType1 DMRS, at least one indicated eType1 / eType2 DMRS antenna port, an indicated FD-OCC despreading length, or an indicated isolated RE handling scheme; and communicate with the UE on the physical shared channel based on at least one of the following: at least one indicated eType1 / eType2 DMRS antenna port, an indicated FD-OCC despreading length, or an indicated isolated RE handling scheme.

[0058] therefore, Figure 1 A wireless communication system is described that can incorporate aspects of one or more of the other figures described herein—such as Figures 2A to 14 Further, although the following description may focus on 5G NR, the concepts described herein may be applicable to other similar fields, such as 5G-Advanced and future versions, LTE, LTE-advanced (LTE-A), and other wireless technologies.

[0059] Figure 2A2 is a diagram showing an example of DMRS symbol locations for Type 1 DMRS. A resource block (RB) 210 consists of 12 subcarriers 204, and the example shows an RB with 14 symbols 202. Type 1 DMRS supports up to 8 antenna ports with up to 2 front-loaded DMRS symbols 206, 208 (e.g., Time Domain Orthogonal Cover Code (TD-OCC) 2) and 2 Code Division Multiplexing (CDM) groups (e.g., CDM Group 0 and CDM Group 1). Front-loaded DMRS means that the signal appears early in the transmission. In Figure 2A In the embodiment, every two consecutive subcarriers in a CDM group (eg, CDM group 0) apply an FD-OCC of length 2. Two DMRS symbols in a CDM group (eg, CDM group 0) apply a time domain orthogonal cover code (TD-OCC) of length 2.

[0060] Figure 2B 2 is a diagram showing an example of DMRS symbol positions for Type 2 DMRS. Type 2 DMRS supports up to 12 antenna ports, with up to 2 front-end DMRS symbols 206, 208 (e.g., TD-OCC 2) and 3 code division multiplexing (CDM) groups (e.g., CDM group 0, CDM group 1, and CDM group 2). Figure 2B As shown, every two consecutive subcarriers in the CDM group apply an FD-OCC of length 2. Two DMRS symbols apply a time domain orthogonal cover code (TD-OCC) of length 2.

[0061] Different DMRS ports may occupy different CDM groups, different FD-OCCs, or different TD-OCCs. The resource elements for DMRS port p in subcarrier k and symbol l are generated as follows: For DMRS type 1, , and for DMRS type 2, ; is the first symbol index allocated to DMRS; is the subcarrier offset of the current CDM group of port p. For DMRS type 1, for CDM groups 1 and 2 respectively, , and for DMRS Type 1, for CDM groups 1 and 2 respectively, ; is the basic sequence of DMRS, which is generated based on the QPSK sequence as defined in 3GPP TS 38.211 Sections 6.4.1.1.1 and 7.4.1.1.1; is FD-OCC and it can be [1, 1] or [1, -1], depending on the DMRS port index; is TD-OCC and it can be [1, 1] or [1, -1], depending on the DMRS port index; for DMRS based on two front-end symbols, , and for DMRS based on a single front-end symbol, , that is, TD-OCC is disabled.

[0062] For UEs with fewer layers and lower MU-MIMO operation or SU-MIMO operation order, some CDM groups may be used for data transmission. The network entity may use scheduling DCI to indicate the number of CDM groups without data. If the number of CDM groups without data is less than the maximum number of CDM groups of the DMRS type, the resource elements reserved for the remaining CDM groups may be used for data transmission.

[0063] In Release 18, to support higher order MU-MIMO, more DMRS ports with higher order FD-OCC are introduced, e.g., FD-OCC 4. Figure 2C An example of enhanced DMRS type 1 (eType1) based on FD-OCC-4 is shown, and Figure 2D An example of an enhanced DMRS type 2 (eType2) based on FD-OCC-4 is shown. Such an enhanced DMRS structure can create more orthogonal DMRS ports to increase the MU-MIMO order of both PDSCH and PUSCH. In one example, 4 FD-OCC sequences {[1, 1, 1, 1], [1, -1, 1, -1], [-1, -1, 1, 1], [1, -1, -1, 1} can be defined to create 4 orthogonal ports.

[0064] Figure 2C 250 is a diagram showing an example of DMRS symbol positions for an eType 1 DMRS. The eType 1 DMRS supports up to 16 antenna ports with up to 2 front-load DMRS symbols 206, 208 (e.g., TD-OCC 2) and 2 code division multiplexing (CDM) groups (e.g., CDM group 0 and CDM group 1). Figure 2CIn the CDM group (e.g., CDM group 0), every four consecutive subcarriers in the CDM group apply a FD-OCC of length 4. Two DMRS symbols in the CDM group (e.g., CDM group 0) apply a time domain orthogonal cover code (TD-OCC) of length 2. For eType1 DMRS, when every four consecutive subcarriers in the CDM group apply a FD-OCC of length 4, two REs cannot find the other two resource elements. These two REs are called isolated REs 252. Figure 2C In FIG. 2 , the UE is scheduled with 1 RB 210 and the UE cannot identify another 2 REs for the last 2 REs in the CDM group to have a complete FD-OCC sequence for FD-OCC-4 decoding.

[0065] Figure 2D 270 is a diagram showing an example of DMRS symbol positions for an eType 2 DMRS. The eType 2 DMRS supports up to 24 antenna ports with up to 2 front-load DMRS symbols 206, 208 (e.g., TD-OCC 2) and 3 code division multiplexing (CDM) groups (e.g., CDM group 0, CDM group 1, and CDM group 2). Figure 2D In the example, a FD-OCC of length 4 is applied to every four consecutive subcarriers within a CDM group (eg, CDM group 0).

[0066] FIG. 2A to FIG. 2D An example of DMRS symbol position of Type1 DMRS / Type2 DMRS / eType1 DMRS / eType2 DMRS is shown. Figure 2C As described above, some eType1 DMRS configurations result in orphan REs 252, which may contain DMRS signals that do not support antenna ports. In addition, if the DMRS receiver does not know the FD-OCC value, the receiver can apply the minimum despreading value that defaults to FD-OCC-4, but this will be inefficient when the FD-OCC value is greater than the minimum value. Therefore, Figure 3 A signaling diagram of an example scenario is shown in which a user equipment (UE) and a network entity exchange messages and implement a process of downlink eType1 and eType2 DMRS configuration and resource mapping to solve these technical issues.

[0067] Figure 3300 is a signaling diagram of an example scenario of a process in which a UE and a network entity exchange messages and implement downlink eType1 and eType2 DMRS configuration and resource mapping according to some embodiments. Initially, the UE 102 may send 302 a UE capability report regarding downlink eType1 / eType2 DMRS to the serving network entity 104. The UE capability report may include one or more UE capabilities indicating that the UE 102 supports at least one of: a total number of eType1 / eType2 DMRS antenna ports, a set of FD-OCC despreading lengths, eType1 DMRS and / or eType2 DMRS, or at least a first isolated RE handling scheme. The total number of antenna ports reported by the UE may indicate at least one of: a maximum number of antenna ports; or a candidate number of antenna ports. For example, the UE may indicate to the network entity that the candidate number of antenna ports is {1,2,4}. The UE may indicate to the network entity that the maximum number of antenna ports is a single value, such as 4.

[0068] As an alternative to over-the-air UE capability reporting, the network entity 104 may receive one or more UE capabilities from a core network entity such as an AMF. Based on the one or more UE capabilities, the network entity 104 enables downlink / uplink eType1 / eType2 DMRS, the number of indicated ports, and an orphan RE handling scheme. In one example, the network entity 104 may enable downlink / uplink eType1 / eType2 DMRS via RRC high-layer parameters such as DMRS-DownlinkConfig for downlink and DMRS-UplinkConfig for uplink.

[0069] The UE 102 receives 304 control signaling from the network entity 104 that causes the UE 102 to enable at least one of: the number of eType 1 or eType 2 DMRS antenna ports, the minimum FD-OCC despreading length, or at least one orphan RE handling scheme.

[0070] Thereafter, the UE 102 receives 306 a DCI from the network entity 104, the DCI scheduling a physical shared channel for at least one of: at least one indicated eType1 / eType2 DMRS antenna port, an indicated FD-OCC despreading length, or an indicated orphan RE treatment scheme, an eType1 DMRS and an eType2 DMRS associated with the DMRS antenna port. For example, the network entity schedules the PDSCH via the DCI. The network entity may use the PDSCH to communicate user data with the UE. For example, the user data includes voice data, video data, etc. The DCI includes an indication of the scheduled eType1 / eType2 DMRS port, and co-scheduled UE information.

[0071] The UE 102 then receives 308 the scheduled PDSCH based on the control signaling and the DCI. The UE 102 determines 310 at least one indicated eType1 / eType2 DMRS antenna port, an indicated FD-OCC despreading length, or an indicated orphan RE treatment scheme. The UE 102 decodes 312 the PDSCH according to the control signaling and the DCI. The UE 102 may send 314 an acknowledgement / negative acknowledgement (ACK / NACK) feedback to the network entity 104 in response to decoding 312 the PDSCH.

[0072] Figure 3 A signaling diagram is described for an example scenario in which a user equipment (UE) and a network entity exchange messages and implement a process for downlink eType1 and eType2 DMRS configuration and resource mapping, and Figure 4 A method is described from the UE side of a wireless communication link. Example method 400 focuses on a UE method for downlink eType1 / eType2 DMRS configuration and resource mapping. Method 400 may be implemented by Figure 1 The network entity 104 depicted in FIG. 1 is implemented by communicating with the UE 102. Figures 1 to 3 and Fig.13 The method may be performed by UE 102, UE equipment 1300, etc., which may include a memory 1324' and may correspond to the entire UE 102 or UE equipment 1300, or components of the UE 102 or UE equipment 1300 such as a wireless baseband processor 1324 and / or an application processor 1306.

[0073] Method 400 begins at block 402, where UE 102 may send a UE capability report message on a downlink eType1 / eType2 DMRS. The UE capability report message may represent Figure 3 Transmission 302 is shown.

[0074] Next, at block 404, UE 102 receives RRC signaling to enable eType1 / eType2 DMRS, a maximum number of indicated eType1 / eType2 DMRS ports, a minimum FD-OCC despreading length corresponding to at least one indicated set of eType1 / eType2 DMRS ports, and / or at least one orphan RE handling scheme. Figure 3 , the UE 102 receives 304 control signaling from the network entity 104, the control signaling causing the UE 102 to enable at least one of: the number of eType1 or eType2 DMRS antenna ports, the minimum FD-OCC despreading length, or at least one orphan RE handling scheme.

[0075] At block 406, UE 102 receives DCI to schedule PDSCH with eType1 / eType2 DMRS with indicated DMRS ports and indicated minimum FD-OCC despreading length and PDSCH scheduling information. Figure 3 , UE 102 receives 306 DCI to schedule PDSCH. At block 408, UE 102 receives the scheduled PDSCH with eType1 / eType2 DMRS using the DMRS port, FD-OCC despreading length, and PDSCH resource indicated in the DCI. For example, referring to Figure 3 , the UE 102 receives 308 a PDSCH signal with eType1 / eType2 DMRS using the DMRS port and FD-OCC despreading length.

[0076] At block 410, UE 102 determines the indicated DMRS port, FD-OCC despreading length, and isolated RE decoding scheme as needed. Figure 3 , the UE 102 determines 310 the indicated DMRS port, FD-OCC despreading length, and / or potential orphan RE handling scheme.

[0077] At block 412, UE 102 may decode the PDSCH based on the determined DMRS port, FD-OCC despreading length, and isolated RE decoding scheme. Figure 3 , UE 102 decodes 312 the PDSCH.

[0078] At block 414, UE 102 may send ACK / NACK feedback for the PDSCH. Figure 3 , the UE 102 sends 314 ACK / NACK feedback for the PDSCH to the network entity. Figure 4 A method is described from the UE side of a wireless communication link, and Figure 5A method is described from the network side of a wireless communication link.

[0079] Now go to Figure 5 , which shows an example method 500 for downlink eType1 / eType2 DMRS configuration and resource mapping implemented in a network entity. The method 500 may be Figure 1 The network entity 104 shown in FIG. Figures 1 to 3 and Fig.14 , the method 500 may be performed by a base station or one or more network entities 104 at a base station, which may correspond to the RU 106, the DU 108, the CU 110, the RU processor 1442, the DU processor 1432, the CU processor 1412, etc. The base station or one or more network entities 104 at a base station may include a memory 1412' / 1432' / 1442', which may correspond to the entirety of one or more network entities 104 or a base station, or a component of one or more network entities 104 or a base station.

[0080] Method 500 begins at block 502, where a base station or one or more network entities 104 at the base station may receive a UE capability report message regarding downlink eType1 / eType2 DMRS. Figure 3 , the base station or one or more network entities 104 at the base station receives 302 a UE capability report message regarding downlink eType1 / eType2 DMRS.

[0081] At block 504, the BS orphan RE handling component 150 of the base station or one or more network entities 104 such as RU 106, DU 108, and / or CU 110 at the base station sends control signaling to enable downlink eType1 / eType2 DMRS, the maximum number or candidate number of indicated ports, the minimum FD-OCC despreading length, and / or one or more orphan RE handling schemes. For example, referring to Figure 3 , the base station or one or more network entities 104 at the base station sends 304 RRC control signaling to enable downlink eType1 / eType2 DMRS, the candidate number of the indicated port, the FD-OCC-2 minimum despreading length, and two isolated RE handling schemes. The network entity 104 may send RRC signaling indicating the RRC reconfiguration message, or the network entity 104 may send a system information block (SIB), where the SIB may be a predefined SIB (e.g., SIB1) or a different SIB (e.g., SIB J, where J corresponds to an integer greater than 21).

[0082] At block 506, the network entity 104 sends a DCI to schedule a PDSCH with an eType1 / eType2 DMRS indicating the DMRS port and FD-OCC despreading length and the scheduled PDSCH resources. Figure 3 , the base station or one or more network entities 104 at the base station sends 306 DCI to schedule the PDSCH.

[0083] At block 508, the network entity 104 transmits a scheduled PDSCH with eType1 / eType2 DMRS using the DMRS port, FD-OCC despreading length, and PDSCH resource indicated in the DCI. Figure 3 , the base station or one or more network entities 104 at the base station sends 308 a PDSCH signal with eType1 / eType2 DMRS using a DMRS port and a FD-CCO despreading length.

[0084] In response, at block 514, the network entity 104 may receive ACK / NACK feedback for the PDSCH message. Figure 3 , the base station or one or more network entities 104 at the base station receives 314 ACK / NACK feedback for the PDSCH message. Figures 3 to 5 A method for downlink communication of a wireless communication link is described, and Figure 6 is a signaling diagram of an example scenario of a process in which a user equipment (UE) and a network entity exchange messages and implement uplink eType1 and eType2 DMRS configuration and resource mapping.

[0085] Figure 6 is a signaling diagram 600 illustrating communication between UE 102 and network entity 104 for uplink eType1 and eType2 DMRS configuration and resource mapping. Network entity 104 may correspond to a base station or an entity at a base station such as RU 106, DU 108, CU 110, and the like.

[0086] Unlike the above-mentioned downlink eType1 / eType2 DMRS configuration, the control signaling for the uplink eType1 / eType2 DMRS does not include the FD-OCC despreading length. The network entity has information about the scheduling status of the co-scheduled UE, and thus the network entity determines the FD-OCC despreading length. Therefore, in the isolated RE handling scheme (refer to FIG. 12A to FIG. 12BIn the DCI, the network entity only needs to indicate to the UE how to send the DMRS in the isolated RE and how to send the corresponding PUSCH. For example, the network entity can indicate to the UE whether to send the DMRS in the isolated RE, user data, or nothing. In some implementations, the DCI can indicate whether to send the DMRS in the isolated RE.

[0087] In some aspects, the network entity may use DCI to indicate whether the DMRS in the isolated RE should be sent when the network entity schedules a PUSCH message. In one example, the network entity may use a 1-bit DCI field to indicate whether the DMRS in the isolated RE should be sent. In another example, the network entity may jointly indicate via the DCI field antenna port whether the DMRS in the isolated RE and the DMRS port indication should be sent. In some aspects, the network entity may further indicate whether the isolated RE can be used for PUSCH data transmission. In some other aspects, the network entity may further indicate whether the RE with the same subcarrier index as the isolated RE can be used for PUSCH transmission. In some further aspects, the network entity may predefine whether the isolated RE can be used for PUSCH data transmission. In some other aspects, the network entity may predefine whether the RE with the same subcarrier index as the isolated RE can be used for PUSCH transmission.

[0088] refer to Figure 6 At the beginning of the example scenario 600, the UE 102 may send 602 a UE capability report regarding uplink eType1 / eType2 DMRS, similar to 302 discussed above. Similar to 304, the UE 102 receives 604 control signaling from a network entity to enable uplink eType1 / eType2 DMRS and / or orphan RE handling scheme.

[0089] Next, the UE 102 receives 606 a DCI to schedule a PUSCH transmission using the indicated eType1 / eType2 uplink DMRS port and / or orphan RE treatment scheme. Also similar to 310, the UE 102 determines 610 the indicated DMRS port and orphan RE treatment scheme - but generates a PUSCH transmission instead of receiving a PDSCH message. The UE sends a PUSCH (e.g., PUSCH data) based on the DCI scheduling and the DMRS-related indicator. The network entity may decode 616 the PUSCH signaling based on the orphan RE treatment scheme selected for the eType1 / eType2 DMRS. Figure 6 describes the signaling diagram for uplink eType1 and eType2 DMRS configuration and resource mapping implementation, and Figure 7 A method is described from the UE side of a wireless communication link.

[0090] Now go to Figure 7 , which shows an example method 700 for uplink eType1 / eType2 DMRS configuration and resource mapping implemented in a UE. The method 700 may be implemented by Figure 1 The network entity 104 depicted in FIG. 1 is implemented by communicating with the UE 102. Figure 1 and Fig.13 The method may be performed by UE 102, UE equipment 1300, etc., which may include a memory 1324' and may correspond to the entire UE 102 or UE equipment 1300, or components of the UE 102 or UE equipment 1300 such as a wireless baseband processor 1324 and / or an application processor 1306.

[0091] Method 700 begins at block 702, where UE 102 may send a UE capability report message regarding uplink eType1 / eType2 DMRS. Figure 6 , the UE 102 sends 602 a UE capability report message regarding uplink eType1 / eType2 DMRS.

[0092] Next, at block 704, UE 102 receives RRC signaling to enable eType1 / eType2 DMRS, and / or an indicator of at least one orphan RE handling scheme. Figure 6 , the UE 102 receives 604 an RRC reconfiguration message including an indication of the eType1 / eType2 DMRS and an indication of the first orphan RE handling scheme and the second orphan RE handling scheme.

[0093] At block 706, the UE 102 receives a DCI to schedule a PUSCH transmission with an eType1 / eType2 DMRS with an indicated DMRS port and / or an orphan handling scheme. Figure 6 , the UE 102 receives 606 a DCI to schedule a PUSCH transmission with an eType1 / eType2 DMRS with an indicated DMRS port and a first orphan treatment scheme.

[0094] At block 710, UE 102 may determine the indicated DMRS port and isolated RE decoding scheme. Figure 6 , the UE 102 determines 610 the indicated DMRS port and generates a PUSCH transmission using a first isolated RE handling scheme.

[0095] At block 714, UE 102 transmits a PUSCH using the determined DMRS port and the first isolated RE decoding scheme. Figure 6 , the UE 102 sends 614 a PUSCH message based on the determined DMRS port and the first isolated RE handling scheme. Figure 7 A method is described from the UE side of a wireless communication link, and Figure 8 A method is described from the network side of a wireless communication link.

[0096] Now go to Figure 8 , which shows an example method 800 implemented in a network entity for uplink eType1 / eType2 DMRS configuration and resource mapping. Figure 1 and Fig.14 The method may be performed by a base station or one or more network entities 104 at a base station, which may correspond to RU 106, DU 108, CU 110, RU processor 1442, DU processor 1432, CU processor 1412, etc. The base station or one or more network entities 104 at a base station may include a memory 1412' / 1432' / 1442', which may correspond to the entirety of one or more network entities 104 or a base station.

[0097] refer to Figure 8 The method 800 begins at block 802, where a base station or one or more network entities 104 at the base station may receive a UE capability report message regarding uplink eType1 / eType2 DMRS from a UE 102. For example, the UE capability report message may be as follows: Figure 6 Representation 602 is shown.

[0098] Next, at block 804, the network entity 104 sends RRC signaling to enable eType1 / eType2 DMRS and / or at least one isolated RE handling scheme. Figure 6 , the network entity 104 sends 604 an RRC reconfiguration message, the RRC reconfiguration message including an indication of the eType1 / eType2 DMRS and / or an indication of the first orphan RE handling scheme.

[0099] At block 806, the network entity 104 sends a DCI to schedule a PUSCH transmission with an eType1 / eType2 DMRS with an indicated DMRS port and / or orphan handling scheme. Figure 6, the network entity 104 sends 606 a DCI to schedule a PUSCH transmission with an eType1 / eType2 DMRS with an indicated DMRS port and a first orphan treatment scheme.

[0100] At block 814, the network entity 104 receives a scheduled PUSCH message that implements the selected orphan RE treatment scheme. Figure 6 , the network entity 104 receives 614 a PUSCH based on the determined DMRS port and the first isolated RE handling scheme.

[0101] At block 816, the network entity 104 decodes the PUSCH message using the orphan RE treatment scheme selected for the eType1 / eType2 DMRS, if required.For example, the network entity 104 decodes 616 the PUSCH based on the orphan RE treatment scheme selected for the eType1 / eType2 DMRS.

[0102] Figure 3 describes the signaling diagram for downlink eType1 and eType2 DMRS configuration and resource mapping, Figure 6 describes the signaling diagram for uplink eType1 and eType2 DMRS configuration and resource mapping, and Fig. 9 Signaling diagrams for both uplink and downlink eType1 and eType2 DMRS configuration and resource mapping are described.

[0103] Fig. 9 A signaling diagram of an example scenario in which a UE and a network entity exchange messages and implement a process of uplink and downlink eType1 and eType2 DMRS configuration and resource mapping according to some embodiments is shown. The network entity 104 may correspond to a base station or an entity such as RU 106, DU 108, CU 110, etc. at a base station. At the beginning of the example scenario 900, the UE 102 may send 602 a UE capability report on uplink eType1 / eType2 DMRS to the serving network entity 104, similar to 302 and 602 discussed above. Similar to 304, the UE 102 receives 604 control signaling from the network entity to enable uplink eType1 / eType2 DMRS, the maximum number of downlink DMRS ports indicated, the minimum FD-OCC despreading length, and / or an orphan RE handling scheme. Next, the UE 102 receives 306 DCI to schedule PDSCH transmission. Also similar to 606, the UE receives 606 DCI to schedule PUSCH transmission. Then, the UE communicates 911 on the physical shared channel based on control signaling based on 308 , 310 , 312 , 314 and / or 610 , 614 , 616 .

[0104] Fig. 9 A signaling diagram is described for an example scenario in which a UE exchanges messages with a network entity and implements uplink and downlink eType1 and eType2 DMRS configuration and resource mapping procedures, and Fig.10 The method of downlink and uplink eType1 and eType2 DMRS configuration and resource mapping is described from the UE side of the wireless communication link.

[0105] Now go to Fig.10 , which shows an example method 1000 implemented in a UE for downlink and uplink eType1 / eType2 DMRS configuration and resource mapping. The method 1000 may be Figure 1 The UE 102 and the network entity 104 shown in FIG. Figure 1 and Fig.13 The method may be performed by UE 102, UE equipment 1300, etc., which may include a memory 1324' and may correspond to the entire UE 102 or UE equipment 1300, or components of the UE 102 or UE equipment 1300 such as a wireless baseband processor 1324 and / or an application processor 1306.

[0106] refer to Fig.10 , method 1000 begins at block 1002, where UE 102 may send a UE capability report message regarding uplink and downlink eType1 / eType2 DMRS (events 302, 602, 902). Fig. 9 , the UE 102 sends 902 a UE capability report regarding uplink and downlink eType1 / eType2 DMRS.

[0107] Next, at block 1004, UE 102 receives RRC signaling to enable uplink and / or downlink eType1 / eType2 DMRS, an indicator of a maximum number of downlink eType1 / eType2 DMRS ports, a minimum FD-OCC despreading length, and / or at least one orphan RE handling scheme (events 304 and 604). For example, referring to Fig. 9 , the UE 102 receives 904 control signaling to enable downlink and uplink eType1 / eType2 DMRS, indicate the maximum number of downlink and uplink DMRS ports, the minimum FD-OCC despreading length, and / or orphan RE handling scheme.

[0108] At block 1006, UE 102 receives DCI to schedule a PDSCH including an indicated eType1 / eType2 DMRS port and an indicated FD-OCC despreading length. Figure 3 , the UE 102 receives 306 the DCI to schedule the PDSCH scheduling information including the indicated eType1 / eType2 DMRS port and the FD-OCC despreading length.

[0109] At block 1011, UE 102 receives a DCI to schedule a PUSCH transmission using the indicated eType1 / eType2 uplink DMRS port and / or orphan RE handling scheme. Figure 6 , the UE 102 receives 606 a DCI to schedule PUSCH messaging including the indicated eType1 / eType2 uplink DMRS ports and the first orphan RE treatment scheme. Fig.10 A method is described from the UE side of a wireless communication link, and Fig.11 A method is described from the network side of a wireless communication link.

[0110] Now go to Fig.11 , which shows an example method 1100 implemented in a network entity for downlink and uplink eType1 / eType2 DMRS configuration and resource mapping. The method 1100 may be implemented by Figure 1 The embodiment is implemented by the UE 102 and the network entity 104 depicted in FIG. Fig.11 1100 is a flow chart of a method of wireless communication at a network entity. Figure 1 and Fig.14 , the method may be performed by a base station or one or more network entities 104 at a base station, which may correspond to RU 106, DU 108, CU 110, RU processor 1442, DU processor 1432, CU processor 1412, etc. The base station or one or more network entities 104 at a base station may include a memory 1412' / 1432' / 1442', which may correspond to the entirety of one or more network entities 104 or base stations, or components of one or more network entities 104 or base stations such as RU processor 1442, DU processor 1432, or CU processor 1412.

[0111] Method 1100 begins at block 1102, where a base station or one or more network entities 104 at a base station may receive a UE capability report message regarding uplink and downlink eType1 / eType2 DMRS (events 302, 602, and 902). Fig. 9, the network entity 104 receives 902 a UE capability report indicating that the UE supports at least one of: a total number of eType1 / eType2 DMRS antenna ports, a set of FD-OCC despreading lengths, or at least a first orphan RE handling scheme.

[0112] Next, at block 1104, the network entity 104 sends RRC signaling to enable uplink and / or downlink eType1 / eType2 DMRS, indicate the maximum number of downlink DMRS ports, the minimum FD-OCC despreading length, and / or one or more orphan RE handling schemes (events 304, 604, and 904). For example, referring to Fig. 9 , the network entity 104 sends 904 control signaling to enable downlink and uplink eType1 / eType2 DMRS, indicate the maximum number of downlink and uplink DMRS ports, the minimum FD-OCC despreading length, and / or one or more orphan RE handling schemes.

[0113] At block 1106, the network entity 104 sends a DCI to schedule a PDSCH including the indicated eType1 / eType2 DMRS ports and FD-OCC despreading length. Figure 3 , the network entity 104 sends 306 a DCI to schedule a PDSCH including the indicated eType1 / eType2 DMRS ports and FD-OCC despreading length.

[0114] At block 1111, the network entity 104 sends a DCI to schedule a PUSCH including an indicated eType1 / eType2 uplink DMRS port, and / or an orphan RE treatment scheme. Figure 6 , the network entity 104 sends 606 a DCI to schedule a PUSCH transmission including the indicated eType1 / eType2 uplink DMRS ports and the first orphan RE treatment scheme.

[0115] In some aspects, when the network entity sends control signaling, the network entity may send an indication that the minimum FD-OCC extension length value is greater than 2. When sending DCI, the network entity may send an indicated FD-OCC despreading length equal to 4.

[0116] These aspects include that the UE may support an orphan RE handling scheme for handling orphan REs. RRC signaling may include an indication of which scheme to use.

[0117] In scheme 1 (default), the network entity shall always schedule an even number of consecutive physical RBs (PRBs) for PDSCH or PUSCH. The network entity may further schedule an even number of starting PRBs or common resource block (CRB) indices for each consecutive PRB block and / or for each precoding resource block group (PRG). CRB is an index from the perspective of the network entity, and the network entity indicates the CRB index of the first PRB index via RRC signaling. The network entity shall use the same precoder to schedule the same co-scheduled UE within a PRG.

[0118] In scheme 2, the DMRS in the isolated RE is not transmitted and the isolated RE is not available for data transmission. Figure 2C , isolated RE 252 cannot be used for data transmission. However, RE 256 can be used for data transmission.

[0119] In scheme 3, DMRS in isolated REs is not transmitted, and isolated REs are used for data transmission. Figure 2C , the isolated RE 252 can be used for data transmission.

[0120] In scheme 4, the DMRS in the isolated RE is not transmitted, and the RE with the same subcarrier index as the isolated RE in the transmission opportunity is not used for data transmission. Figure 2C , the entire subcarrier 254 is unavailable for data transmission.

[0121] Fig.11 A method is described from the network side of a wireless communication link, and FIG. 12A to FIG. 12B A diagram showing an example of DMRS symbol locations for isolated REs.

[0122] Fig. 12A An orphan RE handling scheme is shown in which DMRS in orphan REs are transmitted. Diagram 1200 shows 3 FD-OCC despreading windows of length 2. In this configuration, DMRS in orphan REs are transmitted.

[0123] As shown in schemes 1200 and 1210, the FD-OCC despreading length may determine whether the DMRS in the isolated RE may be transmitted. For example, if the FD-OCC despreading length is less than 4, the DMRS in the isolated RE may be transmitted. If the FD-OCC despreading length is 4, schemes 1210 or 1220 may be applied. Fig. 12B An example of a scheme 1220 using overlapping despreading windows is shown.

[0124] Fig. 12BAn orphan RE handling scheme 1220 using overlapping despreading windows is shown. In scheme 1220, DMRS in orphan REs are always transmitted. When despreading based on a large FD-OCC length is required, the receiver can use adjacent DMRS REs in the same CDM group for FD-OCC despreading. For example, Fig. 12B As shown in , FD-OCC despreading window 1 may include REs 1, 2, 3, and 4 within CDM group 0. FD-OCC despreading window 2 may include REs 3, 4, 5, and 6 within CDM group 1. REs 3 and 4 are common REs for windows 1 and 2 within CDM group 1.

[0125] For the above schemes 2, 3 and 4, the following sub-schemes may be used to determine the PT-RS transmission behavior.

[0126] Scheme A: PT-RS is transmitted in REs having subcarrier indices different from those of isolated REs.

[0127] Scheme B: PT-RS is transmitted in REs with the same subcarrier index as the isolated REs. The receiver can perform frequency domain interpolation to identify the estimated channel in the isolated REs, and then perform phase offset calculation and compensation based on the PT-RS and the interpolated channel with the same subcarrier index.

[0128] Scheme C: PT-RS is transmitted at REs having the same subcarrier index as normal REs of the associated DMRS port in an RB.

[0129] Solution D: The network entity may configure resourceElementOffset in PTRS-UplinkConfig and PTRS-DownlinkConfig to ensure that the PT-RS is not mapped to an RE having the same subcarrier index as an isolated RE.

[0130] FIG. 12A to FIG. 12B A diagram showing an example of DMRS symbol positions for isolated REs is shown, and FIG. 12C to FIG. 12G An example table showing PT-RS RE offset configuration for eType1 / eType2 DMRS is shown.

[0131] Fig. 12C An example of a PT-RS RE offset configuration 1230 for a DM-RS antenna port 1231 within an RB is shown. Fig. 12CAs shown, the PT-RS RE offset configuration can be divided into DM-RS configuration eType1 1232 and PT-RS RE offset configuration eType2 1233. In the DM-RS configuration eType1 1232, the PT-RS RE offset of eType1 does not exceed 7. In the DM-RS configuration eType2 1233, the PT-RS RE offset of eType2 does not exceed 11. For the DM-RS configuration eType1 1232, there are two CDM groups. The first CDM group 1234 can occupy subcarriers 0, 2, 4, and 6. The second CDM group 1235 can occupy subcarriers 1, 3, 5, and 7. There are 8 possible DM-RS antenna ports 1231 (for example, 1000, 1001, 1002, ..., 1007). In the DM-RS configuration eType2 1233, there are three CDM groups. The first CDM group 1234 can occupy subcarriers 0, 1, 6, and 7. 1011). The network entity may send resourceElementOffset as RRC signaling to the UE to convey the PT-RS RE offset. For example, if the PT-RS RE offset is associated with DM-RS antenna port 1000, the network entity may indicate that offset00 is 0, offset01 is 2, offset10 is 4, and offset11 is 6. Table 1230 does not allow the indication of PT-RS in isolated REs. There is no 8 in resourceElementOffset. Isolated REs typically appear at the end of an RB (the 8th or 10th RE).

[0132] Fig.12D Another example of a PT-RS RE offset configuration 1240 for a DMRS antenna port 1241 within an RB is shown. Fig.12DAs shown, the PT-RS RE offset configuration can be divided into a DMRS configuration eType1 1242 and a PT-RS RE offset configuration eType2 1243. For the DM-RS configuration eType1 1242, there are two CDM groups. The first CDM group 1244 can occupy subcarriers 0, 2, 4, and 6. The second CDM group 1245 can occupy subcarriers 1, 3, 5, and 7. There are 8 possible DM-RS antenna ports 1241 in eType1 (for example, 1000, 1001, 1002, ..., 1007). In the DM-RS configuration eType2 1243, there are three CDM groups. The first CDM group 1244 can occupy subcarriers 0, 1, 6, and 7. The second CDM group 1235 can occupy subcarriers 2, 3, 8, and 9. The third CDM group 1246 occupies subcarriers 4, 5, 10, and 11. There are 12 possible DM-RS antenna ports 1241 (e.g., 1000, 1001, 1002, ..., 1011). This example depicts Scheme B. Offsets of 8 and 10 in resourceElementOffset result in PT-RS transmission at REs in the same subcarrier index as the orphan RE. Such indications may be used for cases where there are no orphan REs.

[0133] The number of candidate ports for indicating downlink eType1 / eType2 DMRS (see Figure 12G ) and the maximum number of ports indicated by downlink eType1 / eType2 DMRS (see Fig.12F ) can be used to reduce the overhead of DCI indicated by eType1 / eType2 DMRS ports. When the network entity configures the candidate number of indicated ports or the maximum number of indicated ports, the size of the DCI field can be determined based on the sum of the number of code points for the candidate number of indicated ports. The orphan RE handling scheme for uplink and downlink eType1 / eType2 DMRS should be determined from the above Figure 2C , Fig. 12A and Fig. 12B Select at least one solution from a subset or all of solutions 2 to 6 described in.

[0134] In some aspects, the RRC signaling may further include a scrambling ID for generating an eType1 / eType2 DMRS sequence. Alternatively, more than one scrambling ID for eType1 / eType2 DMRS sequence generation may be further included in the RRC signaling, wherein the scrambling ID is used for sequence generation of a CDM group of eType1 / eType2 DMRS. For example, a first scrambling ID is used in conjunction with a first CDM group, and a second scrambling ID is used for a second CDM group. The scrambling ID technique may result in a reduction in peak-to-average power ratio (PAPR).

[0135] In one aspect, a network entity may indicate a minimum FD-OCC despreading length for a downlink eType1 / eType2 DMRS via DCI (e.g., DCI format 1_1 / 1_2) for flexible scheduling. For example, for an eType1 / eType2 DMRS based on FD-OCC-4, the candidate minimum FD-OCC despreading length may be {1, 2, 4} or {1, 4}. In another example, for an eType1 / eType2 DMRS based on FD-OCC-6, the candidate minimum FD-OCC despreading length may be {1, 3, 6} or {1, 6}. The network entity may indicate a minimum FD-OCC despreading length per CDM group or across CDM groups.

[0136] The UE may determine the FD-OCC despreading length of the CDM group based on the indicated minimum FD-OCC despreading length of the CDM group and the indicated number of DMRS ports. The FD-OCC despreading length of the CDM group is the maximum of: (a) the indicated minimum FD-OCC despreading length and (b) the minimum FD-OCC despreading length used to decode the indicated number of DMRS ports of the CDM group. In one example, if the minimum FD-OCC despreading length is 1 and the number of indicated DMRS ports in the CDM group is 2, which requires the UE to perform a FD-OCC despreading length of 2 to distinguish between the 2 DMRS ports, the FD-OCC despreading length should be 2. In another example, if the minimum FD-OCC despreading length is 1 and the number of indicated DMRS ports in the CDM group is 3, which requires the UE to perform a FD-OCC despreading length of 4 to distinguish between the 3 DMRS ports, the FD-OCC despreading length should be 4.

[0137] In some aspects, a network entity may use a separate DCI field to indicate the minimum FD-OCC despreading length. In one example, the DCI field may occupy 1 bit, which indicates whether the minimum FD-OCC despreading length is 1 or the FD-OCC length of the scheduled eType1 / eType2 DMRS. In another example, the DCI field may occupy more than 1 bit, which indicates the minimum FD-OCC despreading length. In another example, the network entity may use a first 1-bit DCI field to indicate whether the minimum FD-OCC despreading length is 1 or the FD-OCC length of the scheduled DMRS, and use a second 1-bit DCI field to indicate whether Type1 / Type2 DMRS or eType1 / eType2 DMRS is used.

[0138] In some aspects, the network entity may jointly indicate the minimum FD-OCC despreading length and the DMRS port (e.g., antenna port) through a single DCI field. In one example, for some candidate values ​​of the antenna port, the network entity may indicate whether the minimum FD-OCC despreading length is 1 or the FD-OCC length. In one example, for some candidate values ​​of the antenna port, the network entity may indicate the minimum FD-OCC despreading length. For other candidate values ​​of some antenna ports that do not have a related indication of the minimum FD-OCC despreading length, the FD-OCC despreading length should be the same as the FD-OCC length. The benefit of jointly indicating the minimum FD-OCC despreading length and the DMRS port through a single DCI field can maintain DCI overhead.

[0139] Fig.12E An example of a joint indication of a DMRS port and a minimum FD-OCC despreading length is shown. The example is for an eType1 DMRS with one front-load symbol. Ports {0, 1, 2, 3} are from a first CDM group, and ports {4,5, 6, 7} are from a second CDM group. Table 1250 is a modification of Table 7.3.1.2.2-2 in 3GPP 38.212. For example, Table 1250 includes a new column "Minimum FD-OCC Despreading Length" 1251. In Table 1250, two DMRS ports 0, 1 (values ​​7 and 8) may have different minimum FD-OCC despreading lengths.

[0140] In some aspects, the UE may determine the minimum FD-OCC despreading length based on the indicated DMRS ports. In one example, if the number of indicated DMRS ports is greater than X, the minimum FD-OCC despreading length is 1, where X may be predefined, for example, X=3 or 4. The network entity may configure X via high-level signaling (e.g., RRC or MAC control element (CE)). Alternatively, the network entity may dynamically configure X via DCI. If the number of indicated DMRS ports is less than or equal to X, the minimum FD-OCC despreading length is the same as the FD-OCC length. In another example, the network entity may indicate the minimum FD-OCC despreading length for each number of indicated DMRS ports via RRC signaling. For example, the network entity may indicate that the minimum FD-OCC despreading length of port 1 is 2, and the minimum FD-OCC despreading length of port 2 is 4. After the UE receives the scheduling DCI with the indicated DMRS port, the UE shall apply the corresponding minimum FD-OCC despreading length to identify the FD-OCC despreading length for decoding the DMRS. In another example, the network entity may indicate via RRC signaling whether the minimum FD-OCC despreading length for each number of indicated DMRS ports should be 1 or greater than 1 (i.e., whether there are any co-scheduled UEs). For example, the network entity may use a one-bit indication to indicate whether FD-OCC 4 or FD-OCC 1 is determined.

[0141] In one aspect, the network entity may indicate the downlink / uplink eType1 / eType2 DMRS ports through DCI (e.g., DCI format 1_1 / 1_2) based on the maximum number of downlink / uplink DMRS ports indicated. The network entity may configure the maximum number of downlink / uplink DMRS ports indicated through RRC signaling or MAC CE. The network entity may configure the maximum number of candidates for the indicated downlink / uplink DMRS ports through RRC signaling or MAC CE. The payload size of the DCI field antenna port of the eType1 / eType2 DMRS may be determined based on the maximum number of indicated DMRS ports or the candidate number of indicated DMRS ports configured by the network entity. If dynamic switching between eType1 / eType2 DMRS and Type1 / Type2 DMRS is enabled, for example, the network entity configures RRC parameters to enable dynamic switching or uses a separate DCI field to indicate whether the DMRS is based on Type1 / Type2 DMRS or eType1 / eType2 DMRS, the payload size of the DCI field antenna port can be based on the maximum number of code points of eType1 / eType2 DMRS and Type1 / Type2 DMRS.

[0142] Fig.12F An example of an eType 1 DMRS port indication with a single front-end symbol is shown and the maximum number of indicated ports is 1. Table 1260 is a modification of 3GPP 38.212 Table 7.3.1.2.2-1. Table 1260 may indicate to the UE that the maximum number of indicated ports is 1. The DMRS port may include an entry with 1 port indication. This means that 4 bits are required to indicate the DMRS port. This may result in a saving in the overhead of the DMRS port indication.

[0143] Figure 12G An example of eType1 DMRS port indication with a single front-loading symbol is shown and the candidate number of the indicated port is {1, 2, 4}. Table 1270 is a modification of 3GPP 38.212 Table 7.3.1.2.2-1.

[0144] like Fig.13 The UE equipment 1300 described in the flowcharts 400, 700, and 1000 may execute the methods of the flowcharts 400, 700, and 1000. The base station or one or more network entities 104 at the base station (such as Fig.14 The methods of flowcharts 500, 800, and 1100 may be executed as described herein.

[0145] Fig.13 1300 is a diagram illustrating an example of a hardware implementation of a UE equipment 1300. Equipment 1300 may be a UE 102, a component of a UE, or may implement UE functionality. In some aspects, equipment 1300 may include a wireless baseband processor 1324 (also referred to as a modem) coupled to one or more transceivers 1322 (e.g., a wireless RF transceiver). The wireless baseband processor 1324 may include on-chip memory 1324'. In some aspects, equipment 1300 may further include one or more subscriber identity module (SIM) cards 1320 and an application processor 1306 coupled to a secure digital (SD) card 1308 and a screen 1310. The application processor 1306 may include on-chip memory 1306'.

[0146] The equipment 1300 may further include a Bluetooth module 1312, a WLAN module 1314, an SPS module 1316 (e.g., a GNSS module), and a cellular module 1317 located within one or more transceivers 1322. The Bluetooth module 1312, the WLAN module 1314, the SPS module 1316, and the cellular module 1317 may include an on-chip transceiver (TRX) (or in some cases, only a receiver (RX)). The Bluetooth module 1312, the WLAN module 1314, the SPS module 1316, and the cellular module 1317 may include their own dedicated antennas and / or communicate using antennas 1380. The equipment 1300 may further include one or more sensor modules 1318 (e.g., an atmospheric pressure sensor / altimeter; motion sensors such as an inertial management unit (IMU), a gyroscope and / or an accelerometer; light detection and ranging (LIDAR), radio-aided detection and ranging (RADAR), sound navigation and ranging (SONAR), magnetometer, audio and / or other technologies for positioning), additional modules for memory 1326, a power supply 1330 and / or a camera 1332.

[0147] The wireless baseband processor 1324 communicates with another UE 102 and / or with a RU associated with the network entity 104 via one or more antennas 1380 through the transceiver 1322. The wireless baseband processor 1324 and the application processor 1306 can each include a computer-readable medium / memory 1324', 1306', respectively. The additional modules of the memory 1326 can also be regarded as computer-readable media / memory. Each computer-readable medium / memory 1324', 1306', 1326 can be non-temporary. The wireless baseband processor 1324 and the application processor 1306 are each responsible for general processing, including executing software stored on the computer-readable medium / memory. When the software is executed by the wireless baseband processor 1324 / application processor 1306, the wireless baseband processor 1324 / application processor 1306 performs the various functions described. The computer-readable medium / memory can also be used to store data manipulated by the wireless baseband processor 1324 / application processor 1306 when executing the software. The wireless baseband processor 1324 / application processor 1306 may be a component of the UE 102. The equipment 1300 may be a processor chip (modem and / or application) and include only the wireless baseband processor 1324 and / or the application processor 1306, and in another configuration, the equipment 1300 may be the entire UE 102 and include additional modules of the equipment 1300.

[0148] As discussed, the UE orphan RE handling component 140 is configured to: receive control signaling from a network entity that causes the UE to enable at least one of the following: the number of eType1 or eType2 DMRS antenna ports, the minimum FD-OCC despreading length, or at least one orphan RE handling scheme; receive DCI from the network entity that schedules a physical shared channel for at least one of the following: at least one indicated eType1 / eType2 DMRS antenna port, the indicated FD-OCC despreading length, or the indicated orphan RE handling scheme; and communicate with the network entity on the physical shared channel based on at least one of the following: at least one indicated eType1 / eType2 DMRS antenna port, the indicated FD-OCC despreading length, or the indicated orphan RE handling scheme. The UE orphan RE handling component 140 may be located within the radio baseband processor 1324, the application processor 1306, or both the radio baseband processor 1324 and the application processor 1306. The UE isolated RE handling component 140 can be one or more hardware components specifically configured to execute the process / algorithm, implemented by one or more processors configured to execute the process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof.

[0149] As shown, the apparatus 1300 may include various components configured for various functions. In one configuration, the apparatus 1300 and in particular the wireless baseband processor 1324 and / or the application processor 1306 include: a component for receiving control signaling from a network entity, the control signaling causing the UE to enable at least one of the following: the number of eType1 or eType2 DMRS antenna ports, the minimum FD-OCC despreading length, or at least one isolated RE handling scheme; a component for receiving DCI from the network entity, the DCI scheduling a physical shared channel for at least one of the following: at least one indicated eType1 / eType2 DMRS antenna port, the indicated FD-OCC despreading length, or the indicated isolated RE handling scheme; and a component for communicating with the network entity on the physical shared channel based on at least one of the following: at least one indicated eType1 / eType2 DMRS antenna port, the indicated FD-OCC despreading length, or the indicated isolated RE handling scheme. The apparatus 1300 further includes means for sending a UE capability report to a network entity, the UE capability report indicating that the UE supports at least one of: a total number of eType1 / eType2 DMRS antenna ports, a set of FD-OCC despreading lengths, or at least a first orphan RE handling scheme. The means may be the UE orphan RE handling component 140 of the apparatus 1300 configured to perform the functions recited by the means.

[0150] Fig.14 14 is a diagram 1400 showing an example of a hardware implementation of one or more network entities 104. One or more network entities 104 may be a BS, a component of a BS, or may implement BS functionality. One or more network entities 104 may include at least one of a CU 1410, a DU 1430, or a RU 1440. For example, component 199 may be located at any one of the one or more network entities 104, such as at a CU 1410; at both a CU 1410 and a DU 1430; at each of a CU 1410, a DU 1430, and a RU 1440; at a DU 1430; at both a DU 1430 and a RU 1440; or at a RU 1440.

[0151] CU 1410 may include a CU processor 1412. CU processor 1412 may include on-chip memory 1412'. In some aspects, CU 1410 may further include an additional memory module 1414 and a communication interface 1418. CU 1410 communicates with DU 1430 via a midhaul link 162 (such as an F1 interface). DU 1430 may include a DU processor 1432. DU processor 1432 may include on-chip memory 1432'. In some aspects, DU 1430 may further include an additional memory module 1434 and a communication interface 1438. DU 1430 communicates with RU 1440 via a fronthaul link 160. RU 1440 may include a RU processor 1442. RU processor 1442 may include on-chip memory 1442'. In some aspects, the RU 1440 may further include an additional memory module 1444, one or more transceivers 1446, an antenna 1480, and a communication interface 1448. The RU 1440 communicates wirelessly with the UE 102.

[0152] The on-chip memory 1412', 1432', 1442' and the additional memory modules 1414, 1434, 1444 can each be considered a computer-readable medium / memory. Each computer-readable medium / memory can be non-transitory. Each of the processors 1412, 1432, 1442 is responsible for general processing, including executing software stored on the computer-readable medium / memory. The software, when executed by the corresponding processor, causes the processor to perform the various functions described above. The computer-readable medium / memory can also be used to store data manipulated by the processor when executing the software.

[0153] As discussed, the BS orphan RE handling component 150 is configured to: send control signaling to the UE, the control signaling causing the UE to enable at least one of the following: the number of eType1 or eType2 DMRS antenna ports, the minimum FD-OCC despreading length, or at least one orphan RE handling scheme; send DCI to the UE, the DCI scheduling a physical shared channel for at least one of the following: eType1 DMRS, at least one indicated eType1 / eType2 DMRS antenna port, the indicated FD-OCC despreading length, or the indicated orphan RE handling scheme; and communicate with the UE on the physical shared channel based on at least one of the following: at least one indicated eType1 / eType2 DMRS antenna port, the indicated FD-OCC despreading length, or the indicated orphan RE handling scheme. The BS orphan RE handling component 150 may be located within one or more processors of one or more of the CU 1410, the DU 1430, and the RU 1440. The BS orphan RE handling component 150 may be one or more hardware components specifically configured to execute the process / algorithm, implemented by one or more processors configured to execute the process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof.

[0154] The one or more network entities 104 may include various components configured for various functions. In one configuration, the one or more network entities 104 include: a component for sending control signaling to a UE, the control signaling causing the UE to enable at least one of the following: the number of eType1 or eType2 DMRS antenna ports, the minimum FD-OCC despreading length, or at least one orphan RE handling scheme; a component for sending DCI to the UE, the DCI scheduling a physical shared channel for at least one of the following: eType1 DMRS, at least one indicated eType1 / eType2 DMRS antenna port, an indicated FD-OCC despreading length, or an indicated orphan RE handling scheme; and a component for communicating with the UE on the physical shared channel based on at least one of the following: at least one indicated eType1 / eType2 DMRS antenna port, an indicated FD-OCC despreading length, or an indicated orphan RE handling scheme. The apparatus 1400 further includes means for receiving a UE capability report from the UE, the UE capability report indicating that the UE supports at least one of: a total number of eType1 / eType2 DMRS antenna ports, a set of FD-OCC despreading lengths, or at least a first orphan RE handling scheme. The means may be a BS orphan RE handling component 150 of one or more network entities 104 configured to perform the functions recited by the means.

[0155] The specific order or hierarchy of the boxes in the process and flow chart disclosed herein is an illustration of an example method. Therefore, the specific order or hierarchy of the boxes in the process and flow chart can be rearranged. Some boxes can also be merged or deleted. Dashed lines can represent optional elements of the diagram. The attached method claims present elements of each box in an example order and are not limited to the specific order or hierarchy presented in the claims, process and flow chart.

[0156] The detailed description set forth herein describes various configurations in conjunction with the accompanying drawings, but does not represent the only configuration in which the concepts described herein can be practiced. The detailed description includes specific details for providing a comprehensive explanation of the various concepts. However, these concepts can be practiced without using these specific details. In some cases, well-known structures and components are shown in block diagram form in order to avoid blurring such concepts.

[0157] Various aspects of wireless communication systems (such as telecommunication systems) are presented with reference to various equipment and methods. These equipment and methods are described in the detailed description that follows and are illustrated in the accompanying drawings by various blocks, components, circuits, processes, call flows, systems, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using electronic hardware, computer software, or a combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and design constraints imposed on the overall system.

[0158] Elements, or any part of elements or any combination of elements can be implemented as a "processing system" including one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems on chip (SoCs), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gating logic, discrete hardware circuits, and other similar hardware configured to perform various functions described throughout this disclosure. One or more processors in a processing system can execute software, which can be referred to as software, firmware, middleware, microcode, hardware description language, or other. Software should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executables, execution threads, processes, functions, or any combination thereof.

[0159] If the functions described herein are implemented in software, the functions may be stored on a computer-readable medium (such as a non-transitory computer-readable storage medium) or encoded as one or more instructions or codes on the computer-readable medium. Computer-readable media include computer storage media and may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of these types of computer-readable media, or any other medium that can be used to store computer-executable code in the form of computer-accessible instructions or data structures. The storage medium can be any available medium that is accessible to a computer.

[0160] The aspects, implementations, and / or use cases described herein may be implemented across many different platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, the aspects, implementations, and / or use cases may be generated via integrated chip implementations and other non-module component-based devices such as end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / procurement devices, medical devices, artificial intelligence (AI)-enabled devices, machine learning (ML)-enabled devices, and the like. The aspects, implementations, and / or use cases may range from chip-level or modular components to non-modular or non-chip-level implementations, and further to aggregated, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more of the techniques described herein.

[0161] Devices incorporating the various aspects and features described herein may also include additional components and features for implementing and practicing the various aspects and features claimed and described. For example, the transmission and reception of wireless signals necessarily include many components for analog and digital purposes, such as hardware components, antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc. The techniques described herein may be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, aggregated or disaggregated components, end-user devices, etc., in various configurations.

[0162] The description herein is provided to enable those skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Therefore, the claims are not limited to the various aspects described herein, but should be interpreted in view of the full scope of the disclosure consistent with the language of the claims.

[0163] Unless explicitly stated, references to singular elements do not mean "one and only one", but "one or more". Terms such as "if", "when ..." and "at ..." do not imply an immediate temporal relationship or reaction. That is, phrases such as "when ..." do not imply an immediate action in response to the occurrence of an action or during the occurrence of an action, but simply mean that if a certain condition is met, a certain action will occur, but no specific or immediate time constraints are required for the occurrence of the action. Unless explicitly stated otherwise, the term "some" refers to one or more. Combinations such as "at least one of A, B or C" or "one or more of A, B or C" include any combination of A, B and / or C, such as A and B, A and C, B and C, or A and B and C, and may include multiple A, multiple B and / or multiple C, or may include only A, only B or only C. A set should be interpreted as a set of elements in which the number of elements is one or more.

[0164] Unless expressly indicated otherwise, ordinal terms such as "first" and "second" do not necessarily imply an order in time, sequence, value, etc., but are used to distinguish different instances of the term or phrase following each ordinal term.

[0165] The structural equivalents and functional equivalents of the elements of various aspects described in the entire disclosure known or later learned by those of ordinary skill in the art are expressly incorporated herein by reference and are covered by the claims. The words "module", "mechanism", "element", "device", etc. may not be substitutes for the word "component". Therefore, unless the phrase "component for ..." is used to clearly state the claim element, any claim element shall not be interpreted as a means plus function. As used herein, the phrase "based on" should not be interpreted as a reference to a closed information set, one or more conditions, one or more factors, etc. In other words, unless clearly stated differently, the phrase "based on A" (where "A" can be information, conditions, factors, etc.) should be interpreted as "at least based on A".

[0166] The following examples are merely illustrative and may be combined with other examples or teachings described herein without limitation.

[0167] Example 1 is a method of wireless communication at a UE, comprising: receiving control signaling from a network entity, the control signaling causing the UE to enable at least one of: the number of enhanced Type1 (eType1) or eType2 demodulation reference signal (DMRS) antenna ports, the minimum frequency-domain orthogonal cover code (FD-OCC) despreading length, or at least one isolated resource element (RE) handling scheme; receiving downlink control information (DCI) from the network entity, the DCI scheduling a physical shared channel for at least one of: at least one indicated eType1 / eType2 DMRS antenna port, the indicated minimum FD-OCC despreading length, or an indicated isolated RE handling scheme; and communicating with the network entity on the physical shared channel based on at least one of: the at least one indicated eType1 / eType2 DMRS antenna port, the indicated FD-OCC despreading length, or the indicated isolated RE handling scheme.

[0168] Example 2 may be combined with Example 1 and further include sending a UE capability report to the network entity, the UE capability report indicating that the UE supports at least one of: a total number of eType1 / eType2 DMRS antenna ports, a FD-OCC despreading length set, or at least a first isolated RE handling scheme.

[0169] Example 3 may be combined with any one of Examples 1 to 2 and include that the physical shared channel is a physical uplink shared channel (PUSCH).

[0170] Example 4 can be combined with any one of Examples 1 to 2 and includes receiving the control signaling further including: receiving an indication that the minimum FD-OCC despread length value is greater than 2; and including receiving the DCI including: receiving the minimum indicated FD-OCC despread length equal to 4.

[0171] Example 5 may be combined with Example 4 and include that receiving the control signaling further includes: receiving an indicator of the at least one orphan RE handling scheme.

[0172] Example 6 may be combined with any one of Examples 1 to 2 and include that the physical shared channel is a physical downlink shared channel (PDSCH).

[0173] Example 7 may be combined with Example 6 and include that receiving the control signaling further includes: receiving an indicator of the at least one orphan RE handling scheme.

[0174] Example 8 may be combined with any one of Examples 1 to 7 and include receiving the control signaling further comprising: receiving the control signaling via a radio resource control (RRC) message.

[0175] Example 9 may be combined with any one of Examples 1 to 8 and include communicating with the network entity further comprising: avoiding sending DMRS in isolated REs; and avoiding using isolated REs for data transmission.

[0176] Example 10 may be combined with any one of Examples 1 to 9 and include communicating with the network entity further comprising: avoiding sending DMRS in isolated REs; and avoiding using subcarriers of isolated REs for phase tracking reference signals (PT-RS).

[0177] Example 11 may be combined with any one of Examples 1 to 10 and include communicating with the network entity further comprising: shifting the first PT-RS from a subcarrier of the isolated RE to a subcarrier.

[0178] Example 12 may be combined with any one of Examples 1 to 11 and include communicating with the network entity further comprising: shifting the second PT-RS to a second subcarrier different from the isolated RE.

[0179] Example 13 may be combined with any one of Examples 1 to 8 and include communicating with the network entity further comprising: sending the DMRS in the isolated RE; and performing FD-OCC despreading using adjacent DMRS REs.

[0180] Example 14 may be combined with any one of Examples 6 to 8 and include receiving the DCI from the network entity further comprising: receiving an indication to send or avoid sending the DMRS in the isolated RE.

[0181] Example 15 may be combined with any one of Examples 6 to 8 and include receiving the control signaling further comprising: receiving an indication from the network entity that the network entity does not send a phase tracking reference signal (PT-RS) on an RE having the same subcarrier index as the isolated RE.

[0182] Example 16 may be combined with any one of Examples 6 to 8 and include receiving the control signaling further comprising: receiving from the network entity an indication to the network entity to send a PT-RS on an RE having the same subcarrier index as the isolated RE.

[0183] Example 17 is an apparatus for wireless communication for implementing the method described in any one of Examples 1 to 16.

[0184] Example 18 is a non-transitory computer-readable medium storing computer executable code, which, when executed by at least one processor, causes the at least one processor to implement the method as described in any one of Examples 1-16.

[0185] Example 19 is a method for wireless communication at a network entity, comprising: sending control signaling to a user equipment (UE), the control signaling enabling the UE to enable at least one of: the number of enhanced Type1 (eType1) or eType2 demodulation reference signal (DMRS) antenna ports, the minimum FD-OCC despreading length, or at least one isolated resource element (RE) handling scheme; sending downlink control information (DCI) to the UE, the DCI scheduling a physical shared channel for at least one of: at least one indicated eType1 / eType2 DMRS antenna port, the indicated minimum FD-OCC despreading length, or an indicated isolated RE handling scheme; and communicating with the UE on the physical shared channel based on at least one of: the at least one indicated eType1 / eType2 DMRS antenna port, the indicated FD-OCC despreading length, or the indicated isolated RE handling scheme.

[0186] Example 20 may be combined with Example 19 and further include receiving a UE capability report from the UE, the UE capability report indicating that the UE supports at least one of: a total number of eType1 / eType2 DMRS antenna ports, a set of FD-OCC despreading lengths, or at least a first isolated RE handling scheme.

[0187] Example 21 can be combined with Examples 19 to 20 and include that the physical shared channel is a physical uplink shared channel (PUSCH).

[0188] Example 22 can be combined with Examples 19 to 20 and include sending the control signaling further including: sending an indication that the minimum FD-OCC despreading length value is greater than 2; and including sending the DCI including: sending the FD-OCC despreading length of the indication is equal to 4.

[0189] Example 23 may be combined with Example 22 and include sending the control signaling further comprising: sending an indicator of the at least one orphan RE handling scheme.

[0190] Example 24 can be combined with Example 19 and include that the physical shared channel is a physical downlink shared channel (PDSCH).

[0191] Example 25 may be combined with Example 24 and include that sending the control signaling further includes: sending an indicator of the at least one orphan RE handling scheme.

[0192] Example 26 may be combined with Examples 19 to 25 and include sending the control signaling further comprising: sending the control signaling using a radio resource control (RRC) message.

[0193] Example 27 can be combined with Examples 19 to 26 and include communicating with the UE further comprising: sending an indication to the UE to avoid sending a DMRS on the isolated RE; and sending an indication to the UE to avoid using the isolated RE for data transmission.

[0194] Example 28 can be combined with Examples 19 to 27 and include sending the control signaling further including: sending an indication to the UE to avoid sending the DMRS on the isolated RE; and sending an indication to the UE to avoid using an RE with the same subcarrier index as the isolated RE for data transmission.

[0195] Example 29 may be combined with Examples 19 to 28 and include sending the control signaling further comprising: sending an indication to the UE to send the DMRS on the isolated RE; and using adjacent DMRS REs for FD-OCC despreading.

[0196] Example 30 can be combined with Examples 24 to 26 and include sending the control signaling further comprising: avoiding sending a DMRS on the isolated RE; and sending an indication to the UE to avoid using the isolated RE for data transmission.

[0197] Example 31 can be combined with Examples 24 to 26 and include sending the control signaling further including: sending an indication to the UE to use the isolated RE for data transmission.

[0198] Example 32 can be combined with Examples 24 to 26 and include sending the control signaling further including: avoiding sending DMRS on the isolated RE; and sending an indication to the UE to avoid using RE with the same subcarrier index as the isolated RE for data transmission.

[0199] Example 33 may be combined with Examples 24 to 26 and include sending the control signaling further comprising: determining whether to send the DMRS on the isolated RE based on the FD-OCC despreading length.

[0200] Example 34 may be combined with Examples 25 to 26 and include sending the control signaling further comprising: sending the DMRS on the isolated RE; and using adjacent DMRS REs for FD-OCC despreading.

[0201] Example 35 can be combined with Examples 24 to 26 and include sending the control signaling further including: avoiding sending a phase tracking reference signal (PT-RS) on an RE having the same subcarrier index as the isolated RE.

[0202] Example 36 may be combined with Examples 24 to 26 and include sending the control signaling further comprising: sending the PT-RS on an RE having the same subcarrier index as the isolated RE.

[0203] Example 37 is an apparatus for wireless communication for implementing a method as described in any one of Examples 1 to 36.

[0204] Example 38 is an apparatus for wireless communications comprising components for implementing a method as described in any of Examples 1-36.

[0205] Example 39 is a non-transitory computer-readable medium storing computer executable code, which, when executed by at least one processor, causes the at least one processor to implement a method as described in any one of Examples 1 to 36.

Claims

1. A method for wireless communication at a user equipment UE, comprising: Receive control signaling from a network entity, the control signaling enabling the UE to enable at least one of the following: the number of enhanced Type 1 eType 1 or eType 2 demodulation reference signal DMRS antenna ports, the minimum frequency domain orthogonal cover code FD-OCC despreading length, or at least one isolated resource element RE handling scheme; receiving downlink control information DCI from the network entity, the DCI scheduling a physical shared channel for at least one of: at least one indicated eType1 / eType2 DMRS antenna port, an indicated minimum FD-OCC despreading length, or an indicated orphan RE handling scheme; as well as Communicating with the network entity on the physical shared channel is performed based on at least one of: the at least one indicated eType1 / eType2 DMRS antenna port, the indicated FD-OCC despreading length, or the indicated orphan RE handling scheme.

2. The method of claim 1, further comprising: A UE capability report is sent to the network entity, the UE capability report indicating that the UE supports at least one of: a total number of eType1 / eType2 DMRS antenna ports, a set of FD-OCC despreading lengths, or at least a first orphan RE handling scheme.

3. The method according to claims 1 to 2, wherein the physical shared channel is a physical uplink shared channel (PUSCH).

4. The method according to claims 1 to 2, wherein receiving the control signaling comprises: receiving an indication that the minimum FD-OCC despread length value is greater than 2; and Wherein receiving the DCI comprises: The minimum FD-OCC despreading length for receiving the indication is equal to 4.

5. The method of claim 4, wherein receiving the control signaling comprises: An indicator of the at least one orphan RE handling solution is received.

6. The method according to claims 1 to 2, wherein the physical shared channel is a physical downlink shared channel (PDSCH).

7. The method of claim 6, wherein receiving the control signaling comprises: An indicator of the at least one orphan RE handling solution is received.

8. The method according to any one of claims 1 to 7, wherein receiving the control signaling comprises: The control signaling is received via a radio resource control (RRC) message.

9. The method of any one of claims 1 to 8, wherein communicating with the network entity comprises: Avoid sending the DMRS in the isolated RE; as well as Avoid using isolated REs for data transmission.

10. The method of any one of claims 1 to 9, wherein communicating with the network entity comprises: Avoid sending the DMRS in the isolated RE; as well as Avoid using subcarriers with isolated REs for the phase tracking reference signal PT-RS.

11. The method of any one of claims 1 to 10, wherein communicating with the network entity comprises: The first PT-RS is shifted from subcarrier to subcarrier of the isolated RE.

12. The method of claims 1 to 11, wherein communicating with the network entity comprises: The second PT-RS is shifted to a second subcarrier different from the isolated RE.

13. The method of any one of claims 1 to 8, wherein communicating with the network entity comprises: sending the DMRS in the isolated RE; as well as Adjacent DMRS REs are used for FD-OCC despreading.

14. The method of any one of claims 6 to 8, wherein receiving the DCI from the network entity comprises: An indication to send or avoid sending the DMRS in the orphan RE is received.

15. The method of any one of claims 6 to 8, wherein receiving the control signaling comprises: An indication is received from the network entity that the network entity does not send a phase tracking reference signal (PT-RS) on an RE having the same subcarrier index as the orphan RE.

16. The method of any one of claims 6 to 8, wherein receiving the control signaling comprises: An indication is received from the network entity for the network entity to send a PT-RS on an RE having the same subcarrier index as the orphan RE.

17. An apparatus for wireless communication at a UE, comprising a memory and at least one processor, the at least one processor being coupled to the memory and configured to implement the method according to any one of claims 1 to 16.

18. A non-transitory computer readable medium storing computer executable code at a UE, the code, when executed by at least one processor, causes the at least one processor to implement the method according to any one of claims 1 to 16.

19. A method of wireless communication at a network entity, comprising: Sending control signaling to a user equipment UE, wherein the control signaling enables the UE to enable at least one of the following: the number of enhanced Type 1 eType 1 or eType 2 demodulation reference signal DMRS antenna ports, the minimum FD-OCC despreading length, or at least one isolated resource element RE handling scheme; Sending downlink control information DCI to the UE, the DCI scheduling a physical shared channel for at least one of: at least one indicated eType1 / eType2 DMRS antenna port, an indicated minimum FD-OCC despreading length, or an indicated orphan RE handling scheme; as well as Communicating with the UE on the physical shared channel is performed based on at least one of: the at least one indicated eType1 / eType2 DMRS antenna port, the indicated FD-OCC despreading length, or the indicated orphan RE handling scheme.

20. The method of claim 19, further comprising: A UE capability report is received from the UE, the UE capability report indicating that the UE supports at least one of: a total number of eType1 / eType2 DMRS antenna ports, a set of FD-OCC despreading lengths, or at least a first orphan RE handling scheme.

21. The method according to claims 19 to 20, wherein the physical shared channel is a physical uplink shared channel (PUSCH).

22. The method of claims 19 to 20, wherein sending the control signaling comprises: sending an indication that the minimum FD-OCC despreading length value is greater than 2; and The sending of the DCI comprises: The minimum FD-OCC despreading length for sending the indication is equal to 4.

23. The method of claim 22, wherein sending the control signaling comprises: An indicator of the at least one orphan RE handling solution is sent.

24. The method of claim 19, wherein the physical shared channel is a physical downlink shared channel (PDSCH).

25. The method of claim 24, wherein sending the control signaling comprises: An indicator of the at least one orphan RE handling solution is sent.

26. The method of any one of claims 19 to 25, wherein sending the control signaling comprises: The control signaling is sent using a Radio Resource Control (RRC) message.

27. The method of any one of claims 19 to 26, wherein communicating with the UE comprises: sending an indication to the UE to avoid sending the DMRS on the isolated RE; as well as An indication is sent to the UE to avoid using the isolated RE for data transmission.

28. The method of any one of claims 19 to 27, wherein sending the control signaling comprises: sending an indication to the UE to avoid sending the DMRS on the isolated RE; as well as An indication is sent to the UE to avoid using REs having the same subcarrier index as the isolated RE for data transmission.

29. The method of any one of claims 19 to 28, wherein sending the control signaling comprises: sending an indication to the UE to send the DMRS on the isolated RE; as well as Adjacent DMRS REs are used for FD-OCC despreading.

30. The method of any one of claims 24 to 26, wherein sending the control signaling comprises: Avoid sending the DMRS on the isolated RE; as well as An indication is sent to the UE to avoid using the isolated RE for data transmission.

31. The method of any one of claims 24 to 26, wherein sending the control signaling comprises: An indication is sent to the UE to use the isolated RE for data transmission.

32. The method of any one of claims 24 to 26, wherein sending the control signaling comprises: Avoid sending DMRS on the isolated RE; as well as An indication is sent to the UE to avoid using REs having the same subcarrier index as the isolated RE for data transmission.

33. The method of any one of claims 24 to 26, wherein sending the control signaling comprises: Whether to transmit the DMRS on the isolated RE is determined based on the FD-OCC despreading length.

34. The method of any one of claims 25 to 26, wherein sending the control signaling comprises: sending the DMRS on the isolated RE; as well as Adjacent DMRS REs are used for FD-OCC despreading.

35. The method of any one of claims 24 to 26, wherein sending the control signaling comprises: Avoid transmitting a phase tracking reference signal PT-RS on an RE having the same subcarrier index as the isolated RE.

36. The method of any one of claims 24 to 26, wherein sending the control signaling comprises: The PT-RS is transmitted on the RE having the same subcarrier index as the isolated RE.

37. An apparatus for wireless communication at a network entity, comprising a memory and at least one processor, the at least one processor being coupled to the memory and configured to implement the method of any one of claims 19 to 36.

38. A non-transitory computer readable medium storing computer executable code at a network entity, which, when executed by at least one processor, causes the at least one processor to implement the method according to any one of claims 19 to 36.

Images