User equipment and base station performing transmission and reception operations

By using the antenna port field and pre-DMRS in a single uplink authorization in 5G NR system, multiple PUSCH transmissions are flexibly scheduled, which solves the problem of latency and reliability in URLLC scenarios, and improves the system's communication reliability Sex and efficiency.

CN118972031APending Publication Date: 2024-11-15PANASONIC INTELLECTUAL PROPERTY CORP OF AMERICA
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411337593.0
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2019-05-02
Filing Date
2020-02-20
Publication Date
2024-11-15

AI Technical Summary

Technical Problem

The prior art is difficult to implement flexible physical uplink shared channel (PUSCH) transmission dispatch in 5G NR systems, resulting in the inability to meet strict waiting time and reliability requirements in ultra-reliable low-latency communication (URLLC) scenarios.

Method used

Time domain resources are determined by carrying index values ​​in user equipment (UE) and base station (BS) and time domain resources are determined and pre-demodulation reference signal (DMRS) are used in PUSCH transmissions for accurate use of pre-demodulation reference signal (DMRS) in PUSCH transmission Channel estimation allows for flexible scheduling of multiple PUSCH transmissions, ensuring that each PUSCH transmission uses the same or less number of symbols and DMRS port numbers, avoiding channel mapping conflicts.

Benefits of technology

It realizes more flexible and efficient PUSCH transmission scheduling in URLLC scenarios, meets stricter waiting time and reliability requirements, and improves the communication reliability and efficiency of the system.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118972031A_ABST
    Figure CN118972031A_ABST
Patent Text Reader

Abstract

A user equipment and a base station performing transmit and receive operations are described. A user equipment, UE, comprises: a receiver that receives a single uplink grant for a plurality of PUSCH transmissions, the single uplink grant comprising an antenna port field having index values to be used for the plurality of PUSCH transmissions; a processor to determine a time domain resource based on the received uplink grant, the determined time domain resource specifying a first number and length of PUSCH transmissions; a transmitter to transmit a first number of PUSCH transmissions using the determined time domain resources, each PUSCH transmission including at least one preamble DMRS, where the processor determines a number of symbols in each preamble DMRS to be used for the first number of PUSCH transmissions based on the received index value, and if at least two of the first number of PUSCH transmissions have different lengths, determines a number of symbols in each preamble DMRS to be used for the first number of PUSCH transmissions, and if at least two of the first number of PUSCH transmissions have different lengths, determines a number of symbols in each preamble DMRS to be used for the first number of PUSCH transmissions. If at least one preamble DMRS is present, the transmitter transmits a second number of PUSCH transmissions equal to or different from the first number, the second number of PUSCH transmissions not including a different number of symbols for the at least one preamble DMRS.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] This application is a divisional application of the Chinese invention patent application with application date of February 20, 2020 and application number 202080031799.4. Technical Field

[0002] The present disclosure relates to the transmission and reception of signals in a communication system. In particular, the present disclosure relates to methods and devices for such transmission and reception. Background Art

[0003] The 3rd Generation Partnership Project (3GPP) is working on technical specifications for the next generation of cellular technology, also known as fifth generation (5G), including “new radio” (NR) radio access technology (RAT), which operates in the frequency range up to 100 GHz.

[0004] NR is a follower of technologies represented by Long Term Evolution (LTE) and LTE-Advanced (LTE-A). The NR program promotes the provision of a single technology framework to address several use cases, requirements, and defined deployment scenarios, including, for example, enhanced mobile broadband (eMBB), ultra-reliable low latency communications (URLLC), massive machine type communications (mMTC), etc.

[0005] For example, eMBB deployment scenarios may include indoor hotspots, dense cities, rural areas, urban macro and highways; URLLC deployment scenarios may include industrial control systems, mobile medical care (remote monitoring, diagnosis and treatment), vehicle real-time control, smart grid wide-area monitoring systems; mMTC may include scenarios with a large number of devices with non-time-critical data transmission, such as smart wearable devices and sensor networks.

[0006] The similarity between eMBB and URLLC services is that they both require very wide bandwidth, but the difference is that URLLC services require ultra-low latency and very high reliability. In NR, the physical layer is based on time-frequency resources (such as orthogonal frequency division multiplexing OFDM in LTE) and supports multi-antenna operation.

[0007] For systems like LTE and NR, further improvements and options may aid in the efficient operation of the communication system and specific equipment related to the system. Summary of the invention

[0008] One non-limiting and exemplary embodiment facilitates improved support for assignment of Physical Uplink Shared Channel (PUSCH) transmissions with flexible timing and allows accurate channel estimation using Demodulation Reference Signals (DMRS) carried therein.

[0009] In one embodiment, the technology disclosed herein is characterized by a user equipment UE, including a receiver, a processor and a transmitter. The receiver receives a single uplink grant for multiple PUSCH transmissions. The single uplink grant includes an antenna port field with an index value to be used for the multiple PUSCH transmissions. The processor determines time domain resources based on the received uplink grant. The determined time domain resources specify the number of PUSCH transmissions and the length of each of the number of PUSCH transmissions.

[0010] The transmitter uses the determined time domain resources to transmit the number of PUSCH transmissions. Each of the number of PUSCH transmissions includes at least one pre-demodulation reference signal DMRS.

[0011] Specifically, the processor determines the number of symbols to be used for each of at least one leading DMRS for the number of PUSCH transmissions based on the received index value, and if at least two of the number of PUSCH transmissions have different lengths, and if different numbers of symbols are allowed for each of the at least one leading DMRS, the transmitter sends the same or less number of PUSCH transmissions so that a different determined number of symbols is used for none of the included at least one leading DMRS.

[0012] In one embodiment, the technology disclosed herein is characterized by a user equipment (UE), comprising: a receiver, receiving a single uplink grant for multiple PUSCH transmissions, the single uplink grant including an antenna port field having an index value to be used for the multiple PUSCH transmissions; a processor, determining time domain resources based on the received uplink grant, the determined time domain resources specifying a first number of PUSCH transmissions and a length of the PUSCH transmissions; a transmitter, using the determined time domain resources to send the first number of PUSCH transmissions, each of the PUSCH transmissions including at least one pre-demodulation reference signal (DMRS), wherein the processor determines a number of symbols for each of the at least one pre-DMRS to be used for the first number of PUSCH transmissions based on the received index value, and, if at least two of the first number of PUSCH transmissions have different lengths, the transmitter sends a second number of PUSCH transmissions that is equal to or different from the first number, the second number of PUSCH transmissions not including a different number of symbols for the at least one pre-DMRS.

[0013] In one embodiment, the technology disclosed herein is characterized by a base station BS, comprising: a processor, determining time domain resources, the determined time domain resources specifying a first number of multiple PUSCH transmissions and the length of the PUSCH transmissions; a transmitter, sending a single uplink grant based on the determined time domain resources for the first number of PUSCH transmissions, the single uplink grant including an antenna port field having an index value to be used for the first number of PUSCH transmissions; wherein the processor determines a number of symbols to be used for each of the at least one pre-DMRS included in the first number of PUSCH transmissions, the determined number of symbols being a low pre-DMRS corresponding to "one" symbol. The processor determines an index value associated with the low number of leading DMRS symbols to be used for each of at least one leading DMRS included if at least two of the first number of PUSCH transmissions have different lengths and if one of the at least two of the first number of PUSCH transmissions cannot include the high number of leading DMRS symbols, and the receiver receives a second number of PUSCH transmissions that is equal to or different from the first number, and the second number of PUSCH transmissions does not include a different number of symbols for the at least one leading DMRS.

[0014] In one embodiment, the technology disclosed herein is characterized by a method performed by a user equipment UE, comprising: receiving a single uplink grant for multiple PUSCH transmissions, the single uplink grant including an antenna port field having an index value to be used for the multiple PUSCH transmissions; determining time domain resources based on the received uplink grant, the determined time domain resources specifying a first number of PUSCH transmissions and a length of the PUSCH transmissions; using the determined time domain resources to send the first number of PUSCH transmissions, each of the PUSCH transmissions including at least one pre-demodulation reference signal DMRS; and determining a number of symbols for each of the at least one pre-DMRS to be used for the first number of PUSCH transmissions based on the received index value, and, if at least two of the first number of PUSCH transmissions have different lengths, sending a second number of PUSCH transmissions equal to or different from the first number, the second number of PUSCH transmissions not including a different number of symbols for the at least one pre-DMRS.

[0015] In one embodiment, the technology disclosed herein is characterized by a method performed by a base station BS, comprising: determining time domain resources, the determined time domain resources specifying a first number of multiple PUSCH transmissions and the lengths of the PUSCH transmissions; sending a single uplink grant based on the determined time domain resources for the first number of PUSCH transmissions, the single uplink grant including an antenna port field having an index value to be used for the first number of PUSCH transmissions; determining a number of symbols to be used for each of the at least one leading DMRS included in the first number of PUSCH transmissions, the determined number of symbols being one of a low number of leading DMRS symbols corresponding to "one" symbol and a high number of leading DMRS symbols corresponding to "two" symbols; if at least two of the first number of PUSCH transmissions have different lengths and if one of the at least two of the first number of PUSCH transmissions cannot include the high number of leading DMRS symbols, determining an index value to be used for each of the included at least one leading DMRS associated with the low number of leading DMRS symbols; and receiving a second number of PUSCH transmissions equal to or different from the first number, the second number of PUSCH transmissions not including a different number of symbols for the at least one leading DMRS.

[0016] In one embodiment, the technology disclosed herein is characterized by an integrated circuit for controlling a process of a user equipment UE, comprising: receiving a single uplink grant for multiple PUSCH transmissions, the single uplink grant including an antenna port field having an index value to be used for the multiple PUSCH transmissions; determining time domain resources based on the received uplink grant, the determined time domain resources specifying a first number of PUSCH transmissions and a length of the PUSCH transmissions; using the determined time domain resources to send the first number of PUSCH transmissions, each of the PUSCH transmissions including at least one leading demodulation reference signal DMRS; and determining a number of symbols for each of the at least one leading DMRS to be used for the first number of PUSCH transmissions based on the received index value, and, if at least two of the first number of PUSCH transmissions have different lengths, sending a second number of PUSCH transmissions equal to or different from the first number, the second number of PUSCH transmissions not including a different number of symbols for the at least one leading DMRS.

[0017] In one embodiment, the technology disclosed herein is characterized by an integrated circuit for controlling a process of a base station BS, comprising: determining time domain resources, the determined time domain resources specifying a first number of multiple PUSCH transmissions and the lengths of the PUSCH transmissions; sending a single uplink grant based on the determined time domain resources for the first number of PUSCH transmissions, the single uplink grant including an antenna port field having an index value to be used for the first number of PUSCH transmissions; determining a number of symbols to be used for each of the at least one leading DMRS included in the first number of PUSCH transmissions, the determined number of symbols being one of a low number of leading DMRS symbols corresponding to "one" symbol and a high number of leading DMRS symbols corresponding to "two" symbols; if at least two of the first number of PUSCH transmissions have different lengths and if one of the at least two of the first number of PUSCH transmissions cannot include the high number of leading DMRS symbols, determining an index value to be used for each of the included at least one leading DMRS associated with the low number of leading DMRS symbols; and receiving a second number of PUSCH transmissions equal to or different from the first number, the second number of PUSCH transmissions not including a different number of symbols for the at least one leading DMRS.

[0018] It should be noted that the general or specific embodiments may be implemented as a system, a method, an integrated circuit, a computer program, a storage medium, or any selective combination thereof.

[0019] According to the specification and drawings, the additional benefits and advantages of the disclosed embodiments and different implementations will be apparent. Benefits and / or advantages can be obtained individually by various embodiments and features of the specification and drawings, and in order to obtain one or more of such benefits and / or advantages, it is not necessary to provide all of them. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] Hereinafter, exemplary embodiments are described in more detail with reference to the accompanying drawings and diagrams.

[0021] Figure 1 A schematic diagram showing an exemplary architecture for a 3GPP NR system;

[0022] Figure 2 A block diagram showing an exemplary user plane and control plane architecture for LTE eNB, NR gNB and UE;

[0023] Figure 3 A schematic diagram illustrating a usage scenario of massive machine type communication (mMTC) and ultra-reliable low latency communication (URLLC);

[0024] Figure 4 A communication system in NR including a user equipment (UE) and a base station (BS) according to an exemplary scenario is shown;

[0025] Figure 5-Figure 6 A block diagram depicting an exemplary implementation of a user equipment (UE) and a base station (BS);

[0026] Figure 7-Figure 8 A sequence diagram of a user equipment (UE) and a base station (BS) performing multiple PUSCH transmissions according to a first general mechanism is shown;

[0027] Figure 9-10 A sequence diagram showing a user equipment (UE) and a base station (BS) performing multiple PUSCH transmissions according to a first exemplary embodiment of a first general mechanism; and

[0028] Figure 11-13 A schematic diagram depicting resource allocation in the time domain according to the use of a first general mechanism;

[0029] Figure 14-15 A sequence diagram showing a user equipment (UE) and a base station (BS) performing multiple PUSCH transmissions according to a second general mechanism;

[0030] Figure 16-Figure 17 A sequence diagram showing a user equipment (UE) and a base station (BS) performing multiple PUSCH transmissions according to a second exemplary embodiment of a second general mechanism; and

[0031] Figure 18-Figure 20 A schematic diagram of resource allocation in the time domain according to the use of a first general mechanism is depicted. DETAILED DESCRIPTION

[0032] As presented in the background section, 3GPP is working on the next version of the fifth generation of cellular technology (abbreviated as 5G), which includes the development of a new radio access technology (NR) that operates at frequencies ranging up to 100 GHz. 3GPP must identify and develop the technical components required for the successful standardization of NR systems to meet both urgent market needs and longer-term requirements in a timely manner. To achieve this goal, the evolution of the radio interface as well as the radio network architecture is considered in the study project "New Radio Access Technology". The results and agreements are collected in the technical report TR 38.804v14.0.0, which is incorporated herein by reference in its entirety.

[0033] Among other things, an agreement has been reached on the overall system architecture. NG-RAN (Next Generation Radio Access Network) consists of gNBs, which provide NG radio access user plane (SDAP / PDCP / RLC / MAC / PHY, Service Data Adaptation Protocol / Packet Data Convergence Protocol / Radio Link Control / Medium Access Control / Physical) and control plane (RRC, Radio Resource Control) protocol terminations towards UEs. NG-RAN architecture as Figure 1 As shown, based on TS 38.300 v.15.0.0 Section 4, incorporated herein by reference. The gNBs are connected to each other via the Xn interface. The gNB is also connected to the NGC (Next Generation Core) via the Next Generation (NG) interface, more specifically, to the AMF (Access and Mobility Management Function) (e.g., a specific core entity that executes the AMF) via the NG-C interface and to the UPF (User Plane Function) (e.g., a specific core entity that executes the UPF) via the NG-U interface.

[0034] Various deployment scenarios have been discussed for support, as reflected in, for example, 3GPP TR 38.801 v14.0.0 "Study on new radio access technology: Radio access architecture and interfaces". For example, a decentralized deployment scenario is presented (TR 38.801 Section 5.2; centralized deployment is shown in Section 5.4) where base stations supporting 5G NR can be deployed. Figure 2 An exemplary decentralized deployment scenario is shown and is based on the TR 38.801 Figure 5 .2.-1, and also shows an LTE eNB and a user equipment UE connected to both the gNB and the LTE eNB. As mentioned before, the new eNB of NR 5G can be exemplarily referred to as a gNB.

[0035] As also mentioned above, within the 3rd Generation Partnership Project New Radio (3GPP NR), three use cases are considered that are envisioned to support the diverse range of services and applications of IMT-2020 (see Recommendation ITU-R M.2083: IMT Vision "Framework and overall objectives of the future development of IMT for 2020 and beyond", September 2015). 3GPP has completed the first phase of specifications for enhanced mobile broadband (eMMB) in December 2017. In addition to further extending eMMB support, current and future work will involve standardization of ultra-reliable and low latency communications (URLLC) and massive machine type communications. Figure 3 (Recommendation from ITU-RM2083) shows examples of some envisaged usage scenarios for IMT in 2020 and beyond.

[0036] The URLLC use case has stringent requirements on capabilities such as throughput, latency and availability, and the use case is envisioned as one of the enablers of future vertical applications such as wireless control of industrial manufacturing or production processes, telemedicine surgery, distribution automation in smart grids, transportation safety, etc. In the current WID (Work Item Description) RP-172115, it was agreed to support ultra-reliability for URLLC by identifying technologies that meet the requirements set by TR 38.913. For NR URLCC in Release 15, the key requirements include a target user plane latency of 0.5ms for UL (uplink) and a target user plane latency of 0.5ms for DL ​​(downlink). The general URLLC requirement for one transmission of one packet is a BLER (block error rate) of 1E-5 for a packet size of 32 bytes with a user plane of 1ms.

[0037] From the RAN1 perspective, reliability can be improved in a number of possible ways. The scope for improving reliability in Rel 15 is reflected in RP-172817, which includes defining a separate CQI table for URLLC, a more compact DCI format, repetition of PDCCH, etc. However, as NR becomes more stable and developed, the scope for achieving ultra-reliability may expand (for key requirements for NR, see 3GPP TR 38.913V15.0.0 "Study on Scenarios and Requirementsfor Next Generation Access Technologies", which is incorporated herein by reference). Therefore, NR URLLC in Rel.15 should be able to send 32-byte data packets within a user plane latency of 1ms with a success probability corresponding to a BLER of 1E-5. Special use cases for NR URLCC in Rel.15 include augmented reality / virtual reality (AR / VR), e-health, e-safety and mission-critical applications (see also ITU-R M.2083-0).

[0038] In addition, the technical enhancements that NR URLCC targets in Release 15 are aimed at latency improvements and reliability improvements. Technical enhancements for latency improvements include configurable parameter sets, non-slot-based scheduling with flexible mapping, ungranted (configured grant) uplinks, slot-level repetitions for data channels, and downlink preemption. Preemption means that the transmission to which resources have been allocated is stopped, and the allocated resources are used for another transmission that is requested later but has lower latency / higher priority requirements. Therefore, the authorized transmission is preempted by the subsequent transmission. Preemption applies independently of the specific service type. For example, a transmission of service type A (URLCC) may be preempted by a transmission of service type B (such as eMMB). Technical enhancements with respect to reliability improvement include a dedicated CQI / MCS table for a target BLER of 1E-5 (for technical enhancements, see also 3GPP TS 38.211 “NR; Physical channels and modulation”, TS 38.212 “NR; Multiplexing and channel coding”, TS 38.213 “NR; Physical layer procedures for control”, and TS 38.214 “NR; Physical layer procedures for data”, corresponding versions V15.4.0, all incorporated herein by reference).

[0039] The use case for mMTC is characterized by a large number of connected devices that typically send relatively small amounts of non-delay-sensitive data. The devices require low cost and long battery life. From the NR perspective, utilizing very narrow bandwidth portions is a possible solution that, from the user device perspective, saves power and extends battery life.

[0040] As mentioned above, the reliability range of NR is expected to become wider. A key requirement for all cases and especially necessary for URLLC and mMTC is high reliability or ultra-reliability. Several mechanisms can be considered to improve reliability from a radio perspective and a network perspective. In general, there are a few key potential areas that can help improve reliability. Among these areas are compact control channel information, data / control channel repetition, and diversity in frequency, time and / or space domains. These areas apply to general reliability, regardless of whether a specific communication scenario is lower or higher.

[0041] For NR URLLC Rel.16, further use cases with more stringent requirements have been identified, such as factory automation, transportation industry and power distribution, including factory automation, transportation industry and power distribution (see RP-181477, "New SID on Physical Layer Enhancements for NR URLLC", Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, which is incorporated herein by reference). Depending on the use case, the more stringent requirements are higher reliability (up to 10-6 level), higher availability, packet size up to 256 bytes, time synchronization down to about a few μs, where the value can be one or a few μs, depending on the frequency range and short latency of about 0.5 to 1 ms, in particular a target user plane latency of 0.5 ms (see also 3GPP TS22.261 "Service requirements for next generation new services and markets" V16.4.0, which is incorporated herein by reference and RP-181477).

[0042] In addition, for NR URLCC in Rel.16, several technical enhancements have been identified from the perspective of RAN1. Among them are PDCCH (Physical Downlink Control Channel) enhancements related to compact DCI, PDCCH repetition, and increased PDCCH monitoring. In addition, UCI (Uplink Control Information) enhancements are related to enhanced HARQ (Hybrid Automatic Repeat Request) and CSI feedback enhancements. PUSCH enhancements related to mini-slot level hopping and retransmission / repetition enhancements have also been identified. The term "mini-slot" refers to a transmission time interval (TTI) that includes a smaller number of symbols than a time slot (a time slot including 14 symbols).

[0043] In general, TTI determines the timing granularity of scheduling assignments. A TTI is the time interval in which a given signal is mapped to the physical layer. Traditionally, the TTI length can vary from 14 symbols (slot-based scheduling) to 2 symbols (non-slot-based scheduling). Downlink and uplink transmissions are specified to be organized into frames (10ms duration), which are further divided into time slots, the number of which is defined by digital science / subcarrier spacing, and the specified value range is between 10 time slots for a subcarrier spacing of 15kHz and 320 time slots for 240kHz. The number of OFDM symbols per time slot is 14 for a normal cyclic prefix and 12 for an extended cyclic prefix (see 3GPP TS 38.211 V15.4.0 Section 4.1 (General Frame Structure), Section 4.2 (Parameter Set), Section 4.3.1 (Frame and Subframe) and Section 4.3.2 (Time Slot), incorporated herein by reference).

[0044] However, the allocation of time resources for transmission may also be non-slot-based. In particular, a TTI in a non-slot-based allocation may correspond to a mini-slot instead of a slot. For example, one or more mini-slots may be allocated for the transmission of requested data / control signaling. In a non-slot-based allocation, the minimum length of a TTI may typically be in the range of 2 to 14 OFDM symbols.

[0045] PUSCH repetition

[0046] One of the areas for potential enhancements is related to mini-slot repetition of PUSCH within a timeslot. In the following, motivation for supporting repetition of PUSCH within a timeslot is provided, which may allow for potential enhancements to the repetition mechanism for further improving reliability and / or latency to meet the new requirements of NRURLLC. However, this motivation should not be construed as imposing any limitations on the present disclosure.

[0047] To achieve the latency requirements for URLLC PUSCH transmissions, a one-shot transmission (i.e., a single (TTI) assignment) is ideal if the reliability requirements are met. However, the target BLER of 1E-6 is not always achieved by a single transmission. Therefore, a retransmission or repetition mechanism is required.

[0048] In NR Rel.15, retransmission and repetition are supported to achieve the target BLER when a single transmission is not enough. As is known, HARQ-based retransmissions improve the overall reliability by using feedback information and improving subsequent retransmissions according to channel conditions. However, they suffer from additional delays due to the feedback processing timeline. Therefore, repetition is useful for highly delay-tolerant services as they do not wait for any feedback for subsequent transmissions of the same transport block.

[0049] PUSCH repetition can be defined as "transmitting the same transport block more than once without waiting for any feedback of the previous transmission(s) of the same transport block". The advantages of PUSCH retransmissions compared to HARQ are an improvement in overall reliability and a reduction in latency, since no feedback is required. However, in general, there may be no link adaptation, and resource usage may be inefficient.

[0050] In NR Rel.15, limited support for repetitions was introduced. Only semi-static configuration of repetitions is allowed. Furthermore, repetitions are only allowed between slots (slot-level PUSCH repetitions). Repetitions can only occur in the slot following the slot of the previous transmission. Depending on the parameter set and the service type (e.g., URLCC, eMBB), the waiting time between repetitions may be too long for inter-slot repetitions.

[0051] This limited support for repetitions is mainly useful for PUSCH mapping type A. This PUSCH mapping type A only allows PUSCH transmissions starting from the beginning of a slot. With repetitions, this will result in an initial PUSCH transmission and each repetition starting at the beginning of multiple consecutive slots.

[0052] Less useful is the limited support for repetition of PUSCH mapping type B. PUSCH mapping type B allows a PUSCH transmission to start at any symbol within a slot. With repetition, this will result in the initial PUSCH transmission and each repetition starting at the same symbol in multiple consecutive slots within a slot.

[0053] In any case, this limited support may not enable the more stringent latency requirements in NR Rel.15, i.e., latency of up to 0.5 ms. This would require mini-slot repetitions. Furthermore, limited support for repetitions also does not exploit the benefits arising from mini-slots, i.e., a transmission time interval (TTI) comprising a smaller number of symbols than a time slot (a time slot comprising 14 symbols).

[0054] PUSCH Allocation

[0055] Another scope for potential enhancements - more generally - is related to the assignment of PUSCH within one or across multiple time slots. In the following, motivation for supporting the assignment of different PUSCH transmissions is provided, which can allow potential enhancements to uplink usage to further improve latency while meeting reliability requirements to further meet the new requirements of NR URLLC.

[0056] To achieve the latency requirements for URLLC PUSCH transmissions, a single transmission (i.e., single (TTI) assignment) is ideal if the reliability requirements are met. However, for concurrent PUSCH transmissions, the target user plane latency of 0.5 ms is not always achieved. Therefore, enhancements to uplink assignments are needed.

[0057] In NR Rel 15, uplink scheduling is restricted to a single uplink grant per TTI. In the case of a single PUSCH transmission, this scheduling constraint is not a limitation and the target user plane latency can be achieved with a single transmission. However, for concurrent PUSCH transmissions, the scheduling constraint results in that a single transmission may not be sufficient to meet the target user plane latency.

[0058] Specifically, concurrent PUSCH transmissions require separate uplink grants, which, however, must be signaled in consecutive TTIs due to scheduling constraints and also due to large scheduling overhead. Therefore, such scheduling constraints introduce unnecessary delays in case of concurrent PUSCH transmissions. Furthermore, multi-mini-slot assignment of PUSCH within a timeslot is also not possible.

[0059] In any case, due to this scheduling constraint, the more stringent latency requirement in NR Rel.15, i.e., latency of up to 0.5 ms, may not be achieved. This would require mini-slot allocations of PUSCH. Furthermore, limited support for PUSCH allocations does not take advantage of mini-slots, i.e., a transmission time interval (TTI) comprising a smaller number of symbols than a timeslot (a timeslot comprising fourteen symbols).

[0060] First general scenario

[0061] In view of the above, the authors of the present disclosure have recognized a need for more flexible support for PUSCH transmissions, ie, mechanisms that are not limited to PUSCH transmissions that require a separate uplink grant.

[0062] At the same time, more flexibility should not come at the expense of additional signaling overhead. In other words, the authors of the present disclosure have recognized that flexible support for PUSCH transmissions does not require modification of the existing uplink scheduling mechanism, i.e., the existing format of uplink grants. In other words, the signaling mechanism, e.g., the form of downlink control information (DCI) format 0-0 or 0-1 used to convey uplink grants, should remain unchanged, thereby avoiding any additional signaling overhead when scheduling PUSCH transmissions.

[0063] Therefore, an underlying understanding of the present disclosure is that PUSCH transmissions should be supported by flexible timing that does not create additional signaling overhead.

[0064] In this context, support for flexible timing of such PUSCH transmissions is not only recognized as a possibility for the generality of the enhancement mechanism, but can also be seen as a necessity to avoid conflicts (e.g., with dynamic changes in the slot format (UL / DL)). This becomes apparent from the implementation discussed as "Option 4" in Section 6.3.3 in 3GPP TR 38.824v2.0.1, "Study on physical layer enhancements for NRultra-reliable and low latency case (URLLC)", which is incorporated herein by reference.

[0065] For the sake of example, it is assumed that the proposed mechanism is utilized with a semi-static grant-free (configured grant) uplink. At configuration time, the configured grant specifies consecutive symbols of a slot for multiple PUSCH transmissions. However, this specification may cause conflicts with dynamic changes in the slot format. For example, if the slot format specifies a change of one of the specified consecutive symbols from UL to DL, this will trigger a conflict with the configured multiple PUSCH transmissions.

[0066] However, recognizing the need for support for flexible timing, the authors have identified a number of technical constraints resulting from the existing uplink scheduling mechanism, namely, Downlink Control Information (DCI) formats 0-1 of NR Rel.15.

[0067] One possibility for conveying uplink grants is downlink control information (DCI) format 0-1. This format (e.g., DCI format 0-1) is generally understood as a non-fallback format for supporting single-user multiple-input multiple-output (SU-MIMO) or multi-user multiple-input multiple-output (MU-MIMO) in the uplink. To this end, DCI format 0-1 includes an antenna port field that allows consistency of the (multiple) antenna ports used for PUSCH transmission.

[0068] Antenna ports can be defined so that "the channel through which a symbol is communicated on an antenna port can be inferred from the channel through which another symbol is communicated on the same antenna port" (see, e.g., Section 4.4 of 3GPP Technical Specification TS 38.211 v.15.5.0, entitled "Physical channels and modulation (Release 15)"). The concept of antenna ports is also deployed to the pre-demodulation reference signal (DMRS) included in the PUSCH transmission.

[0069] For example, the first pre-DMRS configuration, corresponding to configuration type 1, supports up to four orthogonal DMRS ports if single-symbol DMRS is used, and supports up to eight orthogonal DMRS ports if dual-symbol DMRS is used. The second pre-DMRS configuration, corresponding to configuration type 2, provides support for up to 6 orthogonal DMRS ports if single-symbol DMRS is used, and supports up to 12 orthogonal ports if dual-symbol DMRS is used. From the perspective of the receiver, the DMRS ports are quasi-co-located.

[0070] Advantageously, the pre-DMRS configuration is designed to allow flexibility between using single-symbol DMRS and dual-symbol DMRS. Specifically, configuration type 1 and configuration type 2 are designed to support not only the corresponding maximum symbol length for DMRS (eg, maxLength=2) but also a lower number of symbols.

[0071] It can be seen that, for example, for configuration type 1 (e.g., dmrs-Type=1), it can be reproduced from Section 7.3.1.1.2 of 3GPP Technical Specification TS38.212v.15.5.0, entitled "Multiplexing and channel coding (Release 15)", which is incorporated herein by reference. For this configuration type 1, with a maximum of two symbol DMRS, it is possible to schedule not only 8 DMRS ports but also up to 4 DMRS ports.

[0072] Table 7.3.1.1.2-7: (Multiple) antenna ports, conversion precoder enabled, DMRS-Type = 1, maxLength = 2

[0073]

[0074]

[0075] With this pre-DMRS configuration, the antenna port field included in downlink control information (DCI) formats 0-1 conveys an index value (see, e.g., column 1 in Table 7.3.1.1.2-7 of TS 38.212) that specifies not only the DMRS port used for the pre-DMRS (see, e.g., column 3 in the same table), but also the number of symbols used as the pre-DMRS (e.g., single symbol or double symbol) (see, e.g., column 4 in the same table).

[0076] The authors of the present disclosure have recognized that such a pre-DMRS configuration may result in a number of technical constraints when utilizing a single uplink grant of this DCI format 0-1 to schedule multiple PUSCH transmissions with flexible timing.

[0077] For the sake of example, assume that a single uplink grant is scheduling two PUSCH transmissions with flexible timing. Then, it is generally understood that such two PUSCH transmissions require separate indications of the DMRS ports to be used. Since a single uplink grant only includes a single antenna port field, it is not possible to indicate the individual DMRS ports to be used. Instead, it is only possible to convey one index value that specifies one DMRS port for the corresponding pre-DMRS configuration. Therefore, there is ambiguity as to whether the indicated DMRS port is to be used for the first or the second of the two PUSCH transmissions with flexible timing.

[0078] In other words, the authors of the present disclosure have recognized that there is ambiguity as to which of multiple PUSCH transmissions an index value carried in the antenna port field of a single uplink grant belongs.

[0079] Furthermore, the authors have recognized that a situation may occur where scheduling of two PUSCH transmissions with flexible timing may introduce a mapping conflict for the leading DMRS in the PUSCH transmissions.

[0080] For the sake of example, assume that a single uplink grant is scheduling two PUSCH transmissions with flexible timing (i.e., with different lengths). It is then generally understood that such two PUSCH transmissions are not necessarily allowed to include both single-symbol and dual-symbol DMRS. Rather, the length of a PUSCH transmission imposes a restriction on the number of symbols of DMRS that can be carried therein. This introduces ambiguity as to whether the number of leading symbols for DMRS indicated by a single uplink grant is to be used for the first or second of the two PUSCH transmissions with flexible timing.

[0081] In NR Rel. 15, the demodulation reference signal for PUSCH is described in Section 6.4.1.1 in 3GPP technical specification TS 38.211 v.15.5.0, titled “Physical channels and modulation (Release 15)”, which is incorporated herein by reference.

[0082] For mapping to physical resources, the position(s) of a DMRS symbol is represented by l and the duration l d Given, for example, l d is the duration between the first OFDM symbol of a slot and the last OFDM symbol of the scheduled PUSCH resources of a slot for PUSCH mapping type A according to Tables 6.4.1.1.3-3 and 6.4.1.1.3-4, or l dis the duration of the scheduled PUSCH resources for PUSCH mapping type B according to Tables 6.4.1.1.3-3 and 6.4.1.1.1.3-4. The referenced tables are reproduced below.

[0083] Table 6.4.1.1.3-3: PUSCH DM-RS position within a slot for single-symbol DM-RS and intra-slot frequency hopping disabled.

[0084]

[0085] Table 6.4.1.1.3-4: PUSCH DM-RS position within a slot for dual-symbol DM-RS and intra-slot frequency hopping disabled.

[0086]

[0087] With such a mapping of DMRS symbols to PUSCH, it follows directly that single-symbol DMRS is allowed in any duration of the scheduled PUSCH resource, while dual-symbol DMRS is allowed only in case of mapping type A when the duration of the scheduled PUSCH resource is 4 symbols and higher (see l d <4 results in undefined DRMS ​​position for mapping type A of Table 6.4.1.1.3-4), and in case of mapping type B when the duration of the scheduled PUSCH resource is 5 symbols and higher (see l d <4 and l d =4 results in undefined DMRS positions for mapping type A of Table 6.4.1.1.3-4) is allowed.

[0088] In other words, the authors of the present disclosure have recognized that there is ambiguity as to which of multiple PUSCH transmissions an index value carried in the antenna port field of a single uplink grant belongs.

[0089] In summary, exemplary embodiments of the present disclosure facilitate improved support for assignment of Physical Uplink Shared Channel (PUSCH) transmissions with flexible timing and allow accurate channel estimation using Demodulation Reference Signals (DMRS) carried therein.

[0090] Figure 4An exemplary communication system including a user equipment (UE) 410 and a base station (BS) 460 in a wireless communication network is shown. Such a communication system may be a 3GPP system such as NR and / or LTE and / or UMTS. For example, as shown, the base station (BS) may be a gNB (gNodeB, e.g., NR gNB) or an eNB (eNodeB, e.g., LTE gNB). However, the present disclosure is not limited to these 3GPP systems or any other system.

[0091] Although some terminology of the 3GPP system is used to describe the embodiments and exemplary implementations, the present disclosure is also applicable to any other communication system, in particular any cellular, wireless and / or mobile system.

[0092] On the contrary, it should be noted that many assumptions have been made here in order to be able to explain the principles behind the present disclosure in a clear and understandable manner. However, these assumptions should be understood as examples for illustrative purposes only and should not limit the scope of the present disclosure. An experienced reader will know that the principles disclosed below and as set forth in the claims can be applied in different scenarios and in ways not explicitly described herein.

[0093] The mobile terminal is referred to as user equipment (UE) in LTE and NR. This can be a mobile device such as a wireless phone, a smart phone, a tablet, or a USB (Universal Serial Bus) stick with user equipment functionality. However, the term mobile device is not limited to this, and in general, a relay can also have the functionality of such a mobile device, and a mobile device can also act as a relay.

[0094] A Base Station (BS) forms at least part of a system of interconnected units, such as a (central) baseband unit and different radio frequency units, which interfaces with different antenna panels or radio heads in the network to provide services to the terminals. In other words, the base station provides wireless access to the terminals.

[0095] Referring back to the figure, the user equipment 410 includes a processing circuit (or processor) 430 and a transmitter / receiver (or transceiver) 420, which are indicated as separate building blocks in the figure. Similarly, the base station 460 includes a processing circuit (or processor) 480 and a transmitter / receiver (or transceiver) 470, which are indicated as separate building blocks in the figure. The transmitter / receiver 420 of the user equipment 410 is communicatively coupled to the transmitter / receiver 470 of the base station 460 via a radio link 450.

[0096] Figure 5 and Figure 6An exemplary implementation of a first general scenario according to building blocks of a user equipment 410 and a base station 460 is depicted respectively. The user equipment 410 of the exemplary implementation includes an uplink grant receiver 520-a, a time domain resource determination processing circuit 530-a, a DMRS symbol number determination processing circuit 530-b, a DMRS port number processing circuit 530-c, and a PUSCH transmission transmitter 520-b.

[0097] Similarly, the base station 460 of the exemplary implementation includes a time domain resource determination processing circuit 680-a, a DMRS symbol number determination processing circuit 680-b, a DMRS port number determination processing circuit 680-c, an index value determination processing circuit 680-d, an uplink grant transmitter 670-a, and a PUSCH transmission receiver 670-b.

[0098] The present disclosure is given assuming that the user equipment 410 is to perform multiple physical uplink shared channel (PUSCH) transmissions. In an exemplary use case, these PUSCH transmissions may carry repetitions of the same transport block, resulting in multiple PUSCH repetitions including an initial PUSCH transmission and at least one (subsequent) PUSCH repetition.

[0099] Even for PUSCH transmissions with flexible timing, this does not prevent them from carrying repetitions of the same transport block. Let us consider an example where the scheduled PUSCH transmissions have different lengths, i.e., occupy different numbers of symbols. Even so, PUSCH transmissions can also carry repetitions of the same transport block, as long as the modulation and coding scheme (MCS) is appropriately adjusted for each PUSCH transmission.

[0100] However, the present disclosure should not be construed as being limited to transport block repetitions. For this purpose, the present disclosure refers generally to PUSCH transmissions, i.e., without any restriction on the transport blocks carried therein. Many alternative use cases are also conceivable, e.g., the scheduled PUSCH transmissions are partially used for transport block repetitions and for unimodal transmissions.

[0101] refer to Figure 7 , describes a sequence diagram of a user equipment (UE) performing multiple PUSCH transmissions according to a first general scenario, i.e., wherein the user equipment 410 performs multiple PUSCH transmissions of different symbol numbers excluding a pre-DMRS carried therein.

[0102] Having established that the user equipment 410 is to perform multiple PUSCH transmissions, it receives (see, for example, steps 710- Figure 7) a single (eg, one) uplink grant. The uplink grant is suitable for scheduling multiple PUSCH transmissions. An uplink grant scheduling transmissions on the uplink is received from base station 460, i.e., via a physical uplink shared channel (PUSCH). For example, the receiving operation may be performed by Figure 5 The UL grant receiver 520-a performs.

[0103] The user equipment 410 receives an uplink grant including an antenna port field with an index value. The index value can be used for many purposes for the user equipment 410, for example, to indicate the (multiple) antenna ports on which the PUSCH transmission is to be performed. In other words, the index value is to be used for multiple PUSCH transmissions scheduled by the uplink grant.

[0104] In view of 3GPP terminology, the described uplink grant includes the antenna port field, which may imply the signaling of downlink control information (DCI) format 0-1. For a detailed description of DCI format 0-1, reference is made to Section 7.3.1.1.2 of v.15.5.0 of 3GPP technical specification TS 38.212, which is incorporated herein by reference. In addition, other (alternative) formats for conveying dynamic uplink grants in 3GPP systems, i.e., DCI format 0-0, do not include the antenna port field, because all PUSCH transmissions will exclusively use the pre-configured port numbered 0.

[0105] Also in view of 3GPP terminology, the uplink grant described as including the antenna port field may alternatively imply signaling of a ConfiguredGrantConfig information element (IE). For a detailed description of the ConfiguredGrantConfig IE, please refer to 3GPP technical specification TS 38.331 section 6.3.2 in v.15.5.0, entitled "Radio Resource Control (RRC) protocol specification (Release 15)", which is incorporated herein by reference. It is apparent from the ASN.1 annotations that not all ConfiguredGrantConfig IEs include the antenna port field, as it is included in the sequence of fields that are specified as optional for the IE.

[0106] Based on the received uplink grant, the user equipment 410 determines (see, e.g., steps 720- Figure 7 ) Time domain resources to be used for multiple PUSCH transmissions. Generally speaking, the determined time domain resources for each PUSCH transmission should be understood as a plurality of consecutive symbols designated for uplink transmission. For example, the determination operation can be performed by the time domain resource determination processing circuit 530-a.

[0107] In more detail, the determined time domain resources specify the (e.g., maximum or total) number of PUSCH transmissions being scheduled by the uplink grant, and specify the length (e.g., in symbols) of each of the number of PUSCH transmissions. The time domain resources have been allocated in advance by the base station 460 for use by the user equipment 410.

[0108] In an exemplary implementation, the determined time domain resources may also specify the position of at least one PUSCH transmission, i.e., the first PUSCH transmission of the number of PUSCH transmissions or the position of all PUSCH transmissions. For example, such a position may be specified based on a (relative) time slot offset and an (absolute) symbol number starting within a specified time slot. Alternatively, such a position may be inferred (e.g., in a technical specification) in the form of consecutive PUSCH transmissions, i.e., the last symbol of the preceding PUSCH transmission directly follows the first symbol of the subsequent PUSCH transmission.

[0109] However, in the context of the present disclosure, it is sufficient that the user equipment 410 can (in practice) determine the time domain resources to be used for multiple PUSCH transmissions based on the received uplink grant. In other words, the present disclosure is not limited to any one of the following exemplary embodiments.

[0110] In another exemplary implementation, the user equipment 410 may determine the time domain resources by referring to a radio resource control RRC configuration table. Specifically, an indication of a particular row of the RRC configuration table may be signaled via a dynamic or configured uplink grant, i.e., by referring to an index value from a time domain resource allocation field included in such a dynamic or configured uplink grant.

[0111] In the case of dynamic uplink grant, the mechanics of this implementation can be best summarized as follows:

[0112] The user equipment 410 receives a PUSCH configuration information element IE in the form of RRC signaling, i.e., wherein the PUSCH configuration IE applies to a specific bandwidth portion. Then, the user equipment 410 configures a table defined by the PUSCH time domain resource allocation list IE carried in the received PUSCH configuration IE. The table includes rows, each row having a value indicating a PUSCH mapping type, a value K2 indicating a time slot offset, and a value SLIV indicating a start and length indicator. Thereafter, the user equipment 410 receives DCI in the form of MAC signaling carrying a time domain resource allocation field having a value m, wherein the value m provides a row index m+1 to the RRC configuration table.

[0113] Through this, the user equipment 410 is able to determine the time domain resources for at least one PUSCH transmission based on the following conditions: the number of the time slot carrying the received DCI in the indexed row of the RRC configuration table, the value K2 indicating the time slot offset, and the value SLIV indicating the start and length indicator.

[0114] The mechanism of this exemplary implementation does not (explicitly) specify how the number of multiple PUSCH transmissions is communicated to the user equipment 410. For this reason, different improvements to this mechanism are currently being actively discussed, all aiming to allow the user equipment 410 to (deterministically) characterize the time domain resources used for multiple PUSCH transmissions.

[0115] In one refinement of the exemplary implementation, it is assumed that the DCI carries not only the time domain resource assignment field, but also an (explicit) indication of the (total) number of PUSCH transmissions that the base station 460 is scheduling.

[0116] With this indication of the number of PUSCH transmissions, the user equipment 410 can determine the corresponding time domain resources under the following basic assumption, which is that the determined time domain resources for the first PUSCH transmission are directly followed (continuously) by time domain resources for all subsequent PUSCH transmissions, whose (total) number corresponds to the indicated number of PUSCH transmissions.

[0117] Specifically, the user equipment 410 may use the same parameters of the indexed row of the RRC configuration table to determine not only the time domain resources for the first PUSCH transmission but also the time domain resources for all subsequent PUSCH transmissions so that they are arranged continuously in the time domain. For example, this implies that all time domain resources may have the same symbol length and may be arranged continuously within a time slot or across multiple time slots.

[0118] In another refinement of the exemplary implementation, it is assumed that the PUSCH configuration information element IE carries not only the time domain resource allocation for a single PUSCH transmission, but also such allocation for all subsequent PUSCH transmissions being scheduled by the base station 460 .

[0119] By such a time domain resource allocation, the user equipment 410 can infer the (total) number of PUSCH transmissions from the number of different time domain resource allocations included in the RRC configuration table, for example. Then, by indexing, the user equipment 410 can refer to the indexed row of the RRC configuration table to infer the (total) number of PUSCH transmissions and can also determine the time domain resources used for the same transmission.

[0120] In more detail, the indexed row of the RRC configuration table may include multiple SLIV values ​​corresponding to different time domain resources arranged within a time slot or across multiple time slots. Since each SLIV value indicates the start and length of the time domain resource in symbols, it is not necessary for the time domain resources to be arranged continuously in the time domain. Instead, the start and length of each time domain resource can be configured independently.

[0121] In a further refinement of the exemplary implementation, it is assumed that the user equipment 410, when determining the time domain resources, further (actively) adapts the time domain resource allocation signaled from the base station 460. Such adaptation may become necessary to handle (or deal with) side effects that may be caused by the dynamic reconfiguration of the underlying time slot format (UL / DL).

[0122] In other words, all the above mechanisms are based on time domain resource allocations, which are semi-statically (in advance) configured via RRC. Moreover, it is not possible to reflect all conceivable time slot formats in advance. Therefore, a dynamically indicated change in the time slot format may require an adaptation of the semi-statically configured time domain resource allocation, i.e., when determining the time domain resources that can (actually) be used for PUSCH transmission.

[0123] One possibility of a conflict may be caused by the signaling of a changed slot format that specifies that a symbol of a slot changes from UL to DL. Assuming that the symbol was previously intended to be used as part of the indicated time domain resource allocation, the change from UL to DL specified by it will result in a conflict that has been processed (or handled) on the user equipment side.

[0124] Such a conflict can be resolved by the user equipment shifting the signaled time domain resource allocation so that the determined time domain resources only occupy the UL symbols of the most recently assigned time slot.

[0125] Another possibility of a collision may result from the signaling of a changed slot format that designates fewer slot symbols as UL and more symbols as DL. Then, even if the individual time domain resource allocations are not affected by the slot format change, it may happen that the indicated time domain resource allocations are distributed across multiple slots. In particular, if the signaled time domain resource allocations belonging to a single PUSCH transmission are distributed across multiple slots (across slot boundaries), this will result in a collision that again has to be handled (or handled) on the user equipment side, since PUSCH transmissions across slot boundaries are not allowed.

[0126] Such a conflict may be resolved by the user equipment segmenting the affected PUSCH transmission at the slot boundary into two (consecutive) PUSCH transmissions which no longer cross the slot boundary.

[0127] It is worth noting that due to this segmentation, the user equipment 410 will have to send more PUSCH transmissions than have been scheduled by the uplink grant.

[0128] For the sake of example, assume that user equipment 410 receives an uplink grant that is scheduling three (3) PUSCH transmissions. Assuming that one (1) of these PUSCH transmissions is segmented due to crossing a slot boundary, then this one (1) affected PUSCH transmission will actually result in two (2) PUSCH transmissions, i.e., one (1) PUSCH transmission that is segmented before the slot boundary and another (1) PUSCH transmission that is segmented after the slot boundary. The received uplink grant will then result in user equipment 410 determining time domain resources for a total of four (4) PUSCH transmissions.

[0129] In summary, there are a variety of conceivable implementations that allow the user equipment 410 to determine the time domain resources to be used for multiple PUSCH transmissions based on the received uplink grant. However, the present disclosure should not be construed as being limited to any of these exemplary embodiments.

[0130] After determining the time domain resources for a (possibly high) number of PUSCH transmissions based on the received uplink grant, the user equipment 410 composes PUSCH transmissions for their subsequent transmissions. Each of the number of PUSCH transmissions includes at least one pre-demodulation reference signal (DMRS) to enable coherent demodulation of the PUSCH transmissions.

[0131] In this context, the user device 410 determines (see, for example, steps 730- Figure 7 ) The number of pre-DMRS symbols to be used for each PUSCH transmission (e.g., single symbol or double symbol). To this end, the user equipment 410 determines the number of symbols based on the index value carried in the antenna port field of the received single uplink grant. For example, the determination operation can be performed by the DMRS symbol number determination processing circuit 530-b.

[0132] The key point is the fact that the present disclosure focuses on the case where different numbers of symbols are allowed for each pre-DMRS. In other words, the present disclosure does not consider the case where only single-symbol DMRS can be used (allowed) as a pre-DMRS, but considers the case where both single-symbol and dual-symbol DMRS can be used (allowed) as a pre-DMRS.

[0133] It is generally believed that dual-symbol DMRS enables higher accuracy of channel estimation to be performed when compared to single-symbol DMRS. This helps to achieve better results for coherent demodulation of PUSCH transmissions. In particular, dual-symbol DMRS has been introduced to cope with highly time-varying and / or frequency-selective radio channels. In addition, dual-symbol DMRS is also believed to provide superior detection results for PUSCH transmissions scheduled by configured grants, i.e., avoiding false detections.

[0134] However, the use of this greater number of symbols for the preamble DMRS comes at the expense of reduced throughput per PUSCH transmission basis. If the PUSCH transmission is scheduled with a specific length, the decision whether to use the dual-symbol DMRS may reduce the symbols that carry the payload in the form of a transport block. Therefore, this decision is left to the base station, i.e., it is up to it to decide, under given radio channel conditions, whether it is necessary for the user equipment to use the dual-symbol DMRS for the PUSCH transmission, or whether it is sufficient to use the single-symbol DMRS for the same PUSCH transmission.

[0135] There are two different steps before the user equipment 410 actually knows whether to use dual-symbol DMRS or single-symbol DMRS for some PUSCH transmissions.

[0136] In a first step, the user equipment 410 is signaled an indication whether or not (generally) different numbers of symbols are allowed to be used for PUSCH transmissions. This indication is then used when determining the (actual) number of symbols to be used as pre-DMRS included in each PUSCH transmission.

[0137] For example, the indication may configure (e.g., in the case of "yes") the user equipment 410 so that it can use one of the dual-symbol or single-symbol DMRS for all future PUSCH transmissions. In other words, the configuration only specifies the (general) availability of dual-symbol DMRS for PUSCH transmissions. The actual use of dual-symbol DMRS is not required. In addition to this example, the indication may configure (e.g., in the case of "no") the user equipment 410 so that only single-symbol DMRS can be used for PUSCH transmissions.

[0138] In a second step, the user equipment determines the (actual) number of symbols to be used for each pre-DMRS of the number of PUSCH transmissions. The determination is based on the index value carried in the antenna port field included in the received uplink grant. In this regard, since the index value is carried in the received uplink grant, it is directly linked to the corresponding number of PUSCH transmissions.

[0139] In an exemplary implementation, the user equipment 410 is provided with a configuration that specifies the maximum number of symbols allowed to be used as pre-DMRS. If the maximum number of symbols is "two", then the use of either dual-symbol DMRS or single-symbol DMRS is allowed.

[0140] In another exemplary implementation, the user equipment 410 determines the number of symbols of the leading DMRS to be used for each of the number of PUSCH transmissions. To this end, the user equipment 410 refers to its configuration of the maximum number of symbols and selects the corresponding table based thereon, for example, as described above, in the case of maxLength=2 in Table 7.3.1.1.2-7 of TS 38.212 v.15.5.0. The user equipment 410 then uses the index value received from the antenna port field of the uplink grant to determine the correspondingly indexed row of the selected table, and then extracts the number of symbols of the leading DMRS to be used for the number of PUSCH transmissions from the fourth column of the indexed row.

[0141] It is now emphasized that the present disclosure focuses on the case where the number of PUSCH transmissions have different lengths, ie the time domain resources determined based on the uplink grant specify different lengths for at least two of the number of PUSCH transmissions.

[0142] Under such conditions, it has been recognized that the correct operation of the scheduling of multiple PUSCH transmissions can no longer be ensured. Conversely, if the determined uplink resources specify different lengths of the PUSCH transmissions, it cannot be ensured that the determined (single) number of symbols - since it does not distinguish between the various PUSCH transmissions - is suitable for specifying the use of DMRS for each of the (multiple) number of PUSCH transmissions with different lengths.

[0143] In an exemplary implementation, the user equipment 410 uses the determined (single) symbol number to select the corresponding table for PUSCH mapping, for example, in the case where intra-slot frequency hopping is disabled, and the determined symbol number of Table 6.4.1.1.3-3 in TS 38.211v.15.5.0 is "one", and in the case where intra-slot frequency hopping is disabled, and the determined symbol number of Table 6.4.1.1.3-4 in TS38.211v.15.5.0 is "two", which has been described above. From these tables, the user equipment 410 infers the position of the DMRS in the corresponding PUSCH.

[0144] As soon as the number of PUSCH transmissions do not have the same (single) length but have two different lengths, a situation may arise in which the mapping of the DMRS, ie its position in the corresponding PUSCH transmissions is undefined (or unspecified, inconsistent).

[0145] This follows directly from the observation that the length (or duration) of the PUSCH transmission (the first column in the table above) determines the position of the DMRS in the PUSCH transmission (the second to ninth columns in the table above). And some mapping of the two-symbol DMRS is not defined for PUSCH transmissions of shorter length (or duration). Then, the ambiguity between the (single) index value and (multiple) PUSCH transmissions of different lengths may - in the worst case - lead to an undefined (or unspecified, inconsistent) mapping of DMRS to different lengths of PUSCH transmissions.

[0146] Thus, it can be appreciated that, under the condition that different symbol number (or dual symbol) DMRS are allowed and the scheduled PUSCH transmissions have different lengths, the correct operation of the scheduling of multiple PUSCH transmissions cannot be guaranteed.

[0147] To ensure the correct operation of the scheduling of multiple PUSCH transmissions, the user equipment 410 uses the same (determined) time domain resource or a subset of the time domain resource of the received uplink grant to transmit (see, for example, 740- Figure 7 ) the same (specified) or less number of PUSCH transmissions. Specifically, the transmission operation is performed so that none of the at least one pre-DMRS included uses a different number of symbols (multiple). For example, the transmission operation can be performed by the PUSCH transmission transmitter 520-b.

[0148] Even though the focus of the present disclosure is on the case where the number of PUSCH transmissions have different lengths, a solution for the first general scenario is to address the case where correct operation of the scheduling of the PUSCH cannot be ensured by sending the same or less number of PUSCH transmissions by the user equipment 410, with the constraint that none of the included at least one leading DMRS uses a different number of symbols.

[0149] In other words, although the user equipment operates under the condition that different numbers of symbols are allowed for each pre-DMRS, and the received uplink grant is processed with the same goal, i.e., to allow further use of DMRS with different numbers of symbols (e.g., the user equipment explicitly due to Table 7.3.1.1.2-7maxLength=2 of TS 38.212v.15.5.0), the user equipment 410 is explicitly required to send only PUSCH transmissions that do not include pre-DMRS using different numbers of symbols. Thus, the ambiguity between the (single) uplink grant signaling from the base station and the corresponding transmission of (multiple) PUSCH transmissions can be resolved.

[0150] In an exemplary embodiment, the user equipment 410 determines the number of symbols to be used for each of the at least one pre-DMRS based on the different lengths of all PUSCH transmissions in the number of PUSCH transmissions. For example, this may require the user equipment 410 to not only determine the (single) number of symbols based on the received index value, but also to compare this (single) value with the required (e.g., maximum) number of symbols for each different length PUSCH transmission to avoid undefined (or unspecified, inconsistent) mapping of DMRS to different length PUSCH transmissions. If the comparison result indicates a conflict, the user equipment 410 needs to redetermine the number of symbols to be used (now) based on the different lengths of all PUSCH transmissions in the number of PUSCH transmissions.

[0151] The above description is given from the perspective of the user equipment 410. However, this should not be understood as a limitation of the present disclosure. The base station 460 also performs the first general scenario disclosed herein.

[0152] Again, focus is placed on the assumption that the base station 460 is to schedule multiple physical uplink shared channel (PUSCH) transmissions. In an exemplary use case, these PUSCH transmissions may carry repetitions of the same transport block, resulting in multiple PUSCH repetitions including an initial PUSCH transmission and at least one (subsequent) PUSCH repetition.

[0153] refer to Figure 8 , describes a sequence diagram of a base station (BS) receiving multiple PUSCH transmissions according to a first general scenario, i.e., the base station 460 receives multiple PUSCH transmissions that do not include different numbers of symbols for carrying DMRS therein.

[0154] In this context, the base station 460 determines (see, e.g., steps 810- Figure 8 ) time domain resources, the determined time domain resources specify the number of multiple PUSCH transmissions and the length of each of the number of PUSCH transmissions. For example, the determination operation can be performed by the time domain resource determination processing circuit 680-a.

[0155] The base station 460 determines (eg, see steps 820- Figure 8 ) is used for each of at least one pre-DMRS included in the number of PUSCH transmissions, the determined number of symbols being one of a lower number of symbols and a higher number of symbols. For example, the determination operation may be performed by a DMRS symbol number determination processing circuit 680-b.

[0156] If at least two of the number of PUSCH transmissions have different lengths, and if one of the at least two of the number of PUSCH transmissions cannot include a higher number of symbols for each of the at least one leading DMRS, the base station 460 determines (again, see steps 820- Figure 8 ) An index value associated with a lower symbol number from the determined symbol numbers to be used for each of the at least one pre-DMRS included. For example, the determination operation can be performed by the index value determination processing circuit 680-d.

[0157] Thereafter, the base station 460 transmits based on the determined time domain resources for the number of PUSCH transmissions (see, for example, steps 830-84). Figure 8 ) a single uplink grant including an antenna port field having a determined index value to be used for the number of PUSCH transmissions. For example, the sending operation can be performed by an uplink grant transmitter 670-a.

[0158] And, the base station 460 uses the determined time domain resources to receive (see, for example, steps 840- Figure 8 ) The number of PUSCH transmissions, each of the number of PUSCH transmissions includes at least one pre-demodulation reference signal DMRS.

[0159] For the sake of brevity, the operation of the base station is kept rather short. However, this should not be construed as limiting. Rather, the experienced reader will readily appreciate that the same or similar considerations that have been explicitly described for the user equipment find equal application in the operation of the base station, i.e., when it schedules multiple PUSCH transmissions with a single uplink grant.

[0160] It has also been recognized here that correct operation of the scheduling of multiple PUSCH transmissions can no longer be ensured.

[0161] Therefore, the solution to the first general scenario is to address the situation (the situation where correct operation of PUSCH scheduling cannot be ensured) when the base station 460 determines an index value for each of the included at least one pre-DMRS associated with a lower number of symbols in the determined number of symbols.

[0162] Thereby, it can be ensured that the base station 460 receives the same or less number of PUSCH transmissions with the constraint that none of the included at least one pre-DMRS uses a different determined number of symbols.

[0163] First exemplary implementation

[0164] The following first exemplary embodiment is provided to describe in more detail the operation of the user equipment 410 according to the first general scenario, that is, the user equipment 410 performs multiple PUSCH transmissions that do not include different numbers of symbols for carrying a pre-DMRS therein. Fig. 9 , which shows a sequence diagram of a user equipment 410 performing multiple PUSCH transmissions according to a first exemplary embodiment of the first general mechanism.

[0165] This description is given under the assumption that different numbers of symbols are allowed to be used for each pre-DMRS (e.g., maxLength=2). In other words, the present disclosure does not consider the case where only single-symbol DMRS can be used (allowed) as a pre-DMRS, but considers the case where both single-symbol and dual-symbol DMRS can be used (allowed) as a pre-DMRS.

[0166] Having established that the user equipment 410 is to perform multiple PUSCH transmissions, it receives (see, for example, steps 910- Fig. 9 ) a single (eg, one) uplink grant. The uplink grant is communicated to schedule multiple PUSCH transmissions. An uplink grant scheduling transmissions on the uplink is received from base station 460, ie, over a physical uplink shared channel (PUSCH).

[0167] Based on the received uplink grant, the user equipment 410 determines (see, for example, steps 920- Fig. 9 ) Time domain resources to be used for multiple PUSCH transmissions. Generally, the time domain resources determined for each PUSCH transmission should be understood as a certain number of consecutive symbols specified for uplink transmission.

[0168] The present disclosure will again focus on the case where the number of scheduled PUSCH transmissions have different lengths, ie, the time domain resources determined based on the uplink grant specify different lengths for at least two of the number of PUSCH transmissions.

[0169] In this context, the user device 410 determines (see, for example, steps 930- Fig. 9 ) The number of symbols (e.g., single symbol or double symbol) of the preamble DMRS to be used for each PUSCH transmission. To this end, the user equipment 410 determines the number of symbols based on the index value carried in the antenna port field of the received single uplink grant.

[0170] To this end, the user equipment 410 exemplarily refers to its configuration of the maximum number of symbols and selects the corresponding table based thereon, for example, as described above, in the case of maxLength=2 in Table 7.3.1.1.2-7 of TS 38.212 v.15.5.0. The user equipment 410 then uses the received index value from the antenna port field of the uplink grant to determine the correspondingly indexed row of the selected table, and then extracts the number of symbols of the pre-DMRS to be used for the number of PUSCH transmissions from the fourth column of the indexed row.

[0171] Then, the user equipment checks (see, for example, step 940- Fig. 9 ) Whether one of at least two of the number of PUSCH transmissions cannot include a higher number of symbols for each of at least one pre-DMRS.

[0172] To this end, the user equipment 410 uses the determined (single) symbol number to select the corresponding table for PUSCH mapping, for example, in the case where intra-slot frequency hopping is disabled, and the determined symbol number of Table 6.4.1.1.3-3 in TS 38.211v.15.5.0 is "one", and in the case where intra-slot frequency hopping is disabled, and the determined symbol number of Table 6.4.1.1.3-4 in TS 38.211v.15.5.0 is "two", which has been described above. From these tables, the user equipment 410 infers the position of the DMRS in the corresponding PUSCH.

[0173] Specifically, the user equipment 410 determines whether the mapping or position of the DMRS in the PUSCH transmission (the second to ninth columns in the above table) is defined (the case of "No" in step 940) or undefined (the case of "Yes" in step 940) for each different length (or duration) of the PUSCH transmission (the first column in the above table). This determination operation is based on the general understanding that some mapping of the dual-symbol DMRS is undefined (or unspecified, inconsistent) for PUSCH transmissions of shorter lengths (or durations).

[0174] Having established that the determined number of symbols for the DMRS will result in at least one of the number of PUSCH transmissions in an undefined (“yes” case in step 940) mapping (or position) of the DMRS, all PUSCH transmissions in the number of PUSCH transmissions, the user equipment temporarily selects (not in the mapping (or position) of the DMRS) for all PUSCH transmissions in the number of PUSCH transmissions. Fig. 9 However, this temporary selection of a lower number of symbols has to be confirmed because it may involve a change of the DMRS ports to be used.

[0175] For this reason, the user device 410 checks (see, e.g., steps 950- Fig. 9 ) Whether the same DMRS port cannot be used for all PUSCH transmissions in the number of PUSCH transmissions with a lower number of symbols of at least one preceding DMRS temporarily selected to be used for all PUSCH transmissions in the number of PUSCH transmissions. In other words, the index value carried in the antenna port field determines not only the number of DMRS symbols, but also the DMRS port used for all PUSCH transmissions. And in order to avoid any conflict, it must be ensured that the temporarily selected number of symbols can also be used for the same DMRS port determined based on the index value.

[0176] To this end, the user equipment 410 exemplarily refers to a correspondingly selected table, again in the case of Table 7.3.1.1.2-7 of TS 38.212 v.15.5.0 with maxLength=2, as described above. From this table, the user equipment 410 determines the DMRS port (see, e.g., column 3 in the same table), which is indicated by the index value carried in the antenna port field of the received uplink grant (see, e.g., column 1 in the same table). Thereafter, the user equipment checks whether the temporarily selected lower number of symbols (single symbol DMRS) can also be used with the same DMRS port (see DMRS ports 0-3 in rows 2-5 of the same table) (i.e., with the same DMRS port number).

[0177] If this check is positive (the "yes" case in step 950), the user equipment 410 has established that even if a different, lower number of symbols has been selected, this lower number of symbols can be used for the leading DMRS for all PUSCH transmissions in the number of PUSCH transmissions on the same DMRS port indicated by the uplink grant and that the base station 460 expects to receive PUSCH transmissions thereon.

[0178] In this regard, when selecting at least one pre-DMRS, the user equipment 410 selects at least one pre-DMRS for all PUSCH transmissions in the number of PUSCH transmissions, such that:

[0179] A lower number of symbols is used, and

[0180] The same DMRS port number is used,

[0181] The DMRS port number used for all at least one pre-DMRS is the same as the DMRS port number associated with the received index value.

[0182] This result is in Figure 11-13 Examples are given in the following sections.

[0183] For example, according to Table 7.3.1.1.2-7 of TS 38.212v.15.5.0, for the antenna port mapping of a DMRS configuration type with a maximum length of 2 symbols, if any index value 4, 5, 6 or 7 is indicated to be associated with a 2-symbol length DMRS, the corresponding possible indices that are associated and can be used for a 1-symbol length DMRS are 0, 1, 2 or 3, respectively.

[0184] Furthermore, if the check is objectionable (case "No" in step 950), the user equipment 410 has established that a different, temporarily selected, lower number of symbols cannot be used. The temporarily selected lower number of symbols cannot be used on the same DMRS port as the DMRS port determined based on the index value. In other words, for this number of PUSCH transmissions, this would require the use of a different DMRS port.

[0185] In other words, the DMRS port indicated by the uplink grant and on which the base station 460 expects to receive a PUSCH transmission cannot be used with the temporarily selected lower symbol number for the DMRS.

[0186] In this regard, when selecting at least one pre-DMRS, the user equipment 410 skips (see, for example, steps 970- Fig. 9 ) at least one PUSCH transmission among the number of PUSCHs, the at least one PUSCH transmission:

[0187] · cannot include a higher number of symbols for each of at least one preceding DMRS, and

[0188] • The same DMRS port number as the one associated with the received index value cannot be used.

[0189] Then, the user device 410 sends (see, for example, steps 980- Fig. 9 ) A smaller number of PUSCH transmissions is used, so that for the remaining PUSCH transmissions that are not skipped among the number of PUSCH transmissions, a higher number of symbols and the same DMRS port number are used.

[0190] In summary, the user equipment 410 uses the same (determined) time domain resources determined based on the received uplink grant or a subset of the time domain resources to send the same (see the case of "yes" in step 950) or less (see the case of "no" in step 950) number of PUSCH transmissions. Specifically, the transmission is performed so that none of the included at least one pre-DMRS uses a different number of symbols (multiple).

[0191] The above description of the first exemplary implementation has been given from the perspective of the user equipment 410. However, this should not be understood as a limitation of the present disclosure. The base station 460 equally performs the first exemplary embodiment disclosed herein, i.e., the base station 460 receives multiple PUSCH transmissions that do not include different numbers of symbols for carrying a pre-DMRS therein.

[0192] refer to Fig.10 , which shows a sequence diagram of a base station 460 scheduling multiple PUSCH transmissions according to a first exemplary embodiment of the first general mechanism. In an exemplary use case, these PUSCH transmissions may carry repetitions of the same transport block, resulting in multiple PUSCH repetitions including an initial PUSCH transmission and at least one (subsequent) PUSCH repetition.

[0193] In this context, the base station 460 determines (see, e.g., steps 1010- Fig.10 ) time domain resources, the determined time domain resources specify the number of multiple PUSCH transmissions and the length of each of the number of PUSCH transmissions.

[0194] The present disclosure will again focus on the case where the number of scheduled PUSCH transmissions have different lengths, ie, the time domain resources specify different lengths for at least two of the number of PUSCH transmissions.

[0195] Base station 460 determines (see, for example, steps 1020- Fig.10 ) is a number of symbols to be used for each of at least one pre-DMRS included in the number of PUSCH transmissions, the determined number of symbols being one of a lower and an upper number of symbols.

[0196] Then, the base station 460 checks (see, for example, steps 1030- Fig.10 ) Whether one of the number of PUSCH transmissions cannot include a higher number of symbols for each of the at least one pre-DMRS.

[0197] To this end, the base station 460 uses the determined (single) symbol number to select the corresponding table for PUSCH mapping, for example, in the case where intra-slot frequency hopping is disabled, and the determined symbol number of Table 6.4.1.1.3-3 in TS 38.211v.15.5.0 is "one", and in the case where intra-slot frequency hopping is disabled, and the "determined symbol number of Table 6.4.1.1.3-4 in TS 38.211v.15.5.0 is "two", as described above. From these tables, the user equipment 410 infers the position of the DMRS in the corresponding PUSCH.

[0198] Specifically, the base station 460 determines whether the mapping or position of the DMRS in the PUSCH transmission (the second to ninth columns in the above table) is defined (the case of "No" in step 1030) or undefined (the case of "Yes" in step 1030) for each different length (or duration) of the PUSCH transmission (the first column in the above table). This determination operation is based on the general understanding that some mapping of the dual-symbol DMRS is undefined (or unspecified, inconsistent) for PUSCH transmissions of shorter length (or duration).

[0199] Having established that the determined number of symbols for the DMRS will result in at least one of the number of PUSCH transmissions in an undefined (“yes” case in step 1030) mapping (or position) of the DMRS, the base station 460 selects (not in step 1030) for all PUSCH transmissions in the number of PUSCH transmissions Fig.10 (explicitly shown in FIG. 5 ) All PUSCH transmissions in this number of PUSCH transmissions have at least one leading DMRS (single-symbol DMRS) with a lower number of symbols.

[0200] Having established that the determined number of symbols for the DMRS will result in all PUSCH transmissions in the number of PUSCH transmissions in the defined ("No" case in step 1030) mapping (or position) of the DMRS, the base station 460 selects (not in step 1030) for all PUSCH transmissions in the number of PUSCH transmissions Fig.10 (explicitly shown in FIG. 5 ) All PUSCH transmissions among the number of PUSCH transmissions have at least one leading DMRS (single-symbol DMRS) with a higher number of symbols.

[0201] The base station 460 then determines the index value associated with the lower number of symbols (see, e.g., steps 1040- Fig.10 ), or an index value associated with a higher number of symbols to be used for all PUSCH transmissions in that number of PUSCH transmissions (see, e.g., steps 1050- Fig.10 ), i.e., for each of the at least one pre-DMRS included. The determined index value is also associated with the same DMRS port.

[0202] Thereafter, the base station 460 sends a PUSCH transmission based on the determined number of time domain resources (see, for example, steps 1060- Fig.10 ) a single uplink grant comprising an antenna port field having an index value determined to be used for the number of PUSCH transmissions.

[0203] And, the base station 460 receives using the determined time domain resources (see, for example, steps 1070- Fig.10) The number of PUSCH transmissions, each of the number of PUSCH transmissions includes at least one pre-demodulation reference signal DMRS.

[0204] For the sake of brevity, the operation of the base station is kept rather short. However, this should not be construed as limiting. Rather, the experienced reader will readily appreciate that the same or similar considerations that have been explicitly described for the user equipment find equal application in the operation of the base station, i.e., when it schedules multiple PUSCH transmissions with a single uplink grant.

[0205] Second general scenario

[0206] Reference now Fig.14 , describes a sequence diagram of a user equipment (UE) performing multiple PUSCH transmissions according to a second general scenario, i.e., the user equipment 410 performs multiple PUSCH transmissions that may include different numbers of pre-DMRS symbols carried therein, however, for none of them using a different DMRS port number.

[0207] According to general understanding, the transmission and reception operations of multiple PUSCH transmissions must use DMRS ports consistently. In other words, the leading DMRS of the PUSCH transmission must use a consistent DMRS port (e.g., the same DMRS port number) indicated by the uplink grant, and expect to be received on that port. Without this consistency, the reception of multiple PUSCH transmissions will be unsuccessful because the DMRS included therein cannot contribute to accurate channel estimation and therefore cannot contribute to coherent demodulation at the receiver side.

[0208] For this reason, the second general scenario helps avoid this inconsistency, namely, for the case where multiple PUSCH transmissions are scheduled with different lengths, and different numbers of symbols for DMRS (e.g., single-symbol or double-symbol DMRS) are allowed for the pre-DMRS carried therein.

[0209] Having established that the user equipment 410 is to perform multiple PUSCH transmissions, it receives (see, for example, steps 1410- Fig.14 ) a single (eg, one) uplink grant. The uplink grant is suitable for scheduling multiple PUSCH transmissions. An uplink grant scheduling transmissions on the uplink is received from base station 460, i.e., via a physical uplink shared channel (PUSCH). For example, the receiving operation may be performed by Figure 5 The UL grant receiver 520-a performs.

[0210] The user equipment 410 receives an uplink grant including an antenna port field with an index value. The index value can be used for many purposes for the user equipment 410, for example, to indicate the (multiple) antenna ports on which the PUSCH transmission is to be performed. In other words, the index value is to be used for multiple PUSCH transmissions scheduled by the uplink grant.

[0211] In view of 3GPP terminology, the described uplink grant including the antenna port field may imply the signaling of downlink control information (DCI) format 0-1. For a detailed description of DCI format 0-1, reference is made to Section 7.3.1.1.2 of 3GPP Technical Specification TS 38.212 v.15.5.0, which is incorporated herein by reference. In addition, the other (alternative) format for conveying dynamic uplink grants in 3GPP systems, i.e., DCI format 0-0, does not include the antenna port field, because all PUSCH transmissions will exclusively use the pre-configured port numbered 0.

[0212] Also in view of 3GPP terminology, the uplink grant described as including the antenna port field may alternatively imply signaling of a ConfiguredGrantConfig information element (IE). For a detailed description of the ConfiguredGrantConfig IE, please refer to Section 6.3.2 of 3GPP Technical Specification TS 38.331 v.15.5.0, entitled "Radio Resource Control (RRC) protocol specification (Release 15)", which is incorporated herein by reference. It is apparent from the ASN.1 annotations that not all ConfiguredGrantConfig IEs include the antenna port field, as it is included in the sequence of fields that are specified as optional for the IE.

[0213] Based on the received uplink grant, the user equipment 410 determines (see, e.g., steps 1420- Fig.14 ) Time domain resources to be used for multiple PUSCH transmissions. Generally speaking, the determined time domain resources for each PUSCH transmission should be understood as a certain number of consecutive symbols designated for uplink transmission. For example, the determination operation can be performed by the time domain resource determination processing circuit 530-a.

[0214] In more detail, the determined time domain resources specify the (e.g., maximum or total) number of PUSCH transmissions being scheduled by the uplink grant, and specify the length (e.g., in symbols) of each of the number of PUSCH transmissions. The time domain resources have been allocated in advance by the base station 460 for use by the user equipment 410.

[0215] In an exemplary implementation, the determined time domain resources may also specify the position of at least one PUSCH transmission of the number of PUSCH transmissions, i.e., the position of the first PUSCH transmission of the number of PUSCH transmissions or of all PUSCH transmissions. For example, such a position may be specified based on a (relative) time slot offset and an (absolute) symbol number starting within a specified time slot. Alternatively, such a position may be inferred (e.g. in a technical specification) in the form of consecutive PUSCH transmissions, i.e., the last symbol of the preceding PUSCH transmission directly follows the first symbol of the subsequent PUSCH transmission.

[0216] However, in the context of the present disclosure, it is sufficient that the user equipment 410 can (in practice) determine the time domain resources to be used for multiple PUSCH transmissions based on the received uplink grant. In other words, the present disclosure is not limited to any of the exemplary embodiments described above for the first general scenario.

[0217] All the above mechanisms are based on time domain resource allocations, which are semi-statically (in advance) configured via RRC. Moreover, it is not possible to reflect all conceivable time slot formats in advance. Therefore, a dynamically indicated change in the time slot format may require an adaptation of the semi-statically configured time domain resource allocation, i.e., when determining the time domain resources that can (actually) be used for PUSCH transmission.

[0218] One possibility of a conflict may be caused by the signaling of a changed slot format that specifies that a symbol of a slot changes from UL to DL. Assuming that the symbol was previously intended to be used as part of the indicated time domain resource allocation, the change from UL to DL that it specifies will result in a conflict that has been processed (or handled) on the user equipment side.

[0219] Such a conflict can be resolved by the user equipment shifting the signaled time domain resource allocation so that the determined time domain resources only occupy the UL symbols of the most recently assigned time slot.

[0220] Another possibility for a collision may result from the signaling of a changed slot format that designates fewer slot symbols as UL and more symbols as DL. Then, even if the individual time domain resource allocations are not affected by the slot format change, it may happen that the indicated time domain resource allocations are distributed across multiple slots. Specifically, if the signaled time domain resource allocations belonging to a single PUSCH transmission are distributed across multiple slots (across slot boundaries), this will result in a collision that again has to be handled (or handled) on the user equipment side, since PUSCH transmissions across slot boundaries are not allowed.

[0221] Such a conflict may be resolved by the user equipment segmenting the affected PUSCH transmission at the slot boundary into two (consecutive) PUSCH transmissions which no longer cross the slot boundary.

[0222] It is worth noting that due to this segmentation, the user equipment 410 will have to send more PUSCH transmissions than have been scheduled by the uplink grant.

[0223] For the sake of example, assume that user equipment 410 receives an uplink grant that is scheduling three (3) PUSCH transmissions. Assuming that one (1) of these PUSCH transmissions is segmented due to crossing a slot boundary, then the one (1) affected PUSCH transmission will actually result in two (2) PUSCH transmissions, i.e., one (1) PUSCH transmission that is segmented before the slot boundary and another (1) PUSCH transmission that is segmented after the slot boundary. The received uplink grant will then result in user equipment 410 determining time domain resources for a total of four (4) PUSCH transmissions.

[0224] In summary, there are a variety of conceivable implementations that allow the user equipment 410 to determine the time domain resources to be used for multiple PUSCH transmissions based on the received uplink grant. However, the present disclosure should not be construed as being limited to any of these exemplary embodiments.

[0225] After determining the time domain resources for the (possibly higher) number of PUSCH transmissions based on the received uplink grant, the user equipment 410 composes PUSCH transmissions for their subsequent transmissions. Each of the number of PUSCH transmissions includes at least one pre-pended demodulation reference signal (DMRS) to enable coherent demodulation of the PUSCH transmission.

[0226] In this context, the user device 410 determines (see, for example, steps 1430- Fig.14 ) The DMRS port number of the pre-DMRS to be used for each PUSCH transmission (e.g., DMRS port number 0-7 for type 1 configuration or DMRS port number 0-11 for type 2 configuration). To this end, the user equipment 410 determines the DMRS port number based on the index value carried in the antenna port field of the received single uplink grant. For example, the determination operation can be performed by the DMRS port number determination processing circuit 530-c of the DMRS.

[0227] The key point is the fact that the present disclosure focuses on the case where different numbers of symbols are allowed for each pre-DMRS. In other words, the present disclosure does not consider the case where only single-symbol DMRS can be used (allowed) as a pre-DMRS, but considers the case where both single-symbol and dual-symbol DMRS can be used (allowed) as a pre-DMRS.

[0228] There are two different steps before the user equipment 410 actually knows whether to use dual-symbol DMRS or single-symbol DMRS for certain PUSCH transmissions. In the first step, the user equipment 410 is signaled an indication indicating whether (generally) different numbers of symbols are allowed to be used for PUSCH transmissions. This indication is then used when determining the (actual) number of symbols to be used as the pre-DMRS included in each PUSCH transmission.

[0229] In an exemplary implementation, the user equipment 410 is provided with a configuration that specifies the maximum number of symbols allowed to be used as pre-DMRS. If the maximum number of symbols is "two", then the use of either dual-symbol DMRS or single-symbol DMRS is allowed.

[0230] In a second step, the user equipment determines the (actual) number of symbols to be used for each pre-DMRS of the number of PUSCH transmissions. The determination is based on the index value carried in the antenna port field included in the received uplink grant. In this regard, since the index value is carried in the received uplink grant, it is directly linked to the corresponding number of PUSCH transmissions.

[0231] The number of symbols allowed (see the first step above) also has an impact on the determination of the DMRS port number.

[0232] When different numbers of symbols are allowed for the pre-DMRS, then each of the different numbers of symbols in conjunction with a separate DMRS port number must be individually indicated from the base station 460 to the user equipment 410. For this purpose, in case of different numbers of symbols allowed, the index value communicated within the uplink grant allows an unambiguous indication of the (actual) number of symbols to be used for the pre-DMRS.

[0233] Meanwhile, the index value indicates not only the (actual) number of symbols to be used for the pre-DMRS but also indicates in combination the number of symbols used for the pre-DMRS for the DMRS included in the number of PUSCH transmissions and the DMRS port number.

[0234] Now, if different numbers of symbols are allowed, the index value can only effectively achieve an unambiguous indication of the (actual) number of symbols to be used if the different index values ​​are organized so that the same DMRS port number can be indexed for all different numbers of symbols allowed for the DMRS. Otherwise, the DMRS port cannot be used with both different numbers of symbols allowed.

[0235] In another exemplary implementation, the user equipment 410 determines the DMRS port number of the leading DMRS for each of the number of PUSCH transmissions. To this end, the user equipment 410 refers to its configuration of the maximum number of symbols and selects the corresponding table based thereon, for example, as described above, in the case of maxLength=2 of Table 7.3.1.1.2-7 of TS 38.212 v.15.5.0. The user equipment 410 then uses the received index value of the antenna port field from the uplink grant to determine the correspondingly indexed row of the selected table, and then extracts the DMRS port number of each of the leading DMRS to be used for the number of PUSCH transmissions from the third column of the indexed row.

[0236] As mentioned above, the impact of the number of symbols allowed can also be seen in Table 7.3.1.1.2-7 of TS 38.212 v.15.5.0. This table is designed for the case where different numbers of symbols are allowed, i.e., for the case where maxLength=2. Therefore, each index value (first column of the table) is associated in an unambiguous way with the (actual) number of symbols to be used for the pre-placed DMRS (fourth column of the table). At the same time, each index value (first column of the table) is also associated in an unambiguous way with the DMRS port number (third column of the table).

[0237] In addition, since different DMRS ports identified by numbers can be used for all different numbers of pre-DMRS symbols, different DMRS port numbers 0-3 can be used for single-symbol DMRS (see rows 2 to 5 of the table) and dual-symbol DMRS (see rows 6 to 9 of the table). Only DMRS port numbers 4-7 can be used only for dual-symbol DMRS (see rows 10 to 13 of the table).

[0238] Therefore, the allowed number of symbols has a significant impact on the determination of the DMRS port number, since it not only dictates the table to be used but also dictates the case where at least some DMRS port numbers (e.g., DMRS port numbers 0-3 in the table above) can be indexed using two different index values, i.e., for each allowed (actual) number of symbols.

[0239] It is now emphasized that the present disclosure focuses on the case where the number of PUSCH transmissions have different lengths, ie the time domain resources determined based on the uplink grant specify different lengths for at least two of the number of PUSCH transmissions.

[0240] Under such conditions, it has been recognized that the correct operation of the scheduling of multiple PUSCH transmissions can no longer be ensured. Conversely, if the determined uplink resources specify different lengths for the PUSCH transmissions, it cannot be ensured that the determined (single) number of symbols - since it does not distinguish between the various PUSCH transmissions - is suitable for specifying the use of DMRS for each of the (multiple) number of PUSCH transmissions with different lengths.

[0241] In an exemplary implementation, the user equipment 410 uses the determined (single) symbol number to select the corresponding table for PUSCH mapping, for example, in the case where intra-slot frequency hopping is disabled, and the determined symbol number of Table 6.4.1.1.3-3 in TS 38.211v.15.5.0 is "one", and in the case where intra-slot frequency hopping is disabled, and the determined symbol number of Table 6.4.1.1.3-4 in TS38.211v.15.5.0 is "two", which has been described above. From these tables, the user equipment 410 infers the position of the DMRS in the corresponding PUSCH.

[0242] As soon as the number of PUSCH transmissions do not have the same (single) length but have two different lengths, a situation may arise where the mapping of the DMRS, ie its position in the corresponding PUSCH transmissions is undefined (or unspecified, inconsistent).

[0243] This follows directly from the observation that the length (or duration) of the PUSCH transmission (the first column in the table above) determines the position of the DMRS in the PUSCH transmission (the second to ninth columns in the table above). And some mapping of the dual-symbol DMRS is not defined for PUSCH transmissions of shorter length (or duration). Then, the ambiguity between the (single) index value and (multiple) PUSCH transmissions of different lengths may - in the worst case - lead to an undefined (or unspecified, inconsistent) mapping of DMRS to PUSCH transmissions of different lengths.

[0244] Thus, it can be appreciated that, under the condition that different symbol number (or dual symbol) DMRS are allowed and the scheduled PUSCH transmissions have different lengths, the correct operation of the scheduling of multiple PUSCH transmissions cannot be guaranteed.

[0245] To ensure the correct operation of the scheduling of multiple PUSCH transmissions, the user equipment 410 uses the same (determined) uplink granted time domain resource or a subset of the time domain resource to transmit (see, for example, 1440- Fig.14 ) the same (specified) or less number of PUSCH transmissions. Specifically, the transmission operation is performed so that none of the at least one pre-DMRS included uses a different number of symbols (multiple). For example, the transmission operation can be performed by the PUSCH transmission transmitter 520-b.

[0246] Even though the focus of the present disclosure is on the case where the number of PUSCH transmissions have different lengths, a solution for the second general scenario is to address the case where correct operation of the scheduling of the PUSCH cannot be ensured by sending the same or less number of PUSCH transmissions by the user equipment 410, with a constraint that none of the at least one pre-DMRS included uses a different determined DMRS port number.

[0247] Although the user equipment operates under the condition that a different number of symbols is allowed for each leading DMRS, and the received uplink grant is processed with the same goal, i.e., allowing further use of DMRS with a different number of symbols (e.g., the user equipment explicitly does so due to Table 7.3.1.1.2-7maxLength=2 of TS 38.212 v.15.5.0), the user equipment 410 is explicitly required to only send PUSCH transmissions that do not include leading DMRS using different DMRS port numbers.

[0248] In other words, this second general scenario attempts to achieve the goal of allowing further use of DMRS with different numbers of symbols, but it is recognized that not all different DMRS port numbers can be used with all symbols in the different allowed numbers of symbols (for example, in Table 7.3.1.1.2-7 of TS 38.212v.15.5.0, maxLength=2, DMRS ports 0-3 can be used with both single-symbol DMRS and double-symbol DMRS, while DMRS ports 4-7 can only be used with double-symbol DMRS).

[0249] Thus, it is prevented that some PUSCH transmissions in the number of PUSCH transmissions (e.g., having more symbol numbers used for DMRS) use different DMRS port numbers (e.g., DMRS ports 4-7 in the above table) than DMRS port numbers (e.g., DMRS ports 0-3 in the above table) used for other PUSCH transmissions in the number of PUSCH transmissions (e.g., having less symbol numbers used for DMRS). In other words, although in the second general scenario, different symbol numbers used for DMRS are generally allowed in the number of PUSCH transmissions, it is ensured that the same DMRS port is used for all PUSCH transmissions in the number of PUSCH transmissions, which also corresponds to the DMRS port indicated by the index value of the antenna port field carried in the (single) uplink grant.

[0250] Thereby, the ambiguity between the (single) uplink grant signaling from the base station and the corresponding transmission of (multiple) PUSCH transmissions may be resolved.

[0251] In an exemplary embodiment, the user equipment 410 determines the number of symbols to be used for each of the at least one pre-DMRS based on the different lengths of all PUSCH transmissions in the number of PUSCH transmissions. For example, this may require the user equipment 410 to not only determine the (single) number of symbols based on the received index value, but also to additionally compare the (single) DMRS port number and the corresponding indexed number of symbols with the (e.g., maximum) number of symbols required for each different length PUSCH transmission to avoid undefined (or unspecified, inconsistent) mapping of DMRS to different length PUSCH transmissions. If the comparison indicates a conflict, the user equipment 410 needs to redetermine the number of symbols to be used (now) based on the different lengths of all PUSCH transmissions in the number of PUSCH transmissions.

[0252] The above description is given from the perspective of the user equipment 410. However, this should not be understood as limiting the present disclosure. The base station 460 similarly performs the second general scenario disclosed herein.

[0253] Again, focus is placed on the assumption that the base station 460 is to schedule multiple physical uplink shared channel (PUSCH) transmissions. In an exemplary use case, these PUSCH transmissions may carry repetitions of the same transport block, resulting in multiple PUSCH repetitions including an initial PUSCH transmission and at least one (subsequent) PUSCH repetition.

[0254] refer to Fig.15, describes a sequence diagram of a base station (BS) receiving multiple PUSCH transmissions according to a second general scenario, i.e., the base station 460 receives multiple PUSCH transmissions that do not include different numbers of symbols for carrying DMRS therein.

[0255] In this context, the base station 460 determines (see, e.g., steps 1510- Fig.15 ) time domain resources, the determined time domain resources specify the number of multiple PUSCH transmissions and the length of each of the number of PUSCH transmissions. For example, the determination operation can be performed by the time domain resource determination processing circuit 680-a.

[0256] Base station 460 determines (see, for example, steps 1520- Fig.15 ) is used for each of at least one pre-DMRS included in the number of PUSCH transmissions, the determined number of symbols being one of a lower number of symbols and a higher number of symbols. For example, the determination operation may be performed by a DMRS symbol number determination processing circuit 680-b.

[0257] If at least two of the number of PUSCH transmissions have different lengths, and if one of the at least two of the number of PUSCH transmissions cannot include a higher number of symbols for each of the at least one pre-DMRS, the base station 460 determines (see steps 1530- Fig.15 ) an index value associated with a lower number of symbols from the determined number of symbols, and a DMRS port number, wherein the same DMRS port number may also be used for at least one leading DMRS having the determined lower number of symbols. For example, the determination operation may be performed by the index value determination processing circuit 680-d.

[0258] In an exemplary implementation, if only some PUSCH transmissions cannot include a higher number of symbols for DMRS, the base station 460 determines an index value from a table, e.g., maxLength=2 of Table 7.3.1.1.2-7 of TS 38.212 v.15.5.0, such that use of DMRS ports 4-7 is prevented and use of DMRS ports 0-3 is allowed. Only in this way can the same DMRS port number be used with higher and lower numbers of symbols without non-allowed DMRS port changes during signaling of that number of PUSCH transmissions.

[0259] Importantly, since each of DMRS ports 0-3 can be indicated by a different index value, base station 460 determines the index value corresponding to the higher of the symbol numbers, according to, for example, Table 6.4.1.1.3-3 and Table 6.4.1.1.3-4 in TS 38.211v.15.5.0, which still allows mapping (or location) of DMRS of corresponding lengths for each of the number of PUSCH transmissions.

[0260] Thereafter, the base station 460 transmits based on the determined time domain resources for the number of PUSCH transmissions (see, for example, steps 1540- Fig.15 ) a single uplink grant including an antenna port field having an index value determined to be used for the number of PUSCH transmissions. For example, the sending operation can be performed by an uplink grant transmitter 670-a.

[0261] And, the base station 460 uses the determined time domain resources to receive (see, for example, steps 1550- Fig.15 ) The number of PUSCH transmissions, each of the number of PUSCH transmissions includes at least one pre-demodulation reference signal DMRS.

[0262] For the sake of brevity, the operation of the base station is kept rather short. However, this should not be construed as limiting. Rather, the experienced reader will readily appreciate that the same or similar considerations that have been explicitly described for the user equipment find equal application in the operation of the base station, i.e., when it schedules multiple PUSCH transmissions with a single uplink grant.

[0263] It has also been recognized here that correct operation of the scheduling of multiple PUSCH transmissions can no longer be ensured.

[0264] Therefore, the solution to the second general scenario is when the base station 460 determines an index value associated with a lower number of symbols among the determined numbers of symbols, and a DMRS port number, where the same DMRS port number can also be used for at least one preceding DMRS with the determined lower number of symbols, to resolve the situation (the situation where correct operation of PUSCH scheduling cannot be ensured).

[0265] Thereby, it can be ensured that the base station 460 receives the same or less number of PUSCH transmissions with the constraint that a different determined number of symbols is not used for any of the included at least one pre-DMRS.

[0266] Second Exemplary Embodiment

[0267] The following second exemplary embodiment is provided to describe in more detail the operation of the user equipment 410 according to the second general scenario, that is, the user equipment 410 performs multiple PUSCH transmissions that do not include different numbers of symbols for carrying a pre-DMRS therein. Fig.16 , which shows a sequence diagram of a user equipment 410 performing multiple PUSCH transmissions according to a second exemplary embodiment of the second general mechanism.

[0268] This description is given under the assumption that different numbers of symbols are allowed to be used for each pre-DMRS (e.g., maxLength=2). In other words, the present disclosure does not consider the case where only single-symbol DMRS can be used (allowed) as a pre-DMRS, but considers the case where both single-symbol and dual-symbol DMRS can be used (allowed) as a pre-DMRS.

[0269] Having established that the user equipment 410 is to perform multiple PUSCH transmissions, it receives (see, for example, steps 1610- Fig.16 ) a single (eg, one) uplink grant. The uplink grant is communicated to schedule multiple PUSCH transmissions. An uplink grant scheduling transmissions on the uplink is received from base station 460, ie, over a physical uplink shared channel (PUSCH).

[0270] Based on the received uplink grant, the user equipment 410 determines (see, e.g., steps 1620- Fig.16 ) Time domain resources to be used for multiple PUSCH transmissions. Generally, the time domain resources determined for each PUSCH transmission should be understood as a certain number of consecutive symbols specified for uplink transmission.

[0271] The present disclosure will again focus on the case where the number of scheduled PUSCH transmissions have different lengths, ie, the time domain resources determined based on the uplink grant specify different lengths for at least two of the number of PUSCH transmissions.

[0272] In this context, the user device 410 determines (see, for example, steps 1630- Fig.16 ) The number of symbols (e.g., single symbol or double symbol) of the preamble DMRS to be used for each PUSCH transmission. To this end, the user equipment 410 determines the number of symbols based on the index value carried in the antenna port field of the received single uplink grant.

[0273] To this end, the user equipment 410 exemplarily refers to its configuration of the maximum number of symbols and selects the corresponding table based thereon, for example, as described above, in the case of maxLength=2 in Table 7.3.1.1.2-7 of TS 38.212 v.15.5.0. The user equipment 410 then uses the received index value from the antenna port field of the uplink grant to determine the correspondingly indexed row of the selected table, and then extracts the number of symbols of the pre-DMRS to be used for the number of PUSCH transmissions from the fourth column of the indexed row.

[0274] Then, the user device checks (see, for example, step 1640- Fig.16 ) Whether some (one or more) of at least two transmissions of the number of PUSCH transmissions cannot include a higher number of symbols for each of the at least one pre-DMRS.

[0275] In this context, the term "some" should be understood to indicate a (specific) subset of all PUSCH transmissions in the number of PUSCH transmissions. The term is used consistently in the rearrangement described herein. For example, some of the number of PUSCH transmissions may be the (specific) third PUSCH transmission, rather than the first and second PUSCH transmissions in the total number of three PUSCH transmissions.

[0276] To this end, the user equipment 410 uses the determined (single) symbol number to select the corresponding table for PUSCH mapping, for example, in the case where intra-slot frequency hopping is disabled, and the determined symbol number of Table 6.4.1.1.3-3 in TS 38.211v.15.5.0 is "one", and in the case where intra-slot frequency hopping is disabled, and the determined symbol number of Table 6.4.1.1.3-4 in TS 38.211v.15.5.0 is "two", which has been described above. From these tables, the user equipment 410 infers the position of the DMRS in the corresponding PUSCH.

[0277] Specifically, the user equipment 410 determines whether the mapping or position of the DMRS in the PUSCH transmission (the second to ninth columns in the above table) is defined (the case of "No" in step 1640) or undefined (the case of "Yes" in step 1640) for each different length (or duration) of the PUSCH transmission (the first column in the above table). This determination operation is based on the general understanding that some mapping of the dual-symbol DMRS is undefined (or unspecified, inconsistent) for PUSCH transmissions of shorter lengths (or durations).

[0278] Having established that the determined number of symbols for DMRS will result in some (one or more) of the number of PUSCH transmissions in an undefined ("yes" case in step 1640) mapping (or position) of DMRS, the user equipment temporarily selects ( Fig.16 At least one leading DMRS (single-symbol DMRS) with a lower number of symbols (not explicitly shown in FIG. 1 ) must, however, be confirmed for this temporary selection of a lower number of symbols, since it may involve a change in the DMRS ports to be used.

[0279] For this reason, the user device 410 checks (see, e.g., steps 1650- Fig.16 ) Whether the same DMRS port cannot be used with a temporarily selected lower number of symbols of at least one preceding DMRS to be used for some of the number of PUSCH transmissions (see above) for all PUSCH transmissions of the number of PUSCH transmissions. In other words, the index value carried in the antenna port field determines not only the number of DMRS symbols, but also the DMRS ports of the same some (see above) to be used for the number of PUSCH transmissions. And in order to avoid any conflict, it must be ensured that the temporarily selected number of symbols can also be used for the same DMRS port determined based on the index value.

[0280] To this end, the user equipment 410 exemplarily refers to the correspondingly selected table, again in the case of Table 7.3.1.1.2-7maxLength=2 of TS 38.212 v.15.5.0, as described above. From this table, the user equipment 410 determines the DMRS port (see, e.g., column 3 of the same table) indicated by the index value carried in the antenna port field of the received uplink grant (see, e.g., column 1 of the same table). Thereafter, the user equipment checks whether the temporarily selected lower number of symbols (single-symbol DMRS) can also be used with the same DMRS port (see DMRS ports 0-3 in rows 2-5 of the same table) (i.e., with the same DMRS port number).

[0281] If this check is positive (the "yes" case in step 1650), the user equipment 410 has established that even if a different, lower number of symbols has been selected, this lower number of symbols can be used for the pre-DMRS for some of the number of PUSCH transmissions on the same DMRS port indicated by the uplink grant (see above), and the base station 460 expects to receive PUSCH transmissions thereon.

[0282] For the remaining (or other) PUSCH transmissions of the number of PUSCH transmissions, the user equipment 410 non-temporarily selects the number of symbols so that it corresponds to the (single) number of symbols of the pre-DMRS determined based on the index value carried in the antenna port field of the received single uplink grant. In other words, for those of the number of PUSCH transmissions that may include a higher number of symbols for DMRS, it also uses the higher number of symbols indicated in the single uplink grant.

[0283] In this regard, when selecting at least one pre-DMRS, the user equipment 410 selects all PUSCH transmissions of the number of PUSCH transmissions (see, for example, steps 1660- Fig.16 ) at least one pre-DMRS, such that:

[0284] The lower and upper symbol numbers are used for at least one preamble DMRS, and

[0285] The same DMRS port number is used for both lower and higher symbol numbers,

[0286] The DMRS port number to be used for all the pre-DMRSs in the at least one pre-DMRS is the same as the DMRS port number associated with the received index value.

[0287] The result is Figure 18-Figure 20 For example, according to Table 7.3.1.1.2-7 of TS 38.212 v.15.5.0, for the antenna port mapping of the DMRS configuration type with a maximum symbol length of 2, if any index value 4, 5, 6 or 7 is indicated to be associated with a 2-symbol length DMRS, the corresponding possible indexes associated and usable for a 1-symbol length DMRS are 0, 1, 2 or 3, respectively.

[0288] Furthermore, if the check is objectionable (case "No" in step 1650), the user equipment 410 has established that a different lower number of symbols that was temporarily selected cannot be used. The lower number of symbols that was temporarily selected cannot be used on the same DMRS port as the DMRS port determined based on the index value. In other words, for this number of PUSCH transmissions, this would require the use of a different DMRS port.

[0289] In other words, the DMRS port indicated by the uplink grant and on which the base station 460 expects to receive a PUSCH transmission cannot be used with the temporarily selected lower number of symbols for DMRS.

[0290] In this regard, when selecting at least one pre-DMRS, the user equipment 410 skips (see, for example, steps 1670- Fig.16) some (see above) of the number of PUSCHs, the some PUSCH transmissions:

[0291] · cannot include a higher number of symbols for each of at least one pre-DMRS, and

[0292] • The same DMRS port number as the one associated with the received index value cannot be used.

[0293] Then, the user device 410 sends (see, for example, steps 1680- Fig.16 ) A smaller number of PUSCH transmissions is used so that a higher number of symbols and the same DMRS port number are used for the remaining (or other) PUSCH transmissions that are not skipped among the number of PUSCH transmissions.

[0294] In summary, the user equipment 410 uses the same (determined) time domain resources determined based on the received uplink grant or a subset of the time domain resources to send the same (see the case of "yes" in step 1650) or less (see the case of "no" in step 1650) number of PUSCH transmissions. Specifically, the transmission is performed so that none of the included at least one pre-DMRS uses a different number of symbols (multiple).

[0295] The above description of the second exemplary implementation has been given from the perspective of the user equipment 410. However, this should not be understood as a limitation of the present disclosure. The base station 460 equivalently performs the first exemplary embodiment disclosed herein, that is, the base station 460 receives multiple PUSCH transmissions that do not include different numbers of symbols for carrying a pre-DMRS therein.

[0296] refer to Fig.17 , which shows a sequence diagram of a base station 460 scheduling multiple PUSCH transmissions according to a second exemplary embodiment of the first general mechanism. In an exemplary use case, these PUSCH transmissions may carry repetitions of the same transport block, resulting in multiple PUSCH repetitions including an initial PUSCH transmission and at least one (subsequent) PUSCH repetition.

[0297] In this context, the base station 460 determines (see, e.g., steps 1710- Fig.17 ) time domain resources, the determined time domain resources specify the number of multiple PUSCH transmissions and the length of each of the number of PUSCH transmissions.

[0298] The present disclosure will again focus on the case where the number of scheduled PUSCH transmissions have different lengths, ie, the time domain resources specify different lengths for at least two of the number of PUSCH transmissions.

[0299] Base station 460 determines (see, e.g., steps 1720- Fig.17 ) is a number of symbols to be used for each of at least one leading DMRS included in the number of PUSCH transmissions, the determined number of symbols being one of a lower and an upper number of symbols.

[0300] Then, the base station 460 checks (see, for example, steps 1730- Fig.17 ) Whether some of the number of PUSCH transmissions may not include a higher number of symbols for each of the at least one pre-DMRS.

[0301] In this context, the term "some" should be understood to indicate a (specific) subset of all PUSCH transmissions in the number of PUSCH transmissions. The term is used consistently in the rearrangement described herein. For example, some of the number of PUSCH transmissions may be the (specific) third PUSCH transmission, rather than the first and second PUSCH transmissions in the total number of three PUSCH transmissions.

[0302] To this end, the base station 460 uses the determined (single) symbol number to select the corresponding table for PUSCH mapping, for example, in the case where intra-slot frequency hopping is disabled, and the determined symbol number of Table 6.4.1.1.3-3 in TS 38.211v.15.5.0 is "one", and in the case where intra-slot frequency hopping is disabled, and the "determined symbol number of Table 6.4.1.1.3-4 in TS 38.211v.15.5.0 is "two", as described above. From these tables, the user equipment 410 infers the position of the DMRS in the corresponding PUSCH.

[0303] Specifically, the base station 460 determines whether the mapping or position of the DMRS in the PUSCH transmission (the second to ninth columns in the above table) is defined (the case of "No" in step 1730) or undefined (the case of "Yes" in step 1730) for each different length (or duration) of the PUSCH transmission (the first column in the above table). This determination operation is based on the general understanding that some mapping of the dual-symbol DMRS is undefined (or unspecified, inconsistent) for PUSCH transmissions of shorter length (or duration).

[0304] Having established that the determined number of symbols for the DMRS will result in some of the number of PUSCH transmissions (see above) in an undefined (“yes” case in step 1730) mapping (or position) of the DMRS, the base station 460 selects (not in step 1730) for some of the number of PUSCH transmissions (see above). Fig.17 Explicitly shown in FIG. 1 ) at least one leading DMRS (single-symbol DMRS) having a lower number of symbols.

[0305] Having established that the number of symbols determined for the DMRS will result in all PUSCH transmissions of the number of PUSCH transmissions in the defined (“No” case in step 1730) mapping (or position) of the DMRS, the base station 460 selects (not in step 1740) for all PUSCH transmissions of the number of PUSCH transmissions Fig.17 (explicitly shown in FIG. 5 ) All PUSCH transmissions among the number of PUSCH transmissions have at least one leading DMRS (single-symbol DMRS) with a higher number of symbols.

[0306] The base station 460 then determines an index value associated with a higher number of symbols among the determined numbers of symbols, and a DMRS port number (see, for example, steps 1740- Fig.17 ), - if some PUSCH transmissions that cannot include a higher number of symbols are determined (see case "yes" in step 1730) - wherein the same DMRS port number can also be used for at least one leading DMRS with a determined lower number of symbols.

[0307] Alternatively, base station 460 determines (see, e.g., steps 1750- Fig.17 ) is an index value associated with the higher number of symbols of the same DMRS port to be used in all PUSCH transmissions in this number of PUSCH transmissions, i.e., for each one including at least one pre-DMRS.

[0308] Thereafter, the base station 460 transmits the determined time domain resources based on the number of PUSCH transmissions (see, for example, steps 1760- Fig.17 ) a single uplink grant comprising an antenna port field having an index value determined to be used for the number of PUSCH transmissions.

[0309] And, the base station 460 receives using the determined time domain resources (see, for example, steps 1770- Fig.17 ) The number of PUSCH transmissions, each of the number of PUSCH transmissions includes at least one pre-demodulation reference signal DMRS.

[0310] For the sake of brevity, the operation of the base station is kept rather short. However, this should not be construed as limiting. Rather, the experienced reader will readily appreciate that the same or similar considerations that have been explicitly described for the user equipment find equal application in the operation of the base station, i.e., when it schedules multiple PUSCH transmissions with a single uplink grant.

[0311] The third general scenario

[0312] According to the third general scenario, a user equipment and a base station are proposed to perform and schedule multiple PUSCH transmissions respectively based on a single uplink grant. The operation of the user equipment and the base station according to the third general scenario is not depicted separately, they will be very similar to those used for the first general scenario. Figure 7 and Figure 8 However, their operation may be best understood from the following description.

[0313] The user equipment 410 receives a single uplink grant for multiple PUSCH transmissions. The single uplink grant includes an antenna port field with index values ​​to be used for multiple PUSCH transmissions. For example, the receiving operation can be performed by the uplink grant receiver 520-a.

[0314] Thereafter, the user equipment 410 determines the time domain resources based on the received uplink grant. The determined time domain resources specify the number of PUSCH transmissions and the length of each of the number of PUSCH transmissions. Each of the number of PUSCH transmissions includes at least one pre-demodulation reference signal DMRS. For example, the determination operation can be performed by the time domain resource determination processing circuit 530-b.

[0315] If a different number of symbols is allowed for each of the at least one pre-DMRS, the user equipment 410 performs a specifically adapted transmission operation.

[0316] Specifically, the user equipment 410 sends the same number of PUSCH transmissions so that for all at least one leading DMRS, a lower number of symbols consistent with the received index value is used, and if the received index value is associated with a higher number of symbols to be used for at least one leading DMRS, it does not send any PUSCH transmission of the number of PUSCH transmissions. For example, the sending operation can be performed by the PUSCH transmission transmitter 520-a.

[0317] Separately, the base station 460 determines the time domain resources. The determined time domain resources specify the number of multiple PUSCH transmissions and the length of each of the number of PUSCH transmissions. For example, the determination operation may be performed by the time domain resource determination processing circuit 680-a.

[0318] If a different number of symbols is allowed for each of the at least one pre-DMRS, the base station 460 performs a specifically adapted determination operation of the index value.

[0319] Specifically, the base station determines the index value associated with the lower number of symbols so that the same number of PUSCH transmissions including at least one pre-DMRS using the lower number of symbols are received. For example, the determination operation may be performed by the index value determination processing circuit 680-d.

[0320] Then, the base station 460 sends a single uplink grant based on the determined time domain resources for the number of PUSCH transmissions. The single uplink grant includes an antenna port field with an index value to be used for the number of PUSCH transmissions. For example, the sending operation can be performed by an uplink grant transmitter 670-a.

[0321] And, the base station 460 uses the determined time domain resources to receive the number of PUSCH transmissions, each of which includes at least one pre-demodulation reference signal DMRS. For example, the receiving operation may be performed by the PUSCH transmission receiver 670-b.

[0322] The present disclosure may be implemented by software, hardware, or software in cooperation with hardware.

[0323] Each functional block used in the description of each embodiment described above may be partially or wholly realized by an LSI such as an integrated circuit, and each process described in each embodiment may be partially or wholly controlled by the same LSI or a combination of LSIs.

[0324] LSI can be formed as a chip separately, or can form a chip to include some or all functional blocks. LSI can include data input and output coupled to it. According to the difference in integration, LSI can be referred to as IC, system LSI, super LSI or ultra LSI.

[0325] However, the technology for realizing the integrated circuit is not limited to LSI, and may be realized by using a dedicated circuit, a general-purpose processor, or a dedicated processor.

[0326] In addition, an FPGA (Field Programmable Gate Array) which can be programmed after manufacturing the LSI or a reconfigurable processor in which the connection and setting of a circuit cell provided inside the LSI can be reconfigured may be used.

[0327] The present disclosure may be implemented as digital processing or analog processing. If future integrated circuit technology replaces LSI due to the advancement of semiconductor technology or other derivative technologies, future integrated circuit technology may be used to integrate functional blocks. Biotechnology may also be applied.

[0328] The present disclosure may be implemented by any kind of device, apparatus or system having a communication function, which is referred to as a communication device.

[0329] Some non-limiting examples of such communication devices include phones (e.g., cellular (mobile) phones, smart phones), tablets, personal computers (PCs) (e.g., laptops, desktops, netbooks), cameras (e.g., digital cameras / camcorders), digital players (digital audio / video players), wearable devices (e.g., wearable cameras, smart watches, tracking devices), game consoles, digital book readers, telehealth / telemedicine (remote health and medicine) devices, and vehicles that provide communication capabilities (e.g., cars, airplanes, ships), and various combinations thereof.

[0330] The communication devices are not limited to portable or mobile, and may also include any type of device, equipment, or system that is non-portable or fixed, such as smart home devices (e.g., home appliances, lighting devices, smart meters, control panels), vending machines, and any other "things" in an "Internet of Things (IoT)" network.

[0331] Communications may include exchanging data through, for example, cellular systems, wireless LAN systems, satellite systems, etc., and various combinations thereof.

[0332] The communication device may include a device such as a controller or a sensor that is coupled to a communication device that performs the communication functions described in the present disclosure. For example, the communication device may include a controller or a sensor that generates a control signal or a data signal that is used by the communication device that performs the communication functions of the communication device.

[0333] The communication device may also include infrastructure such as base stations, access points, and any other device, equipment, or system that communicates with or controls devices such as the non-limiting examples above.

[0334] According to a first aspect, a user equipment UE is provided, comprising: a receiver, receiving a single uplink grant for multiple PUSCH transmissions, the single uplink grant comprising an antenna port field having an index value to be used for the multiple PUSCH transmissions; a processor, determining time domain resources based on the received uplink grant, the determined time domain resources specifying the number of PUSCH transmissions and the length of each of the number of PUSCH transmissions; a transmitter, using the determined time domain resources to send a number of PUSCH transmissions, each of the number of PUSCH transmissions comprising at least one pre-demodulation reference signal DMRS, wherein the processor determines the number of symbols for each of the at least one pre-DMRS to be used for the number of PUSCH transmissions based on the received index value, and, if at least two of the number of PUSCH transmissions have different lengths and if different numbers of symbols are allowed for each of the at least one pre-DMRS, the transmitter sends the same or less number of PUSCH transmissions, so that a different determined number of symbols is used for none of the at least one pre-DMRS included.

[0335] According to a second aspect provided in addition to the first aspect, the processor is configured to use a maximum symbol number of "two", which allows, for each of at least one pre-DMRS, to use: a single-symbol DMRS with a lower symbol number of "one", or a double-symbol DMRS with a higher symbol number of "two".

[0336] According to a third aspect provided in addition to the first or second aspect, the processor determines a number of symbols to be used for each of the at least one pre-DMRS based on different lengths of all PUSCH transmissions among the number of PUSCH transmissions.

[0337] According to a fourth aspect provided in addition to any of the first to third aspects, if at least two of the number of PUSCH transmissions have different lengths, and if one of at least two of the number of PUSCH transmissions cannot include a higher number of symbols for each of at least one leading DMRS, the processor selects at least one leading DMRS with a lower number of symbols for all the number of PUSCH transmissions when determining the number of symbols to be used; and the transmitter sends the same number of PUSCH transmissions so that a lower number of symbols is used for all at least one leading DMRS.

[0338] According to a fifth aspect provided in addition to the fourth aspect, the processor selects at least one leading DMRS with a lower number of symbols for all PUSCH transmissions in the number of PUSCH transmissions if at least one of the number of PUSCH transmissions cannot include a higher number of symbols for the at least one leading DMRS included.

[0339] According to the sixth aspect provided in addition to the fourth or fifth aspect, when selecting at least one leading DMRS, the processor selects at least one leading DMRS for all PUSCH transmissions in the number of PUSCH transmissions, so that: a lower number of symbols is used, and the same DMRS port number is used, wherein the DMRS port number to be used for all leading DMRSs in at least one leading DMRS is the same as the DMRS port number associated with the received index value.

[0340] According to the seventh aspect provided in addition to any of the fourth to sixth aspects, the processor, when selecting at least one leading DMRS, skips at least one PUSCH transmission among the number of PUSCH transmissions, the at least one PUSCH transmission: cannot include a higher number of symbols for each of the at least one leading DMRS, and cannot use a DMRS port number that is the same as the DMRS port number associated with the received index value; and the transmitter sends a smaller number of PUSCH transmissions so that for all of the included at least one leading DMRS, a higher number of symbols and the same DMRS port number are used.

[0341] According to an eighth aspect, there is provided a user equipment UE comprising: a receiver receiving a single uplink grant for multiple PUSCH transmissions, the single uplink grant comprising an antenna port field having an index value to be used for the multiple PUSCH transmissions;

[0342] A processor determines time domain resources based on a received uplink grant, the determined time domain resources specifying the number of PUSCH transmissions and the length of each of the number of PUSCH transmissions; a transmitter uses the determined time domain resources to send the number of PUSCH transmissions, each of the number of PUSCH transmissions including at least one pre-demodulation reference signal DMRS, wherein the processor determines a DMRS port number to be used for each of the at least one pre-DMRS for the number of PUSCH transmissions based on a received index value, and if at least two of the number of PUSCH transmissions have different lengths and if a different number of symbols is allowed for each of the at least one pre-DMRS, the transmitter sends the same or less number of PUSCH transmissions so that none of the included at least one pre-DMRS uses a different determined DMRS port number.

[0343] According to a ninth aspect provided in addition to the eighth aspect, the processor is configured to use a maximum number of symbols of "two" for at least one leading DMRS, such that: for a type 1 configuration, a DMRS port having a number between "zero" and "seven" is used, or for a type 2 configuration, a DMRS port having a number between "zero" and "eleven" is used.

[0344] According to a tenth aspect provided in addition to the eighth or ninth aspect, the processor determines a DMRS port number to be used for each of at least one pre-DMRS based on different lengths of all PUSCH transmissions among the number of PUSCH transmissions.

[0345] According to an eleventh aspect provided in addition to any of the eighth to tenth aspects, the processor, based on the received index value, further determines the number of symbols for each of at least one leading DMRS to be used for the number of PUSCH transmissions, and if at least two of the number of PUSCH transmissions have different lengths and if different numbers of symbols are allowed for each of the at least one leading DMRS, the processor, when determining the DMRS port number, selects the same DMRS port number that can be used for all leading DMRSs in the at least one leading DMRS for all PUSCH transmissions in the number of PUSCH transmissions, and the transmitter sends the same number of PUSCH transmissions so that for all of the at least one leading DMRS included, the same DMRS port number is used with different numbers of symbols.

[0346] According to the twelfth aspect provided in addition to the eleventh aspect, when determining the DMRS port number, the processor selects the DMRS port number for all PUSCH transmissions in the number of PUSCH transmissions, so that: a lower or higher number of symbols is used for at least one leading DMRS, and the same DMRS port number is used for the lower and higher number of symbols, wherein the same DMRS port number to be used for all at least one leading DMRS is the same as the DMRS port number associated with the received index value.

[0347] According to the thirteenth aspect provided in addition to the twelfth aspect, the processor skips at least one PUSCH transmission among the number of PUSCH transmissions when selecting a DMRS port number, and the at least one PUSCH transmission: cannot include a higher number of symbols for each of at least one leading DMRS, and cannot use a DMRS port number that is the same as the DMRS port number associated with the received index value; and the transmitter sends a smaller number of PUSCH transmissions so that a higher number of symbols and the same DMRS port number are used for all leading DMRSs in at least one leading DMRS.

[0348] According to the fourteenth aspect, a user equipment UE is provided, comprising: a receiver, receiving a single uplink grant for multiple PUSCH transmissions, the single uplink grant comprising an antenna port field having an index value to be used for the multiple PUSCH transmissions; a processor, determining time domain resources based on the received uplink grant, the determined time domain resources specifying the number of PUSCH transmissions and the length of each of the number of PUSCH transmissions; a transmitter, using the determined time domain resources to send a number of PUSCH transmissions, each of the number of PUSCH transmissions comprising at least one pre-demodulation reference signal DMRS, wherein, if a different number of symbols is allowed for each of at least one pre-DMRS, the transmitter sends the same number of PUSCH transmissions, so that for all pre-DMRSs in at least one pre-DMRS, a lower number of symbols is used, the lower number of symbols being consistent with the received index value, and if the received index value is associated with a higher number of symbols to be used for at least one pre-DMRS, the transmitter does not send any PUSCH transmission of the number of PUSCH transmissions.

[0349] According to the fifteenth aspect provided in addition to the thirteenth aspect, the processor is configured to use a maximum number of "two" symbols, which allows, for each of at least one pre-DMRS, to use: a single-symbol DMRS with a lower number of symbols "one", or a double-symbol DMRS with a higher number of symbols "two".

[0350] According to a sixteenth aspect, a base station BS is provided, comprising: a processor, which determines time domain resources, the determined time domain resources specifying the number of multiple PUSCH transmissions and the length of each of the number of PUSCH transmissions; a transmitter, which sends a single uplink grant based on the determined time domain resources for the number of PUSCH transmissions, the single uplink grant including an antenna port field having an index value to be used for the number of PUSCH transmissions; a receiver, which receives the number of PUSCH transmissions using the determined time domain resources, each of the number of PUSCH transmissions including at least one pre-demodulation reference signal DMRS, wherein the processor determines the number of PUSCH transmissions to be used for the PUSCH transmissions included in the number of PUSCH transmissions. The number of symbols for each of at least one leading DMRS in the PUSCH transmission, the determined number of symbols being one of a lower number of symbols and a higher number of symbols, and, if at least two of the number of PUSCH transmissions have different lengths, and if different numbers of symbols are allowed for each of the at least one leading DMRS, the processor determines an index value associated with a lower number of symbols in the determined number of symbols to be used for each of the included at least one leading DMRS, and the receiver receives the same or a lesser number of PUSCH transmissions such that a different determined number of symbols is used for none of the included at least one leading DMRS.

[0351] According to the seventeenth aspect, a base station BS is provided comprising: a processor, which determines time domain resources, the determined time domain resources specifying the number of multiple PUSCH transmissions and the length of each of the number of PUSCH transmissions; a transmitter, which sends a single uplink grant based on the determined time domain resources for the number of PUSCH transmissions, the single uplink grant comprising an antenna port field having an index value to be used for the number of PUSCH transmissions; a receiver, which receives the number of PUSCH transmissions using the determined time domain resources, each of the number of PUSCH transmissions comprising at least one pre-demodulation reference signal DMRS, wherein the processor determines the number of PUSCH transmissions to be used for at least one of the PUSCH transmissions included in the number of PUSCH transmissions. The processor determines an index value and a DMRS port number associated with the higher number of symbols in the determined number of symbols, wherein the same DMRS port number may also be used for at least one of the leading DMRSs having the determined lower number of symbols, and the receiver receives the same or less number of PUSCH transmissions such that no different determined DMRS port number is used for any of the included at least one leading DMRSs.

[0352] According to the eighteenth aspect, a base station BS is provided, comprising: a processor, which determines time domain resources, the determined time domain resources specifying the number of multiple PUSCH transmissions and the length of each of the PUSCH transmissions; a transmitter, which sends a single uplink grant based on the determined time domain resources for the number of PUSCH transmissions, the single uplink grant comprising an antenna port field having an index value to be used for the multiple PUSCH transmissions; a receiver, which receives the number of PUSCH transmissions using the determined time domain resources, each of the number of PUSCH transmissions comprising at least one pre-demodulation reference signal DMRS, wherein, if a different number of symbols is allowed for each of the at least one pre-DMRS, the processor determines an index value associated with a lower number of symbols so that the same number of PUSCH transmissions including at least one pre-DMRS using a smaller number of symbols is received.

Claims

1. A user equipment (UE), comprising: a receiver that receives a single uplink grant for a plurality of PUSCH transmissions, the single uplink grant including an antenna port field having index values ​​to be used for the plurality of PUSCH transmissions; a processor, configured to determine time domain resources based on the received uplink grant, wherein the determined time domain resources specify a first number of PUSCH transmissions and a length of the PUSCH transmissions; a transmitter, transmitting the first number of PUSCH transmissions using the determined time domain resources, each of the PUSCH transmissions including at least one pre-demodulation reference signal (DMRS); in The processor determines, based on the received index value, a number of symbols for each of the at least one pre-DMRS to be used for the first number of PUSCH transmissions, And, if at least two of the first number of PUSCH transmissions have different lengths, the transmitter transmits a second number of PUSCH transmissions equal to or different from the first number, the second number of PUSCH transmissions not including a different number of symbols for the at least one pre-DMRS.

2. The UE according to claim 1 , wherein: The processor is configured to use a maximum number of symbols of two, which allows, for each of the at least one pre-DMRS, using: A single symbol DMRS included within "one" symbol corresponding to a low number of leading DMRS symbols, or A dual-symbol DMRS included in "two" symbols corresponding to a high number of leading DMRS symbols.

3. The UE according to claim 1 or 2, wherein: The processor determines a number of symbols to use for each of the at least one pre-DMRS based on different lengths of all PUSCH transmissions in the second number of PUSCH transmissions.

4. The UE according to claim 1, wherein: if at least two of the first number of PUSCH transmissions have different lengths and if one of the at least two of the first number of PUSCH transmissions cannot include a high number of leading DMRS symbols corresponding to “two” symbols, the processor, when determining the number of symbols to use, selects at least one leading DMRS corresponding to a low number of leading DMRS symbols corresponding to “one” symbol for all PUSCH transmissions of the second number of PUSCH transmissions; and The transmitter transmits the second number of PUSCH transmissions equal to the first number such that the low number of leading DMRS symbols is used for all leading DMRSs in the at least one leading DMRS; or If at least one of the second number of PUSCH transmissions cannot include a high number of leading DMRS symbols corresponding to “two” symbols, the processor selects at least one leading DMRS corresponding to a low number of leading DMRS symbols corresponding to “one” symbol for all PUSCH transmissions of the second number of PUSCH transmissions.

5. The UE according to claim 4, wherein: When selecting the at least one pre-DMRS, the processor selects the at least one pre-DMRS for all PUSCH transmissions in the second number of PUSCH transmissions such that: The low number of leading DMRS symbols is used, and The same DMRS port number is used, wherein the DMRS port number to be used for all pre-DMRSs in the at least one pre-DMRS is the same as the DMRS port number associated with the received index value; or The processor skips, when selecting the at least one pre-DMRS, at least one PUSCH transmission among the first number of PUSCH transmissions, the at least one PUSCH transmission: The high number of leading DMRS symbols cannot be included, and • cannot use the same DMRS port number as the one associated with the received index value; and The transmitter transmits the second number of PUSCH transmissions different from the first number such that the high number of pre-DMRS symbols and the same DMRS port number are used for all included at least one pre-DMRS.

6. A base station BS, comprising: A processor is configured to determine a time domain resource, wherein the determined time domain resource specifies a first number of multiple PUSCH transmissions and a length of the PUSCH transmissions; a transmitter that transmits a single uplink grant based on the determined time domain resources for the first number of PUSCH transmissions, the single uplink grant including an antenna port field having an index value to be used for the first number of PUSCH transmissions; in The processor determines a number of symbols to be used for each of the at least one pre-DMRS included in the first number of PUSCH transmissions, the determined number of symbols being one of a low pre-DMRS symbol number corresponding to “one” symbol and a high pre-DMRS symbol number corresponding to “two” symbols, and, if at least two of the first number of PUSCH transmissions have different lengths, and if one of the at least two of the first number of PUSCH transmissions cannot include a high number of leading DMRS symbols, determining an index value to be used for each of the included at least one leading DMRS associated with the low number of leading DMRS symbols, The receiver receives a second number of PUSCH transmissions that is equal to or different from the first number, the second number of PUSCH transmissions not including a different number of symbols for the at least one pre-DMRS.

7. A method performed by a user equipment (UE), comprising: receiving a single uplink grant for a plurality of PUSCH transmissions, the single uplink grant comprising an antenna port field having index values ​​to be used for the plurality of PUSCH transmissions; determining time domain resources based on the received uplink grant, the determined time domain resources specifying a first number of PUSCH transmissions and a length of the PUSCH transmissions; Using the determined time domain resources to transmit the first number of PUSCH transmissions, each of the PUSCH transmissions including at least one pre-demodulation reference signal (DMRS); as well as determining a number of symbols for each of the at least one pre-DMRS to be used for the first number of PUSCH transmissions based on the received index value, And, if at least two of the first number of PUSCH transmissions have different lengths, sending a second number of PUSCH transmissions equal to or different from the first number, the second number of PUSCH transmissions not including a different number of symbols for the at least one pre-DMRS.

8. A method performed by a base station BS, comprising: Determining time domain resources, where the determined time domain resources specify a first number of multiple PUSCH transmissions and a length of the PUSCH transmissions; sending a single uplink grant based on the determined time domain resources for the first number of PUSCH transmissions, the single uplink grant including an antenna port field having an index value to be used for the first number of PUSCH transmissions; determining a number of symbols to be used for each of the at least one pre-DMRS included in the first number of PUSCH transmissions, the determined number of symbols being one of a low pre-DMRS symbol number corresponding to “one” symbol and a high pre-DMRS symbol number corresponding to “two” symbols; if at least two of the first number of PUSCH transmissions have different lengths, and if one of the at least two of the first number of PUSCH transmissions cannot include a high number of leading DMRS symbols, determining an index value to be used for each of the included at least one leading DMRS associated with the low number of leading DMRS symbols; as well as A second number of PUSCH transmissions is received that is equal to or different than the first number, the second number of PUSCH transmissions not including a different number of symbols for the at least one pre-DMRS.

9. An integrated circuit for controlling a process of a user equipment (UE), comprising: receiving a single uplink grant for a plurality of PUSCH transmissions, the single uplink grant comprising an antenna port field having index values ​​to be used for the plurality of PUSCH transmissions; determining time domain resources based on the received uplink grant, the determined time domain resources specifying a first number of PUSCH transmissions and a length of the PUSCH transmissions; Using the determined time domain resources to transmit the first number of PUSCH transmissions, each of the PUSCH transmissions including at least one pre-demodulation reference signal (DMRS); as well as determining a number of symbols for each of the at least one pre-DMRS to be used for the first number of PUSCH transmissions based on the received index value, And, if at least two of the first number of PUSCH transmissions have different lengths, sending a second number of PUSCH transmissions equal to or different from the first number, the second number of PUSCH transmissions not including a different number of symbols for the at least one pre-DMRS.

10. An integrated circuit for controlling a process of a base station BS, comprising: Determining time domain resources, where the determined time domain resources specify a first number of multiple PUSCH transmissions and a length of the PUSCH transmissions; sending a single uplink grant based on the determined time domain resources for the first number of PUSCH transmissions, the single uplink grant including an antenna port field having an index value to be used for the first number of PUSCH transmissions; determining a number of symbols to be used for each of the at least one pre-DMRS included in the first number of PUSCH transmissions, the determined number of symbols being one of a low pre-DMRS symbol number corresponding to “one” symbol and a high pre-DMRS symbol number corresponding to “two” symbols; If at least two of the first number of PUSCH transmissions have different lengths, and If one of at least two of the first number of PUSCH transmissions cannot include a high number of leading DMRS symbols, determining an index value to be used for each of the included at least one leading DMRS associated with the low number of leading DMRS symbols; as well as A second number of PUSCH transmissions is received that is equal to or different than the first number, the second number of PUSCH transmissions not including a different number of symbols for the at least one pre-DMRS.