Patent Application
20230114659
Aspects of the present disclosure generally relate to wireless communication and to techniques and apparatuses for joint channel estimation for repetitions without a demodulation reference signal.
Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasts. Typical wireless communication systems may employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, or the like). 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, time division synchronous code division multiple access (TD-SCDMA) systems, and Long Term Evolution (LTE). LTE/LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP).
A wireless network may include one or more base stations that support communication for a user equipment (UE) or multiple UEs. A UE may communicate with a base station via downlink communications and uplink communications. “Downlink” (or “DL”) refers to a communication link from the base station to the UE, and “uplink” (or “UL”) refers to a communication link from the UE to the base station.
The above multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different UEs to communicate on a municipal, national, regional, and/or global level. New Radio (NR), which may be referred to as 5G, is a set of enhancements to the LTE mobile standard promulgated by the 3GPP. NR is designed to better support mobile broadband internet access by improving spectral efficiency, lowering costs, improving services, making use of new spectrum, and better integrating with other open standards using orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) (CP-OFDM) on the downlink, using CP-OFDM and/or single-carrier frequency division multiplexing (SC-FDM) (also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink, as well as supporting beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation. As the demand for mobile broadband access continues to increase, further improvements in LTE, NR, and other radio access technologies remain useful.
Some aspects described herein relate to a method of wireless communication performed by a user equipment (UE). The method may include transmitting, on a physical uplink channel, repetitions without a demodulation reference signal (DMRS). The method may include maintaining continuity for joint channel estimation of the repetitions without a DMRS during a first time domain window that is based at least in part on a second time domain window associated with joint channel estimation for repetitions with a DMRS.
Some aspects described herein relate to a method of wireless communication performed by a network entity. The method may include enabling joint channel estimation of repetitions without a DMRS on a physical uplink channel based at least in part on joint channel estimation being enabled for repetitions with a DMRS. The method may include receiving, from a UE, the repetitions without a DMRS on the physical uplink channel. The method may include performing joint channel estimation of the repetitions without a DMRS within a first time domain window that is based at least in part on a second time domain window associated with joint channel estimation for repetitions with a DMRS.
Some aspects described herein relate to a UE for wireless communication. The UE may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to transmit, on a physical uplink channel, repetitions without a DMRS. The one or more processors may be configured to maintain continuity for joint channel estimation of the repetitions without a DMRS during a first time domain window that is based at least in part on a second time domain window associated with joint channel estimation for repetitions with a DMRS.
Some aspects described herein relate to a network entity for wireless communication. The network entity may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to enable joint channel estimation of repetitions without a DMRS on a physical uplink channel based at least in part on joint channel estimation being enabled for repetitions with a DMRS. The one or more processors may be configured to receive, from a UE, the repetitions without a DMRS on the physical uplink channel. The one or more processors may be configured to perform joint channel estimation of the repetitions without a DMRS within a first time domain window that is based at least in part on a second time domain window associated with joint channel estimation for repetitions with a DMRS.
Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a UE. The set of instructions, when executed by one or more processors of the UE, may cause the UE to transmit, on a physical uplink channel, repetitions without a DMRS. The set of instructions, when executed by one or more processors of the UE, may cause the UE to maintain continuity for joint channel estimation of the repetitions without a DMRS during a first time domain window that is based at least in part on a second time domain window associated with joint channel estimation for repetitions with a DMRS.
Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a network entity. The set of instructions, when executed by one or more processors of the network entity, may cause the network entity to enable joint channel estimation of repetitions without a DMRS on a physical uplink channel based at least in part on joint channel estimation being enabled for repetitions with a DMRS. The set of instructions, when executed by one or more processors of the network entity, may cause the network entity to receive, from a UE, the repetitions without a DMRS on the physical uplink channel. The set of instructions, when executed by one or more processors of the network entity, may cause the network entity to perform joint channel estimation of the repetitions without a DMRS within a first time domain window that is based at least in part on a second time domain window associated with joint channel estimation for repetitions with a DMRS.
Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for transmitting, on a physical uplink channel, repetitions without a DMRS. The apparatus may include means for maintaining continuity for joint channel estimation of the repetitions without a DMRS during a first time domain window that is based at least in part on a second time domain window associated with joint channel estimation for repetitions with a DMRS.
Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for enabling joint channel estimation of repetitions without a DMRS on a physical uplink channel based at least in part on joint channel estimation being enabled for repetitions with a DMRS. The apparatus may include means for receiving, from a UE, the repetitions without a DMRS on the physical uplink channel. The apparatus may include means for performing joint channel estimation of the repetitions without a DMRS within a first time domain window that is based at least in part on a second time domain window associated with joint channel estimation for repetitions with a DMRS.
Aspects generally include a method, apparatus, system, computer program product, non-transitory computer-readable medium, user equipment, base station, network node, network entity, wireless communication device, and/or processing system as substantially described herein with reference to and as illustrated by the drawings and specification.
The foregoing has outlined rather broadly the features and technical advantages of examples according to the disclosure in order that the detailed description that follows may be better understood. Additional features and advantages will be described hereinafter. The conception and specific examples disclosed may be readily utilized as a basis for modifying or designing other structures for carrying out the same purposes of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. Characteristics of the concepts disclosed herein, both their organization and method of operation, together with associated advantages, will be better understood from the following description when considered in connection with the accompanying figures. Each of the figures is provided for the purposes of illustration and description, and not as a definition of the limits of the claims.
While aspects are described in the present disclosure by illustration to some examples, those skilled in the art will understand that such aspects may be implemented in many different arrangements and scenarios. Techniques described herein may be implemented using different platform types, devices, systems, shapes, sizes, and/or packaging arrangements. For example, some aspects may be implemented via integrated chip embodiments or other non-module-component based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail/purchasing devices, medical devices, and/or artificial intelligence devices). Aspects may be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components, and/or system-level components. Devices incorporating described aspects and features may include additional components and features for implementation and practice of claimed and described aspects. For example, transmission and reception of wireless signals may include one or more components for analog and digital purposes (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders, and/or summers). It is intended that aspects described herein may be practiced in a wide variety of devices, components, systems, distributed arrangements, and/or end-user devices of varying size, shape, and constitution.
So that the above-recited features of the present disclosure can be understood in detail, a more particular description, briefly summarized above, may be had by reference to aspects, some of which are illustrated in the appended drawings. It is to be noted, however, that the appended drawings illustrate only certain typical aspects of this disclosure and are therefore not to be considered limiting of its scope, for the description may admit to other equally effective aspects. The same reference numbers in different drawings may identify the same or similar elements.
Various aspects of the disclosure are described more fully hereinafter with reference to the accompanying drawings. This disclosure may, however, be embodied in many different forms and should not be construed as limited to any specific structure or function presented throughout this disclosure. Rather, these aspects are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art. One skilled in the art should appreciate that the scope of the disclosure is intended to cover any aspect of the disclosure disclosed herein, whether implemented independently of or combined with any other aspect of the disclosure. For example, an apparatus may be implemented or a method may be practiced using any number of the aspects set forth herein. In addition, the scope of the disclosure is intended to cover such an apparatus or method which is practiced using other structure, functionality, or structure and functionality in addition to or other than the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of a claim.
Several aspects of telecommunication systems will now be presented with reference to various apparatuses and techniques. These apparatuses and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, or the like (collectively referred to as “elements”). These elements may be implemented using hardware, software, or combinations thereof. Whether such elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system.
While aspects may be described herein using terminology commonly associated with a 5G or New Radio (NR) radio access technology (RAT), aspects of the present disclosure can be applied to other RATs, such as a 3G RAT, a 4G RAT, and/or a RAT subsequent to 5G (e.g., 6G).
A base station 110 may provide communication coverage for a macro cell, a pico cell, a femto cell, and/or another type of cell. A macro cell may cover a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs 120 with service subscriptions. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs 120 with service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UEs 120 having association with the femto cell (e.g., UEs 120 in a closed subscriber group (CSG)). A base station 110 for a macro cell may be referred to as a macro base station. A base station 110 for a pico cell may be referred to as a pico base station. A base station 110 for a femto cell may be referred to as a femto base station or an in-home base station. In the example shown in
In some examples, a cell may not necessarily be stationary, and the geographic area of the cell may move according to the location of a base station 110 that is mobile (e.g., a mobile base station). In some examples, the base stations 110 may be interconnected to one another and/or to one or more other base stations 110 or network nodes (not shown) in the wireless network 100 through various types of backhaul interfaces, such as a direct physical connection or a virtual network, using any suitable transport network.
In some aspects, the term “base station” (e.g., the base station 110) or “network entity” may refer to an aggregated base station, a disaggregated base station, an integrated access and backhaul (IAB) node, a relay node, and/or one or more components thereof. For example, in some aspects, “base station” or “network entity” may refer to a central unit (CU), a distributed unit (DU), a radio unit (RU), a Near-Real Time (Near-RT) RAN Intelligent Controller (RIC), or a Non-Real Time (Non-RT) RIC, or a combination thereof. In some aspects, the term “base station” or “network entity” may refer to one device configured to perform one or more functions, such as those described herein in connection with the base station 110. In some aspects, the term “base station” or “network entity” may refer to a plurality of devices configured to perform the one or more functions. For example, in some distributed systems, each of a number of different devices (which may be located in the same geographic location or in different geographic locations) may be configured to perform at least a portion of a function, or to duplicate performance of at least a portion of the function, and the term “base station” or “network entity” may refer to any one or more of those different devices. In some aspects, the term “base station” or “network entity” may refer to one or more virtual base stations and/or one or more virtual base station functions. For example, in some aspects, two or more base station functions may be instantiated on a single device. In some aspects, the term “base station” or “network entity” may refer to one of the base station functions and not another. In this way, a single device may include more than one base station.
The wireless network 100 may include one or more relay stations. A relay station is an entity that can receive a transmission of data from an upstream station (e.g., a base station 110 or a UE 120) and send a transmission of the data to a downstream station (e.g., a UE 120 or a base station 110). A relay station may be a UE 120 that can relay transmissions for other UEs 120. In the example shown in
The wireless network 100 may be a heterogeneous network that includes base stations 110 of different types, such as macro base stations, pico base stations, femto base stations, relay base stations, or the like. These different types of base stations 110 may have different transmit power levels, different coverage areas, and/or different impacts on interference in the wireless network 100. For example, macro base stations may have a high transmit power level (e.g., 5 to 40 watts) whereas pico base stations, femto base stations, and relay base stations may have lower transmit power levels (e.g., 0.1 to 2 watts).
A network controller 130 may couple to or communicate with a set of base stations 110 and may provide coordination and control for these base stations 110. The network controller 130 may communicate with the base stations 110 via a backhaul communication link. The base stations 110 may communicate with one another directly or indirectly via a wireless or wireline backhaul communication link.
The UEs 120 may be dispersed throughout the wireless network 100, and each UE 120 may be stationary or mobile. A UE 120 may include, for example, an access terminal, a terminal, a mobile station, and/or a subscriber unit. A UE 120 may be a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or a smart bracelet)), an entertainment device (e.g., a music device, a video device, and/or a satellite radio), a vehicular component or sensor, a smart meter/sensor, industrial manufacturing equipment, a global positioning system device, and/or any other suitable device that is configured to communicate via a wireless medium.
Some UEs 120 may be considered machine-type communication (MTC) or evolved or enhanced machine-type communication (eMTC) UEs. An MTC UE and/or an eMTC UE may include, for example, a robot, a drone, a remote device, a sensor, a meter, a monitor, and/or a location tag, that may communicate with a base station, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered Internet-of-Things (IoT) devices, and/or may be implemented as NB-IoT (narrowband IoT) devices. Some UEs 120 may be considered a Customer Premises Equipment. A UE 120 may be included inside a housing that houses components of the UE 120, such as processor components and/or memory components. In some examples, the processor components and the memory components may be coupled together. For example, the processor components (e.g., one or more processors) and the memory components (e.g., a memory) may be operatively coupled, communicatively coupled, electronically coupled, and/or electrically coupled.
In general, any number of wireless networks 100 may be deployed in a given geographic area. Each wireless network 100 may support a particular RAT and may operate on one or more frequencies. A RAT may be referred to as a radio technology, an air interface, or the like. A frequency may be referred to as a carrier, a frequency channel, or the like. Each frequency may support a single RAT in a given geographic area in order to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.
In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly using one or more sidelink channels (e.g., without using a base station 110 as an intermediary to communicate with one another). For example, the UEs 120 may communicate using peer-to-peer (P2P) communications, device-to-device (D2D) communications, a vehicle-to-everything (V2X) protocol (e.g., which may include a vehicle-to-vehicle (V2V) protocol, a vehicle-to-infrastructure (V2I) protocol, or a vehicle-to-pedestrian (V2P) protocol), and/or a mesh network. In such examples, a UE 120 may perform scheduling operations, resource selection operations, and/or other operations described elsewhere herein as being performed by the base station 110.
Devices of the wireless network 100 may communicate using the electromagnetic spectrum, which may be subdivided by frequency or wavelength into various classes, bands, channels, or the like. For example, devices of the wireless network 100 may communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). It should be understood that although a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as a “Sub-6 GHz” band in various documents and articles. A similar nomenclature issue sometimes occurs with regard to FR2, which is often referred to (interchangeably) as a “millimeter wave” band in documents and articles, despite being different from the extremely high frequency (EHF) band (30 GHz-300 GHz) which is identified by the International Telecommunications Union (ITU) as a “millimeter wave” band.
The frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Recent 5G NR studies have identified an operating band for these mid-band frequencies as frequency range designation FR3 (7.125 GHz-24.25 GHz). Frequency bands falling within FR3 may inherit FR1 characteristics and/or FR2 characteristics, and thus may effectively extend features of FR1 and/or FR2 into mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6 GHz-71 GHz), FR4 (52.6 GHz-114.25 GHz), and FR5 (114.25 GHz-300 GHz). Each of these higher frequency bands falls within the EHF band.
With the above examples in mind, unless specifically stated otherwise, it should be understood that the term “sub-6 GHz” or the like, if used herein, may broadly represent frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. Further, unless specifically stated otherwise, it should be understood that the term “millimeter wave” or the like, if used herein, may broadly represent frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-a or FR4-1, and/or FR5, or may be within the EHF band. It is contemplated that the frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and/or FR5) may be modified, and techniques described herein are applicable to those modified frequency ranges.
In some aspects, the UE 120 may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may transmit, on a physical uplink channel, repetitions without a DMRS. The communication manager 140 may maintain continuity for joint channel estimation of the repetitions without a DMRS during a first time domain window that is based at least in part on a second time domain window associated with joint channel estimation for repetitions with a DMRS. Additionally, or alternatively, the communication manager 140 may perform one or more other operations described herein.
In some aspects, a network entity (e.g., base station 110) may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may enable joint channel estimation of repetitions without a DMRS on a physical uplink channel based at least in part on joint channel estimation being enabled for repetitions with a DMRS. The communication manager 150 may receive, from a UE, the repetitions without a DMRS on the physical uplink channel and perform joint channel estimation of the repetitions without a DMRS within a first time domain window that is based at least in part on a second time domain window associated with joint channel estimation for repetitions with a DMRS. Additionally, or alternatively, the communication manager 150 may perform one or more other operations described herein.
As indicated above,
At the base station 110, a transmit processor 220 may receive data, from a data source 212, intended for the UE 120 (or a set of UEs 120). The transmit processor 220 may select one or more modulation and coding schemes (MCSs) for the UE 120 based at least in part on one or more channel quality indicators (CQIs) received from that UE 120. The base station 110 may process (e.g., encode and modulate) the data for the UE 120 based at least in part on the MCS(s) selected for the UE 120 and may provide data symbols for the UE 120. The transmit processor 220 may process system information (e.g., for semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, grants, and/or upper layer signaling) and provide overhead symbols and control symbols. The transmit processor 220 may generate reference symbols for reference signals (e.g., a cell-specific reference signal (CRS) or a demodulation reference signal (DMRS)) and synchronization signals (e.g., a primary synchronization signal (PSS) or a secondary synchronization signal (SSS)). A transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on the data symbols, the control symbols, the overhead symbols, and/or the reference symbols, if applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems), shown as modems 232a through 232t. For example, each output symbol stream may be provided to a modulator component (shown as MOD) of a modem 232. Each modem 232 may use a respective modulator component to process a respective output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each modem 232 may further use a respective modulator component to process (e.g., convert to analog, amplify, filter, and/or upconvert) the output sample stream to obtain a downlink signal. The modems 232a through 232t may transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas), shown as antennas 234a through 234t.
At the UE 120, a set of antennas 252 (shown as antennas 252a through 252r) may receive the downlink signals from the base station 110 and/or other base stations 110 and may provide a set of received signals (e.g., R received signals) to a set of modems 254 (e.g., R modems), shown as modems 254a through 254r. For example, each received signal may be provided to a demodulator component (shown as DEMOD) of a modem 254. Each modem 254 may use a respective demodulator component to condition (e.g., filter, amplify, downconvert, and/or digitize) a received signal to obtain input samples. Each modem 254 may use a demodulator component to further process the input samples (e.g., for OFDM) to obtain received symbols. A MIMO detector 256 may obtain received symbols from the modems 254, may perform MIMO detection on the received symbols if applicable, and may provide detected symbols. A receive processor 258 may process (e.g., demodulate and decode) the detected symbols, may provide decoded data for the UE 120 to a data sink 260, and may provide decoded control information and system information to a controller/processor 280. The term “controller/processor” may refer to one or more controllers, one or more processors, or a combination thereof. A channel processor may determine a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, and/or a CQI parameter, among other examples. In some examples, one or more components of the UE 120 may be included in a housing 284.
The network controller 130 may include a communication unit 294, a controller/processor 290, and a memory 292. The network controller 130 may include, for example, one or more devices in a core network. The network controller 130 may communicate with the base station 110 via the communication unit 294.
One or more antennas (e.g., antennas 234a through 234t and/or antennas 252a through 252r) may include, or may be included within, one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and/or one or more antenna arrays, among other examples. An antenna panel, an antenna group, a set of antenna elements, and/or an antenna array may include one or more antenna elements (within a single housing or multiple housings), a set of coplanar antenna elements, a set of non-coplanar antenna elements, and/or one or more antenna elements coupled to one or more transmission and/or reception components, such as one or more components of
On the uplink, at the UE 120, a transmit processor 264 may receive and process data from a data source 262 and control information (e.g., for reports that include RSRP, RSSI, RSRQ, and/or CQI) from the controller/processor 280. The transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be precoded by a TX MIMO processor 266 if applicable, further processed by the modems 254 (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to the base station 110. In some examples, the modem 254 of the UE 120 may include a modulator and a demodulator. In some examples, the UE 120 includes a transceiver. The transceiver may include any combination of the antenna(s) 252, the modem(s) 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, and/or the TX MIMO processor 266. The transceiver may be used by a processor (e.g., the controller/processor 280) and the memory 282 to perform aspects of any of the methods described herein (e.g., with reference to
At the base station 110, the uplink signals from UE 120 and/or other UEs may be received by the antennas 234, processed by the modem 232 (e.g., a demodulator component, shown as DEMOD, of the modem 232), detected by a MIMO detector 236 if applicable, and further processed by a receive processor 238 to obtain decoded data and control information sent by the UE 120. The receive processor 238 may provide the decoded data to a data sink 239 and provide the decoded control information to the controller/processor 240. The base station 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244. The base station 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink and/or uplink communications. In some examples, the modem 232 of the base station 110 may include a modulator and a demodulator. In some examples, the base station 110 includes a transceiver. The transceiver may include any combination of the antenna(s) 234, the modem(s) 232, the MIMO detector 236, the receive processor 238, the transmit processor 220, and/or the TX MIMO processor 230. The transceiver may be used by a processor (e.g., the controller/processor 240) and the memory 242 to perform aspects of any of the methods described herein (e.g., with reference to
A controller/processor of a network entity (e.g., controller/processor 240 of the base station 110), the controller/processor 280 of the UE 120, and/or any other component(s) of
In some aspects, the UE 120 includes means for transmitting, on a physical uplink channel, repetitions without a DMRS; and/or means for maintaining continuity for joint channel estimation of the repetitions without a DMRS during a first time domain window that is based at least in part on a second time domain window associated with joint channel estimation for repetitions with a DMRS. The means for the UE 120 to perform operations described herein may include, for example, one or more of communication manager 140, antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, controller/processor 280, or memory 282.
In some aspects, a network entity (e.g., base station 110) includes means for enabling joint channel estimation of repetitions without a DMRS on a physical uplink channel based at least in part on joint channel estimation being enabled for repetitions with a DMRS; means for receiving, from a UE, the repetitions without a DMRS on the physical uplink channel; and/or means for performing joint channel estimation of the repetitions without a DMRS within a first time domain window that is based at least in part on a second time domain window associated with joint channel estimation for repetitions with a DMRS. The means for the network entity to perform operations described herein may include, for example, one or more of communication manager 150, transmit processor 220, TX MIMO processor 230, modem 232, antenna 234, MIMO detector 236, receive processor 238, controller/processor 240, memory 242, or scheduler 246.
While blocks in
As indicated above,
Example 300 shows three reception occasions or slots of transport blocks. A receiving UE (or a receiving base station) may use DMRSs in each transport block for channel estimation. That is, channel estimation is performed for each slot, separately. Example 302 shows joint channel estimation, using DMRSs of the three transport blocks together. This may also be referred to as “cross-slot channel estimation” or “DMRS bundling.” Joint channel estimation may improve the accuracy of channel estimation because the estimates involve information across multiple slots. Joint channel estimation may be applicable to low-tier UEs with a reduced number of receive antennas (e.g., one receive antenna) or UEs that are in deep coverage holes.
In order for joint channel estimation to be effective, DMRSs across the slots are to maintain continuity, such as phase continuity. In other words, DMRSs of the same channel estimation process are to have phase coherence from slot to slot. Phase coherence may include phase continuity in the frequency domain across consecutive slots. Signals may have a same phase if the signals have the same frequency and the maxima and minima of the signals are aligned. Signals may be phase coherent if a phase difference between the signals is the same. Maintaining phase continuity may also be referred to as “coherent transmission.”
A transport block or other communication may be repeated multiple times, and these may be referred to as repetitions. Joint channel estimation may be used for physical uplink shared channel (PUSCH) communications (e.g., repetitions) and for physical uplink control channel (PUCCH) communications (e.g., repetitions). A base station may perform joint channel estimation within a time domain window in which joint channel estimation is applicable. Joint channel estimation for PUSCH repetitions and the time domain window may be jointly enabled or disabled via a radio resource control (RRC) configuration for a UE.
However, PUCCH format 0 does not have a DMRS, and thus there is no DMRS bundling for joint channel estimation. Joint channel estimation may still be useful for PUCCH format 0 (or other sequence-based PUCCH formats without a DMRS) and thus DMRS-less repetitions (repetitions without a DMRS) may be introduced for carrying more than two bits.
Joint channel estimation expects uplink continuity across slots of the repetitions. However, the expected accuracy of continuity (e.g., accuracy of phase continuity) may be different for different formats of PUCCH and may depend on the transmission scheme, the rate, and/or a size of uplink control information (UCI).
As indicated above,
According to various aspects described herein, a network entity (e.g., base station 110) and a UE (e.g., UE 120) may enable joint channel estimation for DMRS-less communications (e.g., repetitions) on a physical uplink channel (e.g., PUCCH), where the joint channel estimation is to be performed within a time domain window. DMRS-less repetitions may include repetitions that are without a DMRS (no DMRS symbols). These may include repetitions of a format that does not include DMRS symbols. In some aspects, DMRS-less repetitions may include repetitions that may have one or more DMRS symbols but do not include a sufficient quantity of DMRS symbols for DMRS bundling. The base station 110 and/or the UE 120 may determine to enable joint channel estimation for DMRS-less PUCCH repetitions and determine the time domain window based at least in part on whether joint channel estimation for DMRS PUSCH repetitions and/or DMRS PUCCH repetitions is enabled. DMRS repetitions may include repetitions with a DMRS (DMRS symbols for DMRS bundling).
The base station 110 may configure the time domain window for DMRS-less joint channel estimation based at least in part on the time domain window used for DMRS joint channel estimation. For example, the time domain window for joint channel estimation for DMRS-less PUCCH repetitions may be the same as the time domain window for PUSCH communications with a DMRS or PUCCH communications with a DMRS.
In some aspects, the base station 110 may scale the time domain window for DMRS-less joint channel estimation with respect to the time domain window for DMRS joint channel estimation. The scaling factor may be less than or greater than 1. For example, the time domain window for DMRS-less joint channel estimation may be half the length (e.g., in symbols) or twice the length of the time window for DMRS joint channel estimation. The scaling factor may be predefined in stored configuration information (e.g., a standard specification) or configured by the base station 110 (e.g., as part of a configuration of the PUCCH format).
In some aspects, the UE 120 and the base station 110 may coordinate enablement of DMRS-less joint channel estimation and may select a size of the time domain window based at least in part on a UE capability for maintaining uplink continuity for DMRS-less communications on a physical uplink channel.
Example 400 shows the base station 110 performing joint channel estimation on DMRS-less communications from the UE 120 on a physical uplink channel, such as a PUCCH. The base station 110 may determine to perform joint channel estimation (and the UE 120 may determine to maintain continuity for the joint channel estimation) based at least in part on a format of PUCCH communications. The PUCCH format may be, for example, PUCCH format 0, which is DMRS-less and sequence based. Joint channel estimation may also be enabled based at least in part on a UCI size, a length of a PUCCH in symbols (whether long PUCCH or short PUCCH), or an associated sequence set. A sequence set may indicate whether the sequence set does not include a DMRS. The sequence set may indicate whether the sequence set can be associated with joint channel estimation.
As shown by reference number 405, the UE 120 may transmit a UE capability for maintaining DMRS-less PUCCH communications (e.g., repetitions) for joint channel estimation by the base station 110. The UE capability for maintaining continuity for DMRS-less PUCCH repetitions may be different from a UE capability for maintaining continuity for DMRS PUCCH repetitions. The UE 120 may determine the UE capability for maintaining continuity for DMRS-less PUCCH communications based at least in part on a UE capability for maintaining continuity for DMRS PUCCH repetitions. The UE capability for maintaining continuity for DMRS-less PUCCH repetitions may vary based at least in part on the PUCCH format (e.g., PUCCH format 0), the UCI size, the length of PUCCH (short PUCCH or long PUCCH), and/or the associated sequence set.
As shown by reference number 410, the UE 120 may transmit multiple DMRS-less repetitions (e.g., PUCCH repetitions) during a time domain window 415. As shown by reference number 420, the base station 110 may perform joint channel estimation with the DMRS-less repetitions received during the time domain window 415. The time domain window 415 may be based at least in part on a time domain window used for joint channel estimation of DMRS repetitions. For example, as shown in example 400, the DMRS-less time domain window 415 may be based at least in part on a scaling factor with respect to a DMRS time domain window 416. If the scaling factor is 2, the DMRS-less time domain window 415 may be twice the length (e.g., in symbols) as the DMRS time domain window 416.
In some aspects, the base station 110 may perform joint channel estimation for a mix of DMRS-less repetitions and DMRS repetitions (PUCCH and/or PUSCH). Joint channel estimation based on DMRS repetitions on the PUCCH or the PUSCH may help in detection of DMRS-less communications. Joint channel estimation may be performed on the mix of DMRS-less repetitions and DMRS repetitions as long as all components are covered by the same time domain window 415.
The UE 120 may attempt to maintain continuity of the DMRS-less repetitions and/or DMRS repetitions during the time domain window 415. This may include maintaining phase continuity during the time domain window 415. This may also include refraining from changing a time advance, a spatial filter configuration, or a precoding parameter during the time domain window 415.
The base station 110 may successfully perform joint channel estimation on DMRS-less repetitions during the time domain window 415 if the UE 120 is able to maintain continuity during the time domain window 415. As shown by reference number 425, the base station 110 may transmit a communication based at least in part on a result of the joint channel estimation.
As indicated above,
As shown in
As further shown in
Process 500 may include additional aspects, such as any single aspect or any combination of aspects described below and/or in connection with one or more other processes described elsewhere herein.
In a first aspect, the physical uplink channel includes a PUCCH.
In a second aspect, alone or in combination with the first aspect, a length of the first time domain window and a length of the second time domain window are the same length. In a third aspect, alone or in combination with one or more of the first and second aspects, process 500 includes scaling, using a scaling factor, the first time domain window with respect to the second time domain window. In a fourth aspect, alone or in combination with one or more of the first through third aspects, the scaling factor is less than 1. In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, the scaling factor is greater than 1.
In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, the scaling factor is based at least in part on a format of communications on the physical uplink channel or a size of UCI on the physical uplink channel. In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, process 500 includes obtaining the scaling factor from stored configuration information or from configuration information received from a base station.
In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, maintaining continuity includes maintaining phase continuity during the first time domain window. In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, maintaining continuity includes refraining from changing a time advance, a spatial filter configuration, or a precoding parameter during the first time domain window.
In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, process 500 includes transmitting a UE capability for maintaining continuity for the repetitions without a DMRS during the first time domain window. In an eleventh aspect, alone or in combination with one or more of the first through tenth aspects, the UE capability for maintaining continuity for the repetitions without a DMRS during the first time domain window is different than a UE capability for maintaining continuity for the repetitions with a DMRS.
In a twelfth aspect, alone or in combination with one or more of the first through eleventh aspects, the UE capability for maintaining continuity for the repetitions without a DMRS during the first time domain window is based at least in part on a UE capability for maintaining continuity for the repetitions with a DMRS.
In a thirteenth aspect, alone or in combination with one or more of the first through twelfth aspects, the UE capability for maintaining continuity for the repetitions without a DMRS during the first time domain window is based at least in part on a format of communications on the physical uplink channel, a UCI size, a length of the communications on the physical uplink channel, or a length of an associated sequence set.
In a fourteenth aspect, alone or in combination with one or more of the first through thirteenth aspects, process 500 includes determining to maintain continuity for the repetitions without a DMRS during the first time domain window based at least in part on a format of communications on the physical uplink channel, a UCI size, a length of the communications on the physical uplink channel, or a length of an associated sequence set.
In a fifteenth aspect, alone or in combination with one or more of the first through fourteenth aspects, process 500 includes transmitting, during the first time domain window on the physical uplink channel, repetitions with a DMRS in addition to the repetitions without a DMRS, and maintaining, during the first time domain window, continuity for the joint channel estimation of the repetitions with a DMRS in addition to the repetitions without a DMRS.
Although
As shown in
As further shown in
As further shown in
Process 600 may include additional aspects, such as any single aspect or any combination of aspects described below and/or in connection with one or more other processes described elsewhere herein.
In a first aspect, the physical uplink channel includes a PUCCH.
In a second aspect, alone or in combination with the first aspect, process 600 includes transmitting a communication to the UE based at least in part on a result of performing the joint channel estimation of the repetitions without a DMRS.
In a third aspect, alone or in combination with one or more of the first and second aspects, process 600 includes scaling, using a scaling factor, the first time domain window with respect to the second time domain window. In a fourth aspect, alone or in combination with one or more of the first through third aspects, the scaling factor is less than 1. In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, the scaling factor is greater than 1.
In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, the scaling factor is based at least in part on a format of communications on the physical uplink channel or a size of UCI on the physical uplink channel.
In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, process 600 includes transmitting the scaling factor in configuration information to the UE.
In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, process 600 includes determining to perform the joint channel estimation for the repetitions without a DMRS based at least in part on a format of communications on the physical uplink channel, a UCI size, a length of the communications on the physical uplink channel, or a length of an associated sequence set.
In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, process 600 includes receiving, during the first time domain window on the physical uplink channel, repetitions with a DMRS in addition to the repetitions without a DMRS, and performing, during the first time domain window, the joint channel estimation of the repetitions with a DMRS in addition to the joint channel estimation of the repetitions without a DMRS.
Although
In some aspects, the apparatus 700 may be configured to perform one or more operations described herein in connection with
The reception component 702 may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the apparatus 706. The reception component 702 may provide received communications to one or more other components of the apparatus 700. In some aspects, the reception component 702 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, de-mapping, equalization, interference cancellation, or decoding, among other examples), and may provide the processed signals to the one or more other components of the apparatus 700. In some aspects, the reception component 702 may include one or more antennas, a modem, a demodulator, a MIMO detector, a receive processor, a controller/processor, a memory, or a combination thereof, of the UE described in connection with
The transmission component 704 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus 706. In some aspects, one or more other components of the apparatus 700 may generate communications and may provide the generated communications to the transmission component 704 for transmission to the apparatus 706. In some aspects, the transmission component 704 may perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples), and may transmit the processed signals to the apparatus 706. In some aspects, the transmission component 704 may include one or more antennas, a modem, a modulator, a transmit MIMO processor, a transmit processor, a controller/processor, a memory, or a combination thereof, of the UE described in connection with
The transmission component 704 may transmit, on a physical uplink channel, repetitions without a DMRS. The continuity component 708 may maintain continuity for joint channel estimation of the repetitions without a DMRS during a first time domain window that is based at least in part on a second time domain window associated with joint channel estimation for repetitions with a DMRS.
The scaling component 710 may scale, using a scaling factor, the first time domain window with respect to the second time domain window. The scaling component 710 may obtain the scaling factor from stored configuration information or from configuration information received from a network entity.
The transmission component 704 may transmit a UE capability for maintaining continuity for the repetitions without a DMRS during the first time domain window. The continuity component 708 may determine to maintain continuity for the repetitions without a DMRS during the first time domain window based at least in part on a format of communications on the physical uplink channel, a UCI size, a length of the communications on the physical uplink channel, or a length of an associated sequence set.
The transmission component 704 may transmit, during the first time domain window on the physical uplink channel, repetitions with a DMRS in addition to the repetitions without a DMRS. The continuity component 708 may maintain, during the first time domain window, continuity for the joint channel estimation of the repetitions with a DMRS in addition to the repetitions without a DMRS.
The number and arrangement of components shown in
In some aspects, the apparatus 800 may be configured to perform one or more operations described herein in connection with
The reception component 802 may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the apparatus 806. The reception component 802 may provide received communications to one or more other components of the apparatus 800. In some aspects, the reception component 802 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, de-mapping, equalization, interference cancellation, or decoding, among other examples), and may provide the processed signals to the one or more other components of the apparatus 800. In some aspects, the reception component 802 may include one or more antennas, a modem, a demodulator, a MIMO detector, a receive processor, a controller/processor, a memory, or a combination thereof, of the base station described in connection with
The transmission component 804 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus 806. In some aspects, one or more other components of the apparatus 800 may generate communications and may provide the generated communications to the transmission component 804 for transmission to the apparatus 806. In some aspects, the transmission component 804 may perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples), and may transmit the processed signals to the apparatus 806. In some aspects, the transmission component 804 may include one or more antennas, a modem, a modulator, a transmit MIMO processor, a transmit processor, a controller/processor, a memory, or a combination thereof, of the base station described in connection with
The channel estimation component 808 may enable joint channel estimation of repetitions without a DMRS on a physical uplink channel based at least in part on joint channel estimation being enabled for repetitions with a DMRS. The reception component 802 may receive, from a UE, the repetitions without a DMRS on the physical uplink channel. The channel estimation component 808 may perform joint channel estimation of the repetitions without a DMRS within a first time domain window that is based at least in part on a second time domain window associated with joint channel estimation for repetitions with a DMRS. The transmission component 804 may transmit a communication to the UE based at least in part on a result of performing the joint channel estimation of the repetitions without a DMRS.
The scaling component 810 may scale, using a scaling factor, the first time domain window with respect to the second time domain window. The transmission component 804 may transmit the scaling factor in configuration information to the UE.
The channel estimation component 808 may determine to perform the joint channel estimation for the repetitions without a DMRS based at least in part on a format of communications on the physical uplink channel, a UCI size, a length of the communications on the physical uplink channel, or a length of an associated sequence set.
The reception component 802 may receive, during the first time domain window on the physical uplink channel, repetitions with a DMRS in addition to the repetitions without a DMRS. The channel estimation component 808 may perform, during the first time domain window, the joint channel estimation of the repetitions with a DMRS in addition to the joint channel estimation of the repetitions without a DMRS.
The number and arrangement of components shown in
Deployment of communication systems, such as 5G NR systems, may be arranged in multiple manners with various components or constituent parts. In a 5G NR system, or network, a network node, a network entity, a mobility element of a network, a radio access network (RAN) node, a core network node, a network element, or a network equipment, such as a base station, or one or more units (or one or more components) performing base station functionality, may be implemented in an aggregated or disaggregated architecture. For example, a base station (such as a Node B, evolved NB (eNB), NR BS, 5G NB, access point (AP), a TRP, or a cell, etc.) may be implemented as an aggregated base station (also known as a standalone base station or a monolithic base station) or a disaggregated base station.
An aggregated base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. A disaggregated base station may be configured to utilize a protocol stack that is physically or logically distributed among two or more units (such as one or more CUs, one or more DUs, or one or more RUs). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed throughout one or multiple other RAN nodes. The DUs may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU also can be implemented as virtual units (e.g., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU)).
Base station-type operation or network design may consider aggregation characteristics of base station functionality. For example, disaggregated base stations may be utilized in an IAB network, an open radio access network (O-RAN (such as the network configuration sponsored by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Disaggregation may include distributing functionality across two or more units at various physical locations, as well as distributing functionality for at least one unit virtually, which can enable flexibility in network design. The various units of the disaggregated base station, or disaggregated RAN architecture, can be configured for wired or wireless communication with at least one other unit.
The disaggregated base station 900 architecture may include one or more CUs 910 that can communicate directly with a core network 920 via a backhaul link, or indirectly with the core network 920 through one or more disaggregated base station units (such as a Near-RT RIC 925 via an E2 link, or a Non-RT RIC 915 associated with a Service Management and Orchestration (SMO) Framework 905, or both). A CU 910 may communicate with one or more DUs 930 via respective midhaul links, such as an F1 interface. The DUs 930 may communicate with one or more RUs 940 via respective fronthaul links. The fronthaul link, the midhaul link, and the backhaul link may be generally referred to as “communication links.” The RUs 940 may communicate with respective UEs 120 via one or more RF access links. In some aspects, the UE 120 may be simultaneously served by multiple RUs 940. The DUs 930 and the RUs 940 may also be referred to as “O-RAN DUs (O-DUs”) and “O-RAN RUs (O-RUs)”, respectively. A network entity may include a CU, a DU, an RU, or any combination of CUs, DUs, and RUs. A network entity may include a disaggregated base station or one or more components of the disaggregated base station, such as a CU, a DU, an RU, or any combination of CUs, DUs, and RUs. A network entity may also include one or more of a TRP, a relay station, a passive device, an intelligent reflective surface (IRS), or other components that may provide a network interface for or serve a UE, mobile station, sensor/actuator, or other wireless device.
Each of the units (e.g., the CUs 910, the DUs 930, the RUs 940, as well as the Near-RT RICs 925, the Non-RT RICs 915 and the SMO Framework 905) may include one or more interfaces or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units, or an associated processor or controller providing instructions to the communication interfaces of the units, can be configured to communicate with one or more of the other units via the transmission medium. For example, the units can include a wired interface configured to receive or transmit signals over a wired transmission medium to one or more of the other units. Additionally, the units can include a wireless interface, which may include a receiver, a transmitter or transceiver (such as an RF transceiver), configured to receive or transmit signals, or both, over a wireless transmission medium to one or more of the other units.
In some aspects, the CU 910 may host one or more higher layer control functions. Such control functions can include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), or the like. Each control function can be implemented with an interface configured to communicate signals with other control functions hosted by the CU 910. The CU 910 may be configured to handle user plane functionality (i.e., Central Unit-User Plane (CU-UP)), control plane functionality (i.e., Central Unit-Control Plane (CU-CP)), or a combination thereof. In some implementations, the CU 910 can be logically split into one or more CU-UP units and one or more CU-CP units. The CU-UP unit can communicate bidirectionally with the CU-CP unit via an interface, such as the E1 interface when implemented in an O-RAN configuration. The CU 910 can be implemented to communicate with the DU 930, as necessary, for network control and signaling.
The DU 930 may correspond to a logical unit that includes one or more base station functions to control the operation of one or more RUs 940. In some aspects, the DU 930 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, or the like) depending, at least in part, on a functional split, such as those defined by the 3GPP. In some aspects, the DU 930 may further host one or more low PHY layers. Each layer (or module) can be implemented with an interface configured to communicate signals with other layers (and modules) hosted by the DU 930, or with the control functions hosted by the CU 910.
Lower-layer functionality can be implemented by one or more RUs 940. In some deployments, an RU 940, controlled by a DU 930, may correspond to a logical node that hosts RF processing functions, or low-PHY layer functions (such as performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, or the like), or both, based at least in part on the functional split, such as a lower layer functional split. In such an architecture, the RU(s) 940 can be implemented to handle over the air (OTA) communication with one or more UEs 120. In some implementations, real-time and non-real-time aspects of control and user plane communication with the RU(s) 940 can be controlled by the corresponding DU 930. In some scenarios, this configuration can enable the DU(s) 930 and the CU 910 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.
The SMO Framework 905 may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO Framework 905 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements which may be managed via an operations and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO Framework 905 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 990) to perform network element life cycle management (such as to instantiate virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements can include, but are not limited to, CUs 910, DUs 930, RUs 940 and Near-RT RICs 925. In some implementations, the SMO Framework 905 can communicate with a hardware aspect of a 4G RAN, such as an open eNB (O-eNB) 911, via an O1 interface. Additionally, in some implementations, the SMO Framework 905 can communicate directly with one or more RUs 940 via an O1 interface. The SMO Framework 905 also may include a Non-RT RIC 915 configured to support functionality of the SMO Framework 905.
The Non-RT RIC 915 may be configured to include a logical function that enables non-real-time control and optimization of RAN elements and resources, Artificial Intelligence/Machine Learning (AI/ML) workflows including model training and updates, or policy-based guidance of applications/features in the Near-RT RIC 925. The Non-RT RIC 915 may be coupled to or communicate with (such as via an A1 interface) the Near-RT RIC 925. The Near-RT RIC 925 may be configured to include a logical function that enables near-real-time control and optimization of RAN elements and resources via data collection and actions over an interface (such as via an E2 interface) connecting one or more CUs 910, one or more DUs 930, or both, as well as an O-eNB, with the Near-RT RIC 925.
In some implementations, to generate AI/ML models to be deployed in the Near-RT RIC 925, the Non-RT RIC 915 may receive parameters or external enrichment information from external servers. Such information may be utilized by the Near-RT RIC 925 and may be received at the SMO Framework 905 or the Non-RT RIC 915 from non-network data sources or from network functions. In some examples, the Non-RT RIC 915 or the Near-RT RIC 925 may be configured to tune RAN behavior or performance. For example, the Non-RT RIC 915 may monitor long-term trends and patterns for performance and employ AI/ML models to perform corrective actions through the SMO Framework 905 (such as reconfiguration via 01) or via creation of RAN management policies (such as A1 policies).
As indicated above,
The following provides an overview of some Aspects of the present disclosure:
Aspect 1: A method of wireless communication performed by a user equipment (UE), comprising: transmitting, on a physical uplink channel, repetitions without a demodulation reference signal (DMRS); and maintaining continuity for joint channel estimation of the repetitions without a DMRS during a first time domain window that is based at least in part on a second time domain window associated with joint channel estimation for repetitions with a DMRS.
Aspect 2: The method of Aspect 1, wherein the physical uplink channel includes a physical uplink control channel.
Aspect 3: The method of Aspect 1 or 2, wherein a length of the first time domain window and a length of the second time domain window are the same length.
Aspect 4: The method of any of Aspects 1-3, further comprising scaling, using a scaling factor, the first time domain window with respect to the second time domain window.
Aspect 5: The method of Aspect 4, wherein the scaling factor is less than 1.
Aspect 6: The method of Aspect 4, wherein the scaling factor is greater than 1.
Aspect 7: The method of any of Aspects 4-6, wherein the scaling factor is based at least in part on a format of communications on the physical uplink channel or a size of uplink control information on the physical uplink channel.
Aspect 8: The method of any of Aspects 4-7, further comprising obtaining the scaling factor from stored configuration information or from configuration information received from a network entity.
Aspect 9: The method of any of Aspects 1-8, wherein maintaining continuity includes maintaining phase continuity during the first time domain window.
Aspect 10: The method of any of Aspects 1-9, wherein maintaining continuity includes refraining from changing a time advance, a spatial filter configuration, or a precoding parameter during the first time domain window.
Aspect 11: The method of any of Aspects 1-10, further comprising transmitting a user equipment (UE) capability for maintaining continuity for the repetitions without a DMRS during the first time domain window.
Aspect 12: The method of Aspect 11, where the UE capability for maintaining continuity for the repetitions without a DMRS during the first time domain window is different than a UE capability for maintaining continuity for the repetitions with a DMRS.
Aspect 13: The method of Aspect 11 or 12, where the UE capability for maintaining continuity for the repetitions without a DMRS during the first time domain window is based at least in part on a UE capability for maintaining continuity for the repetitions with a DMRS.
Aspect 14: The method of any of Aspects 11-13, where the UE capability for maintaining continuity for the repetitions without a DMRS during the first time domain window is based at least in part on a format of communications on the physical uplink channel, an uplink control information size, a length of the communications on the physical uplink channel, or a length of an associated sequence set.
Aspect 15: The method of any of Aspects 1-14, further comprising determining to maintain continuity for the repetitions without a DMRS during the first time domain window based at least in part on a format of communications on the physical uplink channel, an uplink control information size, a length of the communications on the physical uplink channel, or a length of an associated sequence set.
Aspect 16: The method of any of Aspects 1-15, further comprising: transmitting, during the first time domain window on the physical uplink channel, repetitions with a DMRS in addition to the repetitions without a DMRS; and maintaining, during the first time domain window, continuity for the joint channel estimation of the repetitions with a DMRS in addition to the repetitions without a DMRS.
Aspect 17: A method of wireless communication performed by a network entity, comprising: enabling joint channel estimation of repetitions without a demodulation reference signal (DMRS) on a physical uplink channel based at least in part on joint channel estimation being enabled for repetitions with a DMRS; receiving, from a user equipment (UE), the repetitions without a DMRS on the physical uplink channel; and performing joint channel estimation of the repetitions without a DMRS within a first time domain window that is based at least in part on a second time domain window associated with joint channel estimation for repetitions with a DMRS.
Aspect 18: The method of Aspect 17, wherein the physical uplink channel includes a physical uplink control channel.
Aspect 19: The method of Aspect 17 or 18, further comprising transmitting a communication to the UE based at least in part on a result of performing the joint channel estimation of the repetitions without a DMRS.
Aspect 20: The method of any of Aspects 17-19, further comprising scaling, using a scaling factor, the first time domain window with respect to the second time domain window.
Aspect 21: The method of Aspect 20, wherein the scaling factor is less than 1.
Aspect 22: The method of Aspect 20, wherein the scaling factor is greater than 1.
Aspect 23: The method of any of Aspects 20-22, wherein the scaling factor is based at least in part on a format of communications on the physical uplink channel or a size of uplink control information on the physical uplink channel.
Aspect 24: The method of any of Aspects 20-23, further comprising transmitting the scaling factor in configuration information to the UE.
Aspect 25: The method of any of Aspects 17-24, further comprising determining to perform the joint channel estimation for the repetitions without a DMRS based at least in part on a format of communications on the physical uplink channel, an uplink control information size, a length of the communications on the physical uplink channel, or a length of an associated sequence set.
Aspect 26: The method of any of Aspects 17-25, further comprising: receiving, during the first time domain window on the physical uplink channel, repetitions with a DMRS in addition to the repetitions without a DMRS; and performing, during the first time domain window, the joint channel estimation of the repetitions with a DMRS in addition to the joint channel estimation of the repetitions without a DMRS.
Aspect 27: An apparatus for wireless communication at a device, comprising a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method of one or more of Aspects 1-26.
Aspect 28: A device for wireless communication, comprising a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method of one or more of Aspects 1-26.
Aspect 29: An apparatus for wireless communication, comprising at least one means for performing the method of one or more of Aspects 1-26.
Aspect 30: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method of one or more of Aspects 1-26.
Aspect 31: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method of one or more of Aspects 1-26.
The foregoing disclosure provides illustration and description but is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations may be made in light of the above disclosure or may be acquired from practice of the aspects.
As used herein, the term “component” is intended to be broadly construed as hardware and/or a combination of hardware and software. “Software” shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, and/or functions, among other examples, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. As used herein, a “processor” is implemented in hardware and/or a combination of hardware and software. It will be apparent that systems and/or methods described herein may be implemented in different forms of hardware and/or a combination of hardware and software. The actual specialized control hardware or software code used to implement these systems and/or methods is not limiting of the aspects. Thus, the operation and behavior of the systems and/or methods are described herein without reference to specific software code, since those skilled in the art will understand that software and hardware can be designed to implement the systems and/or methods based, at least in part, on the description herein.
As used herein, “satisfying a threshold” may, depending on the context, refer to a value being greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, or the like.
Even though particular combinations of features are recited in the claims and/or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features may be combined in ways not specifically recited in the claims and/or disclosed in the specification. The disclosure of various aspects includes each dependent claim in combination with every other claim in the claim set. As used herein, a phrase referring to “at least one of” a list of items refers to any combination of those items, including single members. As an example, “at least one of: a, b, or c” is intended to cover a, b, c, a+b, a+c, b+c, and a+b+c, as well as any combination with multiples of the same element (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c, and c+c+c, or any other ordering of a, b, and c).
No element, act, or instruction used herein should be construed as critical or essential unless explicitly described as such. Also, as used herein, the articles “a” and “an” are intended to include one or more items and may be used interchangeably with “one or more.” Further, as used herein, the article “the” is intended to include one or more items referenced in connection with the article “the” and may be used interchangeably with “the one or more.” Furthermore, as used herein, the terms “set” and “group” are intended to include one or more items and may be used interchangeably with “one or more.” Where only one item is intended, the phrase “only one” or similar language is used. Also, as used herein, the terms “has,” “have,” “having,” or the like are intended to be open-ended terms that do not limit an element that they modify (e.g., an element “having” A may also have B). Further, the phrase “based on” is intended to mean “based, at least in part, on” unless explicitly stated otherwise. Also, as used herein, the term “or” is intended to be inclusive when used in a series and may be used interchangeably with “and/or,” unless explicitly stated otherwise (e.g., if used in combination with “either” or “only one of”).
This patent application claims priority to U.S. Provisional Patent Application No. 63/262,333, filed on Oct. 8, 2021, entitled “JOINT CHANNEL ESTIMATION FOR REPETITIONS WITHOUT A DEMODULATION REFERENCE SIGNAL,” and assigned to the assignee hereof. The disclosure of the prior application is considered part of and is incorporated by reference into this patent application.
| Number | Date | Country | |
|---|---|---|---|
| 63262333 | Oct 2021 | US |
