Data transmission based on superslots in wireless communications

Abstract

A user equipment (UE) receives a resource allocation for a shared channel transmission, the shared channel transmission comprising mapping modulation symbols of a transport block with a single dedicated hybrid automatic repeat request (HARQ) process number onto resource elements of N consecutive time slots of the resource allocation, where N is at least 2. The UE may also receive a demodulation reference signal (DMRS) trigger (DMRS-T) value from a base station indicating a demodulation reference signal (DMRS) pattern to be used for a physical downlink shared channel (PDSCH) transmission, wherein the PDSCH transmission comprises mapping modulation symbols of a transport block with a single dedicated hybrid automatic repeat request (HARQ) process number onto resource elements of N consecutive time slots of the PDSCH resource allocation, where N is at least 2, and measure a transmitted DMRS based on the DMRS pattern corresponding to the DMRS-T value.

Description

Background Art

[0001] A user equipment (UE) may be configured to establish a connection with a network. In one example, the UE may connect to a 5G New Radio (NR) network. NR specifications defining operation for frequencies up to 52.6 GHz have been developed in Rel-15 and Rel-16, where all physical layer channels, signals, procedures, and protocols are designed to be optimized for use at 52.6 GHz. Specifications defining operation for frequencies above 52.6 GHz are under development, however, various challenges arise when using higher frequencies relative to frequencies below 52.6 GHz. For example, higher frequencies experience higher phase noise, greater propagation losses due to high atmospheric absorption, and lower power amplifier efficiency.

[0002] To mitigate the issue of higher phase noise, the maximum subcarrier spacing (SCS) can be increased. However, a larger SCS results in a longer round-trip time for the Hybrid Automatic Repeat Request (HARQ) process and increases downlink control information (DCI) signaling overhead, as the HARQ process number is signaled in the scheduling DCI format. Furthermore, the UE complexity for HARQ process management increases. Summary of the Invention

[0003] Some example embodiments relate to one or more processors configured to perform operations including receiving a resource allocation for a shared channel transmission, wherein the shared channel transmission includes mapping modulation symbols of a transport block having a single dedicated hybrid automatic repeat request (HARQ) process number onto resource elements of N consecutive time slots of the resource allocation, where N is at least 2.

[0004] Other exemplary embodiments relate to a user equipment (UE) having: a transceiver configured to connect to a base station; and one or more processors configured to perform operations, including receiving a resource allocation for a shared channel transmission between the UE and the base station, wherein the shared channel transmission includes mapping modulation symbols of a transport block having a single dedicated hybrid automatic repeat request (HARQ) process number onto resource elements of N consecutive time slots of the resource allocation, where N is at least 2.

[0005] Still other example embodiments relate to one or more processors configured to perform operations including: receiving, from a base station, a demodulation reference signal (DMRS) trigger (DMRS-T) value indicating a demodulation reference signal (DMRS) pattern to be used for a physical downlink shared channel (PDSCH) transmission, wherein the PDSCH transmission includes mapping modulation symbols of a transport block with a single dedicated hybrid automatic repeat request (HARQ) process number onto resource elements of N consecutive time slots of a PDSCH resource assignment, where N is at least 2; and measuring a transmitted DMRS based on the DMRS pattern corresponding to the DMRS-T value. BRIEF DESCRIPTION OF THE DRAWINGS

[0006] Figure 1 Exemplary network arrangements are shown according to various exemplary embodiments.

[0007] Figure 2 An exemplary UE according to various exemplary embodiments is shown.

[0008] Figure 3 Exemplary network cells are shown according to various exemplary embodiments.

[0009] Figure 4 An exemplary transport block mapping scheme utilizing superslots (S-slots) is shown according to various exemplary embodiments.

[0010] Figure 5 An exemplary superslot (S-slot) based TDRA table for PDSCH / PUSCH scheduling on S-slots is shown according to various exemplary embodiments.

[0011] Figure 6 An exemplary superslot (S slot) comprising K slots is shown according to various exemplary embodiments.

[0012] Figure 7 A table providing exemplary dynamic DMRS pattern indications according to various exemplary embodiments is shown.

[0013] Figure 8 Exemplary DMRS patterns for S-slot based PDSCH transmission according to various exemplary embodiments are shown.

[0014] Figure 9 Exemplary DMRS positioning configurations for S-slot based PDSCH transmissions according to various exemplary embodiments are shown.

[0015] Figure 10 Methods for performing superslot (S-slot) based data transmission according to various exemplary embodiments are shown.

[0016] Figure 11 Methods for determining a DMRS pattern for S-slot data transmission according to various exemplary embodiments are shown. DETAILED DESCRIPTION

[0017] The exemplary embodiments may be further understood with reference to the following description and associated drawings, in which similar elements bear the same reference numerals. The exemplary embodiments describe a superslot (S-slot)-based time domain resource allocation (TDRA) scheme for transmit / receive operations between a user equipment (UE) and a next-generation Node B (gNB). An S-slot may include two or more consecutive slots to which a single dedicated hybrid automatic repeat request (HARQ) process number is assigned. Modulation symbols (e.g., one transport block with a dedicated HARQ process number) transmitted on a physical downlink shared channel (PDSCH) or a physical uplink shared channel (PUSCH) may be sequentially mapped to all resource elements (REs) included in the aggregated S-slot.

[0018] The exemplary embodiments described herein relate to S-slot mapping, signaling details for an S-slot based TDRA scheme, and demodulation reference symbol (DMRS) patterns for S-slot based scheduling.

[0019] Network / Device

[0020] Figure 1 An exemplary network arrangement 100 according to various exemplary embodiments is shown. The exemplary network arrangement 100 includes a plurality of UEs 110, 112. Those skilled in the art will appreciate that a UE may be any type of electronic component configured to communicate via a network, such as a component of a connected car, a mobile phone, a tablet computer, a smartphone, a phablet, an embedded device, a wearable device, an Internet of Things (IoT) device, etc. It should also be understood that an actual network arrangement may include any number of UEs used by any number of users. Therefore, the example with two UEs 110, 112 is provided for illustrative purposes only. In some exemplary embodiments described below, a group of UEs may be employed to perform corresponding channel measurements.

[0021] UE 110, 112 can communicate directly with one or more networks. In the example of network configuration 100, the networks with which UE 110, 112 can wirelessly communicate are 5G NR radio access network (5G NR-RAN) 120, LTE radio access network (LTE-RAN) 122, and wireless local area network (WLAN) 124. Therefore, UE 110, 112 can include a 5G NR chipset for communicating with 5G NR-RAN 120, an LTE chipset for communicating with LTE-RAN 122, and an ISM chipset for communicating with WLAN 124. However, UE 110, 112 can also communicate with other types of networks (e.g., traditional cellular networks), and UE 110 can also communicate with the network via a wired connection. Referring to the exemplary embodiment, UE 110, 112 can establish a connection with 5G NR-RAN 120 and / or LTE-RAN 122.

[0022] 5G NR-RAN 120 and LTE-RAN 122 may be part of a cellular network that may be deployed by a cellular provider (e.g., Verizon, AT&T, T-Mobile, etc.). These networks 120, 122 may include, for example, cells or base stations (NodeB, eNodeB, HeNB, eNBS, gNB, gNodeB, macrocell base stations, microcell base stations, small cell base stations, femtocell base stations, etc.) configured to send and receive traffic from UEs equipped with appropriate cellular chipsets. WLAN 124 may include any type of wireless local area network (WiFi, hotspot, IEEE 802.11x network, etc.).

[0023] UEs 110 and 112 may connect to 5G NR-RAN 120 via at least one of next-generation Node B (gNB) 120A and / or gNB 120B. gNBs 120A and 120B may be configured with the necessary hardware (e.g., antenna arrays), software, and / or firmware to perform massive multiple-input, multiple-output (MIMO) functionality. Massive MIMO may refer to a base station configured to generate multiple beams for multiple UEs. Reference to two gNBs 120A and 120B is for illustrative purposes only. The exemplary embodiments are applicable to any suitable number of gNBs. For example, UEs 110 and 112 may simultaneously connect to and exchange data with multiple gNBs in a multi-cell carrier aggregation configuration. UEs 110 and 112 may also connect to LTE-RAN 122 via either or both eNBs 122A and 122B, or to any other type of RAN, as described above. In network arrangement 100, UE 110 is shown as having a connection to gNB 120A, while UE 112 is shown as having a connection to gNB 120B. According to certain exemplary embodiments, the connection of UE 110 to gNB 120A may be at a frequency greater than 52.6 GHz.

[0024] In addition to networks 120, 122, and 124, network arrangement 100 includes a cellular core network 130, the Internet 140, an IP Multimedia Subsystem (IMS) 150, and a network service backbone 160. Cellular core network 130 (e.g., 5GC for NR) can be considered an interconnected collection of components that manage the operation and traffic of a cellular network. Cellular core network 130 also manages traffic flowing between the cellular network and the Internet 140.

[0025] The IMS 150 can be generally described as an architecture for delivering multimedia services to the UE 110 using the IP protocol. The IMS 150 can communicate with the cellular core network 130 and the Internet 140 to provide multimedia services to the UE 110. The network service backbone 160 communicates directly or indirectly with the Internet 140 and the cellular core network 130. The network service backbone 160 can be generally described as a set of components (e.g., servers, network storage arrangements, etc.) that implement a set of services that can be used to extend the functionality of the UE 110 to communicate with various networks.

[0026] Figure 2 An exemplary UE 110 is shown according to various exemplary embodiments. Figure 110. The UE 110 may represent any electronic device and may include a processor 205, a memory arrangement 210, a display device 215, an input / output (I / O) device 220, a transceiver 225, and other components 230. The other components 230 may include, for example, an audio input device, an audio output device, a battery providing a limited power source, a data acquisition device, a port for electrically connecting the UE 110 to other electronic devices, sensors for detecting conditions of the UE 110, and the like. Figure 2 The UE 110 shown may also represent the UE 112 .

[0027] The processor 205 may be configured to execute a plurality of engines of the UE 110. For example, these engines may include a superslot (S-slot) engine 235 for performing operations including transmit / receive operations for transport blocks using a plurality of consecutive aggregated slots. The S-slot engine 235 may perform operations such as determining an S-slot configuration for data transmission, as will be described in further detail below.

[0028] The engine described above as an application (e.g., a program) executed by the processor 205 is merely exemplary. The functionality associated with the engine may also be represented as a standalone integrated component of the UE 110, or may be a modular component coupled to the UE 110, such as an integrated circuit with or without firmware. For example, an integrated circuit may include input circuitry for receiving signals and processing circuitry for processing signals and other information. The engine may also be embodied as one application or multiple separate applications. In addition, in some UEs, the functionality described for the processor 205 is shared between two or more processors, such as a baseband processor and an application processor. The exemplary embodiments may be implemented in any of these or other configurations of the UE.

[0029] The memory 210 may be a hardware component configured to store data related to operations performed by the UE 110. The display device 215 may be a hardware component configured to display data to a user, and the I / O device 220 may be a hardware component that enables user input. The display device 215 and the I / O device 220 may be separate components or may be integrated together (such as a touch screen). The transceiver 225 may be a hardware component configured to establish a connection with the 5G-NR RAN 120, the LTE RAN 122, etc. Thus, the transceiver 225 may operate on a variety of different frequencies or channels (e.g., a contiguous frequency group). For example, when NR-U is configured, the transceiver 225 may operate on an unlicensed spectrum.

[0030] Figure 3An exemplary network cell, in this case a gNB 120A, is shown according to various exemplary embodiments. As described above with reference to UE 110, gNB 120A may represent a cell that provides service as a PCell or SCell or is configured independently from UE 110. gNB 120A may represent any access node of a 5G NR network through which UEs 110, 112 may establish connections and manage network operations. Figure 3 The gNB 120A shown may also represent gNB 120B.

[0031] The gNB 120A may include a processor 305, a memory arrangement 310, an input / output (I / O) device 320, a transceiver 325, and other components 330. The other components 330 may include, for example, an audio input device, an audio output device, a battery, a data acquisition device, ports for electrically connecting the gNB 120A to other electronic devices, and the like.

[0032] The processor 305 may be configured to execute various engines of the gNB 120A. For example, the engines may include a superslot (S-slot) engine 235 for performing operations including configuring S-slots for data transmission, as described in detail below.

[0033] The engines described above, each as an application (e.g., a program) executed by processor 305, are exemplary only. The functionality associated with the engines may also be represented as a standalone, integrated component of gNB 120A, or as a modular component coupled to gNB 120A, such as an integrated circuit with or without firmware. For example, an integrated circuit may include input circuitry for receiving signals and processing circuitry for processing signals and other information. Furthermore, in some gNBs, the functionality described for processor 305 is split among multiple processors (e.g., a baseband processor, an application processor, etc.). The exemplary embodiments may be implemented in any of these or other configurations of the gNB.

[0034] Memory 310 may be a hardware component configured to store data related to operations performed by UE 110, 112. I / O device 320 may be a hardware component or port that enables a user to interact with gNB 120A. Transceiver 325 may be a hardware component configured to exchange data with UE 110, 112 and any other UE in system 100. Transceiver 325 may operate on a variety of different frequencies or channels (e.g., a set of contiguous frequencies). For example, when NR-U functionality is configured, transceiver 325 may operate on an unlicensed bandwidth. Thus, transceiver 325 may include one or more components (e.g., radio components) to enable data exchange with various networks and UEs.

[0035] TDRA based on superslots

[0036] NR specifications defining operation for frequencies up to 52.6 GHz were developed in Rel-15 and Rel-16, where all physical layer channels, signals, procedures, and protocols were designed to be optimized for use at 52.6 GHz. To utilize radio spectrum above 52.6 GHz for operation in NR systems, the 86th RAN Plenary Meeting approved the Rel-17 study project “Study on supporting NR from 52.6 GHz to 71 GHz”. However, frequencies above 52.6 GHz face more difficult challenges, such as higher phase noise, greater propagation losses due to high atmospheric absorption, and lower power amplifier efficiency. More specifically, to alleviate the issue of higher phase noise, the maximum subcarrier spacing (SCS) (i.e., the width of a subcarrier in the frequency domain) can be increased to 480 kHz or even higher (e.g., 960 kHz). However, the data processing time and HARQ-ACK feedback timing for these higher frequency operations may not scale linearly for higher SCSs (e.g., 480 kHz / 960 kHz) relative to the traditional SCS specified for low-frequency NR system operation.

[0037] Hybrid Automatic Repeat Request (HARQ) operations include an acknowledgement / negative acknowledgement (ACK / NACK) mechanism for indicating whether a transmitted packet was successfully received or should be retransmitted. In NR systems, a stop-and-wait (SAW) process is used for HARQ operations, which relies on HARQ-ACK information from the receiver before continuing to transmit any additional data. The round-trip time of the SAW process includes transmitter and receiver data processing time and propagation delay. More specifically, multiple parallel SAW processes, such as HARQ processes, are used to avoid the impact of round-trip time on throughput performance. For example, for a transmitter / receiver pair, up to 16 parallel HARQ processes can occur simultaneously. The longer round-trip time of a larger SCS (e.g., 480KHz / 960KHz) can lead to an increase in the number of parallel HARQ processes, which can also lead to high DCI signaling overhead because the HARQ process number is signaled in the scheduling DCI format. In addition, the UE complexity for HARQ process management increases. It is clear that there is a need to address these issues without reducing throughput.

[0038] According to certain aspects of the present disclosure, a superslot (S-slot)-based time domain resource allocation (TDRA) scheme is used for transmit / receive operations between user equipment (UE) and next-generation Node B (gNB). An S-slot may consist of two or more consecutive slots in the time domain to which a single dedicated hybrid automatic repeat request (HARQ) process number is assigned. Modulation symbols (e.g., one transport block with a dedicated HARQ process number) transmitted on a physical downlink shared channel (PDSCH) or a physical uplink shared channel (PUSCH) may be sequentially mapped to all resource elements (REs) in an S-slot. The sequential RE mapping may be in an increasing order, first in the frequency domain and then in the time domain, or first in the time domain and then in the frequency domain.

[0039] Figure 4 An exemplary transport block mapping scheme 400 utilizing superslots (S-slots) 460 is shown according to various exemplary embodiments. The transport block 410 undergoes channel coding 420, HARQ processing 430 (e.g., including a dedicated HARQ process number), and data modulation 440 to generate modulation symbols for PDSCH / PUSCH transmission. The modulation symbols are then sequentially mapped to N slots 450 of the S-slots 460. Figure 4 In the example of , as shown by the dashed line in time slot 450, mapping is performed in increasing order first in frequency and then in time.

[0040] Signaling details

[0041] Various methods may be used to indicate the S slots within the window used for data transmission.

[0042] In the first approach, when a UE is scheduled using the PDSCH / PUSCH via Downlink Control Information (DCI) transmission from the gNB, the Time Domain Resource Assignment (TDRA) field value of the DCI provides a row index into the allocation table. Each index value corresponds to parameters of the starting slot (e.g., the Slot Offset field) and the Start and Length Indication Value (SLIV) for each of the N slots of a superslot, where N ≥ 2. The slot offset value and SLIV can be configured for the UE via higher-layer signaling (e.g., RRC signaling).

[0043] Figure 5An exemplary superslot (S-slot) based TDRA table 500 for PDSCH / PUSCH scheduling on an S-slot 550 is shown according to various exemplary embodiments. Each TDRA field index value 510 indicates a slot offset 520 and N SLIVs 530 for each of N slots 560 of the S-slot, where N ≥ 2. That is, each indication (SLIV) combination may include multiple SLIVs 530 in consecutive slots 560 within the S-slot 550. The starting slot 560 of the S-slot 550 is signaled by the slot offset field 520 relative to the PDCCH / PUCCH slot. Figure 4 As shown, one S slot of up to N slots can be used for resource allocation for a single transport block (TB) transmission. More than one UE can be scheduled in a time slot 560 of an S slot 550 in a time domain multiplexing (TDM) manner to improve resource efficiency, as shown, for example, by a portion 570 of the time slot 560 for a first UE configuration and a portion 580 of the time slot 560 for a second UE configuration. Note that the size of each S slot can be the same or different.

[0044] In the second approach, a superslot (S-slot) resource grid can be introduced for resource allocation and RE mapping for PDSCH / PUSCH transmission between UE and gNB. Each S-slot grid is used for subcarriers and OFDM symbols, where N RB Indicates the number of PRBs, Indicates the RB size in the number of SCs, is the number of OFDM symbols in a time slot, and K represents the number of time slots within S slots, as Figure 6 shown.

[0045] The value K can be provided to the UE in different ways. In some embodiments, K may be defined by a standard and may be a function of the SCS used for PDSCH / PUSCH transmissions. In other embodiments, K may be signaled in a system information block (SIB). For example, SIB1 may be used to carry the K value. In other embodiments, K may be provided using dedicated RRC signaling on a per-UE basis. For example, different K values ​​may be configured based on the 5QI delay requirements of the data traffic. A larger K value may be configured for UEs with delay-tolerant traffic.

[0046] According to certain aspects of the present disclosure, a scaling factor may be introduced to determine time domain resource allocation for S-slot-based TDRA without increasing signaling overhead relative to NR system operation specified for frequencies of 52.6 MHz and below. Various approaches may be considered to achieve this goal.

[0047] The UE may derive the time domain resource allocation (TDRA) based on the SLIV value encoded in the scheduling DCI format, which indicates the starting symbol S0 and the number of symbols L. The UE may then scale S0 and / or the number of symbols L to determine the S slot starting position, e.g. and / or the number of symbols in the S time slot, for example L sslot =SF*L. In some embodiments, only the S0 value is scaled, e.g. And L sslot = L. In other embodiments, only the L value is scaled, e.g. And L sslot =SF*L. In another embodiment, both the S0 value and the L value are scaled, for example And L sslot =SF*L.

[0048] Each of the above embodiments of scaling TDRA may be more or less suitable for a given transmission type. For example, the exemplary embodiment discussed above that scales only the L value may be configured for a UE with Ultra-Reliable Low-Delay Communication (URLLC) traffic to provide finer granularity resource allocation in the time domain and better meet the stringent delay requirements of URLLC.

[0049] In some exemplary embodiments, the value of the scaling factor SF may be a function of the value of K. For example, the scaling factor value may be equal to the size of an S slot, e.g., SF = K. In another embodiment, the value of the scaling factor SF may be configured based on, for example, traffic type via dedicated RRC signaling.

[0050] Figure 10 A method 1000 for performing superslot (S-slot)-based data transmission according to various exemplary embodiments is shown. An S-slot may include two or more consecutive slots in a resource allocation for PDSCH or PUSCH transmission, where a single transport block (TB) is mapped to a resource element (RE) on the S-slot. Method 1000 may be particularly suitable when operating at frequencies greater than 52.6 GHz and using a subcarrier spacing (SCS) of 480 kHz or greater for network operation between user equipment (UE) and next-generation Node Bs (gNBs) to reduce HARQ signaling overhead and UE complexity for HARQ process management relative to lower frequencies and lower SCSs.

[0051] In 1005, the gNB allocates resources for data transmission and signals the resource allocation to the UE. Depending on the various implementations discussed above, the resource allocation may or may not include an explicit indication of S-slot parameters. For example, in the first method described above, the gNB includes a TDRA field value in the scheduling DCI to indicate the slot offset and SLIV value for each of the S-slots. In the second method described above, the gNB indicates resource grid parameters that may include a K value (indicating the number of slots within an S-slot). In some implementations, the K value is signaled by the gNB, while in other implementations, K is hard-coded in the UE configuration and is based on the SCS. In still other implementations, the gNB additionally signals a scaling factor (SF) to scale one or both of the starting symbol or the number of symbols of the S-slot.

[0052] In 1010, the UE determines S-slot parameters for mapping transport blocks to S-slots. As discussed above, the mapping may be determined by explicit instructions from the gNB. In other embodiments, the UE may determine the number of S-slots and / or apply a scaling factor SF signaled by the gNB or hard-coded in the UE specification.

[0053] At 1015, the transport block is processed (e.g., according to the Figure 4 The UE performs channel coding, HARQ processing, and data modulation) and maps it to S slots for transmission. For PUSCH transmission, the UE performs TB mapping and transmission, while for PDSCH transmission, the gNB performs TB mapping and transmission.

[0054] DMRS mode based on S-slot scheduling

[0055] According to certain aspects of the present disclosure, a UE may be configured with a set of demodulation reference signal (DMRS) patterns. Each DMRS pattern has different DMRS symbol positions and / or different DMRS densities in the time domain relative to the other DMRS patterns in the set. The gNB may then select one of the DMRS patterns based on, for example, the UE mobility state. However, the gNB may also select a DMRS pattern based on other factors. In other exemplary embodiments, the set of DMRS patterns (DMRS symbol positions and / or densities) may be specified by a standard.

[0056] A DMRS trigger (DMRS-T) field may be included in the scheduling DCI to indicate which DMRS pattern in the set of DMRS patterns is to be used for the scheduled PDSCH transmission. The association between the value of the DMRS-T field and the DMRS pattern may be configured by higher layers.

[0057] Figure 7Table 700 is shown providing exemplary dynamic DMRS pattern indications according to various exemplary embodiments. In this example, the DMRS-T field in the scheduling DCI format is 2 bits, allowing four possible values, such as 00, 01, 10, or 11, where for "00", no DMRS is transmitted for the data associated with the scheduling DCI, and for the remaining DMRS-T values ​​(01, 10, or 11), the first, second, or third DMRS pattern is configured by higher layers. However, in other embodiments, a greater or lesser number of bits may be used to indicate a different number of possible DMRS-T values. DMRS may be shared across multiple consecutive S slots to minimize reference signal overhead. This will be discussed below. Figure 8 An example of sharing DMRSs over consecutive S slots is described.

[0058] Figure 8 An exemplary DMRS pattern 800 for S-slot-based PDSCH transmissions according to various exemplary embodiments is shown. In this example, it is assumed that the UE is in a low mobility state. In this example, six S-slots 810 are shown, such as S-slots 810a-810f, each S-slot 810 aggregates two slots 820, 825 for data scheduling. The first slot 820 of each two S-slots 810 may include a DMRS signal 830, and the remaining slots may be used for PDSCH transmissions 840. In this example, two PDSCH transmissions 840 are shown, such as a first PDSCH transmission 840a in S-slot 810d and a second PDSCH transmission 840b in S-slot 810e.

[0059] According to some exemplary embodiments, DMRS 830 may be used in consecutive S slots 810 (e.g., Figure 8 The UE may receive an indication in an earlier S-slot 810 (e.g., S-slot 810d) to reuse the DMRS 830 scheduled in the later S-slot 810 (e.g., DMRS 830 in S-slot 810e) for two PDSCH transmissions 840 in consecutive slots 810d and 810e in order to reduce reference signal overhead.

[0060] In other exemplary embodiments, three or more consecutive S-slots 810 with PDSCH transmissions 840 may share DMRS. For example, if an additional PDSCH 840 is scheduled in S-slot 810c, the UE may receive an indication to reuse the DMRS from S-slot 810e for the PDSCH in S-slot 810c to further minimize PDSCH decoding latency. Note that DMRS 830 may be sent in S-slot 810e even if the UE or gNB decides to skip the associated PDSCH / PUSCH transmission (e.g., PDSCH 840b scheduled in S-slot 810e) to facilitate decoding of an earlier PDSCH / PUSCH (e.g., PDSCH 840a).

[0061] For DMRS position 1 in S-slot data transmission, several approaches can be considered. In the first approach, the UE can be configured with a reference subcarrier spacing (SCS) for DMRS position determination. The UE can determine the position of the DMRS symbol based on the data mapping type and duration corresponding to the reference SCS. For example, the DMRS can be transmitted in the first symbol that overlaps with the DMRS position based on the reference SCS.

[0062] In some exemplary embodiments, to avoid impact on decoding delay, the first DMRS position, e.g., l=0, may be based on the SCS of the PDSCH / PUSCH transmission, while other DMRS positions (if any) may be determined based on a reference SCS depending on the duration of data transmission.

[0063] Figure 9 An exemplary DMRS positioning configuration 900 for S-slot based PDSCH transmission is shown according to various exemplary embodiments. Figure 9 The example assumes a reference SCS of 120 kHz, where the SCS of the serving cell is 480 kHz. Figure 9 As shown, the UE can determine the DMRS position based on the reference SCS (e.g., 120 kHz) to avoid unnecessary RS overhead.

[0064] In a second approach, the DMRS pattern can be defined on a per S-slot basis by distributing the possible positions across the S-slots. In other words, any pattern that distributes the DMRS across the S-slots can be used.

[0065] Figure 11 A method 1100 for determining a DMRS pattern for S-slot data transmission according to various exemplary embodiments is shown. At 1105, the UE receives a configuration of a set of DMRS patterns. The DMRS pattern may be hard-coded or signaled by the gNB.

[0066] In 1110, the gNB indicates to the UE one of the set of DMRS patterns to be used for S-slot data transmission. The indication may be a DMRS-T field value included in the DCI transmission.

[0067] In 1115, the UE determines the DMRS position in the S-slot transmission. For example, a reference SCS (e.g., 120 KHz) may be used and extended to the SCS used by the gNB (e.g., 480 KHz).

[0068] Those skilled in the art will appreciate that the exemplary embodiments described above can be implemented with any suitable software configuration or hardware configuration or combination thereof. Exemplary hardware platforms for implementing the exemplary embodiments may include, for example, Intel x86-based platforms with compatible operating systems, Windows OS, Mac platforms and MAC OS, mobile devices with operating systems such as iOS, Android, etc. In other examples, the exemplary embodiments of the above methods may be embodied as a program comprising lines of code stored on a non-transitory computer-readable storage medium, which, when compiled, can be executed on a processor or microprocessor.

[0069] Although this patent application describes various combinations of various aspects each having different features, those skilled in the art will understand that any feature of one aspect may be combined with features of other aspects in any manner not publicly denied or that is not functionally or logically inconsistent with the operation or function of the device of the disclosed aspects of the present invention.

[0070] It is understood that the use of personally identifiable information should be subject to privacy policies and practices that are generally recognized to meet or exceed industry or government requirements for maintaining user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of authorized use should be clearly stated to users.

[0071] It will be apparent to those skilled in the art that various modifications may be made to the present disclosure without departing from the spirit or scope of the present disclosure. Therefore, the present disclosure is intended to cover modifications and variations of the present disclosure provided that these modifications and variations are within the scope of the appended claims and their equivalents.

Claims

1. An electronic device comprising one or more processors configured to perform operations comprising: receiving a resource allocation for a physical downlink shared channel (PDSCH) transmission, wherein the PDSCH transmission comprises mapping modulation symbols of a transport block having a single dedicated hybrid automatic repeat request (HARQ) process number onto resource elements of N consecutive time slots of the resource allocation, where N is at least 2; and Receive downlink control information DCI for scheduling the PDSCH, the DCI including a time domain resource allocation TDRA value corresponding to the N consecutive time slots of the resource allocation for the PDSCH, wherein the TDRA value provides a row index of an allocation table, the row index corresponding to a time slot offset and multiple start and length indicator values ​​SLIV for the PDSCH.

2. The electronic device according to claim 1, wherein the operation further comprises: receiving the PDSCH transmission from a base station; as well as The PDSCH transmission is decoded based on the indicated configuration of the N consecutive time slots. 3 . The electronic device of claim 1 , wherein the modulation symbols are sequentially mapped to the resource elements in an increasing order of i) first in frequency and then in time or ii) first in time and then in frequency.

4. The electronic device according to claim 1, wherein the operation further comprises: Determine a value of N to be used for the PDSCH transmission, wherein N is either: i) determined as a function of the subcarrier spacing used for the resource allocation; ii) signaled to a user equipment (UE) in a system information block; or iii) signaled to the UE using dedicated radio resource control (RRC) signaling. 5 . The electronic device of claim 1 , wherein the resource allocation comprises a time domain resource allocation (TDRA) value indicating a starting symbol (S_0) and a number of symbols (L), wherein one or both of the starting symbol (S_0) and the number of symbols (L) are scaled by a scaling factor. 6 . The electronic device of claim 5 , wherein the value of the scaling factor is determined as a function of N or configured by a base station via higher layer signaling and based on a type of traffic transmitted by the shared channel.

7. The electronic device of claim 6, wherein for ultra-reliable low latency communication (URLLC) traffic, the number of symbols L is scaled by the scaling factor and the starting symbol S_0 is not scaled by the scaling factor.

8. A user equipment (UE), comprising: a transceiver configured to connect to a base station; as well as One or more processors configured to perform operations including: receiving a resource allocation for a physical downlink shared channel (PDSCH) transmission between the UE and the base station, wherein the PDSCH transmission comprises mapping modulation symbols of a transport block with a single dedicated hybrid automatic repeat request (HARQ) process number onto resource elements of N consecutive time slots of the resource allocation, where N is at least 2; as well as Receive downlink control information DCI for scheduling the PDSCH, the DCI including a time domain resource allocation TDRA value corresponding to the N consecutive time slots of the resource allocation for the PDSCH, wherein the TDRA value provides a row index of an allocation table, the row index corresponding to a time slot offset and multiple start and length indicator values ​​SLIV for the PDSCH.

9. The UE according to claim 8, wherein the operations further comprise: receiving the PDSCH transmission from the base station; as well as The PDSCH transmission is decoded based on the indicated configuration of the N consecutive time slots.

10. The UE of claim 8, wherein the modulation symbols are sequentially mapped to the resource elements in an increasing order of i) first in frequency and then in time or ii) first in time and then in frequency.

11. The UE according to claim 8, wherein the operations further comprise: Determine a value of N to be used for the PDSCH transmission, where N is either: i) determined as a function of the subcarrier spacing used for the resource allocation; ii) signaled to the UE in a system information block; or iii) signaled to the UE using dedicated radio resource control (RRC) signaling. 12 . The UE according to claim 8 , wherein the resource allocation comprises a time domain resource allocation (TDRA) value indicating a starting symbol S_0 and a number of symbols L, wherein one or both of the starting symbol S_0 and the number of symbols L are scaled by a scaling factor.

13. A UE according to claim 12, wherein the value of the scaling factor is determined as a function of N or is configured by the base station via higher layer signaling and based on the traffic type used for the shared channel transmission, wherein for ultra-reliable low latency communication (URLLC) traffic, the number of symbols L is scaled by the scaling factor and the starting symbol S_0 is not scaled by the scaling factor.

14. The UE of claim 8, wherein the connection between the UE and the base station uses a frequency greater than 52.6 GHz and a subcarrier spacing of 480 kHz or greater.

15. A method performed by a user equipment (UE), comprising: receiving a resource allocation for a physical downlink shared channel (PDSCH) transmission between the UE and a base station, wherein the PDSCH transmission comprises mapping modulation symbols of a transport block with a single dedicated hybrid automatic repeat request (HARQ) process number onto resource elements of N consecutive time slots of the resource allocation, where N is at least 2; as well as Receive downlink control information DCI for scheduling the PDSCH, the DCI including a time domain resource allocation TDRA value corresponding to the N consecutive time slots of the resource allocation for the PDSCH, wherein the TDRA value provides a row index of an allocation table, the row index corresponding to a time slot offset and multiple start and length indicator values ​​SLIV for the PDSCH.

16. The method according to claim 15, further comprising: receiving the PDSCH transmission from the base station; as well as The PDSCH transmission is decoded based on the indicated configuration of the N consecutive time slots.

17. The method of claim 15, wherein the modulation symbols are sequentially mapped to the resource elements in an increasing order of i) first in frequency and then in time or ii) first in time and then in frequency.

18. The method according to claim 15, further comprising: Determine a value of N to be used for the PDSCH transmission, where N is either: i) determined as a function of the subcarrier spacing used for the resource allocation; ii) signaled to the UE in a system information block; or iii) signaled to the UE using dedicated radio resource control (RRC) signaling.

19. The method of claim 15, wherein the resource allocation comprises a time domain resource allocation (TDRA) value indicating a starting symbol (S_0) and a number of symbols (L), wherein one or both of the starting symbol (S_0) and the number of symbols (L) are scaled by a scaling factor.

Images