WO2022205286A1

WO2022205286A1 - Transmitter for improving pusch repetition transmission

Info

Publication number: WO2022205286A1
Application number: PCT/CN2021/084867
Authority: WO
Inventors: Jinghua Zhang; Jia SHENG
Original assignee: Tcl Communication(Ningbo) Co., Ltd.
Priority date: 2021-04-01
Filing date: 2021-04-01
Publication date: 2022-10-06
Also published as: CN117561766A

Abstract

Increasing the maximum repetition number of PUSCH leads to interruption by higher priority transmissions and HARQ-ACK feedback delay. Proposed is a transmitter configured to communicate in a communication system, and the transmitter includes a circuitry configured to transmit PUSCH repetitions based on PUSCH repetition type A, in which a minimum number of symbols for one PUSCH repetition is configured in order to increase the reliability of PUSCH decoding. In addition, the transmitter includes a circuitry configured to multiplex an uplink control information (UCI) in PUSCH transmission occasion by puncturing some PUSCH symbols if the UCI carries hybrid automatic repeat request (HARQ) feedback, in order to improve HARQ-ACK feedback delay.

Description

TRANSMITTER FOR IMPROVING PUSCH REPETITION TRANSMISSION

TECHNICAL FIELD

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

BACKGROUND ART

Wireless communication systems, such as the third-generation (3G) of mobile telephone standards and technology are well known. Such 3G standards and technology have been developed by the Third Generation Partnership Project (3GPP) . The 3rd generation of wireless communications has generally been developed to support macro-cell mobile phone communications. Communication systems and networks have developed towards being a broadband and mobile system. In cellular wireless communication systems, user equipment (UE) is connected by a wireless link to a radio access network (RAN) . The RAN includes a set of base stations (BSs) which provide wireless links to the UEs located in cells covered by the base station, and an interface to a core network (CN) which provides overall network control. The RAN and CN each conducts respective functions in relation to the overall network. The 3rd Generation Partnership Project has developed the so-called Long Term Evolution (LTE) system, namely, an Evolved Universal Mobile Telecommunication System Territorial Radio Access Network, (E-UTRAN) , for a mobile access network where one or more macro-cells are supported by a base station known as an eNodeB or eNB (evolved NodeB) . More recently, LTE is evolving further towards the so-called 5G or NR (new radio) systems where one or more cells are supported by a base station known as a next generation Node B called gNodeB (gNB) .

The 5G standard will support a multitude of different services each with very different requirements. These services include Enhanced Mobile Broadband (eMBB) for high data rate transmission, Ultra-Reliable Low Latency Communication (URLLC) for devices requiring low latency and high link reliability and Massive Machine-Type Communication (mMTC) to support a large number of low-power devices for a long life-time requiring highly energy efficient communication.

A base station (BS) refers to a network central unit in the NR that is used to control one or multiple TRPs associated with one or multiple cells. A BS could be referred to as, eNB, NodeB, or gNodeB (also called gNB) . A TRP is a transmission and reception point that provides network coverage and directly communicates with UEs, for example. A cell is composed of one or multiple associated TRPs, i.e. the coverage of the cell is a superset of the coverage of all the individual TRP (s) associated with the cell. One cell is controlled by one BS. A cell can also be referred to as a TRP group (TRPG) .

Physical Uplink Shared Channel (PUSCH) repetition can be scheduled in different transmission occasions toward different TRPs so that UE has multiple chances to perform PUSCH transmission. PUSCH repetition targeting towards different TRPs can avoid possible blockage between TRPs or between any TRP and the UE. As a result, PUSCH repetition not only enhance the reliability but also improve the coverage.

In Rel-15/16, PUSCH repetition type A and type B have been specified. For PUSCH repetition type A, different repetitions of PUSCH are in different slots, which have the same length and starting symbol. For PUSCH repetition type B, due to the crossing slot boundary or invalid symbols, a nominal repetition is divided into multiple actual repetitions. For PUSCH repetition type A, the number of repetitions is determined by the higher layer parameter numberOfRepetitions-r16 and pusch-AggregationFactor. For PUSCH repetition Type B, the number of nominal repetitions is determined by the higher layer parameter numberOfRepetitions-r16.

In RAN #90 e-meeting, a new Rel-17 work item on NR coverage enhancements was approved. The objective of this work item is to specify enhancements for PUSCH, PUCCH and Msg3 PUSCH for both FR1 and FR2 as well as TDD and FDD.

The detailed objectives are as follows.

● Specification of PUSCH enhancements [RAN1, RAN4]

○ Specify the following mechanisms for enhancements on PUSCH repetition type A [RAN1]

■ Increasing the maximum number of repetitions up to a number to be determined during the course of the work.

■ The number of repetitions counted on the basis of available UL slots.

○ Specify mechanism (s) to support TB processing over multi-slot PUSCH [RAN1]

■ TBS determined based on multiple slots and transmitted over multiple slots.

○ Specify mechanism (s) to enable joint channel estimation [RAN1, RAN4]

■ Mechanism (s) to enable joint channel estimation over multiple PUSCH transmissions, based on the conditions to keep power consistency and phase continuity to be investigated and specified if necessary by RAN4 [RAN1, RAN4]

○ Potential optimization of DMRS location/granularity in time domain is not precluded

■ Inter-slot frequency hopping with inter-slot bundling to enable joint channel estimation [RAN1]

● Specification of PUCCH enhancements [RAN1, RAN4]

○ Specify signaling mechanism to support dynamic PUCCH repetition factor indication [RAN1]

○ Specify mechanism to support DMRS bundling across PUCCH repetitions [RAN1, RAN4]

● Specify mechanism (s) to support Type A PUSCH repetitions for Msg3 [RAN1]

Furthermore, following agreements related to PUSCH repetition type A have been made in RAN1#103-e: Agreements: Capture the followings into the TR

● Enhancements on PUSCH repetition type A were studied from several aspects, including increasing the maximum number of repetitions, the number of repetitions counted on the basis of available UL slots and flexible symbol resource allocation in different slots.

● Potential specification impacts of enhancements on increasing the maximum number of repetitions include:

‐ TDRA (Time-Domain Resource Allocation) .

● Potential specification impacts of enhancements on the number of repetitions counted on the basis of available UL slots include:

‐ TDRA (Time-Domain Resource Allocation) .

‐ Mechanism to determine transmission occasion of actual repetition.

‐ Mechanism to determine whether flexible special slot can be determined as an available UL slot.

● Potential specification impacts of enhancements on flexible symbol resource allocation in different slots include:

‐ TDRA (Time-Domain Resource Allocation) .

‐ Mechanism to determine UL symbols for each slot.

Agreements: Capture the following observation into the TR.

● Enhancements on PUSCH repetition type A is beneficial for PUSCH coverage enhancements for TDD. It is recommended to support enhancements on PUSCH repetition type A in Rel-17, including the following two options (potential down-selection during the WI phase) :

○ Option 1: Increasing the maximum number of repetitions, e.g., up to 32.

○ Option 2: The number of repetitions counted on the basis of available UL slots.

TECHNICAL PROBLEM

Increasing the maximum repetition number of PUSCH leads to two issues: (1) PUSCH repetition may be interrupted by DL transmission on flexible symbols. (2) when the number of repetitions is high, the repetition transmission would occupy lots of UL transmission resource, especially in TDD systems where the UL transmission resources are limited.

TECHNICAL SOLUTION

A first aspect of the present disclosure provides a transmitter, configured to communicate in a communication system, the transmitter comprising: one or more interfaces configured to communicate with one or more parties within the communication system; and a circuitry configured to: transmit physical uplink shared channel (PUSCH) repetitions based on PUSCH repetition type A, wherein in the PUSCH repetition type A, different repetitions of PUSCH are in different slots, wherein a minimum number of symbols for one PUSCH repetition is configured.

A second aspect of the present disclosure provides a transmitter, configured to communicate in a communication system, the transmitter comprising: one or more interfaces configured to communicate with one or more parties within the communication system; and a circuitry configured to: multiplexing an uplink control information (UCI) in physical uplink shared channel (PUSCH) transmission occasion by puncturing some PUSCH symbols if the UCI carries hybrid automatic repeat request (HARQ) feedback.

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

The disclosed transmitter may utilize a method that may be programmed as computer executable instructions stored in non-transitory computer readable medium. The non-transitory computer readable medium, when loaded to a computer, directs a processor of the computer to execute the disclosed method. The method may be programmed as computer program product, that causes a computer to execute the disclosed method.

The non-transitory computer readable medium may include at least one from a group consisting of: a hard disk, a CD-ROM, an optical storage device, a magnetic storage device, a Read Only Memory, a Programmable Read Only Memory, an Erasable Programmable Read Only Memory, EPROM, an Electrically Erasable Programmable Read Only Memory and a Flash memory.

ADVANTAGEOUS EFFECTS

In order to increase the reliability of PUSCH decoding, UE can perform a soft combination with different transport-block sizes of PUSCH repetition. Two schemes composed of PUSCH repetition are proposed. In the first scheme, two transport-block sizes of PUSCH repetition have the systematic bits and parity bits, but the sizes of the systematic bits and parity bits are different. In the second scheme, the larger transport-block sizes of PUSCH repetition have all systematic bits and one part of parity bits, and the smaller transport-block sizes of PUSCH repetition have remaining parity bits which considered as an extension of the larger transport-block sizes of PUSCH repetition. In order to prevent HARQ-ACK feedback delay, two approaches of multiplexing UCI in PUSCH occasion by puncturing some PUSCH symbols are proposed. According to the UCI type priority, ACK/NACK, SR and CSI are mapped in the available symbols by priority. In the first approach, UCI is mapped to the PUSCH occasion by puncturing PUSCH symbols and placed on the columns of symbols on both sides of the DMRS. In the second approach, UCI is mapped to the PUSCH occasion by puncturing available PUSCH symbols from the top left to right.

DESCRIPTION OF DRAWINGS

In order to more clearly illustrate the embodiments of the present disclosure or related art, the following Figures that will be described in the embodiments are briefly introduced. It is obvious that the drawings are merely some embodiments of the present disclosure, a person having ordinary skill in this field can obtain other Figures according to these Figures without paying the premise.

Figure 1 is a schematic diagram illustrating PUSCH repetition on the basis of available UL slots.

Figure 2 is a schematic diagram illustrating PUSCH repetition with smaller transport-block sizes.

Figure 3 is a schematic diagram illustrating soft combining of different PUSCH repetitions.

Figure 4 is a schematic diagram illustrating PUSCH repetitions with different transport-block sizes.

Figure 5 is a schematic diagram illustrating PUSCH repetition with split parts.

Figure 6 is a schematic diagram illustrating PDSCH scheduling restriction when PUSCH repetition is scheduled.

Figure 7 is a schematic diagram illustrating that UCI is mapped to the PUSCH occasion by puncturing PUSCH symbols on the both sides of the DMRS.

Figure 8 is a schematic diagram illustrating that UCI is mapped to the PUSCH occasion by puncturing available PUSCH symbols from the top left to right.

FIG. 9 is a block diagram of an example system for wireless communication according to an embodiment of the present disclosure.

DETAILED DESCRIPTION OF EMBODIMENTS

Embodiments of the disclosure are described in detail with the technical matters, structural features, achieved objects, and effects with reference to the accompanying drawings as follows. Specifically, the terminologies in the embodiments of the present disclosure are merely for describing the purpose of the certain embodiment, but not to limit the disclosure.

For easy of understanding, it is noted that in some circumstance, the term transmitter may be implemented by a UE and the term receiver may be implemented by a base station such as gNodeB, or by a TRP, for example; in other circumstance, the transmitter/receiver may be implemented by a base station such as gNodeB, or by a TRP, for example. However, this should not be taken as a limitation to interpretation of this invention.

The following abbreviations are used in the present disclosure.

3GPP Third Generation Partnership Project

ACK Acknowledgment

CI Cancellation 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 acknowledgment

NR New Radio

NTN Non-Terrestrial 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

TDD Time Division Duplex

TRP Transmission/Reception Point

SFI Slot Format Indicator

UCI Uplink Control Information

UE User Equipment

UL Uplink

Currently, NR supports PUSCH repetition type A with a maximum repetition number up to 16. It is proposed to increase this limit to 32. The primary motivation for this increase comes from a desire to enable NTN connectivity to smartphones and not just satellite phones. The goal here is to enable low data rate services that can tolerate large latencies. Short message services, VoIP, etc are potential applications. Compared to satellite phones, smartphones suffer from reduced antenna gain and a wider gap in uplink coverage. Repetitions are viewed as a primary means to recover this loss in coverage.

However, increasing the maximum repetition number of PUSCH leads to two issues: (1) PUSCH repetition may be interrupted by DL transmission on flexible symbols. PUSCH repetition transmission resource can be unavailable due to being overridden by PUCCH, SFI, CI and higher priority transmissions (2) when the number of repetitions is high, the repetition transmission would occupy lots of UL transmission resource, especially in TDD systems where the UL transmission resources are limited. In this case, if there is a UCI carrying HARQ-ACK feedback, HARQ-ACK would have to wait until PUSCH repetitions have been finished. Latency-sensitive services could not work well.

In order to address the above issues, this disclosure proposes to transmit PUSCH repetition with a minimum number of symbols, and UCI is mapped to the PUSCH occasion by puncturing some PUSCH symbols.

Embodiments

This disclosure considers PUSCH repetition for coverage enhancement. It proposes different approaches in the following for PUSCH repetition in order to enhance the coverage of PUSCH.

1. Increase the maximum number of repetition

In Rel-15/16, PUSCH repetition type A and type B have been specified. For PUSCH repetition type A, different repetitions of PUSCH are in different slots, which have the same length and starting symbol. For PUSCH repetition type B, due to the crossing slot boundary or invalid symbols, a nominal repetition is divided into multiple actual repetitions.

In Rel-15, the maximum number of repetition type A is 8, the number of slots for PUSCH repetitions is {2, 4, 8} . In Rel-16, the maximum number of repetition type A has been 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 can be dynamically indicated in the DCI for scheduling PUSCH in Rel-16.

In R16, the number of repetition is conFigure in the PUSCH time domain allocation list as indicated in a parameter numberOfRepetitions-r16 below.

PUSCH-Allocation-r16 : : = SEQUENCE {

mappingType-r16 ENUMERATED {typeA, typeB} OPTIONAL, --Cond NotFormat01-02-Or-TypeA

startSymbolAndLength-r16 INTEGER (0.. 127) OPTIONAL, --Cond NotFormat01-02-Or-TypeA

startSymbol-r16 INTEGER (0.. 13) OPTIONAL, --Cond RepTypeB

length-r16 INTEGER (1.. 14) OPTIONAL, --Cond RepTypeB

numberOfRepetitions-r16 ENUMERATED {n1, n2, n3, n4, n7, n8, n12, n16} OPTIONAL, --Cond Format01-02

...

The PUSCH coverage still needs to be enhanced in later version of the standard. Increasing the number of repetitions can enhance coverage. A solution for the maximum number of repetitions is thus proposed to increase to a number greater than or equal to 32. It is observed that there is almost 3dB BLER gain with 32 repetitions compared to 16 repetitions, and the gain increases with the number of repetitions. However, 32 PUSCH repetition will result in a doubling of delay and over-allocated UL resources in some scenarios. To solve this issue, some candidate number of repetitions should be considered to achieve the finer granularity, e.g. 18, 20, 24, 28 etc.

As discussed above, to support increase the maximum number of repetitions in later version of the standard, the additional maximum repetitions can be appended to the R16 time domain allocation list as indicated in a parameter numberOfRepetitions-r17 below:

PUSCH-Allocation-r17 : : = SEQUENCE {

mappingType-r17 ENUMERATED {typeA, typeB} OPTIONAL, --Cond NotFormat01-02-Or-TypeA

startSymbolAndLength-r17 INTEGER (0.. 127) OPTIONAL, --Cond NotFormat01-02-Or-TypeA

startSymbol-r17 INTEGER (0.. 13) OPTIONAL, --Cond RepTypeB

length-r17 INTEGER (1.. 14) OPTIONAL, --Cond RepTypeB

numberOfRepetitions-r17 ENUMERATED {n1, n2, n3, n4, n7, n8, n12, n16, n18, n20, n24, n28, n32} OPTIONAL, --Cond Format01-02

...

Therefore, in an embodiment, it is proposed that for PUSCH repetition type A, the maximum number of repetitions is extended to a number greater than or equal to 32, where the maximum number of repetitions for the PUSCH repetition type A can be just the number 32; in another embodiment, it is proposed that for PUSCH repetition Type-A, some candidate values should be considered to obtain the finer granularity of repetitions, e.g. 18, 20, 24, 28.

Increasing the number of repetitions for PUSCH repetition type A can enhance coverage. Therefore, NTN connectivity is enabled for smartphones. Applications that can tolerate large latencies, such as Short message services, VoIP, etc, are potential applications. Further, in order to obtain the finer granularity of repetitions, it is considered only some candidate values for the number of repetitions.

2. Soft combining

In TDD systems, due to UL/DL slot configuration, UL repetition transmission may be interrupted by DL transmission on flexible symbols. Besides, PUSCH repetition transmission resource can be unavailable due to being overridden by PUCCH, SFI, CI and higher priority transmissions as shown in Figure 1. In these cases, the PUSCH occasion is still counted in the number of repetitions regardless of whether the PUSCH is actually transmitted. Then actual number of repetitions could be reduced. If the number of repetitions is conservative, the unavailable PUSCH occasions would cause unsatisfactory performance, and then the retransmission is needed, which leads to latency and waste of transmission resources. However, as mentioned above, the larger number of repetitions also result in over-allocation for PUSCH repetition.

For the issue of interruption by higher priority transmissions, some conventional skills involve dropping or postponing the PUSCH repetition. Dropping repetitions has the advantage of no additional latency; however, latency is already not a major concern while PUSCH coverage that is the actual objective can be degraded, especially for configured grant PUSCH. Considering that the number of repetitions is chosen in order to have certain coverage, if not all repetitions are transmitted, coverage can be impacted. Postponing repetitions has the advantage that PUSCH is received with the required reliability because all repetitions are transmitted. However, latency will increase, and there may even be HARQ stalling. It also needs to be considered that postponing use of resources will have an impact on the scheduling which needs to reserve resources to accommodate the additional transmissions within a certain time period.

To address the collision by PUCCH, SFI, CI and higher priority transmissions during PUSCH repetition transmissions, smaller symbol PUSCH repetition can be configured. For PUSCH repetition Type A, a UE can transmit PUSCH repetition in a slot only if there are L consecutive UL symbols. If the transmission with fewer than L consecutive UL symbols, a minimum number of symbols for a PUSCH repetition can be configured with starting symbol being the S symbol.

As shown in Figure 2, the PUCCH should be transmitted in the Slot #n+1 and configured with the starting symbol S=0 and the number of consecutive symbols L=4. In this case, a minimum number of symbols for a PUSCH repetition can also be configured. If symbols 4 through 12 are indicated as UL symbols in slot #n+1, a UE can transmit PUSCH repetition which is configured with the starting symbol S=4 and the number of consecutive symbols L=9.

It is proposed that the length of PUSCH repetition Type A can be smaller than L for avoiding unsatisfactory performance and retransmission.

As shown in the above example, the starting symbol S=2 and the number of consecutive symbols L=11 can be considered as larger transport-block sizes. The starting symbol S=4 and the number of consecutive symbols L=9 can be considered as smaller transport-block sizes. If the PUSCH repetitions cannot be decoded separately, the different PUSCH repetitions can perform a soft combination to increase the PUSCH decoding. As shown in Figure 3, two repetitions are transmitted on two different monitoring occasions. The UE performs blind detection on the first PUSCH transmission in the monitoring occasion 1. If the first PUSCH is not decoded, the UE will perform a soft combination with different PUSCH repetitions. The resulting code rate is lower than the first transmission since the coded bits consist of two sets of parity bits in different PUSCH repetition. However, it increases the reliability of PUSCH decoding.

It is proposed to perform soft combining of different repeated PUSCHs in different monitoring occasion. UE can perform a soft combination with different transport-block sizes of PUSCH repetition for increasing the reliability of PUSCH decoding.

2.1 Different sizes of systematic bits and parity bits transmitted in PUSCH repetitions

The repetition transmits increments of redundant bits. Each repetition has a different set of coded bits than the previous transmission. As shown in the Figure 4, the larger transport-block sizes PUSCH repetition has larger sizes of the systematic bits and parity bits, and the smaller transport-block sizes PUSCH repetition has smaller sizes of systematic bits and parity bits. Therefore, the different PUSCH repetitions can consist of different sets of systematic bits and parity bits. All previously received packets can be stored in a buffer. The UE can combine additional redundant bits with the previous transmission of the same packet. At every repetition, the UE gains extra information. So that the code rate is decreased. Each redundancy version with a high code rate should be part of the low rate mother code.

It is proposed that the PUSCH repetitions are constructed with different sizes of systematic bits and parity bits for increasing the reliability of PUSCH decoding. More specifically, two transport-block sizes of PUSCH repetitions have the systematic bits and parity bits, but the sizes of the systematic bits and parity bits are different.

2.2 Systematic bits transmitted only in longer symbol PUSCH repetitions

The systematic bits are constructed by the DCI and CRC. Figure 5 shows the first part of coded bits with systematic bits that can be sent in the PUSCH repetition 1, the remaining coded bits will be transmitted in PUSCH repetition 2. For example, the coded bits of DCI is split into two parts when two repetitions are configured for this DCI. The first part is transmitted in the larger transport-block sizes repetition and the second part is the smaller transport-block sizes repetition. In this approach, only the larger transport-block sizes PUSCH repetition can be self-decodable since all systematic bits and one part of parity bits are included. In this case, the following smaller transport-block sizes PUSCH repetition can be considered as an extension of the larger transport-block sizes PUSCH repetition.

It is proposed that the systematic bits are only transmitted in the larger transport-block sizes PUSCH repetition and the remaining parity bits can be transmitted in the smaller transport-block sizes PUSCH repetition for increasing the reliability of PUSCH decoding. More specifically, the larger transport-block sizes of PUSCH repetition have all systematic bits and one part of parity bits, and the smaller transport-block sizes of PUSCH repetition have remaining parity bits which considered as an extension of the larger transport-block sizes of PUSCH repetition.

For the issue of interruption by higher priority transmissions. Compared to conventional dropping and postponing repetitions, this disclosure proposes smaller transport-block size PUSCH repetition that can avoid dropping and postponing. The soft combining with different sizes of PUSCH repetition can even increase the reliability of decoding.

3. UCI multiplexing on PUSCH repetitions

In the current specification, UE does not expect to detect a DCI, indicating a PUCCH resource for HARQ-ACK in a later slot, if UE detects a DCI scheduling a PUSCH transmission in a previous slot and the HARQ-ACK information be multiplexed on the PUSCH transmission. When the number of repetitions is high, the repetition transmission would occupy lots of UL transmission resource, especially in TDD systems where the UL transmission resources are limited. In this case, if there is a UCI carrying HARQ-ACK feedback, as shown in Figure 6, HARQ-ACK would have to wait until PUSCH repetitions have been finished, and the latency-sensitive services could not work well.

To overcome this drawback, a looser timeline can be achieved if the UCI is mapped to the PUSCH occasion by puncturing some PUSCH symbols, since UE does not need to regenerate the baseband signal of all symbols in the PUSCH resource.

UCI information mainly includes: SR (scheduling request) , CQI (channel quality indicator) , PMI (precoding matrix indicator) , RI (rank indication) , ACK (acknowledgment) and NACK (Negative acknowledgment) . CQI, PMI and RI are included in channel state information (CSI) . In an embodiment, UCI type priority is HARQ-ACK/NACK > SR > CSI. According to the number of symbols of PUSCH can be punched, UCI data can be mapped and based on the UCI type priority. In other words, HARQ-ACK/NACK should be prioritized when the PUSCH symbol that can be punctured is limited.

It is proposed that according to the UCI type priority, UCI is mapped to the PUSCH transmission occasion by puncturing PUSCH symbols.

3.1 Puncturing by the available symbols from the both sides of the DMRS

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

It is proposed that according to UCI type priority, UCI is mapped to the PUSCH transmission occasion by puncturing PUSCH symbols and placed on the columns of symbols on both sides of the DMRS.

3.2 Puncturing by the available symbols from top left to right

The UCI is punctured and mapped, and placed on the available symbols from top left to right, as shown in Figure 8. Start with the top left symbol in the top row, and punch the available symbols to the right for UCI mapping. When there are no available symbols in the top row, continue to punch the available symbols in the top second row from left to right. The extra UCI, such as ACK/NACK, SR and CSI, is mapped to the available PUSCH symbols according to UCI type priority. Starting the mapping after the existing UCI position can protect the existing UCI.

It is proposed that according to UCI type priority, UCI is mapped to the PUSCH transmission occasion by puncturing available PUSCH symbols from the top left to right.

For the issue of HARQ-ACK feedback delay, some conventional skills involve removing the timeline restriction to facilitate downlink scheduling and HARQ-ACK feedback. However, removing the timeline restriction will lead to a more stringent timeline for UCI multiplexing on PUSCH repetitions.

In Rel-16, NR supports PUSCH repetition type A with a maximum repetition number up to 16. It is proposed in this disclosure to increase this limit to a number greater than or equal to 32 (e.g., a number equal to 32) . However, increasing the maximum repetition number of PUSCH will cause problems for interruption of higher priority transmission and HARQ-ACK feedback delay. To address those issues, this disclosure proposes smaller transport-block size PUSCH repetition and UCI multiplexing by puncturing the PUSCH symbol.

In the aspect of smaller transport-block size PUSCH repetition, in order to increase the reliability of PUSCH decoding, UE can perform a soft combination with different transport-block sizes of PUSCH repetition. Two schemes composed of PUSCH repetition are proposed. In the first scheme, two transport-block sizes of PUSCH repetition have the systematic bits and parity bits, but the sizes of the systematic bits and parity bits are different. In the second scheme, the larger transport-block sizes of PUSCH repetition have all systematic bits and one part of parity bits, and the smaller transport-block sizes of PUSCH repetition have remaining parity bits which considered as an extension of the larger transport-block sizes of PUSCH repetition.

In the aspect of UCI multiplexing by puncturing the PUSCH symbol, two approaches of multiplexing UCI in PUSCH occasion by puncturing some PUSCH symbols are proposed. According to the UCI type priority, ACK/NACK, SR and CSI are mapped in the available symbols by priority. In the first approach, UCI is mapped to the PUSCH occasion by puncturing PUSCH symbols and placed on the columns of symbols on both sides of the DMRS. In the second approach, UCI is mapped to the PUSCH occasion by puncturing available PUSCH symbols from the top left to right.

Figure 9 is a block diagram of an example system 1300 for wireless communication according to an embodiment of the present disclosure. Embodiments described herein may be implemented into the system using any suitably configured hardware and/or software. Figure 9 illustrates the system 1300 including a radio frequency (RF) circuitry 1310, a baseband circuitry 1320, a processing unit 1330, a memory/storage 1340, a display 1350, a camera 1360, a sensor 1370, and an input/output (I/O) interface 1380, coupled with each other as illustrated.

The processing unit 1330 may include a circuitry, such as, but not limited to, one or more single-core or multi-core processors. The processors may include any combinations of general-purpose processors and dedicated processors, such as graphics processors and application processors. The processors may be coupled with the memory/storage and configured to execute instructions stored in the memory/storage to enable various applications and/or operating systems running on the system.

The baseband circuitry 1320 may include a circuitry, such as, but not limited to, one or more single-core or multi-core processors. The processors may include 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. The radio control functions may include, but are not limited to, signal modulation, encoding, decoding, radio frequency shifting, etc. In some embodiments, the baseband circuitry may provide for communication compatible with one or more radio technologies. For example, in some embodiments, the baseband circuitry may support communication with 5G NR, LTE, an evolved universal terrestrial radio access network (EUTRAN) and/or other wireless metropolitan area networks (WMAN) , a wireless local area network (WLAN) , a wireless personal area network (WPAN) . Embodiments in which the baseband circuitry is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuitry. In various embodiments, the baseband circuitry 1320 may include circuitry to operate with signals that are not strictly considered as being in a baseband frequency. For example, in some embodiments, baseband circuitry may include circuitry to operate with signals having an intermediate frequency, which is between a baseband frequency and a radio frequency.

The RF circuitry 1310 may enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium. In various embodiments, the RF circuitry may include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network. In various embodiments, the RF circuitry 1310 may include circuitry to operate with signals that are not strictly considered as being in a radio frequency. For example, in some embodiments, RF circuitry may include circuitry to operate with signals having an intermediate frequency, which is between a baseband frequency and a radio frequency.

In various embodiments, the transmitter circuitry, control circuitry, or receiver circuitry discussed above with respect to the UE, eNB, gNB or TRP may be embodied in whole or in part in one or more of the RF circuitries, the baseband circuitry, and/or the processing unit. As used herein, “circuitry” may refer to, be part of, or include an Application Specific Integrated Circuit (ASIC) , an electronic circuit, a processor (shared, dedicated, or group) , and/or a memory (shared, dedicated, or group) that execute one or more software or firmware programs, 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 functions associated with the circuitry may be implemented by, one or more software or firmware modules. In some embodiments, some or all of the constituent components of the baseband circuitry, the processing unit, and/or the memory/storage may be implemented together on a system on a chip (SOC) .

The memory/storage 1340 may be used to load and store data and/or instructions, for example, for system. The memory/storage for one embodiment may include any combination of suitable volatile memory, such as dynamic random access memory (DRAM) ) , and/or non-volatile memory, such as flash memory. In various embodiments, the I/O interface 1380 may include one or more user interfaces designed to enable user interaction with the system and/or peripheral component interfaces designed to enable peripheral component interaction with the system. User interfaces may include, but are not limited to a physical keyboard or keypad, a touchpad, a speaker, a microphone, etc. Peripheral component interfaces may include, but are not limited to, a non-volatile memory port, a universal serial bus (USB) port, an audio jack, and a power supply interface.

In various embodiments, the sensor 1370 may include one or more sensing devices to determine environmental conditions and/or location information related to the system. In some embodiments, the sensors may include, but are not limited to, a gyro sensor, an accelerometer, a proximity sensor, an ambient light sensor, and a positioning unit. The positioning unit may also be part of, or interact with, the baseband circuitry and/or RF circuitry to communicate with components of a positioning network, e.g., a global positioning system (GPS) satellite. In various embodiments, the display 1350 may include a display, such as a liquid crystal display and a touch screen display. In various embodiments, the system 1300 may be a mobile computing device such as, but not limited to, a laptop computing device, a tablet computing device, a netbook, an ultrabook, a smartphone, etc. In various embodiments, system may have more or less components, and/or different architectures. Where appropriate, methods described herein may be implemented as a computer program. The computer program may be stored on a storage medium, such as a non-transitory storage medium.

The embodiment of the present disclosure is a combination of techniques/processes that can be adopted in 3GPP specification to create an end product.

A person having ordinary skill in the art understands that each of the units, algorithm, and steps described and disclosed in the embodiments of the present disclosure are realized using electronic hardware or combinations of software for computers and electronic hardware. Whether the functions run in hardware or software depends on the condition of application and design requirement for a technical plan. A person having ordinary skill in the art can use different ways to realize the function for each specific application while such realizations should not go beyond the scope of the present disclosure. It is understood by a person having ordinary skill in the art that he/she can refer to the working processes of the system, device, and unit in the above-mentioned embodiment since the working processes of the above-mentioned system, device, and unit are basically the same. For easy description and simplicity, these working processes will not be detailed.

It is understood that the disclosed system, device, and method in the embodiments of the present disclosure can be realized with other ways. The above-mentioned embodiments are exemplary only. The division of the units is merely based on logical functions while other divisions exist in realization. It is possible that a plurality of units or components are combined or integrated in another system. It is also possible that some characteristics are omitted or skipped. On the other hand, the displayed or discussed mutual coupling, direct coupling, or communicative coupling operate through some ports, devices, or units whether indirectly or communicatively by ways of electrical, mechanical, or other kinds of forms.

The units as separating components for explanation are or are not physically separated. The units for display are or are not physical units, that is, located in one place or distributed on a plurality of network units. Some or all of the units are used according to the purposes of the embodiments. Moreover, each of the functional units in each of the embodiments can be integrated in one processing unit, physically independent, or integrated in one processing unit with two or more than two units.

If the software function unit is realized and used and sold as a product, it can be stored in a readable storage medium in a computer. Based on this understanding, the technical plan proposed by the present disclosure can be essentially or partially realized as the form of a software product. Or, one part of the technical plan beneficial to the conventional technology can be realized as 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 computational device (such as a personal computer, a server, or a network device) to run all or some of the steps disclosed by the embodiments of the present disclosure. The storage medium includes a USB disk, a mobile hard disk, a read-only memory (ROM) , a random access memory (RAM) , a floppy disk, or other kinds of media capable of storing program codes.

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

Claims

A transmitter, configured to communicate in a communication system, the transmitter comprising:

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

a circuitry configured to:

transmit physical uplink shared channel (PUSCH) repetitions based on PUSCH repetition type A,

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

wherein a minimum number of symbols for one PUSCH repetition is configured.
The transmitter according to claim 1, wherein the minimum number of symbols for the one PUSCH repetition is configured with a starting symbol and the number of consecutive symbols.
The transmitter according to claim 1, wherein at least two of the PUSCH repetitions have different types of lengths and are configured with different starting symbols.
The transmitter according to claim 1, wherein the circuit is further configured to:

perform a soft combination on different PUSCH repetitions in different monitoring occasion.
The transmitter according to claim 1, wherein the PUSCH repetitions are constructed with different sizes of systematic bits and parity bits.
The transmitter according to claim 1, wherein the PUSCH repetitions comprise a first PUSCH repetition having all systematic bits and one part of parity bits for coded bits of information, and a second PUSCH repetition having remaining parity bits which considered as an extension of first PUSCH repetition, wherein the first PUSCH repetition has larger transport-block sizes than the second PUSCH repetition.
A transmitter, configured to communicate in a communication system, the transmitter comprising:

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

a circuitry configured to:

multiplex an uplink control information (UCI) on a physical uplink shared channel (PUSCH) repetition by puncturing some PUSCH symbols in the PUSCH repetition.
The transmitter according to claim 7, wherein according to UCI type priority, the UCI is mapped to transmission occasion of the PUSCH repetition.
The transmitter according to claim 8, wherein the UCI type priority indicates that hybrid automatic repeat request (HARQ) feedback is prior to a scheduing request (RI) of the UCI that is prior to channel state information (CSI) of the UCI.
The transmitter according to claim 7, wherein the UCI is mapped to transmission occasion of the PUSCH repetition by puncturing the PUSCH symbols and placed on columns of symbols on both sides of demodulation reference signals (DMRS) .
The transmitter according to claim 7, wherein the UCI is mapped to transmission occasion of the PUSCH repetition by puncturing available PUSCH symbols from top left to right.