Integrated circuit for controlling base station for executing transmission / reception processing

Abstract

To provide an integrated circuit for controlling a base station (BS) in a communication system.SOLUTION: An integrated circuit includes: processing circuits 430, 480 that are processors for determining a time-domain resource, where the determined time-domain resource defines the number of a plurality of physical uplink shared channel (PUSCH) transmissions and respective lengths of the plurality of PUSCH transmissions; transmitter circuits 420, 470 that are transmitters for transmitting a single uplink grant on the basis of the time-domain resource determined for the plurality of PUSCH transmissions, where the single uplink grant includes an antenna port field comprising an index value to be used for the plurality of PUSCH transmissions; and receiver circuits 420, 470 that receives the plurality of PUSCH transmissions using the determined time-domain resource, where each of the plurality of PUSCH transmissions includes at least one front-loaded demodulation reference signal (DMRS).SELECTED DRAWING: Figure 4

Description

[Technical Field]

[0001] TECHNICAL FIELD This disclosure relates to the transmission and reception of signals in communication systems. In particular, this disclosure relates to integrated circuits for controlling base stations for such transmission and reception. [Background technology]

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

[0003] NR is the successor to the technologies represented by Long Term Evolution (LTE) and LTE Advanced (LTE-A). NR is designed to facilitate the provision of a single technical framework that addresses multiple defined usage, requirements, and deployment scenarios, including, for example, enhanced Mobile Broadband (eMBB), Ultra-Reliable Low-Latency Communications (URLLC), and massive Machine Type Communication (mMTC).

[0004] For example, eMBB deployment scenarios may include indoor hotspots, dense urban, rural, urban macro and high speed; URLLC deployment scenarios may include industrial control systems, mobile healthcare (remote monitoring, diagnosis and treatment), real-time control of vehicles, wide area monitoring and control systems for smart grids; and mMTC deployment scenarios may include scenarios with a large number of devices with non-time critical data transmission such as smart wearables and sensor networks.

[0005] eMBB and URLLC services are similar in that they both require extremely high bandwidth, but URLLC services differ in that they 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.

[0006] For systems such as LTE and NR, further improvements and options may facilitate efficient operation of the communication system as well as particular devices associated with the system. Summary of the Invention

[0007] One non-limiting and exemplary embodiment improves support for allocation of Physical Uplink Shared Channel (PUSCH) transmissions with flexible timing and facilitates allowing accurate channel estimation utilizing the demodulation reference signals (DMRS) carried therein.

[0008] In an embodiment, the disclosed technology features 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 index values ​​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 define the number of PUSCH transmissions and the length of each PUSCH transmission.

[0009] The transmitter transmits a plurality of PUSCH transmissions utilizing the determined time domain resources, each PUSCH transmission including at least one pre-placed demodulation reference signal (DMRS).

[0010] In particular, the processor determines the number of symbols to be used for each DMRS placed before at least one of the multiple PUSCH transmissions based on the received index value, and if at least two of the multiple PUSCH transmissions have different lengths and a different number of symbols is allowed for each of the at least one preceding DMRS, the transmitter transmits the same or fewer PUSCH transmissions so that the determined different number of symbols is not used for any of the at least one preceding DMRS included.

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

[0012] Further benefits and advantages of the disclosed embodiments will become apparent from the specification and drawings. Benefits and / or advantages may be obtained individually from various embodiments and features of the specification and drawings, which need not all be provided to obtain one or more of such benefits and / or advantages. [Brief explanation of the drawings]

[0013] In the following, exemplary embodiments are explained in more detail with reference to the accompanying drawings. [Figure 1] 1 shows a schematic diagram of an example architecture for a 3GPP NR system. [Figure 2] 1 shows a block diagram of an example user and control plane architecture for an LTE eNB, an NR gNB, and a UE. [Figure 3] FIG. 1 is a schematic diagram showing a usage scenario of mMTC (massive Machine Type Communications) and URLLC (Ultra Reliable and Low Latency Communications). [Figure 4] 1 illustrates a communication system in NR including a user equipment (UE) and a base station (BS) according to an exemplary scenario. [Figure 5] 1 shows a block diagram of an exemplary implementation of a user equipment (UE) and a base station (BS). [Figure 6] 1 shows a block diagram of an exemplary implementation of a user equipment (UE) and a base station (BS). [Figure 7] 1 shows a sequence diagram of a user equipment (UE) and a base station (BS) performing multiple PUSCH transmissions according to a first general mechanism. [Figure 8] 1 shows a sequence diagram of a user equipment (UE) and a base station (BS) performing multiple PUSCH transmissions according to a first general mechanism. [Figure 9] 1 shows a sequence diagram of a user equipment (UE) and a base station performing multiple PUSCH transmissions according to a first exemplary implementation of a first general mechanism. [Figure 10] 1 shows a sequence diagram of a user equipment (UE) and a base station performing multiple PUSCH transmissions according to a first exemplary implementation of a first general mechanism. [Figure 11] 1 shows a schematic diagram of resource allocation in the time domain by utilizing a first general mechanism; [Figure 12] 1 shows a schematic diagram of resource allocation in the time domain by utilizing a first general mechanism; [Figure 13] 1 shows a schematic diagram of resource allocation in the time domain by utilizing a first general mechanism; [Figure 14] 10 shows a sequence diagram of a user equipment (UE) and a base station (BS) performing multiple PUSCH transmissions according to a second general mechanism. [Figure 15] 1 shows a sequence diagram of a user equipment (UE) and a base station (BS) performing multiple PUSCH transmissions according to a first general mechanism. [Figure 16] 10 shows a sequence diagram of a user equipment (UE) and a base station performing multiple PUSCH transmissions according to a second exemplary implementation of the second general mechanism. [Figure 17] 10 shows a sequence diagram of a user equipment (UE) and a base station performing multiple PUSCH transmissions according to a second exemplary implementation of the second general mechanism. [Figure 18] 1 shows a schematic diagram of resource allocation in the time domain by utilizing a first general mechanism; [Figure 19] 1 shows a schematic diagram of resource allocation in the time domain by utilizing a first general mechanism; [Figure 20] 1 shows a schematic diagram of resource allocation in the time domain by utilizing a first general mechanism; DETAILED DESCRIPTION OF THE INVENTION

[0014] As presented in the background section, 3GPP is working on the next release of fifth-generation cellular technology, simply referred to as 5G, which includes the development of New Radio (NR) access technology operating in frequencies up to 100 GHz range. 3GPP must identify and develop the technology components required to successfully standardize an NR system that meets both immediate market needs and longer-term requirements in a timely manner. To accomplish this, the evolution of the radio network architecture along with the air interface is considered in the study item "New Radio Access Technology," which is incorporated herein by reference in its entirety. Results and consensus are collected in Technical Report TR 38.804 v14.0.0.

[0015] In particular, an overall system architecture has been agreed upon. The Next Generation Radio Access Network (NG-RAN) consists of gNBs, which provide the 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 termination for UEs. The NG-RAN architecture, based on Section 4 of TS 38.300 v15.0.0, which is incorporated herein by reference, is shown in Figure 1. The gNBs are interconnected with each other by an Xn interface. The gNBs are also connected to the Next Generation Core (NGC) by an NG (Next Generation) interface, more specifically to the Access and Mobility Management Function (AMF) (e.g., a specific core entity that runs the AMF) by an NG-C interface, and to the User Plane Function (UPF) (e.g., a specific core entity that runs the UPF) by an NG-U interface.

[0016] For example, as reflected in 3GPP TR 38.801 v14.0.0, "Study on new radio access technology: Radio access architecture and interfaces," various different deployment scenarios are discussed to be supported. For example, a decentralized deployment scenario (Section 5.2 of TR 38.801, with the centralized deployment described in Section 5.4, which is incorporated herein by reference) is presented therein, in which base stations supporting 5G NR can be deployed. Figure 2 illustrates an exemplary decentralized deployment scenario and is based on Figure 5.2-1 of TR 38.801, further showing an LTE eNB with user equipment (UE) connected to both the gNB and the LTE eNB. As described above, the new eNB for NR 5G may illustratively be referred to as a gNB.

[0017] As mentioned above, the 3GPP NR (3rd Generation Partnership Project New Radio) is considering three use cases that are expected to support a wide range of services and applications through 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). Phase 1 specifications for enhanced Mobile Broadband (eMBB) were finalized by 3GPP in December 2017. In addition to further extending eMBB support, current and future research will involve standardization for Ultra-Reliable and Low-Latency Communications (URLLC) and massive Machine-Type Communications (mMTC). Figure 3 (from Recommendation ITU-R M.2083) shows some specific examples of expected use scenarios for IMT beyond 2020.

[0018] URLLC use cases have stringent requirements for capabilities such as throughput, latency, and availability, and have been envisioned as one of the enablers for future vertical applications, such as wireless control of industrial manufacturing or production processes, remote surgery, logistics automation in smart grids, and transportation safety. The current Work Item Description (WID) RP-172115 has agreed to support ultra-reliability for URLLC by identifying technologies that meet the requirements set by TR 38.913. For NR URLLC in Release 15, key requirements include a target user plane delay of 0.5 ms for the uplink (UL) and 0.5 ms for the downlink (DL). A typical URLLC requirement for a single transmission of a packet is a block error rate (BLER) of 1E-5 for a 32-byte packet size with a user plane delay of 1 ms.

[0019] From the perspective of RAN1, reliability can be improved in a number of possible ways. The scope for improving reliability in Rel. 15 is captured in RP-172817, which includes provisions such as a separate CQI table for URLLC, a more compact DCI format, and PDCCH repetition. However, the scope may widen to achieve ultra-reliability as NR becomes more stable and developed (for key requirements of NR URLLC, see 3GPP TR 38.913 v15.0.0, “Study on Scenarios and Requirements for Next Generation Access Technologies,” incorporated herein by reference). Thus, NR URLLC in Rel. 15 should be capable of transmitting 32-byte data packets within a 1-ms user-plane delay with a success rate corresponding to a BLER of 1E-5. Specific use cases for NR URLLC 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).

[0020] Additionally, technology enhancements targeted by NR URLLC in Release 15 aim to improve latency and reliability. Technology enhancements for latency improvement include configurable numerology, non-slot-based scheduling with flexible maps, grant-free (configured grant) uplink, slot-level repetition of data channels, and downlink preemption. Preemption means that a transmission that has already been allocated resources is stopped and the allocated resources are used for another transmission that has subsequently requested but has a lower latency / higher priority request. Thus, an already granted transmission is preempted by a subsequent transmission. Preemption is applicable independently of the specific service type. For example, a transmission for service type A (URLLC) can be preempted by a transmission for service type B (e.g., eMBB). Technical enhancements for improved reliability include dedicated CQI / MCS tables for a target BLER of 1E-5 (for technical enhancements, see 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," each version V15.4.0, all of which are incorporated herein by reference).

[0021] The mMTC use case is typically characterized by a very large number of connected devices transmitting data that is not sensitive to a relatively small amount of latency. The devices are required to be low cost and have very long battery life. From an NR perspective, utilizing very narrow bandwidth portions is one possible solution to have power savings from the UE perspective and enable long battery life.

[0022] As mentioned above, the reliability range in NR is expected to be wider. One important requirement for all cases, especially for URLLC and mMTC, is high or ultra-reliability. Several mechanisms can be considered to improve reliability from a radio perspective and a network perspective. In general, there are few important potential areas that can help improve reliability. Among these areas are compact control channel information, repetition of data / control channels, and diversity with respect to frequency, time, and / or spatial domains. These areas are generally applicable to reliability, regardless of the specific communication scenario.

[0023] For NR URLLC Rel. 16, additional use cases with more stringent requirements have been identified, 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, incorporated herein by reference). The more stringent requirements include higher reliability (up to a level of 10-6), higher availability, packet sizes up to 256 bytes, time synchronization down to the order of a few microseconds, which can be one or a few microseconds depending on the frequency range, and low latency on the order of 0.5-1 ms, with a target user plane latency of 0.5 ms, depending on the use case (see "Service requirements for next generation new services and markets," V16.4.0 and RP-181477, incorporated herein by reference).

[0024] Furthermore, Rel. 16 NR-URLLC specified several technology enhancements from the perspective of RAN1. Among these are PDCCH (Physical Downlink Control Channel) enhancements related to compact DCI, PDCCH repetition, and increased PDCCH monitoring. Furthermore, UCI (Uplink Control Information) enhancements related to enhanced HARQ (Hybrid Automatic Repeat Request) and CSI feedback enhancements. Also specified were PUSCH enhancements related to minislot-level hopping and retransmission / repetition enhancements. The term "minislot" refers to a TTI (Transmission Time Interval) containing fewer symbols than a slot (a slot consisting of 14 symbols).

[0025] Generally, the TTI determines the timing granularity for scheduling assignments. One TTI is the time interval over which a given signal is mapped to the physical layer. Traditionally, the TTI length is variable, ranging from 14 symbols (slot-based scheduling) to 2 symbols (non-slot-based scheduling). Downlink and uplink transmissions are specified to be organized into frames (10 ms duration) that are further divided into slots, the number of slots being dictated by the numerology / subcarrier spacing, with specified values ​​ranging from 10 slots for a 15 kHz subcarrier spacing to 320 slots for a 240 kHz subcarrier spacing. The number of OFDM symbols per slot is 14 for the normal cyclic prefix and 12 for the extended cyclic prefix (see sections 4.1 (Overall Frame Structure), 4.2 (Numerology), 4.3.1 (Frames and Subframes), and 4.3.2 (Slots) of 3GPP TS 38.211 v.15.4.0, which is incorporated herein by reference).

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

[0027] PUSCH repeat One area for potential enhancement relates to minislot repetition of PUSCH within a slot. In the following, motivation is provided for supporting PUSCH repetition within a slot, which may enable potential enhancements to the repetition mechanism to further improve reliability and / or delay to meet new requirements for NR URLLC. However, this motivation should not be understood as imposing any constraints on the present disclosure.

[0028] To achieve the delay requirement for URLLC PUSCH transmission, one-shot transmission (i.e., single TTI allocation) is ideal if the reliability requirement is met. However, the target BLER of 1E-6 cannot always be achieved by one-shot transmission. Therefore, a retransmission or repeat mechanism is required.

[0029] In NR Rel. 15, when one-shot transmission is not sufficient, both retransmission and repetition are supported to achieve the target BLER. HARQ-based retransmissions are well known to improve overall reliability by utilizing feedback information and improving subsequent retransmissions according to channel conditions. However, they incur additional delay due to the feedback processing timeline. Therefore, repetition is useful for delay-tolerant services to perform subsequent transmissions of the same transport block without waiting for feedback.

[0030] PUSCH repetition can be defined as "transmitting the same transport block two or more times without waiting for feedback of the previous transmission of the same transport block." The advantage of PUSCH retransmission is improved overall reliability and reduced latency compared to HARQ, since no feedback is required. However, link adaptation is generally not possible and resource utilization may be inefficient.

[0031] NR Rel.15 introduces limited support for repetition. Only semi-static configuration of repetition is allowed. Also, repetition is only allowed between slots (slot-level PUSCH repetition). Repetition is only allowed in slots following the slot of the previous transmission. Depending on the numerology and service type (e.g., URLLC, eMBB), the delay between repetitions may be too long for inter-slot repetition.

[0032] Such limited support for repetitions is mainly useful for PUSCH mapping type A, which only allows PUSCH transmissions to start at the beginning of a slot. With repetitions, this results in the first PUSCH transmission, with each repetition starting at the beginning of multiple consecutive slots.

[0033] The limited support for repetition in PUSCH mapping type B is not very useful. PUSCH mapping type B allows a PUSCH transmission to start at any symbol within a slot. With repetition, this results in the first PUSCH transmission starting at the same symbol in multiple consecutive slots within a slot, with each repetition starting at the same symbol in multiple consecutive slots.

[0034] In either case, such limited support may not be able to achieve the more stringent delay requirements in NR Rel. 15, i.e., up to 0.5 ms delay, which would require minislot repetition. Furthermore, limited support of repetition also does not take advantage of the benefits that come from a minislot, i.e., a transmission time interval (TTI) that contains fewer symbols than a slot (a slot containing 14 symbols).

[0035] PUSCH allocation Another area for potential enhancement relates more generally to allocation of PUSCH within a slot or across multiple slots. In the following, motivation is provided for supporting different PUSCH transmission allocations that may enable potential enhancements to uplink utilization to further improve latency while meeting reliability requirements to further meet the new demands of NR URLLC.

[0036] To achieve the delay requirement for URLLC PUSCH transmission, once again one-shot transmission (i.e., single (TTI) allocation) is ideal if reliability is met. However, the target user plane delay of 0.5 ms cannot always be achieved for simultaneous PUSCH transmission. Therefore, enhancements to the uplink allocation are needed.

[0037] In NR Rel.15, uplink scheduling is constrained to a single uplink grant per TT1. In the case of a single PUSCH transmission, this scheduling constraint is not a limitation, and the target user plane delay may be achieved via one-shot transmission. However, for simultaneous PUSCH transmissions, the scheduling constraint results in one-shot transmissions that may not be sufficient to meet the target user plane delay.

[0038] In particular, simultaneous PUSCH transmissions require separate uplink grants, which must be signaled in consecutive TTIs and incur significant scheduling overhead due to scheduling constraints. Therefore, the scheduling constraints introduce unnecessary delays in the case of simultaneous PUSCH transmissions. Also, multiple minislot allocations of PUSCH within a slot are not possible.

[0039] In either case, due to such scheduling constraints, it may not be able to achieve the more stringent delay requirements in NR Rel. 15, i.e., delays down to 0.5 ms. This may require minislot allocation of PUSCH. Furthermore, limited support for PUSCH allocation also does not take advantage of the benefits that come from a minislot, i.e., a transmission time interval (TTI) that contains fewer symbols than a slot (a slot containing 14 symbols).

[0040] First general-purpose scenario In view of the above, the authors of the present disclosure have recognized the need for a more flexible support of PUSCH transmissions, ie, a mechanism that is not limited to PUSCH transmissions requiring a separate uplink grant.

[0041] At the same time, the higher flexibility should not be obtained 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 modifications to the current uplink scheduling mechanism, i.e., the current format of the uplink grant. In other words, the signaling mechanism, for example, in the form of format 0-0 or 0-1 of downlink control information (DCI) for carrying the uplink grant, remains the same, thereby avoiding additional signaling overhead when scheduling PUSCH transmissions.

[0042] Therefore, it is a basic understanding of the present disclosure that PUSCH transmission is supported with flexible timing that does not cause additional signaling overhead.

[0043] In this context, such flexible timing support for PUSCH transmissions can be recognized not only as a possibility for increasing the versatility of the mechanism, but also as a necessity for avoiding conflicts with, for example, dynamic changes to the slot format (UL / DL), as becomes clear from the implementation discussed under Section 6.3.3 as "Option 4" of 3GPP TR 38.824 v2.0.1 "Study on physical layer enhancements for NR ultra-reliable and low latency case (URLLC)," which is incorporated herein by reference.

[0044] For illustrative purposes, assume 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 a conflict with a dynamic change of the slot format. For example, if the slot format specifies a change to one of the specified consecutive symbols from UL to DL, this will trigger a conflict with the configured multiple PUSCH transmissions.

[0045] However, recognizing the need for flexible timing support, the authors identified substantial technical constraints arising from the current uplink scheduling mechanism, namely, Downlink Control Information (DCI) Formats 0-1 in NR Rel. 15.

[0046] One possibility for carrying the uplink grant 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. In this regard, DCI Format 0-1 includes an antenna port field that enables antenna port consistency for PUSCH transmissions.

[0047] Antenna ports may be defined such that "the channel carried by symbols on an antenna port can be inferred from the channel carried by other symbols on the same antenna port" (see, e.g., section 4.4 of 3GPP Technical Specification TS 38.211 v.15.5.0, titled "Physical channels and modulation (Release 15)"). The antenna port concept is also extended to the front-loaded demodulation reference signal (DMRS) included in the PUSCH transmission.

[0048] For example, a first front-mounted DMRS configuration corresponding to configuration type 1 supports up to four orthogonal DMRS ports when single-symbol DMRS is used and up to eight orthogonal DMRS ports when double-symbol DMRS is used. A second front-mounted DMRS configuration corresponding to configuration type 2 provides support for up to six orthogonal DMRS ports when single-symbol DMRS is used and up to 12 orthogonal ports when double-symbol DMRS is used. From the receiver's perspective, the DMRS ports are quasi-co-located.

[0049] Effectively, the forward-mounted DMRS configurations are designed to allow flexibility between single-symbol DMRS and double-symbol DMRS. In particular, configuration type 1 and configuration type 2 are devised to support not only the maximum length of each symbol for DMRS (e.g., maxLength=2), but also fewer symbols. This can be seen, for example, for configuration type 1 (e.g., dmrs-Type=1), reproduced below from section 7.3.1.1.2 of 3GPP Technical Specification TS 38.212 v.15.5.0, "Multiplexing and channel coding (Release 15)," which is incorporated herein by reference. For this configuration type 1, not only can eight DMRS ports be scheduled for a maximum two-symbol DMRS, but also up to four DMRS ports can be scheduled. [Table 1] According to such a front-mounted DMRS configuration, the antenna port field included in downlink control information (DCI) format 0-1 carries not only the DMRS port used for the front-mounted DMRS (see, e.g., the third column of Table 7.3.1.1.2-7 of TS 38.212), but also an index value (see, e.g., the first column of the same table) that specifies the number of symbols (e.g., single symbol or double symbol) used for the front-mounted DMRS (see, e.g., the fourth column of the same table).

[0050] The authors of this disclosure have recognized that such forward-mounted DMRS configurations may impose substantial technical constraints on utilizing a single uplink grant of said DCI format 0-1 for scheduling multiple PUSCH transmissions with flexible timing.

[0051] For example, assume that a single uplink grant schedules two PUSCH transmissions with flexible timing. It is generally understood that each of these PUSCH transmissions requires separate notification of the DMRS port to be used. Because a single uplink grant contains only a single antenna port field, it is not possible to signal the individual DMRS ports to be used. Rather, it is only possible to convey a single index value that specifies one DMRS port for each preceding DMRS configuration. Thus, there is ambiguity as to whether this signaled DMRS port is used for the first or second of the two PUSCH transmissions with flexible timing.

[0052] In other words, the authors of this disclosure have recognized that there is an ambiguity that one index value carried in the antenna port field of a single uplink grant may relate to any one of multiple PUSCH transmissions.

[0053] The authors also recognized that situations may arise where scheduling two PUSCH transmissions with flexible timing may lead to conflicts regarding the mapping of the front-mounted DMRS in the PUSCH transmissions.

[0054] For example, assume that a single uplink grant schedules two PUSCH transmissions with flexible timing, i.e., different lengths. It is generally understood that such two PUSCH transmissions do not necessarily allow both single-symbol and double-symbol DMRS transmissions. Rather, the length of a PUSCH transmission imposes constraints on the number of symbols for DMRS that can be carried therein. This introduces ambiguity as to whether the number of symbols forwarded for DMRS indicated by the single uplink grant is used for the first or second of the two PUSCH transmissions with flexible timing.

[0055] In NR Rel. 15, the demodulation reference signal for the PUSCH is described in section 6.4.1.1 of 3GPP Technical Specification TS 38.211 v.15.5.0, titled "Physical channels and modulation (Release 15)," which is incorporated herein by reference.

[0056] For mapping to physical resources, the position of the DMRS symbol is given by l and the duration is l d where, for example, l d is the duration between the first OFDM symbol of a slot for PUSCH mapping type A according to Table 6.4.1.1.3-3 and 6.4.1.1.3-4 and the last OFDM symbol of the scheduled PUSCH resource of the slot, or d is the duration of the scheduled PUSCH resource for PUSCH mapping type B according to Tables 6.4.1.1.3-3 and 6.4.1.1.3-4. The referenced tables are reproduced below. [Table 2] [Table 3]

[0057] With such a mapping of DMRS symbols to PUSCH, it is allowed for any duration of the scheduled PUSCH resource for single-symbol DMRS, while for mapping type A, double-symbol DMRS is allowed when the duration of the scheduled PUSCH resource is four symbols or more (which results in an unspecified DMRS position for mapping type A in Table 6.4.1.1.3-4). d<4), and in the case of mapping type B, when the duration of the scheduled PUSCH resource is 5 symbols or more (resulting in an unspecified DMRS position for mapping type A in Table 6.4.1.1.3-4). d <4 and l d =4).

[0058] In other words, the authors of this disclosure have recognized that there is again an ambiguity that one index value carried in the antenna port field of a single uplink grant relates to any one of multiple PUSCH transmissions.

[0059] In summary, the present disclosure of example embodiments improves support for allocation of Physical Uplink Shared Channel (PUSCH) transmissions with flexible timing and facilitates enabling accurate channel estimation utilizing the demodulation reference signals (DMRS) carried thereon.

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

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

[0062] Rather, it should be noted that numerous assumptions have been made herein so that the principles underlying the present disclosure can be explained in a clear and understandable manner. However, these assumptions should be understood as merely examples for illustrative purposes and should not limit the scope of the present disclosure. Those skilled in the art will recognize that the principles as described in the following disclosure and claims can be applied to different scenarios and methods not explicitly described herein.

[0063] A mobile terminal is called a user equipment (UE) in LTE and NR. It may be a mobile device such as a wireless phone, a smartphone, a tablet computer, or a Universal Serial Bus (USB) stick with user equipment functionality. However, the term mobile device is not so limited; in general, a relay may have the functionality of such a mobile device, and a mobile device may also function as a relay.

[0064] A base station (BS) forms at least part of a system of interconnected units, e.g. a (central) baseband unit and different radio frequency units, which interface with different antenna panels or radio heads in the network to serve the terminals, i.e. the base station provides wireless access to the terminals.

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

[0066] 5 and 6 respectively show exemplary implementations according to a first general scenario of the building blocks of a user equipment 410 and a base station 460. 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.

[0067] 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 transmitter / receiver 670-b.

[0068] This disclosure is provided under the assumption that the user equipment 410 performs multiple physical uplink shared channel (PUSCH) transmissions. In an example use case, these PUSCH transmissions may carry repetitions of the same transport block, thereby resulting in multiple PUSCH repetitions, including the initial PUSCH transmission and at least one (subsequent) PUSCH repetition.

[0069] Even for PUSCH transmissions with flexible timing, this does not prevent them from carrying repetitions of the same transport block. Consider the example where scheduled PUSCH transmissions have different lengths, i.e., occupy different numbers of symbols. Even then, PUSCH transmissions can carry repetitions of the same transport block if the modulation and coding scheme (MCS) is appropriately adjusted for each PUSCH transmission.

[0070] Nevertheless, the present disclosure should not be understood as being limited only to transport block repetition. Thus, the present disclosure refers generally to PUSCH transmissions, i.e., without any restrictions on the transport blocks carried therein. Many alternative use cases are also possible, for example, when scheduled PUSCH transmissions are used in part for transport block repetition and one-shot transmissions.

[0071] Referring to FIG. 7, a sequence diagram is shown in which a user equipment (UE) performs multiple PUSCH transmissions according to a first general scenario, i.e., the user equipment 410 performs multiple PUSCH transmissions that do not include different numbers of symbols for the forward-mounted DMRSs carried thereon.

[0072] When the user equipment 410 determines that it will perform multiple PUSCH transmissions, it receives a single (e.g., one) uplink grant (see, e.g., step 710 of FIG. 7), suitable for scheduling the multiple PUSCH transmissions. The uplink grant is received from the base station 460, which is scheduling the transmission on the uplink, i.e., on the physical uplink shared channel (PUSCH). For example, this receiving operation may be performed by the UL grant receiver 520-a of FIG. 5.

[0073] The user equipment 410 receives an uplink grant that includes an antenna port field with an index value. This index value may be used for many purposes in the user equipment 410, for example to indicate the antenna port on which the PUSCH transmission is to be performed. In other words, this index value is used for multiple PUSCH transmissions scheduled by the uplink grant.

[0074] In terms of 3GPP terminology, the described uplink grant including the antenna port field may refer to signaling of downlink control information (DCI) formats 0-1. For a comprehensive description of DCI formats 0-1, see section 7.3.1.1.2 of 3GPP Technical Specification TS 38.212 v.15.5.0, which is incorporated herein by reference. Furthermore, since all PUSCH transmissions exclusively utilize the pre-configured port with number 0, another (alternative) format for conveying dynamic uplink grants in 3GPP systems, i.e., DCI format 0-0, does not include the antenna port field.

[0075] Also, in terms of 3GPP terminology, the described uplink grant including the antenna port field may alternatively refer to the signaling of the ConfiguredGrantConfig information element (IE). A comprehensive description of the ConfiguredGrantConfig IE is given in section 6.3.2 of 3GPP technical specification TS 38.331 v.15.5.0, titled "Radio Resource Control (RRC) protocol specification (Release 15)," which is incorporated herein by reference. As is evident from the ASN.1 notation, not all ConfiguredGrantConfig IEs necessarily include the antenna port field, since it is included in the sequence of fields designated as optional for the IE.

[0076] Based on the received uplink grant, the user equipment 410 determines time domain resources to be used for multiple PUSCH transmissions (e.g., see step 720 of FIG. 7). In general, the determined time domain resources for each PUSCH transmission should be understood as multiple consecutive symbols designated for uplink transmission. For example, this determination operation may be performed by the time domain resource determination processing circuit 530-a.

[0077] More specifically, the determined time domain resources define the number (e.g., maximum or total) of PUSCH transmissions scheduled in the uplink grant and define the length (e.g., in symbols) of each of the multiple PUSCH transmissions. The time domain resources are pre-allocated by the base station 460 for utilization by the user equipment 410.

[0078] In an example implementation, the determined time domain resource may also define the position of at least one, i.e., the first or all, of multiple PUSCH transmissions. Such a position may be defined, for example, in terms of a (relative) slot offset and an (absolute) symbol number specifying the start within the slot. Alternatively, such a position may be inferred (e.g., in a technical specification) in the form of consecutive PUSCH transmissions, i.e., when the last symbol of a preceding PUSCH transmission is immediately followed by the first symbol of a subsequent PUSCH transmission.

[0079] Nevertheless, in the context of this disclosure, it is sufficient that the user equipment 410 can (actually) determine the time domain resources used for multiple PUSCH transmissions based on the received uplink grant. In other words, this disclosure is not limited to any of the following example implementations.

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

[0081] In the case of dynamic uplink grants, the mechanism of this implementation can be best summarized as follows:

[0082] The user equipment 410 receives a PUSCH config information element (IE) in the form of RRC signaling, i.e., the PUSCH config IE is applicable to a specific bandwidth portion. The user equipment 410 then configures a table defined by the PUSCH time domain resource allocation list (IE) carried in the received PUSCH config IE. The table includes rows each having a value indicating a PUSCH mapping type, a value K2 indicating a slot offset, and a value SLIV indicating a start and length indicator. The user equipment 410 then receives DCI in the form of MAC signaling carrying the time domain resource allocation filled with a value of m, where the value of m provides a row index m+1 to the RRC configuration table.

[0083] This allows the user equipment 410 to determine the time domain resource for at least one PUSCH transmission based on the number of slots carrying the received DCI, the value K2 indicating the slot offset, and the value SLIV indicating the start and length indicators included in the indexed row of the RRC configuration table.

[0084] The mechanism of this exemplary implementation does not (explicitly) specify how the number of multiple PUSCH transmissions is signaled to the user equipment 410. For this reason, different improvements to the mechanism are currently under active discussion, all aimed at allowing the user equipment 410 to (conclusively) characterize the time domain resources for multiple PUSCH transmissions.

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

[0086] This indication of the number of PUSCH transmissions allows the user equipment 410 to determine the respective time domain resources with the underlying assumption that the determined time domain resource for the first PUSCH transmission directly (consecutively) follows the time domain resources for all subsequent PUSCH transmissions whose (total) number corresponds to the indicated number of PUSCH transmissions.

[0087] In particular, the user equipment 410 may use the same parameters of the indexed row of the RRC configuration table to determine the time domain resources of not only the first PUSCH transmission but also all subsequent PUSCH transmissions such that they are arranged contiguously in the time domain, e.g., this means that all time domain resources have the same symbol length and are arranged contiguously within one slot or across multiple slots.

[0088] In another refinement of the example implementation, it is assumed that the PUSCH config 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 scheduled by the base station 460.

[0089] According to such time domain resource allocation, the user equipment 410 can, for example, infer the (total) number of PUSCH transmissions from the number of individual time domain resource allocations contained in the RRC configuration table, and via the index, the user equipment 410 can refer to the indexed row of the RRC configuration table to infer the (total) number of PUSCH transmissions and determine the time domain resources for the same transmissions.

[0090] More specifically, an indexed row of the RRC configuration table may contain multiple SLIV values ​​corresponding to individual time domain resources located within one slot or across multiple slots. Because each SLIV value indicates the start and length of a time domain resource with respect to a symbol, the time domain resources need not be located contiguously in the time domain. Rather, the start and length of each time domain resource may be set independently.

[0091] 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 by the base station 460. Such adaptation may be necessary to handle (or address) possible side effects resulting from dynamic reconfiguration of the underlying slot format (UL / DL).

[0092] In other words, all the above-mentioned mechanisms are based on a time domain resource allocation that is semi-statically configured (in advance) via RRC, and cannot reflect all possible slot formats in advance. Therefore, dynamically notified slot format changes may be required to adapt the semi-statically configured time domain resource allocation, i.e., when determining the time domain resources (actually) available for PUSCH transmission.

[0093] One possible conflict may arise from the signaling of a changed slot format, which specifies the symbol of the slot that changes from UL to DL. If this symbol was previously intended to be used as part of the signaled time domain resource allocation, its specified change from UL to DL will result in a conflict that is handled at the user equipment side.

[0094] Such conflicts may be resolved by the user equipment shifting the signaled time domain resource allocation so that the determined time domain resources occupy only the newly designated UL symbols of the slot.

[0095] Another potential conflict may arise from the signaling of a modified slot format that specifies fewer symbols of a slot as UL and more symbols as DL. Even if individual time-domain resource allocations are not affected by the slot format change, situations may arise where the signaled time-domain resource allocations are distributed across multiple slots. In particular, in the case where the signaled time-domain resource allocations related to a single PUSCH transmission are distributed across multiple slots (crossing a slot boundary), this will result in a conflict that needs to be reprocessed (or handled) at the user equipment side, since PUSCH transmissions that cross slot boundaries are not allowed.

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

[0097] In particular, due to this segmentation, the user equipment 410 must send more PUSCH transmissions than scheduled by the uplink grant.

[0098] For illustrative purposes, assume that the user equipment 410 receives an uplink grant scheduling three PUSCH transmissions. If one of these PUSCH transmissions is segmented by crossing a slot boundary, the affected PUSCH transmission actually results in two PUSCH transmissions: one for the segment before the slot boundary and another for the segment after the slot boundary. The received uplink grant then causes the user equipment 410 to determine the time domain resources for a total of four PUSCH transmissions.

[0099] In summary, there are several possible 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, although the present disclosure should not be understood as being limited to any of these example implementations.

[0100] After determining the time domain resources for (possibly more) PUSCH transmissions based on the received uplink grant, the user equipment 410 configures the PUSCH transmissions for those subsequent transmissions, each of which includes at least one pre-mounted demodulation reference signal (DMRS) to enable coherent demodulation of the PUSCH transmission.

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

[0102] It is emphasized that the present disclosure focuses on a situation where different numbers of symbols are allowed to be used for each of the front-mounted DMRs, i.e., the present disclosure considers a situation where not only a single-symbol DMRS is allowed as the front-mounted DMRS, but instead both single-symbol and double-symbol DMRSs are allowed to be used as the front-mounted DMRS.

[0103] It is generally understood that, compared with single-symbol DMRS, double-symbol DMRS allows for higher accuracy of channel estimation, which facilitates achieving better results for coherent demodulation of PUSCH transmissions. In particular, double-symbol DMRS has been introduced motivated by addressing highly time-variant and / or frequency-selective wireless channels. Furthermore, double-symbol DMRS is also recognized to provide superior detection results, i.e., avoidance of false detection, for PUSCH transmissions scheduled by configured grants.

[0104] Nevertheless, using such a larger number of symbols for the front-loaded DMRS comes at the expense of reduced throughput per PUSCH transmission. If PUSCH transmissions are scheduled at a certain length, the decision whether to use double-symbol DMRS or not may reduce the symbols available to 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 the base station to decide whether, under given radio channel conditions, the user equipment needs to use double-symbol DMRS for a PUSCH transmission or whether it is sufficient to use single-symbol DMRS for the same PUSCH transmission.

[0105] There are two distinct steps before the user device 410 actually knows whether to use double-symbol DMRS or single-symbol DMRS for a particular PUSCH transmission.

[0106] In a first step, the user equipment 410 is signaled with an indication whether the use of different numbers of symbols is (generally) allowed for PUSCH transmissions, which is subsequently used when determining the (actual) number of symbols to be used as forward-mounted DMRS included in each PUSCH transmission.

[0107] For example, the notification may configure the user equipment 410 (e.g., for "Yes") to be able to use either double-symbol or single-symbol DMRS for all future PUSCH transmissions. In other words, the configuration simply specifies the (overall) availability of double-symbol DMRS for PUSCH transmissions. It does not require that double-symbol DMRS be actually used. In addition to this example, the notification may also configure the user equipment 410 (e.g., for "No") to be able to use only single-symbol DMRS for PUSCH transmissions.

[0108] In a second step, the user equipment determines the (actual) number of symbols to be used for each of the DMRSs preceding the multiple PUSCH transmissions. This determination is based on the index value conveyed in the antenna port field contained in the received uplink grant. In this regard, since the index value is conveyed in the received uplink grant, it is directly linked to each of the PUSCH transmissions.

[0109] 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 a forward-mounted DMRS: if the maximum number of symbols is two, then either double-symbol DMRS or single-symbol DMRS is allowed.

[0110] In another example implementation, the user equipment 410 determines the number of symbols used for the DMRS preceding each of the multiple PUSCH transmissions. To this end, the user equipment 410 references its setting of the maximum number of symbols and, based on this, selects a corresponding table, such as Table 7.3.1.1.2-7 of TS 38.212 v.15.5.0, as described above, when maxLength=2. The user equipment 410 then uses the index value received from the antenna port field of the uplink grant to determine the corresponding indexed row of the selected table and extracts the number of symbols used for each of the DMRS preceding each of the multiple PUSCH transmissions from the fourth column of the indexed row.

[0111] It is emphasized here that the present disclosure focuses on situations where a number of PUSCH transmissions have different lengths, i.e. where the time domain resources determined based on the uplink grant specify different lengths for at least two of the multiple PUSCH transmissions.

[0112] It is recognized that under this condition, the correct functioning of the scheduling of multiple PUSCH transmissions can no longer be ensured. Rather, if the determined uplink resource defines PUSCH transmissions of different lengths, it does not distinguish between the individual PUSCH transmissions, and therefore it cannot be guaranteed that the determined (single) number of symbols is suitable for defining the use of DMRS for each of the (multiple) PUSCH transmissions having different lengths.

[0113] In an exemplary implementation, the user equipment 410 uses the determined (single) number of symbols to select a corresponding table for PUSCH mapping and a determined number of symbols of "1" in Table 6.4.1.1.3-3 of TS 38.211 v.15.5.0 if intra-slot frequency hopping is not possible, or "2" in Table 6.4.1.1.3-4 of TS 38.211 v.15.5.0 if intra-slot frequency hopping is not possible, as described above. From these tables, the user equipment 410 estimates the location of the DMRS in each PUSCH.

[0114] As soon as these PUSCH transmissions do not have the same (single) length, but have two different lengths, a situation may arise where the mapping of the DMRS, i.e., its position in the respective PUSCH transmission, is undefined (or unspecified, non-compliant).

[0115] This follows directly from the observation that the length (or duration) of the PUSCH transmission (first column in the table above) determines the position of the DMRS in the PUSCH transmission (columns two through nine in the table above). And, for shorter lengths (or durations) of PUSCH transmissions, no specific mapping of the double-symbol DMRS is specified. And, the ambiguity between a (single) index value and PUSCH transmissions of different lengths may, in the worst case, result in an unspecified (or unspecified, non-compliant) mapping of the DMRS to PUSCH transmissions of different lengths.

[0116] From this it can be seen that correct functioning of scheduling multiple PUSCH transmissions cannot be ensured in situations where different numbers of symbols (or double symbols) DMRS are allowed and the scheduled PUSCH transmissions have different lengths.

[0117] To ensure correct functioning of the scheduling of multiple PUSCH transmissions, the user equipment 410 transmits the same (defined) or fewer PUSCH transmissions using the same (defined) or a subset of the time domain resources of the received uplink grant (see, for example, 740 in FIG. 7). Specifically, this transmission operation is performed such that none of the at least one configured anteriorly-placed DMRSs uses a different number of symbols. For example, this transmission operation may be performed by the PUSCH transmission transmitter 520-b.

[0118] Even with the focus of this disclosure on situations where multiple PUSCH transmissions have different lengths, a solution to the first general scenario is to resolve situations where the user equipment 410 cannot ensure correct functioning of PUSCH scheduling by transmitting the same or fewer PUSCH transmissions, with the constraint that the determined different number of symbols is not used for any of the at least one configured antecedent DMRS.

[0119] In other words, instead of the user equipment operating under conditions in which a different number of symbols is allowed to be used for each of the preceding DMRSs and the received uplink grant is processed for the same purpose, i.e., to allow further use of DMRSs with a different number of symbols (e.g., the user equipment explicitly due to maxLength=2 in Table 7.3.1.1.2-7 of TS 38.212 v.15.5.0), it is explicitly required that the user equipment 410 transmits only PUSCH transmissions that do not include preceding DMRSs that use a different number of symbols. This resolves any ambiguity between the (single) uplink grant signaling from the base station and the corresponding transmission of the (multiple) PUSCH transmissions.

[0120] In an exemplary embodiment, the user equipment 410 determines the number of symbols to be used for each of the at least one forward-mounted DMRS based on all the different lengths of the multiple PUSCH transmissions. For example, this may involve not only determining the (single) number of symbols based on the index value received by the user equipment 410, but also comparing this (single) number with the (e.g., maximum) number of symbols required for each of the PUSCH transmissions of different lengths to avoid unspecified (or unspecified, non-compliant) mapping of DMRSs to PUSCH transmissions of different lengths. If this comparison indicates a conflict, the user equipment 410 needs to re-determine the (currently) used number of symbols based on all the different lengths of the multiple PUSCH transmissions.

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

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

[0123] Referring to FIG. 8, a sequence diagram of a base station (BS) receiving multiple PUSCH transmissions is shown for a first general scenario, i.e., where the base station 460 receives multiple PUSCH transmissions that do not include different numbers of symbols for the forward-mounted DMRSs carried thereon.

[0124] In this context, the base station 460 determines a time domain resource (see, e.g., step 810 of FIG. 8), where the determined time domain resource specifies the number of PUSCH transmissions and the length of each of the PUSCH transmissions. For example, this determination operation may be performed by the time domain resource determination processing circuit 680-a.

[0125] The base station 460 determines the number of symbols to be used for each of at least one preceding DMRS included in the plurality of PUSCH transmissions (e.g., see step 820 in FIG. 8), where the determined number of symbols is one of a smaller number and a larger number of symbols. For example, this determination operation may be performed by the DMRS symbol number determination processing circuit 680-b.

[0126] If at least two of the multiple PUSCH transmissions have different lengths and one of the at least two of the multiple PUSCH transmissions cannot include a larger number of symbols for each of the at least one forwardly placed DMRS, base station 460 determines an index value associated with a smaller number of symbols from the determined number of symbols used for each of the included at least one forwardly placed DMRS (see again step 820 in FIG. 8). For example, this determination operation may be performed by index value determination processing circuit 680-d.

[0127] The base station 460 then transmits a single uplink grant based on the determined time domain resources for the multiple PUSCH transmissions (e.g., see step 830 of FIG. 8), where the single uplink grant includes an antenna port field with the determined index value to be used for the multiple PUSCH transmissions. For example, this transmitting operation may be performed by the uplink grant transmitter 670-a.

[0128] The base station 460 then receives multiple PUSCH transmissions using the determined time domain resources (e.g., see step 840 of FIG. 8), each of the multiple PUSCH transmissions including at least one pre-placed demodulation reference signal (DMRS).

[0129] For simplicity, the operation of the base station is kept fairly short. However, this should not be understood as a limitation. Rather, those skilled in the art will readily understand that the same or similar considerations as those explicitly described for user equipment equally apply in the operation of the base station, i.e., when the base station is scheduling multiple PUSCH transmissions using a single uplink grant.

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

[0131] Therefore, resolving this situation (when correct functioning of PUSCH scheduling cannot be ensured) when determining index values ​​associated with a smaller number of symbols from the determined number of symbols used for each of the at least one forward-mounted DMRS included in base station 460 is a solution to the first general scenario.

[0132] This allows the base station 460 to be assured of receiving the same or fewer PUSCH transmissions, subject to the constraint that the determined different number of symbols is not used for any of the at least one preceding DMRS involved.

[0133] First Exemplary Implementation The following first exemplary implementation is provided to give a more detailed description of the operation of the user equipment 410 according to a first general scenario, i.e., when the user equipment 410 performs multiple PUSCH transmissions that do not include different numbers of symbols for the forward-mounted DMRSs carried thereon. Reference is made to Figure 9, which shows a sequence diagram of the user equipment 410 performing multiple PUSCH transmissions according to a first exemplary implementation of the first general mechanism.

[0134] This explanation is given under the assumption that a different number of symbols (e.g., maxLength=2) is allowed to be used for each of the front-mounted DMRSs. In other words, the present disclosure does not consider a situation where only a single-symbol DMRS is available (allowed) as a front-mounted DMRS, but instead considers a situation where both a single-symbol and a double-symbol DMRS are available (allowed) as a front-mounted DMRS.

[0135] When the user equipment 410 determines that it will perform multiple PUSCH transmissions, it receives a single (e.g., one) uplink grant (see, e.g., step 910 of FIG. 9). The uplink grant is carried to schedule the multiple PUSCH transmissions. The uplink grant is received from the base station 460, which is scheduling the transmission on the uplink, i.e., on the physical uplink shared channel (PUSCH).

[0136] Based on the received uplink grant, the user equipment 410 determines the time domain resources to be used for the multiple PUSCH transmissions (see, e.g., step 920 of FIG. 9). In general, the determined time domain resources for each PUSCH transmission should be understood as multiple consecutive symbols designated for the uplink transmission.

[0137] The present disclosure again focuses on the situation where scheduled PUSCH transmissions have different lengths, i.e., the time domain resources determined based on the uplink grant specify different lengths for at least two of the PUSCH transmissions.

[0138] In this context, the user equipment 410 determines the number of symbols (e.g., single symbol or double symbol) to be used for the DMRS preceding each PUSCH transmission (see, e.g., step 930 of FIG. 9 ). To this end, the user equipment 410 determines the number of symbols based on the received index value conveyed in the antenna port field of a single uplink grant.

[0139] For this purpose, the user equipment 410 illustratively refers to its setting of the maximum number of symbols and, based on this, selects a corresponding table, for example, Table 7.3.1.1.2-7 of TS 38.212 v.15.5.0 in this example where maxLength=2 as described above. The user equipment 410 then uses the index value received from the antenna port field of the uplink grant to determine the corresponding indexed row of the selected table, and extracts from the fourth column of this indexed row the number of symbols used for each of the DMRSs placed before the multiple PUSCH transmissions.

[0140] The user equipment then checks whether at least two of the multiple PUSCH transmissions can include a larger number of symbols for each of the at least one forward-placed DMRS (see, e.g., step 940 of FIG. 9).

[0141] To this end, the user equipment 410 uses the determined (single) symbol number to select the corresponding table for PUSCH mapping as described above, e.g., a determined symbol number of "1" in Table 6.4.1.1.3-3 of TS 38.211 v.15.5.0 if intra-slot frequency hopping is disabled, or a determined symbol number of "2" in Table 6.4.1.1.3-4 of TS 38.211 v.15.5.0 if intra-slot frequency hopping is disabled. From these tables, the user equipment 410 estimates the location of the DMRS in each PUSCH.

[0142] In particular, the user equipment 410 determines whether the mapping or location of the DMRS in the PUSCH transmission (columns 2-9 of the table above) is specified ("no" in step 940) or unspecified ("yes" in step 940) for different lengths (or durations) of each PUSCH transmission (column 1 of the table above). This determination operation is based on the general understanding that a particular mapping of the double-symbol DMRS is unspecified (or unspecified, non-compliant) for shorter lengths (or durations) of PUSCH transmission.

[0143] If it is determined that the determined number of symbols for a DMRS can result for at least one of the multiple PUSCH transmissions in the unspecified mapping (or position) of the DMRS ("yes" in step 940), the user equipment tentatively selects at least one forward-mounted DMRS with fewer symbols (single-symbol DMRS) for all of the multiple PUSCH transmissions (not explicitly shown in FIG. 9). However, this tentative selection of fewer symbols needs to be confirmed, as it may involve a change in the DMRS port used.

[0144] For this reason, the user device 410 checks whether the same DMRS port is available with the tentatively selected fewer symbols used for at least one preceding DMRS of all of the multiple PUSCH transmissions (see, e.g., step 950 of FIG. 9). 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. Also, to avoid contention, it must be ensured that the tentatively selected symbols are also available for the same DMRS port, as determined based on the index value.

[0145] For this purpose, the user equipment 410 exemplarily refers to the correspondingly selected table, Table 7.3.1.1.2-7 of TS 38.212 v.15.5.0, as described above again in the present case with maxLength=2. From this table, the user equipment 410 determines the DMRS port (see, for example, the third column of the same table) indicated by the index value (see, for example, the first column of the same table) carried in the antenna port field of the received uplink grant. The user equipment then checks whether the provisionally selected fewer symbols (single-symbol DMRS) are also available with the same DMRS port (see, for example, DMRS ports 0-3 in the second to fifth rows of the same table), i.e., with the same DMRS port number.

[0146] If the confirmation is positive (“yes” in step 950), the user equipment 410 has confirmed that even if a different fewer number of symbols were selected, the fewer number of symbols is available for the DMRS signaled via the uplink grant and placed before all of the multiple PUSCH transmissions on the same DMRS port on which the base station 460 expects to receive the PUSCH transmission.

[0147] In this regard, when selecting at least one forward-loaded DMRS, the user equipment 410 may: Fewer symbols are used, -To ensure that the same DMRS port number is used, Select at least one forward-placed DMRS for all of the multiple PUSCH transmissions, where the DMRS port number used for all of the at least one forward-placed DMRS is the same as the DMRS port number associated with the received index value.

[0148] The results are illustrated in Figures 11-13.

[0149] For example, according to Table 7.3.1.1.2-7 of TS 38.212 v.15.5.0, for antenna port mapping of a DMRS configuration type with a maximum length of 2 symbols, if any of index values ​​4, 5, 6, or 7 associated with a 2-symbol-long DMRS is signaled, the corresponding possible index associated with a 1-symbol-long DMRS and available for use is 0, 1, 2, or 3, respectively.

[0150] Furthermore, if the determination is negative ("no" in step 950), the user equipment 410 has determined that a different tentatively selected smaller number of symbols cannot be used via the same DMRS port as the DMRS port determined based on the index value. In other words, for multiple PUSCH transmissions, this requires that different DMRS ports be used.

[0151] That is, the DMRS port, as indicated via the uplink grant, on which base station 460 expects to receive a PUSCH transmission cannot be used with fewer symbols tentatively selected for DMRS.

[0152] In this regard, when selecting at least one forward-loaded DMRS, the user equipment 410 may: No more than one symbol for each of the at least one forward-mounted DMRS can be included; The DMRS port number cannot be the same as the DMRS port number associated with the received index value. Omit at least one PUSCH transmission from the plurality of PUSCH transmissions (see, eg, step 970 of FIG. 9).

[0153] The user device 410 then transmits fewer PUSCH transmissions such that more symbols and the same DMRS port numbers are used for the remainder of the non-omitted PUSCH transmissions (see, e.g., step 980 of FIG. 9).

[0154] In summary, the user equipment 410 transmits the same (see "yes" in step 950) or fewer (see "no" in step 950) PUSCH transmissions using the same or a portion determined based on the received uplink grant, in particular such that at least one preceding DMRS does not use a different number of symbols.

[0155] The above description of the first exemplary implementation 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 may equally perform the first exemplary implementation disclosed herein, i.e., receive multiple PUSCH transmissions that do not include different numbers of symbols for the forward-mounted DMRSs carried thereon.

[0156] Reference is made to Figure 10, which illustrates a sequence diagram of a base station 460 scheduling multiple PUSCH transmissions according to a first exemplary implementation 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 that include the initial PUSCH transmission and at least one (subsequent) PUSCH transmission.

[0157] In this context, the base station 460 determines a time domain resource (see, for example, step 1010 of FIG. 10), which defines the number of PUSCH transmissions and the length of each of the PUSCH transmissions.

[0158] This disclosure again focuses on situations where scheduled PUSCH transmissions have different lengths, ie, where the time domain resources define different lengths for at least two of the PUSCH transmissions.

[0159] The base station 460 determines the number of symbols to be used for each of at least one forward-placed DMRS included in the multiple PUSCH transmissions (e.g., see step 1020 of FIG. 10), where the determined number of symbols is one of a fewer number and a greater number of symbols.

[0160] Base station 460 then determines whether one of the numbers of PUSCH transmissions can include a larger number of symbols for each of at least one preceding DMRS (see, for example, step 1030 of FIG. 10).

[0161] For this purpose, the base station 460 uses the determined number of symbols to select a corresponding table of PUSCH mapping, e.g., a determined number of symbols of "1" in Table 6.4.1.1.3-3 of TS 38.211 v.15.5.0 when intra-slot frequency hopping is disabled, or a determined number of symbols of "2" in TS 38.211 v.15.5.0 when intra-slot frequency hopping is disabled, as described above. From these tables, the user equipment 410 estimates the location of the DMRS in each PUSCH.

[0162] In particular, base station 460 determines whether the mapping or location of the DMRS in the PUSCH transmission (columns 2-9 of the table above) is specified (if "no" in step 1030) or unspecified (if "yes" in step 1030) for different lengths (or durations) of each PUSCH transmission (column 1 of the table above). This determination operation is based on the general understanding that a particular mapping of the double-symbol DMRS is unspecified (or unspecified, non-compliant) for shorter lengths (or durations) of PUSCH transmission.

[0163] If it is determined that the number of symbols determined for the DMRS occurs for at least one of the multiple PUSCHs in the unspecified mapping (or position) of the DMRS (if "yes" in step 1030), the base station 460 selects at least one forward-placed DMRS with fewer symbols (single-symbol DMRS) for all of the multiple PUSCH transmissions (not explicitly shown in FIG. 10).

[0164] If it is determined that the number of symbols determined for a DMRS occurs for all of the multiple PUSCHs in the specified mapping (or position) of the DMRS (if "no" in step 1030), base station 460 selects at least one forward-placed DMRS with a larger number of symbols (single-symbol DMRS) for all of the multiple PUSCH transmissions (not explicitly shown in FIG. 10).

[0165] Base station 460 then determines an index value associated with a smaller number of symbols (e.g., see step 1040 of FIG. 10) or a larger number of symbols (e.g., see step 1050 of FIG. 10) to be used in all of the multiple PUSCH transmissions, i.e., for each of the at least one forward-placed DMRS. The determined index values ​​are also associated with the same DMRS port.

[0166] The base station 460 then transmits a single uplink grant based on the determined time domain resources for the multiple PUSCH transmissions (e.g., see step 1060 of FIG. 10), where the single uplink grant includes an antenna port field with the determined index value to be used for the multiple PUSCH transmissions.

[0167] The base station 460 also receives multiple PUSCH transmissions using the determined time domain resources (e.g., see step 1070 of FIG. 10), each of the multiple PUSCH transmissions including at least one pre-placed demodulation reference signal (DMRS).

[0168] For simplicity, the operation of the base station is kept rather short. However, this should not be understood as a limitation. Rather, those skilled in the art will readily understand that the same or similar considerations as those explicitly described for the user equipment equally apply in the operation of the base station, i.e., when the base station is scheduling multiple PUSCH transmissions via a single uplink grant.

[0169] Second general-purpose scenario Referring now to FIG. 14, a sequence diagram of a user equipment (UE) performing multiple PUSCH transmissions according to a second general scenario is shown, i.e., the user equipment 410 performs multiple PUSCH transmissions that may include different numbers of symbols for the forward-mounted DMRSs carried thereon, but for none of them different DMRS port numbers are used.

[0170] According to a common understanding, the DMRS port must be used consistently for the transmission and reception of multiple PUSCH transmissions. In other words, the DMRS placed in front of the PUSCH transmission must use a consistent DMRS port (e.g., the same DMRS port number) that is signaled via the uplink grant and expected to be received. Without such consistency, the reception of multiple PUSCH transmissions will not be successful because the included DMRS cannot contribute to accurate channel estimation and therefore coherent demodulation at the receiver side.

[0171] Thus, the second general scenario facilitates avoiding such inconsistencies for cases 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 preceding DMRS carried therein.

[0172] When the user equipment 410 determines that it will perform multiple PUSCH transmissions, it receives a single (e.g., one) uplink grant (see, e.g., step 1410 of FIG. 14). The uplink grant is suitable for scheduling the multiple PUSCH transmissions. The uplink grant is received from the base station 460 that is scheduling the transmission on the uplink, i.e., on the physical uplink shared channel (PUSCH). For example, this receiving operation may be performed by the UL grant receiver 520-a of FIG. 5.

[0173] The user equipment 410 receives an uplink grant that includes an antenna port field with an index value. This index value may be used for many purposes in the user equipment 410, for example to indicate the antenna port on which the PUSCH transmission is to be performed. In other words, this index value is used for multiple PUSCH transmissions scheduled by the uplink grant.

[0174] In terms of 3GPP terminology, the described uplink grant including the antenna port field may refer to signaling of downlink control information (DCI) formats 0-1. For a comprehensive description of DCI formats 0-1, see section 7.3.1.1.2 of 3GPP Technical Specification TS 38.212 v.15.5.0, which is incorporated herein by reference. Furthermore, another (alternative) format for conveying dynamic uplink grants in 3GPP systems, namely DCI format 0-0, does not include the antenna port field because all PUSCH transmissions exclusively use the pre-configured port with number 0.

[0175] Also, in terms of 3GPP terminology, the uplink grant described including the antenna port field may alternatively refer to the signaling of the ConfiguredGrantConfig information element (IE). For a comprehensive description of the ConfiguredGrantConfig IE, see section 6.3.2 of 3GPP Technical Specification TS 38.331 v.15.5.0, titled "Radio Resource Control (RRC) protocol specification (Release 15)," which is incorporated herein by reference. As is evident from the ASN.1 notation, not all ConfiguredGrantConfig IEs include the antenna port field, since it is included in the sequence of fields designated as optional for the IE.

[0176] Based on the received uplink grant, the user equipment 410 determines time domain resources to be used for multiple PUSCH transmissions (e.g., see step 1420 of FIG. 14). In general, the determined time domain resources for each PUSCH transmission should be understood as multiple consecutive symbols designated for uplink transmission. For example, this determination operation may be performed by the time domain resource determination processing circuit 530-a.

[0177] More specifically, the determined time domain resources define the number (e.g., maximum or total) of PUSCH transmissions scheduled by the uplink grant and define the length (e.g., symbols) of each of the PUSCH transmissions. The time domain resources are pre-assigned by the base station 460 for use by the user equipment 410.

[0178] In an example implementation, the determined time domain resource may also define the location of at least one, i.e., the first or all, of multiple PUSCH transmissions. Such a location may be defined, for example, in terms of a (relative) slot offset and an (absolute) symbol number specifying the start within the slot. Alternatively, such a location may be estimated (e.g., in a technical specification) in terms of consecutive PUSCH transmissions, i.e., the last symbol of a preceding PUSCH transmission directly precedes the first symbol of a following PUSCH transmission.

[0179] Nevertheless, in the context of this disclosure, it is sufficient that the user equipment 410 is (actually) able to determine the time domain resources to be used for multiple PUSCH transmissions based on the received uplink grant. In other words, this disclosure is not limited to any of the example implementations described above for the first general scenario.

[0180] All of the above mechanisms are based on semi-statically configured time domain resource allocation via RRC, and cannot reflect all possible slot formats in advance. Therefore, dynamically signaled slot format changes may be required to adapt the semi-statically configured time domain resource allocation, i.e., to determine the time domain resources that are actually available for PUSCH transmission.

[0181] One potential conflict can arise from the signaling of a changed slot format that specifies the symbol of the slot that changes from UL to DL. If this symbol was previously intended for use as part of a signaled time domain resource allocation, that specified change from UL to DL will result in a conflict that is handled (or addressed) at the user equipment side.

[0182] Such a conflict may be resolved by the user equipment shifting its signaled time domain resource allocation so that the determined time domain resources occupy only the newly designated UL symbols of the slot.

[0183] Another potential conflict may result from signaling a modified slot format that specifies fewer symbols of a slot as UL and more symbols as DL. Even if individual time-domain resource allocations are not affected by the slot format change, situations may arise where the signaled time-domain resource allocations are distributed across multiple slots. In particular, if the signaled time-domain resource allocations associated with a single PUSCH transmission are distributed across multiple slots (crossing a slot boundary), this will result in a conflict that needs to be handled again at the user equipment side, since PUSCH transmissions that cross slot boundaries are not allowed.

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

[0185] In particular, due to this segmentation, the user equipment 410 must send more PUSCH transmissions than scheduled by the uplink grant.

[0186] For illustrative purposes, assume that the user equipment 410 receives an uplink grant that schedules three PUSCH transmissions. If one of these PUSCH transmissions is segmented by crossing a slot boundary, this single affected PUSCH transmission actually results in two PUSCH transmissions: one for the segment before the slot boundary and another for the segment after the slot boundary. The received uplink grant then results in the user equipment 410 determining time domain resources for a total of four PUSCH transmissions.

[0187] In summary, there are several possible 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, although the present disclosure should not be understood as being limited to any of these example implementations.

[0188] After determining the time domain resources for the (possibly larger) PUSCH transmissions based on the received uplink grant, the user equipment 410 configures the PUSCH transmissions for those subsequent transmissions, each of which includes at least one pre-mounted demodulation reference signal (DMRS) to enable coherent demodulation of the PUSCH transmission.

[0189] In this context, the user equipment 410 determines the DMRS port number (e.g., DMRS port numbers 0 to 7 for a Type 1 configuration, or DMRS port numbers 0 to 11 for a Type 2 configuration) to be used for the DMRS that is placed in front of each PUSCH transmission (see, for example, step 1430 in FIG. 14). To this end, the user equipment 410 determines the DMRS port number based on the received index value carried in the antenna port field of the single uplink grant. For example, this determination operation may be performed by the DMRS port number determination processing circuit 530-c for the DMRS.

[0190] Emphasis is placed on the fact that this disclosure focuses on a situation where different numbers of symbols are allowed to be used for each of the front-mounted DMRSs. In other words, this disclosure does not consider a situation where only single-symbol DMRSs are allowed as front-mounted DMRSs, but instead considers a situation where both single-symbol and double-symbol DMRSs are allowed as front-mounted DMRSs.

[0191] There are two distinct steps before the user equipment 410 actually knows whether to use double-symbol or single-symbol DMRS for a particular PUSCH transmission. In the first step, the user equipment 410 is signaled with an indication of whether the use of a different number of symbols is (generally) permitted for PUSCH transmissions. This indication is subsequently used in determining the (actual) number of symbols to be used as front-loaded DMRS included in each PUSCH transmission.

[0192] In an exemplary implementation, the user equipment 410 is provided with a configuration that specifies the maximum number of symbols that are allowed to be used as a forward-mounted DMRS: if the maximum number of symbols is two, then either double-symbol or single-symbol DMRS is allowed to be used.

[0193] In a second step, the user equipment determines the (actual) number of symbols to be used for each DMRS preceding the multiple PUSCH transmissions. This determination is based on the index value conveyed in the antenna port field contained in the received uplink grant. In this regard, since the index value is conveyed in the received uplink grant, it is directly linked to the respective number of PUSCH transmissions.

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

[0195] When different numbers of symbols are allowed for the forward-placed DMRS, each different number of symbols must be associated with a different DMRS port number and be separately notifiable from the base station 460 to the user equipment 410. For this reason, the index value carried in the uplink grant allows for unambiguous notification of the (actual) number of symbols used for the forward-placed DMRS in the case of different numbers of allowed symbols.

[0196] At the same time, the index value not only signals the (actual) number of symbols used for the DMRS placed in front, but rather signals the number of symbols for the DMRS placed in front combined with the DMRS port number used for the DMRS included in the multiple PUSCH transmissions.

[0197] Here, if different numbers of symbols are allowed, the index value only effectively achieves unambiguous notification of the (actual) number of symbols used in organizing the different index values, so that the same DMRS port number is a possible index for all of the different numbers of symbols allowed for DMRS, otherwise a DMRS port would not be available with both of the different numbers of symbols allowed.

[0198] In an exemplary implementation, the user equipment 410 determines the DMRS port number for the DMRS preceding each of the multiple PUSCH transmissions. To do so, the user equipment 410 references its configuration of the maximum number of symbols and, based on this, selects a corresponding table, such as Table 7.3.1.1.2-7 of TS 38.212 v.15.5.0, as described above, for maxLength=2. The user equipment 410 then uses the index value received from the antenna port field of the uplink grant to determine the corresponding indexed row of the selected table and extracts, from the third column of this indexed row, the DMRS port number used for each of the DMRS preceding each of the multiple PUSCH transmissions.

[0199] The effect of the number of allowed symbols can be seen in Table 7.3.1.1.2-7 of TS 38.212 v.15.5.0, as mentioned above. This table is designed for the case where a different number of symbols is allowed, i.e., maxLength=2. Therefore, each index value (first column of the table) is unambiguously associated with the (actual) number of symbols used for the preceding DMRS (fourth column of the table). At the same time, each index value (first column of the table) is also unambiguously associated with a DMRS port number (third column of the table).

[0200] Furthermore, because different DMRS ports identified by numbers are available for DMRSs placed on all fronts of different numbers of symbols, different DMRS port numbers 0-3 may be used for both single-symbol DMRSs (see rows 2-5 of the table) and double-symbol DMRSs (see rows 6-9 of the table). Only DMRS port numbers 4-7 may be used for double-symbol DMRSs (see rows 10-13 of the table).

[0201] Therefore, the allowed number of symbols has a substantial impact on the determination of the DMRS port numbers, in that it not only defines the table to be used, but also defines the situation where at least some of the DMRS port numbers (e.g., DMRS port numbers 0 to 3 in the table described above) are indexable with two different index values, i.e., each of the (actual) numbers of symbols allowed.

[0202] Here, emphasis is placed on the fact that the present disclosure focuses on situations where the multiple PUSCH transmissions have different lengths, i.e. where the time domain resource determined based on the uplink grant specifies different lengths for at least two of the multiple PUSCH transmissions.

[0203] It is recognized that under this condition, the correct functioning of the scheduling of multiple PUSCH transmissions can no longer be ensured. Rather, if the determined uplink resources define PUSCH transmissions of different lengths, it cannot be guaranteed that the determined (single) number of symbols is suitable for defining the use of DMRS for each of the (multiple) PUSCH transmissions with different lengths, since the determined uplink resources do not distinguish between the individual PUSCH transmissions.

[0204] In an exemplary implementation, the user equipment 410 uses the determined number of symbols to select a corresponding table for PUSCH mapping, e.g., a determined number of symbols of "1" in Table 6.4.1.1.3-3 of TS 38.211 v.15.5.0 if intra-slot frequency hopping is disabled, or a determined number of symbols of "2" in Table 6.4.1.1.3-4 of TS 38.211 v.15.5.0 if intra-slot frequency hopping is disabled, as described above. From these tables, the user equipment 410 estimates the location of the DMRS in each PUSCH.

[0205] As soon as the multiple PUSCH transmissions do not have the same (single) length, but have two different lengths, a situation may arise where the mapping of the DMRS, i.e., its position in each PUSCH transmission, is undefined (or unspecified, non-compliant).

[0206] This follows directly from the observation that the length (or duration) of a PUSCH transmission (column 1 of the table above) determines the position of the DMRS in the PUSCH transmission (columns 2-9 of the table above), and no specific mapping of double-symbol DMRS is specified for shorter lengths (or durations) of PUSCH transmissions. Furthermore, the ambiguity between a single index value and PUSCH transmissions of different lengths may, in the worst case, result in an unspecified (or unspecified, non-compliant) mapping of DMRS to PUSCH transmissions of different lengths.

[0207] From this it can be seen that the correct functioning of the scheduling of multiple PUSCH transmissions cannot be guaranteed under the condition that DMRSs of different numbers of symbols (or double symbols) are allowed and the scheduled PUSCH transmissions have different lengths.

[0208] To ensure correct functioning of the scheduling of multiple PUSCH transmissions, the user equipment 410 transmits the same (defined) or fewer PUSCH transmissions using the same (defined) or a portion of the time domain resources of the uplink grant (see, for example, 1440 in FIG. 14). Specifically, this transmission operation is performed such that none of the included at least one preceding DMRS uses different DMRS port numbers. For example, this transmission operation may be performed by the PUSCH transmission transmitter 520-b.

[0209] When the present disclosure focuses on a situation where multiple PUSCH transmissions have different lengths, the solution to the second general scenario is to solve a situation where the correct functioning of PUSCH scheduling can be ensured by user equipment 410 transmitting the same or fewer PUSCH transmissions with the constraint that a different determined DMRS port number is not used for any of the at least one preceding DMRS.

[0210] Although it is permitted that a different number of symbols may be used for each preceding DMRS and the received uplink grant is processed for the same purpose, i.e., operating to allow further utilization of DMRSs with different numbers of symbols (e.g., user equipment in Table 7.3.1.1.2-7 of TS 38.212 v.15.5.0., explicitly due to maxLength=2), the user equipment 410 is explicitly required to transmit only PUSCH transmissions that do not contain preceding DMRSs that use different DMRS port numbers.

[0211] That is, this second general scenario attempts to achieve this objective, i.e., to allow further use of DMRS with different numbers of symbols, but recognizes that not all different DMRS port numbers can be used with all the different numbers of symbols allowed (e.g., in Table 7.3.1.1.2-7 of TS 38.212 v.15.5.0, according to maxLength=2, DMRS ports 0 to 3 can be used with both single-symbol DMRS and double-symbol DMRS, and DMRS ports 4 to 7 can be used with only double-symbol DMRS).

[0212] This prevents, for example, a situation in which some of the multiple PUSCH transmissions with a larger number of symbols for DMRS use a different DMRS port number (e.g., DMRS ports 4-7 in the table above) than the DMRS port numbers (e.g., DMRS ports 0-3 in the table above) used for other of the multiple PUSCH transmissions with fewer symbols for DMRS. In other words, in this second general scenario, different numbers of symbols for DMRS are generally allowed among the multiple PUSCH transmissions, but it is guaranteed that the same DMRS port is used for all of the multiple PUSCH transmissions that also correspond to the DMRS port indicated via the index value of the antenna port field carried in the (single) uplink grant.

[0213] This allows for resolution of any ambiguity between the signaling of a (single) uplink grant from the base station and the corresponding transmission of a (multiple) PUSCH transmission.

[0214] In an example embodiment, the user equipment 410 determines a DMRS port number to be used for each of the at least one forward-placed DMRS based on all the different lengths of the multiple PUSCH transmissions. For example, this may require the user equipment 410 not only to determine a (single) DMRS port number based on the received index value, but also to compare the (single) DMRS port number with the corresponding indexed symbol number by the (e.g., maximum) number of symbols required for each of the different length PUSCH transmissions to avoid unspecified (or unspecified, non-compliant) mapping of the DMRS to the different length PUSCH transmissions. If the comparison indicates a conflict, the user equipment 410 needs to re-determine the (currently) used DMRS port number based on all the different lengths of the multiple PUSCH transmissions.

[0215] The above description 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 may equally implement the second general scenario disclosed herein.

[0216] Again, the assumption is that the base station 460 schedules 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 the initial PUSCH transmission and at least one (subsequent) PUSCH repetition.

[0217] Referring to FIG. 15, a sequence diagram of a base station (BS) receiving multiple PUSCH transmissions according to a second general scenario is shown, i.e., the base station 460 receives multiple PUSCH transmissions that do not include different DMRS port numbers of the forward-mounted DMRSs carried therein.

[0218] In this context, the base station 460 determines a time domain resource (e.g., see step 1510 of FIG. 15), where the determined time domain resource specifies the number of PUSCH transmissions and the length of each of the PUSCH transmissions. For example, this determination operation may be performed by the time domain resource determination processing circuit 680-a.

[0219] The base station 460 determines the number of symbols to be used for each of at least one forward-mounted DMRS included in the multiple PUSCH transmissions (e.g., see step 1520 in FIG. 15), where the determined number of symbols is one of a smaller number and a larger number of symbols. For example, this determination operation may be performed by the DMRS symbol number determination processing circuit 680-b.

[0220] When at least two of the multiple PUSCH transmissions have different lengths and when one of the at least two of the multiple PUSCH transmissions cannot include a larger number of symbols for each of the at least one preceding DMRS, base station 460 determines an index value associated with a larger number of symbols from the determined number of symbols and a DMRS port number for which the same DMRS port number is also usable for the at least one preceding DMRS by the determined fewer symbols (see step 1530 in FIG. 15). For example, this determination operation may be performed by index value determination processing circuit 680-d.

[0221] In an example implementation, base station 460 determines an index value from a table such as Table 7.3.1.1.2-7 of TS 38.212 v.15.5.0 with maxLength=2 such that if only a portion of a PUSCH transmission can contain more symbols for DMRS, then use of DMRS ports 4 through 7 is prohibited and use of DMRS ports 0 through 3 is permitted. Then, only the same DMRS port number can be used with more and fewer symbols without disallowing changes of DMRS ports during signaling of the number of PUSCH transmissions.

[0222] Importantly, since each of DMRS ports 0-3 can be signaled via a different index value, base station 460 determines the index value to correspond to the greater number of symbols that still allows for the mapping (or location) of DMRS for each length of multiple PUSCH transmissions, e.g., according to Tables 6.4.1.1.3-3 and 6.4.1.1.3-4 of TS 38.211 v.15.5.0.

[0223] The base station 460 then transmits a single uplink grant based on the determined time domain resources for the multiple PUSCH transmissions (e.g., see step 1540 of FIG. 15), where the single uplink grant includes an antenna port field with the determined index value to be used for the multiple PUSCH transmissions. For example, this transmitting operation may be performed by the uplink grant transmitter 670-a.

[0224] The base station 460 also receives multiple PUSCH transmissions using the determined time domain resources (e.g., see step 1550 of FIG. 15), each of the multiple PUSCH transmissions including at least one pre-placed demodulation reference signal (DMRS).

[0225] For simplicity, the operation of the base station is kept somewhat brief. However, this is not to be understood as a limitation. Rather, those skilled in the art will readily appreciate that the same or similar considerations explicitly described for user equipment find equal application in the operation of a base station when scheduling multiple PUSCH transmissions with a single uplink grant.

[0226] It has also been recognized that the correct functioning of the scheduling of multiple PUSCH transmissions can no longer be guaranteed.

[0227] Thus, base station 460 determines an index value associated with a larger number of symbols from the determined number of symbols, and a DMRS port number for which the same DMRS port number is also available for at least one preceding DMRS with the determined fewer symbols.

[0228] This allows the base station 460 to ensure that it receives the same or fewer PUSCH transmissions such that a different DMRS port number is not used as determined for any of the at least one preceding DMRS included.

[0229] Second Exemplary Implementation The following second exemplary implementation is provided to give a more detailed description of the operation of the user equipment 410 according to a second general scenario, i.e., the user equipment 410 performs multiple PUSCH transmissions that do not include different DMRS port numbers for the forward-loaded DMRSs carried therein. Reference is made to Figure 16, which shows a sequence diagram of the user equipment 410 performing multiple PUSCH transmissions according to the second exemplary implementation of the second general mechanism.

[0230] This explanation is given under the assumption that different numbers of symbols are allowed to be used for each DMRS placed in front (e.g., maxLength=2). That is, this disclosure does not consider a situation in which only a single-symbol DMRS is available (allowed) as a DMRS placed in front, but rather considers a situation in which both a single-symbol and a double-symbol DMRS are available (allowed) as a DMRS placed in front.

[0231] When the user equipment 410 determines that it will perform multiple PUSCH transmissions, it receives a single (e.g., one) uplink grant (see, e.g., step 1610 of FIG. 16). The uplink grant is conveyed to schedule the multiple PUSCH transmissions. The uplink grant is received from the base station 460, which is scheduling transmissions on the uplink, i.e., on the physical uplink shared channel (PUSCH).

[0232] Based on the received uplink grant, the user equipment 410 determines the time domain resources to be used for the multiple PUSCH transmissions (see, for example, step 1620 of FIG. 16). In general, the time domain resources determined for each PUSCH transmission are understood as the number of consecutive symbols designated for the uplink transmission.

[0233] The present disclosure again focuses on situations where scheduled PUSCH transmissions have different lengths, i.e., where the time domain resources determined based on the uplink grant specify different lengths for at least two of the PUSCH transmissions.

[0234] In this context, the user equipment 410 determines the number of symbols (e.g., single symbol or double symbol) to be used for the DMRS preceding each PUSCH transmission (see, e.g., step 1630 of FIG. 16. To this end, the user equipment 410 determines the number of symbols based on the received index value conveyed in the antenna port field of a single uplink grant.

[0235] For this purpose, the user equipment 410 exemplarily refers to its setting of the maximum number of symbols and selects a corresponding table accordingly, for example, Table 7.3.1.1.2-7 of TS 38.212 v.15.5.0 as described above in the present case where maxLength=2. The user equipment 410 then determines the corresponding indexed row of the selected table using the index value received from the antenna port field of the uplink grant, and extracts the number of symbols used for each DMRS placed in front of the multiple PUSCH transmissions from the fourth column of the indexed row.

[0236] Thereafter, the user equipment checks whether some (one or more) of the multiple PUSCH transmissions can include more symbols for each DMRS placed in front of at least one other (see, for example, step 1640 of FIG. 16).

[0237] In this context, the term "some" is understood to refer to a (particular) subset of all of the plurality of PUSCH transmissions. This term is used consistently throughout the remainder of this description. For example, a part of the plurality of PUSCH transmissions may be a (particular) third PUSCH transmission, but not the first and second PUSCH transmissions from a total of three PUSCH transmissions.

[0238] To this end, the user equipment 410 uses the determined number of symbols to select a corresponding table for PUSCH mapping, e.g., a determined number of symbols of "1" in Table 6.4.1.1.3-3 of TS 38.211 v.15.5.0 if intra-slot frequency hopping is disabled, or a determined number of symbols of "2" in Table 6.4.1.1.3-4 of TS 38.211 v.15.5.0 if intra-slot frequency hopping is disabled, as described above. From these tables, the user equipment 410 estimates the location of the DMRS in each PUSCH.

[0239] In particular, the user equipment 410 determines whether the mapping or location of the DMRS in the PUSCH transmission (columns 2-9 in the table above) is specified (if "no" in step 1640) or unspecified (if "yes" in step 1640) for different lengths (or durations) of each PUSCH transmission (column 1 in the table above). This determination operation is based on the general understanding that a particular mapping of the double-symbol DMRS is unspecified (or unspecified, non-compliant) for shorter lengths (or durations) of PUSCH transmission.

[0240] Upon determining that the number of symbols determined for a DMRS occurs for a portion (one or more) of the PUSCH transmissions in the unspecified mapping (or position) of the DMRS (if "yes" in step 1640), the user equipment tentatively selects (not explicitly shown in FIG. 16) at least one forward-placed DMRS with fewer symbols (single-symbol DMRS) for that portion (see above). However, this tentative selection of fewer symbols needs to be confirmed, as it may involve a change in the DMRS port used.

[0241] For this reason, the user equipment 410 checks whether the same DMRS port is available with fewer pre-selected symbols used for a DMRS placed before at least one of the portions of the multiple PUSCH transmissions (see above) (see, e.g., step 1650 of FIG. 16). That is, the index value carried in the antenna port field determines not only the number of symbols for the DMRS but also the DMRS port used for that portion of the multiple PUSCH transmissions. Also, to avoid contention, it must be ensured that the number of pre-selected symbols is also available for the same DMRS port determined based on the index value.

[0242] For this purpose, the user equipment 410 exemplarily refers to a correspondingly selected table, again in the present case with maxLength=2, exemplarily Table 7.3.1.1.2-7 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., the third column of the same table) indicated by the index value (see, e.g., the first column of the same table) carried in the antenna port field of the received uplink grant. The user equipment then checks whether the provisionally selected fewer symbols (single-symbol DMRS) are also available with the same DMRS port (see, e.g., DMRS ports 0-3 in rows 2-5 of the same table), i.e., with the same DMRS port number.

[0243] If the confirmation is positive (“yes” in step 1650), the user equipment 410 has confirmed that even if a different fewer number of symbols were selected, this fewer number of symbols is indicated via the uplink grant and is available for the DMRS to be placed in front of some of the PUSCH transmissions (see above) via the same DMRS port on which the base station 460 expects to receive the PUSCH transmission.

[0244] For the remainder (or other) of the multiple PUSCH transmissions, the user equipment 410 tentatively selects the number of symbols to correspond to the (single) number of symbols for the preceding DMRS, which is determined based on the received index value conveyed in the antenna port field of the single uplink grant. That is, for PUSCH transmissions that can include more symbols for DMRS, it also utilizes the more symbols signaled in the single uplink grant.

[0245] In this regard, when selecting at least one forward-loaded DMRS, the user equipment 410 may: Fewer and more symbols are used for at least one forward-mounted DMRS; The same DMRS port number is used for fewer and more symbols. For all of the multiple PUSCH transmissions, select at least one forward-placed DMRS, where the same DMRS port number used for all of the at least one forward-placed DMRS is the same as the DMRS port number associated with the received index value.

[0246] This result is illustrated in Figures 18 to 20. For example, according to Table 7.3.1.1.2-7 of TS 38.212 v.15.5.0 for antenna port mapping for a DMRS configuration type with a maximum length of two symbols, if any of index values ​​4, 5, 6, or 7 associated with a two-symbol-long DMRS is signaled, the corresponding possible indexes associated and usable for a one-symbol-long DMRS are 0, 1, 2, or 3, respectively.

[0247] Furthermore, if the determination is negative (“no” at step 1650), the user equipment 410 has determined that a different tentatively selected fewer symbols cannot be used on the same DMRS port as the DMRS port determined based on the index value, i.e., for multiple PUSCH transmissions, this requires that different DMRS ports be used.

[0248] That is, the DMRS port, as indicated via the uplink grant, on which base station 460 expects to receive a PUSCH transmission cannot be used with fewer symbols tentatively selected for DMRS.

[0249] In this regard, when selecting at least one forward-loaded DMRS, the user equipment 410 may: It cannot include more symbols for each DMRS placed in front of at least one The DMRS port number cannot be the same as the DMRS port number associated with the received index value. Omit some PUSCH transmissions (see above) from the multiple PUSCH transmissions (see, for example, step 1670 of FIG. 16).

[0250] The user device 410 then transmits fewer PUSCH transmissions such that for the remaining (or other) non-omitted PUSCH transmissions, a larger number of symbols and the same DMRS port number are used (e.g., see step 1680 of FIG. 16).

[0251] In summary, the user equipment 410 transmits the same (see "yes" in step 1650) or fewer (see "no" in step 1650) number of PUSCH transmissions using the same (determined) or a subset of the time domain resources determined based on the received uplink grant, in particular such that none of the at least one preceding DMRS uses a different DMRS port number(s).

[0252] The above description of the second exemplary implementation is given from the perspective of the user equipment 410. However, this should not be understood as a limitation on the present disclosure. The base station 460 equally performs the first exemplary implementation disclosed herein, i.e., the base station 460 receives multiple PUSCH transmissions that do not include different DMRS port numbers for the forward-loaded DMRSs carried thereon.

[0253] Reference is made to Figure 17, which illustrates a sequence diagram of a base station 460 scheduling multiple PUSCH transmissions according to a second exemplary implementation 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 the initial PUSCH transmission and at least one (subsequent) PUSCH repetition.

[0254] In this context, the base station 460 determines a time domain resource (see, for example, step 1710 of FIG. 17), where the determined time domain resource defines the number of multiple PUSCH transmissions and the length of each of the multiple PUSCH transmissions.

[0255] This disclosure again focuses on situations where scheduled PUSCH transmissions have different lengths, ie, where the time domain resources define different lengths for at least two of the PUSCH transmissions.

[0256] The base station 460 determines the number of symbols to be used for each of at least one forward-placed DMRS included in the multiple PUSCH transmissions (see, for example, step 1720 of FIG. 17), where the determined number of symbols is one of a smaller number and a larger number of symbols.

[0257] Base station 460 then determines whether a portion of the multiple PUSCH transmissions can include more symbols for each of the at least one forward-placed DMRSs (see, eg, step 1730 of FIG. 17).

[0258] In this context, the term "some" is understood to refer to a (particular) subset of all of the plurality of PUSCH transmissions. This term is used consistently throughout the remainder of this description. For example, a part of the plurality of PUSCH transmissions may be a (particular) third PUSCH transmission, but not the first and second PUSCH transmissions from a total of three PUSCH transmissions.

[0259] To this end, the base station 460 uses the determined number of symbols to select a corresponding table for PUSCH mapping, e.g., a determined number of symbols of "1" in Table 6.4.1.1.3-3 of TS 38.211 v.15.5.0 if intra-slot frequency hopping is disabled, or a determined number of symbols of "2" in Table 6.4.1.1.3-4 of TS 38.211 v.15.5.0 if intra-slot frequency hopping is disabled, as described above. From these tables, the user equipment 410 estimates the location of the DMRS in each PUSCH.

[0260] In particular, base station 460 determines whether the mapping or location of the DMRS in the PUSCH transmission (columns 2-9 in the table above) is specified (if "no" in step 1730) or unspecified (if "yes" in step 1730) for different lengths (or durations) of each PUSCH transmission (column 1 in the table above). This determination operation is based on the general understanding that a particular mapping of the double-symbol DMRS is unspecified (or unspecified, non-compliant) for shorter lengths (or durations) of PUSCH transmission.

[0261] Upon determining that the number of symbols determined for a DMRS occurs for a portion (see above) of the multiple PUSCH transmissions in the unspecified mapping (or position) of the DMRS (if "yes" in step 1730), base station 460 selects at least one preceding DMRS with fewer symbols (single-symbol DMRS) for that portion (see above) of the multiple PUSCH transmissions (not explicitly shown in FIG. 17).

[0262] Base station 460 then determines an index value associated with a larger number of symbols from the determined number of symbols, and if it is determined that some PUSCH transmissions cannot include a larger number of symbols (see the "yes" case in step 1730), a DMRS port number for which the same DMRS port number is also usable for at least one preceding DMRS with the determined fewer symbols (see, for example, step 1740 in FIG. 17).

[0263] Alternatively, the base station 460 determines, for each of the at least one forward-mounted DMRS included, an index value associated with a larger number of symbols and the same DMRS port to be used in all of the multiple PUSCH transmissions.

[0264] The base station 460 then transmits a single uplink grant based on the determined time domain resources for the multiple PUSCH transmissions (e.g., see step 1760 of FIG. 17), where the single uplink grant includes an antenna port field with the determined index value to be used for the multiple PUSCH transmissions.

[0265] The base station 460 also receives multiple PUSCH transmissions using the determined time domain resources (e.g., see step 1770 of FIG. 17), each PUSCH transmission including at least one pre-placed demodulation reference signal (DMRS).

[0266] For simplicity, the operation of the base station is kept somewhat brief. However, this should not be understood as a limitation. Rather, those skilled in the art will find that the same or similar considerations explicitly described for user equipment apply equally to the operation of the base station, i.e., when it is scheduling multiple PUSCH transmissions with a single uplink grant.

[0267] Third general-purpose scenario According to a third general scenario, a user equipment and a base station are proposed that respectively perform and schedule multiple PUSCH transmissions based on a single uplink grant. The operation of the user equipment and the base station according to this third general scenario is not shown separately; they will be very similar to those shown in Figures 7 and 8 for the first general scenario. Nevertheless, their operation can best be understood from the following description.

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

[0269] The user equipment 410 then determines time domain resources based on the received uplink grant. The determined time domain resources define the number of PUSCH transmissions and the length of each PUSCH transmission. Each PUSCH transmission includes at least one pre-loaded demodulation reference signal (DMRS). For example, this determination operation may be performed by the time domain resource determination processing circuit 530-b.

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

[0271] In particular, the user equipment 410 transmits the same number of PUSCH transmissions for all of the at least one forward-placed DMRS such that fewer symbols are used according to the received index value, and does not transmit any of the PUSCH transmissions if the received index value is associated with a greater number of symbols used for the at least one forward-placed DMRS. For example, this transmission operation may be performed by the PUSCH transmission transmitter 520-a.

[0272] Separately, the base station 460 determines time domain resources, which define the number of PUSCH transmissions and the length of each PUSCH transmission. For example, this determination operation may be performed by the time domain resource determination processing circuit 680-a.

[0273] If different numbers of symbols are allowed for each of the at least one preceding DMRS, the base station 460 performs a specifically adapted decision operation on the index values.

[0274] In particular, the base station determines index values ​​associated with fewer symbols such that the same number of PUSCH transmissions, including at least one forward-mounted DMRS, are received using fewer symbols. For example, this determination operation may be performed by index value determination processing circuitry 680-d.

[0275] The base station 460 then transmits a single uplink grant based on the determined time domain resources for the multiple PUSCH transmissions. The single uplink grant includes an antenna port field with index values ​​to be used for the multiple PUSCH transmissions. For example, this determination operation may be performed by the uplink grant transmitter 670-a.

[0276] The base station 460 may also receive multiple PUSCH transmissions using the determined time domain resources, each PUSCH transmission including at least one pre-placed demodulation reference signal (DMRS). For example, this receiving operation may be performed by the PUSCH transmitter receiver 670-b.

[0277] The present disclosure can be realized by software, hardware, or software in conjunction with hardware.

[0278] Each functional block used in describing each of the above-mentioned embodiments can be realized in part or in whole by an LSI such as an integrated circuit, and each process described in each embodiment may be controlled in part or in whole by the same LSI or a combination of LSIs.

[0279] The LSI may be formed as an individual chip, or may be formed as a single chip containing some or all of the functional blocks. The LSI may also include data input / output devices coupled thereto. Here, the LSI may be referred to as an IC, system LSI, super LSI, or ultra LSI depending on the level of integration.

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

[0281] Furthermore, an FPGA (Field Programmable Gate Array) that can be programmed after manufacturing an LSI or a reconfigurable processor in which the connections and settings of circuit cells arranged inside the LSI can be reconfigured may be used.

[0282] The present disclosure can be realized as digital processing or analog processing. As a result of advances in semiconductor technology and other derivative technologies, if future integrated circuit technology replaces LSI, the functional blocks can be integrated using future integrated circuit technology. Biotechnology can also be applied.

[0283] The present disclosure may be implemented by any type of apparatus, device or system having communication capabilities, referred to as a communications apparatus.

[0284] Some non-limiting examples of such communication devices include telephones (e.g., mobile (cell) phones, smartphones), tablets, personal computers (PCs) (e.g., laptops, desktops, netbooks), cameras (e.g., digital still / video cameras), 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 remote medical) devices, and vehicles (e.g., automobiles, airplanes, ships) that provide communication capabilities, and various combinations thereof.

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

[0286] Communications may include, for example, exchanging data via cellular systems, wireless LAN systems, satellite systems, and the like, as well as various combinations thereof.

[0287] A communications apparatus may include devices such as a controller or a sensor coupled to the communications device to perform the communications functions described in this disclosure. For example, a communications apparatus may include a controller or a sensor that generates control or data signals used by the communications device to perform the communications functions of the communications apparatus.

[0288] Communications equipment may also include infrastructure facilities such as base stations, access points, and any other equipment, device, or system that communicates with or controls equipment such as those in the above non-limiting examples.

[0289] According to a first aspect, there is provided a user equipment (UE), comprising: a receiver that, during operation, receives a single uplink grant for multiple PUSCH transmissions, the single uplink grant including an antenna port field with an index value to be used for the multiple PUSCH transmissions; a processor that, during operation, determines time domain resources based on the received uplink grant, the determined time domain resources defining a number of PUSCH transmissions and a length of each of the multiple PUSCH transmissions; and a transmitter that, during operation, transmits the multiple PUSCH transmissions using the determined time domain resources, wherein each of the multiple PUSCH transmissions includes at least and a transmitter including one front-mounted demodulation reference signal (DMRS), wherein the processor, during operation, determines a number of symbols to be used for each of the at least one front-mounted DMRS of the plurality of PUSCH transmissions based on the received index value, and, when at least two of the plurality of PUSCH transmissions have different lengths and different numbers of symbols are allowed for each of the at least one front-mounted DMRS, the transmitter, during operation, transmits the same or fewer PUSCH transmissions such that the determined different numbers of symbols are not used for any of the included at least one front-mounted DMRS.

[0290] According to a second aspect provided in addition to the first aspect, the processor is configured to use, during operation, for each of the at least one preceding DMRS, a maximum number of two symbols that allows use with a single-symbol DMRS having a smaller number of one symbol or a double-symbol DMRS having a larger number of two symbols.

[0291] According to a third aspect provided in addition to either the first or second aspect, the processor determines, during operation, the number of symbols to be used for each of the at least one forward-mounted DMRS based on all different lengths of the plurality of PUSCH transmissions.

[0292] According to a fourth aspect provided in addition to any of the first to third aspects, when at least two of the plurality of PUSCH transmissions have different lengths and when one of the at least two of the plurality of PUSCH transmissions cannot include a larger number of symbols for each of the at least one forward-placed DMRS, the processor, upon determining the number of symbols to be used during operation, selects the at least one forward-placed DMRS with fewer symbols for all of the plurality of PUSCH transmissions, and the transmitter transmits the same number of PUSCH transmissions so that fewer symbols are used for all of the at least one forward-placed DMRS during operation.

[0293] According to a fifth aspect provided in addition to the fourth aspect, when at least one of the plurality of PUSCH transmissions cannot include a larger number of symbols for the at least one forwardly placed DMRS included therein during operation, the processor selects, for all of the plurality of PUSCH transmissions, the at least one forwardly placed DMRS with the fewer symbols.

[0294] According to a sixth aspect provided in addition to either the fourth or fifth aspect, when the processor selects the at least one forwardly placed DMRS during operation, the processor selects the at least one forwardly placed DMRS such that the fewer symbols are used and the same DMRS port number is used for all of the plurality of PUSCH transmissions, and the DMRS port number used for all of the at least one forwardly placed DMRS is the same as the DMRS port number associated with the received index value.

[0295] According to a seventh aspect, which is provided in addition to any of the fourth to sixth aspects, when the processor selects the at least one forward-placed DMRS during operation, it excludes from the plurality of PUSCH transmissions at least one PUSCH transmission that cannot include a larger number of symbols for each of the at least one forward-placed DMRS and cannot use the same DMRS port number as the DMRS port number associated with the received index value, and the transmitter transmits fewer of the PUSCH transmissions such that the larger number of symbols and the same DMRS port number are used for all of the at least one forward-placed DMRS included during operation.

[0296] According to an eighth aspect, a user equipment (UE) includes: a receiver that, during operation, receives a single uplink grant for multiple PUSCH transmissions, the single uplink grant including an antenna port field with index values ​​to be used for the multiple PUSCH transmissions; a processor that, during operation, determines time domain resources based on the received uplink grant, the determined time domain resources defining a number of PUSCH transmissions and a length of each of the multiple PUSCH transmissions; and a transmitter that, during operation, transmits the multiple PUSCH transmissions using the determined time domain resources, the multiple PUSCH transmissions each including at least one forward PUSCH transmission. and a transmitter including a demodulation reference signal (DMRS) placed in front of the PUSCH transmissions, wherein the processor, during operation, determines a DMRS port number to be used for each of the at least one preceding DMRS of the plurality of PUSCH transmissions based on the received index value, and if at least two of the plurality of PUSCH transmissions have different lengths and different numbers of symbols are allowed for each of the at least one preceding DMRS, the transmitter, during operation, transmits the same number or fewer PUSCH transmissions such that the determined different DMRS port number is not used for any of the included at least one preceding DMRS.

[0297] According to a ninth aspect provided in addition to the eighth aspect, the processor is configured to use a maximum number of 2 symbols for each of the at least one forward-mounted DMRS so that during operation, a DMRS port with a number between 0 and 7 is used for a Type 1 configuration, or a DMRS port with a number between 0 and 11 is used for a Type 2 configuration.

[0298] According to a tenth aspect provided in addition to either the eighth or ninth aspect, the processor determines the DMRS port number to be used for each of the at least one forward-placed DMRS based on all different lengths of the plurality of PUSCH transmissions during operation.

[0299] According to an eleventh aspect, which is provided in addition to any of the eighth to tenth aspects, the processor further determines, based on the received index value during operation, the number of symbols to be used for each of the DMRSs placed before the at least one of the plurality of PUSCH transmissions; and if at least two of the plurality of PUSCH transmissions have different lengths and it is determined that different numbers of symbols are used for at least two of the plurality of PUSCH transmissions having different lengths, the processor, when determining the DMRS port number during operation, selects, for all of the plurality of PUSCH transmissions, the same DMRS port number that can be used for all of the at least one DMRS placed before it; and the transmitter transmits the same number of PUSCH transmissions such that the same DMRS port number is used with the different numbers of symbols for all of the at least one DMRS placed before it during operation.

[0300] According to a twelfth aspect provided in addition to the eleventh aspect, when the processor determines the DMRS port number during operation, it selects the DMRS port number such that, for all of the multiple PUSCH transmissions, fewer and more symbols are used for the at least one earlier placed DMRS and the same DMRS port number is used for the fewer and more symbols, and the same DMRS port number used for all of the at least one earlier placed DMRS is the same as the DMRS port number associated with the received index value.

[0301] According to a thirteenth aspect provided in addition to the twelfth aspect, when the processor determines the DMRS port number during operation, it omits from the plurality of PUSCH transmissions at least one PUSCH transmission that cannot include a larger number of symbols for each of the at least one forwardly placed DMRS and that cannot use the same DMRS port number as the DMRS port number associated with the received index value, and the transmitter transmits the fewer PUSCH transmissions such that the larger number of symbols and the same DMRS port are used for all of the at least one forwardly placed DMRS during operation.

[0302] According to a fourteenth aspect, a user equipment (UE) includes: a receiver that, during operation, receives a single uplink grant for multiple PUSCH transmissions, the single uplink grant including an antenna port field with an index value to be used for the multiple PUSCH transmissions; a processor that, during operation, determines time domain resources based on the received uplink grant, the determined time domain resources defining a number of PUSCH transmissions and a length of each of the multiple PUSCH transmissions; and a transmitter that, during operation, transmits the multiple PUSCH transmissions using the determined time domain resources, the transmitter transmitting the multiple PUSCH transmissions using the determined time domain resources. and a transmitter, each of the PUSCH transmissions including at least one forward-placed demodulation reference signal (DMRS), wherein, when a different number of symbols is allowed for each of the at least one forward-placed DMRS, the transmitter, during operation, transmits the same number of PUSCH transmissions for all of the at least one forward-placed DMRS such that fewer symbols are used according to a received index value, and does not transmit any of the PUSCH transmissions when, during operation, the received index value is associated with a larger number of symbols used for the at least one forward-placed DMRS.

[0303] According to a 15th aspect provided in addition to the 14th aspect, the processor is configured to use a maximum number of two symbols for each of the at least one preceding DMRS during operation, allowing the use of a smaller number of single-symbol DMRSs with one symbol or a larger number of double-symbol DMRSs with two symbols.

[0304] According to a sixteenth aspect, a base station (BS) includes: a processor that, during operation, determines time domain resources, the determined time domain resources defining a number of multiple PUSCH transmissions and a length of each of the multiple PUSCH transmissions; a transmitter that, during operation, transmits a single uplink grant based on the determined time domain resources for the multiple PUSCH transmissions, the single uplink grant including an antenna port field with an index value used for the multiple PUSCH transmissions; and a receiver that, during operation, receives the multiple PUSCH transmissions using the determined time domain resources, each of the multiple PUSCH transmissions including at least one pre-placed demodulation reference signal (DMRS), wherein the processor, during operation, determines the at least one PUSCH transmission included in the multiple PUSCH transmissions. a BS configured to determine a number of symbols to be used for each of one forwardly placed DMRS, the determined plurality of symbols being one of a fewer and a greater number of symbols, and if at least two of the plurality of PUSCH transmissions have different lengths and if one of the at least two of the plurality of PUSCH transmissions cannot include a greater number of symbols for each of the at least one forwardly placed DMRS, the processor determines the index value associated with the fewer symbols from the determined plurality of symbols to be used for each of the at least one forwardly placed DMRS included during operation, and the receiver receives the same or fewer PUSCH transmissions such that the determined different number of symbols is not used for any of the at least one forwardly placed DMRS included during operation.

[0305] According to a seventeenth aspect, a base station (BS) includes: a processor that determines, during operation, time domain resources, wherein the determined time domain resources define a number of multiple PUSCH transmissions and a length of each of the multiple PUSCH transmissions; a transmitter that transmits a single uplink grant based on the determined time domain resources for the multiple PUSCH transmissions, wherein the single uplink grant includes an antenna port field with an index value to be used for the multiple PUSCH transmissions; and a receiver that receives the multiple PUSCH transmissions using the determined time domain resources, wherein each of the multiple PUSCH transmissions includes at least one forward-mounted demodulation reference signal (DMRS), wherein the processor is configured to determine, during operation, the at least one forward-mounted demodulation reference signal (DMRS) included in the multiple PUSCH transmissions. and wherein the processor determines a number of symbols to be used for each of the included DMRSs, the determined number of symbols being one of a fewer number and a greater number of symbols, and in the case where at least two of the plurality of PUSCH transmissions have different lengths and different numbers of symbols are allowed for each of the at least one preceding DMRS, the processor determines during operation the index value associated with the greater number of symbols from the determined number of symbols and a DMRS port number where the same DMRS port number is also usable for the at least one preceding DMRS by the determined fewer symbols, and the receiver receives the same or fewer number of PUSCH transmissions such that the determined different DMRS port number is not utilized for any of the included at least one preceding DMRS during operation.

[0306] According to an eighteenth aspect, there is provided a base station (BS), the BS comprising: a processor that determines, during operation, time domain resources, the determined time domain resources defining a number of multiple PUSCH transmissions and a length of each of the multiple PUSCH transmissions; a transmitter that, during operation, transmits a single uplink grant based on the determined time domain resources for the multiple PUSCH transmissions, the single uplink grant including an antenna port field with an index value to be used for the multiple PUSCH transmissions; and a receiver that, during operation, receives the multiple PUSCH transmissions using the determined time domain resources, each of the multiple PUSCH transmissions including at least one forward-mounted Demodulation Reference Signal (DMRS), wherein if a different number of symbols is allowed for each of the at least one forward-mounted DMRS, the processor determines, during operation, the index value associated with the fewer symbols such that the same number of PUSCH transmissions including the at least one forward-mounted DMRS are received using fewer symbols.

Claims

1. An integrated circuit for controlling a base station (BS), comprising: a control circuit for determining a time domain resource, the determined time domain resource defining a number of PUSCH transmissions and a length of each of the PUSCH transmissions; a transmitter configured to transmit a single uplink grant based on the determined time domain resources for the multiple PUSCH transmissions, the single uplink grant including an antenna port field comprising an index value used for the multiple PUSCH transmissions; and a receiver circuit configured to receive the plurality of PUSCH transmissions using the determined time domain resources, each of the plurality of PUSCH transmissions including at least one pre-placed demodulation reference signal (DMRS); The control circuitry determines a number of symbols to be used for each of the at least one forward-placed DMRS included in the plurality of PUSCH transmissions, the determined number of symbols being one of a fewer number and a greater number of symbols; If at least two of the plurality of PUSCH transmissions have different lengths, and if one of the at least two of the plurality of PUSCH transmissions cannot include a larger number of symbols for each of the at least one forwardly placed DMRS, the processor determines the index value associated with a smaller number of symbols from the determined plurality of symbols to be used for each of the included at least one forwardly placed DMRS; the receiver circuit receives the same or fewer PUSCH transmissions such that the determined different number of symbols is not used for any of the included at least one forward-mounted DMRS. Integrated circuit.

2. An integrated circuit for controlling a base station (BS), comprising: a control circuit configured to determine a time domain resource, the determined time domain resource defining a number of PUSCH transmissions and a length of each of the PUSCH transmissions; a transmitter circuit configured to transmit a single uplink grant based on the determined time domain resources for the plurality of PUSCH transmissions, the single uplink grant including an antenna port field with an index value to be used for the plurality of PUSCH transmissions; a receiver configured to receive the plurality of PUSCH transmissions using the determined time domain resources, each of the plurality of PUSCH transmissions including at least one pre-placed demodulation reference signal (DMRS); The control circuitry, during operation, determines a number of symbols to be used for each of the at least one forward-placed DMRS included in the plurality of PUSCH transmissions, the determined number of symbols being one of a fewer number and a greater number of symbols; If at least two of the multiple PUSCH transmissions have different lengths and different numbers of symbols are allowed for each of the at least one forwardly placed DMRS, the processor determines during operation the index value associated with the larger number of symbols from the determined number of symbols and a DMRS port number where the same DMRS port number is usable for the at least one forwardly placed DMRS by the determined fewer symbols; the receiver circuit receives the same number or fewer PUSCH transmissions such that the determined different DMRS port number is not utilized for any of the included at least one forward-mounted DMRS. Integrated circuit.

3. An integrated circuit for controlling a base station (BS), comprising: a control circuit for determining a time domain resource, the determined time domain resource defining a number of PUSCH transmissions and a length of each of the PUSCH transmissions; a transmitter configured to transmit a single uplink grant based on the determined time domain resources for the plurality of PUSCH transmissions, the single uplink grant including an antenna port field comprising an index value used for the plurality of PUSCH transmissions; and a receiver circuit configured to receive the plurality of PUSCH transmissions using the determined time domain resources, each of the plurality of PUSCH transmissions including at least one pre-placed demodulation reference signal (DMRS); If a different number of symbols is allowed for each of the at least one forward-placed DMRS, the processor determines the index value associated with the fewer symbols such that the same number of PUSCH transmissions including the at least one forward-placed DMRS are received using the fewer symbols. Integrated circuit.

Images