Multiplexing of Uplink Control Information (UCI) on the Physical Uplink Shared Channel (PUSCH)

Abstract

Some aspects of the present disclosure relate to an apparatus and method for a user equipment (UE) to implement a technique of transmitting a configuration grant (CG) physical uplink shared channel (PUSCH) including uplink control information (UCI) without transmitting a physical uplink control channel (PUCCH). The UE determines a first set of CG PUSCHs based on a configuration received from a base station. Each CG PUSCH of the first set of CG PUSCHs overlaps with a PUCCH and is configured to transmit data from the UE to the base station. The UE further determines a second set of CG PUSCHs by excluding a third set of CG PUSCHs from the first set of CG PUSCHs, and selects a CG PUSCH from the second set of CG PUSCHs to carry the UCI included in the PUCCH. The UE further transmits the selected CG PUSCH including the UCI without transmitting the PUCCH.

Description

[Technical Field]

[0001] The described aspects generally relate to multiplexing uplink control information (UCI) onto a physical uplink shared channel (PUSCH). [Background technology]

[0002] The Third Generation Partnership Project (3GPP) has developed a new radio access technology known as 5th Generation (5G) New Radio (NR). The Physical Uplink Control Channel (PUCCH) is an uplink physical channel that carries uplink control information (UCI) from a user equipment (UE) to a base station. The 5G NR PUCCH is flexible in the time and frequency domains. The Physical Uplink Shared Channel (PUSCH) is the main uplink channel used to carry uplink user data from a UE to a base station. When a PUSCH is configured or granted but the UE does not have suitable user data to transmit, the PUSCH may be skipped or dropped if uplink skipping is enabled. However, simply skipping a granted PUSCH may cause reliability or complexity issues. Summary of the Invention

[0003] Some aspects of the present disclosure relate to apparatuses and methods for a user equipment (UE) to implement a technique for multiplexing uplink control information (UCI) onto a physical uplink shared channel (PUSCH) for uplink transmission from the user equipment (UE) to a base station. UCI is typically transmitted via a physical uplink control channel (PUCCH), and the PUSCH is used to carry user data. When there is no appropriate user data to transmit, if uplink skipping is enabled, the granted PUSCH may be dropped or skipped without any transmission from the UE. When a PUCCH and a PUSCH overlap, UCI intended for transmission by the PUCCH may be multiplexed and transmitted on the PUSCH without transmitting the PUCCH. There may be multiple PUSCHs overlapping with one PUCCH. In such a situation, even if there is no appropriate user data, the PUSCH may be transmitted instead of skipped, improving efficiency and / or reducing the base station's complexity in decoding hypotheses. A solution is needed for selecting an overlapped PUSCH from multiple PUSCHs to carry UCI for the PUCCH. The PUSCH may be a configured grant PUSCH or a dynamic grant PUSCH.

[0004] Some aspects of the present disclosure relate to a UE. The UE may include a transceiver configured to wirelessly communicate with a base station and a processor communicatively coupled to the transceiver. The processor of the UE is configured to identify a PUCCH configured to carry UCI. Additionally, the processor is configured to determine a first set of configuration grant PUSCHs based on a configuration received from the base station. Each configuration grant PUSCH in the first set of configuration grant PUSCHs overlaps with a PUCCH and is configured to transmit data from the UE to the base station. In some examples, the first set of configuration grant PUSCHs may include a configuration grant type 1 PUSCH based on a configuration provided by radio resource control (RRC) configuration signaling or a configuration grant type 2 PUSCH based on a configuration provided by a physical downlink control channel (PDCCH).

[0005] According to some aspects, the processor is further configured to determine a second set of configuration grant PUSCHs by excluding a third set of configuration grant PUSCHs from the first set of configuration grant PUSCHs. In some examples, the third set of configuration grant PUSCHs excluded from the first set of PUSCHs includes configuration grant PUSCHs that include symbols that collide with semi-static downlink (DL) symbols, DL symbols indicated by dynamic downlink control information (DCI), or flexible symbols indicated by a slot format indicator.

[0006] The processor is then configured to select a configured grant PUSCH from the second set of configured grant PUSCHs to carry the UCI included in the PUCCH. The processor may be configured to select a configured grant PUSCH from the second set of configured grant PUSCHs based on an index of the configured grant PUSCH, a logical channel priority of data mapped to the configured grant PUSCH, or a transmission duration of the configured grant PUSCH. In some examples, the processor may be configured to select a configured grant PUSCH from the second set of configured grant PUSCHs that has the smallest index of each configured grant PUSCH, the highest logical channel priority of data mapped to each configured grant PUSCH, or the shortest transmission duration of each configured grant PUSCH. In some other examples, the processor may be configured to operate a medium access control (MAC) layer to select a configured grant PUSCH from the second set of configured grant PUSCHs.

[0007] According to some aspects, the processor may be further configured to determine that no dynamic grant PUSCH overlaps with the PUCCH or the selected configuration grant PUSCH. Additionally or alternatively, the processor may be configured to determine that a dynamic grant PUSCH overlaps with the selected configuration grant PUSCH and that downlink control information (DCI) for the dynamic grant PUSCH is received at a time point separated from the start of the PUCCH and the start of the selected configuration grant PUSCH by less than a predetermined time interval.

[0008] According to some aspects, the selected configured grant PUSCH may carry UCI of the PUCCH. In addition, the selected configured grant PUSCH may carry data generated by a logical channel (LCH) of the MAC layer to be transmitted to the base station. In some examples, the data is selected from a logical channel (LCH) of the MAC layer even if the LCH does not satisfy a pre-configured condition for mapping the LCH of the MAC layer to the selected configured grant PUSCH. For example, the LCH of the MAC layer does not satisfy a pre-configured condition for an allowed subcarrier spacing index value, a PUSCH transmission duration, a configured grant type, cell information, a configured grant index, or a priority index.

[0009] According to some aspects, the processor may be further configured to transmit a selected configured grant PUSCH including UCI and possibly including data generated by the LCH, whereby the UCI is multiplexed with data from the LCH that satisfies pre-configured conditions or data from the LCH that does not satisfy certain pre-configured conditions, and thus the PUCCH may be omitted.

[0010] Some aspects of the present disclosure relate to a method performed by a UE. The method includes identifying a PUCCH configured to carry UCI to be transmitted to a base station. The method further includes determining a first set of configured grant PUSCHs based on a configuration received from the base station. Each configured grant PUSCH in the first set of configured grant PUSCHs overlaps with a PUCCH and is configured to transmit data from the UE to the base station. Then, the method includes determining a second set of configured grant PUSCHs by excluding a third set of configured grant PUSCHs from the first set of configured grant PUSCHs, and selecting a configured grant PUSCH from the second set of configured grant PUSCHs to carry the UCI included in the PUCCH. The method further includes transmitting the selected configured grant PUSCHs including the UCI without transmitting the PUCCH.

[0011] Some aspects of the present disclosure relate to a non-transitory computer-readable medium storing instructions. The instructions, when executed by a processor of a UE, cause the UE to perform various operations. The operations include identifying a PUCCH configured to carry UCI to be transmitted to a base station. The operations further include determining a first set of configured grant PUSCHs based on a configuration received from the base station. Each configured grant PUSCH in the first set of configured grant PUSCHs overlaps with a PUCCH and is configured to transmit data from the UE to the base station. The operations also include determining a second set of configured grant PUSCHs by excluding a third set of configured grant PUSCHs from the first set of configured grant PUSCHs and selecting a configured grant PUSCH from the second set of configured grant PUSCHs to carry the UCI included in the PUCCH. The operations further include transmitting the selected configured grant PUSCHs containing the UCI without transmitting a PUCCH.

[0012] This Summary of the Invention is provided merely for the purpose of illustrating some aspects to provide an understanding of the subject matter described herein. Accordingly, the above features are merely examples and should not be construed as narrowing the scope or spirit of the subject matter in this disclosure. Other features, aspects, and advantages of the present disclosure will become apparent from the following Detailed Description, Figures, and Claims. [Brief explanation of the drawings]

[0013] The accompanying drawings, which are incorporated in and form a part of this specification, illustrate the present disclosure and, together with the description, further serve to explain the principles of the present disclosure and to enable one skilled in the art(s) to make and use the present disclosure.

[0014] [Figure 1]1 illustrates a wireless system including a user equipment (UE) that transmits a configuration grant physical uplink shared channel (PUSCH) that includes uplink control information (UCI) without transmitting a physical uplink control channel (PUCCH) in accordance with certain aspects of the present disclosure.

[0015] [Figure 2] FIG. 1 is a block diagram of a UE that performs functions described herein, in accordance with certain aspects of the present disclosure.

[0016] [Figure 3A] 1 illustrates an example of a relationship between a configured grant PUSCH, a dynamic grant PUSCH, and a PUCCH in accordance with certain aspects of the present disclosure. [Figure 3B] 1 illustrates an example of a relationship between a configured grant PUSCH, a dynamic grant PUSCH, and a PUCCH in accordance with certain aspects of the present disclosure.

[0017] [Figure 4] 1 illustrates an example method performed by a UE and a base station for transmitting a configuration grant PUSCH including UCI without transmitting a PUCCH, in accordance with certain aspects of the present disclosure.

[0018] [Figure 5] 1 illustrates an example method performed by a UE to transmit a configuration grant PUSCH including UCI without transmitting a PUCCH, in accordance with certain aspects of the present disclosure.

[0019] [Figure 6] FIG. 1 illustrates an example computer system that may implement some aspects or portions thereof of the disclosure provided herein.

[0020] The present disclosure is described with reference to the accompanying drawings, in which like reference numbers generally indicate identical or functionally similar elements. Additionally, the left-most digit(s) of a reference number generally identifies the drawing in which the reference number first appears. DETAILED DESCRIPTION OF THE INVENTION

[0021] In wireless systems, such as fifth-generation (5G) New Radio (NR) systems, a physical uplink control channel (PUCCH) can be used to carry uplink control information (UCI) from a user equipment (UE) to a base station, and a physical uplink shared channel (PUSCH) can be used to carry user data from the UE to a base station. When a PUSCH is granted but the UE does not have appropriate user data to transmit, the PUSCH can be skipped or dropped if uplink skipping is enabled. However, if the PUSCH overlaps with a PUCCH, the UCI contained in the PUCCH can be multiplexed onto the PUSCH, and the PUSCH is not skipped. Instead, the PUCCH is not transmitted. In Rel-16, the decision on which PUSCH to multiplex UCI onto is made before the UE knows whether there is useful data available to map onto the PUSCH. This deterministic UE behavior avoids the need to implement different hypotheses for each PUSCH, assuming that UCI is or is not multiplexed thereon, since in the case of multiple PUSCHs overlapping with a PUCCH, the base station knows on which PUSCH UCI is multiplexed.

[0022] The PUSCH can be dynamically scheduled as a dynamic grant (DG) PUSCH by an UL grant in the DCI, or can be a configured grant (CG) type 1 or type 2. CG PUSCH type 1 can be semi-statically configured to operate without detection of an UL grant in the DCI upon receiving higher layer parameters called configuredGrantConfig that include an rrc-ConfiguredUplinkGrant. CG PUSCH type 2 can be semi-persistently scheduled by an UL grant in a valid activation DCI after receiving higher layer parameters called configuredGrantConfig that do not include an rrc-ConfiguredUplinkGrant. For the CG PUSCH, the parameters applied for transmission are provided by configuredGrantConfig, except for dataScramblingIdentityPUSCH, txConfig, codebookSubset, maxRank, and scaling of UCI-OnPUSCH, which are provided by pusch-Config. Upon detecting DCI scheduling a DG PUSCH, the UE 101 may transmit the corresponding DG PUSCH as long as the UE does not generate a transport block and there is no PUCCH with CSI / HARQ-ACK that overlaps in time with the DG PUSCH. In some examples, when a DG PUSCH overlaps with a CG PUSCH, the CG PUSCH may be dropped rather than transmitted. When there are multiple CG PUSCHs and DG PUSCHs that overlap with a PUCCH, a mechanism may be deployed herein to select a CG PUSCH or a DG PUSCH that transmits UCI included in the PUCCH, and the PUCCH may be skipped. The mechanism presented in this disclosure allows the UE to select a CG PUSCH or a DG PUSCH after determining whether there is suitable data available to map to the PUSCH.

[0023] Some aspects of the present disclosure provide a mechanism for selecting a CG PUSCH from a set of CG PUSCHs to carry UCI included in a PUCCH and transmitting the selected CG PUSCH including the UCI without transmitting a PUCCH. In some examples, there may be no DG PUSCH that overlaps with the PUCCH or that overlaps with the selected CG PUSCH. In some other examples, there may be a DG PUSCH that overlaps with the selected CG PUSCH, but the DCI for that DG PUSCH is received at a time point that is less than a predetermined time interval away from the start of the selected CG PUSCH.

[0024] According to some aspects, a UE can determine a first set of CG PUSCHs based on a configuration received from a base station, where each CG PUSCH in the first set of CG PUSCHs overlaps with a PUCCH. The UE can determine a second set of CG PUSCHs by excluding a third set of CG PUSCHs from the first set of CG PUSCHs. A CG PUSCH can be excluded if it contains a symbol that collides with a semi-static DL symbol, a DL symbol indicated by a dynamic DCI, or a flexible symbol indicated by a slot format indicator. Furthermore, a CG PUSCH from the second set of CG PUSCHs can be selected based on an index of the CG PUSCH, a logical channel priority of the data mapped to the CG PUSCH, or a transmission duration of the CG PUSCH.

[0025] FIG. 1 illustrates a wireless system 100 including a UE, e.g., UE 101, that transmits a CG PUSCH including UCI without transmitting a PUCCH, in accordance with certain aspects of the present disclosure. FIG. 2 illustrates a block diagram of a UE, e.g., UE 101, that performs functions described herein, in accordance with certain aspects of the present disclosure. FIGS. 3A-3B illustrate examples of relationships between a CG PUSCH, a DG PUSCH, and a PUCCH, in accordance with certain aspects of the present disclosure. The wireless system 100 is provided for illustrative purposes only and is not intended to limit the aspects of the disclosure. The wireless system 100 may include, but is not limited to, a UE 101, a base station 103, and a base station 105, all of which are communicatively coupled to a core network 107. The UE 101 communicates with the base station 103 via a carrier 106 and with the base station 105 via a carrier 108.

[0026] In some examples, the wireless system 100 may be an NR system, an LTE system, a 5G system, or another wireless system. While many examples are described herein in the context of an NR system, the wireless system 100 is not limited to an NR system. Rather, the wireless system may be any wireless system in which a UE transmits a CG PUSCH including UCI without transmitting a PUCCH, or performs other functions described in this disclosure. Other network entities (not shown), such as a network controller, a relay station, etc., may also be present. The wireless system 100 may support a wide range of use cases, such as enhanced mobile broadband (eMBB), massive machine-type communications (mMTC), ultra-reliable and low-latency communications (URLLC), and enhanced vehicle-to-everything communications (eV2X).

[0027] According to some aspects, base station 103 and base station 105 may be fixed stations or mobile stations. Base station 103 and base station 105 may also be referred to by other names such as base transceiver system (BTS), access point (AP), transmit / receive point (TRP), evolved Node B (eNB), next generation Node B (gNB), 5G Node B (NB), or other equivalent terms. In some examples, base station 103 and base station 105 may be interconnected with each other and / or with other base stations or network nodes in the network through various types of backhaul interfaces not shown, such as direct physical connections, virtual networks, etc.

[0028] According to some aspects, the UE 101 may be fixed or mobile. The UE 101 may be a cellular phone (e.g., a smartphone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop, a desktop, a cordless phone, a wireless local loop station, a tablet, a camera, a gaming device, a netbook, an ultrabook, a medical device or equipment, a biometric sensor or device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, smart jewelry such as a smart wristband, a smart ring, or a smart bracelet), an entertainment device (e.g., a music or video device, or satellite radio), a vehicle component, a smart meter, industrial manufacturing equipment, a global positioning system device, an Internet of Things (IoT) device, a machine type communications (MTC) device, an evolved or enhanced machine type communications (eMTC) device, or any other suitable device configured to communicate over a wireless medium. For example, MTC and eMTC devices may include robots, drones, location tags, etc.

[0029] According to some aspects, base station 103 and base station 105 may be communicatively coupled to core network 107. Base station 103 may serve cell 102, and base station 105 may serve cell 104 contained within cell 102. In some other embodiments, cell 102 may partially overlap with cell 104. Cell 102 or cell 104 may be a macrocell, a picocell, a femtocell, and / or another type of cell. By comparison, a macrocell may cover a relatively large geographic area, e.g., a radius of several kilometers, a femtocell may cover a relatively small geographic area, e.g., a home, and a picocell may cover an area smaller than the coverage area of ​​a macrocell but larger than the coverage area of ​​a femtocell. For example, cell 102 may be a macrocell, and cell 104 may be a picocell or a femtocell. Furthermore, cell 102 may be a picocell, and cell 104 may be a femtocell. In some examples, the geographic area of ​​a cell may move according to the location of a mobile base station.

[0030] According to some aspects, base station 103 may be a serving base station, and cell 102 may be a serving or primary cell. Cell 104 may be a secondary cell. Although not shown, UE 101 may have other secondary cells. Data for UE 101 may be transferred between UE 101 and core network 107 simultaneously over a wireless connection between UE 101 and base station 105 at one carrier frequency (e.g., a component carrier such as carrier 106) and one or more wireless connections between UE 101 and base station 103 at another carrier frequency (e.g., a component carrier such as carrier 108).

[0031] According to some aspects, the UE 101 may include a processor 109 that operates a protocol stack including multiple protocol layers, such as, for example, a physical (PHY) layer 110, in accordance with the description provided herein. In particular, the PHY 110 may include a PUCCH 111 configured to carry UCI 113, a CG PUSCH 112 that carries data 114, and a DG PUSCH 115. In some examples, when the CG PUSCH 112 and the PUCCH 111 overlap in time and the DG PUSCH 115 does not overlap with the CG PUSCH 112 and the PUCCH 111, the UCI 113 may be multiplexed into the CG PUSCH 112 such that the CG PUSCH 112 can carry both the data 114 and the UCI 113 to be transmitted to the base station 103. There may be multiple CG PUSCHs, including the CG PUSCH 112, and further details are shown in FIG. 2.

[0032] In some examples, the UCI 113 may include hybrid automatic repeat request (HARQ) feedback, channel state information (CSI), a scheduling request (SR), or other control information. The PUCCH 111 may be in various formats, such as a short PUCCH occupying one or two OFDM symbols, such as PUCCH formats 0 and 2, or a long PUCCH occupying four to fourteen OFDM symbols, such as PUCCH formats 1, 3, and 4. PUCCH formats 0 and 1 carry a UCI payload having one or two bits. Other PUCCH formats carry a UCI payload having three or more bits.

[0033] In some examples, data 114 may not be available. In such a case, if the CG PUSCH 112 does not overlap with the PUCCH 111, the CG PUSCH 112 may be dropped or skipped without being transmitted to the base station 103. On the other hand, if the CG PUSCH 112 overlaps with the PUCCH 111 and the DG PUSCH 115 does not overlap with the CG PUSCH 112 and the PUCCH 111, the UCI 113 may be transmitted within the CG PUSCH 112, without transmitting data at the same time. Thus, the PUCCH 111 may be skipped without being transmitted.

[0034] In some other examples, when data 114 is not available, the CG PUSCH 112 overlaps with the PUCCH 111, and the DG PUSCH 115 overlaps with the CG PUSCH 112 and the PUCCH 111, the UCI 113 may be transmitted within the DG PUSCH 115. Thus, both the PUCCH 111 and the CG PUSCH 112 may be skipped without being transmitted.

[0035] 2 shows a block diagram of a UE 101 having an antenna panel 217 including one or more antenna elements, such as antenna element 219, coupled to a transceiver 203 and controlled by a processor 109. In particular, the transceiver 203 may include radio frequency (RF) circuitry 216, baseband transmit circuitry 212, and baseband receive circuitry 214. The RF circuitry 216 may include multiple parallel RF chains for one or more of the transmit or receive functions, each connected to one or more antenna elements of the antenna panel. Additionally, the processor 109 may be communicatively coupled to a memory device 201, which is further coupled to the transceiver 203. The processor 109, alone or in combination with instructions in the memory device 201 and the transceiver 203, may perform or cause the transmission of a configuration grant PUSCH including the UCI functionality described herein.

[0036] According to some aspects, the memory device 201 may store information regarding a protocol stack, which may include a PHY 110, a MAC layer 220, an RRC layer 230, or more layers. The PHY 110 may include a PUCCH 111 configured to carry UCI 113, a CG PUSCH 112 carrying data 114, a DG PUSCH 115, and a configuration 211 received from the base station 103. The MAC layer 220 may include a logical channel (LCH) 221 that generates data 223, such as a MAC protocol data unit (PDU), and an LCH 222 that generates data 224.

[0037] According to some aspects, the processor 109 may determine a first set of CG PUSCHs 213 based on the configuration 211. Each CG PUSCH in the first set of CG PUSCHs 213 overlaps with a PUCCH 111 and is configured to transmit data from the UE 101 to the base station 103. Data, such as data 223 or data 224, may be generated by the MAC layer 220. In some examples, the first set of CG PUSCHs 213 may include a CG type 1 PUSCH based on a configuration provided by RRC configuration signaling or a CG type 2 PUSCH based on a configuration provided by a physical downlink control channel (PDCCH). For a CG PUSCH with repetition (either repetition type A or type B), each CG PUSCH repetition may be considered a separate CG PUSCH. Similarly, for CG PUSCHs in NR unlicensed spectrum (NR-U), each of multiple CG PUSCHs configured in one or more slots may be considered separately.

[0038] The processor 109 may further determine the second set of CG PUSCHs 215 by excluding a third set of CG PUSCHs from the first set of CG PUSCHs 213. In some examples, a CG PUSCH may be excluded from the first set of CG PUSCHs 213 if it contains a symbol that collides with a semi-static downlink (DL) symbol. If a CG PUSCH contains a symbol that collides with a semi-static downlink (DL) symbol, it is not transmitted and cannot be used to convey UCI 113 to the base station 103. Similarly, a CG PUSCH may be excluded from the first set of CG PUSCHs 213 if it contains a symbol that collides with a DL symbol indicated by a dynamic DCI or a flexible symbol indicated by a slot format indicator. In some other examples, the third set of CG PUSCHs may be an empty set, and no CG PUSCHs are excluded from being considered as candidates for carrying UCI 113. However, even if a CG PUSCH is selected to carry UCI 113, if the selected CG PUSCH collides with a DL symbol, the selected CG PUSCH may be dropped, and therefore the UCI 113 will also be dropped, which may cause efficiency and reliability problems for the UE 101 and the base station 103.

[0039] The processor 109 may then select a CG PUSCH from the second set of CG PUSCHs 215 to carry the UCI 113 included in the PUCCH 111. The selected CG PUSCH is denoted as the CG PUSCH 112. In some examples, multiple CG PUSCHs in the second set of CG PUSCHs 215 may correspond to the same serving cell and possibly start simultaneously. The CG PUSCH 112 may be selected from the second set of CG PUSCHs 215 based on the index of the CG PUSCH 112, the logical channel priority of the data mapped to the CG PUSCH 112, the transmission duration of the CG PUSCH 112, or the start time of the CG PUSCH 112. For example, the CG PUSCH 112 may have the smallest index of the CG PUSCHs in the second set of CG PUSCHs 215. Additionally or alternatively, the CG PUSCH 112 may have the highest logical channel priority of the data mapped to each CG PUSCH in the second set of CG PUSCHs 215, the shortest transmission duration of each CG PUSCH in the second set of CG PUSCHs 215, or an earlier start time. A combination of the above alternatives may also be used. The above examples are provided for illustrative purposes only and are not intended to limit the aspects of the disclosure. For example, the CG PUSCH 112 may have the highest index, lowest logical channel priority, or longest transmission duration of each CG PUSCH in the second set of CG PUSCHs 215.

[0040] In some other examples, the processor 109 may operate the MAC layer 220 to select a CG PUSCH 112 from the second set 215 based on data availability and prioritization. Initially, the PHY 110 does not make a decision about which one of the second set of CG PUSCHs 215 to use for UCI multiplexing. Instead, the PHY 110 instructs the MAC layer 220 to make such a decision. The MAC layer 220 performs prioritization and transmits the selected CG PUSCH 112 along with data, such as data 223 or data 224, to the PHY 110. The PHY 110 receives the data for the selected CG PUSCH 112 from the MAC layer 220 and further multiplexes the UCI 113 onto the selected CG PUSCH 112. If the PHY 110 does not receive data for any CG PUSCH in the second set of CG PUSCHs 215, the UCI may be dropped or transmitted on the PUCCH 111. Additionally or alternatively, a combination of rules may be applied to select a CG PUSCH 112 from the second set of CG PUSCHs 215. For example, the UE 101 may first select the CG PUSCH(s) with the earliest start time, and then, if multiple CG PUSCHs with the earliest start time exist, choose one depending on the MAC layer 220.

[0041] According to some aspects, to cause the selected CG PUSCH 112 to transmit the UCI 113, the processor 109 may further determine that no DG PUSCH overlaps with the PUCCH 111 or the selected CG PUSCH 112. For example, the processor 109 may further determine that the DG PUSCH 115 does not overlap with the PUCCH 111 or the selected CG PUSCH 112. As shown in FIG. 3A , the PUCCH 111 is within time interval [T1, T2], the CG PUSCH 112 is within time interval [T3, T4], and the DG PUSCH 115 is within time interval [T5, T6]. The time interval [T1, T2] overlaps with the time interval [T3, T4], but both [T1, T2] and [T3, T4] do not overlap with [T5, T6].

[0042] Additionally or alternatively, when the DG PUSCH 115 overlaps with the CG PUSCH 112 but not with the PUCCH 111, the UE expects the DCI 301 for the DG PUSCH 115 to be received a predetermined time interval away from the earlier of the start of the PUCCH 111 or the start of the CG PUSCH 112. This predetermined time interval is intended to provide the UE with sufficient time to make and process UCI multiplexing decisions. As shown in FIG. 3B, the PUCCH 111 falls within time interval [T1, T2], the CG PUSCH 112 falls within time interval [T3, T4], and the DG PUSCH 115 falls within time interval [T7, T8]. Time interval [T1, T2] overlaps with time interval [T3, T4]. Furthermore, time interval [T7, T8] overlaps with time interval [T3, T4]. The DG PUSCH 115 is configured by the DCI 301 received at time T9. The time distance between T9 and T3, the start of the CG PUSCH 112, is I1. If I1 is greater than a predetermined value, the UE can choose the DG PUSCH 115 over the CG PUSCH 112 for data prioritization, in which case the CG PUSCH 112 is dropped and the UCI 113 is still transmitted using the PUCCH 111 because it does not overlap with the DG PUSCH 115. Alternatively, the UE may still choose to multiplex the UCI 113 onto the CG PUSCH 112, in which case the UCI 113 is dropped along with the CG PUSCH 112.

[0043] On the other hand, if I1 is smaller than a predetermined value, the UE 101 may treat it as an error. A CG PUSCH 112 may still be selected to transmit with a multiplexed UCI 113. In this case, the DG PUSCH 115 may be treated as an error. If the CG PUSCH 112 has a multiplexed UCI 113, the UE 101 does not expect to be scheduled a DG PUSCH 115 that overlaps with the CG PUSCH 112 on the same serving cell.

[0044] According to some aspects, the selected CG PUSCH 112 may carry the UCI 113 of the PUCCH 111. Additionally, the CG PUSCH 112 may carry data generated by an LCH of the MAC layer 220, e.g., by LCH 221 or LCH 222, to be transmitted to the base station 103. In some examples, data is selected from an LCH of the MAC layer 220 when certain pre-configured conditions for mapping the LCH to the selected CG PUSCH 112 are met.

[0045] In some examples, data from the LCH may be mapped to the CG PUSCH 112 if the following conditions are met: (1) the set of allowed subcarrier spacing index (SCS) values ​​in the allowedSCS-List, if configured, includes the subcarrier spacing index associated with the CG PUSCH 112; (2) the maxPUSCH-duration, if configured, is greater than or equal to the PUSCH transmission duration associated with the CG PUSCH 112; (3) the configuredGrantType1Allowed, if configured, is set to “true” if the CG PUSCH 112 is of configured grant type 1; (4) the allowedServingCells, if configured, includes cell information associated with the CG PUSCH 112; (5) the allowedCG-List, if configured, includes the configured grant index associated with the CG PUSCH 112; and (6) the allowedPHY-PriorityIndex, if set, includes the priority index associated with the CG PUSCH 112.

[0046] In some other examples, when there is no data from the LCH that meets all the conditions for mapping the data to the CG PUSCH 112, the MAC layer 220 may generate padding, e.g., an empty MAC PDU, for the CG PUSCH 112 that is multiplexed with the UCI 113. The UE 101 may transmit the CG PUSCH 112 carrying the UCI 113 with padding. However, the padding may result in resource inefficiency, unnecessary UE power consumption, and unnecessary interference.

[0047] In some other examples, data may be selected from an LCH of the MAC layer 220 even if the LCH does not meet certain preset conditions for mapping the LCH to the selected CG PUSCH 112. For example, the LCH of the MAC layer 220 does not meet preset conditions regarding the allowed subcarrier spacing index value, the PUSCH transmission duration, the configured grant type, the cell information, the configured grant index, or the priority index. The UE 101 or the base station 103 may determine which preset conditions can be waived and cause the LCH of the MAC layer 220 that does not meet the waived preset conditions to be mapped to the CG PUSCH 112.

[0048] Furthermore, the principles for mapping data generated by the LCH of the MAC layer 220 described above may be applied to the DG PUSCH as well. For example, if a DG PUSCH is selected to carry UCI 113 from the PUCCH 111, data may be selected for inclusion in the DG PUSCH to be multiplexed with the UCI 113. First, data from the LCH may be mapped to the DG PUSCH if certain pre-configured conditions are met. If no such data is available that meets all of the pre-configured conditions, one or more of the conditions may be waived so that data can be selected for carrying on the DG PUSCH and multiplexed with the UCI 113.

[0049] According to some aspects, the processor 109 may be further configured to transmit the CG PUSCH 112, which includes the UCI 113 and may include data generated by the LCH. Thus, the UCI 113 is multiplexed with data from the LCH that meets preset conditions or data from the LCH that does not meet certain preset conditions. Thus, the PUCCH 111 may be skipped without being transmitted to the base station 103.

[0050] 4 illustrates an example method 400 performed by a UE 101 and a base station 103 for transmitting a CG PUSCH including UCI without transmitting a PUCCH, in accordance with some aspects of the present disclosure. The method 400 may be performed by the UE 101 and the base station 103 as shown in FIGS. 1-3.

[0051] At 401, the UE 101 may identify a PUCCH configured to carry UCI. For example, the UE 101 may identify that the PUCCH 111 is configured to carry UCI 113.

[0052] At 402, the UE 101 may receive a configuration from a base station to configure a CG PUSCH. For example, the UE 101 may receive a configuration 211 from the base station 103 to configure a first set 213 of CG PUSCHs.

[0053] At 404, the UE 101 may receive DCI from the base station 103 to configure the DG PUSCH. For example, the UE 101 may receive DCI 301 from the base station 103 to set up the DG PUSCH 115.

[0054] At 405, the UE 101 may identify available CG PUSCHs or DGPUSCHs that overlap with its PUCCH, if any, based on the configuration or DCI received from the base station, and may further select a CG PUSCH for transmitting UCI. On the other hand, if a CG PUSCH does not overlap with a PUCCH, the CG PUSCH may be skipped. For example, the UE 101 may determine that the first set of CG PUSCHs 215 includes a CG PUSCH that overlaps with a PUCCH 111 and further select a CG PUSCH 112 for transmitting UCI 113. A more detailed operation of 405 is shown in FIG. 5.

[0055] At 407, the UE 101 may determine available data to transmit via the selected CG PUSCH. For example, the UE 101 may further determine whether there is available data to transmit via the selected CG PUSCH 112.

[0056] At 409, when data is available for transmission, the UE 101 may map data from a logical channel to the selected CG PUSCH. For example, the UE 101 may map data 223 from logical channel 221 to the selected CG PUSCH 112.

[0057] At 411, the UE 101 may multiplex the UCI of the PUCCH onto the selected CG PUSCH. For example, the UE 101 may multiplex the UCI 113 of the PUCCH 111 onto the selected CG PUSCH 112.

[0058] At 412, the UE 101 may transmit the selected CG PUSCH carrying the UCI of the PUCCH to the base station. For example, the UE 101 may transmit the selected CG PUSCH 112 carrying the UCI 113 of the PUCCH 111 to the base station 103.

[0059] 5 illustrates an example method 500 performed by a UE to transmit a CG PUSCH including UCI without transmitting a PUCCH, according to some aspects of the present disclosure. Method 500 may be performed by UE 101 as shown in FIGS. 1-2. Method 500 may be an example of detailed operations performed at 405 shown in FIG.

[0060] At 502, the UE 101 may identify a PUCCH configured to carry UCI. For example, the UE 101 may determine that the PUCCH 111 is configured to carry UCI 113, similar to the operations performed at 401.

[0061] At 504, the UE 101 can determine a first set of CG PUSCHs based on a configuration received from the base station, where each CG PUSCH in the first set of CG PUSCHs overlaps with a PUCCH and is configured to transmit data from the UE to the base station. For example, the UE 101 can determine a first set of CG PUSCHs 213 based on a configuration 211, where each CG PUSCH in the first set of CG PUSCHs 213 overlaps with a PUCCH 111.

[0062] At 506, the UE 101 may determine a second set of CG PUSCHs by excluding a third set of CG PUSCHs from the first set of configuration grant PUSCHs. For example, the UE 101 may determine a second set of CG PUSCHs 215 by excluding a third set of CG PUSCHs from the first set of CG PUSCHs 213. Various criteria may be applied to exclude CG PUSCHs from being considered to carry UCI, for example, excluding CG PUSCHs that include symbols that collide with semi-static downlink (DL) symbols, as described with respect to FIGS. 1-2.

[0063] At 508, the UE 101 may select a CG PUSCH from the second set of CG PUSCHs to carry the UCI included in the PUCCH. For example, the UE 101 may select a CG PUSCH 215 from the second set of CG PUSCHs 112 to carry the UCI 113 included in the PUCCH 111. Various techniques may be applied to select a CG PUSCH from the second set of CG PUSCHs, for example, the selection may be based on an index of the CG PUSCH, a logical channel priority of the data mapped to the CG PUSCH, or a transmission duration of the CG PUSCH, as described with respect to FIGS.

[0064] At 510, the UE 101 may transmit the selected CG PUSCH carrying the UCI of the PUCCH to the base station. For example, the UE 101 may transmit the selected CG PUSCH 112 carrying the UCI 113 of the PUCCH 111 to the base station 103.

[0065] Various aspects may be implemented using one or more computer systems, such as computer system 600 shown in FIG. 6 . Computer system 600 may be any computer capable of performing the functions described herein, such as UE 101, base station 103, or base station 105, as shown in FIGS. 1 and 2 . Computer system 600 includes one or more processors (also referred to as central processing units, or CPUs), such as processor 604. Processor 604 is connected (e.g., via a bus) to a communications infrastructure 606. Computer system 600 also includes user input / output device(s) 603, such as a monitor, keyboard, pointing device, etc., that communicate with communications infrastructure 606 via user input / output interface(s) 602. Computer system 600 also includes main or primary memory 608, such as random access memory (RAM). Main memory 608 may include one or more levels of cache. Main memory 608 stores control logic (e.g., computer software) and / or data.

[0066] Computer system 600 may also include one or more secondary storage devices or secondary memories 610. Secondary memories 610 may include, for example, a hard disk drive 612 and / or a removable storage device or drive 614. Removable storage drive 614 may be a floppy disk drive, a magnetic tape drive, a compact disk drive, an optical storage device, a tape backup device, and / or any other storage device / drive.

[0067] The removable storage drive 614 may interface with a removable storage unit 618. The removable storage unit 618 includes a computer-usable or computer-readable storage device on which computer software (control logic) and / or data is stored. The removable storage unit 618 may be a floppy disk, magnetic tape, compact disk, DVD, optical storage disk, and / or any other computer data storage device. The removable storage drive 614 reads from and / or writes to the removable storage unit 618 in a well-known manner.

[0068] According to some aspects, secondary memory 610 may include other means, instrumentalities, or techniques for making computer programs and / or other instructions and / or data accessible by computer system 600. Examples of such means, instrumentalities, or techniques may include, for example, removable storage unit 622 and interface 620. Examples of removable storage unit 622 and interface 620 may include a program cartridge and cartridge interface (such as those found in video game devices), a removable memory chip (such as an EPROM or PROM) and associated socket, a memory stick and USB port, a memory card and associated memory card slot, and / or any other removable storage unit and associated interface.

[0069] In some examples, main memory 608, removable storage unit 618, removable storage unit 622 may store instructions that, when executed by processor 604, cause processor 604 to perform operations for a UE or a base station, such as UE 101, base station 103, or base station 105 shown in Figures 1 and 2. In some examples, the operations include those shown and described in Figures 3-4.

[0070] Computer system 600 may further include a communications or network interface 624. Communications interface 624 enables computer system 600 to communicate and interact with any combination of remote devices, remote networks, remote entities, etc. (individually and collectively referred to by reference numeral 628). For example, communications interface 624 enables computer system 600 to communicate with remote devices 628 via communications path 626, which may be wired and / or wireless and may include any combination of a LAN, a WAN, the Internet, etc. Control logic and / or data may be transmitted to and from computer system 600 via communications path 626. Operations of communications interface 624 may be performed by a wireless controller and / or a cellular controller. The cellular controller may be a separate controller for managing communications according to different wireless communication technologies. Operations in the foregoing aspects may be implemented in a wide variety of configurations and architectures. Thus, some or all of the operations in the foregoing aspects may be performed in hardware, software, or both. In some aspects, a tangible, non-transitory apparatus or article of manufacture, also referred to herein as a computer program product or program storage device, includes a tangible, non-transitory computer-usable or readable medium having control logic (software) stored thereon. This may include, but is not limited to, computer system 600, main memory 608, secondary memory 610, removable storage units 618 and 622, and tangible articles of manufacture embodying any combination of the foregoing. Such control logic, when executed by one or more data processing devices (e.g., computer system 600), causes such data processing devices to operate as described herein.

[0071] Based on the teachings contained herein, it will be apparent to one skilled in the relevant art(s) how to make and use aspects of the present disclosure using data processing devices, computer systems and / or computer architectures other than those shown in Figure 6. In particular, aspects may operate with software, hardware, and / or operating system implementations other than those described herein.

[0072] It is understood that it is the "Detailed Description" section, and not the "Summary" and "Abstract" sections, that are intended to be used to interpret the claims. The Summary and Abstract sections may describe one or more exemplary aspects of the disclosure, but not all of the exemplary aspects of the disclosure, as contemplated by the inventor(s), and therefore, the Summary and Abstract sections are not intended to limit the scope of the disclosure or the appended claims in any way.

[0073] While the present disclosure is described herein with reference to exemplary embodiments for exemplary fields and applications, it should be understood that the present disclosure is not limited to the exemplary embodiments. Other embodiments and variations of the embodiments are possible and are within the scope and spirit of the present disclosure. By way of example, and without limiting the generality of this paragraph, the embodiments are not limited to the software, hardware, firmware, and / or entities shown in the figures and / or described herein. Moreover, the embodiments (whether or not explicitly described herein) have significant utility for fields and applications beyond the examples described herein.

[0074] Aspects have been described herein with the help of functional building blocks that illustrate the implementation of certain functions and relationships thereof. Boundaries of these functional building blocks have been arbitrarily defined herein for convenience of description. Alternative boundaries may be defined so long as the specified functions and relationships (or their equivalents) are appropriately performed. In addition, alternative aspects may execute functional blocks, steps, operations, methods, etc. using an order different from that described herein.

[0075] References herein to "one embodiment," "one embodiment," "exemplary embodiment," or similar phrases indicate that the described embodiment may include a particular feature, structure, or characteristic, but not all embodiments necessarily include the particular feature, structure, or characteristic. Also, such phrases do not necessarily refer to the same embodiment. Furthermore, when a particular feature, structure, or characteristic is described in the context of one embodiment, it is within the knowledge of one of ordinary skill in the relevant art(s) to incorporate such particular feature, structure, or characteristic into other aspects, whether or not explicitly mentioned or described herein.

[0076] The breadth and scope of the present disclosure should not be limited by any of the above-described exemplary embodiments, but should be defined only in accordance with the following claims and their equivalents.

[0077] It is understood that use of personally identifiable information should comply with generally recognized privacy policies and practices that meet or exceed industry or government requirements for maintaining user privacy. In particular, personally identifiable information data should be managed and handled in a manner that minimizes the risk of unintended or unauthorized access or use, and the nature of authorized uses should be clearly indicated to users.

[0078] In one or more embodiments, for example, at least one of the components depicted in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes, and / or methods as described in the Examples section below. For example, circuitry associated with a sled device, router, network element, etc. described above in connection with one or more of the foregoing figures may be configured to operate according to one or more of the examples described in the Examples section below.

Claims

1. A user equipment (UE), a transceiver configured to wirelessly communicate with a base station; a processor communicatively coupled to the transceiver, the processor comprising: Identifying a physical uplink control channel (PUCCH) configured to carry uplink control information (UCI); determining a first set of configured grant physical uplink shared channels (PUSCHs) based on the configuration received from the base station, where each configured grant PUSCH in the first set of configured grant PUSCHs overlaps with the PUCCH and is configured to transmit data from the UE to the base station; determining a second set of configured grant PUSCHs by excluding a third set of configured grant PUSCHs from the first set of configured grant PUSCHs, wherein the third set of configured grant PUSCHs excluded from the first set of PUSCHs includes configured grant PUSCHs that include symbols that collide with semi-static downlink (DL) symbols; selecting a configured grant PUSCH from the second set of configured grant PUSCHs to carry the UCI included in the PUCCH; transmitting the selected configuration grant PUSCH including the UCI without transmitting the PUCCH; The PUCCH is configured to determine that there is no dynamic grant PUSCH that overlaps with the PUCCH. UE.

2. 2. The UE of claim 1, wherein the first set of configuration grant PUSCHs includes a configuration grant type 1 PUSCH based on the configuration provided by radio resource control (RRC) configuration signaling, or a configuration grant type 2 PUSCH based on the configuration provided by a physical downlink control channel (PDCCH).

3. 2. The UE of claim 1, wherein the third set of configuration grant PUSCHs excluded from the first set of PUSCHs includes a configuration grant PUSCH including a symbol that collides with a DL symbol indicated by dynamic downlink control information (DCI) or a flexible symbol indicated by a slot format indicator.

4. 2. The UE of claim 1, wherein the processor is configured to select the configured grant PUSCH from the second set of configured grant PUSCHs based on an index of the configured grant PUSCH, a logical channel priority of data mapped to the configured grant PUSCH, a transmission duration of the configured grant PUSCH, a transmission start time of the configured grant PUSCH, or a serving cell of the configured grant PUSCH.

5. 5. The UE of claim 4, wherein the processor is configured to select, from the second set of configured grant PUSCHs, the configured grant PUSCH having the smallest index of each configured grant PUSCH, the highest logical channel priority of data mapped to each configured grant PUSCH, or the shortest transmission duration of each configured grant PUSCH.

6. 2. The UE of claim 1, wherein the processor is configured to operate a medium access control (MAC) layer to select the configured grant PUSCH from the second set of configured grant PUSCHs.

7. 2. The UE of claim 1, wherein the selected configuration grant PUSCH further carries data generated by a logical channel (LCH) of a medium access (MAC) layer to be transmitted to the base station.

8. The UE of claim 7 , wherein the data is selected from the logical channel of the MAC layer without satisfying a pre-configured condition for mapping the logical channel to the selected configured grant PUSCH.

9. 9. The UE of claim 8, wherein the logical channel of the MAC layer does not satisfy the pre-configured conditions for an allowed subcarrier spacing index value, a PUSCH transmission duration, a configured grant type, cell information, a configured grant index, or a priority index.

10. 1. A method for a user equipment (UE), comprising: Identifying a physical uplink control channel (PUCCH) configured to carry uplink control information (UCI) to be transmitted to a base station; determining a first set of configured grant uplink shared channels (PUSCHs) based on the configuration received from the base station, where each configured grant PUSCH in the first set of configured grant PUSCHs overlaps with the PUCCH and is configured to transmit data from the UE to the base station; determining a second set of configured grant PUSCHs by excluding a third set of configured grant PUSCHs from the first set of configured grant PUSCHs, wherein the third set of configured grant PUSCHs excluded from the first set of PUSCHs includes configured grant PUSCHs that include symbols that collide with semi-static downlink (DL) symbols; selecting a configured grant PUSCH from the second set of configured grant PUSCHs to carry the UCI included in the PUCCH; transmitting the selected configuration grant PUSCH including the UCI without transmitting the PUCCH; determining that there is no dynamic grant PUSCH overlapping with the PUCCH; method.

11. 11. The method of claim 10, wherein the third set of configured grant PUSCHs excluded from the first set of PUSCHs includes configured grant PUSCHs that include symbols that collide with DL symbols indicated by dynamic downlink control information (DCI) or flexible symbols indicated by a slot format indicator.

12. 11. The method of claim 10, wherein the selecting the configured grant PUSCH includes selecting the configured grant PUSCH from the second set of configured grant PUSCHs based on an index of the configured grant PUSCH, a logical channel priority of data mapped to the configured grant PUSCH, or a transmission duration of the configured grant PUSCH.

13. 11. The method of claim 10, wherein the selecting the configured grant PUSCH includes operating a medium access control (MAC) layer to select the configured grant PUSCH from the second set of configured grant PUSCHs.

14. 11. The method of claim 10, wherein the selected configured grant PUSCH further carries data generated by a logical channel (LCH) of a medium access (MAC) layer to be transmitted to the base station.

15. A non-transitory computer-readable medium storing instructions that, when executed by a processor of a user equipment (UE), cause the UE to perform an operation, the operation comprising: Identifying a physical uplink control channel (PUCCH) configured to carry uplink control information (UCI) to be transmitted to a base station; determining a first set of configured grant physical uplink shared channels (PUSCHs) based on the configuration received from the base station, where each configured grant PUSCH in the first set of configured grant PUSCHs overlaps with the PUCCH and is configured to transmit data from the UE to the base station; determining a second set of configured grant PUSCHs by excluding a third set of configured grant PUSCHs from the first set of configured grant PUSCHs, wherein the third set of configured grant PUSCHs excluded from the first set of PUSCHs includes configured grant PUSCHs that include symbols that collide with semi-static downlink (DL) symbols; selecting a configured grant PUSCH from the second set of configured grant PUSCHs to carry the UCI included in the PUCCH; transmitting the selected configuration grant PUSCH including the UCI without transmitting the PUCCH; determining that there is no dynamic grant PUSCH overlapping with the PUCCH; Non-transitory computer-readable medium.

Images