Demodulation reference signal time domain mode configuration technology

Abstract

Various aspects of the present invention generally relate to wireless communications. In some aspects, a base station and / or a user device may determine a time domain resource pattern for a demodulation reference signal (DMRS) set, wherein the DMRS set is included in a type B physical downlink shared channel (PDSCH). Using a resource set determined at least in part based on the time domain resource pattern, the base station may transmit and the user device may receive the DMRS set. Many other aspects are also provided.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to Indian Patent Application No. 201941033074 filed on August 16, 2019, entitled “TECHNIQUES FOR DEMODULATION REFERENCE SIGNAL TIME DOMAIN PATTERNCONFIGURATION” and U.S. Non-provisional Application No. 16 / 947683 filed on August 12, 2020, entitled “TECHNIQUES FOR DEMODULATION REFERENCE SIGNAL TIME DOMAIN PATTERNCONFIGURATION”, which are expressly incorporated herein by reference. Technical Field

[0003] Aspects of the present invention generally relate to wireless communications and techniques and apparatus for demodulation reference signal time domain pattern configuration. Background Art

[0004] Wireless communication systems are widely used to provide various telecommunication services, such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). 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 series of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP).

[0005] A wireless communication network may include multiple base stations (BS) that may support communication of multiple user equipments (UEs). User equipments (UEs) may communicate with base stations (BSs) via downlinks and uplinks. A downlink (or forward link) refers to a communication link from a BS to a UE, and an uplink (or reverse link) refers to a communication link from a UE to a BS. As will be described in more detail herein, a BS may be referred to as a Node B, gNB, access point (AP), radio head, transmit receive point (TRP), new radio (NR) BS, 5G Node B, etc.

[0006] The above-mentioned multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different user devices to communicate at municipal, national, regional and even global levels. New Radio (NR), which can also be referred to as 5G, is a set of enhancements to the LTE mobile standard promulgated by the Third Generation Partnership Project (3GPP). NR is designed to better support mobile broadband Internet access by improving spectrum efficiency, reducing costs, improving services, utilizing new spectrum, and using orthogonal frequency division multiplexing (OFDM) with cyclic prefix (CP) (CP-OFDM) on the downlink (DL), using CP-OFDM and / or SC-FDM (e.g., also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink (UL), and supporting beamforming, multiple input multiple output (MIMO) antenna technology and carrier aggregation to better integrate with other open standards. However, as the demand for mobile broadband access continues to grow, LTE and NR technologies need further improvement. Preferably, these improvements should be applicable to other multiple access technologies and telecommunication standards that adopt these technologies. Summary of the invention

[0007] In some aspects, a method of wireless communication performed by a user equipment (UE) may include determining a time domain resource pattern for a demodulation reference signal (DMRS) set, wherein the DMRS set is included in a type B physical downlink shared channel (PDSCH); and receiving the DMRS set using a resource set determined at least in part based on the time domain resource pattern.

[0008] In some aspects, a wireless communication method performed by a base station (BS) may include determining a time domain resource pattern for a DMRS set included in a type B PDSCH; and sending the DMRS set using a resource set determined at least in part based on the time domain resource pattern.

[0009] In some aspects, a UE for wireless communication may include a memory and one or more processors operatively coupled to the memory. The memory and the one or more processors may be configured to determine a time domain resource pattern for a DMRS set, wherein the DMRS set is included in a type B PDSCH; and receive the DMRS set using a resource set determined at least in part based on the time domain resource pattern.

[0010] In some aspects, a BS for wireless communication may include a memory and one or more processors operatively coupled to the memory. The memory and the one or more processors may be configured to determine a time domain resource pattern for a DMRS set, wherein the DMRS set is included in a type B PDSCH; and transmit the DMRS set using a resource set determined at least in part based on the time domain resource pattern.

[0011] In some aspects, a non-transitory computer-readable medium may store one or more instructions for wireless communication. When executed by one or more processors of a UE, the one or more instructions may cause the one or more processors to determine a time domain resource pattern for a DMRS set, wherein the DMRS set is included in a type B PDSCH; and receive the DMRS set using a resource set determined at least in part based on the time domain resource pattern.

[0012] In some aspects, a non-transitory computer-readable medium may store one or more instructions for wireless communication. When executed by one or more processors of a BS, the one or more instructions may cause the one or more processors to determine a time domain resource pattern for a DMRS set, wherein the DMRS set is included in a type B PDSCH; and transmit the DMRS set using a resource set determined at least in part based on the time domain resource pattern.

[0013] In some aspects, an apparatus for wireless communication may include means for determining a time domain resource pattern for a DMRS set included in a Type B PDSCH and means for receiving the DMRS set using a resource set determined at least in part based on the time domain resource pattern.

[0014] In some aspects, an apparatus for wireless communication may include means for determining a time domain resource pattern for a DMRS set included in a Type B PDSCH and means for transmitting the DMRS set using a resource set determined at least in part based on the time domain resource pattern.

[0015] In some aspects, the time-domain resource pattern is based at least in part on another time-domain resource pattern for another uplink or downlink signal.

[0016] In some aspects, the time-domain resource pattern is based at least in part on an interpolation-reduction rule or an extrapolation-reduction rule.

[0017] In some aspects, the time domain resource pattern is based at least in part on a first number of control resource set (CORESET) symbols and a second number of non-CORESET symbols.

[0018] In some aspects, the time domain resource pattern is based at least in part on a reference time domain resource pattern for another DMRS set included in a type-B physical uplink shared channel (PUSCH).

[0019] In some aspects, a reference time-domain resource pattern for another DMRS set included in a Type-B PUSCH is based at least in part on a number of non-CORESET symbols.

[0020] In some aspects, a reference time-domain resource pattern for another DMRS set included in a Type-B PUSCH is based at least in part on a total number of symbols including CORESET symbols and non-CORESET symbols.

[0021] In some aspects, the time-domain resource pattern is based at least in part on a shift applied to a reference time-domain resource pattern.

[0022] In some aspects, the shifting is based at least in part on the number of CORESET symbols.

[0023] In some aspects, a last DMRS from a DMRS set is dropped based at least in part on a number of non-CORESET symbols and a number of symbols of the DMRS of the DMRS set.

[0024] In some aspects, the time domain resource pattern includes a shift applied to a last DMRS of a DMRS set based at least in part on a PDSCH duration (in symbols), a number of DMRSs of the DMRS set, and a gap criterion between a first DMRS and a last DMRS of the DMRS set.

[0025] In some aspects, the time domain resource pattern includes a shift of multiple DMRSs applied to a DMRS set based at least in part on at least one of a number of non-CORESET symbols, a starting symbol of a sequence, an interpolation reduction rule, an extrapolation reduction rule, a gap criterion, or a symbol number criterion.

[0026] In some aspects, the determination of the time-domain resource pattern includes determining the time-domain resource pattern based at least in part on a stored data structure identifying the time-domain resource pattern.

[0027] In some aspects, the determination of the time-domain resource pattern includes determining the time-domain resource pattern based at least in part on a time-domain resource pattern generation process.

[0028] In some aspects, the time domain resource pattern includes a dropped DMRS configured for symbols greater than a threshold number of symbols after a starting symbol of the sequence.

[0029] Aspects generally include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, wireless communication devices, and / or processing systems as substantially described herein with reference to and as illustrated by the accompanying drawings and description.

[0030] The foregoing has been a fairly broad overview of the features and technical advantages of examples according to the present invention, so that the following detailed description is better understood. Other features and advantages will be described below. The disclosed concepts and specific examples can be easily used as a basis for modifying or designing other structures to achieve the same purpose of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. When considered in conjunction with the accompanying drawings, the features of the concepts disclosed herein, their organization and methods of operation, and related advantages will be better understood from the following description. Each of the accompanying drawings is provided for the purpose of illustration and description, and not as a definition of the claims limitation. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] In order to be able to understand the above-mentioned features of the present disclosure in detail, a more specific description briefly summarized above may be made by reference to some aspects, some of which are shown in the accompanying drawings. However, it should be noted that the accompanying drawings only illustrate certain typical aspects of the present invention and should not be considered to limit its scope, as the present specification may admit of other equally effective aspects. The same reference numbers in different figures may identify the same or similar elements.

[0032] Figure 1 is a diagram illustrating an example of a wireless communication network according to various aspects of the present disclosure.

[0033] Figure 2 is a diagram illustrating an example of a base station communicating with a UE in a wireless communication network according to various aspects of the present disclosure.

[0034] Figures 3A-3E is a diagram illustrating an example of a time domain resource pattern for a DMRS according to various aspects of the present invention.

[0035] Figure 4 is a diagram illustrating an example of a time domain resource pattern for a DMRS according to various aspects of the present disclosure.

[0036] Figure 5 is a diagram illustrating an example of a time domain resource pattern for a DMRS according to various aspects of the present disclosure.

[0037] Figure 6 is a diagram illustrating an example of time domain resource pattern shifting according to various aspects of the present disclosure.

[0038] Figures 7A-7E is a diagram illustrating an example of time domain resource pattern shifting according to various aspects of the present disclosure.

[0039] Figure 8 is a diagram illustrating an example process performed, for example, by a user device according to various aspects of the present disclosure.

[0040] Fig. 9is a diagram illustrating example processes performed, for example, by a base station according to various aspects of the present disclosure.

[0041] Fig.10 is a conceptual data flow diagram illustrating the flow of data between different modules / components / assemblies in an example apparatus according to various aspects of the present disclosure.

[0042] Fig.11 is a conceptual data flow diagram illustrating the flow of data between different modules / components / assemblies in an example apparatus according to various aspects of the present disclosure. DETAILED DESCRIPTION

[0043] Various aspects of the present invention are described more fully below with reference to the accompanying drawings. However, the present invention can be embodied in many different forms and should not be construed as being limited to any particular structure or function presented in the present invention. On the contrary, these aspects are provided so that the present disclosure will be thorough and complete, and will fully convey the scope of the present disclosure to those skilled in the art. Based at least in part on the teachings herein, it should be understood by those skilled in the art that the scope of the present invention is intended to cover any aspect disclosed herein, whether independent of any other aspect of the present invention or implemented in combination with any other aspect of the present invention. For example, any number of aspects described herein may be used to implement a device or practice method. In addition, the scope of the present invention is intended to cover such a device or method that is implemented using other structures, functions, or structures and functions outside the various aspects of the present invention described herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of the claims.

[0044] Several aspects of telecommunication systems will now be described with reference to various devices and techniques. These devices 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 and / or the like (collectively referred to as "elements"). These elements may be implemented using hardware, software, or a combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and design constraints imposed on the overall system.

[0045] It should be noted that although aspects may be described herein using terminology generally associated with 3G and / or 4G wireless technologies, aspects of the present disclosure may be applied to other generation-based communication systems, such as 5G and beyond, including NR technologies.

[0046] Figure 11 is a diagram illustrating a wireless network 100 in which various aspects of the present disclosure may be practiced. The wireless network 100 may be an LTE network or some other wireless network, such as a 5G or NR network. The wireless network 100 may include a plurality of BSs 110 (shown as BS 110a, BS 110b, BS 110c, and BS 110d) and other network entities. A BS is an entity that communicates with a user equipment (UE) and may also be referred to as a base station, NR BS, Node B, gNB, 5G Node B (NB), access point, transmit receive point (TRP), etc. Each base station may provide communication coverage for a particular geographic area. In 3GPP, the term "cell" may refer to the coverage area of ​​a BS and / or BS subsystem serving that coverage area, depending on the context in which the term is used.

[0047] A BS 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., a radius of several kilometers) and may allow unrestricted access by UEs through service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs through service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UEs associated with the femto cell (e.g., UEs in a closed subscriber group (CSG)). A BS for a macro cell may be referred to as a macro BS. A BS for a pico cell may be referred to as a pico BS. A BS for a femto cell may be referred to as a femto BS or a home BS. In Figure 1 In the example shown, BS 110a may be a macro BS for macro cell 102a, BS 110b may be a pico BS for pico cell 102b, and BS 110c may be a pico BS for pico cell 102c. A base station may support one or more (e.g., three) cells. The terms "eNB", "base station", "NR BS", "gNB", "TRP", "AP", "Node B", "5G NB", and "cell" may be used interchangeably herein.

[0048] In some aspects, the cells are not necessarily stationary, and the geographic area of ​​the cells may move according to the location of the mobile BS. In some aspects, any suitable transport network may be used to interconnect the BSs to each other and / or to one or more other BSs or network nodes (not shown) in the wireless network 100 through various types of backhaul interfaces such as direct physical connections, virtual networks, etc.

[0049] The wireless network 100 may also include a relay station (relay BS). A relay station is an entity that can receive data transmissions from an upstream station (e.g., a BS or UE) and send data transmissions to a downstream station (e.g., a UE or BS). A relay station may also be a UE that can relay transmissions for other UEs. Figure 1 In the example shown, relay BS 110d may communicate with macro BS 110a and UE 120d to facilitate communication between BS 110a and UE 120d. A relay station may also be referred to as a relay BS, relay base station, relay, or the like.

[0050] The wireless network 100 may be a heterogeneous network including different types of BSs, such as macro BSs, pico BSs, femto BSs, relay BSs, etc. These different types of BSs may have different transmit power levels, different coverage areas, and different effects on interference in the wireless network 100. For example, a macro base station may have a high transmit power level (e.g., 5 to 40 watts), while a pico base station, a femto base station, and a relay base station may have a lower transmit power level (e.g., 0.1 to 2 watts).

[0051] A network controller 130 may be coupled to a set of BSs and may provide coordination and control for these BSs. The network controller 130 may communicate with the BSs via a backhaul. The BSs may also communicate with each other, for example, directly or indirectly via a wireless or wired backhaul.

[0052] UEs 120 (e.g., 120a, 120b, 120c, 120d, 120e) may be dispersed throughout the wireless network 100, and each UE may be fixed or mobile. UEs may also be referred to as access terminals, terminals, mobile stations, subscriber units, stations, etc. UEs may be cellular phones (e.g., smart phones), personal digital assistants (PDAs), wireless modems, wireless communication devices, handheld devices, laptop computers, cordless phones, wireless local loop (WLL) stations, tablet computers, cameras, gaming devices, netbooks, smartbooks, ultrabooks, medical devices or equipment, biometric sensors / devices, wearable devices (smart watches, smart clothing, smart glasses, smart wristbands, smart jewelry (e.g., smart rings, smart bracelets)), entertainment devices (e.g., music or video devices or satellite radios), vehicle components or sensors, smart meters / sensors, industrial manufacturing equipment, global positioning system devices, or any other suitable device configured to communicate via wireless or wired media.

[0053] Some UEs may be considered as machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) UEs. MTC and eMTC UEs include, for example, robots, drones, remote devices, sensors, meters, monitors, location tags, etc., which may communicate with a base station, another device (e.g., a remote device), or some other entity. For example, a wireless node may provide a connection to or to a network (e.g., a wide area network such as the Internet or a cellular network) via a wired or wireless communication link. Some UEs may be considered as Internet of Things (IoT) devices, and / or may be implemented as NB-IoT (narrowband Internet of Things) devices. Some UEs may be considered as customer premises equipment (CPE). UE 120 may be included in a housing that houses components of UE 120 (such as processor components, memory components, etc.).

[0054] Generally, any number of wireless networks can be deployed in a given geographic area. Each wireless network can support a specific RAT and can operate on one or more frequencies. RAT can also be referred to as radio technology, air interface, etc. Frequency can also be referred to as carrier, frequency channel, etc. Each frequency can support a single RAT in a given geographic area to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks can be deployed.

[0055] In some aspects, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly (e.g., without using base station 110 as an intermediary to communicate with each other) using one or more sidelink channels. For example, UE 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, etc.), mesh networks, etc. In this case, UE 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by base station 110.

[0056] As mentioned above, providing Figure 1 As an example. Other examples may differ from Figure 1 An example of description.

[0057] Figure 2 A block diagram of a design 200 of a base station 110 and a UE 120 is shown, which may be Figure 1 Base station 110 may be equipped with T antennas 234a through 234t, and UE 120 may be equipped with R antennas 252a through 252r, where in general T ≥ 1 and R ≥ 1.

[0058] At the base station 110, the transmit processor 220 may receive data for one or more UEs from the data source 212, select one or more modulation and coding schemes (MCS) for each UE based at least in part on a channel quality indicator (CQI) received from the UE, process (e.g., encode and modulate) the data for each UE based at least in part on the MCS selected for the UE, and provide data symbols for all UEs. The transmit processor 220 may also process system information (e.g., for semi-static resource partitioning information (SRPI), etc.) and control information (e.g., CQI requests, grants, upper layer signaling, etc.), and provide overhead symbols and control symbols. The transmit processor 220 may also generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS)) and synchronization signals (e.g., primary synchronization signals (PSS) and secondary synchronization signals (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols (if applicable), and may provide T output symbol streams to T modulators (MOD) 232a to 232t. Each modulator 232 may process a respective output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Each modulator 232 may also process (e.g., convert to analog, amplify, filter, and up-convert) the output sample stream to obtain a downlink signal. The T downlink signals from modulators 232a to 232t may be transmitted via T antennas 234a to 234t, respectively. According to various aspects described in more detail below, position coding may be used to generate synchronization signals to transmit additional information.

[0059] At UE 120, antennas 252a to 252r may receive downlink signals from base station 110 and / or other base stations, and may provide received signals to demodulators (DEMOD) 254a to 254r, respectively. Each demodulator 254 may adjust (e.g., filter, amplify, down-convert, and digitize) received signals to obtain input samples. Each demodulator 254 may also process input samples (e.g., for OFDM) to obtain received symbols. MIMO detector 256 may obtain received symbols from all R demodulators 254a to 254r, perform MIMO detection on received symbols where applicable, and provide detected symbols. Receive processor 258 may process (e.g., demodulate and decode) detected symbols, provide decoded data for UE 120 to data sink 260, and provide decoded control information and system information to controller / processor 280. Channel processor may determine reference signal received power (RSRP), received signal strength indicator (RSSI), reference signal received quality (RSRQ), channel quality indicator (CQI), etc. In some aspects, one or more components of UE 120 may be included in a housing.

[0060] On the uplink, at the UE 120, a transmit processor 264 may receive and process data from a data source 262 and control information from a controller / processor 280 (e.g., for reports including RSRP, RSSI, RSRQ, CQI, etc.). The transmit processor 264 may also 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 modulators 254a through 254r (e.g., for DFT-s-OFDM, CP-OFDM, etc.), and transmitted to the base station 110. At the base station 110, uplink signals from the UE 120 and other UEs may be received by antennas 234, processed by demodulators 232, detected by MIMO detectors 236 (if applicable), and further processed by receive processors 238 to obtain decoded data and control information transmitted by the UE 120. The receive processor 238 may provide the decoded data to a data sink 239 and the decoded control information to the controller / processor 240. The base station 110 may include a communication unit 244 and communicate with the network controller 130 via the communication unit 244. The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292.

[0061] The controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other components of the base station 110 may perform one or more techniques associated with demodulation reference signal time domain pattern configuration, as described in more detail elsewhere herein. For example, the controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component of the can execute or guide e.g. Figure 8 The process of 800 Fig. 9 900 and / or other processes described herein. Memories 242 and 282 may store data and program codes for base station 110 and UE 120, respectively. In some aspects, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions for wireless communication. For example, when executed by one or more processors of base station 110 and / or UE 120, the one or more instructions may execute or direct, for example, Figure 8 The process of 800 Fig. 9 The scheduler 246 may schedule UEs for data transmission on the downlink and / or uplink.

[0062] In some aspects, UE 120 may include: means for determining a time domain resource pattern for a demodulation reference signal (DMRS) set, wherein the DMRS set is included in a type B physical downlink shared channel (PDSCH); means for receiving the DMRS set using a resource set determined at least in part based on the time domain resource pattern, etc. In some aspects, such means may include combining Figure 2 One or more components of UE 120 are depicted, such as controller / processor 280, transmit processor 264, TX MIMO processor 266, MOD 254, antenna 252, demodulator 254, MIMO detector 256, receive processor 258, etc.

[0063] In some aspects, base station 110 may include: means for determining a time domain resource pattern for a DMRS set, wherein the DMRS set is included in a type B PDSCH; means for transmitting the DMRS set using a resource set determined at least in part based on the time domain resource pattern, etc. In some aspects, such means may include combining Figure 2 One or more components of the base station 110 are depicted, such as an antenna 234, a demodulator 232, a MIMO detector 236, a receive processor 238, a controller / processor 240, a transmit processor 220, a TX MIMO processor 230, a MOD 232, an antenna 234, and the like.

[0064] As mentioned above, providing Figure 2 As an example. Other examples may differ from Figure 2 An example of description.

[0065] As described in more detail below, in some communication systems such as NR, a time domain resource pattern may be defined for a DMRS. A start and length indicator vector (SLIV) may be used to identify a time domain resource pattern, the SLIV identifying a starting symbol S and a length L (e.g., L may be the length or duration of a sequence) of at least one DMRS. For example, for a type B PUSCH, a time domain resource pattern may be defined for each possible length of a type B PUSCH. In this case, a type B PUSCH may have a time domain resource pattern defined for a starting symbol S = {0, ..., 13} and a length L = {1, ..., 14} such that S + L ≤ 14. Similarly, a type A PDSCH may be scheduled for a starting symbol S = {0, 1, 2, 3} and a length L = {3, ..., 14} such that 3 ≤ S + L ≤ 14. A device such as a UE and / or a BS may store a data structure such as a lookup table that may define, for example, DMRS positions for type A PDSCH, type B PUSCH, and the like.

[0066] Type B PDSCH may be scheduled for starting symbol S = {0, ..., 12} and length L = {2, 4, 7} such that 2 ≤ S + L ≤ 14. In Type B PDSCH, single symbol DMRS may support L = 2, where the DMRS is located at symbol index I = {0, 1}. Similarly, for L = 4, the single symbol DMRS may be located at symbol index {I = 0, 1}. Similarly, for L = 7, the single symbol DMRS may be located at symbol index I = {2, 3}. For Type B PDSCH, dual symbol (also referred to as "two symbol") DMRS may also be supported, such that for two symbol DMRS, L = 7 and symbol index I = {(0, 4), (1, 5)}.

[0067] However, Type B PDSCH may not support other durations. In addition, for different durations of Type B PDSCH, dual-symbol DMRS may not be supported. It may be advantageous to reuse an existing channel estimation interpolation table that may correspond to an existing time domain resource pattern. However, for Type B PDSCH, using a Type B PUSCH time domain resource pattern may not be sufficient to meet all use cases because the PDSCH may have a control resource set (CORESET) symbol at the beginning of the PDSCH, which does not occur for the PUSCH. In addition, the Type B PUSCH time domain resource pattern may not meet the criteria that are favorable to Type B PDSCH. For example, the Type B PUSCH time domain resource pattern may have a DMRS gap greater than 8 symbols. In addition, when applied to Type B PDSCH, the Type B PUSCH time domain resource pattern may have symbols greater than a threshold number (e.g., greater than 2), which will be extrapolated after the last DMRS of the sequence. This characteristic may cause the receiver complexity of receiving the DMRS and the associated Type B PDSCH to be too large (e.g., UE complexity), which may lead to excessive utilization of processing resources.

[0068] Thus, some aspects described herein define time domain resource patterns for a number of symbols from 2 symbols to 13 symbols for a Type B PDSCH. Additionally, some aspects provide time domain resource patterns for a dual symbol DMRS for a Type B PDSCH. In some aspects, the time domain resource patterns defined herein for a Type B PDSCH may satisfy one or more criteria, such as a DMRS gap of less than or equal to 8 symbols, a maximum number of symbols for extrapolation of less than or equal to 2 symbols, etc. Although some aspects are described herein in terms of a procedural determination of a time domain resource pattern, other aspects are also contemplated, such as a data structure (e.g., a lookup table) identifying a time domain resource pattern for a given set of parameters as described herein.

[0069] In some aspects, a UE (e.g., UE 120) and / or a BS (e.g., BS 110) may determine a time domain resource pattern for a type B PDSCH of length L = {5, 13} based at least in part on other uplink or downlink time domain patterns described herein (e.g., type APDSCH, type B PUSCH, etc.). In this case, as described herein, the UE and / or BS may shift other uplink or downlink time domain resource patterns to minimize interpolation and / or extrapolation of the UE. In some aspects, the UE and / or BS may determine the time domain resource pattern using a set of rules. For example, for a type B PDSCH having J CORESET symbols and K non-CORESET symbols, such that J+K=L (e.g., where L is the duration of the type B PDSCH), the UE and / or BS may select a type B PUSCH time domain resource pattern having K symbols, and shift the type B PUSCH time domain resource pattern by J CORESET symbols to determine the type B PDSCH time domain resource pattern.

[0070] As another example, when there are K=5 non-CORESET symbols and 2 single-symbol DMRS are configured, the BS and / or UE may discard the last DMRS of the 2 single-symbol DMRS. As another example, when there are K=12 non-CORESET symbols and the number of single-symbol DMRS is greater than 1, the BS and / or UE may shift the last DMRS symbol to ensure that the DMRS gap is less than or equal to 8 symbols, thereby satisfying the interpolation reduction rule and allowing the use of the type APDSCH channel estimation interpolation matrix as described herein. As another example, when there are K=13 non-CORESET symbols and the number of configured DMRS is greater than 1, the first one or more DMRS symbols may be shifted to satisfy the interpolation reduction rule and the extrapolation reduction rule, but will result in non-frontload DMRS (e.g., the first DMRS of the DMRS set is located after the first non-CORESET symbol).

[0071] Figures 3A-3E 300-340 are examples of time domain resource patterns for DMRS. The time domain resource pattern may define the location of DMRS relative to, for example, CORESET symbols, PDSCH without DMRS, non-PDSCH symbols, etc. Figures 3A-3E shown.

[0072] like Figure 3AAs shown in Example 300, a time domain resource pattern set is defined for a type A PDSCH single symbol DMRS. For example, a first time domain resource pattern set is defined for 2 DMRS in a type A PDSCH, each having 2 CORESET symbols or 3 CORESET symbols and non-CORESET symbols having K symbols from 7 to 12 and 6 to 11. Similarly, a second time domain resource pattern set is defined for 3 DMRS in a type A PDSCH, each having 2 CORESET symbols or 3 CORESET symbols and non-CORESET symbols having K symbols from 8 to 12 and 7 to 11. Similarly, a first time domain resource pattern set is defined for 4 DMRS in a type A PDSCH, each having 2 CORESET symbols and non-CORESET symbols having K symbols from 10 to 12. As shown in the figure, in the time domain resource location pattern, some symbols are not allocated for PDSCH.

[0073] like Figure 3B As shown in example 310, a time domain resource pattern set is defined for type A PDSCH dual-symbol DMRS. For example, a time domain resource pattern set is defined for 2 DMRS in type A PDSCH with 2 CORESET symbols or 3 CORESET symbols and non-CORESET symbols with K symbols from 8 to 12 and 7 to 11, respectively.

[0074] like Figure 3C As shown in Example 320, a time domain resource pattern set is defined for a type B PDSCH single symbol DMRS. For example, a first time domain resource pattern set is defined for a type B PDSCH without a CORESET symbol and with a length L (and the number of non-CORESET symbols K) of 7, 4, and 2. In this case, for the first length, the time domain resource pattern may include two DMRSs, and for the second and third lengths, the time domain resource pattern may include one DMRS. Similarly, a second time domain resource pattern set is defined for 1 CORESET symbol and a length L of 7, 4, and 2, and the number of non-CORESET symbols K is 6, 3, and 1, respectively. In this case, for the first length, the time domain resource pattern may include two DMRSs, and for the second and third lengths, the time domain resource pattern may include one DMRS. Similarly, a third time domain resource pattern set is defined for 2 CORESET symbols and a length L of 7 and 4, and the number of non-CORESET symbols K is 5 and 2, respectively. In this case, for the first and second lengths, the time domain resource pattern may include one DMRS. Similarly, the fourth time domain resource pattern set is defined for 3 CORESET symbols and a length L of 4 symbols and a number K of non-CORESET symbols of 4 symbols. In this case, the time domain resource pattern may include one DMRS.

[0075] like Figure 3D As shown, through example 330, time domain resource pattern sets are defined for type B PUSCH single symbol DMRS. For example, a first time domain resource pattern set is defined for 2 DMRS with a length L of 5 to 13 symbols in type A PUSCH. Similarly, a second time domain resource pattern set is defined for 3 DMRS with a length L of 8 to 13 symbols in type B PUSCH. Similarly, a third time domain resource pattern set is defined for 4 DMRS with a length L of 10 to 12 symbols in type B PUSCH.

[0076] like Figure 3E As shown, a time domain resource pattern set is defined for a Type B PUSCH dual symbol DMRS by example 340. For example, a time domain resource pattern set is defined for 2 DMRS with a length L of 8 to 13 symbols in a Type B PUSCH.

[0077] As mentioned above, Figures 3A-3E are provided as examples. Other examples may differ from those described in Figures 3A-3E Description.

[0078] Figure 4 is a set of examples 400-414 of time domain resource pattern sets for type B PDSCH. Figure 4 As shown, time domain resource pattern sets are available for lengths 12 and 13.

[0079] like Figure 4 As shown in example 400, a time domain resource pattern for a type B PDSCH having 2 single-symbol DMRS and a length L of 12 symbols may be defined based at least in part on a shift relative to a type B PUSCH time domain resource pattern, as described above. In some aspects, the 2 DMRS may be located at positions {m, m+9}, where m is the first non-CORESET PDSCH symbol. For example, as shown in reference number 401, the last DMRS of the time domain resource pattern is shifted to an earlier symbol relative to the type B PUSCH time domain resource pattern. Similarly, as shown in example 402, as described above, a time domain resource pattern for a type B PDSCH having 2 single-symbol DMRS and a length L of 13 symbols may be defined based at least in part on a shift relative to a type B PUSCH time domain resource pattern. In some aspects, the 2 DMRS may be located at positions {m+1, m+10}, where m is the first non-CORESET PDSCH symbol. For example, as indicated by reference numeral 403, the first DMRS of the time domain resource pattern is shifted to a later symbol relative to the type BPUSCH time domain resource pattern.

[0080] like Figure 4 As further shown in example 404, a time domain resource pattern for a type B PDSCH having 3 single-symbol DMRS and a length L of 12 symbols can be defined based at least in part on a shift relative to a type B PUSCH time domain resource pattern, as described above. In some aspects, the 3 DMRS can be located at positions {m, m+5, m+9}, where m is the first non-CORESET PDSCH symbol. For example, as shown in reference number 405, the last DMRS of the time domain resource pattern is shifted to an earlier symbol relative to the type B PUSCH time domain resource pattern. In this way, the type B PDSCH time domain resource pattern is defined so that a receiver (e.g., UE 120) can reuse a type A PDSCH channel estimation interpolation / extrapolation matrix, thereby reducing memory utilization. In addition, by shifting the last DMRS symbol, the type B PDSCH time domain resource pattern maintains front loading (e.g., including the DMRS in the first symbol in sequence), thereby reducing latency.

[0081] Similarly, as shown in example 406, as described above, a time domain resource pattern for a type B PDSCH having 3 single-symbol DMRS and a length L of 13 symbols can be defined based at least in part on a shift relative to a type B PUSCH time domain resource pattern. In some aspects, the 3 DMRS can be located at positions {m+1, m+6, m+10}, where m is the first non-CORESET PDSCH symbol. For example, as shown in reference numbers 407-1 and 407-2, the first DMRS and the second DMRS of the time domain resource pattern are each shifted to a subsequent symbol relative to the type B PUSCH time domain resource pattern. In this manner, the type B PDSCH time domain resource pattern is defined so that a receiver (e.g., UE 120) can reuse a type A PDSCH channel estimation interpolation matrix, thereby reducing memory utilization.

[0082] like Figure 4As further shown in Example 408, a time domain resource pattern for a Type B PDSCH having 4 single-symbol DMRS and a length L of 12 symbols can be defined without shifting relative to a Type B PUSCH time domain resource pattern, as described above. In some aspects, the 4 DMRS can be located at positions {m, m+3, m+5, m+9}, where m is the first non-CORESET PDSCH symbol. In contrast, as shown in Example 410, a second time domain resource pattern for a Type B PDSCH having 4 single-symbol DMRS with a length L of 13 symbols can be defined based at least in part on a shift relative to a Type B PUSCH time domain resource pattern, as described above. In some aspects, the 4 DMRS can be located at positions {m+1, m+4, m+7, m+10}, where m is the first non-CORESET PDSCH symbol. For example, as shown in reference numbers 411-1, 411-2, 411-3, and 411-4, each DMRS of the time domain resource pattern is shifted to a later symbol relative to the type B PUSCH time domain resource pattern. In this way, the type B PDSCH time domain resource pattern is defined so that a receiver (e.g., UE 120) can reuse the type A PDSCH channel estimation interpolation matrix, thereby reducing memory utilization.

[0083] like Figure 4 As further shown in example 412, as described above, a time domain resource pattern of a type B PDSCH having 2 dual-symbol DMRS and a length L of 12 symbols may be defined based at least in part on a shift relative to a type B PUSCH time domain resource pattern. In some aspects, the 2 dual-symbol DMRS may be located at positions {m, m+1, m+8, m+9}, where m is the first non-CORESET PDSCH symbol. For example, as shown in reference number 413, the symbol of the last DMRS of the time domain resource pattern is shifted to an earlier symbol relative to the type B PUSCH time domain resource pattern. Similarly, as shown in example 414, as described above, a time domain resource pattern of a type B PDSCH having 2 dual-symbol DMRS and a length L of 13 symbols may be defined based at least in part on a shift relative to a type B PUSCH time domain resource pattern. In some aspects, the 2 dual-symbol DMRS may be located at positions {m+1, m+2, m+9, m+10}, where m is the first non-CORESET PDSCH symbol. For example, as indicated by reference numeral 415, the first two DMRS symbols of the second time domain resource pattern are shifted to later symbols relative to the type-B PUSCH time domain resource pattern.

[0084] As mentioned above, Figure 4 Examples are depicted. Other examples may differ from those described in Figure 4 An example of description.

[0085] Figure 5 is a set of examples 500-512 of time domain resource pattern sets for Type B PDSCH.

[0086] like Figure 5 As shown in example 500, a time domain resource pattern of a type B PDSCH having two single-symbol DMRS and a length L of 9 symbols may be defined based at least in part on a shift relative to a type B PUSCH time domain resource pattern (e.g., an 8-symbol type B PUSCH time domain resource pattern), as described above. For example, as shown in reference numeral 501, the DMRS of the first time domain resource pattern is shifted to a later symbol relative to the type B PUSCH time domain resource pattern to accommodate a CORESET symbol at the beginning of the type B PDSCH.

[0087] like Figure 5 As further shown in example 502, a time domain resource pattern of a type B PDSCH having 1 single-symbol DMRS and a length L of 5 symbols can be defined based at least in part on discarding DMRS relative to a type B PUSCH time domain resource pattern (e.g., a 5-symbol type B PUSCH time domain resource pattern), as described above. For example, as shown by reference number 503, the last DMRS of the type B PUSCH time domain resource pattern can be discarded (or replaced by a PDSCH data symbol) to accommodate the PDSCH symbol in the time domain resource pattern for the type B PDSCH. In this case, even if 2 single-symbol DMRS are configured, only the first front-load DMRS is retained.

[0088] like Figure 5 As shown, through examples 506 and 508, a set of time domain resource patterns for a type B PDSCH having 2 single-symbol DMRSs and a DMRS gap of 9 symbols can be defined based at least in part on a shift relative to a type BPUSCH time domain resource pattern, as described above. For example, as shown in example 508 and reference number 509, for length 12, the last DMRS is shifted to an earlier symbol relative to the type BPUSCH time domain resource pattern. By using a shifted version of the type B PUSCH time domain resource pattern for the type B PDSCH pattern, a receiver (e.g., UE 120) can use the same interpolation / extrapolation matrix for channel estimation when using the type B PDSCH pattern as when using the type A PDSCH time domain resource pattern, thereby reducing the utilization of memory resources.

[0089] like Figure 5As further shown, through examples 510 and 512, a time domain resource pattern of a type B PDSCH having 1 single symbol DMRS and a length L of 3 symbols can be defined. For example, as shown by reference number 511, the first DMRS of the first time domain resource pattern is shifted to a later symbol relative to the type B PUSCH time domain resource pattern to accommodate the CORESET symbol at the beginning of the type B PDSCH. Conversely, when there is no CORESET symbol at the beginning of the type B PDSCH, the DMRS can be located in the first symbol of the second time domain resource pattern, as shown in example 512.

[0090] As mentioned above, providing Figure 5 As an example. Other examples may differ from Figure 5 An example of description.

[0091] Figure 6 600 is an example of a time domain resource pattern shift. For example, UE 120 or BS 110 may shift a DMRS pilot pattern to define a time domain resource pattern for a Type B PDSCH. As described above, although some aspects are described according to a set of steps, UE 120 and / or BS 110 may use stored information (such as a stored lookup table) to determine a time domain resource pattern. Figure 6 As shown, example 600 is a Type B PDSCH with a length L of 9 symbols and configured with 2 DMRS.

[0092] In some aspects, to determine the DMRS pattern, a device (e.g., BS 110 and / or UE 120) may select a DMRS pilot pattern for a specific length (e.g., 9 symbols) and a specific number of DMRS (e.g., 2 DMRS) without regard to the presence of CORESET symbols. After selecting the DMRS pilot pattern, all DMRS positions are shifted based at least in part on the number of CORESET symbols that actually exist. For example, in time domain resource pattern 605, no shifting is performed because there are no CORESET symbols. In contrast, in time domain resource pattern 610, when there is 1 CORESET symbol, a shift of 1 symbol is performed. Similarly, in time domain resource patterns 615 and 620, shifts of 2 symbols (e.g., for 2 CORESET symbols) and 3 symbols (e.g., for 3 CORESET symbols), respectively, are performed. After shifting the DMRS symbols, if the PDSCH symbol is not available for DMRS, the DMRS is dropped from the time domain resource pattern, as indicated by reference numeral 625 with respect to the time domain resource pattern 620. Although described in terms of dropping the DMRS that extends beyond the length of the Type B PDSCH, in some aspects, the DMRS may be dropped if the DMRS is shifted to the last symbol, the second to last symbol, etc.

[0093] As mentioned above, providing Figure 6 As an example. Other examples may differ from Figure 6 An example of description.

[0094] Figures 7A-7E Examples 700-740 of time domain resource pattern shifting. Although some aspects are described in terms of a set of procedural steps, a device (eg, UE 120 and / or BS 110) may use a stored data structure to determine a time domain resource pattern defined in accordance with examples 700-740.

[0095] like Fig. 7A As shown, example 700 is associated with a type B PDSCH having a total length L of 10, a number J of CORESET symbols (symbols in an allocation that overlap with a CORESET) of 2, and a number K of non-CORESET symbols (symbols in an allocation that do not overlap with any CORESET symbol) of 8. In this case, in step 702, a device (e.g., UE 120 and / or BS 110) may select a type B PUSCH time domain resource pattern based at least in part on the number of non-CORESET symbols (e.g., 8 symbols). In addition, in step 704, the device may shift a DMRS of the type B PUSCH time domain resource pattern by a certain number of CORESET symbols (e.g., 2 CORESET symbols) to determine the type B PDSCH time domain resource pattern.

[0096] like Figure 7B As shown, example 710 is associated with a type B PDSCH with a total length L of 13, a number of CORESET symbols J of 1, and a number of non-CORESET symbols K of 12. In this case, in step 712, the device (e.g., UE 120 or BS 110) may select a type B PUSCH time domain resource pattern based at least in part on the number of non-CORESET symbols (e.g., 12 symbols). In addition, in step 714, based at least in part on a DMRS gap greater than a threshold amount (e.g., greater than 8 symbols), the device may shift the last DMRS to an earlier symbol. In addition, in step 716, the device may shift the DMRS of the type B PUSCH time domain resource pattern by a certain number of CORESET symbols (e.g., 1 CORESET symbol) to determine the type B PDSCH time domain resource pattern.

[0097] like Figure 7CAs shown, example 720 is associated with a type B PDSCH having a total length L of 13, a number of CORESET symbols J of 1, and a number of non-CORESET symbols K of 12. In this case, the type B PDSCH is configured for 3 DMRSs. As shown, in step 722, a device (e.g., UE 120 or BS 110) may select a type B PUSCH time domain resource pattern based at least in part on the number of non-CORESET symbols (e.g., 12 symbols) and at least in part on the number of DMRSs. In addition, in step 724, based at least in part on the DMRS gap between the first DMRS and the last DMRS being greater than a threshold amount (e.g., greater than 8 symbols), the device may move the last DMRS to an earlier symbol. In addition, in step 726, the device may shift the DMRS of the type B PUSCH time domain resource pattern by a certain number of CORESET symbols (e.g., 1 CORESET symbol) to determine the type B PDSCH time domain resource pattern.

[0098] like Fig.7D As shown, example 730 is associated with a type B PDSCH having a total length L of 12, a number of CORESET symbols L of 0, and a number of non-CORESET symbols K of 13. In this case, the type B PDSCH is configured for 3 DMRSs. As shown, in step 732, a device (e.g., UE 120 or BS 110) may select a type B PUSCH time domain resource pattern based at least in part on the number of non-CORESET symbols (e.g., 8 symbols). In this case, the DMRS gap between the first DMRS and the last DMRS is greater than a threshold (e.g., greater than 8 symbols), but shifting the last DMRS ahead will result in the number of symbols used for extrapolation being greater than a threshold (e.g., greater than 2 symbols). Therefore, in step 734, the device may shift the first two DMRSs of the type B PUSCH time domain resource pattern to corresponding subsequent symbols to ensure that the DMRS gap is less than or equal to the threshold.

[0099] like Fig. 7EAs shown, example 740 is associated with a type B PDSCH with a total length L of 6, a number of CORESET symbols J of 1, and a number of non-CORESET symbols K of 5. In this case, the type B PDSCH is configured for 2 DMRS. As shown, in step 742, the device (e.g., UE 120 or BS 110) may select a type B PUSCH time domain resource pattern based at least in part on the number of non-CORESET symbols (e.g., 5 symbols) and at least in part on the number of DMRS. In addition, in step 744, since there is no equivalent type A PDSCH time domain resource pattern, the device may convert the last DMRS into a PDSCH symbol. In this way, the device reduces the complexity of the receiver (e.g., UE 120), thereby reducing the utilization of processing resources by the receiver (e.g., UE 120). In addition, in step 746, the device may shift the remaining DMRS of the type B PUSCH time domain resource pattern by a certain number of CORESET symbols (e.g., 1 CORESET symbol) to determine the type B PDSCH time domain resource pattern.

[0100] As mentioned above, Figures 7A-7E are provided as examples. Other examples may differ from those described in Figures 7A-7E Description.

[0101] Figure 8 8 is a diagram illustrating an example process 800 performed, for example, by a UE, according to various aspects of the present disclosure. Example process 800 is an example of a UE (eg, UE 120, apparatus 1002, UE 1150, etc.) performing operations associated with a DMRS time domain pattern configuration technique.

[0102] like Figure 8 As shown, in some aspects, process 800 may include determining a time domain resource pattern for a DMRS set, wherein the DMRS set is included in a type B PDSCH (block 810). For example, the UE (e.g., using receive processor 258, transmit processor 264, controller / processor 280, memory 282, etc.) may determine a time domain resource pattern for a DMRS set as described above. In some aspects, the DMRS set is included in a type B PDSCH.

[0103] like Figure 8 As further shown in FIG. 8 , in some aspects, process 800 may include receiving a set of DMRS using a set of resources determined based at least in part on a time-domain resource pattern (block 820). For example, the UE (e.g., using receive processor 258, transmit processor 264, controller / processor 280, memory 282, etc.) may receive a DMRS using a set of resources determined based at least in part on a time-domain resource pattern, as described above.

[0104] Process 800 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0105] In a first aspect, the time domain resource pattern is based at least in part on another time domain resource pattern for another uplink or downlink signal.

[0106] In a second aspect, alone or in combination with the first aspect, the time domain resource pattern is based at least in part on an interpolation reduction rule or an extrapolation reduction rule.

[0107] In a third aspect, alone or in combination with one or more of the first and second aspects, a time domain resource pattern is based at least in part on a first number of CORESET symbols and a second number of non-CORESET symbols.

[0108] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the time domain resource pattern is based at least in part on a reference time domain resource pattern for another DMRS set included in a Type-B PUSCH.

[0109] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, a reference time domain resource pattern for another DMRS set included in type BPUSCH is based at least in part on the number of non-CORESET symbols.

[0110] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, a reference time domain resource pattern for other DMRS sets included in a type-B PUSCH is based at least in part on a total number of symbols.

[0111] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, the time domain resource pattern is based at least in part on a shift applied to a reference time domain resource pattern.

[0112] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, the shifting is based at least in part on the number of CORESET symbols.

[0113] In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, a last DMRS from a DMRS set is dropped based at least in part on the number of non-CORESET symbols of the DMRS set and the number of symbols of the DMRS.

[0114] In a tenth aspect, alone or in combination with one or more of the first to ninth aspects, the time domain resource pattern includes a shift applied to a last DMRS of a DMRS set based at least in part on a PDSCH duration (expressed in symbols), a number of DMRSs of a DMRS set, and a gap criterion between a first DMRS and a last DMRS of the DMRS set. In some aspects, the gap criterion between the first DMRS and the last DMRS is less than or equal to 9 symbols.

[0115] In the eleventh aspect, alone or in combination with one or more of the first to tenth aspects, the time domain resource pattern includes at least partially based on the number of non-CORESET symbols, the starting symbol of the sequence, the interpolation reduction rule, the extrapolation reduction rule, the gap standard or the symbol number standard.

[0116] In a twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, the determining of the time-domain resource pattern comprises determining the time-domain resource pattern based at least in part on a stored data structure identifying the time-domain resource pattern.

[0117] In a thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, the determination of the time domain resource pattern comprises determining the time domain resource pattern based at least in part on a time domain resource pattern generation process.

[0118] In a fourteenth aspect, alone or in combination with one or more of the first to thirteenth aspects, the time domain resource pattern includes a dropped DMRS configured for symbols greater than a threshold number of symbols after a start symbol of a sequence or a start symbol for an allocation of type B PDSCH.

[0119] although Figure 8 Example blocks of process 800 are shown, but in some aspects, process 800 may include additional blocks, fewer blocks, different blocks, or different blocks. Figure 8 Blocks of process 800 may be executed in parallel in a different arrangement than those shown. Additionally or alternatively, two or more blocks of process 800 may be executed in parallel.

[0120] Fig. 9 900 is a diagram illustrating an example process 900, performed, for example, by a BS, in accordance with various aspects of the present disclosure. Example process 900 is an example of a BS (eg, BS 110, BS 1050, device 1102, etc.) performing operations associated with a demodulation reference signal time domain pattern configuration technique.

[0121] like Fig. 9As shown, in some aspects, process 900 may include determining a time domain resource pattern for a DMRS set, wherein the DMRS set is included in a type B PDSCH (block 910). For example, the BS (e.g., using transmit processor 220, receive processor 238, controller / processor 240, memory 242, etc.) may determine a time domain resource pattern for a DMRS set as described above. In some aspects, the DMRS set is included in a type B PDSCH.

[0122] like Fig. 9 As further shown in FIG. 9 , in some aspects, process 900 may include transmitting a set of DMRS using a set of resources determined based at least in part on a time-domain resource pattern (block 920). For example, the BS (e.g., using transmit processor 220, receive processor 238, controller / processor 240, memory 242, etc.) may transmit a DMRS using a set of resources determined based at least in part on a time-domain resource pattern, as described above.

[0123] Process 900 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0124] In a first aspect, the time domain resource pattern is based at least in part on another time domain resource pattern for another uplink or downlink signal.

[0125] In a second aspect, alone or in combination with the first aspect, the time domain resource pattern is based at least in part on an interpolation reduction rule or an extrapolation reduction rule.

[0126] In a third aspect, alone or in combination with one or more of the first and second aspects, a time domain resource pattern is based at least in part on a first number of CORESET symbols and a second number of non-CORESET symbols.

[0127] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the time domain resource pattern is based at least in part on a reference time domain resource pattern for another DMRS set included in a Type-B PUSCH.

[0128] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, a reference time domain resource pattern for another DMRS set included in type BPUSCH is based at least in part on the number of non-CORESET symbols.

[0129] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, a reference time domain resource pattern for other DMRS sets included in a type-B PUSCH is based at least in part on a total number of symbols.

[0130] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, the time domain resource pattern is based at least in part on a shift applied to a reference time domain resource pattern.

[0131] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, the shifting is based at least in part on the number of CORESET symbols.

[0132] In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, a last DMRS from a DMRS set is dropped based at least in part on the number of non-CORESET symbols of the DMRS set and the number of symbols of the DMRS.

[0133] In a tenth aspect, alone or in combination with one or more of the first to ninth aspects, the time domain resource pattern includes a shift applied to the DMRS of the DMRS set based at least in part on the number of non-CORESET symbols, the number of DMRSs of the DMRS set, and a gap criterion between a first DMRS and a last DMRS of the DMRS set. In some aspects, the gap criterion between the first DMRS and the last DMRS is less than or equal to 9 symbols.

[0134] In the eleventh aspect, alone or in combination with one or more of the first to tenth aspects, the time domain resource pattern includes at least partially based on the number of non-CORESET symbols, the starting symbol of the sequence, the interpolation reduction rule, the extrapolation reduction rule, the gap standard or the symbol number standard.

[0135] In a twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, the determining of the time-domain resource pattern comprises determining the time-domain resource pattern based at least in part on a stored data structure identifying the time-domain resource pattern.

[0136] In a thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, the determination of the time domain resource pattern comprises determining the time domain resource pattern based at least in part on a time domain resource pattern generation process.

[0137] In a fourteenth aspect, alone or in combination with one or more of the first to thirteenth aspects, the time domain resource pattern includes a dropped DMRS configured for symbols greater than a threshold number of symbols after a start symbol of a sequence or a start symbol for an allocation of type B PDSCH.

[0138] although Fig. 9 Example blocks of process 900 are shown, but in some aspects, process 900 may include additional blocks, fewer blocks, different blocks, or different blocks. Fig. 9 In addition or alternatively, two or more blocks of process 900 may be executed in parallel.

[0139] Fig.10 1000 is a conceptual data flow diagram illustrating the data flow between different modules / components / components in an example apparatus 1002. The apparatus 1002 may be a UE (eg, UE 120). In some aspects, the apparatus 1002 includes a receiving component 1004, a determining component 1006, and / or a sending component 1008.

[0140] Receiving component 1004 can receive data 1020 from BS 1050. For example, receiving component 1004 can receive a DMRS set according to the time domain resource pattern determined by determining component 1006. In some aspects, receiving component 1004 can receive configuration information configuring the time domain resource pattern and / or parameters thereof.

[0141] The determining component 1006 may receive data 1022 from the receiving component 1004 and / or provide data 1022 to the receiving component 1004. In some aspects, the determining component 1006 may determine a time domain resource pattern for a DMRS set for a type BPDSCH. For example, the determining component 1006 may determine a configuration of the type BPDSCH (e.g., the number of symbols, the number of DMRS, the number of CORESET symbols, etc.), and may derive a time domain resource pattern for a DMRS set for a type B PDSCH. Additionally or alternatively, the determining component 1006 may access a stored data structure to determine the time domain resource pattern. In some aspects, the determining component 1006 may provide data 1024 to the sending component 1008.

[0142] Transmitting component 1008 can transmit data 1026 to BS 1050. For example, transmitting component 1008 can transmit information associated with determining a DMRS set, a response to a DMRS set, and the like.

[0143] The apparatus 1002 may include executing Figure 8 And / or similar additional components to each block of the algorithm in the aforementioned process 800. Figure 8 Each block in the aforementioned process 800 and / or similar may be performed by a component, and the device may include one or more of these components. These components may be one or more hardware components specifically configured to perform the process / algorithm, implemented by a processor configured to perform the process / algorithm, stored in a computer-readable medium for processor implementation, or some combination thereof.

[0144] Fig.10 The number and arrangement of components shown are provided as examples. Fig.10 There may be additional components, fewer components, different components, or a different arrangement of components than those shown in FIG. Fig.10Two or more components shown in may be implemented in a single component, or Fig.10 The single component shown in can be implemented as multiple distributed components. Additionally or alternatively, Fig.10 The component collection shown (e.g., one or more components) can perform one or more functions, which are described as being Fig.10 Another component set shown executes.

[0145] Fig.11 1100 is a conceptual data flow diagram illustrating the data flow between different modules / components / components in an example apparatus 1102. The apparatus 1102 may be a BS (eg, BS 110). In some aspects, the apparatus 1102 includes a receiving component 1104, a determining component 1106, and / or a sending component 1108.

[0146] Receiving component 1104 can receive data 1120 from UE 1150. For example, receiving component 1104 can receive information associated with determining a DMRS set, information identifying a response to the DMRS set, and / or the like.

[0147] The determining component 1106 may receive data 1122 from the receiving component 1104, such as information associated with determining a DMRS set. In some aspects, the determining component 1106 may determine a time domain resource pattern for a DMRS set for a type B PDSCH. For example, the determining component 1106 may determine a configuration of a type B PDSCH (e.g., the number of symbols, the number of DMRS, the number of CORESET symbols, etc.), and may derive a time domain resource pattern for a DMRS set for a type B PDSCH. Additionally or alternatively, the determining component 1106 may access a stored data structure to determine the time domain resource pattern. In some aspects, the determining component 1106 may provide data 1124 to the sending component 1108, such as a time domain resource pattern for sending a DMRS set.

[0148] The transmitting component 1108 can transmit data 1126 to the UE 1150 based at least in part on receiving the data 1124 from the determining component 1106. For example, the transmitting component 1108 can receive information identifying a time domain resource pattern from the determining component 1106 and can transmit a DMRS set according to the time domain resource pattern. In some aspects, the transmitting component 1108 can transmit configuration information to the UE 1150 that configures the time domain resource pattern and / or parameters thereof.

[0149] Device 1102 may include executing Fig. 9 And / or similar additional components to each block of the algorithm in the aforementioned process 900 . Fig. 9Each block in the aforementioned process 900 and / or similarly may be performed by a component, and the device may include one or more of these components. These components may be one or more hardware components specifically configured to perform the process / algorithm, implemented by a processor configured to perform the process / algorithm, stored in a computer-readable medium for processor implementation, or some combination thereof.

[0150] Fig.11 The number and arrangement of components shown are provided as examples. Fig.11 There may be additional components, fewer components, different components, or a different arrangement of components than those shown in FIG. Fig.11 Two or more components shown may be implemented in a single component, or Fig.11 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Fig.11 The component collection shown (e.g., one or more components) can perform one or more functions, which are described as being Fig.11 Another component set shown executes.

[0151] 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 are possible in light of the above disclosure or may be acquired from practice of the invention.

[0152] As used herein, the term "component" is intended to be broadly interpreted as hardware, firmware, and / or a combination of hardware and software. As used herein, a processor is implemented in hardware, firmware, and / or a combination of hardware and software.

[0153] As used herein, satisfying a threshold may refer to a value greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, etc., depending on the context.

[0154] Obviously, the systems and / or methods described herein can be implemented in different forms of hardware, firmware and / or a combination of hardware and software. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit these aspects. Therefore, the operation and behavior of the systems and / or methods are described herein without reference to specific software codes. It should be understood that software and hardware can be designed to implement the systems and / or methods based at least in part on the description herein.

[0155] Even if a particular combination of features is described in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of the various aspects. In fact, many of these features can be combined in ways that are not specifically described in the claims and / or not disclosed in the specification. Although each dependent claim listed below may only directly depend on one claim, the disclosure of each aspect includes the combination of each dependent claim with each other claim in the claim set. The phrase "at least one" in the list of reference items refers to any combination of these items, including single members. For example, "at least one of a, b or c" is intended to cover a, b, c, ab, ac, bc and abc, as well as any combination with multiples of the same elements (e.g., aa, aaa, aab, aac, abb, ac, bbb, bbc, cc or any other order of a, b and c).

[0156] Unless explicitly stated, any element, behavior or instruction used in this article shall not be interpreted as critical or essential. In addition, as used herein, the terms "one" and "the" are intended to include one or more items and can be used interchangeably with "one or more". In addition, as used herein, the terms "set" and "group" are intended to include one or more items (e.g., related items, unrelated items, combinations of related and unrelated items, etc.), and can be used interchangeably with "one or more". If only one item is intended to be used, the phrase "only one" or similar language is used. In addition, as used herein, the terms "have", "have", "have" etc. are intended to be open terms. In addition, unless explicitly stated otherwise, the phrase "based on" means "based at least in part on".

Claims

1. A method of wireless communication performed by a user equipment UE, comprising: Determining a time domain resource pattern for a demodulation reference signal (DMRS) set, wherein the DMRS set is included in a type B physical downlink shared channel (PDSCH), and wherein: the time domain resource pattern is defined at least in part based on discarding DMRS corresponding to symbols greater than a threshold number of symbols after an allocated start symbol for the type B PDSCH; or, the time domain resource pattern includes a shift corresponding to a last DMRS of the DMRS set, the shift being based at least in part on a PDSCH duration, a number of DMRSs of the DMRS set, and a gap criterion between a first DMRS and a last DMRS of the DMRS set; and The set of DMRS is received using a set of resources determined based at least in part on the time-domain resource pattern.

2. The method according to claim 1, wherein: The time domain resource pattern is also based at least in part on another time domain resource pattern of another downlink signal.

3. The method according to claim 1, wherein: The time domain resource pattern is also determined based at least in part on a first number of control resource set (CORESET) symbols and a second number of non-CORESET symbols.

4. The method according to claim 1, wherein: The time domain resource pattern is based at least in part on a reference time domain resource pattern for another DMRS set included in a Type-B Physical Uplink Shared Channel (PUSCH).

5. The method according to claim 4, wherein: A reference time domain resource pattern for another DMRS set included in the Type-B PUSCH is based at least in part on the number of non-control resource CORESET symbols.

6. The method according to claim 4, wherein: A reference time domain resource pattern for another DMRS set included in the Type-B PUSCH is based at least in part on a total number of symbols including control resource set CORESET symbols and non-CORESET symbols.

7. The method according to claim 1, wherein: The gap criterion between the first DMRS and the last DMRS is less than or equal to 9 symbols.

8. The method according to claim 1, wherein: The determination of the time domain resource mode also includes: The time-domain resource pattern is determined based at least in part on a stored data structure identifying time-domain resource patterns.

9. A method of wireless communication performed by a base station BS, comprising: Determining a time domain resource pattern for a demodulation reference signal (DMRS) set, wherein the DMRS set is included in a type B physical downlink shared channel (PDSCH), and wherein: the time domain resource pattern is defined at least in part based on discarding DMRS corresponding to symbols greater than a threshold number of symbols after an allocated start symbol for the type B PDSCH; or, the time domain resource pattern includes a shift corresponding to a last DMRS of the DMRS set, the shift being based at least in part on a PDSCH duration, a number of DMRSs of the DMRS set, and a gap criterion between a first DMRS and a last DMRS of the DMRS set; and The DMRS set is transmitted using a resource set determined based at least in part on the time domain resource pattern.

10. The method according to claim 9, wherein: The time domain resource pattern is also based at least in part on another time domain resource pattern of another downlink signal.

11. The method according to claim 9, wherein: The time domain resource pattern is based at least in part on a first number of control resource set (CORESET) symbols and a second number of non-CORESET symbols.

12. The method according to claim 9, wherein: The time domain resource pattern is based at least in part on a reference time domain resource pattern for another DMRS set included in a Type-B Physical Uplink Shared Channel (PUSCH).

13. The method according to claim 12, wherein: A reference time domain resource pattern for another DMRS set included in the Type-B PUSCH is based at least in part on the number of non-control resource CORESET symbols.

14. The method according to claim 9, wherein: The gap criterion between the first DMRS and the last DMRS is less than or equal to 9 symbols.

15. The method according to claim 9, wherein: The determination of the time domain resource mode also includes: The time-domain resource pattern is determined based at least in part on a stored data structure identifying time-domain resource patterns.

16. A user equipment UE for wireless communication, comprising: Memory; as well as one or more processors operatively coupled to the memory, the memory and the one or more processors being configured to: Determining a time domain resource pattern for a demodulation reference signal (DMRS) set, wherein the DMRS set is included in a type B physical downlink shared channel (PDSCH), and wherein: the time domain resource pattern is defined at least in part based on discarding DMRS corresponding to symbols greater than a threshold number of symbols after an allocated start symbol for the type B PDSCH; or, the time domain resource pattern includes a shift corresponding to a last DMRS of the DMRS set, the shift being based at least in part on a PDSCH duration, a number of DMRSs of the DMRS set, and a gap criterion between a first DMRS and a last DMRS of the DMRS set; as well as The set of DMRS is received using a set of resources determined based at least in part on the time-domain resource pattern.

17. The UE according to claim 16, wherein: The gap criterion between the first DMRS and the last DMRS is less than or equal to 9 symbols.

18. A base station BS for wireless communication, comprising: Memory; as well as one or more processors operatively coupled to the memory, the memory and the one or more processors being configured to: Determining a time domain resource pattern for a demodulation reference signal (DMRS) set, wherein the DMRS set is included in a type B physical downlink shared channel (PDSCH), and wherein: the time domain resource pattern is defined at least in part based on discarding DMRS corresponding to symbols greater than a threshold number of symbols after an allocated start symbol for the type B PDSCH; or, the time domain resource pattern includes a shift corresponding to a last DMRS of the DMRS set, the shift being based at least in part on a PDSCH duration, a number of DMRSs of the DMRS set, and a gap criterion between a first DMRS and a last DMRS of the DMRS set; as well as The DMRS set is transmitted using a resource set determined based at least in part on the time domain resource pattern.

Images