PUSCH dmrs bundling indication for different transport blocks

Abstract

Aspects are provided that allow a UE to perform DMRS bundling in different transport blocks of uplink data on a PUSCH in response to a configuration from a base station indicating the UE to perform DMRS bundling or a configuration enabling the UE to perform DMRS bundling. The UE receives, from the base station, a configuration indicating to bundle DMRSs in different uplink data channel transmissions for joint channel estimation. The UE determines a DMRS bundling window based on the configuration. The UE transmits bundled DMRSs in the DMRS bundling window. The base station performs joint channel estimation based on the bundled DMRSs. Improved link quality and signal gain between the UE and the base station can be accordingly caused by applying DMRS bundling on different PUSCH transmissions.

Description

[0001] Cross-references to (one or more) related applications

[0002] This application claims the benefit of U.S. Provisional Application Serial No. 63 / 137,682, entitled “PUSCH DMRS BUNDLINGINDICATION FOR DIFFERENT TRANSPORT BLOCKS”, filed January 14, 2021, the entire disclosure of which is expressly incorporated herein by reference. Technical Field

[0003] This disclosure relates generally to communication systems, and more specifically to wireless communication systems between user equipment (UE) and base stations. Background Technology

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

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

[0006] The following is a simplified overview of one or more aspects to provide a basic understanding of such aspects. This overview is not a comprehensive summary of all anticipated aspects, nor is it intended to identify key or important elements of all aspects, nor to define 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 an introduction to the more detailed descriptions that follow.

[0007] In one aspect of this disclosure, a method, computer-readable medium, and apparatus are provided. The apparatus may be a UE (User Equipment). The apparatus receives from a base station a configuration indicating the bundling of demodulation reference signals (DMRS) in different uplink data channel transmissions for joint channel estimation. Based on this configuration, the apparatus determines a DMRS bundling window and transmits the bundled DMRS within the DMRS bundling window.

[0008] In one aspect of this disclosure, a method, computer-readable medium, and apparatus are provided. The apparatus may be a base station. The apparatus transmits to a UE a configuration indicating that different DMRSs in uplink data channel transmissions are bundled for joint channel estimation. Based on this configuration, the apparatus receives bundled DMRSs within a DMRS bundling window and performs joint channel estimation based on the bundled DMRSs.

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

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

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

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

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

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

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

[0016] Figure 4A and Figure 4B This is a diagram illustrating an example of DMRS carried in repetitions of uplink data channel transmission.

[0017] Figure 5 This is an example graph illustrating the different relationships between signal-to-noise ratio and block error rate for transport blocks with and without DMRS binding.

[0018] Figure 6 This is a diagram illustrating an example of a DMRS bundled window that includes transmissions over different uplink data channels.

[0019] Figure 7 This is a diagram illustrating another example of DMRS bundled windows that contain different uplink data channel transmissions.

[0020] Figure 8 This is a diagram illustrating a further example of a DMRS bundled window that includes transmissions over different uplink data channels.

[0021] Figure 9 This is a call flow diagram between the UE and the base station.

[0022] Figure 10 This is a flowchart of the wireless communication method at the UE.

[0023] Figure 11 This is a flowchart of a wireless communication method at a base station.

[0024] Figure 12 This is a diagram illustrating an example hardware implementation of an example device (i.e., UE).

[0025] Figure 13 This is a diagram illustrating another example of a hardware implementation of another example device (i.e., a base station). Detailed Implementation

[0026] The detailed description that follows, taken in conjunction with the accompanying drawings, is intended as a description of various configurations and not as representing only configurations in which the concepts described herein can be practiced. The detailed description includes specific details intended to provide a thorough understanding of the various concepts. However, it will be apparent to those skilled in the art that these concepts can be practiced without these specific details. In some cases, well-known structures and components are shown in block diagram form to avoid obscuring such concepts.

[0027] When a UE transmits data on the Physical Uplink Shared Channel (PUSCH), it can transmit a demodulation reference signal (DMRS) in each time slot carrying the data. For example, when transmitting DMRS on the PUSCH, the UE can transmit DMRS in consecutive time slots carrying different uplink data transmissions scheduled by the base station. The base station can process the DMRS to generate a channel estimate for demodulation on the PUSCH. For example, the base station can measure the Reference Signal Received Power (RSRP) of the DMRS in one symbol of a time slot and determine the Channel Quality Indicator (CQI) based on the RSRP of the DMRS in that particular time slot. The base station can similarly measure the RSRP and determine the CQI based on the DMRS in other individual time slots. Therefore, the base station can use the DMRS individually for each time slot to estimate the channel.

[0028] However, in some cases, performing such processing of the DMRS individually for each time slot can lead to channel estimation errors. For example, if the UE is located at the cell edge, the RSRP of the DMRS may change between time slots (e.g., due to interference between the UE and the base station or other factors), and therefore the CQI that the base station can determine individually for one time slot may be inaccurate for the next time slot. As a result, if the base station performs link adaptation based on incorrect channel estimation, the quality of the communication link between the base station and the UE may deteriorate.

[0029] To prevent link quality degradation based on erroneous channel estimation, DMRS bundling can be applied. In DMRS bundling, when a transmitter (e.g., a UE) transmits DMRS to a receiver (e.g., a base station) in multiple time slots (e.g., transmitting one DMRS in one time slot, another in the next, and so on), the transmitter maintains power consistency and phase continuity between the DMRS. For example, to maintain phase continuity between DMRS, the same modulation and coding scheme (MCS) (e.g., binary phase shift keying (BPSK) or quadrature phase shift keying (QPSK)) can be used to transmit DMRS, the same duplex scheme (e.g., time division duplex (TDD) or frequency division duplex (FDD)) can be used to transmit DMRS in time slots, or consecutive, allocated time-domain resources can be used to transmit DMRS. Similarly, to maintain power consistency between DMRS, the same transmission power can be used to transmit DMRS. After the receiver receives the bundled DMRS in multiple time slots, the receiver jointly processes the DMRS (e.g., for channel estimation). For example, a receiver can measure the average RSRP from the RSRPs of power-consistent and phase-continuous DMRSs across multiple time slots and identify the CQI based on the average RSRP. Therefore, the receiver can jointly process DMRSs across multiple time slots. In this way, due to DMRS bundling, the possibility of erroneous channel estimation caused by RSRP changes between time slots can be reduced (and may lead to signal gain).

[0030] Therefore, applying DMRS bundling to different transport blocks of a PUSCH transmission can lead to improved link quality and signal gain through joint channel estimation. Thus, it is desirable to specify a mechanism capable of performing DMRS bundling or joint channel estimation (e.g., with consistent DMRS transmission power and phase continuity) across multiple transport blocks of different PUSCH transmissions. To this end, aspects of this disclosure are provided that allow a base station to configure DMRS bundling (and thus enable joint channel estimation) and allow the UE to determine, based on the configuration, the PUSCH transmissions in which to bundle DMRS (e.g., a DMRS bundling window). For example, when a base station configures DMRS bundling across multiple different PUSCH transmissions, the base station can configure the UE to maintain power consistency and phase continuity between DMRS during transmissions, such that when the base station receives DMRS with consistent power and phase continuity, the base station can jointly process the DMRS (e.g., for channel estimation). Furthermore, the UE can determine a DMRS bundling window, which includes a start time corresponding to one of the transmissions (e.g., one transport block) and an end time corresponding to another of the transmissions (e.g., another transport block), within which the UE intends to maintain power consistency and phase continuity between DMRS. As a result, when the base station instructs the UE to bundle DMRS, the base station can configure the UE to transmit DMRS with consistent power and continuous phase across multiple PUSCH slots within the determined DMRS bundling window. Furthermore, when the base station receives the bundled DMRS, it can perform joint channel estimation based on the DMRS with consistent power and continuous phase received within the DMRS bundling window. In this way, the aforementioned benefits of improving link quality and signal gain through DMRS bundling can be achieved.

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

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

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

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

[0035] Base station 102 configured for 4G Long Term Evolution (LTE) (collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) can be connected to EPC 160 via a first backhaul link 132 (e.g., S1 interface). Base station 102 configured for 5G New Radio (NR) (collectively referred to as Next Generation RAN (NG-RAN)) can be connected to the core network 190 via a second backhaul link 184. Among other functions, base station 102 can perform one or more of the following functions: user data transmission, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution of Non-Access Stratum (NAS) messages, NAS node selection, synchronization, Radio Access Network (RAN) sharing, Multimedia Broadcast Multicast Service (MBMS), subscriber and device tracking, RAN Information Management (RIM), paging, location, and delivery of warning messages. Base stations 102 can communicate directly or indirectly with each other (e.g., via EPC 160 or core network 190) via a third backhaul link 134 (e.g., an X2 interface). The first backhaul link 132, the second backhaul link 184, and the third backhaul link 134 can be wired or wireless.

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

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

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

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

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

[0041] In light of the foregoing, unless otherwise specifically stated, it should be understood that the terms "below 6 GHz" and the like, if used herein, can broadly refer to frequencies less than 6 GHz, frequencies within FR1, or frequencies that may include intermediate frequency bands. Furthermore, unless otherwise specifically stated, it should be understood that the terms "millimeter wave" and the like, if used herein, can broadly refer to frequencies that may include intermediate frequency bands, frequencies within FR2, or frequencies within the EHF band.

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

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

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

[0045] The core network 190 may include Access and Mobility Management Functions (AMF) 192, other AMFs 193, Session Management Functions (SMF) 194, and User Plane Functions (UPF) 195. AMF 192 may communicate with Unified Data Management (UDM) 196. AMF 192 is the control node that handles signaling between UE 104 and the core network 190. Typically, AMF 192 provides Quality of Service (QoS) streaming and session management. All user IP packets are transmitted through UPF 195. UPF 195 provides UE IP address allocation and other functions. UPF 195 connects to IP services 197. IP services 197 may include the Internet, intranet, IMS, packet-switched (PS) streaming services, and / or other IP services.

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

[0047] Refer again Figure 1 In some respects, UE 104 may include UE DMRS bundling component 198. UE DMRS bundling component 198 is configured to receive from a base station a configuration indicating the bundling of DMRS in different uplink data channel transmissions for joint channel estimation, determine a DMRS bundling window based on the configuration, and transmit the bundled DMRS within the DMRS bundling window.

[0048] Refer again Figure 1 In some respects, base station 102 / 180 may include BS DMRS bundling component 199. BS DMRS bundling component 199 is configured to transmit to the UE a configuration indicating that DMRS in different uplink data channel transmissions are bundled for joint channel estimation, receive bundled DMRS in a DMRS bundling window based on this configuration, and perform joint channel estimation based on the bundled DMRS.

[0049] While this disclosure may focus on 5G NR, the concepts and aspects described herein are applicable to other similar fields, such as LTE, LTE-A Advanced, Code Division Multiple Access (CDMA), Global System for Mobile Communications (GSM), or other wireless / radio access technologies.

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

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

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

[0053] like Figure 2A As shown, some REs carry reference (pilot) signals (RS) for the UE. The RS may include a demodulated RS (DM-RS) (indicated as R for a particular configuration).x (where 100x is the port number, but other DM-RS configurations are also possible) and the Channel State Information Reference Signal (CSI-RS) used for channel estimation at the UE. RS may also include Beam Measurement RS (BRS), Beam Refinement RS (BRRS), and Phase Tracking RS (PT-RS).

[0054] Figure 2B Examples of various DL channels within a subframe of a frame are shown. The Physical Downlink Control Channel (PDCCH) carries the DCI within one or more Control Channel Elements (CCEs), each CCE comprising nine RE Groups (REGs), each REG comprising four consecutive REs in an OFDM symbol. The PDCCH within a BWP can be referred to as a Control Resource Set (CORESET). Additional BWPs can be located at higher and / or lower frequencies across the entire channel bandwidth. The Primary Synchronization Signal (PSS) can be located within symbol 2 of a specific subframe of the frame. The PSS is used by the UE 104 to determine subframe / symbol timing and physical layer identification. The Secondary Synchronization Signal (SSS) can be located within symbol 4 of a specific subframe of the frame. The SSS is used by the UE to determine the Physical Layer Cell Identifier Group Number and radio frame timing. Based on the Physical Layer Identifier and Physical Layer Cell Identifier Group Number, the UE can determine the Physical Cell Identifier (PCI). Based on the PCI, the UE can determine the location of the aforementioned DM-RS. The Physical Broadcast Channel (PBCH), carrying the Master Information Block (MIB), can be logically grouped with the PSS and SSS to form a Synchronization Signal (SS) / PBCH block (also known as an SS block (SSB)). The MIB provides the number of Relay Blocks (RBs) and the System Frame Number (SFN) in the system bandwidth. The Physical Downlink Shared Channel (PDSCH) carries user data, broadcast system information not transmitted via the PBCH (such as System Information Blocks (SIBs)), and paging messages.

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

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

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

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

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

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

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

[0062] The TX processor 368 can use the channel estimator 358 to select appropriate coding and modulation schemes from the reference signal transmitted by the base station 310 or the channel estimate derived from feedback, and facilitate spatial processing. The spatial stream generated by the TX processor 368 can be provided to different antennas 352 via individual transmitters 354TX. Each transmitter 354TX can modulate an RF carrier with the corresponding spatial stream for transmission.

[0063] UL transmission is processed at base station 310 in a manner similar to the receiver function description at UE 350. Each receiver 318RX receives signals through its corresponding antenna 320. Each receiver 318RX recovers the information modulated onto the RF carrier and provides that information to RX processor 370.

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

[0065] At least one of the TX processor 368, RX processor 356, and controller / processor 359 can be configured to perform operations related to... Figure 1 Aspects related to UE DMRS bundled components 198.

[0066] At least one of the TX processor 316, RX processor 370, and controller / processor 375 can be configured to perform operations related to... Figure 1 The relevant aspects of the BS DMRS bundled component 199.

[0067] When a base station schedules a UE to transmit uplink data in different transport blocks within a PUSCH, dynamic granting can be used to accomplish the scheduling. When scheduling uplink data in a PUSCH within dynamic granting, the base station can transmit a DCI to the UE, which includes time-domain resource allocations indicating parameters associated with one or more different PUSCH transmissions, such as slot offset, start and length indicator values ​​(SLIVs), and PUSCH mapping types (e.g., PUSCH mapping type A or B). The base station can also transmit a PUSCH configuration (e.g., pusch-Config or other names) to the UE via dedicated RRC signaling, which may include a list of time-domain allocations indicating parameters associated with time-domain resource allocations in the DCI.

[0068] Furthermore, when the UE transmits data on an uplink data channel (e.g., on the PUSCH), the UE can transmit DMRS in each time slot carrying the data. For example, when transmitting DMRS on the PUSCH, the UE can transmit DMRS in consecutive time slots carrying different uplink data transmissions using one or more dynamic grant scheduling. The base station can process the DMRS to generate a channel estimate for PUSCH demodulation. For example, Figure 4A An example 400 is shown, comprising multiple time slots 402 carrying data in a PUSCH including DMRS 404. The data transmitted in each time slot 402 may differ from one another (e.g., different transport blocks). When the base station receives data in each time slot 402, it can process the DMRS 404 in each time slot individually for channel estimation. For example, the base station can measure the RSRP of the DMRS 404 in symbol 406 of one of the time slots 402 and determine the CQI based on the RSRP of the DMRS in that particular time slot. The base station can similarly measure the RSRP of the DMRS from other individual time slots and determine the CQI. Therefore, the base station can use the DMRS individually for each time slot to estimate the channel.

[0069] However, in some cases, processing DMRS in this way for each time slot can lead to channel estimation errors. For example, if the UE is located at the cell edge, the RSRP of the DMRS may change between time slots (e.g., due to interference between the UE and the base station or other factors), and therefore the CQI that the base station can determine individually for one time slot may be inaccurate for the next time slot. As a result, if the base station performs link adaptation based on incorrect channel estimation, the quality of the communication link between the base station and the UE may deteriorate.

[0070] To prevent link quality degradation based on erroneous channel estimation, DMRS bundling can be applied. In DMRS bundling, when a transmitter (e.g., a UE) transmits DMRS to a receiver (e.g., a base station) across multiple time slots (e.g., transmitting one DMRS in one time slot, another in the next, and so on), the transmitter maintains power consistency and phase continuity between the DMRS. For example, to maintain phase continuity between DMRS, the same MCS (e.g., BPSK or QPSK) can be used to transmit the DMRS, the same duplex scheme (e.g., TDD or FDD) can be used to transmit the DMRS in the time slots, or consecutive, allocated time-domain resources can be used to transmit the DMRS. Similarly, to maintain power consistency between DMRS, the same transmission power can be used to transmit the DMRS. After the receiver receives the bundled DMRS across multiple time slots, the receiver jointly processes the DMRS (e.g., for channel estimation). For example, the receiver can measure the average RSRP from the RSRP of the power-consistent and phase-continuous DMRS across multiple time slots and identify the CQI based on the average RSRP. Therefore, the receiver can process DMRS jointly across multiple time slots. In this way, due to DMRS bundling, the possibility of erroneous channel estimation caused by changes in RSRP between time slots can be reduced.

[0071] For example, Figure 4B Example 450 shows multiple time slots 452 carrying data in a PUSCH including bundled DMRS 454. The data transmitted in each time slot 402 can be different from each other (e.g., different transport blocks). Furthermore, the DMRS in each time slot 452 are power-consistent and phase-continuous (bundled). Therefore, when the base station receives data in each time slot 402, the base station can jointly process the bundled DMRS 454 in the time slots for channel estimation. For example, the base station can perform joint channel estimation by measuring the average RSRP of the DMRS in symbols 456, 458, and 460 of each time slot 402 and determining the CQI based on the average RSRP of the DMRS in the multiple time slots. Therefore, the risk of erroneous channel estimation due to RSRP changes between time slots 452 can be reduced.

[0072] In addition to reducing the risk of erroneous channel estimation, DMRS bundling can also lead to signal gain. Figure 5 The diagram illustrates an example of signal gain that may occur due to DMRS bundling. Curve 502 shows the effect of carrying signals from different transport blocks (e.g., as mentioned above). Figure 4A and 4B The block error rate (BLER) and signal-to-noise ratio (SNR) experienced by the UE in time slots for different PUSCH transmissions and data from repeated transport blocks (e.g., repetitions of PUSCH transmissions). This example also assumes the UE has a single transmit antenna and four receive antennas, the UE transmits data including a single DMRS symbol to the base station in a single resource block (RB) or time slot, and there is an 11 Hz (Doppler) frequency shift between the UE and the base station. As shown in the table, it has been found that applying DMRS bundling to the joint channel estimation results in a signal gain of approximately 0.8–1.8 dB, depending on the number of time slots including the bundled DMRS.

[0073] therefore, Figure 4B and Figure 5 This demonstrates the benefits that can result from applying DMRS bundling across different transport blocks of PUSCH transmission (e.g., improved link quality and signal gain through joint channel estimation). Furthermore, joint channel estimation can be supported across different transport blocks using uplink data with one or more dynamically licensed schedules. Therefore, a mechanism needs to be specified that enables DMRS bundling or joint channel estimation (e.g., with consistent DMRS transmission power and phase continuity) across multiple transport blocks of different PUSCH transmissions.

[0074] To this end, aspects of this disclosure are provided that allow a base station to configure DMRS bundling (and thus enable joint channel estimation) and allow a UE to determine, based on the configuration, the PUSCH transmissions in which to bundle DMRS (e.g., a DMRS bundling window). For example, when a base station configures DMRS bundling across multiple different PUSCH transmissions, the base station can configure the UE to maintain power consistency and phase continuity between DMRS during transmissions, such that when the base station receives power-consistent and phase-continuous DMRS, the base station can jointly process the DMRS (e.g., for channel estimation). Furthermore, the UE can determine a DMRS bundling window that includes a start time corresponding to one of the transmissions (e.g., a transport block) and an end time corresponding to another of the transmissions (e.g., another transport block), in which the UE maintains power consistency and phase continuity between DMRS. As a result, when the base station instructs the UE to bundle DMRS, the base station can configure the UE to transmit DMRS with consistent power and continuous phase across multiple PUSCH slots within the determined DMRS bundling window. Furthermore, when the base station receives the bundled DMRS, it can perform joint channel estimation based on the DMRS with consistent power and continuous phase received within the DMRS bundling window. In this way, the aforementioned benefits of improving link quality and signal gain through DMRS bundling can be achieved.

[0075] Although the examples described below regarding DMRS bundling involve cases where PUSCH transmissions occupy the same frequency (e.g., the same 12 subcarriers of multiple physical resource blocks without frequency hopping, such as...), Figure 4B (As shown), but in other examples, the transmission may alternatively occupy multiple frequencies (e.g., with inter-slot frequency hopping). Therefore, joint channel estimation based on DMRS bundling can be performed with or without inter-slot frequency hopping. Furthermore, although the examples described below regarding DMRS bundling involve PUSCH transmissions occupying a single DMRS bundling window, in other examples, the transmission may alternatively occupy multiple consecutive or discontinuous DMRS bundling windows or be split between multiple consecutive or discontinuous DMRS bundling windows. The parameters of each of these multiple DMRS bundling windows (e.g., the duration or start / end time of each window) can be configured in the same or similar manner as for a single DMRS bundling window, as described below.

[0076] In the first example, the base station may provide the UE with a configuration that instructs the UE to perform DMRS bundling across dynamically scheduled PUSCH transmissions carrying different transport blocks for joint channel estimation, or enables the UE to perform DMRS bundling across dynamically scheduled PUSCH transmissions carrying different transport blocks for joint channel estimation. For example, when PUSCH transmissions are dynamically scheduled in one or more DCIs, the base station may provide the UE with a configuration within the PUSCH configuration (e.g., PUSCH-Config) that enables DMRS bundling. This configuration may be, for example, one or more bits or flags indicating whether the UE wants to bundle DMRS in time slots carrying different uplink data on the PUSCH (e.g., to maintain DMRS power consistency and phase continuity), allowing the base station to perform joint channel estimation on the DMRS received from the UE. The same configuration (e.g., bits or flags) may enable DMRS bundling for different transport blocks of the PUSCH transmission as well as for repeated transport blocks (repeated) of the PUSCH transmission. Alternatively, different configurations (e.g., bits or flags) may enable DMRS bundling for different and identical transport blocks of the PUSCH transmission. For example, this configuration may include one or more bits that instruct the UE to transmit DMRS in each time slot of different PUSCH transmissions with the same MCS, the same TDD or FDD duplex scheme, in consecutive time-domain resources, or with the same transmission power. Therefore, in this example, the UE can determine that the DMRS bundling window contains dynamically scheduled PUSCH transmissions in one or more DCIs, and the base station can perform joint channel estimation of DMRS within the DMRS bundling window.

[0077] In the second example, when the base station provides the UE with a DCI to schedule multiple PUSCH transmissions in different transport blocks, the DCI can indicate a DMRS bundling window, including a start slot and an end slot or duration, in which the DMRS of the scheduled PUSCH transmissions are bundled for joint channel estimation. For example, the DCI can instruct the UE to transmit a set of subsequent slots containing different uplink data, and the UE can determine the DMRS bundling window to correspond to this set of subsequent slots. When DMRS are bundled within a DMRS bundling window, the UE maintains power consistency and phase continuity among the DMRS carried in these slots. For example, Figure 6 Example 600 is shown, in which the UE receives DCI 602 at time slot n, which schedules different uplink data transmissions in multiple time slots 604, including a first PUSCH transmission 606 with DMRS 608 at time slot n+k and a second PUSCH transmission 610 with DMRS 612 at time slot n+k+1. Time slot 604 can be... Figure 4B The time slot 452 corresponds to and DMRS612 can be used with Figure 4BThe bundled DMRS corresponds to DMRS 454. In this case, DCI 602 can instruct the DMRS bundle to start at time slot n+k and end at time slot n+k+1. Therefore, the UE can determine, in response to DCI 602, that the DMRS bundle window 614 contains the first PUSCH transmission and the second PUSCH transmission (time slots n+k and n+k+1). After determining the DMRS bundle window, the UE can bundle DMRS 608 and 612 in time slots 604 within the window by transmitting the DMRS in each time slot with the same MCS, the same TDD or FDD duplex scheme, in consecutive time domain resources, or with the same transmission power to maintain power consistency and phase continuity between the DMRS. Once the base station receives the bundled DMRS, the base station can perform joint channel estimation (e.g., by identifying the average RSRP of DMRS 608 and 612 in time slots 604 within the DMRS bundle window 614).

[0078] Although Figure 6 Example 600 shows a DCI 602 scheduling two different PUSCH transmissions 606, 610 and indicating two time slots 604 for a DMRS bundling window. However, in other examples, the DCI can schedule any number of different PUSCH transmissions and indicate any number of time slots for DMRS bundling (which can be equal to or less than the number of PUSCH transmissions). For example, if DCI 602 indicates that the DMRS bundling begins at time slot n+k and ends at time slot n+k+3 (four time slots), the UE can determine that the DMRS bundling window 614 contains four time slots for the different PUSCH transmissions scheduled by that DCI. In another example, if DCI 602 schedules four different PUSCH transmissions from time slot n+k to time slot n+k+3, but indicates that the DMRS bundling will occur at time slots n+k and n+k+1 (but not at time slots n+k+2 and n+k+3), the UE can determine that the DMRS bundling window 614 contains two indicated time slots.

[0079] In the third example, when the base station provides multiple DCIs to the UE, each DCI scheduling different PUSCH transmissions in a corresponding transport block, each DCI may include a new bundling indicator (NBI) bit that the base station can configure to indicate the DMRS bundling window. The base station can switch the NBI in each DCI to indicate to the UE when the DMRS bundling window starts and ends. For example, if the base station configures the NBI of one DCI to have the same value as the NBI of a previous DCI (e.g., both NBIs are 0 or both NBIs are 1), the UE can determine that the PUSCH transmissions scheduled by the two DCIs are within the same DMRS bundling window. On the other hand, if the base station configures the NBI of one DCI to have a different value than the NBI of a previous DCI (e.g., one NBI is 0 and the other is 1), the UE can determine that the PUSCH transmissions scheduled by the two DCIs are within different DMRS bundling windows. Therefore, based on the NBI of each DCI, the UE can determine which time slots of the PUSCH transmissions, including those scheduled by DMRS, should be bundled with each other, and thus determine the start and end times of each DMRS bundling window. When DMRS are bundled within each DMRS bundling window, the UE maintains power consistency and phase continuity in the DMRS carried in these time slots.

[0080] For example, Figure 7 Example 700 is shown, in which the UE receives DCI 702, each DCI 702 scheduling different uplink data transmissions in a corresponding one of multiple time slots 704, including a first PUSCH transmission 706 with DMRS 708 in a first time slot, a second PUSCH transmission 710 with DMRS 712 in a second time slot, a third PUSCH transmission 714 with DMRS 716 in a third time slot, a fourth PUSCH transmission 718 with DMRS 720 in a fourth time slot, and a fifth PUSCH transmission 722 with DMRS 724 in a fifth time slot. Each time slot can be associated with... Figure 4B The time slot 452 corresponds to and each DMRS can be associated with Figure 4BThe bundled DMRS 454 corresponds to each DCI. Each DCI may include an NBI 726, which is configured to have a value of 0 or 1 to determine the size of the DMRS bundle window 728. For example, the UE may determine that the first DMRS bundle window 728 corresponds to the first PUSCH transmission and the second PUSCH transmission, and that the second DMRS bundle window 728 corresponds to the third, fourth, and fifth PUSCH transmissions. The UE may determine the start time 730 and the stop time 732 of each DMRS bundle window based on the NBI 726 of each DCI 702. For example, in response to an NBI switch (from 0 to 1 in this example) in the DCI scheduling the second and third PUSCH transmissions, the UE may determine the start of the second DMRS bundle window and the end of the first DMRS bundle window. Similarly, in response to a re-switching of the NBI in a subsequent DCI following the DCI that schedules the fifth PUSCH transmission (from 1 to 0 in this example), the UE can determine the second end of the DMRS bundling window (and thus another DMRS bundling window can begin). After determining each DMRS bundling window, the UE can bundle the DMRS in slot 704 within each window by transmitting the DMRS in each of the slots 704 with the same MCS, the same TDD or FDD duplex scheme, in consecutive time-domain resources, or with the same transmission power to maintain power consistency and phase continuity between the DMRS. Once the base station receives the bundled DMRS, the base station can perform joint channel estimation (e.g., by identifying the average RSRP of the DMRS in slot 704 within each DMRS bundling window).

[0081] Furthermore, each DCI that schedules one or more different PUSCH transports may include a specific DCI format indicating which DMRSs in these different transport blocks should be bundled. The specific DCI format indicating DMRS bundling may differ from other DCI formats that do not indicate DMRS bundling (e.g., DCI formats 0_0, 0_1, 1_0, 1_1, 2_0, 2_1, 2_2, and 2_3). For example, the DCI format indicating DMRS bundling may include an NBI (e.g., NBI 726), which the UE can identify to determine the DMRS bundling window.

[0082] Furthermore, to configure a specific UE to perform DMRS bundling in response to a DCI, the base station can assign a Bundling Indication Radio Network Temporary Identifier (BI-RNTI) to that UE. The BI-RNTI can be UE-specific or group-specific (associated with a group of UEs including that UE). When the base station subsequently configures the DCI to enable that specific UE to perform DMRS bundling in one or more scheduled PUSCH transmissions, the base station can append a Cyclic Redundancy Check (CRC) to the DCI scrambled with the UE's BI-RNTI. When the UE receives the DCI for the scheduled PUSCH transmission(s), the UE can decode the DCI including the CRC to identify the BI-RNTI, and if the decoded BI-RNTI matches the UE's BI-RNTI, the UE can determine that the base station will configure the UE to bundle DMRS in that scheduled transmission(s). As a result, the UE can determine the DMRS bundling window (e.g., DMRS bundling window 614 or 728), and the UE can bundle the DMRS in time slots 604 and 704 within each window by transmitting the DMRS in each of the time slots 604 and 704 with the same MCS, the same TDD or FDD duplex scheme, in consecutive time domain resources, or with the same transmission power to maintain power consistency and phase continuity among the DMRS. Once the base station receives the bundled DMRS, the base station can perform joint channel estimation (e.g., by identifying the average RSRP of the DMRS in time slots 604 and 704 within each DMRS bundling window).

[0083] In the fourth example, the UE can be scheduled to transmit different transport blocks of uplink data in a PUSCH of a certain number of symbols after receiving the DCI. This number of symbols can represent the PUSCH preparation time T. proc,2 , among which, T proc,2 The preparation time N2 and the time d are the PUSCH preparation time. 2,1 The function, where N2 is based on the parameter set μ of UE processing capability 1, where μ and (μ DL ,μ UL This leads to having the maximum T. proc,2 One (μ) DL ,μ UL The smaller value between them or the subcarrier spacing (SCS) corresponds to, where, μ DL The subcarrier spacing corresponding to the DCI carrying the scheduling PUSCH is transmitted, and μ ULThis corresponds to the subcarrier spacing of the PUSCH to be transmitted. For example, depending on whether the smaller SCS between the SCS associated with DCI and the SCS associated with uplink data transmission is 15kHz (μ=0), 30kHz (μ=1), 60kHz (μ=2), or 120kHz (μ=3), the preparation time N2 for UE processing capability 1 can be 10, 12, 23, or 36 symbols. Furthermore, the PUSCH preparation process time T... proc,2 The number of symbols assumes that the first symbol assigned by PUSCH consists only of DMRS (d 2,1 =0). Therefore, the UE can determine a preparation time gap of at least 10, 12, 23, or 36 symbols between the reception of the DCI and the first DMRS to be transmitted in the PUSCH.

[0084] In addition, the UE can determine the DMRS bundling window during the PUSCH preparation process time T. proc,2 Then, an additional number of symbols begins. This additional number of symbols can represent the additional time gap d between receiving the DCI and transmitting uplink data on the PUSCH. Therefore, the start time of the DMRS bundling window can be related to T, which is scheduled to be transmitted after receiving the DCI. proc,2 The initial PUSCH transmission (e.g., the initial transport block) with +d symbols transmitted corresponds to the end time of the DMRS bundling window, while the end time of the DMRS bundling window can correspond to the last PUSCH transmission (e.g., the final transport block) scheduled for transmission via DCI. As in the previous example, when DMRSs are bundled within the DMRS bundling window, the UE maintains power consistency and phase continuity among DMRSs in adjacent PUSCH transmissions. In contrast, for DMRSs not within the DMRS bundling window (e.g., DMRS transmitted during the additional time gap d), the UE does not actively seek to maintain power consistency and phase continuity among these DMRSs because these DMRSs are not bundled.

[0085] The additional time gap d can be an element of a set of durations (e.g., d ∈ {0, 1, 2} symbols or a set of some other number of symbols), which the UE can determine based on the SCS. For example, similar to calculating T... proc,2 In this case, the UE can determine the smaller SCS between the SCS associated with DCI and the SCS associated with PUSCH transmission, and identify the additional time gap d as 0, 1 or 2 symbols depending on the value of the smaller SCS.

[0086] Furthermore, the UE can report the additional time slot d that it determines to apply to its PUSCH transmissions as a UE capability. For example, when the base station sends a UE capability query message to the UE during initial access or at some other time, the UE can report to the base station in a capability information message the additional time slot d that it has selected based on the SCS (and is therefore able to apply DMRS bundling). For example, the UE can report to the base station that it can apply additional time slots d∈{0,1,2} symbols between the start of the DCI reception and DMRS bundling window. Therefore, when the UE transmits its uplink data on the PUSCH according to the determined additional time slot d, the base station can monitor the PUSCH transmissions accordingly based on the capability information message. For example, the base station can determine that, depending on the value of d indicated in the capability information message, the bundled DMRS will be in T proc,2 The next 0, 1, or 2 symbols are received.

[0087] For example, Figure 8 Example 800 of time slot 802 is shown, each time slot including DMRS 804 and uplink data scheduled by the UE to be transmitted on PUSCH 806 in DCI 808. Time slot 802 can be... Figure 4B It corresponds to time slot 452 in the code, and DMRS804 can be used with... Figure 4B The bundled DMRS 454 corresponds to this. The base station can schedule the UE to transmit uplink data on the PUSCH in different transport blocks via DCI 808. When the UE receives DCI 808, the UE can determine the DMRS bundling window 810, whose start time is scheduled to be in the PUSCH preparation time 812 (T) of the configured PUSCH transmission. proc,2 The additional time slot 814(d) corresponds to a PUSCH transmission that occurs after the additional time slot 814(d). The additional time slot 814 can be determined based on the smaller SCS between the SCS 816 associated with DCI 808 and the SCS 818 associated with time slot 802, which includes the PUSCH transmission. The end time of the DMRS bundling window can correspond to the last of the configured PUSCH transmissions scheduled in DCI 808. After the DMRS bundling window is determined, the UE can bundle DMRS 804 in time slot 802 within the window by transmitting DMRS in each consecutive or adjacent time slot with the same MCS, the same TDD or FDD duplex scheme, in consecutive time domain resources, or with the same transmission power to maintain power consistency and phase continuity between DMRS. Once the base station receives the bundled DMRS, the base station can perform joint channel estimation (e.g., by identifying the average RSRP of DMRS 804 in time slot 802 within the DMRS bundling window 810).

[0088] Furthermore, the base station can provide the UE with a configuration for the DMRS bundling window, including the window size or duration and the start time or time slot of the window. This configuration can define the size or duration of the DMRS bundling window as the number of symbols including uplink and downlink symbols, the number of time slots including uplink and downlink time slots, the number of subframes, the number of frames, or the amount of time. Therefore, the DMRS bundling window can be defined based on the total number of symbols, time slots, subframes, frames, milliseconds, or some other time representation. For example, if the UE is scheduled to transmit different PUSCH transmissions in a sequence of ten time slots with the format: DDDUUDDDUU (where D represents a downlink time slot and U represents an uplink time slot), the configuration can explicitly indicate that the size of the DMRS bundling window is ten time slots, ten subframes (assuming 15kHz SCS), one frame, or 10 milliseconds. Therefore, the UE can determine the DMRS bundling window as ten time slots (or ten subframes, one frame, 10ms, etc.) based on this configuration, even though the UE can actually only bundle DMRS in four of the ten time slots (uplink time slots).

[0089] The UE can indicate its capability to support DMRS bundling window sizes. For example, when the base station sends a UE capability query message to the UE during initial access or at some other time, the UE can report to the base station in a capability information message that it can perform DMRS bundling (e.g., maintaining power consistency and phase continuity) within a specified number of time slots, symbols, subframes, frames, or time quantities. Supported DMRS bundling window sizes (e.g., the specified number of time slots, symbols, or time quantities) can include uplink and downlink time slots, uplink and downlink symbols, or uplink and downlink transmission times. For example, the UE can inform the base station that it can transmit DMRS in different PUSCH transmissions within a DMRS bundling window of ten time slots (including downlink time slots) with the same MCS, the same TDD or FDD duplex scheme, in contiguous time domain resources, or with the same transmission power. Therefore, the base station can explicitly configure the DMRS bundling window based on the UE's capabilities.

[0090] Figure 9 An example of call flow 900 between UE 902 and base station 904 is shown. The UE may transmit a capability information message 906 to the base station. The capability information message may indicate the capability of a supported DMRS bundling window size. The capability information message may include an additional time gap d, which determines the start time of the DMRS bundling window, and the UE may apply this additional time gap d between receiving DCI and transmitting uplink data on PUSCH. The capability information message may be transmitted in response to a capability information query from the base station (e.g., during initial access). For example, refer to the fourth example above and Figure 8The UE can report that it has determined an additional time slot 814 for its PUSCH transmission applications as a UE capability. For example, the UE can report to the base station in a capability information message that the UE has selected and is therefore capable of applying additional time slot d for DMRS bundled applications based on SCS 816, 818.

[0091] Base station 904 may provide DMRS bundling configuration 908 to UE 902. For example, referring to the first example above, DMRS bundling configuration 908 may be a configuration that instructs the UE to perform DMRS bundling across dynamically scheduled PUSCH transmissions carrying different transport blocks for joint channel estimation, or a configuration that enables the UE to perform DMRS bundling across dynamically scheduled PUSCH transmissions carrying different transport blocks for joint channel estimation. This configuration may be provided within a PUSCH configuration (e.g., PUSCH-Config). Alternatively, DMRS bundling configuration 908 may be separate from the PUSCH configuration. DMRS bundling configuration 908 may also define the size or duration of the DMRS bundling window as the number of symbols including uplink and downlink symbols, the number of time slots including uplink and downlink time slots, the number of subframes, the number of frames, or the amount of time.

[0092] In another example, the DMRS bundling configuration 908 can be DCI 910 (or included therein). For example, referring to the second example above, DCI 910 can indicate a DMRS bundling window, including a start slot and an end slot or duration, in which the DMRS scheduled by the DCI for PUSCH transmissions are bundled for joint channel estimation. For example, DCI 910 (the DMRS bundling configuration in this example) can indicate a set of subsequent slots in which the UE will transmit different uplink data along with the bundled DMRS, as described above regarding... Figure 6 Alternatively, referring to the third example above, DCI910 may be one of multiple DCIs provided to the UE, each DCI scheduling different PUSCH transmissions in a corresponding transport block. In such a case, each DCI may include an NBI bit that the base station can configure to indicate the DMRS bundling window (DMRS bundling configuration in this example), as described above regarding... Figure 7 The DCI910, which schedules one or more of the different PUSCH transmissions, may include a specific DCI format indicating which DMRS in these different transmission blocks should be bundled. For example, the DCI format indicating DMRS bundling may include NBI. Furthermore, a CRC may be appended to the DCI scrambled by the UE's BI-RNTI.

[0093] After receiving DMRS bundling configuration 908 and DCI 910 from base station 904, at 912, UE 902 determines the DMRS bundling window based on the DMRS bundling configuration. For example, referring to the first example above, after the base station provides the DMRS bundling configuration instructing the UE to perform DMRS bundling across dynamically scheduled PUSCH transports carrying different transport blocks, the UE can determine that the DMRS bundling window includes dynamically scheduled PUSCH transports in one or more DCIs (e.g., DCI 910). In another example, referring to the second example above and Figure 6 The UE can determine the DMRS bundling window to correspond to a set of subsequent time slots in which the UE intends to transmit different uplink data, as indicated in the DCI. For example, refer to Figure 6 The UE can determine that the DMRS bundling window 614 contains the first PUSCH transmission 606 and the second PUSCH transmission 610 (slots n+k and n+k+1) scheduled by the DCI 602. In another example, refer to the third example above and Figure 7 The UE can determine the boundaries of the DMRS bundling window based on the NBI in multiple DCIs (including DCI 910). For example, refer to Figure 7 The UE can determine that the first DMRS bundling window 728 corresponds to the first PUSCH transmission 706 and the second PUSCH transmission 710, and the second DMRS bundling window 728 corresponds to the third PUSCH transmission 714, the fourth PUSCH transmission 718, and the fifth PUSCH transmission 722. The UE can also determine the DMRS bundling window in response to decoding the BI-RNTI in the CRC appended to the DCI. In another example, refer to the fourth example above and... Figure 8 The UE can determine the DMRS binding window during the PUSCH preparation process time T. proc,2 Then, an additional number of symbols are added. Therefore, the UE can determine the start time of the DMRS bundling window and the time scheduled to be received after T... proc,2 The initial PUSCH transmission (e.g., a transport block) with +d symbols transmitted corresponds to the initial PUSCH transmission (e.g., a transport block), while the end time of the DMRS bundling window can correspond to the last PUSCH transmission (e.g., a transport block) scheduled via DCI. For example, the UE can determine DMRS bundling window 810, whose start time corresponds to the time scheduled for PUSCH preparation time 812 (T proc,2This corresponds to the initial PUSCH transmission that occurs after the additional time gap 814(d). When DMRSs are bundled within the DMRS bundling window, the UE maintains power consistency and phase continuity among DMRSs in adjacent PUSCH transmissions. In contrast, for DMRSs not within the DMRS bundling window, the UE does not actively seek to maintain power consistency and phase continuity among these DMRSs because these DMRSs are not bundled.

[0094] At 914, the UE can determine the time gap between the start time of the DCI and DMRS bundling window. This time gap (e.g., the additional time gap d) can be an element of a set of durations (e.g., d ∈ {0, 1, 2} symbols or a set of some other number of symbols), which the UE can determine based on the SCS. For example, similar to calculating T. proc,2 In this case, the UE can determine the smaller SCS between the SCS associated with DCI and the SCS associated with PUSCH transmission, and identify the additional time gap d as 0, 1, or 2 symbols depending on the value of the smaller SCS. For example, refer to the description above and regarding... Figure 8 In the fourth example, after the UE receives DCI 910, the UE can determine the additional time slot 814 based on the smaller SCS between the SCS 816 associated with DCI 808 and the SCS 818 associated with time slot 802 which includes PUSCH transmission.

[0095] After determining the DMRS bundling window at 912 and optionally the time slot at 914, UE 902 can bundle DMRSs in the time slots of dynamically scheduled PUSCH transport blocks. For example, at 915, the UE can maintain power consistency and phase continuity between DMRSs. For example, refer to... Figure 6 and Figure 7 The UE can bundle DMRSs in time slots 604 and 704 within DMRS bundling windows 614 and 728 to maintain power consistency and phase continuity between DMRSs, by transmitting DMRSs in the same MCS, the same TDD or FDD duplex scheme, in consecutive time domain resources, or with the same transmission power in each consecutive or adjacent time slots. The UE 902 can then transmit uplink data 916, including the bundled DMRSs, on the PUSCH in different transport blocks.

[0096] Once base station 904 receives the bundled DMRS, at 918, the base station can perform joint channel estimation based on the bundled DMRS. For example, refer to Figure 6 and 7The base station can perform joint channel estimation (e.g., by identifying the average RSRP of DMRS 608, 612, 708, 712, 716, 720, and 724 in slots 604 and 704 within the DMRS bundling windows 614 and 728).

[0097] Figure 10 This is a flowchart 1000 of a wireless communication method. This method can be performed by a UE (e.g., UE 104, 350, 902; device 1202). Optional aspects are shown in dashed lines. This method allows the UE to perform DMRS bundling in different transport blocks of uplink data on the PUSCH in response to an instruction from a base station (e.g., base station 102 / 180, 310, 904) to perform DMRS bundling or a configuration enabling the UE to perform DMRS bundling.

[0098] At point 1002, the UE receives from the base station an indication to bundle DMRS in different uplink data channel transmissions for joint channel estimation. For example, 1002 can be performed by configuration component 1240. For example, refer to... Figure 9 UE 902 can receive DMRS bundling configuration 908 from base station 904. In one example, refer to... Figure 6-9 The DMRS bundling configuration 908 can be a configuration that instructs UE 902 to perform DMRS bundling for joint channel estimation across dynamically scheduled PUSCH transmissions carrying different transport blocks (e.g., PUSCH transmissions 606, 706, 806), or a configuration that enables UE 902 to perform DMRS bundling for joint channel estimation across dynamically scheduled PUSCH transmissions carrying different transport blocks (e.g., PUSCH transmissions 606, 706, 806). This configuration can be received in the PUSCH configuration, and different uplink data channel transmissions can be scheduled in the DCI. For example, refer to... Figure 6-9A DMRS bundling configuration 908 can be provided within a PUSCH configuration (e.g., PUSCH-Config), and PUSCH transmissions (e.g., PUSCH transmissions 606, 706, 806) can be scheduled in one or more DCIs 910 (e.g., DCIs 602, 702, 808). This configuration can indicate the duration of the DMRS bundling window as the number of symbols including uplink and downlink symbols, the number of slots including uplink and downlink time slots, the number of subframes, the number of frames, or the amount of time. This configuration can also be received in response to a capability information message indicating the supported duration of the DMRS bundling window. For example, when the base station sends a UE capability query message to the UE during initial access or at some other time, the UE can report to the base station in the capability information message that the UE is capable of performing DMRS bundling (maintaining power consistency and phase continuity) in a specified number of slots, symbols, subframes, frames, or the amount of time, and the base station can explicitly configure the DMRS bundling window according to the UE's capabilities.

[0099] In another example, the configuration may include a DCI that indicates the DMRS binding window. For example, refer to Figure 6 , 7 And 9, DMRS bundling configuration 908 can be in the form of DCI 910, where, in such an example, DCI 910 (e.g., DCI 602, 702) indicates the DMRS bundling window (e.g., DMRS bundling window 614, 728). In one example, the DMRS bundling window can be indicated by multiple time slots in which DMRS are to be bundled. For example, refer to Figure 6 and 9 DCI 910 (e.g., DCI 602) may indicate a DMRS bundling window 614, including a start time slot (e.g., time slot 604 including the first PUSCH transmission 606) and an end time slot or duration (e.g., time slot 604 including the second PUSCH transmission 610), in which DMRS 608, 612 of the scheduled PUSCH transmissions of the DCI are to be bundled for joint channel estimation. In another example, the DCI may include an NBI, where the NBI indicates the DMRS bundling window. For example, see Reference Figure 7 and 9DCI 910 can be one of multiple DCIs provided to UE 902 (e.g., DCI 702), each DCI scheduling different PUSCH transmissions in a corresponding transport block (e.g., PUSCH transmissions 706, 710, 714, 718, 722). In such a case, DCI 702 can each include an NBI bit (e.g., NBI 726) that the base station can configure to indicate the DMRS bundling window 728. Additionally, the DCI can include a DCI format associated with BI-RNTI. For example, see reference... Figure 7 and 9 DCI 910 (e.g., DCI 702), which schedules one of the different PUSCH transmissions (e.g., PUSCH transmissions 706, 710, 714, 718, 722), may include a specific DCI format containing an NBI, and a CRC may be appended to the DCI scrambled by the BI-RNTI of UE 902. The BI-RNTI may be UE-specific or group-specific.

[0100] At point 1004, the UE determines the DMRS bundling window based on its configuration. For example, point 1004 can be performed by the bundling window component 1242. For example, refer to... Figure 9 At 912, UE 902 can determine the DMRS bundling window based on the DMRS bundling configuration 908 received from base station 904. As an example, the UE can determine the DMRS bundling window from multiple time slots in the DCI in which the UE wants to bundle DMRS. For example, refer to... Figure 6 The UE can determine that the DMRS bundling window 614 contains the first PUSCH transmission 606 and the second PUSCH transmission 610 (slots n+k and n+k+1) scheduled by the DCI 602.

[0101] In another example of 1004, at 1006, the UE can determine the start time of the DMRS bundling window where the NBI in response to the first DCI switches to a first value, and the end time of the DMRS bundling window where the NBI in response to the second DCI switches to a second value different from the first value. For example, 1006 can be performed by the bundling window component 1242. For example, refer to... Figure 7 and Figure 9 UE 902 can determine the start time 730 and stop time 732 of the DMRS bundling window 728 based on the NBI 726 of each DCI 702. For example, the UE can determine Figure 7The second DMRS bundling window 728 shown begins in response to a switch (from 0 to 1) of NBI 726 in DCI 702 scheduling the second PUSCH transmission 710 and the third PUSCH transmission 714, and ends in response to another switch (from 1 to 0) of NBI in subsequent DCIs following DCI 702 scheduling the fifth PUSCH transmission 722. Therefore, the UE can determine that DMRS bundling window 728 corresponds to the third PUSCH transmission 714, the fourth PUSCH transmission 718, and the fifth PUSCH transmission 722.

[0102] At point 1008, the UE can determine the time gap between the start time of the DCI and DMRS binding window. For example, 1008 can be performed by time gap component 1244. For example, refer to... Figure 8 and Figure 9 At 914, UE 902 can determine the time interval between the start time of receiving DCI 808, 910 and the DMRS bundling window 810 (e.g., T). proc,2 +d). This time gap can include preparation time for different uplink data channel transmissions (e.g., PUSCH preparation time 812 or T). proc,2 ) and additional time gaps (e.g., additional time gap 814 or d). These additional time gaps can be based on the minimum SCS between the first SCS of the DCI and the second SCS of different uplink data channel transmissions. For example, refer to Figure 8 and 9 After UE 902 receives DCI 808 and 910, UE can determine additional time slot 814 based on the smaller SCS between SCS 816 associated with DCI 808 and 910 and SCS 818 associated with time slot 802 which includes different PUSCH transmissions (e.g., different transport blocks carried in PUSCH 806).

[0103] At point 1010, the UE can report additional time slots to the base station in the capability information message. For example, point 1010 can be performed by capability information component 1246. For example, refer to... Figure 8 and 9 UE 902 may transmit a capability information message 906 to base station 904, which includes the UE determining additional time slots 814 for its PUSCH transmission applications.

[0104] At point 1009, the UE can maintain power consistency between the bundled DMRSs. For example, 1009 can be performed by the bundled DMRS component 1248. Similarly, at point 1011, the UE can maintain phase continuity between the bundled DMRSs. For example, 1011 can be performed by the bundled DMRS component 1248. For example, refer to... Figure 9 At 915, UE 902 can maintain power consistency and phase continuity between DMRSs. The UE can maintain power consistency, for example, by applying the same transmission power to the DMRSs in the DMRS bundle window, and the UE can maintain phase continuity, for example, by applying the same MCS, the same TDD or FDD scheme, or by allocating continuous time domain resources to the DMRSs in the DMRS bundle window.

[0105] Finally, at 1012, the UE transmits the bundled DMRS within the DMRS bundling window. For example, 1012 can be performed by the bundled DMRS component 1248. For example, refer to... Figure 6-9 UE 902 can transmit uplink data 916 on the PUSCH, including bundled DMRS (e.g., DMRS 608, 612, 708, 712, 716, 720, 724, 804), in different transport blocks (e.g., data transmission in PUSCH 606, 610, 706, 710, 714, 718, 722, or PUSCH 806). Reference Figure 6-8 The UE can maintain power consistency and phase continuity between DMRS 608, 612, 708, 712, 716, 720, 724, and 804 in time slots 604, 704, and 802 within the DMRS bundling windows 614, 728, and 810 by transmitting DMRS in the same MCS, the same TDD or FDD duplex scheme, in consecutive time domain resources, or with the same transmission power in each consecutive or adjacent time slots.

[0106] Figure 11 This is a flowchart 1100 of a wireless communication method. This method can be performed by a base station (e.g., base station 102 / 180, 310, 904; device 1302). Optional aspects are shown in dashed lines. This method allows the base station to configure a UE (e.g., UE 104, 350, 902) to perform DMRS bundling in different transport blocks of uplink data on the PUSCH, enabling the base station to perform joint channel estimation.

[0107] At 1102, the base station transmits to the UE a configuration indicating the bundling of DMRS in different uplink data channel transmissions for joint channel estimation. For example, 1102 can be performed by configuration component 1340. For example, refer to... Figure 9 Base station 904 can transmit DMRS bundling configuration 908 to UE 902. In one example, refer to... Figure 6-9The DMRS bundling configuration 908 can be a configuration that instructs UE 902 to perform DMRS bundling for joint channel estimation across dynamically scheduled PUSCH transmissions carrying different transport blocks (e.g., PUSCH transmissions 606, 706, 806), or a configuration that enables UE 902 to perform DMRS bundling for joint channel estimation across dynamically scheduled PUSCH transmissions carrying different transport blocks (e.g., PUSCH transmissions 606, 706, 806). This configuration can be transmitted in the PUSCH configuration, and different uplink data channel transmissions can be scheduled in the DCI. For example, refer to... Figure 6-9 The DMRS bundling configuration 908 can be provided within a PUSCH configuration (e.g., PUSCH-Config), and PUSCH transmissions (e.g., PUSCH transmissions 606, 706, 806) can be scheduled in one or more DCIs 910 (e.g., DCIs 602, 702, 808). This configuration can indicate the duration of the DMRS bundling window as the number of symbols including uplink and downlink symbols, the number of slots including uplink and downlink time slots, the number of subframes, the number of frames, or the amount of time. This configuration can respond to a capability information message indicating the supported duration of the DMRS bundling window. For example, when the base station sends a UE capability query message to the UE during initial access or at some other time, the UE can report to the base station in the capability information message that the UE is capable of performing DMRS bundling (maintaining power consistency and phase continuity) in a specified number of slots, symbols, subframes, frames, or the amount of time, and the base station can explicitly configure the DMRS bundling window according to the UE's capabilities.

[0108] In another example, the configuration may include a DCI that indicates the DMRS binding window. For example, refer to Figure 6 , 7 And 9, DMRS bundling configuration 908 can be in the form of DCI 910, where, in such an example, DCI 910 (e.g., DCI 602, 702) indicates the DMRS bundling window (e.g., DMRS bundling window 614, 728). In one example, the DMRS bundling window can be indicated by multiple time slots in which DMRS are to be bundled. For example, refer to Figure 6 and 9DCI 910 (e.g., DCI 602) may indicate a DMRS bundling window 614, including a start time slot (e.g., time slot 604 including the first PUSCH transmission 606) and an end time slot or duration (e.g., time slot 604 including the second PUSCH transmission 610), in which DMRS 608, 612 of the scheduled PUSCH transmissions of the DCI are to be bundled for joint channel estimation. In another example, the DCI may include an NBI, where the NBI indicates the DMRS bundling window. For example, see Reference Figure 7 and 9 DCI 910 can be one of multiple DCIs provided to UE 902 (e.g., DCI 702), each DCI scheduling different PUSCH transmissions in a corresponding transport block (e.g., PUSCH transmissions 706, 710, 714, 718, 722). In such a case, DCI 702 can each include an NBI bit (e.g., NBI 726) that the base station can configure to indicate the DMRS bundling window 728. Additionally, the DCI can include a DCI format associated with BI-RNTI. For example, see reference... Figure 7 and 9 DCI 910 (e.g., DCI 702), which schedules one of the different PUSCH transmissions (e.g., PUSCH transmissions 706, 710, 714, 718, 722), may include a specific DCI format containing an NBI, and a CRC may be appended to the DCI scrambled by the BI-RNTI of UE 902. The BI-RNTI may be UE-specific or group-specific.

[0109] At 1104, the base station receives the bundled DMRS within the DMRS bundling window based on this configuration. For example, 1104 can be performed by the bundled DMRS component 1342. Power consistency can be maintained between the bundled DMRSs. Similarly, phase continuity can be maintained between the bundled DMRSs. For example, the DMRSs can have the same MCS, the same TDD or FDD scheme, the same allocation of continuous time-domain resources for phase continuity, or the same transmission power for power consistency. For example, refer to... Figure 6-9 In response to transmitting DMRS bundling configuration 908 to UE 902, the base station can receive uplink data 916 on the PUSCH including bundled DMRS (e.g., DMRS 608, 612, 708, 712, 716, 720, 724, 804) in different transport blocks (e.g., transmission of data in PUSCH transmissions 606, 610, 706, 710, 714, 718, 722, or PUSCH 806). (See reference) Figure 6-8The UE can maintain power consistency and phase continuity between DMRS 608, 612, 708, 712, 716, 720, 724, and 804 in time slots 604, 704, and 802 within the DMRS bundling windows 614, 728, and 810 by transmitting DMRS in the same MCS, the same TDD or FDD duplex scheme, in consecutive time domain resources, or with the same transmission power in each consecutive or adjacent time slots.

[0110] In one example, as described above, the DMRS bundling window can be indicated in the DCI by the multiple time slots in which the UE wants to bundle the DMRS. For example, refer to Figure 6 The DMRS bundling window 614 may include a first PUSCH transmission 606 and a second PUSCH transmission 610 (slots n+k and n+k+1) scheduled by DCI 602. In another example, as described above, the DCI may include an NBI. In such an example, the start time of the DMRS bundling window may respond to the NBI of the first DCI switching to a first value and the end time of the DMRS bundling window may respond to the NBI of the second DCI switching to a second value different from the first value. For example, refer to... Figure 7 and 9 The start time 730 and stop time 732 of the DMRS bundle window 728 can be based on the NBI 726 of each DCI 702. For example, as Figure 7 As shown, the second DMRS bundle window 728 begins in response to the switching (from 0 to 1) of NBI 726 in DCI 702, which schedules the second PUSCH transmission 710 and the third PUSCH transmission 714, and ends in response to another switching (from 1 to 0) of NBI in subsequent DCIs after DCI 702, which schedules the fifth PUSCH transmission 722. Therefore, the DMRS bundle window 728 can correspond to the third PUSCH transmission 714, the fourth PUSCH transmission 718, and the fifth PUSCH transmission 722.

[0111] In another example, the bundled DMRS can be received after the time gap between the start time of the DCI and DMRS bundling window. For example, refer to Figure 8 and 9 At 914, UE 902 can determine the time gap (e.g., T) between the start time of receiving DCI 808, 910 and the start time of DMRS binding window 810. proc,2 +d). This time gap can include preparation time for different uplink data channel transmissions (e.g., PUSCH preparation time 812 or T). proc,2) and additional time gaps (e.g., additional time gap 814 or d). The additional time gap can be based on the minimum SCS between the first SCS of the DCI and the second SCS of the different uplink data channel transmissions. For example, refer to Figure 8 and 9 After UE 902 receives DCI 808 and 910, UE can determine additional time slot 814 based on the smaller SCS between SCS 816 associated with DCI 808 and 910 and SCS 818 associated with time slot 802 which includes different PUSCH transmissions (e.g., different transport blocks carried in PUSCH 806).

[0112] At point 1106, the base station may receive an additional time slot from the UE in the capability information message. For example, 1106 may be performed by the additional time slot component 1344. For example, refer to... Figure 8 and 9 UE 902 can transmit capability information message 906 to base station 904, which includes additional time slots 814 that the UE determines to apply for its PUSCH transmission.

[0113] Finally, at 1108, the base station performs joint channel estimation based on the bundled DMRS. For example, 1108 can be performed by the joint channel estimation component 1346. For example, refer to... Figure 9 Once base station 904 receives the bundled DMRS, at 918, the base station can perform joint channel estimation based on the bundled DMRS. For example, refer to... Figure 6-8 The base station can perform joint channel estimation by identifying the average RSRP of DMRS 608, 612, 708, 712, 716, 720, 724, and 804 in time slots 604, 704, and 802 within the DMRS bundling window 614, 728, and 810, and determining the CQI associated with the channel based on the identified average RSRP.

[0114] Figure 12Figure 1200 illustrates an example of a hardware implementation of device 1202. Device 1202 is a UE and includes a cellular baseband processor 1204 (also referred to as a modem) coupled to a cellular RF transceiver 1222 and one or more Subscriber Identity Module (SIM) cards 1220, an application processor 1206 coupled to a Secure Digital (SD) card 1208 and a screen 1210, a Bluetooth module 1212, a Wireless Local Area Network (WLAN) module 1214, a Global Positioning System (GPS) module 1216, and a power supply 1218. The cellular baseband processor 1204 communicates with the UE 104 and / or BS 102 / 180 via the cellular RF transceiver 1222. The cellular baseband processor 1204 may include computer-readable media / memory. The computer-readable media / memory may be non-transitory. The cellular baseband processor 1204 is responsible for general processing, including executing software stored on the computer-readable media / memory. When executed by the cellular baseband processor 1204, the software causes the cellular baseband processor 1204 to perform the various functions described above. The computer-readable medium / memory can also be used to store data manipulated by the cellular baseband processor 1204 during software execution. The cellular baseband processor 1204 also includes a receiving component 1230, a communication manager 1232, and a transmission component 1234. The communication manager 1232 includes one or more of the components shown. The components within the communication manager 1232 can be stored in a computer-readable medium / memory and / or configured as hardware within the cellular baseband processor 1204. The cellular baseband processor 1204 can be a component of the UE 350 and can include a memory 360 and / or at least one of a TX processor 368, an RX processor 356, and a controller / processor 359. In one configuration, the device 1202 can be a modem chip and only include the baseband processor 1204, and in another configuration, the device 1202 can be the entire UE (e.g., see...). Figure 3 (350) and includes the aforementioned additional module of device 1202.

[0115] Communication manager 1232 includes configuration component 1240, which is configured to receive from a base station a configuration indicating the bundling of DMRS in different uplink data channel transmissions for joint channel estimation, for example, as described in conjunction with 1002. Communication manager 1232 also includes bundling window component 1242, which receives input in the form of a configuration from configuration component 1240 and is configured to determine a DMRS bundling window based on that configuration, for example, as described in conjunction with 1004. For example, the bundling window component may be configured to determine the start time of the DMRS bundling window when the NBI of a first DCI switches to a first value and the end time of the DMRS bundling window when the NBI of a second DCI switches to a second value different from the first value, for example, as described in conjunction with 1006. The communication manager 1232 also includes a time-slot component 1244, which receives configuration-form input from the configuration component 1240 and is configured to determine a time slot between the start time of the DCI and DMRS bundling window, wherein the time slot includes preparation time and additional time slots for different uplink data channel transmissions, for example, as described in conjunction with 1008. The communication manager 1232 also includes a capability information component 1246, which receives time-slot-form input from the time-slot component 1244 and is configured to report additional time slots to the base station in a capability information message, for example, as described in conjunction with 1010. The communication manager 1232 also includes a bundled DMRS component 1248, which receives DMRS bundling window-form input from the bundling window component 1242 and is configured to transmit bundled DMRS within the DMRS bundling window, for example, as described in conjunction with 1012. The bundled DMRS component 1248 can also be configured to maintain power consistency between the bundled DMRSs, for example, as described in conjunction with 1009, and to maintain phase continuity between the bundled DMRSs, for example, as described in conjunction with 1011.

[0116] The device may include execution Figure 10 The above flowchart describes the additional components of each block of the algorithm. Therefore, Figure 10 Each block in the flowchart above can be executed by a component, and the apparatus can include one or more of these components. The component can be one or more hardware components specifically configured to execute the process / algorithm, implemented by a processor configured to execute the process / algorithm, stored in a computer-readable medium for processor implementation, or some combination thereof.

[0117] In one configuration, apparatus 1202, and in particular cellular baseband processor 1204, includes components for receiving from a base station a configuration indicating the bundling of DMRS in different uplink data channel transmissions for joint channel estimation; components for determining a DMRS bundling window based on the configuration; and components for transmitting the bundled DMRS within the DMRS bundling window.

[0118] In one configuration, the component for determining may also be configured to determine the start time of the DMRS bundling window when the NBI of the first DCI switches to a first value and the end time of the DMRS bundling window when the NBI of the second DCI switches to a second value different from the first value.

[0119] In one configuration, the component used for determination can also be configured to determine a time gap between the start time of the DCI and DMRS bundling window, wherein the time gap includes preparation time and additional time gap for different uplink data channel transmissions.

[0120] In one configuration, device 1202, and in particular cellular baseband processor 1204, may include components for reporting additional time gaps to the base station in a capability information message.

[0121] In one configuration, device 1202, and in particular cellular baseband processor 1204, may include components for maintaining power consistency between bundled DMRS and components for maintaining phase continuity between bundled DMRS.

[0122] The aforementioned components may be one or more of the aforementioned components of the device 1202 configured to perform the functions described therein. As described above, the device 1202 may include a TX processor 368, an RX processor 356, and a controller / processor 359. Therefore, in one configuration, the aforementioned components may be the TX processor 368, the RX processor 356, and the controller / processor 359 configured to perform the functions described therein.

[0123] Figure 13Figure 1300 illustrates an example of a hardware implementation of device 1302. Device 1302 is a baseband unit (BS) and includes a baseband unit 1304. The baseband unit 1304 can communicate with the UE 104 via a cellular RF transceiver. The baseband unit 1304 may include a computer-readable medium / memory. The baseband unit 1304 is responsible for general processing, including executing software stored on the computer-readable medium / memory. This software, when executed by the baseband unit 1304, causes the baseband unit 1304 to perform the various functions described above. The computer-readable medium / memory can also be used to store data manipulated by the baseband unit 1304 during software execution. The baseband unit 1304 also includes a receiving component 1330, a communication manager 1332, and a transmitting component 1334. The communication manager 1332 includes one or more of the components shown. The components within the communication manager 1332 may be stored in the computer-readable medium / memory and / or configured as hardware within the baseband unit 1304. The baseband unit 1304 may be a component of the BS 310 and may include at least one of the memory 376 and / or the TX processor 316, the RX processor 370 and the controller / processor 375.

[0124] Communication manager 1332 includes a configuration component 1340 configured to transmit to the UE a configuration indicating that different uplink data channel transmissions (DMRSs) are bundled for joint channel estimation, for example, as described in conjunction with 1102. Communication manager 1332 also includes a bundled DMRS component 1342 that receives input in the form of a configuration from configuration component 1340 and is configured to receive bundled DMRSs in a DMRS bundling window based on that configuration, for example, as described in conjunction with 1104. Communication manager 1332 also includes an additional time slot component 1344 configured to receive additional time slots from the UE in a capability information message, for example, as described in conjunction with 1106. Communication manager 1332 also includes a joint channel estimation component 1346 that receives input in the form of bundled DMRSs from bundled DMRS component 1342 and is configured to perform joint channel estimation based on the bundled DMRSs, for example, as described in conjunction with 1108.

[0125] The device may include execution Figure 11 The above flowchart describes the additional components of each block of the algorithm. Therefore, Figure 11 Each block in the flowchart above can be executed by a component, and the apparatus can include one or more of these components. The component can be one or more hardware components specifically configured to execute the process / algorithm, implemented by a processor configured to execute the process / algorithm, stored in a computer-readable medium for processor implementation, or some combination thereof.

[0126] In one configuration, apparatus 1302, and in particular baseband unit 1304, includes components for transmitting to the UE a configuration indicating that DMRSs in different uplink data channel transmissions are bundled for joint channel estimation; components for receiving bundled DMRSs in a DMRS bundling window based on the configuration; and components for performing joint channel estimation based on the bundled DMRSs.

[0127] In one configuration, the receiving component can also be configured to receive additional time gaps from the UE in a capability information message.

[0128] The aforementioned components may be one or more of the aforementioned components of the device 1302 configured to perform the functions described therein. As described above, the device 1302 may include a TX processor 316, an RX processor 370, and a controller / processor 375. Therefore, in one configuration, the aforementioned components may be the TX processor 316, the RX processor 370, and the controller / processor 375 configured to perform the functions described therein.

[0129] It should be understood that the specific order or hierarchy of boxes in the disclosed process / flowchart is an illustration of the example method. Based on design preferences, it can be understood that the specific order or hierarchy of boxes in the process / flowchart can be rearranged. Furthermore, some boxes may be combined or omitted. The appended method claims present the elements of the various boxes in the example order, but are not intended to limit one to the specific order or hierarchy presented.

[0130] The foregoing description is provided to enable any person skilled in the art to practice the aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Therefore, the claims are not intended to be limited to the aspects shown herein, but are given the full scope consistent with the language of the claims, wherein reference to an element in the singular is not intended to mean “one and only one,” but rather “one or more,” unless specifically stated otherwise. Terms such as “if,” “in,” and “when” should be interpreted as meaning “in the circumstances,” rather than implying an immediate temporal relationship or reaction. That is, these phrases, such as “in,” do not imply an immediate action in response to or during the occurrence of an action, but simply that an action will occur if a condition is met, without requiring a specific or immediate time constraint for the action to occur. The word “exemplary” herein means “serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other aspects. Unless otherwise specifically stated, the term “some” means one or more. Combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" include any combination of A, B, and / or C, and may include multiple A, multiple B, or multiple C. Specifically, combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" may be only A, only B, only C, A and B, A and C, B and C, or A and B and C, wherein any such combination may include one or more members of A, B, or C. All structural and functional equivalents of the elements of the aspects described throughout this disclosure that are known to those skilled in the art or will be learned thereafter are expressly incorporated herein by reference and are intended to be included in the claims. Furthermore, nothing disclosed herein is intended as a donation to the public, whether or not such disclosure is expressly recited in the claims. The terms “module,” “mechanism,” “element,” and “device” are not necessarily substitutes for the term “component.” Therefore, no claim element should be interpreted as a component plus a function unless the element is explicitly stated using the phrase “component for…”.

[0131] The following examples are merely illustrative and may be combined with other embodiments or aspects of the teachings described herein, without limitation.

[0132] Example 1 is a method for wireless communication at a user equipment (UE), comprising: receiving from a base station a configuration indicating demodulation reference signals (DMRS) in bundled uplink data channel transmissions for joint channel estimation; determining a DMRS bundling window based on the configuration; and transmitting the bundled DMRS within the DMRS bundling window.

[0133] Example 2 is the method according to Example 1, wherein the configuration is received in a Physical Uplink Shared Channel (PUSCH) configuration, and wherein different uplink data channel transmissions are scheduled in downlink control information (DCI).

[0134] Example 3 is the method according to Example 1, wherein the configuration includes downlink control information (DCI) indicating the DMRS bundling window.

[0135] Example 4 is the method according to Example 3, wherein the DMRS bundling window is indicated in the DCI by multiple time slots in which the DMRS are to be bundled.

[0136] Example 5 is the method according to Example 3, wherein the DCI includes a DCI format associated with a Bundled Indication Radio Network Temporary Identifier (BI-RNTI).

[0137] Example 6 is the method described according to Example 5, wherein BI-RNTI is UE-specific or group-specific.

[0138] Example 7 is a method according to any one of Examples 3, 5 or 6, wherein the DCI includes a New Bundling Indicator (NBI) and the determination of the DMRS bundling window includes: determining the start time of the DMRS bundling window when the NBI of the first DCI switches to a first value and the end time of the DMRS bundling window when the NBI of the second DCI switches to a second value different from the first value.

[0139] Example 8 is the method according to Example 1, further comprising: determining a time gap between the start time of receiving downlink control information (DCI) and the DMRS bundling window, wherein the time gap includes preparation time and additional time gap for different uplink data channel transmissions.

[0140] Example 9 is the method according to Example 8, wherein the additional time gap is based on the minimum SCS between the first subcarrier spacing (SCS) of the DCI and the second SCS of the different uplink data channel transmissions.

[0141] Example 10 is the method according to Example 8 or 9, further comprising: reporting additional time gaps to the base station in a capability information message.

[0142] Example 11 is an apparatus for wireless communication, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and operable when executed by the processor to cause the apparatus to perform: receiving from a base station a configuration indicating the bundling of demodulation reference signals (DMRS) in different uplink data channel transmissions for joint channel estimation; determining a DMRS bundling window based on the configuration; and transmitting the bundled DMRS within the DMRS bundling window.

[0143] Example 12 is an apparatus according to Example 11, wherein the configuration is received in a Physical Uplink Shared Channel (PUSCH) configuration, and wherein different uplink data channel transmissions are scheduled in downlink control information (DCI).

[0144] Example 13 is an apparatus according to Example 11, wherein the configuration includes downlink control information (DCI) indicating the DMRS bundling window.

[0145] Example 14 is an apparatus according to Example 13, wherein the DMRS bundling window is indicated in the DCI by a plurality of time slots in which the DMRS are to be bundled.

[0146] Example 15 is an apparatus according to Example 13, wherein the DCI includes a DCI format associated with a Bundled Indication Radio Network Temporary Identifier (BI-RNTI).

[0147] Example 16 is an apparatus according to Example 15, wherein BI-RNTI is UE-specific or group-specific.

[0148] Example 17 is an apparatus according to any one of Examples 13, 15, or 16, wherein the DCI includes a New Bundling Instruction (NBI), and wherein, when executed by a processor, the instruction further causes the apparatus to: determine the start time of the DMRS bundling window when the NBI of the first DCI switches to a first value and the end time of the DMRS bundling window when the NBI of the second DCI switches to a second value different from the first value.

[0149] Example 18 is an apparatus according to Example 11, wherein the instruction, when executed by a processor, further causes the apparatus to: determine a time gap between the reception of downlink control information (DCI) and the start time of the DMRS bundling window, wherein the time gap includes preparation time and additional time gap for different uplink data channel transmissions.

[0150] Example 19 is an apparatus according to Example 18, wherein the additional time gap is based on the minimum SCS between the first subcarrier spacing (SCS) of the DCI and the second SCS of the different uplink data channel transmissions.

[0151] Example 20 is an apparatus according to Example 18 or 19, wherein the instruction, when executed by a processor, also causes the apparatus to: report additional time gaps to the base station in a capability information message.

[0152] Example 21 is an apparatus for wireless communication, comprising: components for receiving from a base station a configuration indicating demodulation reference signals (DMRS) bundled in different uplink data channel transmissions for joint channel estimation; components for determining a DMRS bundling window based on the configuration; and components for transmitting the bundled DMRS within the DMRS bundling window.

[0153] Example 22 is an apparatus according to Example 21, wherein the configuration is received in a Physical Uplink Shared Channel (PUSCH) configuration, and wherein different uplink data channel transmissions are scheduled in downlink control information (DCI).

[0154] Example 23 is an apparatus according to Example 21, wherein the configuration includes downlink control information (DCI) indicating the DMRS bundling window.

[0155] Example 24 is an apparatus according to Example 23, wherein the DMRS bundling window is indicated in the DCI by a plurality of time slots in which the DMRS are to be bundled.

[0156] Example 25 is an apparatus according to Example 23, wherein the DCI includes a DCI format associated with a Bundled Indication Radio Network Temporary Identifier (BI-RNTI).

[0157] Example 26 is an apparatus according to Example 25, wherein BI-RNTI is UE-specific or group-specific.

[0158] Example 27 is an apparatus according to any one of Examples 23, 25 or 26, wherein the DCI includes a New Bundling Indicator (NBI), and wherein the component for determining is further configured to determine the start time of the DMRS bundling window when the NBI of the first DCI switches to a first value and the end time of the DMRS bundling window when the NBI of the second DCI switches to a second value different from the first value.

[0159] Example 28 is an apparatus according to Example 21, wherein the determining component is further configured to determine a time gap between the reception of downlink control information (DCI) and the start time of the DMRS bundling window, wherein the time gap includes preparation time and additional time gap for different uplink data channel transmissions.

[0160] Example 29 is an apparatus according to Example 28, wherein the additional time gap is based on the minimum SCS between the first subcarrier spacing (SCS) of the DCI and the second SCS of the different uplink data channel transmissions.

[0161] Example 30 is an apparatus according to Example 28 or 29, further comprising: a component for reporting additional time gaps to a base station in a capability information message.

[0162] Example 31 is a computer-readable medium storing computer-executable code that, when executed by a processor, causes the processor to: receive from a base station a configuration indicating the bundling of demodulation reference signals (DMRS) in different uplink data channel transmissions for joint channel estimation; determine a DMRS bundling window based on the configuration; and transmit the bundled DMRS within the DMRS bundling window.

[0163] Example 32 is a method for wireless communication at a base station, comprising: transmitting to a user equipment (UE) a configuration indicating that demodulation reference signals (DMRS) in bundled uplink data channel transmissions are used for joint channel estimation; receiving bundled DMRS in a DMRS bundling window based on the configuration; and performing joint channel estimation based on the bundled DMRS.

[0164] Example 33 is the method according to Example 32, wherein the configuration is transmitted in a Physical Uplink Shared Channel (PUSCH) configuration, and wherein different uplink data channel transmissions are scheduled in downlink control information (DCI).

[0165] Example 34 is the method according to Example 32, wherein the configuration includes downlink control information (DCI) indicating the DMRS bundling window.

[0166] Example 35 is the method according to Example 34, wherein the DMRS bundling window is indicated in the DCI by multiple time slots in which the DMRS are to be bundled.

[0167] Example 36 is the method according to Example 34, wherein the DCI includes a DCI format associated with a Bundled Indication Radio Network Temporary Identifier (BI-RNTI).

[0168] Example 37 is the method described according to Example 36, wherein BI-RNTI is UE-specific or group-specific.

[0169] Example 38 is the method according to any one of Examples 34, 36 or 37, wherein the DCI includes a New Bundling Indicator (NBI), the DMRS Bundling window starts when the NBI of the first DCI switches to a first value, and the DMRS Bundling window ends when the NBI of the second DCI switches to a second value different from the first value.

[0170] Example 39 is the method according to Example 32, wherein DMRS is received after a time gap between the UE receiving downlink control information (DCI) and the start time of the DMRS bundling window, wherein the time gap includes preparation time and additional time gap for different uplink data channel transmissions.

[0171] Example 40 is the method according to Example 39, wherein the additional time gap is based on the minimum SCS between the first subcarrier spacing (SCS) of the DCI and the second SCS of the different uplink data channel transmissions.

[0172] Example 41 is the method according to Example 39 or 40, further comprising: receiving an additional time gap from the UE in a capability information message.

[0173] Example 42 is an apparatus for wireless communication, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and operable when executed by the processor to cause the apparatus to perform: transmitting to a user equipment (UE) a configuration indicating that demodulation reference signals (DMRS) in bundled uplink data channel transmissions are bundled for joint channel estimation; receiving bundled DMRS in a DMRS bundling window based on the configuration; and performing joint channel estimation based on the bundled DMRS.

[0174] Example 43 is an apparatus according to Example 42, wherein the configuration is transmitted in a Physical Uplink Shared Channel (PUSCH) configuration, and wherein different uplink data channel transmissions are scheduled in downlink control information (DCI).

[0175] Example 44 is an apparatus according to Example 42, wherein the configuration includes downlink control information (DCI) indicating the DMRS bundling window.

[0176] Example 45 is an apparatus according to Example 44, wherein the DMRS bundling window is indicated in the DCI by a plurality of time slots in which the DMRS are to be bundled.

[0177] Example 46 is an apparatus according to Example 44, wherein the DCI includes a DCI format associated with a Bundled Indication Radio Network Temporary Identifier (BI-RNTI).

[0178] Example 47 is an apparatus according to Example 46, wherein BI-RNTI is UE-specific or group-specific.

[0179] Example 48 is an apparatus according to any one of Examples 44, 46 or 47, wherein the DCI includes a New Bundling Indicator (NBI), the DMRS Bundling Window starts when the NBI of the first DCI switches to a first value, and the DMRS Bundling Window ends when the NBI of the second DCI switches to a second value different from the first value.

[0180] Example 49 is an apparatus according to Example 42, wherein DMRS is received after a time gap between the UE receiving downlink control information (DCI) and the start time of the DMRS bundling window, wherein the time gap includes preparation time and additional time gap for different uplink data channel transmissions.

[0181] Example 50 is an apparatus according to Example 49, wherein the additional time gap is based on the minimum SCS between the first subcarrier spacing (SCS) of the DCI and the second SCS of the different uplink data channel transmissions.

[0182] Example 51 is an apparatus according to Example 49 or 50, wherein the instruction, when executed by the processor, also causes the apparatus to: receive an additional time gap from the UE in a capability information message.

[0183] Example 52 is an apparatus for wireless communication, comprising: components for transmitting to a user equipment (UE) a configuration indicating that demodulation reference signals (DMRS) are bundled in different uplink data channel transmissions for joint channel estimation; components for receiving bundled DMRS in a DMRS bundling window based on the configuration; and components for performing joint channel estimation based on the bundled DMRS.

[0184] Example 53 is an apparatus according to Example 52, wherein the configuration is transmitted in a Physical Uplink Shared Channel (PUSCH) configuration, and wherein different uplink data channel transmissions are scheduled in downlink control information (DCI).

[0185] Example 54 is an apparatus according to Example 52, wherein the configuration includes downlink control information (DCI) indicating the DMRS bundling window.

[0186] Example 55 is an apparatus according to Example 54, wherein the DMRS bundling window is indicated in the DCI by a plurality of time slots in which the DMRS are to be bundled.

[0187] Example 56 is an apparatus according to Example 54, wherein the DCI includes a DCI format associated with a Bundled Indication Radio Network Temporary Identifier (BI-RNTI).

[0188] Example 57 is an apparatus according to Example 56, wherein BI-RNTI is UE-specific or group-specific.

[0189] Example 58 is an apparatus according to any one of Examples 54, 56 or 57, wherein the DCI includes a New Bundling Indicator (NBI), the DMRS Bundling Window starts when the NBI of the first DCI switches to a first value, and the DMRS Bundling Window ends when the NBI of the second DCI switches to a second value different from the first value.

[0190] Example 59 is an apparatus according to Example 52, wherein DMRS is received after a time gap between the UE receiving downlink control information (DCI) and the start time of the DMRS bundling window, wherein the time gap includes preparation time and additional time gap for different uplink data channel transmissions.

[0191] Example 60 is an apparatus according to Example 59, wherein the additional time gap is based on the minimum SCS between the first subcarrier spacing (SCS) of the DCI and the second SCS of the different uplink data channel transmissions.

[0192] Example 61 is an apparatus according to Example 59 or 60, further comprising: a component for reporting additional time gaps to a base station in a capability information message.

[0193] Example 62 is a computer-readable medium storing computer-executable code that, when executed by a processor, causes the processor to: transmit to a user equipment (UE) a configuration indicating that demodulation reference signals (DMRS) are bundled in different uplink data channel transmissions for joint channel estimation; receive bundled DMRS in a DMRS bundling window based on the configuration; and perform joint channel estimation based on the bundled DMRS.

[0194] Example 63 is the method according to Examples 1 to 10, wherein the configuration indicates the duration of the DMRS bundling window as the number of symbols including uplink and downlink symbols, the number of slots including uplink and downlink slots, the number of subframes, the number of frames, or the amount of time.

[0195] Example 64 is the method according to any one of Examples 1 to 10 or 63, wherein the configuration is received in response to a capability information message indicating the duration of support for the DMRS bundle window.

[0196] Example 65 is a method according to any one of Examples 1 to 10, 63 or 64, further comprising maintaining power consistency between bundled DMRSs and maintaining phase continuity between bundled DMRSs, wherein the bundled DMRSs include DMRSs having the same modulation and coding scheme (MCS), the same time division duplex (TDD) or frequency division duplex (FDD) scheme, continuous allocation of time domain resources or the same transmission power.

[0197] Example 66 is an apparatus according to Examples 11 through 20, wherein the configuration indicates the duration of the DMRS bundling window as the number of symbols including uplink and downlink symbols, the number of slots including uplink and downlink slots, the number of subframes, the number of frames, or the amount of time.

[0198] Example 67 is an apparatus according to any one of Examples 11 to 20 or 66, wherein the configuration is received in response to a capability information message indicating the support duration of the DMRS bundling window.

[0199] Example 68 is an apparatus according to any one of Examples 11 to 20, 66 or 67, wherein the instructions, when executed by a processor, also cause the apparatus to maintain power consistency between bundled DMRSs and to maintain phase continuity between bundled DMRSs, wherein the bundled DMRSs include DMRSs having the same modulation and coding scheme (MCS), the same time division duplex (TDD) or frequency division duplex (FDD) scheme, allocation of continuous time domain resources or the same transmission power.

[0200] Example 69 is an apparatus according to Examples 21 to 30, wherein the configuration indicates the duration of the DMRS bundling window as the number of symbols including uplink and downlink symbols, the number of slots including uplink and downlink slots, the number of subframes, the number of frames, or the amount of time.

[0201] Example 70 is an apparatus according to any one of Examples 21 to 30 or 69, wherein the configuration is received in response to a capability information message indicating the support duration of the DMRS bundling window.

[0202] Example 71 is an apparatus according to any one of Examples 21 to 30, 69 or 70, further comprising components for maintaining power consistency between bundled DMRSs and for maintaining phase continuity between bundled DMRSs, wherein the bundled DMRSs include DMRSs having the same modulation and coding scheme (MCS), the same time division duplex (TDD) or frequency division duplex (FDD) scheme, continuous time domain resource allocation or the same transmission power.

[0203] Example 72 is the method according to Examples 32 to 41, wherein the configuration indicates the duration of the DMRS bundling window as the number of symbols including uplink and downlink symbols, the number of slots including uplink and downlink slots, the number of subframes, the number of frames, or the amount of time.

[0204] Example 73 is the method according to any one of Examples 32 to 41 or 72, wherein the configuration is received in response to a capability information message indicating the support duration of the DMRS bundle window.

[0205] Example 74 is a method according to any one of Examples 32 to 41, 72 or 73, wherein power consistency is maintained between bundled DMRSs and phase continuity is maintained between bundled DMRSs, wherein the bundled DMRSs include DMRSs having the same modulation and coding scheme (MCS), the same time division duplex (TDD) or frequency division duplex (FDD) scheme, continuous time domain resource allocation or the same transmission power.

[0206] Example 75 is an apparatus according to Examples 42 to 51, wherein the configuration indicates the duration of the DMRS bundling window as the number of symbols including uplink and downlink symbols, the number of slots including uplink and downlink slots, the number of subframes, the number of frames, or the amount of time.

[0207] Example 76 is an apparatus according to any one of Examples 42 to 51 or 75, wherein the configuration is received in response to a capability information message indicating the support duration of the DMRS bundle window.

[0208] Example 77 is an apparatus according to any one of Examples 42 to 51, 75 or 76, wherein power consistency is maintained between bundled DMRSs and phase continuity is maintained between bundled DMRSs, wherein the bundled DMRSs include DMRSs having the same modulation and coding scheme (MCS), the same time division duplex (TDD) or frequency division duplex (FDD) scheme, continuous allocation of time domain resources or the same transmission power.

[0209] Example 78 is an apparatus according to Examples 52 to 61, wherein the configuration indicates the duration of the DMRS bundling window as the number of symbols including uplink and downlink symbols, the number of slots including uplink and downlink slots, the number of subframes, the number of frames, or the amount of time.

[0210] Example 79 is an apparatus according to any one of Examples 52 to 61 or 78, wherein the configuration is received in response to a capability information message indicating the support duration of the DMRS bundling window.

[0211] Example 80 is an apparatus according to any one of Examples 52 to 61, 78 or 79, wherein power consistency is maintained between bundled DMRSs and phase continuity is maintained between bundled DMRSs, wherein the bundled DMRSs include DMRSs having the same modulation and coding scheme (MCS), the same time division duplex (TDD) or frequency division duplex (FDD) scheme, continuous allocation of time domain resources or the same transmission power.

Claims

1. A method for wireless communication at a user equipment (UE), comprising: The base station receives instructions to bundle demodulation reference signals (DMRS) in different uplink data channel transmissions for configuration of joint channel estimation. The DMRS bundling window is determined based on the configuration; and Bundled DMRSs are transmitted within the DMRS bundling window, wherein power consistency and phase continuity are maintained between the bundled DMRSs.

2. The method according to claim 1, wherein, The configuration is received in the Physical Uplink Shared Channel (PUSCH) configuration, and the different uplink data channel transmissions are scheduled in the Downlink Control Information (DCI).

3. The method according to claim 1, wherein, The configuration includes downlink control information (DCI) that indicates the DMRS bundling window.

4. The method according to claim 3, wherein, The DMRS bundling window is indicated in the DCI by multiple time slots in which the DMRS are to be bundled.

5. The method according to claim 3, wherein, The DCI includes a DCI format associated with the Bundled Indication Radio Network Temporary Identifier BI-RNTI.

6. The method according to claim 5, wherein, The BI-RNTI is UE-specific or group-specific.

7. The method according to claim 3, wherein, The DCI includes a new bundling indicator (NBI), and the determination of the DMRS bundling window includes: Determine the start time of the DMRS bundling window when the NBI switches to a first value in response to a first DCI, and determine the end time of the DMRS bundling window when the NBI switches to a second value different from the first value in response to a second DCI.

8. The method according to claim 1, further comprising: Determine the time gap between the start time of receiving downlink control information (DCI) and the start time of the DMRS bundling window, wherein the time gap includes the preparation time and additional time gap for the transmission of the different uplink data channels.

9. The method according to claim 8, wherein, The additional time gap is based on the minimum SCS between the first subcarrier spacing (SCS) of the DCI and the second SCS of the different uplink data channel transmissions.

10. The method of claim 8, further comprising: The additional time gap is reported to the base station in the capability information message.

11. The method according to claim 1, wherein, The configuration indicates the duration of the DMRS bundling window as the number of symbols including uplink and downlink symbols, the number of slots including uplink and downlink slots, the number of subframes, the number of frames, or the amount of time.

12. The method according to claim 1, wherein, The configuration is received in response to a capability information message indicating the duration of support for the DMRS bundled window.

13. An apparatus for wireless communication at a user equipment (UE), comprising: At least one memory, the memory including instructions; and At least one processor is configured to execute the instructions to cause the device to: The base station receives instructions to bundle demodulation reference signals (DMRS) in different uplink data channel transmissions for configuration of joint channel estimation. The DMRS bundling window is determined based on the configuration; and Bundled DMRSs are transmitted within the DMRS bundling window, wherein power consistency and phase continuity are maintained between the bundled DMRSs.

14. A method for wireless communication at a base station, comprising: Transmit to the User Equipment (UE) an instruction to bundle demodulation reference signals (DMRS) in different uplink data channel transmissions for configuration of joint channel estimation; Based on the configuration, bundled DMRSs are received in the DMRS bundling window, wherein power consistency and phase continuity are maintained between the bundled DMRSs; and Joint channel estimation is performed based on the bundled DMRS.

15. The method according to claim 14, wherein, The configuration is transmitted in the Physical Uplink Shared Channel (PUSCH) configuration, and the different uplink data channels are scheduled for transmission in the Downlink Control Information (DCI).

16. The method of claim 14, wherein, The configuration includes downlink control information (DCI) that indicates the DMRS bundling window.

17. The method according to claim 16, wherein, The DMRS bundling window is indicated in the DCI by multiple time slots in which the DMRS are to be bundled.

18. The method according to claim 16, wherein, The DCI includes a DCI format associated with the Bundled Indication Radio Network Temporary Identifier BI-RNTI.

19. The method according to claim 18, wherein, The BI-RNTI is UE-specific or group-specific.

20. The method of claim 16, wherein, The DCI includes a New Bundling Indicator (NBI), the start time of the DMRS bundling window is in response to the NBI of the first DCI switching to a first value, and the end time of the DMRS bundling window is in response to the NBI of the second DCI switching to a second value different from the first value.

21. The method according to claim 14, wherein, The DMRS is received after the time gap between the UE receiving the downlink control information (DCI) and the start time of the DMRS bundling window, wherein the time gap includes the preparation time and additional time gap for the transmission of the different uplink data channels.

22. The method according to claim 21, wherein, The additional time gap is based on the minimum SCS between the first subcarrier spacing (SCS) of the DCI and the second SCS of the different uplink data channel transmissions.

23. The method of claim 21, further comprising: The additional time gap is received from the UE in the capability information message.

24. The method according to claim 14, wherein, The configuration indicates the duration of the DMRS bundling window as the number of symbols including uplink and downlink symbols, the number of slots including uplink and downlink slots, the number of subframes, the number of frames, or the amount of time.

25. The method according to claim 14, wherein, The configuration is transmitted in response to a capability information message indicating the duration of support for the DMRS bundled window.

26. An apparatus for wireless communication at a base station, comprising: At least one memory, the memory including instructions; and At least one processor is configured to execute the instructions to cause the device to: Transmit to the User Equipment (UE) an instruction to bundle demodulation reference signals (DMRS) in different uplink data channel transmissions for configuration of joint channel estimation; Based on the configuration, bundled DMRSs are received in the DMRS bundling window, wherein power consistency and phase continuity are maintained between the bundled DMRSs; and Joint channel estimation is performed based on the bundled DMRS.

27. A user equipment (UE) comprising components for performing the method of any one of claims 1-12.

28. A computer-readable medium having program code recorded thereon, wherein the program code is executable by one or more processors of a user equipment (UE) to cause the processors to perform the method according to any one of claims 1-12.

29. A base station comprising components for performing the method of any one of claims 14-25.

30. A computer-readable medium having program code recorded thereon, wherein the program code is executable by one or more processors of a base station to cause the processors to perform the method according to any one of claims 14-25.

Images