CN110036689B

CN110036689B - Uplink transmission method and communication device

Info

Publication number: CN110036689B
Application number: CN201880004797.9A
Authority: CN
Inventors: 杨维东; 蔡隆盛; 廖培凯; 桂建卿
Original assignee: MediaTek Inc
Current assignee: MediaTek Inc
Priority date: 2017-09-19
Filing date: 2018-09-19
Publication date: 2023-04-14
Anticipated expiration: 2038-09-19
Also published as: WO2019057092A1; TWI693853B; CN110036689A; TW201924430A; US20190090261A1; US10716127B2

Abstract

Various solutions are described relating to Uplink Control Information (UCI) feedback time indication (signaling) in wireless communications. A User Equipment (UE) identifying a type of uplink transmission to be performed for a network node of a wireless network; the UE receiving a control signal from the network node and determining a minimum time offset for transmission scheduling of the identified type of uplink transmission in accordance with the control signal; performing the uplink transmission to the network node in accordance with the transmission schedule such that: performing a first type of uplink transmission using a first time offset; performing a second type of uplink transmission using a second time offset, the second time offset being different from the first time offset.

Description

Uplink transmission method and communication device

Technical Field

The present application relates generally to wireless communications, and more particularly to Uplink Control Information (UCI) feedback time indication (signaling) in wireless communications.

Background

Unless otherwise indicated herein, the approaches described in this section are not prior art to the claims set forth below and are not admitted to be prior art by inclusion in this section.

In mobile communications in Long-Term Evolution (LTE) and/or fifth generation (5G) and New Radio (NR) mobile networks, it has been assumed that for aperiodic (aperiodic) Channel State Information (CSI) reported on a Physical Uplink Shared Channel (PUSCH), a possible time offset value Y is the same as an offset of PUSCH scheduling determined in a scheduling and hybrid automatic repeat request (HARQ) Acknowledgement Indicator (AI). However, since the offset of the PUSCH scheduling is determined by the processing latency of the PUSCH and the offset of the CSI feedback is determined by the CSI processing latency, they may not completely overlap each other.

Disclosure of Invention

The following summary is illustrative only and is not intended to be in any way limiting. That is, the following summary is provided to introduce concepts, points, benefits and advantages of the novel and non-obvious techniques described herein. Selected implementations are further described below in the detailed description. Thus, the following summary is not intended to identify essential features of the claimed subject matter, nor is it intended for use in determining the scope of the claimed subject matter.

The present invention proposes some solutions, schemes, methods and arrangements relating to UCI feedback time indication (signaling) in wireless communication. It is believed that the proposed solution, scheme, method and apparatus may reduce transmission overhead, thereby improving system performance.

In one aspect, a method may involve a processor of a user equipment identifying a type of Uplink (UL) transmission to perform for a network node of a wireless network. The method further involves the processor receiving a control signal from the network node and determining a minimum time offset for a transmission schedule for the identified type of UL transmission from the control signal. The method further involves the processor performing the UL transmission to the network node according to the transmission schedule such that a first type of UL transmission is performed using a first time offset and a second type of UL transmission is performed using a second time offset different from the first time offset.

In one aspect, an apparatus may include a transceiver and a processor coupled with the transceiver. The transceiver is capable of communicating wirelessly with a network node of a wireless network. The processor is capable of: (a) Identifying a type of UL transmission to be performed for the network node; (b) Receiving, via the transceiver, a control signal from the network node; (c) Determining a minimum time offset for transmission scheduling of the identified type of UL transmission in accordance with the control signal; and (d) performing, via the transceiver, the UL transmission to the network node according to the transmission schedule such that (i) a first type of UL transmission is performed using a first time offset, and (ii) a second type of UL transmission is performed using a second time offset different from the first time offset.

It is worth noting that although the description provided herein may be in the context of certain radio access technologies, networks and network topologies, such as 5G/NR mobile communications, the proposed concepts, schemes and any variants/derivatives may also be implemented in other types of radio access technologies, networks and network topologies, such as, but not limited to, LTE-Advanced Pro, internet of things (IoT) and narrowband Internet of things (Narrow Band Internet of things (NB-IoT), where applicable. Accordingly, the scope of the invention is not limited to the examples described herein.

Drawings

The accompanying drawings are included to provide a further understanding of the invention, and are incorporated in and constitute a part of this specification. The drawings illustrate embodiments of the invention and together with the description serve to explain the principles of the invention. It is to be understood that the figures are not necessarily to scale, since some features may be shown out of proportion to the actual implementation, for clarity of illustrating the concepts of the invention.

Fig. 1 is a schematic diagram of an example scenario of time offset for PUSCH scheduling according to an embodiment of the present invention;

FIG. 2 is a diagram of an example scenario of multi-slot aggregation according to an embodiment of the present invention;

fig. 3 is a schematic diagram of an example scenario of time offset for PUSCH scheduling according to an embodiment of the present invention;

fig. 4 is a schematic diagram of an example scenario of time offset for PUSCH scheduling according to an embodiment of the present invention;

fig. 5 is a diagram of an example scenario for uplink transmission time of UCI and data according to an embodiment of the present invention;

fig. 6 is a diagram of an example scenario for uplink transmission time of UCI not multiplexed with data according to an embodiment of the present invention;

FIG. 7 is a block diagram of an example wireless communication environment according to an embodiment of the present invention;

FIG. 8 is a flow chart of an example process according to an embodiment of the present invention.

Detailed Description

Detailed examples and embodiments of the claimed subject matter are disclosed herein. However, it is to be understood that the disclosed embodiments and implementations are merely illustrative of the claimed subject matter, which can be embodied in various forms. This invention may, however, be embodied in many different forms and should not be construed as limited to the exemplary embodiments and implementations set forth herein. Rather, these exemplary embodiments and implementations are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art. In the following description, details of well-known features and techniques may be omitted to avoid unnecessarily obscuring the presented embodiments and implementations.

SUMMARY

Embodiments according to the present invention relate to various techniques, methods, schemes and/or solutions for UCI feedback time indication in wireless communications. Some solutions according to the invention can be implemented separately or jointly. That is, although these possible solutions may be separately described below, two or more of these possible solutions may be implemented in one combination or another combination.

CSI feedback for Wide-Bandwidth (Wide-Bandwidth) systems

In LTE, the maximum bandwidth is limited to 20MHz, and the propagation conditions between the base station (e.g., eNodeB) and the UEs served by the base station are similar on different carrier tones. Therefore, the conventional one has a dual stage codebook and a single W ₁ The conventional feedback framework of (a) already serves LTE well.

However, in 5G, the radio conditions between the base station (e.g. eNodeB) and the UEs served by the base station may be different on different carrier tones. There may be several contributing factors. First, due to the considerable channel bandwidth in 5G, the propagation conditions may differ at different tones, e.g. different number of clusters (clusters) at high and low frequencies in the carrier bandwidth. Second, the 5G base station can reuse the radio front-end of the current LTE deployment. For example, if the front end of the LTE network is operating from 3.6GHz to 3.6GHz +20mhz, instead of building a new radio front end to cover 3.6GHz to 3.6GHz +40mhz to support a 40MHz 5G system, the operator may choose to build a 5G radio front end covering 3.6GHz +20mhz to 3.6GHz +40mhz, and 5G radio signals may be routed to or from both radio front ends to save cost. It is worth noting that in this case different antenna structures may be used at different frequencies in the carrier bandwidth. Because the propagation conditions are not the same at the higher and lower frequencies and different antenna structures are used, the transmission conditions are different overall and the approximate same location (QCL) assumption is different for the data transmission channel state information reference signal (CSI-RS) at the lower and higher frequencies. Third, the interference situation can be very different at high and low frequencies.

However, considering higher and lower frequencies as part of a single carrier bandwidth may still be preferable due to considerations such as system overhead (e.g., sharing all overhead channels such as Primary Synchronization Signal (PSS)/Secondary Synchronization Signal (SSS), physical Random Access Channel (PRACH), broadcast Channel (BCH), etc.), better relay efficiency (e.g., shared paging capability), lower signaling overhead (e.g., scheduling Physical Downlink Shared Channel (PDSCH) and Physical Uplink Shared Channel (PUSCH) on higher and lower frequencies using one Physical Downlink Control Channel (PDCCH)). Thus, some modifications may be required.

Under the proposed scheme according to the present invention, the first change may involve taking QCL assumptions for the CSI-RS and PDSCH and demodulation reference signals (DMRS) for the sub-part of the carrier bandwidth and/or the bandwidth part (BWP), and the partitioning of the BWP or carrier bandwidth for a UE may be Radio Resource Control (RRC) configured to save signaling overhead in dynamic signaling, e.g., downlink Control Information (DCI). Also, since propagation conditions and interference situation of a desired signal may be different, a single Rank Indication (RI) or a single wideband W ₁ May not be sufficient. Thus, under the proposed scheme, the UE may be configured to report CSI-RS resource index (CRI), RI, W, for each configured sub-portion of the BWP/carrier bandwidth ₁ ,W ₂ And a Channel Quality Indicator (CQI). To simplify the UCI reporting rules, CSI reporting for different sub-parts may be doneFollowing the design of the carrier aggregation case. For example, assuming that there are two subparts (cc-1-part 1 and cc-1-part 2) under carrier 1 and two subparts (cc-2-part 1 and cc-2-part 2) under carrier 2, the CSI aggregation rule may be defined according to cc-1-part1, cc-1-part2, cc-2-part1, cc-2-part2 (first according to the carrier index). Alternatively, the CSI aggregation rule may be defined according to cc-1-part1, cc-2-part1, cc-1-part2, cc-2-part2 (first according to the index of the subpart).

Under the proposed scheme, on the base station side, the base station may simultaneously use multiple PDCCHs to schedule multiple PDSCHs to UEs on multiple sub-parts, possibly using different transmission rank (rank) and MCS levels and precoders. Each PDSCH may or may not be restricted within a sub-portion. The base station may also choose to schedule a single PDSCH on multiple sub-portions using a single PDCCH. In addition, a Precoding Matrix Indicator (PMI) of each sub-section may follow CSI feedback for UEs of the respective sub-sections.

Indicating UCI feedback time in NR

Considering frequency-division duplexing (FDD), assume K _min As a time offset for the minimum PUSCH schedule obtained using a set of conditions (e.g., a given set of parameters (numerology), size of resource allocation and related BWP, transport Block Size (TBS) size, coding rate, etc.), the offset for the PUSCH schedule may be from K _min ,K _min +1,K _min +2,K _min +3, \8230andmedium value. Due to the restriction of the bit width of the offset in the UL DCI for indicating PUSCH scheduling, only a limited number of values are allowed. For example, two bits are used for related signaling, { K _min ,K _min +1,K _min +2,K _min +3 is allowed, it is desirable that the value of K _ min be as low as possible in order to benefit from low delay design considerations in NR.

For CSI feedback, consider the case of FDD, assuming Y _ min is the time offset of the minimum CSI feedback using a given condition set (e.g., condition set 1), such as a given parameter set (numerology), the size and subband size configuration of the relevant BWP (e.g., using BWP size and using subband size that determines the number of subbands to use for CQI feedback), the number of ports to use for CSI feedback, the type of CSI feedback (e.g., type I or type II), wideband pair of subbands, single CSI report, and so on. Then, the time offset Y _ min of the minimum CSI feedback required may be different for the set of other conditions (e.g., condition set 2 of CSI reports for three cells (cells)).

Considering time-division duplexing (TDD), if semi-static (semi-static) downlink/uplink (UL/DL) configuration or separation is used for the UE, it is noted that typically the time offset of the minimum PUSCH scheduling may depend on the scheduling slot n in the radio frame. This can be illustrated by the "k" value table from the TD-LTE design (TS 36.231, rel-13). The use of the definition "k" in TS 36.213, clause 8.2, is as follows: "for TDD UL/DL configurations 1-6 and normal HARQ operation, the UE should adjust a corresponding PUSCH transmission in a subframe n + k using k given in table 8-2 according to PDCCH and PHICH information when detecting a PDCCH with DCI format 0 and/or a Physical Hybrid automatic repeat Indicator Channel (PHICH) transmission in the subframe n for the UE.

TABLE 8-2K for TDD configurations 0-6

In NR, UL/DL slot configuration may be semi-statically configured to a UE or dynamically indicated to a UE using a common set of PDCCHs. Fig. 1 illustrates an example scenario 100 of time shifting for PUSCH scheduling according to an embodiment of the present invention. In fig. 1, "D" indicates a slot in which a PDCCH can be transmitted and a PUSCH is not allowed. Under one set of conditions, assume K _min =3, for UL grants (UL grant) received at the UE on slot 0 in radio frame f, as shown in fig. 1, it may happen that the allowed value of time offset for PUSCH scheduling comes from {3,4,7,8 }.

In the case of configuring the allowed time offset value (e.g., {3,4,7,8 }) by RRC signaling, a mapping of the time offset for PUSCH scheduling in UL grant DCI may be established such that "00" → k =3, "01" → k =4, "10" → k =7, "11" → k =8. In the example shown in fig. 1, DCI code state "01" may not be useful for the UL grant received in slot 1 because it will point to the slot for DL transmission (slot 5).

In order to make all code states available for uplink transmission in a feasible time slot, one way may be: for UL grants received on time slot n, from time slot n + K _min And a first one of the following slots in which PUSCH may be communicated may be indicated by a first code state (e.g., "00") for a PUSCH scheduling time offset, from slot n + K _min And a second of the following slots in which PUSCH may be communicated may be indicated by a second code state (e.g., "01") for PUSCH scheduling time offsets, and so on. Therefore, for a UL grant received on time slot 0, "00" → k =3, "01" → k =4, "10" → k =7, "11" → k =8. For a UL grant received on slot 1, "00" → k =4, "01" → k =7, "10" → k =8, "11" → k =9.

When UCI (including CSI reporting, beam reporting, HARQ acknowledgement, scheduling Request (SR), and the like) is multiplexed with PUSCH, since UCI and PUSCH are transmitted in the same slot, a time offset for UCI feedback may be the same as a PUSCH scheduling time offset. For example, slot aggregation or Transmission Time Interval (TTI) bundling may be used for PUSCH and UCI. However, as analyzed before, not all allowed time offset values for PUSCH scheduling are also allowed time offset values for UCI feedback.

Under the condition set 1, Y _min Can be greater or less than K _min . Having the time offset of the PUSCH schedule indicate the time offset of the UCI feedback is not ideal. For example, if K _min =3 and Y _min =2, then either the field of time offset for PUSCH scheduling (e.g. for UCI multiplexed with data on PUSCH) or the field of time offset for UCI feedback (e.g. UCI not multiplexed with data and field with data) must be scheduled using the allowable values from {2,3,4,5,6}, eitherPUSCH) for FDD. Here, {2} may be used for uplink transmission of UCI not multiplexed with data, and {3,4,5,6} may be used for UCI multiplexed with data. Accordingly, two bits are required to inform the PUSCH/UCI time offset.

In the proposed scheme according to the present invention, a better design may define the relationship of code status to UCI time offset depending on whether UL grant schedules transmission of UCI not multiplexed with data or schedules transmission of UCI multiplexed with data. For UCI multiplexed with data, the mapping rule as given earlier may be applied to the time offset of PUSCH scheduling. UCI reporting may be in time slot n + Y _min And up or down to the earliest of the slots available for scheduling PUSCH. Fig. 2 illustrates an example scenario 200 of multiple slot aggregation, according to an embodiment of the present invention.

For transmission of UCI feedback not multiplexed with data, for UL grant received in slot n, from slot n + Y _min And a first slot among the following slots in which the PUSCH may be communicated may be indicated by a first code status (e.g., "00") for a time offset of UCI feedback. From time slot n + Y _min And a second of the following slots in which PUSCH may be communicated may be indicated by a second code state (e.g., "01"), a time offset for PUSCH scheduling, and so on.

Fig. 3 illustrates an example scenario 300 of PUSCH scheduling time offset, according to an embodiment of the invention. In FIG. 3, Y is used _min Slot 1 is a DL slot, code state "00" points to transmission of only UCI in slot 2, code state "01" points to transmission of only UCI in slot 3, and so on.

Alternatively, the mapping between code states and time offsets in case of UCI only transmission is by RRC signaling, which may be separate from the RRC signaling and/or mapping of time offsets for PUSCH scheduling. Fig. 4 illustrates an example scenario 400 of time offset for PUSCH scheduling according to an embodiment of the present invention. In the example shown in fig. 4, RRC signaling can be used to establish "00" → Y =4, "01" → Y =7, "10" → Y =8, "11" → Y =9.

In view of the above, for UL DCI having fields as shown below, different mapping rules from code state to time offset may be used for UCI-only case and UCI-data multiplexing case.

DCI＝{

…

PUSCH-scheduling/CSI-feedback-timing-offset,

…

}

Alternatively, the UL DCI for the UCI-only case may be given by:

DCI＝{

…

CSI-feedback-timing-offset,

…

}

also, UL DCI for the case where UCI is multiplexed with data may be given by:

DCI＝{

…

PUSCH-scheduling/CSI-feedback-timing-offset,

…

}

accordingly, under the proposed scheme, different mapping rules from code state to time offset may be used for the UCI-only case and the UCI multiplexed with data case. That is, the time offset of the CSI may be separately determined for transmission of UCI only and transmission of UCI multiplexed with data.

Fig. 5 illustrates an example scenario 500 for uplink transmission time of UCI multiplexed with data, according to an embodiment of the invention. In scenario 500, for a UL grant received via DCI in slot n, the time offset fields of PUSCH transmission time and CSI feedback may correspond to slots n + a1, n + a1+2 and n + a1+3 (which correspond to code states "00", "01", "10", and "11"), in scenario 500, there may be multiple conditions under which the UE can send CSI feedback multiplexed with data, such as, but not limited to, condition set 1, condition set 2, and condition set 3. UL transmission under condition set 1 may involve one report with 32 ports, for example. UL transmission under condition set 2 may involve, for example, two reports with 32 ports. UL transmission under condition set 3 may involve, for example, a single report with 2 ports. As shown in fig. 5, transmission of CSI feedback (as part of UCI feedback) multiplexed with data may occur in the same time frame in which PUSCH is transmitted.

Fig. 6 illustrates an example scenario 600 for uplink transmission time for UCI not multiplexed with data, according to an embodiment of the invention. In scenario 600, the time offset for PUSCH transmission and the time offset for CSI feedback (as part of UCI feedback) are different for UL grant received via DCI in slot n. As illustrated in fig. 6, the transmission of CSI feedback (as part of UCI feedback) not multiplexed with data may occur outside of the time frame in which PUSCH is transmitted. The PUSCH transmission time offset field may correspond to time slots n + a1, n + a1+1, n + a1+2, and n + a1+3.

The CSI feedback transmission time offset may depend on the conditions when the UE transmits CSI feedback that is not multiplexed with data. In scenario 600, there may be conditions under which the UE can send CSI feedback that is not multiplexed with data. Such as but not limited to condition set 1, condition set 2, and condition set 3. UL transmission under condition set 1 may involve one report with 32 ports, for example. UL transmission under condition set 2 may involve, for example, two reports with 32 ports. UL transmission under condition set 3 may involve a single report with 2 ports, for example. For transmission of CSI feedback not multiplexed with data under condition set 1, code states "00", "01", "10", and "11" may correspond to time offset fields n + b1, n + b1+2, and n + b1+3. For transmission of CSI feedback not multiplexed with data under condition set 2, code states "00", "01", "10", and "11" may correspond to time offset fields n + b2, n + b2+1, n + b2+2, and n + b2+3. For transmission of CSI feedback not multiplexed with data under condition set 3, code states "00", "01", "10", and "11" may correspond to time offset fields n + b3, n + b3+1, n + b3+2, and n + b3+3.

Illustrative embodiments

Fig. 7 illustrates an exemplary wireless communication environment 700 according to an embodiment of the invention. Wireless communication environment 700 may involve a communication device 710 and a network device 720 in wireless communication with each other. Each of the communication device 710 and the network device 720 may perform various functions to implement the processes, schemes, techniques, processes and methods described herein relating to UCI feedback time indication in wireless communications, including the various processes, scenarios, schemes, solutions, concepts and techniques described above, as well as the process 800 described below.

The communication device 710 may be part of an electronic device, the communication device 710 may be a UE such as a portable or mobile device, a wearable device, a wireless communication device, or a computing device. For example, the communication apparatus 710 may be implemented in a smartphone, a smart watch, a personal digital assistant, a digital camera, or a computing device such as a tablet computer, a laptop computer, or a notebook computer. Further, the communication device 710 may also be part of a machine type device, which may be an IoT or NB-IoT device such as a non-mobile or fixed device, a home device, a wired communication device, or a computing device. For example, the communication device 710 may be implemented in a smart thermostat, a smart refrigerator, a smart door lock, a wireless speaker, or a home control center. Alternatively, communication device 710 may be implemented in the form of one or more Integrated Circuit (IC) chips, such as, but not limited to, one or more single-core processors, one or more multi-core processors, one or more reduced-instruction-set-computing (RISC) processors, or one or more complex-instruction-set-computing (CISC) processors.

The communication device 710 may include at least some of those components shown in fig. 7, such as a processor 712. The communication apparatus 710 may also include one or more other components (e.g., an internal power supply, a display device and/or a user interface device) that are not relevant to the solution proposed by the present invention, and, therefore, such components of the communication apparatus 710 are not shown in fig. 7 nor described below for the sake of simplicity and brevity.

The network device 720 may be part of an electronic device, which may be a network node such as a TRP, a base station, a small cell (cell), a router, or a gateway. For example, network device 720 may be implemented in an eNodeB in an LTE, LTE-Advanced, or LTE-Advanced Pro network, or in a gNB in a 5g, nr, ioT, or NB-IoT network. Alternatively, network device 720 may be implemented in the form of one or more IC chips, such as, but not limited to, one or more single-core processors, one or more multi-core processors, one or more RISC processors, or one or more CISC processors.

Network device 720 may include at least some of those components shown in fig. 7, such as a processor 722. The network apparatus 720 may also include one or more other components (e.g., an internal power supply, a display device and/or a user interface device) that are not relevant to the proposed solution of the present invention, and, therefore, such components of the communication apparatus 720 are not shown in fig. 7 nor described below for the sake of simplicity and brevity.

In one aspect, each of the processors 712 and 722 may be implemented in the form of one or more single-core processors, one or more multi-core processors, one or more RISC processors, or one or more CISC processors. That is, even though the singular term "processor" is used herein to refer to the processor 712 and the processor 722, each of the processor 712 and the processor 722 may include multiple processors in some implementations and a single processor in other implementations consistent with the invention. In another aspect, each of the processors 712 and 722 may be implemented in hardware (and optionally firmware) with electronic components including, for example and without limitation, one or more transistors, one or more diodes, one or more capacitors, one or more resistors, one or more inductors, one or more memristors, and/or one or more varactors configured and arranged to achieve particular objectives in accordance with the present invention. In other words, in at least some implementations, each of the processor 712 and the processor 722 is a dedicated machine specifically designed, arranged, and configured to perform specific tasks related to UCI feedback time indication in wireless communications according to various embodiments of the present invention.

In some embodiments, the communication device 710 may also include a transceiver 716 coupled to the processor 712 and capable of wirelessly transmitting and receiving data, signals and information. In some implementations, the communication device 710 can also include a memory 714, the memory 714 being coupled to the processor 712 and capable of being accessed (accessed) by the processor 712 and storing data therein. In some implementations, the network device 720 can also include a transceiver 726 that is coupled to the processor 722 and that is capable of wirelessly transmitting and receiving data, signals and information. In some embodiments, the network device 720 may also include a memory 724, the memory 724 being coupled to the processor 722 and capable of being accessed by the processor 722 and storing data therein. Thus, the communication device 710 and the network device 720 may wirelessly communicate with each other via the transceiver 716 and the transceiver 726, respectively.

To facilitate a better understanding, the following description of the operation, functionality, and capabilities of each of the communication device 710 and the network device 720 is provided in the context of a mobile communication environment in which the communication device 710 is implemented in or as a communication device or UE. The network device 720 is implemented in or as a network node (e.g., a gNB or a TRP) of a wireless network (e.g., a 5G/NR mobile network).

In various proposed schemes according to the present invention, the processor 712 of the communication device 710 can identify the type of UL transmission to be performed for the network device 720. Additionally, the processor 712 may receive control signals from the network device 720 via the transceiver 716. Further, the processor 712 can determine a minimum time offset for transmission scheduling of the identified UL transmission type based on the control signal. Further, the processor 712 may perform UL transmissions to the network device 720 via the transceiver 716 according to the transmission schedule such that the first type of UL transmission is performed with a first time offset and the second type of UL transmission is performed with a second time offset, the second time offset being different from the first time offset.

In some embodiments, the first type of UL transmission may involve transmission of UCI feedback multiplexed with data on PUSCH. Also, the second type of UL transmission may involve transmission of UCI feedback without multiplexing with data.

In some embodiments, in identifying the type of UL transmission, the processor 712 may identify the type of UL transmission of the UCI feedback multiplexed with data on the PUSCH. In some embodiments, the time offset for UL transmission of UCI feedback multiplexed with data may be equal to the time offset for PUSCH scheduling.

In some embodiments, in identifying the type of UL transmission, the processor 712 may identify the type of UL transmission of UCI feedback multiplexed with data on PUSCH. In some embodiments, the time offset for UL transmission of UCI feedback multiplexed with data may be different from the time offset for PUSCH scheduling.

In some embodiments, in identifying the type of UL transmission, the processor 712 may identify the type of UL transmission as a transmission of UCI feedback that is not multiplexed with data. In some embodiments, the processor 712 may perform some operations upon receiving control signals from the network device 720. For example, the processor 712 may receive RRC signaling. Also, the processor 712 can configure a time offset value for UL transmission according to the RRC signaling. In some embodiments, in configuring the time offset value for UL transmission, the processor 712 may establish a mapping of the time offset value for PUSCH scheduling to a corresponding code state, as indicated in the control signal UL DCI.

In some embodiments, when determining the minimum time offset for the transmission schedule from the control signal, the processor 712 may determine the minimum time offset measured from the beginning at the time point of receiving the control signal.

In some embodiments, in performing UL transmission, the processor 712 may perform UL transmission under one of a plurality of condition sets related to one or more of a parameter set, a resource allocation or size of bandwidth part (BWP), a transport block size, a coding rate, a subband size configuration, a plurality of ports for CSI feedback, a type of CSI feedback, and a bandwidth type for UL transmission.

In some embodiments, in identifying the type of UL transmission, the processor 712 may identify the type of UL transmission of the UCI feedback multiplexed with data on the PUSCH. In some embodiments, the time offset for UL transmission of UCI feedback multiplexed with data may be the same as the time offset for PUSCH scheduling. In this example, UL transmission of UCI feedback multiplexed with data may be performed within a time frame of PUSCH under each of a plurality of sets of conditions.

In some embodiments, in identifying the type of UL transmission, the processor 712 may identify the type of UL transmission that is not fed back with UCI multiplexed with data on PUSCH. In some embodiments, the time offset for UL transmission of UCI feedback without multiplexing with data is different from the time offset for PUSCH scheduling. In this example, UL transmission of UCI feedback without multiplexing with data may be performed outside of the time frame of PUSCH under one or more of the multiple sets of conditions.

Illustrative Process

FIG. 8 illustrates an example process 800 according to an embodiment of the invention. Process 800 may be an example implementation of various processes, scenarios, solutions, concepts and technologies, or combinations thereof, in accordance with some or all of the invention, regarding UCI feedback time indication in wireless communications. Process 800 may represent an aspect of an implementation of features of communication device 710. Process 800 may include one or more operations, actions, or functions illustrated by one or more of blocks 810,820,830, and 840. Although shown in discrete blocks, the various blocks of the process 800 may be divided into further blocks, combined into fewer blocks, or eliminated, depending on the desired implementation. Further, the blocks of the process 800 may be performed in the order shown in fig. 8, or may be performed in a different order, and one or more blocks of the process 800 may be repeated one or more times. Process 800 may be implemented by communication device 710 or any suitable UE or machine type device. For illustrative purposes only and not by way of limitation, process 800 is described below in the context of communication device 710 as a UE and network device 720 as a network node (e.g., a gNB) of a wireless network. Process 800 may begin at block 810.

At block 810, the process 800 may involve the processor 712 of the communication device 710 identifying a type of UL transmission to perform for the network device 720. Process 800 may proceed from 810 to 820.

At block 820, process 800 may involve processor 712 receiving a control signal from network device 720 via transceiver 716. Process 800 may proceed from 820 to 830.

At block 830, process 800 may involve processor 712 determining a minimum time offset for a transmission schedule for the identified type of UL transmission from the control signal. Process 800 may proceed from 830 to 840.

At block 840, the process 800 may involve the processor 712 performing, via the transceiver 716, a UL transmission to the network device 720 according to the transmission schedule such that the first type of UL transmission is performed using a first time offset and the second type of UL transmission is performed using a second time offset different from the first time offset.

In some embodiments, in identifying the type of UL transmission, processor 800 may involve processor 712 identifying the type of UL transmission for UCI feedback multiplexed with data on PUSCH. In some embodiments, the time offset for UL transmission of UCI feedback multiplexed with data may be equal to the time offset for PUSCH scheduling.

In some embodiments, in identifying the type of UL transmission, processor 800 may involve processor 712 identifying the type of UL transmission of UCI feedback multiplexed with data on PUSCH. In some embodiments, the time offset for UL transmission of UCI feedback multiplexed with data may be different from the time offset for PUSCH scheduling.

In some embodiments, in identifying the type of UL transmission, the processor 800 may involve the processor 712 identifying the type of UL transmission as a transmission of UCI feedback that is not multiplexed with data. In some implementations, the processor 800 may involve the processor 712 performing some operations in receiving control signals from the network device 720. For example, processor 800 may involve processor 712 receiving RRC signaling. Moreover, processor 800 can involve processor 712 configuring a time offset value for UL transmission according to RRC signaling. In some embodiments, processor 800 involves processor 712 establishing a mapping from a time offset value for PUSCH scheduling to a corresponding code state as indicated by UL DCI in a control signal when configuring a time offset value for UL transmission.

In some embodiments, in determining the minimum time offset for the transmission schedule from the control signal, processor 800 may involve processor 712 determining the minimum time offset as measured at a point in time when the control signal is received.

In some embodiments, in identifying the type of UL transmission, processor 800 may involve processor 712 performing the UL transmission under one of a plurality of sets of conditions related to one or more of a set of parameters, a resource allocation or a size of bandwidth part (BWP), a transport block size, a coding rate, a subband size configuration, a number of ports for CSI feedback, a type of CSI feedback, and a bandwidth type for the UL transmission.

In some embodiments, in identifying the type of UL transmission, processor 800 may involve processor 712 identifying the type of UL transmission for UCI feedback multiplexed with data on PUSCH. In some embodiments, the time offset for UL transmission of UCI feedback multiplexed with data may be equal to the time offset for PUSCH scheduling. In these cases, UL transmission of UCI feedback multiplexed with data under each of the multiple sets of conditions may be performed within a time frame of PUSCH.

In some embodiments, in identifying the type of UL transmission, the processor 800 may involve the processor 712 identifying the type of UL transmission on PUSCH that is not multiplexed with UCI feedback for data. In some embodiments, the time offset of the UL transmission of UCI feedback not multiplexed with data is different from the time offset used for PUSCH scheduling. In these cases, UL transmission of UCI feedback without multiplexing with data may be performed outside of the time frame of the PUSCH under one or more of the multiple sets of conditions.

Additional description

The subject matter described herein sometimes illustrates different components contained within, or connected with, different other components. It is to be understood that such depicted architectures are merely examples, and that in fact many other architectures can be implemented which achieve the same functionality. In a conceptual sense, any arrangement of components to achieve the same functionality is effectively "associated" such that the desired functionality is achieved. Hence, any two components herein combined to achieve a particular functionality can be seen as "associated with" each other such that the desired functionality is achieved, irrespective of architectures or intermedial components. Likewise, any two components so associated can also be viewed as being "operably connected," or "operably coupled," to each other to achieve the desired functionality, and any two components capable of being so associated can also be viewed as being "operably couplable," to achieve the desired functionality. Specific examples of operably couplable include but are not limited to physically mateable and/or physically interacting components and/or wirelessly interactable and/or wirelessly interacting components and/or logically interacting and/or logically interactable components.

Furthermore, with respect to the use of any plural and/or singular terms herein, those having skill in the art can translate from the plural to the singular and/or from the singular to the plural as is appropriate to the context and/or application. Various singular/plural permutations (permation) may be expressly set forth herein for the sake of clarity.

Furthermore, those skilled in the art will understand that terms used herein generally, and especially terms used in the appended claims, such as the body of the appended claims, are generally intended as "open" terms, such that the term "including" should be interpreted as "including but not limited to," the term "having" should be interpreted as "having at least," the term "includes" should be interpreted as "includes but is not limited to," etc. It will be further understood by those within the art that if a specific number of an introduced claim element is intended, such an intent will be explicitly recited in the claim, and in the absence of such recitation no such intent is present. For example, as an aid to understanding, the following appended claims may contain usage of the introductory phrases "at least one" and "one or more" to introduce claim elements. However, the use of such phrases should not be construed to imply that the introduction of a claim element by the indefinite articles "a" or "an" limits any particular claim containing such introduced claim element to only one such element, even when the same claim includes the introductory phrases "one or more" or "at least one" and indefinite articles such as "a" or "an", e.g., "a" and/or "an" should be interpreted to mean "at least one" or "one or more", as appropriate to the use of the definite article or articles used to introduce the claim element. In addition, even if a specific number of an introduced claim element is explicitly recited, those skilled in the art will recognize that such recitation should be interpreted to mean at least the recited number, e.g., the bare recitation of "two elements" without other modifiers, means at least two elements, or two or more elements. Further, where structures similar to "at least one of A, B, and C, etc." are used, in general such structures will be understood by those skilled in the art to have for their purpose the convention that, for example, "a system having at least one of A, B, and C" will include but not be limited to systems having A alone, B alone, C alone, A and B together, A and C together, B and C together, and/or A, B, and C together, etc. Where a structure similar to "at least one of a, B, or C, etc." is used, in general, such a convention will be understood by those skilled in the art, for example, "a system having at least one of a, B, or C" will include but not be limited to systems having a alone, B alone, C alone, a and B together, a and C together, B and C together, and/or a, B, and C together, etc. It will be further understood by those within the art that virtually any disjunctive word and/or phrase presenting two or more alternative terms, whether in the description, claims, or drawings, should be understood to contemplate the possibilities of including one of the terms, either term, or both terms. For example, the phrase "a or B" will be understood to include the possibility of "a" or "B" or "a and B".

From the foregoing, it will be appreciated that various embodiments disclosed herein have been described herein for purposes of illustration, and that various modifications may be made without deviating from the scope and spirit of the invention. Accordingly, the various embodiments disclosed herein are not intended to be limiting, with the true scope and spirit being indicated by the following claims.

Claims

1. An uplink transmission method, comprising:

a processor of a user equipment identifies a type of uplink transmission to be performed for a network node of a wireless network;

the processor performs the uplink transmission to the network node according to a transmission schedule of the type of uplink transmission such that:

performing a first type of uplink transmission using a first time offset; and

performing a second type of uplink transmission using a second time offset, the second time offset being different from the first time offset;

wherein the first type of uplink transmission comprises transmission of uplink control information, UCI, feedback multiplexed with data on a physical uplink shared channel, PUSCH, and wherein the second type of uplink transmission comprises transmission of UCI feedback not multiplexed with data;

wherein the second time offset is dependent on a set of conditions when the user equipment transmits CSI feedback without multiplexing with data;

wherein the condition set is related to one or more of subband size configuration, port number for CSI feedback, and CSI feedback type.

2. The method of claim 1, wherein the identifying the type of uplink transmission comprises: identifying a type of uplink transmission of the UCI feedback multiplexed with data on the PUSCH, and wherein a time offset for the uplink transmission of the UCI feedback multiplexed with data is the same as a time offset for PUSCH scheduling.

3. The method of claim 1, wherein the identifying the type of uplink transmission comprises: identifying an uplink transmission type of UCI feedback not multiplexed with data on a PUSCH, and wherein a time offset for the uplink transmission of the UCI feedback not multiplexed with data is different from a time offset for PUSCH scheduling.

4. The method of claim 1, wherein the identifying the type of uplink transmission comprises: identifying the type of the uplink transmission as a transmission of UCI feedback not multiplexed with data, and further comprising receiving a control signal from a network node, wherein receiving a control signal from the network node comprises:

receiving radio resource control, RRC, signaling; and

configuring a time offset value for the uplink transmission according to the RRC signaling.

5. The method of claim 4, wherein the configuring the time offset value for the uplink transmission comprises: establishing a mapping of time offset values for the uplink transmission to corresponding code states in accordance with what is indicated in the uplink grant downlink control information, DCI, in the control signal.

6. The method of claim 1, further comprising: the processor receiving a control signal from the network node; the processor determining a minimum time offset for transmission scheduling of the identified type of uplink transmission in accordance with the control signal; determining a minimum time offset for the transmission schedule based on the control signal comprises: the minimum time offset is determined and measured at the point in time when the control signal is received.

7. The method of claim 1, wherein performing the uplink transmission comprises: performing the uplink transmission under one of a plurality of condition sets, wherein the one of the plurality of condition sets is related to one or more of a parameter set, a resource allocation or a size of a bandwidth part BWP, a transport block size, a coding rate, a subband size configuration, a number of ports for channel state information CSI feedback, a type of CSI feedback, and a bandwidth type for the uplink transmission.

8. The method of claim 7, wherein the identifying the type of uplink transmission comprises: identifying an uplink transmission type of UCI feedback multiplexed with data on a PUSCH, wherein a time offset for uplink transmission of the UCI feedback multiplexed with data is the same as a time offset for PUSCH scheduling, and wherein the uplink transmission of the UCI feedback multiplexed with data is performed within a time frame of the PUSCH under each of a plurality of sets of conditions.

9. The method of claim 7, wherein the identifying the type of uplink transmission comprises: identifying an uplink transmission type of UCI feedback not multiplexed with data on a PUSCH, wherein a time offset for the uplink transmission of UCI feedback not multiplexed with data is different from a time offset for PUSCH scheduling, and wherein the uplink transmission of UCI feedback not multiplexed with data is performed outside of a time frame of the PUSCH scheduling under one or more of a plurality of sets of conditions.

10. A communication device, comprising:

a transceiver capable of wireless communication with a network node of a wireless network; and

a processor coupled with the transceiver, the processor capable of:

identifying a type of uplink transmission performed for the network node; and

performing, via the transceiver, the uplink transmission to the network node according to a transmission schedule of the type of uplink transmission such that:

performing a first type of uplink transmission using a first time offset; and

wherein the second time offset is dependent on a set of conditions when the communication apparatus transmits CSI feedback not multiplexed with data;

11. The apparatus of claim 10, wherein in identifying the type of uplink transmission, the processor is capable of identifying the type of uplink transmission for UCI feedback multiplexed with data on PUSCH, and wherein a time offset for the uplink transmission for the UCI feedback multiplexed with data is the same as a time offset for PUSCH scheduling.

12. The apparatus of claim 10, wherein in identifying the type of uplink transmission, the processor is capable of identifying a type of uplink transmission for UCI feedback not multiplexed with data on PUSCH, and wherein a time offset for the uplink transmission for the UCI feedback not multiplexed with data is different than a time offset for PUSCH scheduling.

13. The apparatus of claim 10, wherein, in identifying the type of the uplink transmission, the processor is capable of identifying the type of the uplink transmission as a transmission of UCI feedback not multiplexed with data, and the processor is further configured to receive, via the transceiver, a control signal from the network node, wherein, in receiving the control signal from the network node, the processor is capable of:

receiving radio resource control, RRC, signaling; and

14. The apparatus according to claim 13, wherein in configuring the time offset value for the uplink transmission, the processor is capable of establishing a mapping of the time offset value for the uplink transmission to a corresponding code state as indicated in an uplink grant downlink control information, DCI, in the control signal.

15. The apparatus of claim 10, wherein the processor is further configured to receive a control signal from the network node via the transceiver; determining a minimum time offset for transmission scheduling of the identified type of uplink transmission in accordance with the control signal; in determining a minimum time offset for the transmission schedule from the control signal, the processor can: determining the minimum time offset, wherein the minimum time offset is measured from a point in time when the control signal is received.

16. The apparatus of claim 10, wherein in performing the uplink transmission, the processor is capable of performing the uplink transmission under one of a plurality of sets of conditions, wherein one of the plurality of sets of conditions relates to one or more of a set of parameters, a resource allocation or a size of a bandwidth part BWP, a transport block size, a coding rate, a subband size configuration, a number of ports for channel state information, CSI, feedback, a type of CSI feedback, and a bandwidth type for the uplink transmission.

17. The apparatus of claim 16, wherein in the identifying the type of uplink transmission, the processor is capable of identifying a type of uplink transmission for UCI feedback multiplexed with data on a PUSCH, wherein a time offset for the uplink transmission for the UCI feedback multiplexed with data is the same as a time offset for PUSCH scheduling, and wherein the uplink transmission for UCI feedback multiplexed with data is performed within a time frame of the PUSCH under each of a plurality of sets of conditions.

18. The apparatus of claim 16, wherein in identifying the type of uplink transmission, the processor is capable of identifying a type of uplink transmission for UCI feedback not multiplexed with data on PUSCH, wherein a time offset for the uplink transmission for the UCI feedback not multiplexed with data is different than a time offset for PUSCH scheduling, and wherein the uplink transmission for UCI feedback not multiplexed with data is performed outside of a time frame for PUSCH scheduling at one or more of a plurality of sets of conditions.