RU2801706C2 - User equipment and system performing transmit and receive operations - Google Patents

Abstract

FIELD: means for receiving/transmitting data.

SUBSTANCE: physical uplink shared channel (PUSCH) configuration information element (IE) is received in the form of radio resource control (RRC) signals, wherein said PUSCH configuration information element (IE) is applicable to a specific part of the bandwidth. A table is configured which is specified by the PUSCH Time Domain Resource Assignment List Information Element (IE) carried in the received PUSCH Configuration Information Element (IE), said table containing rows each containing a value indicating a PUSCH mapping type, a value of K₂, indicating the slot offset, and an SLIV value indicating the start and length indicator. Downlink control information (DCI) signals are received, carrying a resource assignment field in the time domain having a value of m, wherein said value of m provides an m+1 row index for a table configured by radio resource control (RRC). The assigned resources for the initial PUSCH transmission and the assigned resources for at least one repetition thereof are determined. The PUSCH transmission is performed using respectively determined assigned resources for the initial PUSCH transmission and for the specified at least one repetition thereof.

EFFECT: increased flexibility in supporting transport block repetitions without additional waste of signal resources.

17 cl, 4 tbl, 8 ex, 23 dwg

Description

State of the art

1. Technical field

The present invention relates to the transmission and reception of signals in a communication system. In particular, the present invention relates to methods and apparatus for such transmission and reception.

2. Description of the prior art

The 3rd Generation Partnership Project (3GPP consortium) is working on technical specifications for a next generation cellular technology called fifth generation (5G) that includes “New Radio” (NR) radio access technology (RAT) that operates in frequency bands up to 100 GHz .

The NR system is a technology successor represented by Long Term Evolution (LTE) and Advanced Long Term Evolution (LTE-A) technologies. The NR system aims to facilitate the provision of a single technical framework covering several specific use cases, requirements, and deployment scenarios, including e.g. Evolved Mobile Broadband (eMBB), Ultra Reliable Low Latency Communications (URLLC), Mass Machine Type Communications (mMTC), etc. .P.

For example, advanced mobile broadband (eMBB) deployment scenarios may include indoor, dense urban, rural, large-scale urban, and high-speed communications; Ultra Reliable Low Latency Communication (URLLC) deployment scenarios may include industrial control systems, m-health (remote monitoring, diagnosis and treatment), real-time vehicle control, global monitoring and control systems for smart grids; Machine Type Mass Communication (mMTC) may include scenarios with a large number of devices with non-time critical data transmission, such as smart wearable devices and sensor networks.

The eMBB and URLLC services are similar in that they both require very high bandwidth, but differ in that the URLLC service requires ultra-low latency and very high reliability. In an NR system, the physical layer is based on time-frequency resources (such as orthogonal frequency division multiplexing (OFDM) as in the LTE standard) and can support multiple antennas.

For systems like those of the LTE and NR standard, additional enhancements and options may contribute to the efficient operation of the communication system, as well as specific devices related to said system.

DISCLOSURE OF THE INVENTION

One non-limiting and exemplary embodiment of the present invention facilitates increased flexibility in supporting transport block repetitions without additional overhead of signaling resources.

In one embodiment, the methods disclosed herein characterize a UE, including: a receiver, a processor, and a transmitter. The receiver in operation receives a Physical Uplink Shared Channel (PUSCH) Configuration Information Element (IE) in the form of Radio Resource Control (RRC) signals, wherein said PUSCH Configuration Information Element (IE) is applicable to a particular portion of the bandwidth.

The processor, during operation, configures a table which is specified by the PUSCH time-domain resource assignment list information element (IE) carried in the received PUSCH configuration information element (IE), said table containing rows each containing a value indicating the PUSCH mapping type. , a K ₂ value indicating the slot offsets, and an SLIV value indicating the start and length indicator.

The receiver, during operation, receives downlink control information (DCI) in the form of medium access control (MAC) signals carrying a time domain resource assignment field having a value of m, where the value of m provides an m+1 row index for a table configured by Radio Resource Control (RRC).

The processor during operation determines the assigned resources for the initial PUSCH transmission and the assigned resources for at least one repetition thereof based on: a slot number carrying the received downlink control information (DCI); a value of K ₂ indicating slot offsets; and a value of SLIV indicating a start and length indicator contained in an indexed row of a table configured by radio resource control (RRC);

And the transmitter, during operation, performs the PUSCH transmission using respectively determined assigned resources for the initial PUSCH transmission and at least one repetition thereof; wherein the determination of the assigned resources is based on at least one additional value contained in an indexed row of a table configured by Radio Resource Control (RRC) that determines the assigned resources in the time domain for at least one repetition of the initial PUSCH transmission.

It should be noted that general or specific embodiments may be implemented as a system, method, integrated circuit, computer program, storage medium, or any selective combination of the above.

Additional advantages and disadvantages of the disclosed embodiments will become apparent from the description and accompanying drawings. Benefits and/or advantages may be selectively obtained by implementing the various embodiments and features described herein and shown in the accompanying drawings, which need not all be provided in order to obtain one or more of such benefits and/or advantages.

BRIEF DESCRIPTION OF THE DRAWINGS

The following implementation examples are described in more detail with reference to the attached diagrams and accompanying drawings.

FIG. 1 schematically shows the architecture of an exemplary 3GPP NR system;

FIG. 2 shows an exemplary user and control plane architecture for an LTE eNB, a New Radio (NR) gNB, and a user equipment (UE);

FIG. 3 is a schematic diagram showing use cases for mass machine type communication (mMTC) and ultra-reliable low latency communication (URLLC);

On FIG. 4 shows a communication system in an NR system including a user equipment (UE) and a base station (BS) according to an exemplary scenario;

FIG. 5-6 are block diagrams of an exemplary implementation of a user equipment (UE) and a base station (BS);

FIG. 7 is a flowchart of user equipment performing PUSCH retries according to an exemplary mechanism;

FIG. 8-9 show a schematic illustration of a table configured by radio resource control (RRC) for PUSCH repetitions and corresponding time domain resource assignments according to the use of the first exemplary implementation; And

FIG. 10-11 is a schematic illustration of a radio resource control (RRC) configured table for PUSCH repetitions and corresponding time domain resource assignments according to another use of the first exemplary embodiment;

FIG. 12-13 is a schematic illustration of a radio resource control (RRC) configured table for PUSCH repetitions and corresponding time domain resource assignments according to another use of the first exemplary embodiment;

FIG. 14-15 show a schematic illustration of a table configured by radio resource control (RRC) for PUSCH repetitions and corresponding time domain resource assignments according to the use of the second exemplary embodiment;

FIG. 16-17 show a schematic illustration of a radio resource control (RRC) configured table for PUSCH repetitions and corresponding time domain resource assignments according to another use of the second exemplary embodiment;

FIG. 18-19 show a schematic illustration of a table configured by radio resource control (RRC) for PUSCH repetitions and corresponding time domain resource assignments according to the use of the third exemplary implementation;

FIG. 20-21 is a schematic illustration of a radio resource control (RRC) configured table for PUSCH repetitions and corresponding time domain resource assignments according to another use of the third exemplary embodiment; And

FIG. 22-23 show a schematic illustration of a radio resource control (RRC) configured table for PUSCH repetitions and corresponding time domain resource assignments according to the use of the fourth exemplary embodiment.

IMPLEMENTATION OF THE INVENTION

As described in the Background section, the 3GPP consortium is working on the next release of the 5th generation cellular technology, simply called 5G, which includes the development of New Radio (NR) access technology operating at frequencies up to 100 GHz. The 3GPP consortium must identify and develop the technological components needed to successfully standardize an NR system that meets both immediate market needs and longer-term requirements in a timely manner. To achieve this goal, in the item of the study "Access Technology New Radio", the development of the radio interface, as well as the architecture of the radio network, is considered. The results and agreements are collected in Technical Report TR38.804 v14.0.0, incorporated herein in its entirety by reference.

Among other things, a preliminary agreement was reached on the overall architecture of the system. The NG-RAN (Next Generation - Radio Access Network, next generation - radio access network) network consists of gNB stations providing the NG radio access user plane, i.e. SDAP/PDCP/RLC/MAC/PHY (Service Data Adaptation Protocol, SDAP)/Packet Data Convergence Protocol (PDCP)/Radio Link Control (RLC)/control protocol media access (Medium Access Control, MAC)/physical layer protocol (Physical Layer, PHY)), and the control plane, ie. terminating the Radio Resource Control (RRC) protocol towards the UE. FIG. 1 shows the NG-RAN network architecture based on TS 38.300 v.15.0.0, Section 4, which is incorporated herein by reference. gNB stations are interconnected via the Xn interface. gNB stations are also connected via a Next Generation (NG) interface to a Next Generation Core (NGC), more specifically, to an Access and Mobility Management Function (AMF) (e.g., a specific core object executing the AMF) via the NG-C interface and to a User Plane Function (UPF) (eg, a specific kernel object executing the UPF) via the NG-U interface.

Various supported deployment scenarios are currently being discussed, as reflected, for example, in the 3GPP specification TR38.801 v14.0.0 "Access Technology Study New Radio: Radio Access Architecture and Interfaces". in TR 38.801; the centralized application is illustrated in section 5.4, incorporated herein by reference), in which base stations supporting the 5G NR system can be applied.FIG. 2 shows an exemplary non-centralized application scenario based on FIG.5.2. -1 of said technical report TR 38.801, while further illustrating the LTE eNB as well as the user equipment (UE) that is connected to both the gNB and the LTE eNB. A 5G NR may be referred to as a gNB station as an example.

Also as noted above, the 3rd Generation Partnership New Radio Project (3GPP NR) considers three use cases envisaged to support a wide range of services and applications using the IMT-2020 specification (see Recommendation ITU-R M.2083: IMT concept - "Infrastructure and common goals for the future development of IMT for 2020 and beyond", September 2015). The specification for Evolved Mobile Broadband (eMBB) Phase 1 was finalized by the 3GPP consortium in December 2017. In addition to further expanding support for eMBB Advanced Mobile Broadband, current and future work may include the standardization of ultra-reliable low latency communications (URLLC) and machine-type mass communications. FIG. 3 (from Recommendation ITU-R M.2083) shows some examples of intended use cases for the IMT specification up to 2020 and beyond.

The use case of Ultra Reliable Low Latency Communication (URLLC) places stringent requirements on characteristics such as throughput, latency, and availability, and has been conceived as one of the enabling factors for the development of future vertical applications such as wireless control of industrial production or manufacturing processes, remote medical surgery, smart grid distribution automation, transportation security, etc. The current work item description (WID) RP-172115 agreed to maintain the ultra-reliability of the URLLC system by defining methods that meet the requirements established by TR 38.913. For the NR URLCC Release 15 network, the key requirements include a target user plane delay of 0.5 ms for UL (uplink) and 0.5 ms for DL (downlink). The general URLLC requirement for a single packet transmission is a block error rate (BLER) of 1E-5 for a packet size of 32 bytes with a user plane of 1 ms.

From the point of view of the RAN1 standard, reliability can be improved in various ways. The current area of reliability improvement is documented in RP-172817, which includes defining separate CQI tables for URLLC communication, more compact downlink control information (DCI) formats, PDCCH repetition, and the like. However, this area can be expanded to achieve ultra-reliability as the NR network becomes more stable and mature (key requirements for URLCC NR network see also 3GPP report TR 38.913 V15.0.0 "Scenarios and Requirements Study for Next Generation Access Technologies" ", incorporated herein by reference). Accordingly, the NR URLLC network according to version 15 must be able to transmit 32 bytes of data packet with a user plane delay of 1 ms with a success probability that corresponds to the BLER 1E-5 block error rate. Special Use Cases for the NR URLCC Network Vol. 15 include augmented reality/virtual reality (AR/VR), e-health, e-security and mission-critical applications (see also Recommendation ITU-R M.2083-0).

Moreover, technology enhancements targeting the NR URLCC Release 15 network aim to improve latency and improve reliability. Technology enhancements to improve latency include configurable numerology, slot-less scheduling with flexible mapping ratio, resolutionless uplink (with configurable resolution), slot-level repetition for data channels, and downlink preemption. Preemption means that a transmission for which resources have already been assigned is stopped, and the resources already assigned are used for another transmission that was requested later but has a lower latency/higher priority requirement. Accordingly, an already authorized transmission is interrupted by a later transmission. Preemption preemption applies regardless of the specific type of service. For example, a transmission for service type A (URLCC) may be interrupted by a transmission for service type B (eg, eMBB). Reliability technology enhancements include dedicated CQI/MCS tables for target BLER 1E-5 block error rate (for technology enhancements, see also 3GPP TS 38.211 “NR; Physical Channels and Modulation”, TS 38.212 “NR; Multiplexing and channel coding", TS 38.213 "NR; Physical layer procedures for control" and TS 38.214 "NR; Physical layer procedures for data", corresponding to versions V15.4.0, all of which are incorporated herein by reference).

The mass machine-type communication (mMTC) use case is characterized by a very large number of connected devices, usually transmitting a relatively small amount of latency-insensitive data. Devices must be inexpensive and must have very long battery life. From the point of view of the NR network, the use of parts with a very narrow bandwidth is one of the possible solutions to save power from the point of view of the UE and provide a long battery life.

As stated above, the scope of reliability in the NR network is expected to become wider. One of the key requirements in all cases, especially for URLLC and mMTC communication, is high reliability or ultra-reliability. Several reliability mechanisms can be considered from a radio and network point of view. Overall, there are several key potential areas that can help improve reliability. These areas include compact control channel information, data/control channel repetition, and frequency, time, and/or space diversity. These areas apply to reliability in general, regardless of specific communication scenarios.

For Network NR Communications URLLC Rel. 16, additional use cases with more stringent requirements have been defined, such as factory automation, transportation, and power distribution, including factory automation, transportation, and power distribution (see RP-181477, "New SID for Physical Layer Enhancements for NR URLLC" , Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, incorporated herein by reference). More stringent requirements are higher reliability (up to level 10-6), higher availability, packet sizes up to 256 bytes, time synchronization up to several µs, where the value can be one or more µs depending on the frequency range, and a short delay of the order of 0 .5-1ms, specifically target user plane delay of 0.5ms depending on use cases (see also 3GPP TS 22.261 Service Requirements for New Services and Next Generation Markets V16.4.0 incorporated herein by reference and document RP-181477).

Moreover, for the URLCC NR network in Rel. 16, several technology enhancements have been identified in terms of the RAN1 standard. Among them are Physical Downlink Control Channel (PDCCH) improvements related to compact DCI information, PDCCH repetition, enhanced PDCCH monitoring. In addition, Uplink Control Information (UCI) enhancements are associated with Advanced Hybrid Automatic Repeat Request (HARQ) and CSI feedback enhancements. PUSCH enhancements related to mini-slot level hopping and relay/repeating enhancements have also been identified. The term "mini-slot" refers to a Transmission Time Interval (TTI) containing fewer symbols than a slot (a slot contains fourteen symbols).

In general, the TTI defines the timing granularity for the scheduling assignment. One TTI is a time interval in which these signals are mapped to the physical layer. Typically, the length of the TTI may vary from 14 symbols (slot based scheduling) to 2 symbols (slotless scheduling). Downlink and uplink transmissions shall be organized into frames (10 ms long) consisting of 10 subframes (1 ms long). When transmitting based on slots, the subframe is in turn divided into slots, the number of slots being given by numerology/subcarrier spacing, and these values are in the range of 10 slots for a subcarrier spacing of 15 kHz to 320 slots for a subcarrier spacing of 240 kHz. The number of OFDM symbols per slot is 14 for normal cyclic prefix and 12 for extended cyclic prefix (see Sections 4.1 (general frame structure), 4.2 (numerology), 4.3.1 (frames and subframes) and 4.3.2 (slots) of the technical the 3GPP TS 38.211 V15.4.0 specification, incorporated herein by reference). However, the assignment of temporary resources for transmission may also be non-slot based. In particular, TTIs in a non-slot based assignment may correspond to minislots rather than slots. For example, one or more minislots may be assigned for the requested data/control signaling. For non-slot-based assignments, the minimum TTI length can typically be 2 Orthogonal Frequency-Division Multiplex (OFDM) symbols.

Other identified improvements relate to scheduling/Hybrid Automatic Repeat Request (HARQ)/Channel State Information (CSI) and prioritization/multiplexing of UL Tx transmissions between UEs. In addition, configurable grant (no grant) UL uplink transmissions are presented, with a focus on improved configurable grant performance, as well as exemplary techniques such as explicitly defined Hybrid Automatic Request-ACKnowledgement, HARQ-ACK) providing K repetitions and mini-slot repetitions per slot, and other enhancements related to Multiple Input Multiple Output (MIMO) techniques (see also 3GPP Technical Specification TS 22.261 V16.4.0).

This disclosure relates to potential layer 1 enhancements to further improve reliability/reduce latency, as well as other requirements related to the use cases identified in the document (RP-181477, New SID for Physical Layer Enhancements for NR URLLC Network, Huawei, HiSilicon , Nokia, Nokia Shanghai Bell). In particular, improvements are discussed for repeating a common physical uplink channel (Physical Uplink Shared CHannel, PUSCH). It is expected that the ideas proposed in this disclosure will have an impact on the PUSCH repetition enhancements that lie at the core of the new study items (SI)/work items (WI) in the NR URLLC Vol. 16.

Repeat PUSCH

One area for potential improvements relates to repeating a PUSCH mini-slot in a slot. The following is the motivation for supporting in-slot PUSCH repetition, which may provide potential enhancements to the repetition mechanism to further improve reliability and/or reduce latency to meet the new requirements of the NR URLLC network.

To achieve the delay requirement for the PUSCH transmission of the URLLC link, a one-time transmission (ie, a single (TTI) assignment) is ideally suited, provided that the reliability requirement is satisfied. However, with a single transmission, the target error rate for BLER 1E-6 blocks is not always achieved. Therefore, relay or repetition mechanisms are required.

Online NR Vol. 15, both relays and repetitions are supported to achieve the target BLER error rate when a single transmission is not enough. It is well known that HARQ-based relaying improves overall reliability by utilizing feedback information and improving subsequent relays according to channel conditions. However, this is hampered by additional delay due to the feedback processing schedule. Therefore, retries are useful for services with high latency tolerance because they perform subsequent transmissions of the same transport blocks without waiting for any feedback.

PUSCH repetition may be defined as "transmitting the same transport block more than once without waiting for any feedback related to previous transmission(s) of the same transport block". PUSCH relays have the advantage of improving overall reliability and reducing latency compared to HARQ, since no feedback is required in this case. However, in general, link adaptation is not possible, and resource use may be inefficient.

Online NR Vol. 15 introduced limited support for replays. Only semi-static retry configurations are allowed. Moreover, retries are only allowed between slots (repetition of PUSCH at the slot level). Repetition is possible only in the slot following the slot of the previous transmission. Depending on the numerology and type of service (eg URLCC, eMBB), the delay between repetitions may be too long for repetition between slots.

This limited repetition support is mainly useful for creating a type A PUSCH mapping relationship. This PUSCH mapping type A only allows PUSCH transmissions starting from the beginning of a slot. With repetitions, this may result in an initial PUSCH transmission, with each repetition occurring at the beginning of a plurality of consecutive slots.

Less useful is the limited repetition support for type B PUSCH mapping. PUSCH mapping type B allows PUSCH transmissions to start on any symbol in the slot. With repetitions, this may result in an initial PUSCH transmission, with each repetition starting in a slot with the same symbol in multiple consecutive slots.

In any case, such limited support may not be possible to achieve compliance with the more stringent network delay requirements of NR Rel. 15, i.e. with a delay of up to 0.5 ms. This will require repetitions of mini-slots. In addition, limited repetition support also does not take advantage of minislots, namely the transmission of time intervals (TTIs) comprising fewer symbols than one slot (a slot containing fourteen symbols).

General Scenario for Uplink

In view of the foregoing, it is clear from the present disclosure that there is a need for more flexible support for repetitions, namely a mechanism that is not limited to repetitions that start with the same character in consecutive slots, be it the first character at the beginning of the slot to display PUSCH type A, or be it any other character in the slot to display PUSCH type B.

At the same time, greater flexibility should not be achieved at the expense of additional overhead of signaling resources. In other words, it is clear from the present disclosure that flexible repetition support does not require additional (dynamic) signal scheduling for each initial PUSCH transmission. In other words, the signaling mechanism, for example in the form of downlink control information (DCI), should remain unchanged, thus avoiding any additional overhead of signaling resources in repetition scheduling.

Therefore, the proposal of the present disclosure is that transport block (TB) repetitions should be supported with flexible timing that does not necessarily introduce additional signaling resource overhead. The following disclosure is presented with a focus on uplink transmissions. However, this should not be considered as a limitation since the concepts disclosed in this document may equally apply to downlink transmissions.

FIG. 4 shows 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 consortium system such as an NR and/or LTE system and/or a Universal Mobile Telecommunications System (UMTS). For example, as shown in the drawing, the base station (BS) may be a gNB base station (gNodeB, for example, i.e. gNB base station of NR system) or an eNB base station (eNodeB, for example, i.e. LTE gNB station) . However, the present invention is not limited to these 3GPP systems or any other systems.

Even though the embodiments and exemplary embodiments are described using some of the 3GPP systems terms, the present invention is also applicable to any other communication systems, and in particular to any cellular, wireless and/or mobile systems.

Rather, it should be noted that many assumptions have been made herein in order to be able to explain in a clear and understandable manner the principles underlying the present disclosure. However, these assumptions should be understood only as examples for purposes of illustration, which should not limit the scope of the present invention. One skilled in the art will appreciate that the principles of the following description and the principles set forth in the appended claims may be applied to various scenarios and in ways not expressly described herein.

The mobile terminal in LTE and NR networks is called user equipment (user equipment, UE). It may be a mobile device such as a cordless phone, smartphone, tablet, or USB stick with user equipment functionality. However, the term "mobile device" is not limited to this, and, in general, a repeater may also have the functionality of such a mobile device, and the mobile device may also operate as a repeater.

The base station (BS) forms at least part of a system of interconnected units, for example, a baseband (central) unit and various RF units interacting with various antenna panels or radio heads in said network to provide services to terminal devices. In other words, the base station provides wireless access to terminal devices.

As shown in the figure, the user equipment 410 includes a processing circuit (or processor) 430 and a transmitter/receiver (or transceiver) 420, which are indicated in the diagram as separate building blocks. Similarly, base station 460 includes processing circuitry (or processor) 480 and transmitter/receiver (or transceiver) 470, which are labeled as separate building blocks in the diagram. The transmitter/receiver 420 of the user equipment 410 is in communication via a radio link 450 with the transmitter/receiver 470 of the base station 460.

FIG. 5 and 6 depict exemplary implementations of the building blocks of user equipment 410 and base station 460, respectively. The user equipment 410 according to the exemplary embodiment comprises a PUSCH configuration information element (IE) receiver 520-a, a processing circuit 530-a, a configuration table, a downlink control information (DCI) receiver 520-b, a information element receiver 520-c ( IE) a configurable grant configuration, a processing circuit 530-b that determines the assigned resources, and a PUSCH transmitter 520-d.

Similarly, the exemplary base station 460 comprises: a PUSCH configuration information element (IE) transmitter 570-a; a processing circuit 580-a configuring a table; a DCI control information transmitter 570-b; a configurable permission configuration information element (IE) transmitter 570-c; a processing circuit 580-b assigning resources; and a 570-d PUSCH receiver.

In general, the present disclosure assumes that user equipment 410 is in range of base station 460 and is configured with at least one downlink bandwidth fraction and at least one uplink bandwidth fraction. Parts of the bandwidth are located in the bandwidth of the carrier served by the base station 460.

In addition, the present disclosure assumes that the user equipment 410 operates in a radio resource control (RRC) connected state (denoted as: RRC_CONNECTED), whereby it is able to receive data and/or control signals on the downlink from the base station 460 and is able to transmit data and/ or control signals on the uplink of the base station 460.

Before performing PUSCH retries as proposed in the present disclosure, user equipment 410 receives control messages as specified in the radio resource control (RRC) and medium access control (MAC) protocol layer. In other words, the user equipment 410 uses a signaling mechanism that is readily available in various protocol layers of various communication technologies.

In general, there is a significant difference between control messages defined in Radio Resource Control (RRC) and messages defined in Media Access Control (MAC). This difference becomes apparent from the fact that Radio Resource Control (RRC) control messages are typically used to configure radio resources (eg, radio links) on a semi-static basis, while Media Access Control (MAC) control messages are used to dynamically determine each access to medium (eg transmission) individually. It directly follows that Radio Resource Control (RRC) occurs less frequently than Medium Access Control (MAC).

Accordingly, excessive overhead of the Medium Access Control (MAC) signaling resources can significantly reduce the performance of the communication system, while the Radio Resource Control (RRC) control message is handled more leniently by standardization. In other words, the media access control (MAC) signaling resource overhead is a well-known system performance limitation.

For this reason, traditional PUSCH repetition mechanisms are based on pre-specified (eg, hard-coded in the relevant standard) timing relationship between the initial PUSCH transmission and its repetitions. In other words, it has been found that the potential for system performance degradation outweighs the benefits of more flexible use of PUSCH repetitions.

In view of the foregoing, the present disclosure proposes a mechanism that overcomes the shortcomings of known mechanisms and permits flexible transport block (TB) repetitions while eliminating signal resource overhead.

In the context of the present invention, the term "transport block" should be understood as a data unit for transmission on the uplink and/or downlink. For example, the term "transport block" is widely understood as equivalent to the packaged data unit (PDU) of the medium access control (MAC) layer. Thus, transport block transmission is equally understood as transmission on a physical uplink shared channel (PUSCH) and/or a physical downlink shared channel (PDSCH).

In particular, since PUSCH and/or PDSCH transmissions typically carry a payload, the present disclosure should relate to PUSCH and/or PDSCH transmissions carrying a Medium Access Control Packet Data Unit (MAC PDU). In other words, the terms PUSCH and/or PDSCH transmissions should be understood to describe the transmission of a MAC PDU on the PUSCH and/or PDSCH.

Below with reference to FIG. 7 describes a general scenario related to performing PUSCH repetitions based on dynamic grant, namely, downlink control information (DCI) carrying a resource assignment field in the time domain, such as, for example, downlink control information (DCI) of DCI format 0-0 or DCI 0-1 format.

However, this description is not to be understood as a limitation of the present disclosure, which only applies to PUSCH transmissions, more specifically, repetitions thereof. Rather, it is clear that the concepts disclosed in this document can equally apply to downlink transmissions.

The receiver 420 of the user equipment 410 receives (see, for example, step 710 in FIG. 7) a physical uplink shared channel (PUSCH) configuration information element (IE). This PUSCH Configuration Information Element (IE) is received in the form of Radio Resource Control (RRC) signals and is applicable to a specific part of the bandwidth. A PUSCH configuration information element (IE) is received from a base station 460 serving a particular portion of the bandwidth. For example, this receive operation may be performed by the PUSCH configuration information element (IE) receiver 520-a shown in FIG. 5.

The PUSCH configuration information element (IE) carries, among other things, a parameter list in the form of an information element (IE) referred to as "PUSCH TimeDomain ResourceAllocationList Resource Assignment List", each parameter of said parameter list being referred to as a "Time Domain Resource AllocationList". PUSCH Domains" ("PUSCH-TimeDomainResourceAllocation").

Next, the processor 430 of the user equipment 410 configures (see, for example, step 720 in FIG. 7) the table that is specified by the PUSCH Time Domain Resource Assignment List Information Element (IE) carried in the received PUSCH Configuration Information Element (IE). The table contains rows, each containing a value indicating a PUSCH mapping type, a K ₂ value indicating slot offsets, and an SLIV value indicating a start and length indicator. For example, this configuration operation may be performed by the table configuration processing circuit 520-a shown in FIG. 5.

In the exemplary implementation, each row of a table configured by Radio Resource Control (RRC) corresponds to one of a plurality of parameters called "PUSCH Time Domain Resource Allocation" from a list of parameters called "Time Domain Resource Assignment List". PUSCH" ("PUSCH-TimeDomainResourceAllocationList"). However, this should not be understood as a limitation of the present disclosure, as will be apparent from the following alternative.

Scenarios are also possible that differ from the exemplary implementation, namely that some rows of the configured table correspond to the corresponding parameters contained in the parameter list information element (IE), while other rows are configured according to a set of pre-specified rules, easily applying the principles set forth in the PUSCH Time Domain Resource Assignment Information Element (IE).

However, this should not detract from the fact that the table configured by the radio resource control (RRC) is completely specified by the resource assignment list information element (IE) in the PUSCH time domain.

The receiver 420 of the user equipment 410 then receives (see, for example, step 730 in FIG. 7) the downlink control (DCI) information in the form of medium access control (MAC) signals. The downlink control information (DCI) carries a resource assignment field in the time domain with a value of m, where the value of m provides an m+1 row index for the configurable table. For example, this receiving operation may be performed by the downlink control information (DCI) receiver 520-b shown in FIG. 5.

In the context of the present disclosure, this downlink control information (DCI) carries an uplink grant as it serves the purpose of triggering PUSCH retries. In this regard, the received downlink control information (DCI) is represented in DCI format 0-0 or DCI format 0-1. In this regard, the described scenario refers to a situation where PUSCH repetitions are scheduled through dynamic resolution.

However, this should not be understood as a limitation of the present disclosure, as the concepts disclosed herein are equally applicable to configurable grant or non-grant scheduling techniques. A detailed description of this unauthorized scheduling method is provided as an alternative to the mechanism shown in FIG. 7.

The processor 430 of the user equipment 410 then determines the assigned resources for the initial PUSCH transmission as well as the assigned resources for at least one repetition of the initial PUSCH transmission. For clarity and brevity, the following description focuses on resource assignment in the time domain. For example, this determination operation may be performed by the assigned resource determination processing circuit 530-b shown in FIG. 5.

The resources to be used by the user equipment 410 for the initial PUSCH transmission and its repetition(s) have been previously assigned by the base station 460. In this context, the processor 430 accordingly determines which of the previously assigned resources it should use for the PUSCH transmission and its repetition(s). ).

As part of this determination operation, processor 430 first determines (see, for example, step 740 shown in FIG. 7) assigned resources for the initial PUSCH transmission based on: (i) the slot number carrying the received downlink control information (DCI); (ii) a value of K ₂ indicating slot offsets; and (iii) an SLIV value indicating a start and length indicator contained in an indexed row of a table configured by radio resource control (RRC). This implies that processor 430 has predetermined that the value indicating the PUSCH mapping type indicates mapping type B.

For example, it may be assumed that the received downlink control information (DCI) was carried in the slot numbered k, and furthermore, said downlink control information (DCI) has a resource assignment field in the time domain filled with the value m. The processor for initial PUSCH transmission then accesses the row at index m+1 in the table configured by radio resource control (RRC) and uses the corresponding K ₂ values indicating slot offsets and SLIV values indicating start indicator and length. With this value, the processor determines that the allocated resources for the initial PUSCH transmission are included in slot number k+K ₂ and have a start and length in that slot's symbol expression corresponding to the value of SLIV.

When determining the assigned resources, the processor 430 also uses a value indicating the PUSCH mapping type further contained in the row of the table configured by radio resource control (RRC) at row index m+1. In particular, in the case where the specified value indicates a type A PUSCH mapping, the processor 430 uses only the length specified by the SLIV value indicating the start indicator and the length. In the case where the specified value indicates a type B PUSCH mapping, processor 430 uses both the start and the length determined by the value SLIV indicating the start and length indicator.

Then, as part of this determination operation, processor 430 determines the assigned resources for at least one repetition of the initial PUSCH transmission. To do this, processor 430 checks (see, for example, step 750 in FIG. 7) whether there is an (explicit) assignment of time domain resources associated with parameters (eg, timing) to repeat. To do this, processor 430 returns to row index m+1 and checks if that row contains additional values (eg, at least one value) that define an assigned resource in the time domain for at least one repetition of the initial PUSCH transmission.

In the case of a negative test result, processor 430 uses (see, for example, step 760 of FIG. 7) a conventional slot-based repetition mechanism to repeat the initial PUSCH transmission. In other words, processor 430 uses predefined (eg, hardcoded in the relevant standard) timing relationships between the initial PUSCH transmission and its repetitions. For example, this causes the initial PUSCH transmission and each repetition to start with the same symbol and have the same length in symbols of multiple consecutive slots.

Returning to the above example, the processor 430 at least one repetition accesses the row with index m+1 of the row of the table configured by radio resource control (RRC), and determines that the assigned resources for the first repetition of the initial PUSCH transmission are included in slot number k+ K ₂ +1 (where 1 is a predefined constant given by standardization) and have a start and length in character units of that slot corresponding to the same value of the SLIV indicator.

In the case of the second repetition, the processor 430 determines that the assigned resources for the second repetition of the initial PUSCH transmission are included in slot number k+K ₂ +2 (where 2 is again a predefined constant that is specified by standardization) and have the start and length in symbols of this slots corresponding to the same SLIV indicator value as for the original PUSCH transmission and its first repetition. Further repetitions follow in adjacent slots.

In addition to this example, assuming that the PUSCH mapping type indicated in row index m+1 is type B, and assuming that the value of the SLIV indicator indicates starting at symbol 4 and 4 symbols long, processor 430 determines, that each of the initial, first, and second PUSCH retransmissions has resources corresponding to symbol 4, symbol 5, symbol 6, and symbol 7 in slots k+K ₂ , k+K ₂ +1 , k+K ₂ + 2 respectively.

Obviously, these assigned resources defined by the processor 430 cannot be flexibly configured. This is overcome by alternative determination by processor 430.

If the check is positive, processor 430 uses (see, for example, step 770 in FIG. 7) additional values (eg, at least one value) contained in an indexed row of a table configured by radio resource control (RRC) to determine the assigned resources. to repeat the initial PUSCH transmission. In other words, the at least one additional value contained defines an assigned resource in the time domain for repeating the initial PUSCH transmission.

In this context, it should be emphasized that at least one additional value is contained in a table row configured by radio resource control (RRC), which is specified by the resource assignment list information element (IE) in the PUSCH time domain. In other words, since the (entire) table configured by Radio Resource Control (RRC) is specified by the Time Domain Resource Assignment List Information Element (IE) PUSCH, also at least one additional value contained therein is specified by the Assignment List Information Element (IE). time domain resources PUSCH.

To satisfy these constraints, at least one additional value may be (directly) prescribed by a parameter contained in the Time Domain Resource Assignment List Information Element (IE) PUSCH, or alternatively, at least one additional value may be (indirectly) derived from the corresponding parameters. contained in the resource assignment list information element (IE) in the PUSCH time domain. In either case, the at least one additional value indicates, in the time domain, a repetition of the initial PUSCH transmission.

It is important to understand that the processor 430 of the user equipment 410 uses additional values from the indexed row of the table configured by radio resource control (RRC) to determine the assigned resources for the specified repetitions. This approach differs significantly from the traditional slot-based recurrence mechanism for the following reasons:

First, at least one additional value is taken from a table row configured by Radio Resource Control (RRC) that is (actively) indexed by row index m+1 derived from the value m in the resource assignment field in the time domain in the received downlink control information (DCI). In this regard, changing index values m in the time domain resource assignment field of the received downlink control information (DCI) allow at least one of the additional values to be used to determine the assigned time domain resources for at least one repetition of the initial PUSCH transmission. This increases the flexibility of such allocated resources.

Second, at least one additional value is taken from the (same) row of the table configured by radio resource control (RRC) that is (already) indexed by row index m+1 derived from the value m in the resource assignment field in the time domain in the received downlink control information (DCI). In this regard, no additional index value is required other than the index value m in the resource assignment field in the time domain of the received downlink control information (DCI) when determining the assigned resources to perform at least one repetition of the initial PUSCH transmission. Thus, any additional overhead of signaling resources is eliminated.

Therefore, this allows increased flexibility while avoiding the overhead of signaling resources, namely by the processor 430 of the user equipment 410 using at least one additional value from an indexed row of a table configured by radio resource control (RRC) to determine the assigned resources for the specified repetitions. .

Finally, the transmitter 420 of the user equipment 410 performs (not shown in FIG. 7) a PUSCH transmission using appropriately assigned resources for the initial PUSCH transmission and at least one repetition thereof. For example, this transmission operation may be performed by the PUSCH transmitter 520-d shown in FIG. 5.

The above description has been made in terms of user equipment 410. However, this should not be understood as limiting the present invention. Base station 460 also runs the general scenario disclosed herein.

The transmitter 470 of the base station 460 transmits a Physical Uplink Shared Channel (PUSCH) Configuration Information Element (IE) in the form of Radio Resource Control (RRC) signals. The PUSCH Configuration Information Element (IE) is applicable to a specific portion of the bandwidth. For example, this transmission operation may be performed by transmitter 670-a transmitting a PUSCH configuration information element (IE) as shown in FIG. 6.

Next, the processor 480 of the base station 460 configures a table that is specified by the PUSCH Time Domain Resource Assignment List Information Element (IE) carried in the received PUSCH Configuration Information Element (IE). The table configured by Radio Resource Control (RRC) contains rows, each of which contains: a value indicating the PUSCH mapping type; a K ₂ value indicating slot offsets; and an SLIV value indicating the start and length indicator. For example, this configuration operation may be performed by the table configuration processing circuit 680-a shown in FIG. 6.

The transmitter 470 of the base station 460 then transmits the downlink control (DCI) information in the form of medium access control (MAC) signals carrying a time domain resource assignment field having a value of m, where the value of m provides an index of m+1 rows into the table configured by Radio Resource Control (RRC). For example, this transmission operation may be performed by the downlink control information (DCI) transmitter 670-b shown in FIG. 6.

The processor 480 of the base station 460 allocates resources for the initial PUSCH transmission and allocates resources for at least one repetition thereof based on: (i) a slot number carrying the transmitted downlink control information (DCI); (ii) a value of K ₂ indicating slot offsets; and (iii) an SLIV value indicating a start and length indicator contained in an indexed row of a table configured by radio resource control (RRC).

In particular, the determination of the assigned resources is based on at least one additional value contained in an indexed row of a table configured by Radio Resource Control (RRC) that determines the assigned resources in the time domain for at least one repetition of the initial PUSCH transmission. For example, this resource assignment operation may be performed by the resource assignment processing circuit 680-b shown in FIG. 6.

Finally, the receiver 470 of the base station 460 receives the PUSCH transmission using the appropriately assigned resources for the initial PUSCH transmission and at least one repetition thereof. For example, this receive operation may be performed by the PUSCH receiver 670-d shown in FIG. 6.

The following describes a general scenario related to performing PUSCH retries based on a configurable grant (or no grant), namely a configurable grant configuration information element (IE) received as radio resource control (RRC) signals, also containing an information element (IE) resource assignment list in the PUSCH time domain.

The receiver 420 of the user equipment 410 receives a physical uplink shared channel (PUSCH) configuration information element (IE) in the form of radio resource control (RRC) signals. The PUSCH Configuration Information Element (IE) is applicable to a specific portion of the bandwidth. A PUSCH configuration information element (IE) is received from a base station 460 serving a particular portion of the bandwidth. For example, said receive operation may be performed by the PUSCH configuration information element (IE) receiver 520-a shown in FIG. 5.

Next, the processor 430 of the user equipment 410 configures a table that is specified by the PUSCH Time Domain Resource Assignment List Information Element (IE) carried in the received PUSCH Configuration Information Element (IE). The table configured by Radio Resource Control (RRC) contains rows, each of which contains: a value indicating the PUSCH mapping type; a K ₂ value indicating slot offsets; and an SLIV value indicating the start and length indicator. For example, this configuration operation may be performed by the table configuration processing circuit 530-a shown in FIG. 5.

The receiver 420 of the user equipment 410 then receives a configurable grant configuration information element (IE) in the form of radio resource control (RRC) signals carrying a time domain assignment field containing a value of m, where the specified value of m provides an m+1 row index for the configurable table. For example, this receiving operation may be performed by the Configurable Grant Configuration Information Element (IE) receiver 520-c shown in FIG. 5.

The processor 430 of the user equipment 410 determines the assigned resources for the initial PUSCH transmission and the assigned resources for at least one repetition thereof based on: (i) the value of the time domain offset field optionally carried in the received configurable grant configuration information element (IE) and associated with the appointments in the time domain; (ii) a value of K ₂ indicating slot offsets; and (iii) an SLIV value indicating a start and length indicator contained in an indexed row of a table configured by radio resource control (RRC).

In particular, the determination of the assigned resources is based on at least one additional value contained in an indexed row of a table configured by Radio Resource Control (RRC) that determines the assigned resources in the time domain for at least one repetition of the initial PUSCH transmission. For example, this determination operation may be performed by the processing circuit 530-b determining assigned resources.

Finally, the transmitter 420 of the user equipment 410 performs the PUSCH transmission using respectively determined assigned resources for the initial PUSCH transmission and at least one repetition thereof. For example, this transmission operation may be performed by the PUSCH transmitter 530-d shown in FIG. 5.

The above description has been made in terms of user equipment 410. However, this should not be understood as limiting the present invention. Base station 460 also runs the general scenario disclosed herein.

The transmitter 470 of the base station 460 transmits the Physical Uplink Shared Channel (PUSCH) Configuration Information Element (IE) in the form of Radio Resource Control (RRC) signals, the PUSCH Configuration Information Element (IE) applicable to a particular portion of the bandwidth. For example, this transmission operation may be performed by the PUSCH configuration information element (IE) transmitter 670-a shown in FIG. 6.

Next, the processor 480 of the base station 460 configures a table that is specified by the PUSCH Time Domain Resource Assignment List Information Element (IE) carried in the received PUSCH Configuration Information Element (IE). The table configured by Radio Resource Control (RRC) contains rows, each of which contains: a value indicating the PUSCH mapping type; a K ₂ value indicating slot offsets; and an SLIV value indicating the start and length indicator. For example, this configuration operation may be performed by the table configuration processing circuit 680-a shown in FIG. 6.

The transmitter 470 of the base station 460 then transmits a configurable grant configuration information element (IE) in the form of Radio Resource Control (RRC) signals carrying a time domain assignment field containing the value m, said m value providing an m+1 row index for the table configured radio resource control (RRC). For example, this transmission operation may be performed by the Configurable Grant Configuration Information Element (IE) transmitter 670-c shown in FIG. 6.

The processor 480 of the base station 460 allocates resources for the initial PUSCH transmission and allocates resources for at least one repetition thereof based on: (i) the value of the time domain offset field optionally carried in the received configurable grant configuration information element (IE) and associated with the assignment field in the time domain; (ii) a value of K ₂ indicating slot offsets; and (iii) an SLIV value indicating a start and length indicator contained in an indexed row of a table configured by radio resource control (RRC).

In particular, the determination of the assigned resources is based on at least one additional value contained in an indexed row of a table configured by Radio Resource Control (RRC) that determines the assigned resources in the time domain for at least one repetition of the initial PUSCH transmission. For example, this resource assignment operation may be performed by the resource assignment processing circuit 680-b shown in FIG. 6.

Finally, the receiver 470 of the base station 460 receives the PUSCH transmission using appropriately assigned resources for the initial PUSCH transmission and at least one repetition thereof. For example, this receive operation may be performed by the PUSCH receiver 670-d shown in FIG. 6.

General downlink scenario

As stated above, the present disclosure is not limited to uplink transport block (TB) repetitions, but can equally apply to downlink transmissions, namely to achieve flexible support for downlink repetitions. Also in this case, transport block (TB) repetitions with flexible timing parameters are supported, which do not create additional overhead of signaling resources.

In other words, the benefits of improved flexibility in transport block repetition scheduling are not only achievable for Physical Uplink Shared Channel (PUSCH) transmissions, but are equally achievable for Physical Downlink Shared Channel (PDSCH) transmissions. This follows directly from the high degree of similarity between the PUSCH Time Domain Resource Assignment List Information Element and the PDSCH Time Domain Resource Assignment List Information Element.

In addition, there is no additional overhead of signaling resources because the scheduling described below is based on the PDSCH time domain resource assignment field in the 1-0 or 1-1 downlink control information (DCI), which is very similar to the assignment field PUSCH time domain resources in Downlink Control Information (DCI) format 0-0 or 0-1 as described above.

Typically, the receiver 420 of the user equipment 410 receives a Physical Downlink Shared Channel (PDSCH) Configuration Information Element (IE) in the form of Radio Resource Control (RRC) signals. The PDSCH Configuration Information Element (IE) is applicable to the specific portion of the bandwidth that is served by the base station 460.

Next, the processor 430 of the user equipment 410 configures a table that is specified by the PDSCH Time Domain Resource Assignment List Information Element (IE) carried in the received PDSCH Configuration Information Element (IE). The table configured by Radio Resource Control (RRC) contains rows, each of which contains: a value indicating the PDSCH mapping type; a K ₂ value indicating slot offsets; and an SLIV value indicating the start and length indicator.

The receiver 420 of the user equipment 410 then receives the downlink control information (DCI) in the form of medium access control (MAC) signals carrying a time domain resource assignment field having a value of m, where the value of m provides an m+1 row index for the table, configured radio resource control (RRC).

The processor 430 of the user equipment 410 determines the assigned resources for the initial PDSCH transmission and the assigned resources for at least one repetition thereof based on: (i) a slot number carrying the received downlink control information (DCI); (ii) a value of K ₂ indicating slot offsets; and (iii) an SLIV value indicating a start and length indicator contained in an indexed row of a table configured by radio resource control (RRC).

In particular, the determination of the assigned resources is based on at least one additional value contained in an indexed row of a table configured by Radio Resource Control (RRC) that indicates the assigned resources in the time domain for at least one repetition of the initial PDSCH transmission.

Finally, the receiver 420 of the user equipment 410 receives the PDSCH transmission using appropriately assigned resources for the initial PDSCH transmission and at least one repetition thereof.

First exemplary implementation

The following first exemplary implementation is provided with the understanding that at least one additional value contained in an indexed row of a radio resource control (RRC) configured table is at least one of: a K ₂ ' value indicating a second slot offset for at least one repetition; a value of SLIV' indicating a second start and length indicator value for at least one repetition; and optionally a value indicating the number of at least one repetition.

In particular, the second start and length indicator value SLIV' comprises: a value S' indicating a symbol number indicating the start of the assigned time domain resources for at least one repetition; and a value L' indicating a number of symbols specifying a length of assigned resources for at least one repetition.

With this understanding, the table configured by radio resource control (RRC) contains not only values that define the allocated resources for the initial PUSCH transmission. Rather, the table configured by radio resource control (RRC) contains additional K ₂ ' and/or SLIV' values that define assigned resources for repeating the initial PUSCH transmission. In addition, an optional additional value indicating the number of at least one repetition also complements the table configured by radio resource control (RRC), allowing more flexibility to determine which of the indicated assigned resources should be used for repetitions.

Specifically, in the first exemplary embodiment, a radio resource control (RRC) configured table contains rows each containing: a value indicating a PUSCH mapping type; a K ₂ value indicating slot offsets; and an SLIV value indicating a start and length indicator for the initial PUSCH transmission, and as additional values: a K ₂ ' value indicating a second slot offset for at least one repetition; and a SLIV' value indicating a second start and length indicator value for at least one repetition.

An example of such a table configured by Radio Resource Control (RRC) is reproduced below, namely as Table 1:

Downlink Control Information String Index (DCI) PUSCH display type K2 S L {K2'}, {S'}, {L'} 1 Type A K2_1 S_1 L_1 {K2'_1_1, K2'_1_2,….K2'_1_n},
{S2'_1_1, S2'_1_2,….S2'_1_n},
{L2'_1_1, L2'_1_2,….L2'_1_n} 2 Type B K2_2 S_2 L_2 {K2'_2_1, K2'_2_2,….K2'_2_n},
{S2'_2_1, S2'_2_2,….S2'_2_n},
{L2'_2_1, L2'_2_2,….L2'_2_n} …. …. …. …. …. …. 16 …. …. …. …. ….

Table 1

In this exemplary Table 1, each of the SLIV and SLIV' values, as shown, contains: an S and S' value indicating a character number specifying the beginning of the assigned resources, and an L and L' value indicating the number of characters specifying the length of the assigned resources. .

In particular, the table configured by radio resource control (RRC) contains not only one set of additional values K ₂ ' and SLIV' or better K ₂ ', S' and L', but instead contains such a set of additional values for each of the PUSCH repetitions to be transmitted by the user equipment 410. This provides a high degree of flexibility for each of the PUSCH repetitions without incurring additional signaling resource overhead.

In particular, the processor 430, 480 of the user equipment 410 or the base station 460 configures this table according to the parameters contained in the time domain resource assignment list information element (IE) of the PUSCH, namely according to the parameter list called the time domain resource assignment list. time domain PUSCH. In other words, the table is defined by the PUSCH Time Domain Resource Assignment List Information Element (IE) which is carried in the PUSCH Configuration Information Element (IE) received as Radio Resource Control (RRC) signals.

An example of such a PUSCH Time Domain Resource Assignment List Information Element (IE) is reproduced in this document below as Example 1. element (IE) of the resource assignment list in the PUSCH time domain.

-- ASN1START

--TAG-PUSCH-TIMEDOMAINRESOURCEALLOCATIONLIST-START

--TAG-PUSCH-TIMEDOMAINRESOURCEALLOCATIONLIST-STOP

-- ASN1STOP

Example 1: ASN.1 notation "PUSCH-TimeDomainResourceAllocationList IE"

As can be seen from this Example 1, the PUSCH time domain resource assignment parameter includes not only values indicating the PUSCH mapping type, a K ₂ value indicating slot offsets for the initial PUSCH transmission, an SLIV value indicating the start and length indicator for the initial PUSCH transmission , but also a value indicating the number of repetitions (called the number of resource indicator value (RIV) assignments), and for each of the repetitions (called RIV assignments), a value of K ₂ ' indicating the second slot offset for at least one repetition , an SLIV' value indicating a second start and length indicator value for at least one repetition.

When comparing the PUSCH Time Domain Resource Assignment List Information Element (IE) of Example 1 with the Radio Resource Control (RRC) configured table from Table 1, it can be seen that a value indicating the number of repetitions (called the number of RIV assignments) of the specified Information Element (IE ), is only indirectly reflected in the table configured by radio resource control (RRC), namely as the total of each of the values of K ₂ ', S' and L'. However, this value can also be directly included in a table configured by radio resource control (RRC).

Additional meanings will be explained in more detail with respect to various uses of the first exemplary embodiment depicted in FIG. 8-13.

One use of the first exemplary implementation

One use of a radio resource control (RRC) configured table according to the first exemplary embodiment is shown in FIG. 8-9, which depict an exemplary table configured by Radio Resource Control (RRC) for PUSCH repetitions and show corresponding time domain resource assignments according to the use of the first exemplary implementation.

According to the specified exemplary table configured by Radio Resource Control (RRC), in the row with index 3, values are given for which the corresponding resource assignments in the time domain are shown. The table configured by radio resource control (RRC) contains in row index 3 a value indicating that the PUSCH mapping type should be type b, which means that resource assignments can start in the specified slot and not necessarily at the beginning of the specified slot.

In addition, this line contains the value K ₂ indicating that the assigned resources for the initial PUSCH transmission are included in slot number k+2 of slot. In addition, S and L values are included indicating that the assigned resources for the initial PUSCH transmission start in slot number k+2 with symbol number 1 and are 4 symbols long.

In addition, this line contains two additional K ₂ ' values indicating that the assigned resources for the first and second repetitions of the initial PUSCH transmission are included in the slots with respect to the value k corresponding to the slot number carrying the received downlink control information (DCI) or corresponding to the value a time domain offset field further carried in the received configuration information element (IE) of the configurable resolution.

Thus, the assigned resources for the first and second repetitions are included in slot numbers k+2 and k+3, respectively. Additionally, two S' values and two L' values are included indicating that the assigned resources for the first and second repetitions of the initial PUSCH transmission start in the corresponding slot number k+2 and k+3 slots in symbol number 6 and symbol 1, respectively. The corresponding resource assignments in the time domain are also shown.

Another use of the first exemplary implementation

Another use of the table configured radio resource control (RRC), the first exemplary implementation is shown in FIG. 10-11, an exemplary table configured by Radio Resource Control (RRC) for PUSCH repetitions is given and corresponding time domain resource assignments are shown according to the use of the first exemplary embodiment.

According to the specified exemplary table configured by Radio Resource Control (RRC), in the row with index 3, values are given for which the corresponding resource assignments in the time domain are shown. The table configured by radio resource control (RRC) contains in row index 3 a value indicating that the PUSCH mapping type should be type b, which means that resource assignments can start in the specified slot and not necessarily at the beginning of the specified slot.

In addition, this line contains the value K ₂ indicating that the assigned resources for the initial PUSCH transmission are included in slot number k+2 of slot. In addition, S and L values are included indicating that the assigned resources for the initial PUSCH transmission start in slot number k+2 with symbol number 1 and are 4 symbols long.

In addition, this line contains two additional K ₂ 'values indicating that the assigned resources for both the first and second repetitions of the initial PUSCH transmission are included in slot numbers relative to slot number k+2, with the assigned resources for the initial PUSCH transmission .

Thus, the assigned resources for the first and second repetitions are included in slot numbers (k+2)+0 and (k+2)+1 slots, respectively. Additionally, two S' values and two L' values are included indicating that the assigned resources for the first and second repetitions of the initial PUSCH transmission start in the corresponding slot number (k+2)+0 and (k+2)+1 slots in symbol c numbers 6 and 1 characters respectively. The corresponding resource assignments in the time domain are also shown.

Another use of the first exemplary implementation

Another use of the table configured radio resource control (RRC), the first exemplary implementation is shown in FIG. 12-13, which show an exemplary table configured by Radio Resource Control (RRC) for PUSCH repetitions and show corresponding time domain resource assignments according to the use of the first exemplary implementation.

According to the specified exemplary table configured by Radio Resource Control (RRC), in the row with index 3, values are given for which the corresponding resource assignments in the time domain are shown. The table configured by radio resource control (RRC) contains in row index 3 a value indicating that the PUSCH mapping type should be type b, which means that resource assignments can start in the specified slot and not necessarily at the beginning of the specified slot.

In addition, this line contains the value K ₂ indicating that the assigned resources for the initial PUSCH transmission are included in slot number k+2 of slot. In addition, S and L values are included indicating that the assigned resources for the initial PUSCH transmission start in slot number k+2 with symbol number 1 and are 4 symbols long.

In addition, this line contains two additional K ₂ 'values indicating that the assigned resources for the first repetition of the initial PUSCH transmission are included in the slots indicated relative to slot number k+2, with the assigned resources for the initial PUSCH transmission, and the second repetition is included in the slot with respect to the slot number (k+2)+0 with assigned resources for the first repetition.

Thus, the assigned resources for the first and second repetitions are included in slot numbers (k+2)+0 and ((k+2)+0)+1 slots, respectively. Additionally, two S' values and two L' values are included indicating that the assigned resources for the first and second repetitions of the initial PUSCH transmission start in the corresponding slot number (k+2)+0 and ((k+2)+0)+1 slots in the symbol numbered 6 and 1 symbols respectively. The corresponding resource assignments in the time domain are also shown.

In other words, the second slot offset determines the assigned resources for the next one of the at least one repetition relative to the resource assigned slot number for the previous one of the at least one repetition.

Second exemplary implementation

The following second exemplary embodiment is proposed with the understanding that at least one additional value contained in an indexed row of a table configured by Radio Resource Control (RRC) is at least one of: resources for at least one repetition; a value of L' indicating a number of symbols indicating a length of assigned resources for at least one repetition; and optionally a value indicating the number of at least one repetition.

With this understanding, the table configured by radio resource control (RRC) contains not only values that define the allocated resources for the initial PUSCH transmission. Rather, the radio resource control (RRC) configured table contains additional G' and/or L' values that define assigned resources for repeating the initial PUSCH transmission. In addition, an optional additional value indicating the number of at least one repetition may also complement the table configured by radio resource control (RRC), allowing more flexibility to determine which of the indicated assigned resources should be used for repetitions.

An example of such a table configured by Radio Resource Control (RRC) is reproduced below, namely as Table 2:

Downlink Control Information String Index (DCI) PUSCH display type K2 S L L' {G} 1 Type A K2_1 S_1 L_1 L_1' {G_1_1, G_1_2....G_1_n1} 2 Type B K2_2 S_2 L_2 L_2' {G_2_1, G_2_2....G_2_n2} …. …. …. …. …. …. …. 16 …. …. …. …. …. ….

table 2

In particular, the table configured by Radio Resource Control (RRC) not only contains one set of additional G' and L' values, but instead contains one additional L' value that applies to all repetitions, and a set of additional G' values for each of of the PUSCH repetitions to be transmitted by the user equipment 410. This provides a high degree of flexibility for each of the PUSCH repetitions without incurring additional signaling resource overhead.

In particular, the processor 430, 480 of the user equipment 410 or the base station 460 configures this table according to the parameters contained in the time domain resource assignment list information element (IE) of the PUSCH, namely according to the parameter list called the time domain resource assignment list. time domain PUSCH. In other words, the table is defined by the PUSCH Time Domain Resource Assignment List Information Element (IE) which is carried in the PUSCH Configuration Information Element (IE) received as Radio Resource Control (RRC) signals.

An example of such a PUSCH Time Domain Resource Assignment List Information Element (IE) is reproduced in this document below as Example 2 As terminology may change in the future, this example should be understood more broadly with respect to its functions and additional parameter passing concepts contained in the information element (IE) resource assignment list in the PUSCH time domain.

-- ASN1START

--TAG-PUSCH-TIMEDOMAINRESOURCEALLOCATIONLIST-START

--TAG-PUSCH-TIMEDOMAINRESOURCEALLOCATIONLIST-STOP

-- ASN1STOP

Example 2: ASN.1 notation "PUSCH-TimeDomainResourceAllocationList IE"

As can be seen from this Example 2, the PUSCH time domain resource assignment parameter includes not only values indicating the PUSCH mapping type, a K ₂ value indicating slot offsets for the initial PUSCH transmission, an SLIV value indicating the start and length indicator for the initial PUSCH transmission , but also a value L' (called the length of each repetition) indicating the length in terms of the number of characters of each repetition, a value indicating the number of repetitions (called the number of repetitions), and for each of the repetitions a value G' (called the repetition interval) indicating the number space characters before assigned resources for at least one repetition.

When comparing the PUSCH Time Domain Resource Assignment List Information Element (IE) of Example 2 with the Radio Resource Control (RRC) configured table, it can be seen from Table 2 that a value indicating the number of repetitions (called repetition count) of the Information Element (IE) is only indirectly reflected in the table configured by radio resource control (RRC), namely as the total number of G' values. However, this value can also be directly included in a table configured by radio resource control (RRC).

Additional meanings will be explained in more detail with respect to various uses of the second exemplary embodiment depicted in FIG. 14-17.

One Use of the Second Exemplary Implementation

One use of a Radio Resource Control (RRC) configured table according to a second exemplary embodiment is shown in FIG. 14-15, which depict an exemplary table configured by Radio Resource Control (RRC) for PUSCH repetitions and show corresponding time domain resource assignments according to the use of the second exemplary embodiment.

According to the specified exemplary table configured by Radio Resource Control (RRC), in the row with index 3, values are given for which the corresponding resource assignments in the time domain are shown. The table configured by radio resource control (RRC) contains in row index 3 a value indicating that the PUSCH mapping type should be type b, which means that resource assignments can start in the specified slot and not necessarily at the beginning of the specified slot.

In addition, this line contains the value K ₂ indicating that the assigned resources for the initial PUSCH transmission are included in slot number k+2 of slot. In addition, S and L values are included indicating that the assigned resources for the initial PUSCH transmission start in slot number k+2 with symbol number 1 and are 4 symbols long.

In addition, this line contains one additional value L', indicating that the length, expressed as a number of characters, is 4 for the assigned resources of each of the first and second repetitions, and two additional G' values, indicating that the assigned resources for the first and second repetitions initial PUSCH transmissions start with a symbol with a gap G' equal to the number of symbols 1, 6 before the assigned resources.

For the first and second repetitions, the number of symbols of the gap indicated by the value G' refers to the number 4 of the last symbol in slot k+2 of the assigned resources for the initial PUSCH transmission.

Thus, the assigned resources for the first and second repetitions are included in the slots with slot numbers k+2. Specifically, the number of the last symbol of the initial PUSCH initial transmission assigned resources is 4. Thus, a 1 symbol span defines the assigned resources for the first repetition, which start with a symbol having a number of 4+1 and end with a symbol having a number of 4+1+4 . A 6-character-long gap defines the assigned resources for the second repetition, starting at character number 4+6 and ending at character number 4+6+4. The corresponding resource assignments in the time domain are also shown.

Another Use of the Second Exemplary Implementation

Another use of the Radio Resource Control (RRC) configured table according to the second exemplary embodiment is shown in FIG. 16-17, which depict an exemplary table configured by Radio Resource Control (RRC) for PUSCH repetitions and show corresponding time domain resource assignments according to yet another use of the second exemplary embodiment.

According to the specified exemplary table configured by Radio Resource Control (RRC), in the row with index 3, values are given for which the corresponding resource assignments in the time domain are shown. The table configured by radio resource control (RRC) contains in row index 3 a value indicating that the PUSCH mapping type should be type b, which means that resource assignments can start in the specified slot and not necessarily at the beginning of the specified slot.

In addition, this line contains the value K ₂ indicating that the assigned resources for the initial PUSCH transmission are included in slot number k+2 of slot. In addition, S and L values are included indicating that the assigned resources for the initial PUSCH transmission start in slot number k+2 with symbol number 1 and are 4 symbols long.

In addition, this line contains one additional value L', indicating that the length, expressed as a number of characters, is 4 for the assigned resources of each of the first and second repetitions, and two additional G' values, indicating that the assigned resources for the first and second repetitions initial PUSCH transmissions start with a character gap equal to the number of characters 1, 6 before the assigned resources.

For the first and second repetitions, the number of symbols of the gap indicated by the G' value refers to the number 4 of the last symbol in slot k+2 of the assigned resources for the initial PUSCH transmission. For the first and second repetitions, the number of symbols of the gap indicated by the G' value refers to the number 4+1+4 of the last symbol in slot k+2 of the assigned resource for the first repetition.

Thus, the assigned resources for the first and second repetitions are included in the slots with slot numbers k+2. Specifically, the number of the last symbol of the initial PUSCH initial transmission assigned resources is 4. Thus, a 1 symbol span defines the assigned resources for the first repetition, which start with a symbol having a number of 4+1 and end with a symbol having a number of 4+1+4 . The 1 symbol gap defines the allocated resources for the second repetition, which starts with symbol number 4+1+4+1 and ends with symbol number 4+1+4+1+4.

In other words, the number of gap symbols determines the assigned resources for the next one of the at least one repetition relative to the number of the last assigned resource symbol for the previous one of the at least one repetition.

Third Exemplary Implementation

The following second exemplary embodiment is proposed with the understanding that at least one additional value contained in an indexed row of a table configured by Radio Resource Control (RRC) is at least one of: resources for at least one repetition; a value L' indicating a number of symbols indicating a length of assigned resources for at least one repetition; and optionally a value indicating the number of at least one repetition.

With this understanding, the table configured by radio resource control (RRC) contains not only values that define the allocated resources for the initial PUSCH transmission. Rather, the radio resource control (RRC) configured table contains additional G' and/or L' values that define assigned resources for repeating the initial PUSCH transmission. In addition, an optional additional value indicating the number of at least one repetition may also complement the table configured by radio resource control (RRC), allowing more flexibility to determine which of the indicated assigned resources should be used for repetitions.

An example of such a table configured by Radio Resource Control (RRC) is reproduced below, namely as Table 3:

Downlink Control Information String Index (DCI) PUSCH display type K2 S L {L'}, {G} 1 Type A K2_1 S_1 L_1 {L‘_1_1,L‘_1_2....L‘_1_n1}, {G_1_1, G_1_2....G_1_n1} 2 Type B K2_2 S_2 L_2 {L'_2_1,L'_2_2....L'_2_n2},
{G_2_1, G_2_2....G_2_n2} …. …. …. …. …. …. 16 …. …. …. …. ….

Table 3

In particular, the table configured by Radio Resource Control (RRC) not only contains one set of additional G' and L' values, but instead contains a set of additional G' and L' values for each of the PUSCH repetitions to be transmitted by the user equipment 410. This provides a high degree of flexibility for each of the PUSCH repetitions without incurring additional overhead of signaling resources.

In particular, the processor 430, 480 of the user equipment 410 or the base station 460 configures this table according to the parameters contained in the time domain resource assignment list information element (IE) of the PUSCH, namely according to the parameter list called the time domain resource assignment list. time domain PUSCH. In other words, the table is defined by the PUSCH Time Domain Resource Assignment List Information Element (IE) which is carried in the PUSCH Configuration Information Element (IE) received as Radio Resource Control (RRC) signals.

An example of such a PUSCH Time Domain Resource Assignment List Information Element (IE) is reproduced in this document below as Example 3. element (IE) of the resource assignment list in the PUSCH time domain.

-- ASN1START

--TAG-PUSCH-TIMEDOMAINRESOURCEALLOCATIONLIST-START

--TAG-PUSCH-TIMEDOMAINRESOURCEALLOCATIONLIST-STOP

-- ASN1STOP

Example 3: ASN.1 notation "PUSCH-TimeDomainResourceAllocationList IE"

As can be seen from this Example 3, the PUSCH time domain resource assignment parameter includes not only values indicating the PUSCH mapping type, a K ₂ value indicating slot offsets for the initial PUSCH transmission, an SLIV value indicating the start and length indicator for the initial PUSCH transmission , but also a value indicating the number of repetitions (called the number of repetitions), and for each of the repetitions (called the repetition interval), a value L' (called the length of each repetition) indicating the length expressed in the number of characters of each repetition, and a value G' indicating the number of gap characters before assigned resources for at least one repetition.

When comparing the PUSCH Time Domain Resource Assignment List Information Element (IE) of Example 3 with a table configured by Radio Resource Control (RRC), in Table 3, it can be seen that a value indicating the number of repetitions (called repetition count) of the Information Element (IE) is only indirectly reflected in the table configured by radio resource control (RRC), namely as the total of each of the values of G' and L'. However, this value can also be directly included in a table configured by radio resource control (RRC).

Additional meanings will be explained in more detail with respect to various uses of the third exemplary embodiment depicted in FIG. 18-21.

One Use of the Third Exemplary Implementation

One use of a radio resource control (RRC) configured table according to a third exemplary embodiment is shown in FIG. 18-19, which depict an exemplary table configured by Radio Resource Control (RRC) for PUSCH repetitions and show corresponding time domain resource assignments according to the use of the second exemplary implementation.

According to the specified exemplary table configured by Radio Resource Control (RRC), in the row with index 3, values are given for which the corresponding resource assignments in the time domain are shown. The table configured by radio resource control (RRC) contains in row index 3 a value indicating that the PUSCH mapping type should be type b, which means that resource assignments can start in the specified slot and not necessarily at the beginning of the specified slot.

In addition, this line contains the value K ₂ indicating that the assigned resources for the initial PUSCH transmission are included in slot number k+2 of slot. In addition, S and L values are included indicating that the assigned resources for the initial PUSCH transmission start in slot number k+2 with symbol number 1 and are 4 symbols long.

In addition, this string contains two additional values L' indicating the length in the number of symbols 4, 3 for the assigned resources of the first and second repetitions, and two additional values G' indicating that the assigned resources for the first and second repetitions of the initial PUSCH transmission start with character with a gap G' equal to the number of characters 1, 6, before the assigned resources.

For the first and second repetitions, the number of symbols of the gap indicated by the value G' refers to the number 4 of the last symbol in slot k+2 of the assigned resources for the initial PUSCH transmission.

Thus, the assigned resources for the first and second repetitions are included in the slots with slot numbers k+2. Specifically, the number of the last symbol of the initial PUSCH initial transmission assigned resources is 4. Thus, a 1 symbol span defines the assigned resources for the first repetition, which start with a symbol having a number of 4+1 and end with a symbol having a number of 4+1+4 . The 6 character gap defines the allocated resources for the second repetition, which starts with character number 4+6 and ends with character number 4+6+3. The corresponding resource assignments in the time domain are also shown.

Another Use of the Second Exemplary Implementation

Another use of a radio resource control (RRC) configured table according to a second exemplary embodiment is shown in FIG. 20-21, which depict an exemplary table configured by Radio Resource Control (RRC) for PUSCH repetitions and show corresponding time domain resource assignments according to another use of the second exemplary embodiment.

According to the specified exemplary table configured by Radio Resource Control (RRC), in the row with index 3, values are given for which the corresponding resource assignments in the time domain are shown. The table configured by radio resource control (RRC) contains in row index 3 a value indicating that the PUSCH mapping type should be type b, which means that resource assignments can start in the specified slot and not necessarily at the beginning of the specified slot.

In addition, this line contains the value K ₂ indicating that the assigned resources for the initial PUSCH transmission are included in slot number k+2 of slot. In addition, S and L values are included indicating that the assigned resources for the initial PUSCH transmission start in slot number k+2 with symbol number 1 and are 4 symbols long.

In addition, this string contains two additional values L' indicating the length in the number of symbols 4, 3 for the assigned resources of the first and second repetitions, and two additional values G' indicating that the assigned resources for the first and second repetitions of the initial PUSCH transmission start with character with a gap G' equal to the number of characters 1, 6, before the assigned resources.

For the first and second repetitions, the number of symbols of the gap indicated by the G' value refers to the number 4 of the last symbol in slot k+2 of the assigned resources for the initial PUSCH transmission. For the first and second repetitions, the number of symbols of the gap indicated by the G' value refers to the number 4+1+4 of the last symbol in slot k+2 of the assigned resource for the first repetition.

Thus, the assigned resources for the first and second repetitions are included in the slots with slot numbers k+2. Specifically, the number of the last symbol of the initial PUSCH initial transmission assigned resources is 4. Thus, a 1 symbol span defines the assigned resources for the first repetition, which start with a symbol having a number of 4+1 and end with a symbol having a number of 4+1+4 . The 1 symbol gap defines the assigned resources for the second repetition, which starts with symbol number 4+1+4+1 and ends with symbol number 4+1+4+1+3.

In other words, the number of gap symbols determines the assigned resources for the next one of the at least one repetition relative to the number of the last assigned resource symbol for the previous one of the at least one repetition.

Fourth Exemplary Embodiment

The following fourth exemplary embodiment is proposed with the understanding that at least one additional value contained in an indexed row of a table configured by Radio Resource Control (RRC) is at least one of: a value L' indicating the number of characters defining the length assigned resources for at least one repetition; and optionally a value indicating the number of at least one repetition.

With this understanding, the table configured by radio resource control (RRC) contains not only values that define the allocated resources for the initial PUSCH transmission. Rather, the radio resource control (RRC) configured table contains additional L' values that define assigned resources for repeating the initial PUSCH transmission. In addition, an optional additional value indicating the number of at least one repetition may also complement the table configured by radio resource control (RRC), allowing more flexibility to determine which of the indicated assigned resources should be used for repetitions.

An example of such a table configured by Radio Resource Control (RRC) is reproduced below, namely as Table 4:

Downlink Control Information String Index (DCI) PUSCH display type K2 S L {L'} 1 Type A K2_1 S_1 L_1 {L'_1_1,L'_1_2....L'_1_n1} 2 Type B K2_2 S_2 L_2 {L'_2_1,L'_2_2....L'_2_n2} …. …. …. …. …. …. 16 …. …. …. …. ….

Table 4

In particular, the table configured by Radio Resource Control (RRC) not only contains one additional L' value, but instead contains a set of additional L' values for each of the PUSCH repetitions to be transmitted by the user equipment 410. This provides a high degree of flexibility for each from PUSCH repetitions without generating additional overhead of signaling resources.

In particular, the processor 430, 480 of the user equipment 410 or the base station 460 configures this table according to the parameters contained in the time domain resource assignment list information element (IE) of the PUSCH, namely according to the parameter list called the time domain resource assignment list. time domain PUSCH. In other words, the table is defined by the PUSCH Time Domain Resource Assignment List Information Element (IE) which is carried in the PUSCH Configuration Information Element (IE) received as Radio Resource Control (RRC) signals.

An example of such a PUSCH Time Domain Resource Assignment List Information Element (IE) is reproduced in this document below, namely as Example 4. Since the terminology may change in the future, this example should be understood more broadly with respect to its functions and additional parameter passing concepts contained in in the resource assignment list information element (IE) in the PUSCH time domain.

-- ASN1START

--TAG-PUSCH-TIMEDOMAINRESOURCEALLOCATIONLIST-START

--TAG-PUSCH-TIMEDOMAINRESOURCEALLOCATIONLIST-STOP

-- ASN1STOP

Example 4: ASN.1 notation "PUSCH-TimeDomainResourceAllocationList IE"

As can be seen from this Example 4, the PUSCH time domain resource assignment parameter includes not only values indicating the PUSCH mapping type, a K ₂ value indicating slot offsets for the initial PUSCH transmission, an SLIV value indicating the start and length indicator for the initial transmission PUSCH, but also a value indicating the number of repetitions (called the number of repetitions), and for each of the repetitions (called the length of the repetition), the value L' (called the length of each repetition) indicating the length, expressed in the number of symbols of each repetition, for at least one repetitions.

When comparing the PUSCH Time Domain Resource Assignment List Information Element (IE) of Example 4 with the table configured by Radio Resource Control (RRC), it can be seen in Table 4 that a value indicating the number of repetitions (called repetition count) of the Information Element (IE) is only indirectly reflected in the specified radio resource control (RRC) configured table, namely as the total number of L' values. However, this value can also be directly included in a table configured by radio resource control (RRC).

Additional meanings will be explained in more detail with respect to various uses of the fourth exemplary embodiment depicted in FIG. 22-23.

One Use of the Fourth Exemplary Implementation

One use of a radio resource control (RRC) configured table according to a fourth exemplary embodiment is shown in FIG. 22-23, which depict an exemplary table configured by Radio Resource Control (RRC) for PUSCH repetitions and show corresponding time domain resource assignments according to the use of the second exemplary embodiment.

According to the specified exemplary table configured by Radio Resource Control (RRC), in the row with index 3, values are given for which the corresponding resource assignments in the time domain are shown. The table configured by radio resource control (RRC) contains in row index 3 a value indicating that the PUSCH mapping type should be type b, which means that resource assignments can start in the specified slot and not necessarily at the beginning of the specified slot.

In addition, this line contains the value K ₂ indicating that the assigned resources for the initial PUSCH transmission are included in slot number k+2 of slot. In addition, S and L values are included indicating that the assigned resources for the initial PUSCH transmission start in slot number k+2 with symbol number 1 and are 4 symbols long.

In addition, this string contains two additional L' values indicating the length in number of characters 4, 4 for the assigned resources of the first and second repetitions.

For the first and second repetitions, the beginning of the assigned resources continuously follows the last symbol of the assigned resources for the corresponding one of the initial PUSCH transmission and its first repetition.

Thus, the assigned resources for the first and second repetitions are included in the slots with slot numbers k+2. Specifically, the number of the last symbol of the initial PUSCH initial transmission assigned resources is 4. Thus, the assigned resources for the first repetition starting with symbol number 4 and ending with symbol number 4+4 are determined. And assigned resources for the second repetition are defined, which start with symbol number 4+4 and end with symbol number 4+4+4. The corresponding resource assignments in the time domain are also shown.

Another exemplary implementation

Another exemplary implementation is described below in which the behavior of the first or second exemplary implementations can be configured in the base station 460. To this end, an exemplary PUSCH Time Domain Resource Assignment List Information Element (IE) can be specified. , which is reproduced in this document below, namely as Example 5. Since the terminology may change in the future, this example should be understood more broadly in relation to its functions and concepts for passing additional parameters contained in the Time Domain Resource Assignment List Information Element (IE). PUSCH.

-- ASN1START

--TAG-PUSCH-TIMEDOMAINRESOURCEALLOCATIONLIST-START

--TAG-PUSCH-TIMEDOMAINRESOURCEALLOCATIONLIST-STOP

-- ASN1STOP

Example 5: ASN.1 notation "PUSCH-TimeDomainResourceAllocationList IE"

According to yet another exemplary implementation, the PUSCH Time Domain Resource Assignment List Information Element (IE) further comprises a parameter indicating whether the transport block size is calculated for each PUSCH transmission separately, or whether the combined transport block size is calculated for all PUSCH transmissions, including an initial PUSCH transmission and at least one repeat thereof.

This yet another exemplary embodiment may be combined with any of the exemplary first through fourth embodiments. In conjunction with the first exemplary implementation, the exemplary PUSCH Time Domain Resource Assignment List Information Element (IE) may be defined as reproduced herein below, namely as in Example 6. Since the terminology may change in the future , this example should be understood more broadly with respect to its functions and concepts for passing additional parameters contained in the PUSCH Time Domain Resource Assignment List Information Element (IE).

-- ASN1START

--TAG-PUSCH-TIMEDOMAINRESOURCEALLOCATIONLIST-START

--TAG-PUSCH-TIMEDOMAINRESOURCEALLOCATIONLIST-STOP

-- ASN1STOP

Example 6: ASN.1 notation "PUSCH-TimeDomainResourceAllocationList IE"

It is important to note that Example 6 refers to two different computational mechanisms for calculating the transport block size (TBS), namely the combined and separate calculation of the TBS size. However, this should not be construed as limiting the present invention. Rather, if it is agreed that three or even more different calculation mechanisms should be used, then one skilled in the art will appreciate that also applicable one of the three or even more different calculation mechanisms can be indicated in the Destination List Information Element (IE). resources in the PUSCH time domain.

According to yet another exemplary implementation, the PUSCH Time Domain Resource Assignment List Information Element (IE) further comprises a parameter indicating whether frequency hopping is applied to each PUSCH transmission separately, or whether continuous frequency hopping is applied to all PUSCH transmissions, including an initial PUSCH transmission and at least one repeat thereof.

This yet another exemplary embodiment may be combined with any of the exemplary first through fourth embodiments. In combination with the first exemplary implementation, the exemplary PUSCH Time Domain Resource Assignment List Information Element (IE) may be defined as reproduced herein below, namely as in Example 7. Since the terminology may change in the future , this example should be understood more broadly with respect to its functions and concepts for passing additional parameters contained in the PUSCH Time Domain Resource Assignment List Information Element (IE).

-- ASN1START

--TAG-PUSCH-TIMEDOMAINRESOURCEALLOCATIONLIST-START

--TAG-PUSCH-TIMEDOMAINRESOURCEALLOCATIONLIST-STOP

-- ASN1STOP

Example 7: ASN.1 notation "PUSCH-TimeDomainResourceAllocationList IE"

It is important to note that Example 7 refers to two different frequency hopping mechanisms, namely a mechanism in which frequency hopping is applied either individually or to all PUSCH transmissions. However, this should not be construed as limiting the present invention. Rather, if it is agreed that three or even more different calculation mechanisms should be used, one skilled in the art will appreciate that also applicable one of the three or even more different frequency hopping mechanisms can be indicated in the List Information Element (IE). assignment of resources in the PUSCH time domain.

According to yet another exemplary implementation, the PUSCH Time Domain Resource Assignment List Information Element (IE) further comprises a parameter indicating whether demodulation reference symbols (DMRS) are present in all or each individual one of the at least one repeating the initial PUSCH transmission or not.

This yet another exemplary embodiment may be combined with any of the exemplary first through fourth embodiments. In combination with the first exemplary implementation, the exemplary PUSCH Time Domain Resource Assignment List Information Element (IE) may be defined as reproduced herein below, namely as in Example 8. Since the terminology may change in the future , this example should be understood more broadly with respect to its functions and concepts for passing additional parameters contained in the PUSCH Time Domain Resource Assignment List Information Element (IE).

-- ASN1START

--TAG-PUSCH-TIMEDOMAINRESOURCEALLOCATIONLIST-START

--TAG-PUSCH-TIMEDOMAINRESOURCEALLOCATIONLIST-STOP

-- ASN1STOP

Example 8: ASN.1 notation "PUSCH-TimeDomainResourceAllocationList IE"

According to a first aspect, a user equipment (UE) is provided, comprising: a receiver that, during operation, receives a physical uplink shared channel (PUSCH) configuration information element (IE) in the form of radio resource control (RRC) signals, said configuration information element (IE) PUSCH is applicable to a specific portion of the bandwidth; a processor that, during operation, configures a table specified by a PUSCH Time Domain Resource Assignment List Information Element (IE) carried in a received PUSCH Configuration Information Element (IE), said table containing rows each containing a value indicating a mapping type PUSCH, a K ₂ value indicating slot offsets, and an SLIV value indicating a start and length indicator; said receiver, during operation, receives downlink control information (DCI) in the form of medium access control (MAC) signals carrying a time domain resource assignment field having a value of m, said value of m providing an m+1 row index for said table configured by radio resource control (RRC), and the specified processor during operation determines the assigned resources for the initial PUSCH transmission and the assigned resources for at least one repetition thereof based on: the slot number carrying the received downlink control information (DCI), the value of K ₂ indicating slot offsets and SLIV values indicating start indicator and length contained in an indexed row of a table configured by radio resource control (RRC); and a transmitter that, during operation, performs a PUSCH transmission using respectively determined assigned resources for the initial PUSCH transmission and for at least one repetition thereof; and wherein the determination of the assigned resources is based on at least one additional value contained in an indexed row of a table configured by Radio Resource Control (RRC) that determines the assigned resources in the time domain for at least one repetition of the initial PUSCH transmission.

According to a second aspect, a user equipment (UE) is provided, comprising: a receiver that, during operation, receives a physical uplink shared channel (PUSCH) configuration information element (IE) in the form of radio resource control (RRC) signals, said configuration information element (IE) PUSCH is applicable to a specific portion of the bandwidth; a processor that, during operation, configures a table specified by a PUSCH Time Domain Resource Assignment List Information Element (IE) carried in a received PUSCH Configuration Information Element (IE), said table containing rows each containing a value indicating a mapping type PUSCH, a K ₂ value indicating slot offsets, and an SLIV value indicating a start and length indicator; wherein said receiver, during operation, receives a configurable grant configuration information element (IE) in the form of radio resource control (RRC) signals carrying a time domain resource assignment field having a value of m, said value of m providing an m+1 row index for said table configured by Radio Resource Control (RRC), wherein said processor determines, during operation, the assigned resources for the initial PUSCH transmission and the assigned resources for at least one iteration thereof, based on: the value of the Time Domain Offset field optionally carried in the received Configuration Information Element (IE) a configurable resolution and associated with a time domain assignment field, a K ₂ value indicating slot offsets, and an SLIV value indicating a start indicator and a length contained in an indexed row of a table configured by radio resource control (RRC); and a transmitter that, during operation, performs a PUSCH transmission using respectively determined assigned resources for the initial PUSCH transmission and for at least one repetition thereof; wherein the determination of the assigned resources is based on at least one additional value contained in an indexed row of a table configured by Radio Resource Control (RRC) that determines the assigned resources in the time domain for at least one repetition of the initial PUSCH transmission.

According to a third aspect, which is provided in addition to the first or second aspect, the at least one additional value is one of: a K ₂ ' value indicating a second slot offset for at least one repetition, an SLIV' value indicating a second start indicator value, and length for at least one repetition and a value indicating the number of at least one repetition, and/or wherein the second value of the start and length indicator SLIV' comprises: a value S' indicating a symbol number indicating the start of assigned resources for at least one repetitions, and a value L' indicating the number of symbols defining the length of the assigned resources for at least one repetition.

According to a fourth aspect, which is provided in addition to the third or fourth aspect, in the case where at least one additional value is a K ₂ ' value indicating a second slot offset, said second slot offset specifying allocated resources for all at least one repetition regarding: the slot number carrying the received downlink control information (DCI) or the value of the time domain offset field optionally carried in the received configurable grant configuration information element (IE).

According to a fifth aspect, which is provided in addition to the third or fourth aspect, in the case where at least one additional value is a K ₂ ' value indicating a second slot offset, said second slot offset determines the allocated resources for all of the at least one repetition. regarding the slot number with assigned resources for the initial PUSCH transmission.

According to a sixth aspect, which is provided in addition to the third or fourth aspect, in the case where at least one additional value is a K ₂ ' value indicating a second slot offset, said second slot offset determines the allocated resources for the first of at least one repetition. relative to the resource assigned slot number for the initial PUSCH transmission, or the second slot offset determines the allocated resources for the subsequent one of the at least one repetition relative to the resource assigned slot number for the preceding one of the at least one repetition.

According to a seventh aspect, which is provided in addition to the first or second aspect, at least one value is one of: a value G' indicating the number of symbols of the gap before the allocated resources for at least one repetition, a value L' indicating the number of symbols specifying a length of assigned resources for at least one repetition, and a value indicating the number of at least one repetition.

According to the eighth aspect, which is provided in addition to the seventh aspect, in the case where at least one additional value is a value G' indicating the number of gap symbols, the specified number of gap symbols determines the allocated resources for all of the at least one repetition relative to the number of the last the assigned resource symbol for the initial PUSCH transmission.

According to a ninth aspect, which is provided in addition to the eighth aspect, in the case where at least one additional value is a G' value indicating the number of gap symbols, said number of gap symbols determines the allocated resources for the first of at least one repetitions with respect to the number of the last assigned resource symbol for the initial PUSCH transmission, or the specified number of gap symbols determines the assigned resources for the next one of the at least one repetitions relative to the last assigned resource symbol number for the previous one of the at least one repetition.

According to a tenth aspect, which is provided in addition to the third or eighth aspect, in the case where at least one additional value is an L' value indicating a number of symbols specifying a length of allocated resources, said number of symbols specifies a length of allocated resources for all of at least at least one repetition, or the specified number of characters determines the length of the allocated resources for a particular one of the at least one repetition.

According to an eleventh aspect, which is provided in addition to one of the first to tenth aspects, the PUSCH Time Domain Resource Assignment List Information Element (IE) further comprises at least one of the following parameters: a parameter indicating whether a transport block size is calculated for each PUSCH transmissions separately, or whether the combined transport block size is calculated for all PUSCH transmissions, including the initial PUSCH transmission and at least one repetition thereof; a parameter indicating whether frequency hopping is applied for each PUSCH separately, or whether continuous frequency hopping is applied to all PUSCH transmissions, including the initial PUSCH transmission and at least one repetition thereof; and a parameter indicating whether demodulation reference symbols (DMRS) are present in all or each of the at least one repetition of the initial PUSCH transmission or not.

According to a twelfth aspect, a method is provided for a user equipment (UE), including: receiving a physical uplink shared channel (PUSCH) configuration information element (IE) in the form of radio resource control (RRC) signals, said PUSCH configuration information element (IE) applicable to a specific parts of the bandwidth; configuring a table which is specified by the PUSCH Time Domain Resource Assignment List Information Element (IE) carried in the received PUSCH Configuration Information Element (IE), said table having rows each containing a value indicating a PUSCH mapping type, value K ₂ , indicating the slot offsets, and an SLIV value, indicating the start and length indicator; receiving downlink control information (DCI) in the form of medium access control (MAC) signals carrying a time domain resource assignment field having a value of m, said value of m providing an m+1 row index for a specified radio resource control configured table ( RRC) determining assigned resources for initial PUSCH transmission and assigned resources for at least one repetition thereof based on: a slot number carrying received downlink control information (DCI), a K ₂ value indicating slot offsets, and an SLIV value indicating an indicator start and length contained in the indexed row of the table configured by radio resource control (RRC); and transmitting the PUSCH using respectively determined assigned resources for the initial PUSCH transmission and for at least one repetition thereof; and wherein the determination of the assigned resources is based on at least one additional value contained in an indexed row of a table configured by Radio Resource Control (RRC) that determines the assigned resources in the time domain for at least one repetition of the initial PUSCH transmission.

According to a thirteenth aspect, a method is provided for a user equipment (UE), including: receiving a physical uplink shared channel (PUSCH) configuration information element (IE) in the form of radio resource control (RRC) signals, said PUSCH configuration information element (IE) applicable to a specific parts of the bandwidth; configuring a table which is specified by the PUSCH Time Domain Resource Assignment List Information Element (IE) carried in the received PUSCH Configuration Information Element (IE), said table having rows each containing a value indicating a PUSCH mapping type, value K ₂ , indicating the slot offsets, and an SLIV value, indicating the start and length indicator; receiving a configurable grant configuration information element (IE) in the form of radio resource control (RRC) signals carrying a time domain resource assignment field having a value of m, said value of m providing an m+1 row index for a specified radio resource control (RRC) configured table ) determining the assigned resources for the initial PUSCH transmission and the assigned resources for at least one repetition thereof based on: the value of the time domain offset field optionally carried in the received Configurable Grant Configuration Information Element (IE) and associated with the time domain assignment field, the value of K ₂ indicating slot offsets and SLIV values indicating start indicator and length contained in an indexed row of a table configured by radio resource control (RRC); and transmitting the PUSCH using respectively determined assigned resources for the initial PUSCH transmission and for at least one repetition thereof; wherein the determination of the assigned resources is based on at least one additional value contained in an indexed row of a table configured by Radio Resource Control (RRC) that determines the assigned resources in the time domain for at least one repetition of the initial PUSCH transmission.

According to a fourteenth aspect, there is provided a base station (BS) comprising: a transmitter that, during operation, transmits a physical uplink shared channel (PUSCH) configuration information element (IE) in the form of radio resource control (RRC) signals, said configuration information element (IE) PUSCH is applicable to a specific portion of the bandwidth; a processor that, during operation, configures a table specified by a PUSCH Time Domain Resource Assignment List Information Element (IE) carried in a received PUSCH Configuration Information Element (IE), said table containing rows each containing a value indicating a mapping type PUSCH, a K ₂ value indicating slot offsets, and an SLIV value indicating a start and length indicator; wherein said transmitter, during operation, transmits downlink control information (DCI) in the form of medium access control (MAC) signals carrying a time domain resource assignment field having a value of m, said value of m providing an m+1 row index for said a table configured by Radio Resource Control (RRC), wherein said processor assigns resources for initial PUSCH transmission during operation and assigns resources for at least one repetition thereof based on: slot number carrying received downlink control information (DCI), K value ₂ , indicating slot offsets, and SLIV values, indicating start indicator and length, contained in the indexed row of the table configured by radio resource control (RRC); and a receiver that, during operation, receives a PUSCH transmission using respectively assigned resources for an initial PUSCH transmission and for at least one repetition thereof; and wherein the determination of the assigned resources is based on at least one additional value contained in an indexed row of a table configured by Radio Resource Control (RRC) that determines the assigned resources in the time domain for at least one repetition of the initial PUSCH transmission.

According to a fifteenth aspect, there is provided a base station (BS) comprising: a transmitter that, during operation, transmits a physical uplink shared channel (PUSCH) configuration information element (IE) in the form of radio resource control (RRC) signals, said configuration information element (IE) PUSCH is applicable to a specific portion of the bandwidth; a processor that, during operation, configures a table specified by a PUSCH Time Domain Resource Assignment List Information Element (IE) carried in a received PUSCH Configuration Information Element (IE), said table containing rows each containing a value indicating a mapping type PUSCH, a K ₂ value indicating slot offsets, and an SLIV value indicating a start and length indicator; wherein said transmitter, during operation, transmits a configurable grant configuration information element (IE) in the form of radio resource control (RRC) signals carrying a time domain resource assignment field having a value of m, said value of m providing an m+1 row index for said table configured by Radio Resource Control (RRC), wherein said processor, during operation, assigns resources for the initial PUSCH transmission and assigns resources for at least one repetition thereof based on: the value of the Time Domain Offset field optionally carried in the received Configuration Information Element (IE) of the configurable a resolution and time domain assignment field associated, a K ₂ value indicating slot offsets, and an SLIV value indicating a start indicator and a length contained in an indexed row of a table configured by radio resource control (RRC); and a receiver that, during operation, receives a PUSCH transmission using respectively determined allocated resources for an initial PUSCH transmission and for at least one repetition thereof; wherein the determination of the assigned resources is based on at least one additional value contained in an indexed row of a table configured by Radio Resource Control (RRC) that determines the assigned resources in the time domain for at least one repetition of the initial PUSCH transmission.

According to a sixteenth aspect, a method is provided for a base station (BS), including: transmitting a physical uplink shared channel (PUSCH) configuration information element (IE) in the form of radio resource control (RRC) signals, wherein said PUSCH configuration information element (IE) is applicable to a specific parts of the bandwidth; configuring a table which is specified by the PUSCH Time Domain Resource Assignment List Information Element (IE) carried in the received PUSCH Configuration Information Element (IE), said table having rows each containing a value indicating a PUSCH mapping type, value K ₂ , indicating the slot offsets, and an SLIV value, indicating the start and length indicator; transmission of downlink control information (DCI) in the form of medium access control (MAC) signals carrying a time domain resource assignment field having a value of m, said value of m providing an m+1 row index for a specified radio resource control configured table ( RRC) assigning resources for the initial PUSCH transmission and assigning resources for at least one repetition thereof based on: a slot number carrying received downlink control information (DCI), a K ₂ value indicating slot offsets, and an SLIV value indicating a start indicator and lengths contained in an indexed row of a table configured by radio resource control (RRC); receiving a PUSCH transmission using respectively assigned resources for an initial PUSCH transmission and for at least one repetition thereof; and wherein the determination of the assigned resources is based on at least one additional value contained in an indexed row of a table configured by Radio Resource Control (RRC) that determines the assigned resources in the time domain for at least one repetition of the initial PUSCH transmission.

According to a seventeenth aspect, there is provided a method for a base station (BS), including: transmitting a physical uplink shared channel (PUSCH) configuration information element (IE) in the form of radio resource control (RRC) signals, said PUSCH configuration information element (IE) applicable to a specific parts of the bandwidth; configuring a table which is specified by the PUSCH Time Domain Resource Assignment List Information Element (IE) carried in the received PUSCH Configuration Information Element (IE), said table having rows each containing a value indicating a PUSCH mapping type, value K ₂ , indicating the slot offsets, and an SLIV value, indicating the start and length indicator; transmission of a configurable grant configuration information element (IE) in the form of radio resource control (RRC) signals carrying a time domain resource assignment field having a value of m, said value of m providing an m+1 row index for a specified radio resource control (RRC) configured table ) assigning resources for the initial PUSCH transmission and assigning resources for at least one repetition thereof based on: the value of the time domain offset field optionally carried in the received Configurable Grant Configuration Information Element (IE) and associated with the time domain assignment field, the value of K ₂ , indicating slot offsets, and SLIV values, indicating start indicator and length, contained in the indexed row of the table configured by radio resource control (RRC); receiving a PUSCH transmission using respectively determined assigned resources for an initial PUSCH transmission and for at least one repetition thereof; wherein the determination of the assigned resources is based on at least one additional value contained in an indexed row of a table configured by Radio Resource Control (RRC) that determines the assigned resources in the time domain for at least one repetition of the initial PUSCH transmission.

The present invention may be implemented in the form of software, hardware, or software combined with hardware.

Each of the functional blocks used in describing each of the above embodiments may be partially or wholly implemented by a large integrated circuit (LSI), such as an integrated circuit, and each of the processes described in each of the embodiments may be partially or wholly controlled. one LSI or a combination of LSIs.

LSI can be made separately in the form of chips, or one chip can be made in such a way that it contains part of the functional blocks or all of the functional blocks. The LSI may include the input and output of data related to it. LSI in this case may be called an integrated circuit (IC), system LSI, very large IC (VLSI) or ultra-large IC (ULSI) depending on the difference in the degree of integration.

However, the implementation method of the integrated circuit is not limited to the LSI circuit, and may be implemented using a dedicated circuit, a general purpose processor, or a special purpose processor.

In addition, a field programmable gate array (FPGA) may be used, which may be programmed after the manufacture of the LSI or a reconfigurable processor in which the connections and settings of the circuit elements located in the LSI can be reconfigured.

The present invention may be implemented in the form of digital processing or analog processing. If the latest integrated circuit technology replaces current LSIs as a result of advances in semiconductor technology or other technology derived therefrom, functional blocks can be built using said latest integrated circuit technology. Biotechnology may also be applied.

The present disclosure may be implemented by any type of equipment, device, or system having a communication function implemented by a communication device.

Some non-limiting examples of such a communication device include a telephone (e.g., cell phone, smartphone), tablet, personal computer (PC) (e.g., laptop, desktop, netbook), camera (e.g., digital photo/video camera), digital player (digital audio/video player), wearable device (e.g., wearable camera, smart watch, tracking device), game console, digital book reader, telemedicine/remote medicine device ( remote health and medicine) and a vehicle with communication functions (e.g. car, plane, ship), as well as their various combinations.

Said communication device is not limited to a portable or movable communication device, and may also include any type of equipment, device, or system that is not portable or fixed, such as a smart home device (e.g., household appliance, lighting, smart meter, control panel) , vending machine and any other "things" in the "Internet of Things (IoT)" network.

The communication may include data exchange, for example, via a cellular communication system, a wireless network (LAN) system, a satellite communication system, and the like, as well as various combinations thereof.

The communication device may include a device, such as a controller or sensor, that is connected to a communication device that performs the communication function described in this disclosure. For example, the communication device may include a controller or sensor that generates control signals or data signals that are used by the communication device that performs the communication function of the specified communication device.

The communications device may also include an infrastructure entity such as a base station, access point, and any other equipment, device, or system that communicates with or controls devices, such as in the non-limiting examples above.

Claims (105)

1. User equipment (UE), containing: a receiver that, during operation, receives a Physical Uplink Shared Channel (PUSCH) Configuration Information Element (IE) in the form of Radio Resource Control (RRC) signals, said PUSCH Configuration Information Element (IE) being applicable to a particular portion of the bandwidth; a processor that, during operation, configures a table that is specified by a PUSCH Time Domain Resource Assignment List Information Element (IE) carried in a received PUSCH Configuration Information Element (IE), said table containing rows each containing a value indicating a type displaying PUSCH, a K ₂ value indicating a slot offset, and an SLIV value indicating a start and length indicator; said receiver, during operation, receives downlink control information (DCI) signals carrying a resource assignment field in the time domain having a value of m, wherein the value of m provides an m+1 row index for a table configured by radio resource control (RRC), and said processor, during operation, determines the assigned resources for the initial PUSCH transmission and the assigned resources for at least one repetition thereof based on: - the slot number carrying the received downlink control information (DCI), and - a value of K ₂ indicating a slot offset and a value of SLIV indicating a start indicator and a length contained in an indexed row of a table configured by radio resource control (RRC); And a transmitter that, during operation, performs a PUSCH transmission using respectively determined assigned resources for an initial PUSCH transmission and for said at least one repetition thereof; And wherein the determination of the assigned resources is based on at least one additional value contained in an indexed row of a table configured by Radio Resource Control (RRC) that determines the assigned resources in the time domain for at least one repetition of the initial PUSCH transmission. 2. User equipment (UE), containing: a receiver that, during operation, receives a Physical Uplink Shared Channel (PUSCH) Configuration Information Element (IE) in the form of Radio Resource Control (RRC) signals, said PUSCH Configuration Information Element (IE) being applicable to a particular portion of the bandwidth; a processor that, during operation, configures a table that is specified by a PUSCH Time Domain Resource Assignment List Information Element (IE) carried in a received PUSCH Configuration Information Element (IE), said table containing rows each containing a value indicating a type displaying PUSCH, a K ₂ value indicating a slot offset, and an SLIV value indicating a start and length indicator; said receiver, during operation, receives a configurable grant configuration information element (IE) in the form of radio resource control (RRC) signals carrying a time domain assignment field having a value of m, said value of m providing an m+1 row index for the table, configured radio resource control (RRC), and said processor, during operation, determines the assigned resources for the initial PUSCH transmission and the assigned resources for at least one repetition thereof based on: - the values of the time domain offset field optionally carried in the received Configurable Grant Configuration Information Element (IE) and associated with the time domain assignment field, and - a value of K ₂ indicating a slot offset and a value of SLIV indicating a start indicator and a length contained in an indexed row of a table configured by radio resource control (RRC); And a transmitter that, during operation, performs a PUSCH transmission using respectively determined assigned resources for an initial PUSCH transmission and for said at least one repetition thereof; And wherein the determination of the assigned resources is based on at least one additional value contained in an indexed row of a table configured by Radio Resource Control (RRC) that determines the assigned resources in the time domain for the at least one repetition of the initial PUSCH transmission. 3. User equipment (UE) according to claim 1 or 2, in which at least one additional value is one of: - the value of K2' indicating the second slot offset for the specified at least one repetition, - a value of SLIV' indicating a second value of the start and length indicator for at least one repetition, and - a value indicating the number of said at least one repetition, and/or wherein the second value SLIV' of the start and length indicator contains: - a value S' indicating a symbol number defining the beginning of the assigned resources for the specified at least one repetition, and - a value L' indicating the number of symbols defining the length of the allocated resources for the specified at least one repetition. 4. The user equipment (UE) of claim 3, wherein in the case where at least one additional value is a K ₂ ' value indicating a second slot offset, said second slot offset specifies assigned resources for all of said at least one repetition with respect to: the specified slot number carrying the received downlink control information (DCI), or a specified value of the time domain offset field, optionally carried in the received configuration information element (IE) of the configurable resolution. 5. The user equipment (UE) according to claim 3 or 4, wherein in the case where at least one additional value is a K ₂ ' value indicating a second slot offset, said second slot offset determines the assigned resources for all of the at least one repetition relative to the resource assigned slot number for the initial PUSCH transmission. 6. The user equipment (UE) according to claim 3 or 4, wherein in the case where at least one additional value is a K ₂ ' value indicating a second slot offset, said second slot offset specifies the assigned resources for the first of said at least one repetition relative to the resource assigned slot number for the initial PUSCH transmission, or said second slot offset determines the assigned resources for the subsequent one of said at least one repetition relative to the resource assigned slot number for the preceding one of the at least one repetition. 7. User equipment (UE) according to claim 1 or 2, in which at least one value is one of: - the value of G' indicating the number of symbols of the gap before the allocated resources for the specified at least one repetition, - the value of L' indicating the number of symbols defining the length of the assigned resources for the specified at least one repetition, and - a value indicating the number of specified at least one repetition. 8. The user equipment (UE) of claim 7, wherein in the case where at least one additional value is a G' value indicating the number of gap symbols, the specified number of gap symbols determines the assigned resources for all of the specified at least one repetition relative to the last symbol number of the assigned resources for the initial PUSCH transmission. 9. The user equipment (UE) of claim 8, wherein in the case where at least one additional value is a G' value indicating the number of gap symbols, the specified number of gap symbols specifies the assigned resources for the first of the specified at least one repetition relative to the last symbol number of the assigned resources for the initial PUSCH transmission, or the specified number of gap symbols determines the assigned resources for the subsequent one of the specified at least one repetition relative to the number of the last symbol of the assigned resources for the previous one of the specified at least one repetition. 10. The user equipment (UE) according to claim 3 or 8, wherein in the case where at least one additional value is an L' value indicating the number of symbols defining the length of the assigned resources, the specified number of characters specifies the length of the assigned resources for all of the specified at least one repetition, or the specified number of characters determines the length of the assigned resources for a particular one of the specified at least one repetition. 11. User equipment (UE) according to one of paragraphs. 1-10, wherein the Time Domain Resource Assignment List Information Element (IE) PUSCH further comprises at least one of: - a parameter indicating whether the transport block size is calculated for each individual PUSCH transmission, or whether the combined transport block size is calculated for all PUSCH transmissions, including the initial PUSCH transmission and at least one repetition thereof, - a parameter indicating whether frequency hopping is applied for each individual PUSCH transmission, or whether continuous frequency hopping is applied to all PUSCH transmissions, including the initial PUSCH transmission and at least one repetition thereof, and - a parameter indicating whether demodulation reference symbols (DMRS) are present in all or each one of said at least one repetition of the initial PUSCH transmission or not. 12. A method for receiving and transmitting signals for a user equipment (UE), including: receiving a physical uplink shared channel (PUSCH) configuration information element (IE) in the form of radio resource control (RRC) signals, wherein said PUSCH configuration information element (IE) is applicable to a specific portion of the bandwidth; configuring a table which is specified by the PUSCH Time Domain Resource Assignment List Information Element (IE) carried in the received PUSCH Configuration Information Element (IE), said table having rows each containing a value indicating a PUSCH mapping type, value K ₂ , indicating the slot offset, and an SLIV value indicating the start and length indicator; receiving downlink control information (DCI) signals carrying a time domain resource assignment field having a value of m, said value of m providing an m+1 row index for a table configured by radio resource control (RRC), determining assigned resources for the initial PUSCH transmission and assigned resources for at least one repetition thereof based on: - the slot number carrying the received downlink control information (DCI), and - a value of K ₂ indicating a slot offset and a value of SLIV indicating a start indicator and a length contained in an indexed row of a table configured by radio resource control (RRC); And performing a PUSCH transmission using respectively determined assigned resources for the initial PUSCH transmission and for said at least one repetition thereof; And wherein the determination of the assigned resources is based on at least one additional value contained in an indexed row of a table configured by Radio Resource Control (RRC) that determines the assigned resources in the time domain for the at least one repetition of the initial PUSCH transmission. 13. A method for receiving and transmitting signals for a user equipment (UE), including: receiving a physical uplink shared channel (PUSCH) configuration information element (IE) in the form of radio resource control (RRC) signals, wherein said PUSCH configuration information element (IE) is applicable to a specific portion of the bandwidth; configuring a table which is specified by the PUSCH Time Domain Resource Assignment List Information Element (IE) carried in the received PUSCH Configuration Information Element (IE), said table having rows each containing a value indicating a PUSCH mapping type, value K ₂ , indicating the slot offset, and an SLIV value indicating the start and length indicator; receiving a configurable grant configuration information element (IE) in the form of Radio Resource Control (RRC) signals carrying a time-domain destination field having a value of m, wherein said value of m provides an m+1 row index for a table configured by Radio Resource Control (RRC), determining assigned resources for the initial PUSCH transmission and assigned resources for at least one repetition thereof based on: - the values of the time domain offset field optionally carried in the received Configurable Grant Configuration Information Element (IE) and associated with the time domain assignment field, and - a value of K ₂ indicating a slot offset and a value of SLIV indicating a start indicator and a length contained in an indexed row of a table configured by radio resource control (RRC); And performing a PUSCH transmission using respectively determined assigned resources for the initial PUSCH transmission and for said at least one repetition thereof; And wherein the determination of the assigned resources is based on at least one additional value contained in an indexed row of a table configured by Radio Resource Control (RRC) that determines the assigned resources in the time domain for the at least one repetition of the initial PUSCH transmission. 14. Base station (BS), containing: a transmitter that, during operation, transmits a Physical Uplink Shared Channel (PUSCH) Configuration Information Element (IE) in the form of Radio Resource Control (RRC) signals, said PUSCH Configuration Information Element (IE) being applicable to a particular portion of the bandwidth; a processor that, during operation, configures a table that is specified by a PUSCH Time Domain Resource Assignment List Information Element (IE) carried in a received PUSCH Configuration Information Element (IE), said table containing rows each containing a value indicating a type displaying PUSCH, a K ₂ value indicating a slot offset, and an SLIV value indicating a start and length indicator; wherein said transmitter, during operation, transmits downlink control information (DCI) signals carrying a resource assignment field in the time domain having a value of m, said value of m providing an m+1 row index for a table configured by radio resource control (RRC), and said processor, during operation, allocates resources for the initial PUSCH transmission and allocates resources for at least one iteration thereof based on: - the slot number carrying the transmitted downlink control information (DCI), and - a value of K ₂ indicating a slot offset and a value of SLIV indicating a start indicator and a length contained in an indexed row of a table configured by radio resource control (RRC); And a receiver that, during operation, receives a PUSCH transmission using respectively assigned resources for an initial PUSCH transmission and for said at least one repeat thereof; And wherein the determination of the assigned resources is based on at least one additional value contained in an indexed row of a table configured by Radio Resource Control (RRC) that determines the assigned resources in the time domain for the at least one repetition of the initial PUSCH transmission. 15. Base station (BS), containing: a transmitter that, during operation, transmits a Physical Uplink Shared Channel (PUSCH) Configuration Information Element (IE) in the form of Radio Resource Control (RRC) signals, said PUSCH Configuration Information Element (IE) being applicable to a particular portion of the bandwidth; a processor that, during operation, configures a table that is specified by a PUSCH Time Domain Resource Assignment List Information Element (IE) carried in a received PUSCH Configuration Information Element (IE), said table containing rows each containing a value indicating a type displaying PUSCH, a K ₂ value indicating a slot offset, and an SLIV value indicating a start and length indicator; said transmitter, during operation, transmits a configurable grant configuration information element (IE) in the form of radio resource control (RRC) signals carrying a time-domain assignment field having a value of m, said value of m providing an m+1 row index for the table, configured radio resource control (RRC), and said processor, during operation, allocates resources for the initial PUSCH transmission and allocates resources for at least one iteration thereof based on: - the values of the time domain offset field optionally carried in the received Configurable Grant Configuration Information Element (IE) and associated with the time domain assignment field, and - a value of K ₂ indicating a slot offset and a value of SLIV indicating a start indicator and a length contained in an indexed row of a table configured by radio resource control (RRC); And a receiver that, during operation, receives a PUSCH transmission using respectively determined assigned resources for an initial PUSCH transmission and for said at least one repeat thereof; And wherein the determination of the assigned resources is based on at least one additional value contained in an indexed row of a table configured by Radio Resource Control (RRC) that determines the assigned resources in the time domain for the at least one repetition of the initial PUSCH transmission. 16. Integrated circuit for managing user equipment (UE), containing: a receiving circuit that, during operation, receives a Physical Uplink Shared Channel (PUSCH) Configuration Information Element (IE) in the form of Radio Resource Control (RRC) signals, said PUSCH Configuration Information Element (IE) being applicable to a specific portion of a bandwidth; a processing scheme that, during operation, configures a table that is specified by a PUSCH Time Domain Resource Assignment List Information Element (IE) carried in a received PUSCH Configuration Information Element (IE), said table containing rows each containing a value indicating a PUSCH mapping type, a K ₂ value indicating a slot offset, and an SLIV value indicating a start and length indicator; said receiving scheme, during operation, receives downlink control information (DCI) signals carrying a resource assignment field in the time domain having a value of m, wherein the value of m provides an m+1 row index for a table configured by radio resource control (RRC), and said run-time processing scheme determines the assigned resources for the initial PUSCH transmission and the assigned resources for at least one repetition thereof based on: - the slot number carrying the received downlink control information (DCI), and - a value of K ₂ indicating a slot offset and a value of SLIV indicating a start indicator and a length contained in an indexed row of a table configured by radio resource control (RRC); And a transmission scheme that, during operation, performs a PUSCH transmission using respectively determined assigned resources for an initial PUSCH transmission and for said at least one repeat thereof; And wherein the determination of the assigned resources is based on at least one additional value contained in an indexed row of a table configured by Radio Resource Control (RRC) that determines the assigned resources in the time domain for at least one repetition of the initial PUSCH transmission. 17. An integrated circuit for controlling a base station (BS), comprising: a transmission scheme that, during operation, transmits a physical uplink shared channel (PUSCH) configuration information element (IE) in the form of radio resource control (RRC) signals, said PUSCH configuration information element (IE) being applicable to a specific portion of a bandwidth; a processing scheme that, during operation, configures a table that is specified by a PUSCH Time Domain Resource Assignment List Information Element (IE) carried in a received PUSCH Configuration Information Element (IE), said table containing rows each containing a value indicating a PUSCH mapping type, a K ₂ value indicating a slot offset, and an SLIV value indicating a start and length indicator; wherein said transmission scheme during operation transmits downlink control information (DCI) signals carrying a resource assignment field in the time domain having a value of m, said value of m providing an m+1 row index for a table configured by radio resource control (RRC) , and said processing scheme during operation allocates resources for the initial PUSCH transmission and allocates resources for at least one iteration thereof based on: - the slot number carrying the transmitted downlink control information (DCI), and - a value of K ₂ indicating a slot offset and a value of SLIV indicating a start indicator and a length contained in an indexed row of a table configured by radio resource control (RRC); And a receiving scheme that, during operation, receives a PUSCH transmission using respectively assigned resources for an initial PUSCH transmission and for said at least one repetition thereof; And wherein the determination of the assigned resources is based on at least one additional value contained in an indexed row of a table configured by Radio Resource Control (RRC) that determines the assigned resources in the time domain for the at least one repetition of the initial PUSCH transmission.