CN117561766A - Transmitter for enhancing PUSCH repeated transmission - Google Patents

Abstract

Increasing the maximum number of repetitions of PUSCH leads to problems with interruption of higher priority transmissions and HARQ-ACK feedback delay. There is provided a transmitter for communicating in a communication system, the transmitter comprising circuitry configured to: the PUSCH repetition is transmitted based on PUSCH repetition type a, wherein for one PUSCH repetition, a minimum number of symbols is configured to improve the reliability of PUSCH decoding. The transmitter includes circuitry configured to: if the UCI carries hybrid automatic repeat request (HARQ) feedback, the UCI is multiplexed onto PUSCH transmission by puncturing some PUSCH symbols to improve HARQ-ACK feedback delay.

Description

Transmitter for enhancing PUSCH repeated transmission

Technical Field

The present disclosure relates to the field of wireless communication systems, and more particularly, to a transmitter for enhancing PUSCH retransmission.

Background

Wireless communication systems, such as third generation (3G) mobile phone standards and technologies, are well known, and the third generation partnership project (Third Generation Partnership Project,3 GPP) has developed such 3G standards and technologies, and generally, third generation wireless communication has been developed to the extent that macrocell mobile phone communication is supported, communication systems and networks have been developed toward broadband mobile systems. In a cellular wireless communication system, a User Equipment (UE) is connected to a radio access network (Radio Access Network, RAN) by a wireless link. The RAN includes a set of base stations (base stations) providing radio links to UEs located in cells (cells) covered by the base stations, and includes an interface to a Core Network (CN) having a function of controlling the overall Network. The RAN and CN each perform a corresponding function with respect to the entire network. The third generation partnership project has evolved a so-called long term evolution (Long Term Evolution, LTE) system, an evolved universal mobile telecommunications system regional radio access network (Evolved Universal Mobile Telecommunication System Territorial Radio Access Network, E-UTRAN), for a mobile access network of one or more macro cells supported by base stations called enodebs or enbs (evolved nodebs). Recently, LTE has evolved further to so-called 5G or New Radio (NR) systems, where one or more cells are supported by a base station called a gNB.

The 5G standard will support a number of different services, each with very different requirements. These services include enhanced mobile broadband (Enhanced Mobile Broadband, eMBB) technology for high-speed data transmission, ultra-reliable low-latency communication (URLLC) technology for devices requiring low latency and high link reliability, and mass Machine-Type Communication (mctc) technology for communications requiring high energy efficiency, long service life, to support a large number of low power devices.

A Base Station (BS) refers to a network center element in an NR for controlling one or more TRPs associated with one or more cells. The BS may refer to an eNB, nodeB, or gndeb (also referred to as gNB). For example, TRP is one transmission reception point that provides network coverage and communicates directly with the UE. A cell is made up of one or more associated TRPs, i.e. the coverage area of a cell is a superset of the coverage area of all individual TRPs associated with the cell. One cell is controlled by one base station. One cell may also be referred to as a TRP group (TRPG).

Physical Uplink Shared Channel (PUSCH) repetition may be scheduled to different TRPs at different transmission occasions, so that the UE may have multiple occasions to make PUSCH transmissions. Sending PUSCH repeated to different TRPs may avoid possible transmission blockage between TRPs or between any one TRP and the UE. Therefore, PUSCH repetition not only enhances reliability, but also improves coverage.

In release 15/16 specifications, PUSCH repetition of type a and type B has been specified. For PUSCH repetition of type a, the different repetitions of PUSCH are in different slots, which have the same length and starting symbol. For PUSCH repetition of type B, the nominal repetition is split into multiple actual repetitions as it crosses slot boundaries or invalid symbols. For PUSCH repetition of type a, the number of repetitions is determined by the higher layer parameters number ofrepetition-r 16 and PUSCH-aggregation factor. For PUSCH repetition of type B, the nominal number of repetitions is determined by the higher layer parameter numberofrepetition-r 16.

At the RAN #90 electronic conference, a new Rel-17 work item was approved for NR coverage enhancement. The goal of this work item is to normalize the enhanced functions of PUSCH, PUCCH and Msg3 PUSCH for FR1 and FR2 and TDD and FDD.

The detailed objectives are as follows:

● Specifications of PUSCH enhancement function [ RAN1, RAN4]

The following mechanism is specified to enhance PUSCH repetition type a [ RAN1]

■ The maximum number of repetitions is increased to a number, which is determined during operation.

■ The number of repetitions calculated from the available UL slots.

TB handling of PUSCH to support multiple timeslots [ RAN1] with a mechanism

■ The TBS is determined based on and transmitted over a plurality of time slots.

One or more mechanisms are specified to enable joint channel estimation [ RAN1, RAN4]

■ Based on the situation where power consistency and phase continuity are maintained, one or more mechanisms to implement joint channel estimation over multiple PUSCH transmissions will be studied and normalized by RAN4, if necessary [ RAN1, RAN4]

Feasible optimization of DMRS position/granularity in the time domain is not excluded

■ Inter-slot frequency hopping in inter-slot bundling to achieve joint channel estimation

[RAN1]

● Specifications of PUCCH enhancement function [ RAN1, RAN4]

Signaling mechanism to support dynamic PUCCH repetition factor indication [ RAN1]

Mechanism of DMRS bundling for specification support of repetition across PUCCH [ RAN1, RAN4]

● One or more mechanisms for PUSCH repetition of type A of Msg3 [ RAN1] are supported by specification

Furthermore, at the RANs 1#103 electronic conference, the following protocol related to PUSCH repetition type a is also passed:

protocol: incorporating the following into TR

● Enhancement of PUSCH repetition type a has been studied from several aspects, including increasing the maximum number of repetitions, the number of repetitions calculated based on the available UL slots, and flexible symbol resource allocation in different slots.

● Enhancements in terms of increasing the maximum number of repetitions, possible effects on the specification include:

TDRA (time domain resource allocation).

● The possible impact on the specification, based on the increase in the number of repetitions calculated for the available UL slots, includes:

TDRA (time domain resource allocation).

-a mechanism to determine the actual repeated transmission occasions.

-a mechanism to determine if a flexible special slot can be determined as an available UL slot.

● Enhancements in flexible symbol resource allocation in different slots, possible impacts on specifications include:

TDRA (time domain resource allocation).

-a mechanism to determine UL symbols for each slot.

Protocol: the following observations are incorporated into TR.

● The enhancement in PUSCH repetition type a is advantageous for PUSCH coverage enhancement for TDD. It is suggested to support enhancement of PUSCH repetition type a in Rel-17, including the following two options (possible next step selection in WI phase):

option 1: the maximum number of repetitions is increased, for example, up to 32.

O option 2: the number of repetitions calculated from the available UL slots.

Increasing the maximum number of repetitions of PUSCH leads to two problems: (1) PUSCH repetition may be interrupted by DL transmission on flexible symbols. (2) When the number of repetitions is large, the repeated transmission occupies a large amount of UL transmission resources, especially in TDD systems where UL transmission resources are limited.

Disclosure of Invention

A first aspect of the present application provides a transmitter for communicating in a communication system, the transmitter comprising: one or more interfaces configured to communicate with one or more parties within the communication system; and circuitry configured to: the method includes transmitting Physical Uplink Shared Channel (PUSCH) repetition based on PUSCH repetition type a, wherein in the PUSCH repetition type a, different PUSCH repetitions are located in different slots, wherein for one PUSCH repetition, a minimum number of symbols is configured.

A second aspect of the present application provides a transmitter for communicating in a communication system, the transmitter comprising: one or more interfaces configured to communicate with one or more parties within the communication system; and circuitry configured to: uplink Control Information (UCI) is multiplexed onto a Physical Uplink Shared Channel (PUSCH) repetition by puncturing some PUSCH symbols in the PUSCH repetition.

For example, the disclosed transmitter may be implemented by a UE, and the disclosed receiver may be implemented by a base station such as a gNodeB or by a TRP. In other cases, the transmitter/receiver may be implemented by a base station such as a gNodeB or by a TRP.

The disclosed transmitter may utilize this method, which may be programmed as computer-executable instructions stored in a non-transitory computer-readable medium that, when loaded into a computer, instruct the processor of the computer to perform the disclosed method. The disclosed methods can be programmed as a computer program product that causes a computer to perform the disclosed methods.

The non-transitory computer readable medium may include at least one of the group consisting of: hard disks, CD-ROMs, optical storage devices, magnetic storage devices, read-only memory, programmable read-only memory, erasable programmable read-only memory, electrically erasable programmable read-only memory, and flash memory.

To improve the reliability of PUSCH decoding, the UE may soft combine with different transport block sizes of PUSCH repetition. Two schemes of PUSCH repetition are proposed. In the first scheme, two transport block sizes of PUSCH repetition have systematic bits and parity bits, but the sizes of the systematic bits and parity bits are different. In a second scheme, the larger transport block in the PUSCH repetition has all systematic bits and a portion of the parity bits, and the smaller transport block in the PUSCH repetition has the remaining parity bits, which is considered an extension of the larger transport block in the PUSCH repetition. To prevent HARQ-ACK feedback delay, two ways of multiplexing UCI at PUSCH occasions by puncturing certain PUSCH symbols are proposed. ACK/NACK, SR and CSI are mapped into available symbols in a prioritized order according to UCI type priority. The first method is to map UCI to PUSCH opportunities by puncturing PUSCH symbols and place the UCI on symbols in the row direction on both sides of the DMRS. In the second approach, UCI is mapped onto PUSCH occasions by puncturing the available PUSCH symbols from top left to right.

Drawings

In order to more clearly illustrate the embodiments of the present disclosure or related techniques, the drawings described in the embodiments below are briefly introduced as follows. It is apparent that these drawings represent only some embodiments in the present application, and that one of ordinary skill in the art can derive other drawings from these drawings without making a preset.

Fig. 1 shows a schematic diagram of PUSCH repetition based on available UL slots.

Fig. 2 shows a schematic diagram of PUSCH repetition with smaller transport blocks.

Fig. 3 shows a schematic diagram of soft combining of different PUSCH repetitions.

Fig. 4 shows a schematic diagram of PUSCH repetition with different transport block sizes.

Fig. 5 shows a schematic diagram of PUSCH repetition with segmentation.

Fig. 6 shows a schematic diagram of PDSCH scheduling restriction when PUSCH repetition is scheduled.

Fig. 7 shows a schematic diagram of mapping UCI onto PUSCH occasions by puncturing PUSCH symbols on both sides of a DMRS.

Fig. 8 shows a schematic diagram of mapping UCI onto PUSCH occasions by puncturing available PUSCH symbols from top left to right.

Fig. 9 shows a block diagram of an exemplary system for wireless communication according to an embodiment of the present application.

Detailed Description

The embodiments of the present application will be described in detail below with reference to the accompanying drawings in terms of technical solutions, structural features, achieved objects, and effects. In particular, the terminology used in the embodiments of the present application is used only for the purpose of describing certain embodiments and is not intended to be limiting of the present application.

For ease of understanding, it is noted that in some cases the term "transmitter" may be implemented by the UE, while the term "receiver" may be implemented by a base station such as a gmodeb or by TRP. In other cases, the transmitter/receiver may be implemented by a base station such as a gNodeB or by a TRP. However, this should not be seen as limiting the interpretation of the invention.

The following abbreviations are used in this disclosure.

3GPP third Generation partnership project

ACK acknowledgement

CI cancel indicator

CRC cyclic redundancy check

CSI channel state information

DCI downlink control information

DMRS demodulation reference signal

gNB generation node B

HARQ hybrid automatic repeat request

NACK negative acknowledgement

NR new radio

NTN non-regional network

PDCCH physical downlink control channel

PDSCH physical downlink shared channel

PUCCH physical uplink control channel

PUSCH physical uplink shared channel

RAN radio access network

RE resource element

Rel release version

TDD time division duplexing

TRP transmission receiving point

SFI slot format indicator

UCI uplink control information

UE user equipment

UL Uplink (Uplink)

Currently, NR supports PUSCH repetition type a, with a maximum number of repetitions up to 16. It is recommended to increase this limit to 32. The main motivation for increasing the maximum number of repetitions comes from the desire to enable NTNs to connect to smartphones rather than just satellite phones. The goal here is to achieve a low data rate service that can tolerate high delays. Short message service, voIP, etc. are potential applications. Compared with satellite phones, the antenna gain of the smart phone is reduced, and the uplink coverage gap is larger. Repetition is considered as the primary means of compensating for coverage loss.

However, increasing the maximum number of repetitions of PUSCH leads to two problems: (1) PUSCH repetition may be interrupted by DL transmission on flexible symbols. PUSCH retransmission resources may become unavailable due to being occupied by PUCCH, SFI, CI and higher priority transmissions. (2) When the number of repetitions is high, the repeated transmission will occupy a large amount of UL transmission resources, especially in TDD systems where UL transmission resources are limited. In this case, if there is UCI carrying HARQ-ACK feedback, HARQ-ACK will have to wait until PUSCH repeated transmission has been completed. Delay sensitive services do not work properly.

To solve the above problem, the present application proposes to transmit PUSCH repetition with a minimum number of symbols, and map UCI onto PUSCH occasions by puncturing some PUSCH symbols.

Examples

The present application contemplates PUSCH repetition for coverage enhancement. Different schemes are presented for PUSCH repetition below to enhance PUSCH coverage.

1. Increasing the maximum number of repetitions

In release 15/16 specifications, PUSCH repetition of type a and type B has been specified. For PUSCH repetition of type a, the different repetitions of PUSCH are in different slots, which have the same length and starting symbol. For PUSCH repetition of type B, the nominal repetition is split into multiple actual repetitions as it crosses slot boundaries or invalid symbols.

In Rel-15, the maximum number of repetition types a is 8 and the number of slots for pusch repetition is {2,4,8}. In Rel-16, the maximum number of repetition types a has increased to 16, and the number of slots for pusch repetition is {1,2,3,4,7,8,12,16}. Further, the repeated PUSCH transmission in Rel-15 is semi-statically determined, while the number of repetitions may be dynamically indicated in DCI for scheduling PUSCH in Rel-16.

In R16, the repetition number is configured in the PUSCH time domain allocation list, as shown by the parameter numberofrepetition-R16 below.

In a later version of the standard, PUSCH coverage still needs to be enhanced. An increase in the number of repetitions may enhance coverage. Thus, a solution is proposed in which the maximum number of repetitions is increased to greater than or equal to 32. It can be observed that the BLER gain for 32 repetitions is almost 3dB compared to 16 repetitions, and that the gain increases with increasing number of repetitions. However, in some scenarios, 32 PUSCH repetitions may result in double delay and over allocation of UL resources. To address this problem, the number of repetitions of some candidates should be considered to achieve finer granularity, e.g., 18, 20, 24, 28, etc.

As described above, to support an increase in the maximum number of repetitions in subsequent versions of the standard, an additional maximum number of repetitions may be appended to the time-domain allocation list of R16, as shown by the following parameter numberofrepetition-R17:

thus, in one embodiment, a scheme of expanding the maximum number of repetitions to be greater than or equal to 32 for PUSCH repetition type a is proposed, where the maximum number of repetitions of PUSCH repetition type a may be 32; in another embodiment, it is proposed that for PUSCH repetition type a, some candidates should be considered to obtain finer repetition granularity, e.g. 18, 20, 24, 28.

Increasing the number of PUSCH repetition type a repetitions may enhance coverage. Thus, NTN connections may be implemented in smartphones. Applications that can tolerate large delays, such as short message service, voIP, etc., are potential applications. Furthermore, to obtain finer repetition granularity, only some candidates of the repetition number are considered.

2. Soft combining

In a TDD system, UL repeated transmissions may be interrupted by DL transmissions on flexible symbols due to UL/DL slot configuration. Furthermore, PUSCH retransmission resources may become unavailable due to being covered by PUCCH, SFI, CI and higher priority transmissions, as shown in fig. 1. In these cases, PUSCH occasions still count for the number of repetitions, whether or not the PUSCH is actually transmitted. Then the actual number of repetitions may be reduced. If the number of repetitions remains constant, the opportunity for unavailable PUSCH results in transmission performance that is not ideal and then requires retransmission, which can lead to delays and waste of transmission resources. However, as described above, a larger number of repetitions may also result in excessive allocation of PUSCH repetitions.

For interruption problems caused by higher priority transmissions, some conventional techniques involve dropping or deferring PUSCH repetition. The advantage of discarding duplicates is that no extra delay is created; however, delay has not been a major issue when PUSCH coverage as the actual target is degraded, especially for configuring authorized PUSCH. Considering that the number of repetitions is chosen in order to have a certain coverage, the coverage may thus be affected if not all repetitions are transmitted. The advantage of deferring repetition is that PUSCH can be received with the required reliability, since all repetitions are already transmitted. However, the delay may increase and even HARQ stalling may occur. It is also considered that deferring the use of resources will have an impact on scheduling which requires reserving resources to accommodate additional transmissions within a specific time period.

To resolve collisions between PUSCH repetition transmissions and PUCCH, SFI, CI and higher priority transmissions, PUSCH repetition of smaller symbols may be configured. For PUSCH repetition type a, the UE may transmit PUSCH repetition in one slot only when there are L consecutive UL symbols. If the transmission is less than L consecutive UL symbols, a minimum number of symbols for PUSCH repetition may be configured, with the starting symbol being an S symbol.

As shown in fig. 2, PUCCH should be transmitted in slot #n+1 and configure a start symbol s=0 and a consecutive symbol number l=4. In this case, the minimum number of symbols for PUSCH repetition may also be configured. If symbols 4 to 12 are indicated as UL symbols in slot #n+1, the UE may transmit PUSCH repetition configured with a start symbol s=4 and a consecutive symbol number l=9.

The PUSCH repetition type a may be proposed to be less than L in length to avoid performing undesirable and re-transmissions.

As shown in the example above, the start symbol s=2 and the consecutive symbol number l=11 can be considered as a larger transport block. The start symbol s=4 and the consecutive symbol number l=9 can be considered as a smaller transport block. If the PUSCH repetition cannot be decoded alone, different PUSCH repetitions may be soft combined to improve PUSCH decoding success. As shown in fig. 3, the two repetitions are sent on two different monitoring occasions. The UE blindly detects the first PUSCH transmission on monitoring occasion 1. If the first PUSCH is not decoded, the UE will repeat soft combining with a different PUSCH. Since the coded bits consist of two sets of parity bits in different PUSCH repetitions, the resulting code rate will be lower than the first transmission. However, this improves the reliability of PUSCH decoding.

Soft combining of different repeated PUSCH at different monitoring occasions is proposed. The UE may soft-combine the different-sized transport blocks repeated for PUSCH to improve the reliability of PUSCH decoding.

2.1 different sized parity bits and systematic bits transmitted in PUSCH repetition

Repeated transmissions add redundancy bits. Each repetition has a set of coded bits that are different from the previous transmission. As shown in fig. 4, PUSCH repetition of a larger transport block has larger systematic bits and parity bits, while PUSCH repetition of a smaller transport block has smaller systematic bits and parity bits. Thus, different PUSCH repetitions may consist of different groups of systematic bits and parity bits. All previously received data packets may be stored in the buffer. The UE may combine the additional redundancy bits with the previous transmission of the same data packet. At each repetition, the UE obtains additional information. Thus, the code rate is reduced. Each redundancy version with a high code rate should be part of a low code rate mother code.

It is proposed to construct PUSCH repetition with systematic bits and parity bits of different sizes to improve the reliability of PUSCH decoding. More specifically, two transport blocks of PUSCH repetition have systematic bits and parity bits, but the two systematic bits and parity bits are different in size.

2.2 transmission of systematic bits only in PUSCH repetition of longer symbols

The systematic bits are composed of DCI and CRC. Fig. 5 shows a first part of the coded bits with systematic bits that can be transmitted in PUSCH repetition 1, the remaining coded bits would be transmitted in PUSCH repetition 2. For example, when the DCI configures two repetitions, the coded bits of the DCI are divided into two parts. The first part is transmitted in repetitions of a larger transport block, while the second part is a repetition of a smaller transport block. In this way, only PUSCH repetition for a larger transport block may be self-decodable, as it includes all systematic bits and a portion of the parity bits. In this case, the PUSCH repetition of the subsequent smaller transport block may be regarded as an extension of the PUSCH repetition of the larger transport block.

It is proposed to transmit systematic bits only in PUSCH repetition of a larger transport block, and to transmit remaining parity bits in PUSCH repetition of a smaller transport block, to improve reliability of PUSCH decoding. More specifically, the PUSCH repetition of a larger transport block has all systematic bits and a portion of the parity bits, while the PUSCH repetition of a smaller transport block has the remaining parity bits, which is considered an extension of the PUSCH repetition of a larger transport block.

For the interrupt problem caused by higher priority transmissions. Compared to the conventional way of repeating dropping and deferring, the present application proposes PUSCH repetition of smaller transport block size that can avoid dropping and deferring. Soft combining of PUSCH repetition of different sizes may even improve the reliability of decoding.

UCI multiplexing on PUSCH repetition

In the current specification, if the UE detects DCI scheduling PUSCH transmission in a previous slot and HARQ-ACK information is multiplexed to PUSCH transmission, the UE does not expect to detect one DCI in a subsequent slot, which indicates PUCCH resources for HARQ-ACK. When the number of repetitions is large, the repeated transmission occupies a large amount of UL transmission resources, especially in TDD systems where UL transmission resources are limited. In this case, if there is UCI carrying HARQ-ACK feedback, as shown in fig. 6, HARQ-ACK will have to wait until PUSCH repetition is completed, and time-sensitive services may not work properly.

To overcome this drawback, a more relaxed timeline can be achieved if UCI is mapped to PUSCH occasions by puncturing some PUSCH symbols, since the UE does not need to regenerate the baseband signals of all symbols in PUSCH resources.

The UCI information mainly includes: SR (scheduling request), CQI (channel quality indicator), PMI (precoding matrix indicator), RI (rank indication), ACK (acknowledgement) and NACK (negative acknowledgement). CQI, PMI, and RI are included in Channel State Information (CSI). In one embodiment, the priority of UCI type is HARQ-ACK/NACK > SR > CSI. The UCI data may be prioritized and mapped based on the UCI type according to the number of symbols of PUSCH that can be punctured. In other words, HARQ-ACK/NACK should be prioritized when PUSCH symbols that can be punctured are limited.

It is proposed to map UCI to PUSCH transmission occasions by puncturing PUSCH symbols according to UCI type priority.

3.1 puncturing by available symbols on both sides of DMRS

UCI is punctured and mapped and placed on symbols of columns on both sides of a demodulation reference signal (DMRS). According to the priority of the UCI type, ACK/NACK is first mapped as shown in fig. 7. If all ACK/NACK are mapped and there are more symbols available on both sides of the DMRS, the SR and CSI can also be mapped according to type priority. The ACK/NACK transmission may be mapped using the opposite frequency direction as the CQI/PMI. When the ACK/NACK information needs to occupy a large number of Resource Elements (REs), the ACK/NACK information may cover the CQI/PMI, thereby protecting more important ACK/NACK information.

It is proposed to map UCI to PUSCH transmission occasions by puncturing PUSCH symbols according to the priority of UCI type and place them on symbols of columns on both sides of DMRS.

3.2 puncturing available symbols in order from top left to right

UCI is punctured and mapped and placed on available symbols in order from top left to right as shown in fig. 8. Starting from the symbol on the upper left side of the top row, the available symbols are punctured until the right side for UCI mapping. When the top row has no available symbols, the available symbols of the second row from above continue to be punctured from left to right. Additional UCI, such as ACK/NACK, SR, and CSI, is mapped to the available PUSCH symbols according to the priority of the UCI type. The mapping may protect the existing UCI starting from the position of the existing UCI.

It is proposed to map UCI to PUSCH transmission occasions by puncturing available PUSCH symbols from top left to right according to UCI type priority.

For the problem of HARQ-ACK feedback delay, some conventional techniques involve removing the timeline constraint to facilitate downlink scheduling and HARQ-ACK feedback. However, removing the inter-time constraint will result in more stringent time for UCI multiplexing on PUSCH repetition.

In Rel-16, NR supports PUSCH repetition type a with a maximum repetition number of 16. The present application proposes to increase this limit to greater than or equal to 32 (e.g., equal to 32). However, increasing the maximum number of repetitions of PUSCH causes problems with interruption of high priority transmission and HARQ-ACK feedback delay. To solve these problems, the present application proposes PUSCH repetition of smaller transport blocks and UCI multiplexing scheme by puncturing PUSCH symbols.

For smaller transport blocks in PUSCH, to improve reliability of PUSCH decoding, the UE may soft combine with different transport block sizes of PUSCH repetition. Two schemes of PUSCH repetition are proposed. In the first scheme, two transport block sizes of PUSCH repetition have systematic bits and parity bits, but the sizes of the systematic bits and parity bits are different. In a second scheme, the larger transport block in the PUSCH repetition has all systematic bits and a portion of the parity bits, and the smaller transport block in the PUSCH repetition has the remaining parity bits, which is considered an extension of the larger transport block in the PUSCH repetition.

For puncturing PUSCH symbols for UCI multiplexing, two ways of multiplexing UCI at PUSCH occasions by puncturing some PUSCH symbols are proposed. ACK/NACK, SR and CSI are mapped into available symbols in a prioritized order according to UCI type priority. The first method is to map UCI to PUSCH opportunities by puncturing PUSCH symbols and place the UCI on symbols in the row direction on both sides of the DMRS. In a second approach, UCI is mapped onto PUSCH occasions by puncturing available PUSCH symbols from top left to right, and ACK/NACK, SR and CSI are mapped into available symbols in a prioritized order according to UCI type priority. The first method is to map UCI to PUSCH opportunities by puncturing PUSCH symbols and place the UCI on symbols in the row direction on both sides of the DMRS. In the second approach, UCI is mapped onto PUSCH occasions by puncturing the available PUSCH symbols from top left to right.

Fig. 9 is a block diagram of an example system 1300 for wireless communication in accordance with an embodiment of the present disclosure. The embodiments described herein may be implemented into the system using any suitably configured hardware and/or software. Fig. 9 illustrates a system 1300, the system 1300 comprising Radio Frequency (RF) circuitry 1310, baseband circuitry 1320, processing unit 1330, memory/storage 1340, display 1350, camera 1360, sensor 1370, and input/output (I/O) interface 1380, coupled to one another as shown.

Processing unit 1330 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. A processor may include any combination of general-purpose and special-purpose processors (e.g., graphics processors and application processors). The processor may be coupled with the memory/storage device and configured to execute instructions stored in the memory/storage device to enable various application programs and/or an operating system to run on the system.

Baseband circuitry 1320 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The processor may comprise a baseband processor. The baseband circuitry may handle various radio control functions that enable communication with one or more radio networks via the RF circuitry. Radio control functions may include, but are not limited to, signal modulation, encoding, decoding, radio frequency shifting, and the like. In some embodiments, the baseband circuitry may provide communications compatible with one or more wireless technologies. For example, in some embodiments, the baseband circuitry may support communication with 5G NR, LTE, evolved Universal Terrestrial Radio Access Network (EUTRAN), and/or other wireless wide area networks (WMANs), wireless Local Area Networks (WLANs), wireless Personal Area Networks (WPANs). An embodiment in which the baseband circuitry is configured to support wireless communications for more than one wireless protocol may be referred to as a multi-mode baseband circuitry. In various embodiments, baseband circuitry 1320 may include circuitry to operate with signals that are not strictly considered to be in baseband frequency. For example, in some embodiments, the baseband circuitry may include circuitry to operate with signals having an intermediate frequency between the baseband frequency and the radio frequency.

RF circuitry 1310 may use modulated electromagnetic radiation to enable communication with a wireless network through a non-solid medium. In various embodiments, the RF circuitry may include switches, filters, amplifiers, and the like to facilitate communication with the wireless network. In various embodiments, RF circuit 1310 may include circuitry for operating with signals that are not strictly considered to be at radio frequencies. For example, in some embodiments, the RF circuitry may include circuitry for operating with signals having an intermediate frequency between baseband and radio frequencies.

In various embodiments, the transmitter circuitry, control circuitry, or receiver circuitry discussed above with respect to the user equipment, eNB, gNB, or TRP may be implemented in whole or in part in one or more of RF circuitry, baseband circuitry, and/or processing units. As used herein, "circuitry" may refer to, be part of, or include the following: an Application Specific Integrated Circuit (ASIC), an electronic circuit executing one or more software or firmware programs, a processor and/or memory (shared, dedicated, or group), a combinational logic circuit, and/or other suitable hardware components that provide the described functionality. In some embodiments, the electronic device circuitry may be implemented in or the functionality associated with one or more software or firmware modules. In some embodiments, some or all of the constituent components of the baseband circuitry, processing unit, and/or memory/storage may be implemented together on a system-on-a-chip (SOC).

Memory/storage 1340 may be used to load and store data and/or instructions for the system, for example. The memory/storage of an embodiment may include any combination of suitable volatile memory (e.g., dynamic Random Access Memory (DRAM)) and/or non-volatile memory (e.g., flash memory). In various embodiments, I/O interface 1380 may include one or more user interfaces designed to enable a user to interact with the system and/or peripheral component interfaces designed to enable peripheral components to interact with the system. The user interface may include, but is not limited to, a physical keyboard or keypad, a touchpad, a speaker, a microphone, and the like. The peripheral component interface may include, but is not limited to, a non-volatile memory interface, a Universal Serial Bus (USB) interface, an audio jack, and a power interface.

In various embodiments, the sensor 1370 may include one or more sensing devices for determining environmental conditions and/or location information related to the system. In some embodiments, the sensors may include, but are not limited to, gyroscopic sensors, accelerometers, proximity sensors, ambient light sensors, and positioning units. The positioning unit may also be part of or interact with baseband circuitry and/or RF circuitry to communicate with components of a positioning network, such as Global Positioning System (GPS) satellites. In various embodiments, the display 1350 may include a display such as a liquid crystal display and a touch display. In various embodiments, system 1300 may be a mobile computing device such as, but not limited to, a laptop computing device, a tablet computing device, a netbook, a superbook, a smartphone, and the like. In various embodiments, the system may have more or fewer components and/or different architectures. The methods described herein may be implemented as computer programs, where appropriate. The computer program may be stored on a storage medium such as a non-transitory storage medium.

Some embodiments of the present application are a combination of "technologies/procedures" that may be employed in 3GPP specifications to develop end products.

Those of skill in the art will appreciate that each of the elements, algorithms, and steps described and disclosed in the embodiments of the present application are implemented using electronic hardware, or combinations of software and electronic hardware for a computer. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the particular implementation. Those skilled in the art can implement the functionality of each particular application in different ways without such implementation exceeding the scope of the application. It will be appreciated by those skilled in the art that reference may be made to the operation of the systems, devices and units of the above embodiments, as the operation of the systems, devices and units is substantially the same. For ease of description and brevity, these operations will not be described in detail.

It should be understood that the systems, devices, and methods disclosed in the embodiments of the present application may be implemented in other manners. The embodiments described above are merely illustrative. The partitioning of the cells is based solely on logic functions, while other partitions exist when implemented. Multiple units or components may be combined or may be integrated into another system. Some features may be omitted or skipped. On the other hand, the mutual coupling, direct coupling or communicative coupling shown or discussed may be indirect coupling or electrical, mechanical or other form of communicative coupling via some interfaces, devices or units.

The units described as separate components may or may not be physically separate. The units shown may or may not be physical units, may be located in one place, or may be distributed over a plurality of network units. Some or all of the units may be used according to the purpose of the embodiment. In addition, each functional unit in each embodiment may be integrated in one processing unit, may be physically independent, or may be integrated in one processing unit.

If the software functional unit is implemented and sold or used as a stand-alone product, it may be stored in a readable storage medium in a computer. Based on such understanding, the technical solutions presented in the present application may be implemented essentially or partly in the form of a software product. Alternatively, a part of the technical solutions beneficial to the prior art may be implemented in the form of a software product. The software product in the computer is stored in a storage medium, including a plurality of commands for a computing device (e.g., a personal computer, a server, or a network device) to execute all or part of the steps disclosed in the embodiments of the present application. The storage medium includes a USB disk, a removable hard disk, a read-only memory (ROM), a random-access memory (RAM), a floppy disk, or other medium capable of storing program code.

While the present application has been described in connection with what is presently considered to be the most practical and preferred embodiment, it is to be understood that the present application is not limited to the disclosed embodiment, but is intended to cover various arrangements made without departing from the scope of the appended claims in its broadest interpretation.

Claims (11)

1. A transmitter for communicating in a communication system, the transmitter comprising:

one or more interfaces configured to communicate with one or more parties within the communication system; and

circuitry configured to:

PUSCH repetition is transmitted based on Physical Uplink Shared Channel (PUSCH) repetition type a,

wherein, in the PUSCH repetition type A, different PUSCH repetitions are located in different time slots,

wherein for one PUSCH repetition, a minimum number of symbols is configured.

2. The transmitter of claim 1, wherein the smallest number of symbols for PUSCH repetition configures a start symbol and a consecutive number of symbols.

3. The transmitter of claim 1, wherein at least two of the PUSCH repetitions have different types of lengths and are configured with different starting symbols.

4. The transmitter of claim 1, wherein the circuitry is further configured to:

soft combining is repeated for different PUSCHs on different monitoring occasions.

5. The transmitter of claim 1, wherein the PUSCH repetition consists of systematic bits and parity bits of different sizes.

6. The transmitter of claim 1, wherein the PUSCH repetition comprises a first PUSCH repetition having all systematic bits and a portion of parity bits for encoding bits of information, and a second PUSCH repetition having remaining parity bits considered as an extension of the first PUSCH repetition, and wherein the first PUSCH repetition has a larger transport block size than the second PUSCH repetition.

7. A transmitter for communicating in a communication system, the transmitter comprising:

one or more interfaces configured to communicate with one or more parties within the communication system; and

circuitry configured to:

uplink Control Information (UCI) is multiplexed onto a Physical Uplink Shared Channel (PUSCH) repetition by puncturing some PUSCH symbols in the PUSCH repetition.

8. The transmitter of claim 7, wherein the UCI is mapped to the PUSCH repetition transmission occasion according to the priority of UCI type.

9. The transmitter of claim 8, wherein the priority of the UCI type indicates that hybrid automatic repeat request (HARQ) feedback takes precedence over a scheduling Request (RI) of the UCI, which takes precedence over Channel State Information (CSI) of the UCI.

10. The transmitter of claim 7 wherein the UCI is mapped to transmission occasions of the PUSCH repetition by puncturing PUSCH symbols and placed on symbols of columns on both sides of a demodulation reference signal (DMRS).

11. The transmitter of claim 7, wherein the UCI is mapped to a transmission occasion of the PUSCH repetition by puncturing available PUSCH symbols from top left to right.